Pair Programming: Better Than Adderall
summary
Pair programming at Pivotal Labs puts two engineers at one workstation, pairing eight hours a day with two keyboards and monitors, giving instant code review and daily pair rotation so six engineers cover every story type. Test-driven development provides a runnable test suite to commit directly to master, find the failing test to resume work, and safely refactor. The concrete claim: these practices replace coping hacks and even medication—one engineer reports he stopped taking Adderall and moved into engineering leadership.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:10Attention Deficit Disorder
- 5:50University Accommodations
- 7:26Second Job
- 10:22Retrospective
- 11:27What is Pair Programming
- 19:25What is TestDriven Development
- 21:05Why TestDriven Development
- 23:47Distractions
- 27:08Why Pivotal
- 30:10Empathy
related talks
32mI Have Pair Programmed for 27,000 Hours: Ask Me Anything!
53mHow to really work together as a team
41mPair Programming
48mPair Programming, TDD and Other Impractical Things
52mPair Programming: Poop & Pee adventures
34mMinimizing Decision Fatigue to Improve Team Productivity
23m10 x your teamwork through pair programming
33mSherlock Holmes and Pairing