In a recent paper, a Google research team details how they empirically determined the types of technical debt and ways to manage it inside the organization. The ideas in the paper bear a very close resemblance with Usable Software Design, in that the engineers are interviewed about the challenges they face with the design and help define technical debt.
We comment on the paper and these similarities, and offer alternate ways to do the same thing inside smaller organizations.
Links:
- The paper “Defining, Measuring, and Managing Technical Debt” by Ciera Jaspan and Collin Green https://ieeexplore.ieee.org/document/10109339
- The book “Usable Software Design” by Alex Bolboaca https://leanpub.com/usablesoftwaredesign/
- Ward Cunningham on the Debt metaphor https://youtu.be/pqeJFYwnkjE
- Ward Cunningham’s wiki, a treasure trove of wisdom about software development; eg. https://wiki.c2.com/?MetaphorsForNontechnicalAudience
