From Developer to Development Manager
summary
Company grows to about 242 developers and doubles every 18 months; concrete lessons focus on mistakes and fixes. A timing stopwatch added to DB causes three days of production downtime. Real‑time transcoders get a band‑stop filter to remove the vuvuzela B♭ drone and restore streams successfully. Pricing automation bug allows zero-euro microwaves to be ordered, 26 industrial microwaves shipped before detection. Use blameless postmortems, architectural decision records and a personal management README to capture intent, ownership and reduce repeat failures.
AI-written summary · about
chapters (8)
- 0:00Introduction and background
- 4:21What got you here won't get you there
- 7:51Story about listening
- 14:11Story about ownership
- 24:07Story about failing
- 33:38Story about assisting others
- 40:23Key takeaways and book recommendations
- 42:56Closing and Q&A
related talks
20mDoing Things the Hard Way
39mSPACE and Beyond - Measuring Developer Productivity
45mFrom 5 to 100 in Product Development team in just 5 years
44mFrom Developer to Manager
39mImplementing Programmer Anarchy
59mMove Fast But Don't Break Things
28mRefactoring Your Team For Fun and Profit
51mA Teacher, an Economist and a Developer Walk Into a Bar