> Nobody should be writing code with the goal of passing a code review. It's not backwards. Code needs to be readable, well thought out, bug free. Code review

> Nobody should be writing code with the goal of passing a code review. It's not backwards. Code needs to be readable, well thought out, bug free. Code review (done well) helps establish these points. > If you're writing a system that requires 5000 lines of code, it's a waste of your time to figure out how to break it up into 5 or 10 PRs I guess if you think those 5000 lines are perfect that makes sense. Often big PRs in my experience have a lot of issues that the authors and other reviewers will have trouble catching. > Once they've demonstrated their ability to write good code, from that point forward you trust them not to screw things up. Ha! I don't even trust myself not to screw things up.