The two dimensions of Technical Debt
Technical Debt is a powerful concept, first described by that name by Ward Cunningham in 1992.? It is readily understood and easily communicated.? It’s useful even to a non-technical audience, because we all broadly understand about financial debt.?
As argued by Cunningham, as soon as you deliver your first code, you have a set of implied commitments.? From that point, the code which you have shipped will incur an on-going cost.? Effectively you have incurred a debt from releasing that code.
It's worth noting that Cunningham worked in a finance company and saw carefully managed debt as potentially an asset...
I have built and led technology groups in multiple high growth scaling organisations, working across the organization to coach teams and develop and scale the structures and practices which allow the teams to thrive and achieve repeatable delivery of business value.
I am available for both consulting and full-time VP Engineering/Operations roles in Cambridge and London.