Being in a senior role I find I often run into resistance, especially from product manegers, when it comes to trying to really get to the bottom of some requirement. Sometimes I find myself second-guessing if I should bother.

This article was a good reminder that I should bother.

I'm a big fan of keeping notes as I work, as I develop software. I like to /try/ and take a lab notebook approach where possible. But, to this day, I've not really settled on the "one right approach".

Here's someone else's approach...

While most of the article is written as a joke, I've seen some of these "dark side" approaches for code reviews done by actual people who don't seem to want to use code review to lift everyone.

Saving this so I can relive the trauma.