Nice article, enjoyed the style and the !important example is a very good one.
As Rob Tuley also alludes to, is the distinction between bad code and purposeful technical debt important?
I think Martin Fowler does a great job of explaining the point of view (http://martinfowler.com/bliki/TechnicalDebtQuadrant.html) whereby there are various ways of creating/accruing bad code/tech debt but it’s how/if/when you pay it off (or indeed try to prevent) that is most interesting.
Graham Russell
Nice article, enjoyed the style and the !important example is a very good one.
As Rob Tuley also alludes to, is the distinction between bad code and purposeful technical debt important?
I think Martin Fowler does a great job of explaining the point of view (http://martinfowler.com/bliki/TechnicalDebtQuadrant.html) whereby there are various ways of creating/accruing bad code/tech debt but it’s how/if/when you pay it off (or indeed try to prevent) that is most interesting.