bluelightning2k

All I can think of is Doctor Evil issuing a ransom for 100 billion dollars... Or I defrost your fridge.

Not every comment I have is useful sadly but it's weird where the mind goes

Thanks, great perspective and explanation.

I must be getting dumber as I get older. I genuinely can't work out what Dots actually is.

It seems like a dumbed down reskin of Codex/ChatGPT Work but with the power-user features e.g. visibility/mentions removed. As a serious engineer why would I want that? Then the word agent becomes dot.

It also seems to be running a VM so the agent has its own computer.

I guess the intent was to pull together the Codex, claw and ChatGPT Work paradigms and simplify them?

I like Cognition as a company and hope they succeed. Seemingly excellent engineering org.

I used to really like Windsurf. (Now Devin. Kind of? But also now Antigravity.) I still use it as my editor but haven't touched the agent for a while simply due to the rise of Codex.

I wonder if the best analogy here is Amazon.

They allow 3rd party sellers in their platform and in their warehouses

There's many reasons for this but they include:

Somebody will compete in every segment: building the taxis, operating them, and vertically integrating them. Put another way - some people will buy taxis in this model either way, so Tesla is incentivized to participate in this also. That helps them get economies of scale.

It also of course minimize risk. But not just the obvious kind. It also minimises risk of a niche competitor taking the buy to own robotaxi market and from that wedge becoming a substantial competitor.

But also like Amazon - operators should worry about Tesla taking the data they have about most successful routes and using that to compete directly in the must lucrative identified markets.

Actually, while I still like your point there really is still a lot of operational work.

You need to clean, inspect, repair, insure, secure and charge the cars. To do so efficiently you will need to custom develop premises full of chargers and efficient charging and cleaning infrastructure.

That absolutely is operationally intense. Premises, permits, construction and then significant operations.

That's actually a very good point.

Also if Elon Musk has a demonstrable superpower it's the ability to raise capital. So they really could order 100,000 of these themselves.

If I was building this for serverless I would transform with two copies of the code: instrumented and not. Then do one single if statement between them.

If you are transforming anyway you're looking at virtually zero dev time cost and runtime cost when no probe is active of less than 1 ms.

This approach survives any environment I know of and has almost zero runtime cost.

I like your product and team. j think you have something here.

You wrap it but there must be some kind of call you're making to your API. So are you saying that call fires immediately, races the main wrapped execution, and is therefore done when the execution is finished, therefore neglible latency except for cold starts on extremely short functions?

How does the probe function technically. Inspector API I believe is unavailable on CloudFlare etc.

I once wrote something like this which could work on serverless platforms without the Inspector API. It used Typescript AST transforms to insert no-op listeners at every line, so they would dynamically eval or dump breakpoint style if a listenToLine parameter equalled their line, otherwise no-op. So trivial but not technically zero runtime cost.

This debugging in production thing has always been interesting to me. Rookout, etc.

How does it work? Using the NodeJs inspector API or other language equivalent to drop breakpoints? Those APIs are unavailable in many serverless environments and are challenging to use alongside bundlers.

You are a very talented 15 year old engineer. Not a wannabe. Just getting a head start on the imposter syndrome!

Welcome to the club

Why is it hard? Ultimately you take whatever your signal is and send it to some relatively cheap LLM.

How is it easier to sign up and manage a different service, implement a different API, etc.

And from the company side the fatal flaw is that these types of tools rely upon 1% of their users having huge spend. Nobody is going to be a huge spender here because it's easier to hand roll than navigate procurement on this (not to mention impossible to justify the spend, additional security/privacy risk, etc.)

It feels approximately impossible for this company to have large accounts.

Why... why do companies keep taking every tiny feature and trying to productize it?

In the tradition of boring software, even before LLMs it was much simpler to just use your existing tools and hand-roll. With LLMs I cannot fathom reaching for a product for something small like this.

Must admit, for this particular case I don't see the appeal in using a wrapper.

Why would I not just use Codex directly?

The we wrote a bunch of prompts argument is kind of meh. That sort of thing has not only diminishing value with subsequent model releases but I actually believe will turn negative. The model will know better by default.

For example, initially giving the model some advice on code best practice was helpful. But now it's unhelpful because the model already knows best.