Post

This is utterly unhinged in the best possible way. High praise for running a tour of the plane while it's a quarter-built and mid-flight. steve-yegge.medium.com/welcome-to-g... Some choice excerpts.

Yegge is certainly a flavour. This so ahead of the curve I'm considering it as a piece of speculative design. Interesting: 1. Design and planning becomes the bottleneck when you hand all production code over to agentic systems. Design is a bottleneck *even when* the interface is just a TUI...

2. The cost could be as much as $2k+ / month? (wild speculation - open to more accurate guesses) At this early stage the efficiency of the system is literal shit, so the cost ≈ valuable output equation is inaccurate. But companies would pay ~near this for a high quality, low waste version of this

There's a central orchestrator, implementation monkeys, a git merge resolver, an unsticker who troubleshoots issues, a work hustler, maintenance workers, special ops teams. Agents with specific roles working in a cohesive flow with trad programming supports: git, daemons, issue tracking, tmux

I'm not going to claim I entirely understand the workflow primitives even after a couple reads (does this diagram help? no? no) But the gist seems to be breaking tasks down into atomic units of work, tracked in git, executed, checked, and merged through a zoo of loops and pre-defined workflows.

I'm in fruitful debates with colleagues over projects like this. Namely: how much hands-on access to code do we think developers will need in the next generation of tools? How close does it need to be? I'm in the code-must-be-close camp, at least for the next 2 years. My bias is I do front-end...