I think it's valid to take on Technical Debt, but only when it's been explicitly decided that there's a good reason to take on technical debt. It's when you make a habit of always taking the quick and dirty approach and never take the time to refactor that you start running into problems.
The idea is to not always say "we'll do it later". "Later" works fine as long as the various decision-makers involved can be talked into doing it later. If their answer is always "if it works, don't touch it," then they are the target audience for that old saw.
5 comments
[ 4.9 ms ] story [ 17.7 ms ] threadJust like real companies, bootstrapping sounds like the ideal situation but it's not the reality for most people.
"If you don't have enough time to do it right, when will you have time to do it over?"
It always seemed to me that an answer of "later" is potentially completely valid.