Building a Career In Programming
summary
Panel argues individual contributors build careers by choosing projects, not titles: concrete wins include rewriting a build pipeline and tooling, shipping Python bindings that changed testing and brought interns, improving an internal code generator that reduced generated code size, and stabilizing a flaky C++ service so weekly outages stop. Managers match that with monthly check‑ins and permission to run 3–5 experiments; several side projects take 6–9 months before team value appears, but measurable metrics make them defensible.
AI-written summary · about
chapters (8)
- 0:00Off-road career paths
- 13:53Making it work
- 27:49Finding and validating ideas
- 50:10Community and team play
- 1:02:57Living with ambiguity
- 1:13:47Visibility vs criticality
- 1:21:35Earning your keep
- 1:27:17Closing thoughts
related talks
54mCareer Advice for Programmers
52mCrafting Your Career, the Open Source Way
41mPanel Discussion: How to Chart Your Own Career Path in Open Source
01h 48mCareer Path Experience Stories
50mGrowing Your Career: From Tactical to Strategic
42mIndividual Contributor Careers
25mRethinking the Developer Career Path
44mBeing a programmer in 21st century