Developer First Culture
summary
Company builds an internal engineering excellence team, grows 1→80 in 20 months, and standardizes stack and workflow: GitHub Enterprise + Jenkins + Danger + Code Climate + RuboCop. Pair‑programming stations, mandatory linters, CI/CD pipelines, and pull‑request approval rules enforce code quality; TDD is encouraged but not yet universal. Office hosts 20+ meetups and weekly tech talks to raise mastery. The result is faster deploys, fewer regressions, and higher developer retention.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 1:02My GitHub profile
- 1:58SP Digital
- 3:19Engineering Excellence Team
- 4:07Developer First Culture
- 4:50Optimizing for Developer Happiness
- 5:16Why Optimizing for Developer Happiness
- 6:46Quality Work
- 7:16Happiness
- 9:24Software Craftsmanship
- 10:29Software Craftsmanship Manifesto
- 11:28Developer Happiness
- 12:31Development Practices
- 18:02Daily Standups
- 18:18Programming Stations
- 18:57Code Practices
- 20:43Programming Languages
- 21:26Tools
- 21:57Why GitHub
- 22:44Documentation
- 23:40Integrations
- 25:27Request Approval
- 25:58Status checks
- 27:05Environment
- 28:00Internal Tech Talks
- 29:29Public Conferences
- 30:24Tech Talks
related talks
45mFrom 5 to 100 in Product Development team in just 5 years
49mCoding Culture
21mGrow-thrive-make a difference: Leading through uncertainty
51mBuilding a High-Performance Team is Everyone's Job
28mScaling DevOps Talent in a Large Enterprise
27mBeyond developer
45mDeveloper Joy – How great teams get s% t done
24mFrom Developing Code To Developing People