Tech debt nomads and slash-and-burn development
summary
Argues that a recurring slash-and-burn loop sees a new tech lead perform a token rewrite, spend a few months rebuilding a subsystem, then leave, causing a three years average turnover and large knowledge loss. Shows that token rewrites (a single PEP system or project) deliver short-term pride but accrue new debt, enabling hero narratives and technosolutionism. Recommends staying longer, owning trade-offs, and shifting incentives toward long-term custodianship.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 0:10The slash and burn loop
- 6:57Causes of the pattern
- 8:19Psychological aspects
- 8:48Breaking the cycle
- 9:54Analyzing trade-offs
- 10:05Adopting healthier habits
