Comment by skydhash
1 day ago
> Code review is (for many) the least fun part of programming.
I'm lurking around the OpenBSD mailing list and it seems that code review is where collaboration starts. You send a patch, explain its purpose, people try it out and comment. If it's OK (various factors decide that), it's imported inside the codebase.
The main issue in corporate settings is that the author of the PR wants to browbeat you into accepting his/her changes. Either directly or by appealing to the manager. They don't want collaboration, they just see you as the blocker between them and the "Done" status on the ticket.
I used to work at a company that did in-person pair review. I wasn’t an engineer there but the engineers all legitimately enjoyed the process. They hired very capable people as a default, so it was watching two passionate and talented engineers debate.