I'm very good at telling agents what to do. That's not a problem. I understand a code base I worked 20 years in like no one else. The problem creeps in slowly: the less I know about this code base, the worse I'll be at directing agents. They'll do ok on their own, and they can certainly help me understand code too in a way my colleagues never could. But still, I'm slowly becoming less and less familiar with my own code base. In a few years, it would be foreign to me. And I would be describing changes in terms of high level features instead of architectural changes, refactorings and so on, that I do now. And I don't yet trust the LLMs to do a good job with that. So right now there's sort of a honeymoon period when the human understanding of code is good, and the LLMs are finally good enough to write and modify code. But I wonder what will happen after that.
If anything, LLM coding makes to me the case that we should all move to high legibility paradigms.
If code writing is accelerated, and there's not more assurance that at least someone knows the code because they actually wrote it, we should only ever generate code in very explicit and readable ways.
I'm having a lot of success with this approach. I don't want to encapsulate it in terms that might trigger emotional responses, but there have been texts and tooling available for decades that enable writing code in very specific ways that make the code base extremely readable and reasonable. These techniques were historically considered cumbersome and pedantic exercises in purity (hint) but now we have these metaphorical heavy duty tractors for syntax and semantic work so they suddenly become so much more tenable and arguably the only sane approach to scale up the usage of these power tools of the mind.
1: Carefully pick critical areas that I do by hand, and have AI do the other 90%.
2: Make small changes by hand before / after doing the work with AI.
Most important: Slowly rotate the areas that I do by hand. This way, I keep my hands-on knowledge good enough to give AI knowledgeable instructions.
"Mentor review" describes the situation where there is a knowledge imbalance between the author and reviewer. It can represent an onboarding situation but it isn't static - there are always areas of the codebase that some people are more familiar with than others.
A "peer review" is more the situation where both the author and reviewer have similar knowledge in a given area. The purpose of the review here is primarily to look for oversights.
I'd say, the peer review should be deprecated at this point. AI can generally do a better job at looking for minor / localized problems. The "mentor" type review should stay however as it is still very valuable.
This one worries me enormously. What happens when we stop adapting the stuff we know, and everything becomes code we've inherited from someone/something else?
While I haven't worked on any 20yo code base, while working on my projects, I have found that iteratively I am asking to do many of the low-level things like architectural changes and refactorings.
These situations often pop up when I am not getting an expected output, multiple back and forths, specific bugs, continuously flaking tests. I usually then ask it to explain the architecture and what's going on. I add the patterns it's missing or I feel it should consider from next time onwards, to the harness.
It's not the same as pre-llm era but I think this is how things are going to evolve.
I think of clankers as "lossy intention amplification and reprojection devices with hopefully tasteful distortion." Whether they're amplifying and reprojecting our intentions into code or a bunch of assumptions in some specification document, I think the problems are the same: if we stop even skimming the code at some point, it will still need to serve a purpose valuable to humans to be worth anything. It's kind of like getting a device that can answer the ultimate question of life, the universe and everything: you still need to know what questions to ask it.
I have to beat the GPT and Claude models over the head with a brick every ten seconds for it to even partially code or design as well as me. Despite precise and generous specification, they frequently make horrible architectural decisions.
When I read claims like yours, I want to withhold judgement and understand, because it 100% does not line up with my experience and my gut reaction is to question your own capability to either write, read or understand quality code. I code all day long with AI models but it's an extremely frustrating experience at times. And don't even get me started on all the annoying meta behavior outside of coding, such as Sol's obsession with "tests" or competing for world's busiest-yet-least-functional UI
Most of them haven't really wrote that much code in the last 10 yrs because they became more of managers and LLMs blow their boomer minds away.
Opus 5.5/Fable will light your codebase on fire. I really dont understand yall who are that impressed. Not saying its not useful, but it isnt what this site would lead you to believe.