[3vidence]

I'm not sure I understand the argument or value of this post?

It feels close to just saying, make your code better and you will see less bugs.

I don't disagree but the product environment has a lot to do with how features get deployed and how closely a developer can match the real life deployment to their development setup.

World class experts make mistakes all the time, I think learning how to address bugs is probably a more valuable skill.

[corytheboyd]

Yeah I was expecting real, concrete tricks, something involving the right/perfect(?) combination of language, tool, pattern, etc.

This is just “think correctly, and often, then, no more bugs”. Not helpful?

[atq2119]

Think correctly even if it may seem inconvenient, and thinking correctly becomes an ingrained habit. And then, a lot fewer bugs.

That's the analogy to the author's story about their exam.

(I'm pretty sure the "no bugs" part is just hyperbole to make a point.)

[nottorp]

> something involving the right/perfect(?) combination of language, tool, pattern

It's fun to spend a few lifetimes on the quest for the perfect tool.

[corytheboyd]

Exactly what I’m getting at hah, its neat to see what other people come up with, to see if I want to change my own little set of perfect tools :p We all know it’s nonsense, but we’re going to do it anyway!