SRE (and DevOps) at a Startup
summary
Split is a feature‑flagging SaaS at Series B with a few dozen engineers, and the claim is that startups must choose between developers wearing the SRE hat or hiring a dedicated SRE; hiring wins when outages, blocked releases, missing logs, or untracked production code cost weeks. Practical rules: metrics first, use SaaS for capacity where possible, enforce CI mandatory and semantic versioning, prefer trunk-based development, centralize alerts/incident channels, and have SREs embed in teams to build automation, monitoring, and repeatable releases.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:12SRE (and DevOps) at a Startup
- 0:49My Background
- 1:22What is Split?
- 1:44Overview
- 2:29What is SRE?
- 5:35DevOps is Not a Job Title
- 6:50Life at a Startup
- 8:33Lots of Pieces
- 9:15Developers Have Product Focus
- 10:44Specialist (aka SRE)
- 12:44Pure DevOps vs Specialist
- 13:58Who To Hire
- 16:11SRE Hierarchy of Reliability
- 17:03Metrics and Monitoring
- 18:41Incident Response
- 20:20Release
- 22:24Capacity Planning
- 23:02Summary • SRE is an implementation of the DevOps paradigm.
- 24:38Questions?
