The paper’s interviews show what that looks like on a team: a junior software engineer described a project where only one senior engineer could approve changes and could review the interviewee’s code only once a week.
So the issue is not AI. The issue is organizations and certain personalities who think that a human is going to be a better coder than an engineer. At this point rolling and writing your own code is akin to making up your own encryption scheme.
“this is obviously true because i feel like it is” does not mean things are actually true. things should be formally measured as real trends and not just vibes.
but you prefer to be smug lmao
I was sitting with someone the other day who worked at a major ecommerce/media company (outside the US). They had access to Opus 4.5 via Co-pilot.
Back in reality, this means they have a corporate subscription to Copilot, which she doesn't use.
They limit all developer to $100/month (maybe it was $150) budget too.
Their "coding with AI" was prompts like "implement this function" where they write the function header.
It's actually shocking to see people still working like that.
Some of us have moved away from IDEs and writing code entirely and work terminal-first, while others still use agents the way I did two years ago.
For example, I recently watched someone in an actual code file adding Python import statements by waiting for Copilot’s inline suggestion to kick in. It was such a bizarre thing to witness. That’s not because of the person (I don’t want to judge anyone’s way of working; if someone enjoys writing code, that’s fine by me). It’s because I remember doing exactly that years ago, and since then I’ve stopped writing code altogether.
I even remembered that I had built an extension back then, because Copilot folks never added a quick opt-out or silent mode to Copilot inline suggestions[1].
It’s strange how fast everything has changed.
[1]: https://marketplace.visualstudio.com/items?itemName=Bubulus....
That's a bit rent-seeking on Anthropic's part, IMO.
In particular, code review is not solved. Pointing another error-prone bot at the output of your first error-prone bot, and then pressing "Enter" if the test suite passes, is not a solution.
Of course for industries and corporate it might not be an issue.
* the code does what you want
* it has no security holes
* it's able to be updated in the future without breaking everything
if the code looks like spaghetti, it doesn't really matter anymore, because humans are editing it. The only one of those three that I'm not entirely comfortable with yet is the security issue, and I don't know how to resolve it without actually having a human audit the code. If we figure out how to ensure security of AI generated code, there will be no point to code review anymore.
Genuinely curious -- are others here still seeing lots of spaghetti code from frontier models? It happens occasionally for me, but only when editing old hand-written code bases that honestly had a bit of spaghetti there already (you might say the model simply followed the house style ... :/ )
For new agentic coding projects, these is generally very nicely structured from the start and extend well, IME. Yes, sometimes it needs a refactor if the code is pushed well outside the bounds of its original scope -- but hand-tooled code will need that just the same.
But this, and other over-engineered code issues, can generally be solved at the system prompt/developer prompt/AGENTS.md level.