> So to give a quick recap, as adding more code to a product will slow down development, we should view all code as technical debt. Not a fan of this habit of

> So to give a quick recap, as adding more code to a product will slow down development, we should view all code as technical debt. Not a fan of this habit of taking a perfectly good technical term and redefining for another purpose; especially if there is already good, existing measures, such as code complexity. Rather, than calling all new code "technical debt", how about every planned feature, as part of it's total cost calculation, include the incremental costs of any increased code and/or architectural complexity it introduces.