@charity-majors · 50 positions · 1 change of mind · On ppll ↗
Co-founder and CTO of Honeycomb, previously an infrastructure engineer at Parse, Facebook and Linden Lab. Co-author of "Database Reliability Engineering" and "Observability Engineering". Writes at charity.wtf about on-call, hierarchy, hiring and the engineer/manager pendulum.
Charity Majors did not write this page.
We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording.
Their own site.
Is this you? Claim it or ask us to remove it.Or tell us what is wrong here.
Their wordsEither can work. Both have tradeoffs and implications. If you try to import either philosophy wholesale, it will break in unexpected ways; if you try to mix and match, it will probably be an unfettered nightmare.
Their wordsBut I also think that in my mind, 20 years of DevOps was really about one thing. Trying to create one feedback loop that connected people writing code to that code in production. And it failed.
Their wordsyou want to hire people for their unique strengths, not their lack of weaknesses. If they’re strong where you need them to be strong, it’s okay if they aren’t equally superpowered at everything — that’s why we build teams, to supplement and balance each other out.
Their wordsIt's like they have all the wisdom of their most senior engineers looking at every single diff and that is fantastic. Which means that you don't have to worry about remembering and looking and nitpicking and all the things that we're not good at anyway
Their wordsBut hierarchy is not intrinsically authoritarian. Hierarchy did not originate as a political structure that humans invented for controlling and dominating one another, it is in fact a property of self-organizing systems, and it emerges for the benefit of the subsystems.
Their wordsAs soon as you merge, it should be going out. You like you should have to stop the train to make your code not go into production as soon as you've merged.
Their wordsit's always weird to me just how much software engineers really seem to believe that the world exists in the repo. It doesn't. It's production, you know?