- #HOW TO SIGN OUT OF FACEBOOK CRITICAL OPS MANUAL#
- #HOW TO SIGN OUT OF FACEBOOK CRITICAL OPS SOFTWARE#
- #HOW TO SIGN OUT OF FACEBOOK CRITICAL OPS CODE#
It’s the prerequisite thing you have to do, in order to get to the stuff you want to do.
#HOW TO SIGN OUT OF FACEBOOK CRITICAL OPS SOFTWARE#
YOUR core business model probably has nothing to do with infrastructure.īecause of that, a great sort is now happening between software engineering, infrastructure operations, and core business value. The value of serverless is unlocked by clear and powerful abstractions that let you delegate running large portions of your infrastructure to other people who can do it better than you - yes, because of economies of scale, but more so because that’s their core business model.
#HOW TO SIGN OUT OF FACEBOOK CRITICAL OPS CODE#
The value of serverless isn’t found in “less ops.” Less ops doesn’t yield better systems than more ops, any more than fewer lines of code means better software. Operations is the constellation of your organizational memory: patterns, practices, habits, defaults, aspirations, expertise, tools, and everything else used to deliver business value to users. Business is the why, development is the what, operations is the how. The way to do something well generally starts with adding focus and rigor, not writing it off.Ĭonsider Business Development and Operations. When you denigrate it and diminish it, that’s the first sign that you aren’t doing it well. If this is such an inexorable march towards utopia, maybe someone can explain to me why the shops that flirt the hardest with #NoOps have been, without exception, such humanitarian disasters? The existence of ops is a technical failure: a blemish to be automated away, eradicated by adding more and more code.
#HOW TO SIGN OUT OF FACEBOOK CRITICAL OPS MANUAL#
In some corners of engineering, “ops” is straight up used as a synonym for toil and manual labor. Where are Ops careers heading? Where Does Ops Fit, Anyway? The reality for most teams is that operations engineering is more necessary than ever.īeyond Hamilton clap backs, that distinction matters because it has real career ramifications for engineers who, like me, are so operationally minded. At best, the shifts that supposedly reduce your ops are simply delegating the operability of your stack to someone that does it better.
I hate to be the bearer of bad news (not really), but the role of operations isn’t going away. BUT, unfortunately, the chorus chose to double-down on one of the stupidest and most dangerous tendencies the serverless movement has had from day one: misunderstanding and trash-talking operations.Įven if you don’t run any servers or have any infrastructure of your own, you’ll still have to deal with operability and operations engineering problems. I love Hamilton, I love serverless, and I’m not trying to be a crank or a killjoy or police people’s language. Have you seen Lambda: A Serverless Musical? Charity is the co-author of Database Reliability Engineering (O'Reilly), and is devoted to creating a world where every engineer is on call and nobody thinks on call sucks. She started Honeycomb to bring engineers the observability tooling they need for the era of distributed systems. Charity ran infrastructure at Parse and was an engineering manager at Facebook. Charity Majors is the co-founder and CTO of Honeycomb.io, a tool to help software engineers understand what happens when their code meets production.