BEST OF POSTS
This is a list of the best posts.
- Top 20 Mistakes in Technology
- Joint Application Design & Architecture Review Board
- Seed, Feed and Weed to Succeed
- Fault Isolative Architectures or “Swimlaning”
- Splitting Databases for Scale
- How Technical Does The CEO Need To Be?
- Ethics: How Good Companies Go Bad
- Splitting Applications or Services for Scale
- Be A Leader!
- A Case for Technology Agnostic Design (TAD)
- Are you building the right product?
- How to interview engineers
- What every engineer needs to know
- Building High Performance Teams
- Code Review
Thanks for the kind review!
For those of you interested in getting a copy of the book, you can get one free here: http://codereviewbook.com
I agree with the conclusion of your post — any code review is better than nothing. Consider reviewing e.g. just the stable code branch, just during feature-freeze, just the “Top 10 Scariest Files” as voted by the development team, just unit tests, just new hires.
Thanks.
[...] and Severity for bugs are defined, logging definitions must be determined and adhered to. Code reviews are a way to ensure common usage. Data being sent to five different files in different formats [...]