> It's hard for me to take this article seriously without even a single example -- I can't tell if this is a strawman or not. I felt similarly: it just rang sl

> It's hard for me to take this article seriously without even a single example -- I can't tell if this is a strawman or not. I felt similarly: it just rang slightly false to me. For one thing, a code review wouldn't be the first solution I'd reach for when diagnosing the kind of problems described (performance issues, memory leaks, random crashes). There's plenty of tooling available for most platforms that will generally get you to a solution more quickly and reliably (granted, the post mentions only spending half a day), and often highlight problems you might easily miss in a code review. I'm not saying code reviews aren't useful, but that measurement of real-life behaviour can be more useful in these circumstances. Still, the point about not copy-pasting code directly from the internet is well made: been bitten enough times over the years that I've become extremely wary of it, even - and perhaps especially - when in a hurry.