, 3 tweets, 1 min read Read on Twitter
This is an absolutely inspiring story of how one company transformed its culture and practices to let engineers own their code in production, with 3 SREs supporting 15-20 devs on a single monolith codebase.
One super important point: being on call rarely is a way worse experience than being on call regularly. In my experience, a six week rotation is the sweet spot.

Another: you need to have oncall buddies. They have three oncall at all times, primary/secondary can also work well.
Impressed at how well they worked to split up responsibilities: three rotations inside a single monolith is an advanced maneuver. Nice work.

My favorite detail is the CODEOWNERS file ☺️

We need more case studies like this. Thanks for sharing @molly_struve and team!! 🎉🎈
Missing some Tweet in this thread?
You can try to force a refresh.

Like this thread? Get email updates or save it to PDF!

Subscribe to Charity Majors
Profile picture

Get real-time email alerts when new unrolls are available from this author!

This content may be removed anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Follow Us on Twitter!

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3.00/month or $30.00/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!