Technical debt and triple dept model

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/11

encourage image

There's no tags or description

Looks like no tags are added yet.

12 Terms

1
New cards

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

2
New cards

What is a debt spot

the part of the software that contain the technical debt

3
New cards

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

4
New cards

What is principal

the cost of fixing a debt

5
New cards

Interest

the cost for the extra time you have to add to understand the code

6
New cards

How to take on technical debt

deliberate debt, inadvertent debt, technological gap

7
New cards

What is a deliberate debt

the team is aware they’re taking a shortcut and accepts the costs

8
New cards

What is an inadvertent debt

the team doesnt noticing taking on the debt

9
New cards

What is an technological gap

the team made the right decision at time but the world around has changed

10
New cards

Storeys triple debt model

  1. Technical debt lives in the code, architecture and the tests

  2. Cognitive debt is the loss of the teams shared understanding of the system

  3. Intent debt is the lack of clear goals, constraints and rationales for the system


11
New cards

What is cognitive offloading

you hand a well defined task to a tool and keep the understanding

12
New cards

What is cognitive surrender

you accept ai output with little scrutiny and the understanding never forms