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.

The first trillion is the hardest I guess.

You are correct, I guess “Permanent Ubuntu Live USB” isn’t really accurate as I tend to distro hop. I picked Purple because I was using Ubuntu at the time, then I came to associate that one with “current linux image” and the others were more situational. This was about the same time I came to realize that for 99% of file transfers it was easier to just scp things across the network rather than dig a USB drive out of the drawer, so pretty soon after I bought them the only thing I used them for was bootable images, and for whatever reason Purple has been the first choice for that task, so I’m pretty sure it has had more writes than the other four put together.

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.

I bought a 5-pack of 8GB USB drives for making live USBs, many years ago it feels like, and have somehow managed to hold onto all of them. I tend to use Green and Black the most for file transfers and they have started to fail pretty regularly but I can’t throw them out, they’re a family. Funnily enough Purple, the one that got assigned “Permanent Ubuntu Live USB” duty and has seen more than its share of writes, is still rock solid.

I loved having a smartwatch, for the brief period of time I had one. They fell to (IMO) the pitfalls of being annoying to charge and being tied to massive smartphone walled gardens. After a few years my smartwatch couldn’t even hold a charge through a single day, and had lost support from the manufacturer anyway, and was hard to keep synced with my phone, and eventually the hassle became too much for it to be worth it.

But if we had a standard API for wearables that smartphone companies adhered to, and I didn’t have to charge it every night, I would love to have another smartwatch. They’re so convenient.