Re:Harvard researchers find AI coding agents shifted the bot...
by scruple on Tuesday November 17, 2026 @11:51PM
(#50542019)
I talked to some tech directors about this at work this week. Line by line code reviews aren't really possible anymore. We need the evolve the way we do code reviews but it isn't happening.
Re:Harvard researchers find AI coding agents shifted the bot...
by rhines on Wednesday November 18, 2026 @12:24AM
(#50542209)
I think the solution is to develop the infrastructure needed to confidently push code without review and trust that it works because your system is so thoroughly tested. But taking the time to do this is antithetical to the goal of speeding everything up right now.
Re:Harvard researchers find AI coding agents shifted the bot...
by dropshade77 on Wednesday November 18, 2026 @03:59AM
(#50543738)
With the rate at which new features are demanded and the number of ways a single feature can fail (or be expected to behave) do you think your approach is feasible? To what degree would AI be involved in the building of this infrastructure? Past a certain level of AI involvement, would we not be back to square one?
Re:Harvard researchers find AI coding agents shifted the bot...
by therealdrag0 on Wednesday November 18, 2026 @01:45AM
(#50542689)
Reviewing tiny code changes like that was never going to give you understanding of the system. That is not an AI problem.
You need to understand the architecture of the system. The broad flows of data and domains. And then you need to understand the features of the system, aka the rules and contracts. First learn it for your team’s domain, then for adjacent domains.
Learning the minutiae of the code specifically is no longer (was it ever?) your primary job. You are an engineer of a system. You need to have a mental model of the system, start high and build up low over time.
You can use AI to build your understanding by Q&A and by drafting diagrams etc.
Everyone's doing code reviews--well, not even code reviews; just PR reviews--so how are they supposed to gain an understanding of the system.
I review a PR, I see that one new endpoint was added to the API. It looks correct. I say "LGTM" in a GitHub comment.
The sprint's almost over, everyone's in a rush to do code reviews.
I look at another PR. Somebody added a button to the UI. The button looks correct, it's connect to some callbacks that look correct. They get a thumbs-up emoji from me. I bet they feel satisfied.
I look at another PR. Somebody changed a timeout in the settings because some people complained about dropped connections. It's a really small change, so, approved.
At what point am I supposed to understand the system? I looked at a single API endpoint, in isolation, and then a button, and then a harmless looking settings change.
I was pressured to hurry.
Am I supposed to somehow get an understanding of the big picture through this?
Imagine if instead there was time to review large logical sections of the code together. Imagine if we focused our reviews on the overall code instead of on the lines in one random PR at a time.