People and Culture
summary
Teams explain what actually changed: a cross-company SRE team plus a platform team that builds reusable libraries, with responsibility for reliability across ~350 people. A move to a monorepo and continuous pushes (about 20 to 100 times per day) gives visible infra and app code, enabling on‑the‑job learning. They use mob programming, inner‑source shared Docker images, TDD, and pull‑request reviews; forks happen when needs diverge. The claim is practical: these practices speed onboarding and reduce handoffs.
AI-written summary · about
chapters (16)
- 0:00People and Culture panel intro
- 2:51Team organization today
- 4:35DevOps adoption challenges
- 8:28From rigid to self-organized
- 11:41Value of team roles
- 15:55Management efficiency concerns
- 18:44Ownership in DevOps
- 20:06Knowledge sharing benefits
- 23:39Benefits of a monorepo approach
- 26:50CI without feature branches
- 27:34Learning culture encouragement
- 31:10Shared ownership in practice
- 34:41Mob programming
- 37:57Collaboration balance
- 40:21Including introverts
- 43:53Closing remarks
related talks
36mRebooting Culture
59mTech leadership, one year after
26mFrom Nothing to SRE: Practical Guidance on Implementing SRE in Smaller Organisations
41mBuilding an SRE Capability Inside a Large Organization
22mBuilding SRE: Culture from the Outside In
51mFrom the Trenches - Remote Scaled Trunk-Based Development
13mWhat To Do When SRE is Just a New Job Title?
22mCreating a team mindset of continuous improvement