Agreed. This really just sounded like a "Look at this new tool I found" type of article. Which is great, but I was disappointed that he didn't go over bugs that

Agreed. This really just sounded like a "Look at this new tool I found" type of article. Which is great, but I was disappointed that he didn't go over bugs that he found with this method and more specific value-adds that this helps provide. I do think there is merit to looking at code outside of an IDE (for the sake of keeping yourself focused on the task at hand), but that's what a typical code review provides. Maybe a process like this is good for looking at "bad" code and theorizing how to improve it. But even then a lot of my problems span multiple files and multiple modules (and I don't suspect I am alone in this) so it seems inefficient to print all of that out.