Guides

Why do we do code reviews? We have four main reasons for doing code reviews: Increase code quality Learning Context and knowledge exchange Find bugs sooner 1. Increasing Code Quality. We want to deliver high quality software. Some of our sites are very important to lots of people. They need to be reliable, stable, maintainable, testable and visible. No developer is perfect, but everyone is different and has a unique perspective....

When evaluation time comes around, I like to send this out to the developer in advance of the meeting. Then we go through each item in the level they are at and the one above. For each item, we mark it as green, yellow, or red. Green means they have many examples of this. Yellow means they don’t have a lot of examples, or they haven’t been given the opportunity yet....