"Trophy Winning Teams"
summary
A dev team builds a front-end boilerplate, a Sass pattern library, and a WordPress base theme so new hires start with the same folder structure and a chosen task runner (Gulp). Style guides pair with linters (JSHint, sass-lint) and pull-request code reviews on GitHub/Bitbucket; initial senior-only review fails and rejecting PRs proves counterproductive, so reviews become collaborative. A centralized playbook lives at github.com/dxw/playbook. Team practices include pair programming, a buddy system, and regular developer lunches; these mostly improve onboarding and code consistency.
AI-written summary · about
chapters (9)
- 0:00Introduction to teamwork
- 2:23Planning in sporting teams
- 6:18Baselines in development teams
- 10:17Code consistency and style guides
- 17:05Enforcing coding guidelines
- 24:51Documentation for teams
- 28:20Team structure and mentorship
- 35:02Learning and sharing knowledge
- 38:17Conclusion and Q&A
related talks
31mScaling Happy Engineering Teams
09mScaling Frontend Teams
47mA universal fusion of the team
51mBuilding a High-Performance Team is Everyone's Job
17mHow to Ensure Code Quality and Consistency in Distributed Teams
31mProductionalizing a Data Science Team
48mLess Process, more Guidance with a Team Playbook
18mAgile leadership and technical mastery, a harmonious alliance