How Could Small Teams Get Ready for SRE
summary
Zendesk Singapore scales from 10 to 40 engineers and dedicates a quarter to technical debt, then forms a tooling team that builds a deployment pipeline using Samson deployments, a shared staging environment, Docker/Vagrant local devs and Jenkins-driven browser tests. Continuous deploy moves to a weekly release cadence with beta gating and incident postmortems. Result: fewer manual SSH deploys, rising staging adoption, fewer production hotfixes and the tooling team shifts from constant firefighting to enabling developers.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:17What Do You Mean by a Small Team
- 6:21Engineering Education
- 9:02Simple Deployment Process
- 17:34Development Environments
- 22:29Miscellaneous Initiatives
- 27:42Change in the Release Process
related talks
33mMy Journey to SRE
28mEvolution of SRE and Rising Need of SRE Catalyzers
13mSucceeding as the Lone SRE in a Small Team
45mFrom 5 to 100 in Product Development team in just 5 years
13mWhat To Do When SRE is Just a New Job Title?
42mStart Small, Scale Big: Building and Scaling Platforms and SRE Culture...
25mSRE in the Third Age
29mZero to SRE