From Keynes to Code: Efficiency & Well-being in Open Source
summary
Keynes predicted 15 hours a week by 2030 but knowledge work hours rise instead, and open source shows the same dynamics: visible metrics like commits and PRs create pseudo-productivity, faster responders attract more work in the efficiency trap, and critical infra like OpenSSL relied on two overloaded maintainers exposed by Heartbleed 2014. Concrete remedies include concentrating on a few projects, protected deep work blocks or “no‑meeting Mondays,” clearer priorities, stronger community management, saying no, and organizational sponsorship as in the Mercedes‑Benz F Manifesto and the 4,000 weeks framing.
AI-written summary · about
chapters (12)
- 0:00Introduction to talk
- 1:06Keynes' 1930 work prediction
- 3:38Reality of modern work hours
- 5:05The efficiency trap explained
- 8:17Pseudo-productivity in knowledge work
- 12:37Measuring knowledge work productivity
- 16:30Inbox zero and visible activity
- 19:44Cal Newport’s productivity advice
- 23:40Limited time and intentional choices
- 24:43Pseudo-productivity in open source
- 26:30Burnout in open source projects
- 28:18Supporting open source sustainably
related talks
23mConsumption Is Fractal: Open Source...
28mFinding a balance
17mKeynote: The Double Helix of Open Source Software & Companies
32mOpen Source: When Nights & Weekends Are Not Enough
01h 03mThe Effective Developer - Work Smarter, Not Harder.
36mThe Art of a Balanced Life (Keynote)
01h 01mWe're Building On Hollowed Foundations (...)
36mOpen Source Work Is Work