← All IntelClip / AI AgentsThe 'read-only code' thesis and why it's expensive
From Loop Engineering from First Principles — Kyle Mistele, HumanLayer · ≈2:57
Pushes back on the frontier-lab position that agent output need not be read, pointing at the Claude Code flicker bug and unlimited-token budgets as evidence the approach doesn't transfer.
What’s in it
- Pushes back on the frontier-lab position that agent output need not be read, pointing at the Claude Code flicker bug and unlimited-token budgets as evidence the approach doesn't transfer.
Clip transcript
assume. And in fact, all of our loops that we're building are producing so much code that we can't possibly read all of it, right? So we might as well just not read any of it, right? We're we're investing in verification and in code review, but all this code is read only. This is the thesis of a conference that was here in town last month. So a lot of smart people at Frontier Labs think that this is the future of software development. And if you're doing this, you're moving 10x faster and everybody else is getting left behind. Now, it's not clear how well this works yet. Uh Took 6 months to fix the Claude code terminal flicker. The open code team wrote a renderer in a fraction of that time. And open claw of course also notoriously has stability issues. What is abundantly clear, however, is that this is really expensive if you don't work at a Frontier Lab and have an unlimited token budget. And all this code that we're writing is actually really expensive, right? Matt Pocock talked about this recently. Uh bad code is much more expensive in the age of agents than it it has ever been at any point in the past. So, today I want to talk about what I think works in
Comments
Sign in to comment.
Loading comments…