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.
replyArent 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.
reply1/ 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?
reply2/ 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.
Yeah, that’s the issue.
replyThere is a lot of boilerplate or I can ask for ideas, but outside of boilerplate the review step make generation seemingly worse.