Technical debt lives in the code; cognitive debt lives in developers' minds
Image putting techdebt and cognitive debt next to each other. Looks very generated btw. Techdebt described as legacy code, quick fixes, buggy logic: messy code & complexity. Cognitive debt as: lost understanding, knowledge gaps, team confusion: overhelmed developers.
Technical debt nicely captures that “human understanding” also matters, but the words “technical debt” conjure up the notion that the accrued debt is a property of the code and effort needs to be spent on removing that debt from code.
While techdebt is about the accumulation of human decisions, and the resulting erosion of human understanding, the term itself suggests it is a property of the code itself, and that one could remove it from code.
The term technical debt is often used to refer to the accumulation of design or implementation choices that later make the software harder and more costly to understand, modify, or extend over time
Techdebt def used in this article. the sum total of choices made over time that make software harder to understand / maintain / modify over time. (Is there a measure for it, when do you decide to replace e.g.? #openvraag)
By Margaret-Anne Storey, Professor of Computer Science, University of Victoria and Canada Research Chair in Human and Social Aspects of Software Engineering https://en.wikipedia.org/wiki/Margaret-Anne_Storey
added to feedreader
Techdebt, maintenance costs due to expedient choices in development to accelerate development.
Applies to software dev w AI too.
the project of building a post-American internet: a project to reduce tech debt, to unlock America's monopoly trillions and divide them among the world's entrepreneurs (for whom they represent untold profits), and the world's technology users (for whom they represent untold savings); all while building resiliency and sovereignty.
post-American internet as a project reducing tech-debt (meaning in this context?)
good points here.