| It's way easier. People don't need to read code anymore, nor will they have to care about building mental models about the system as this article suggests. The way to think about coding agents is that a good one should in theory literally replace the developer entirely. No, a whole organisation of developers. In theory a product owner should just be able to dictate how they want to product to function at a high level and the AI should take care of the rest in the same way a human programmer or team of programmers would have in the past. If there are conflicts in what's being requested, then the AI should be able to recognise that and ask for production direction. As always with every generation of AI people seem to way over index on the now. - "They're good for autocomplete, that's about it" - "They're good for quickly mocking up small functions, but they make a lot of mistakes" - "They're good for scaffolding some parts of the system if you're good at prompt engineering" - "They're good at writing most of the code, but humans will always need to do the last 10%" - "They can write all of the code, but humans will still need to architect the system" You are here. Perhaps this is where progress stops. I wouldn't bet on that however. AI is making programming an irrelevent field. |
Furthermore, I predict they will identify massive structural issues, propose huge lifts to redo it correctly, and will instead be told to do patchwork fixes to stop the bleeding.
Now, I do think AI is (or will be) good enough to implement these patchwork fixes when given explicit instructions, but someone will need to figure it out for them.
The problem is if you don’t understand the root cause, you’ll at best feed the LLM a list of symptoms, and it will dutifully fix them. “Our p99 on this endpoint is breaching” becomes “I’ve added an index for this query,” or “I’ve added a caching layer,” when the actual problem may well be that you’re storing huge blobs that bloat your working set, cause buffer pool churn, and saturate your NIC. Is the symptom solved? Yes. Is it scalable? No, you’ll next need to vertically scale the instance, which is more expensive, and has an upper bound. Eventually you’ll decide to shard, which adds complexity, when the actual solution would’ve eliminated all of those issues at once.