Tedious tasks aren’t useless.
I’ve wanted to share this tweet for a while, and have finally found a few minutes to post it. I think it’s important.
Sometimes utility feels like futility, but someone’s gotta do it.
When faced with gnarly problems like messy databases and heartbreakingly crufty code we often sidestep the real problem: “Just throw it out and we’ll rebuild it with your favorite sexy big product/framework/language here”.
This is great, but just because something is big doesn’t mean that replacing it will solve your problem. Consider a failing football team. The stadium they play in is certainly the larges part of the operation. Will building a new one make the team better?
In the end a lot of what we do probably should be ditch-digging. Not everything is a do-over.
FUTILITY AND DITCH DIGGING - Knowing and Doing