'Technical debt' is a software development term, but it seems to me it could also describe an institutional practice generally. The term refers to "a process where developers make a conscious decision to ship code with known limitations into production." This is done in order to get something out there quickly and to get early feedback. The rapid deployment of 'remote learning' could be thought of as the institutional form of technical debt; it was a rapid response, but it created a requirement to later come back and address the limitations the initial rush to production didn't address. Institutions may feel their technical debt may be discharged by the end of the pandemic, but that way of thinking about it creates the risk that they'll never catch up - technical bankruptcy. Image: ProductPlan.
Today: 5 Total: 21 [Direct link] [Share]
