I feel like this can be argued so many ways. For instance, while code review might block some changes from being introduced into the system, it also does have more benefits than the &quot;fluffy&quot; ones you mentioned. Maybe an engineer that has more experience with the codebase can point out a way of doing something that is more in line with what the team&#x27;s style is (earlier move toward standardized code vs letting people do what they want). Maybe you missed a utility function that already achieves what some of your code does. Maybe there&#x27;s not a bug, but again a more experienced dev sees something that can be optimized and will save time in the future that would be spent on tracing system performance issues. The idea that we need to move ultra fast as devs... I think that is necessary in some cases, but I&#x27;m not convinced that taking some time to code review tasks is as expensive as you suggested. I mean even reviewing 1000 lines of code should take no more than 30 minutes. And if it looks entirely confusing and hard to follow, then maybe it&#x27;s something to revisit because I guarantee you&#x27;re gonna be spending longer if you have to go back and refactor&#x2F;extend messy and unclean code that technically works. I think the key here is to catch things that stand out and not review the minutae.<p>This is just my opinion of the matter. On the topic of team building, I don&#x27;t really care for all that stuff. Unit tests w&#x2F; CI and periodic refactoring are great for revisiting design decisions. Code reviews are great for catching bad design decisions early on, though so use it as a tool.