One of my mentors once gave me a list of obvious things to check when stuff doesn't work. Funny, years later I still need this list:
It worked. No one touched it but you. It doesn't work. It's probably something you did.
It worked. You made one change. It doesn't work. It's probably the change you made.
It worked. You promoted it. It doesn't work. Your testing environment probably isn't the same as your production environment.
It worked for these 10 cases. It didn't work for the 11th case. It was probably never right in the first place.
It worked perfectly for 10 years. Today it didn't work. Something probably changed.
edw519, Hacker News, on debugging.
I always need that list, too.
It worked for these 10 cases. It didn't work for the 11th case. It was probably never right in the first place.
That one is counterintuitive, but true surprisingly often. Maybe not most of the time, but more often than you might think. And it picks the worst times to be right, let me tell you. Especially if it reveals a mistake in the math underlying everything you've been doing....
The solution, I suppose, is to learn to enjoy rewriting.
This is our monthly thread for collecting these little gems and pearls of wisdom, rationality-related quotes you've seen recently, or had stored in your quotesfile for ages, and which might be handy to link to in one of our discussions.