What debugging taught me about patience

This is placeholder text — replace it with the real note.

The bug that takes an afternoon is annoying. The bug that takes three days is instructive.

Somewhere around hour six of the second day, I stop trying to be clever and start actually reading the code that's in front of me, instead of the code I assume is there. That shift — from assuming to reading — is most of what debugging has taught me, and it applies well outside of software.

Patience, in this line of work, mostly means being willing to be wrong for a little longer before you're right.