The Human Element in Development
summary
Five concrete case studies show how tools expose culture: a mailing list was forked into “team” and “discuss” lists, creating confusion and signaling avoidance; engineers spend ~2% of time per month on expense reports so a company paying in >40 currencies builds its own broken system, which ships late with broken ACLs and forces a key engineer to leave; four recurring executive briefings eat ~10% of dev time with no notes or agenda; a public kanban board becomes a trophy case (webcam and CEO sticky notes) and fails to offload cognitive load; forced ranked reviews (bottom 10%) breed distrust.
AI-written summary · about
chapters (8)
- 0:00Start
- 2:14Some standard disclaimers ...
- 4:33Five Tools
- 5:16Mailing
- 6:12A Tale of Two Lists
- 19:07Predictable Results
- 21:46Agendas? Notes? Pfft!
- 23:52The Big Reveal
related talks
27mThe human cost of development
43mHumane Development
47mThe Psychology of Software Teams
35mPanel: Developer Experience and Productivity
01h 18mKeynote: Psychology of Software Development: We’re Only Human After All
34mBuilding a Culture For Developer Productivity
28mBuilding Culture through Communication
32mTales from the DevOps Transformation Trenches
