News for hackers. Stuff that matters.
Re:GPT-5.5 by dandaka on Thursday April 23, 2026 @05:32PM (#47882340)
Writing code is 10-100x faster, doing actual product engineering work is nowhere near that multipliers — no conflict!
Re:GPT-5.5 by giwook on Thursday April 23, 2026 @05:55PM (#47882635)
Reviewing code is slower now though because you didn't write the code in the first place so you're basically reviewing someone else's PR. And now it's like a 3000 line PR in an hour or two instead of every couple weeks.
Re:GPT-5.5 by 32df on Thursday April 23, 2026 @08:59PM (#47884248)
Arent most people just almost skipping this step entirely? How else can you end up in a net benefit situation? Reviewing code is more intense than writing/reviewing simultaneously.
Re:GPT-5.5 by mwwaters on Friday April 24, 2026 @12:28AM (#47885522)
Yeah, that’s the issue.

There is a lot of boilerplate or I can ask for ideas, but outside of boilerplate the review step make generation seemingly worse.

Re:GPT-5.5 by dandaka on Friday April 24, 2026 @05:07AM (#47887619)
1/ Reviewing code can't be more intense than writing. I can't understand where this statement comes from! If that would be true, why would senior developers review code of junior, instead of writing themselves from scratch?

2/ I think we need to build more efficient ways to 'QA code' instead of 'read with eyes' review process. Example — my agents are writing a lot of tests and review each other.