1/11
Looks like no tags are added yet.
What is a technical debt
the invisible result of past decisions about the code, the architecture or the tests that makes future changes slower, riskier or more expensive
What is a debt spot
the part of the software that contain the technical debt
What is the four elements of technical debt
invisible: users dont see it, devs see it when they change the software
past decisions: the debts come from how something was built
debt spot:each past decision leaves a debt spot in the code, architecture or the tests
future changes: the cost appears when the team changes the software
What is principal
the cost of fixing a debt
Interest
the cost for the extra time you have to add to understand the code
How to take on technical debt
deliberate debt, inadvertent debt, technological gap
What is a deliberate debt
the team is aware they’re taking a shortcut and accepts the costs
What is an inadvertent debt
the team doesnt noticing taking on the debt
What is an technological gap
the team made the right decision at time but the world around has changed
Storeys triple debt model
Technical debt lives in the code, architecture and the tests
Cognitive debt is the loss of the teams shared understanding of the system
Intent debt is the lack of clear goals, constraints and rationales for the system
What is cognitive offloading
you hand a well defined task to a tool and keep the understanding
What is cognitive surrender
you accept ai output with little scrutiny and the understanding never forms