alt Hacker NewsAt what point do we really not read code itself anymore? Have Sonnet/Opus write the code, work with the agents on a high level, then have Fable code review and its done.
Any bugs found are looped through agents to fix, and the cycle repeats. Why dig into the code unless for hobby? Just as people don’t write assembly anymore unless for hobby (or learning)
Only exception might be the upper echelons of optimization, like language authors or compiler level work. But even then…
Replies
If using llms is like using wordpress instead of writing the website yourself probably never
I think we are approaching the point where it no longer makes sense to have LLMs write code in an intermediate, human readable programming language.
I know this topic is very contentious but it seems very clear to me that this is the long-term direction of writing software. UI code isn't quite there yet, which is why we've got all these vibeslop websites proliferating now that all have identical crappy UIs. But I imagine it will get there too.
>Only exception might be the upper echelons of optimization, like language authors or compiler level work. But even then…
Optimization work is especially suited for LLMs. They're great at hill-climbing problems and have infinite patience to test different ideas.
You still reading code?
im not reading it. and im using fable up front earlier then having sonnet/opus implement and verify.
I stopped reading the code many months ago, probably 18 months ago. I the "early" days of agentic coding one did feel dumb when telling the agent for the 30th time to fix a bug and it just couldn't. Now I cannot possibly imagine a scenario where an agent wouldn't be able to fix a given issue on 1st or 2nd try.
I think it very much depends on what you're working on, and how much you're responsible. For a web front end, not really. A backend where a single line can make a mess out of your data? Yes. Part of the issue too, is code review brings up things you the prompter didn't think about that another teammate may be thinking about. The value goes beyond making sure the code is "correct", but also that it makes sense in your domain.
The "we don't read/write assembly anymore" argument doesn't fit though. Given an input x we know without a doubt we'll get output y. With an LLM, that isn't the case no matter how many guard rails, specs, markdown files, diagrams you give it.