Maybe we can save the theatrical vs. streaming, 'must see it in a cinema' spiel for when we're safely on the other end of a deadly pandemic.

— Alex Winter (@Winter) September 4, 2021

I’m already safely on the other end of a pandemic and so are all the other people who have been vaccinated.

Oh, we doing that thing again where we pretend the vaccines don’t work? OK then.

DevOps was originally intended to break down the silos between developers and system administrators (and related fields).

What DevOps became — what MBAs changed it into — was that developers should become expert system administrators and that system administrators should become professional software developers. Yet I’ve never met a developer who was even a good (much less great) system administrator and relatedly, I’ve never met a system administrator who was a good software developer.

I know it shouldn’t need to be said, but it does alas need to be shouted at MBA types: everyone being an expert at everything isn’t a real thing. It just cannot happen. What has occurred in reality is that we have developers being terrible and dangerous system administrators and system administrators being atrocious developers.

Many years ago, a friend of a friend of mine threatened to kill me because I called him a “mindless Randbot” to his face.

I asked him, “Why not try now?” God I was a prick. But a funny and bold prick. North Florida upbringing does give you that at least.

The first ten on today’s playlist:

Operations is not Developer IT.

Oh fuck yes I identify with this so much. I spend so much time debugging developer problems that I should never even see, should never even be brought to my attention.

Yet as the years go on the number of developers who approach me and say “this worked on my laptop, it doesn’t work in the test environment, why” has steadily increased. Often they have not even bothered to do basic troubleshooting, things like read the documentation on what the error message is attempting to tell you. Sometimes I don’t even get an error message in these reports, just a development saying “this page doesn’t load for me now but it did before”. The number of times I have sent a full-time Node developer a link to the Node.js docs is too high.

I’ve done this, and solved all sorts of bugs in applications and deployment/development tools I don’t use, know little to nothing about, and should have no reason to ever look at.

Despite the bullshit about how this was going to empower us to do “our best work faster”, the results have been clear. Operations is drowning, forced to learn both all the fundamentals their peers had to learn (Linux, networking, scripting languages, logging and monitoring) along with one or more cloud providers (how do network interfaces attach to EC2 instances, what are the specific rules for how to invalidate caches on Cloudfront, walk me through IAM Profiles). On top of all of that, they need to understand the abstraction on top of this abstraction, the nuance of how K8 and AWS interact, how storage works with EBS, what are you monitoring and what is it doing. They also need to learn more code than before, now often expected to write relatively complicated internal applications which manage these processes.

The knowledge and skills required to do the same job I did 10 years ago have increased by about 10x-15x — that is, you have to know about 10-15 times as many technologies and master that many more skills to do the same work we did then. It’s insane. I’m near my cognitive limits now and I’m very smart. I’ve seen people leave my field because they simply could not handle the greatly-increased complexity any longer. I’d say my field used to require maybe a minimum 110 IQ and now it requires probably 130 to even play. To be actually good, it’s higher.

This is largely MBA-driven, by the way. It’s (mostly) not the fault of developers, though many devs tend to be cocky jerks who never think anything is their responsibility. That said, MBAs are the ones who have collapsed teams, reduced headcount, thrown out QA while attempting to push developers to release features faster and then made operations people (me) be developer IT and generalized QA for things developers don’t want to understand or think about.

What Australia and New Zealand should have done given foresight:

Buy time to prepare more resiliency (e.g., more ICU capacity, vaccines, masks) for the inevitable breach

Instead of this crazy "zero COVID" policy

— Trishank Karthik Kuppusamy (@trishankkarthik) September 3, 2021

I agree, but it didn’t take any foresight to know that, to do those things. It just required not being a full-on dumbass. That’s it; that’s all.

Australia and New Zealand decided that idiotic Zero Covid Forever was the way to go and the only possible plan, and now they’ll pay for it for a long, long, long time. I don’t want their people to suffer, but they brought it on themselves. Now it’s — as I like to say — the consequences phase.