The human cost of development
summary
Research, interviews and charts argue that technical debt is not a tooling problem but a social one: deadlines and management choices create hacks like the Foo Ltd monolith and copy‑paste plugin work that ship but don’t scale. Burnout shows up across the industry, with reported rates at over half in some datasets. Suggested remedies are structural — unions, shared control, and policies such as a four-day work week or extended paid recovery leave — not more ping‑pong tables.
AI-written summary · about
chapters (6)
- 0:00Start
- 0:05THE HUMAN COST OF DEVELOPMENT
- 2:51Not based on personal experience.
- 3:04DISCLAIMER #3
- 20:56MISSING ANALYSIS
- 22:47The common thread
related talks
28mTechnical Debt: Why it'll ruin your software
38mThe Human Element in Development
35mTechnical Debt. A guide for developers and IT managers
01h 36mWorkshop: Tackling Technical Debt: An Analytical Approach
48mTechnical Debt Trap
11mTechnical Debt Crisis! When Non-Engineers Write Code
39mStop Focusing on Tech Debt
53mThe Technical Debt Trap