To do... or not to do
Whenever I sit down to write some code in a system with technical debt (OK, honestly, that’s any system ever), I inevitably encounter bits and pieces, maybe even entire modules, that could use some serious refactoring.
My little brain alarm bells go off not only at old bugs and race conditions, but also when I see old code that simply has become misaligned with the current domain model, could use symbol naming improvements, or duplicates logic in an unsavory way.
It is tempting to “do it now” but let’s be real: you may know exactly what to do, but it’s just a distraction (and probably more trouble than you realized) from whatever important thing you were working on before.
Save that to-do for later!