The socio technical developer
summary
The core claim is that software is a socio-technical system: organizational incentives, law and financing shape code and are reinforced by it, illustrated by Conway's law example (eight researchers → five‑pass COBOL, three‑pass ALGOL). Practical tactics include coaching, ensemble/mob programming to overcome desk‑force and assumptions, incremental change over grand rewrites, and skepticism of process theater and 10x heroics. Autonomy requires accountability — e.g. teams owning their budget to make real strategic tradeoffs — and these approaches are reported as workable in large public systems.
AI-written summary · about
chapters (14)
- 0:00Socio-technical development intro
- 1:27Software as socio-technical system
- 3:32Conway's law and system design
- 6:02Joining a new dev team
- 11:17Developer goals and impact
- 14:51Human complexity in teams
- 21:37Group dynamics and identity
- 23:43Reluctance to communicate
- 29:41Rhetoric in tech discussions
- 33:10Building trust with curiosity
- 36:42Ensemble programming for communication
- 38:47Autonomy in dev teams
- 42:40Expanding team autonomy
- 43:00Conclusion: sustainable systems
related talks
01h 00mTackling Socio-technical Complexity in the Heart of Your Team
47mThe Psychology of Software Teams
28mLearn Sociotechnical Systems The Hard Way
05mSoftware Development as an Emotional System
28mContractualism + Software Engineering: We're All In This Together
22mDo We Need Software Craftsmen?
22mTechnical Debt is a Social Problem
01h 03mThe Psychology of Technologists