Humane Development
summary
Argues for humane development by naming concrete failures and fixes: shows a Kanban backlog and a real estimate that misses by 2.5×, contrasts sprint culture with Tabata and marathon pacing, cites nursing‑home experiments where giving choice measurably improves wellbeing, and traces how Scrum certification and tooling ossify into control. Proposes practical moves: treat processes as code, do process metaprogramming, ask “why” to expose fake deadlines, and aim for empathy → honesty → trust → autonomy.
AI-written summary · about
chapters (22)
- 0:00Start
- 7:17Abstraction!
- 7:46Human Resources
- 9:05Agile
- 12:37Speed
- 22:12We are humans working with humans to develop software for the benefit of humans.
- 22:56A mission statement is not enough
- 24:31Crunch Mode is an Exceptional Situation
- 25:28100% TEST COVERAGE
- 25:46Formalized processes are code for your company.
- 26:55Processes are a problem statement.
- 27:32Address the source of the problem.
- 27:45Legacy
- 28:23Process Metaprogramming
- 30:48Build small tools.
- 31:00Leave room for choices.
- 33:11Learned Helplessness
- 36:40Empathy Honesty Trust
- 36:55Autonomy
- 38:29Stop trying to substitute throughput for efficiency.
- 40:24Lead by example.
- 40:58Stop looking for people to control.
related talks
44mHumane Development
43mHumane Development
54mA Discourse in Humane Development
31mThe Effective Developer - Work Smarter, Not Harder
34mBuilding a Culture For Developer Productivity
38mThe Human Element in Development
43mApplying Agile out of development
53m26 Heuristics For Effective Software Development