DEV Community


Discussion on: The myth of "never going back to fix it later"

eljayadobe profile image

I love (in the if I didn't laugh, I'd cry sense) reading code like...

// TODO: temporary hack.
// We absolutely MUST fix this after shipping v3.

And 3.0 shipped 26 years ago, on September 1994.

Not this particular comment, because it had been fixed a long time ago. But the comment wasn't removed.

Those TODO comments become even funnier when the hack has been expanded to, and has a multi-headed hydra of behaviors that are cemented in place. And the temporary hack still has the undesirable properties (say, a memory leak, or inefficiency, or only handles the "happy path" correctly).

Weinberg's Law: If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization.