Consider systems that require continuous active stabilization to not fail because the system has no naturally stable equilibrium state even in theory. Some of our most sophisticated engineering systems have this property e.g. the flight control systems that allow a B-2 bomber to fly.
To build reliable systems the humans involved need to know what was built and how. I'm not looking for full automation, I'm looking for intelligence and augmentation, and I'll give my money and my recommendation as team lead / eng manager to whatever product offers that best.
Started with API keys, ended with self-evolving, self-healing Systems AGI... and I still have to retrieve my own API keys lol. At least the system is acquisition-ready, fully decoupled, heals its own memory leaks and stalled sockets natively, and scales horizontally.
Show HN: I Built Systems AGI – 1600 Verticals, Self-Healing, Self ...
The thing is, making everything context means our systems can be extremely fluid and language-driven, which means tool developers can do a lot more, a lot faster. It's a number go up thing, in my opinion. We could make better harnesses with stricter controls, but we wouldn't build things like Claude Code as quickly.
Seems like a cool idea—I'm always game to try new operating systems! Recently been playing around with Playbit (https://playbit.app/) Pneuma reminds me a little bit of Yansu AI, a project I saw recently on HN that proactively builds apps with AI (https://yansu.app/) reply evanbarke | parent [–]
What do the relatively hands-off "it can do whole features at a time" coding systems need to function without taking up a shitload of time in reviews? Great automated test coverage, and extensive specs.