Pretty sure this counts as a humble brag.

The program manager got wind that we were seeing a lot of system crashes during testing, and he wanted to know why the redesigned system was crashing so much more often than the one it was replacing.

When fixing things, sometimes it is important to go slow. Don’t expose all the hidden errors all at once. Save the company money a few percent at a time, not all at once. Big changes tend to get the wrong kind of attention.

Just came here to say that on the photo is Gromozeka. He is an archeologist, not a programmer.

I’m glad that engineers don’t approach things the way that code monkeys do.