The writing got faster and nothing ships faster. Review is the bottleneck now.
retained text
Curious if this is just us. The coding part of my job has genuinely gotten quicker this year. Stuff that used to take me the better part of a week now lands in a day. But our sprints haven't gotten any faster, and when I actually look at where the time goes now, it's review. What I didn't expect is that reviewing got harder, not easier. When I wrote the code myself I knew which four lines I was unsure about, so I'd say so in the description and someone could glance at those and approve. Now I open a diff I didn't watch being written and I have no idea which parts the author actually understands and which parts just appeared. So I read the whole thing properly, the way you read a stranger's work. The habit that helped most is embarrassingly small. I ask for a two-line note in the PR saying which files the author is confident about and which they want a real look at. It saves me a lot of time, and it tells me something more useful, which is which PRs nobody in the room understands. Those are the ones worth slowing down for. The other change was that we stopped treating an approval as the end of it and started asking who can answer questions about that code two weeks later. That shifted behaviour more than any process document we wrote. I'm not looking for AI review tool suggestions here, I've tried a few and that's a different argument. I want to know what you ask the human to do differently, because that's the part I haven't figured out.
document fetched 2026-11-03 00:25 · canonical https://reddit.com/r/developersIndia/comments/1xlmskc/the_writing_got_faster_and_nothing_ships_faster