News for hackers. Stuff that matters.
Re:Harvard researchers find AI coding agents shifted the bot... by bob1029 on Wednesday November 18, 2026 @01:48AM (#50542711)
[delayed]
Re:Harvard researchers find AI coding agents shifted the bot... by hgomersall on Wednesday November 18, 2026 @02:36AM (#50543000)
But now it's the owners doing the review. We had a debate this week about AI coding policy and the conclusion was we had to be much more aggressive in our strategy to fully understand the whole thing. With respect to a pretty trivial code base I made multiple changes during that "review", which was actually closer to a break the tests then fix the tests loop, fully grokking every line. I expect it was not much quicker than writing the whole thing, though much of the more tedious parts were automated.
Re:Harvard researchers find AI coding agents shifted the bot... by Seattle3503 on Wednesday November 18, 2026 @03:16AM (#50543333)
> I think code review like this has always been a bad idea. Code ownership is what you want. Put developers on the hook with git blame perpetually. Why should a developer be excused from responsibility the moment a PR merges? This is the core of the dysfunction.

I lead a team. Someone wanted to do something that I thought was a bad idea. I said "we can do this if you own it" and they said "yes". They quit a few months later. Now I own it. I'm thinking about switching jobs soon.

Re:Harvard researchers find AI coding agents shifted the bot... by bengold14 on Wednesday November 18, 2026 @03:59AM (#50543743)
I respectfully disagree - code review is currently obsolete, but it was an important tool:

1. It was good for collaboration. Sharing how you are changing the codebase pushes everyone to row in the same direction, and provides a sense of team ownership.

2. It was good as a push for engineers to take pride in their work. Knowing someone is watching gives you subconsciously an extra reason to not cut corners. And when you spend effort not cutting corners you expect that in your teammates, which is a (potentially) virtuous circle.

3. It was good for catching mistakes. When code was expensive this was important.

Everyone thinks of code review as primarily relevant for 3, and since code is no longer expensive they think it is unimportant. But 3 isn't dead, its importance has just shifted from code to architecture. It is still an expensive mistake to screw up architecture and have other engineers build upon that flaw. Re-architecting with live users, data and/or hardware is not as simple as fixing a code bug, and it deserves attention to catch mistakes. Collaboration & pride are also still important.

This is the reason that instead of stopping review, we need to change what and how we review.

(disclosure I work in this space and run https://www.archme.io which is working to solve the above)