This is really cool! My dad always talked about the one he had when he was much younger.
In a similar vein I’m teaching my son to rebuild an old ‘62 VW that’s been in the family since ‘62 and am constantly reminded of how nice it is when things are simple. And I’ve learned that the dollars spent are not that important when you are having fun and learning or teaching something!
I got a little annoyed (okay, more than a little) with agentic developer tools and started building a replacement that I use every day now for development - both at home and at work. I have found that starting with an idea or design, using that to create a proper implementation plan, and then asking an agent to build something has been the most effective workflow for getting what I want (and that I don’t trust most models to not accidentally delete everything from my computer).
So I built an app that combines that workflow with some code dependency graph and sandboxing ideas (semi-structured build manifests with auto-installing tools / isolation) from a startup I previously co-founded, along with a handful of other tools / features (like virtualized code workspace over gRPC that works locally or remotely, starlark for scripting, a debugger with an investigation log and proposed fixes, dependency analyzer, security reviewer, and per-agent models/providers so I can use more expensive models for more complex work, like design or debugging work, and cheaper models for writing code) and built my own day-to-day development assistant that I’m pretty happy with!
As an added bonus, since I don’t like being stuck with one provider, it supports most any LLM provider (including local ones) and I can seamlessly switch between providers or models in the middle of my work if one is offline or going in circles.
Except that in the specific example I have (this is my post), the results of the inner select (I would assume) should be cached because the condition in the inner select is a fixed set of criteria, not related at all to the outer records. Also of interest is that NOT IN(insert subselect here) doesn't raise the same issue. Additionally it prevents the entire query from using any indices... I have lots of interesting query planner results from this particular go around.
Also it's been fixed in 6.0-alpha just not back-ported, so I'm not sure I agree here.
Initially workers are hosted by you but down the road we're looking to add some nice hosted / management features for those who want it (think github hooks for auto-deployment / upgrading of workers) If your data is sensitive you can always encrypt it without too much overhead. We're working on supporting SSL for transport and we have IP-based restriction to queues along with a management console. In our experience, most of the data that goes through our systems is pretty meaningless without context (but we understand that some folks will want something a little extra.)
In a similar vein I’m teaching my son to rebuild an old ‘62 VW that’s been in the family since ‘62 and am constantly reminded of how nice it is when things are simple. And I’ve learned that the dollars spent are not that important when you are having fun and learning or teaching something!