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!! 🎉🎈
You can follow @mipsytipsy.
Tip: mention @threader_app on a Twitter thread with the keyword “compile” to get a link to it.
Enjoy Threader? Sign up.
Since you’re here...
... we’re asking visitors like you to make a contribution to support this independent project. In these uncertain times, access to information is vital. Threader gets 1,000,000+ visits a month and our iOS Twitter client was featured as an App of the Day by Apple. Your financial support will help two developers to keep working on this app. Everyone’s contribution, big or small, is so valuable. Support Threader by becoming premium or by donating on PayPal. Thank you.