Google Technical Debt approach vs. Usable Software Design

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.


More from the Blog

Leave a Comment

Your email address will not be published. Required fields are marked *

    Your Cart
    Your cart is empty
      Apply Coupon
      Scroll to Top