Code review checklists are usually a pain. They’re often ridiculous in length or content. They’re not fun to use. Checklists can be an excellent way of finding defects early in the development process, but most of the time, checklists are so impractical that they’re more of a hindrance than a help.
The problem is that people use the list as a general guide. They don’t consider every item in every file. Which items will they remember as they look at the code? Will it be the most important ones?
If you want to continue reading Jason Cohen’s article at Embedded.com, click here