Tag Archives: what to look for

We’ve had two themes running through the articles on what to look for in a code review: Lots of what we’re tempted to look for can (and should) be automated Humans are good at checking things computers can not. In … Continue reading →

This is part 6 of 6 posts on what to look for in a code review. See previous posts from the series. How much work you do building a secure, robust system is like anything else on your project – it … Continue reading →

This is part 5 of 6 posts on what to look for in a code review. See other posts from the series. In today’s post we’ll look more closely at the design of the code itself, specifically checking to see if … Continue reading →

This is part 4 of 6 posts on what to look for in a code review. See previous posts from the series. Data structures are a fundamental part of programming – so much so it’s actually one of the areas that’s consistently … Continue reading →

This is part 3 of 6 posts on what to look for in a code review. See other posts from the series. In part three of our series on code reviews, we’re going to cover what you can look for in … Continue reading →

This is part 2 of 6 posts on what to look for in a code review. See other posts from the series. In the last post we talked about a wide variety of things you could look for in a code review. … Continue reading →

This is part 1 of 6 posts on what to look for in a code review. See other posts from the series. Let’s talk about code reviews. If you take only a few seconds to search for information about code reviews, … Continue reading →