Some checkers write their defect markings on a separate paper instead of the printout of code they are meant to scrutinize. You might even write down everything necessary, including the reason of the issue, the severity of it and the location where it resides. The list of items certainly looks orderly and nice, but the reality of the situation is messier. Often it happens that you can't completely understand a marking on the list without the actual location in code, where you found it. To explain your finding to the author, you need to turn to the right page in the code, check your notes again and try to synchronize your thoughts. Time is wasted and still some of your findings are lost because you can't find the real reason again.

A less than optimal way to report findings is listing them on a separate piece of paper or email or in any way that is not directly connected with the reviewed subject. This is one of the things that can go wrong in a code inspection. The text is an excerpt from Chapter 2. "Symptoms".