queerlilhayseed

A poor architect blames their tools. Serverless is an option among many, and it’s good for occasional atomic workloads. And, like many hot new things, it’s built with huge customers in mind and sold to everyone else who wants to be the next huge customer. It’s the architect’s job to determine whether functions are fit for their purposes. Also,

Here’s the fundamental problem with serverless: it forces you into a request-response model that most real applications outgrew years ago.

IDK what they consider a “real” application but plenty of software still operates this way and it works just fine. If you need a lot of background work, or low latency responses, or scheduled tasks or whatever then use something else that suits your needs, it doesn’t all have to be functions all the time.

And if you have a higher-up that got stars in their eyes and mandated a switch to serverless, you have my pity. But if you run a dairy and you switch from cows to horses, don’t blame the horses when you can’t get milk.

I have big plans for those repos and I am definitely going to get around to it 🥹

The first trillion is the hardest I guess.

Alternatively: vampires who still don’t know how to use any slang that evolved after their own youth.

“I’m carrying this team like the beast with two backs”

“Never look a Trojan horse in the mouth”

“She was so mad her face launched a thousand ships”

“If circuses had bread, then the clowns wouldn’t eat lost children”

It’s an old joke from back when IBM was the dominant player in IT infrastructure. The idea was that IBM was such a known quantity that even non-technical executives knew what it was and knew that other companies also used IBM equipment. If you decide to buy from a lesser known vendor and something breaks, you might be blamed for going off the beaten track and fired (regardless of where the fault actually lay), whereas if you bought IBM gear and it broke, it was simply considered the cost of doing business, so buying IBM became a CYA tactic for sysadmins even if it went against their better technical judgement. AWS is the modern IBM.

cross-region failovers are a thing, but they’re expensive to maintain so not everyone does it. I am kinda surprised one region failure had this much impact though

No one ever got fired for buying IBM.

One of the things that really excites me about the internet is its impact on the development of language. We’re still at the very beginning of its impact, considering the timescale on which language has traditionally evolved, but I suspect that in time the advent of the internet will be considered a major inflection point in the history of language, maybe the single greatest inflection point in the history of language itself. All of a sudden, billions of people who otherwise would never have had the means to converse directly, are now able to converse directly with billions of other people all over the globe, in near real-time. I can’t really imagine how that doesn’t have a seismic impact on how human language evolves. I would love to jump forward in time a few centuries just to see how the things that are happening right now shake out in the long term.