tool @ tool @r.rosettast0ned.com

▪█─────█▪

---

Read more

Posts

0

Comments

78

Joined

2 yr. ago

Unless you're really deep into a particular provider's unique-esque products (Lambda, Azure AD, Fargate, etc), this is exactly why things like Terraform exist.

Places like that never learn their lesson until The Event™ happens. At my last place, The Event™ was a derecho that knocked out power for a few days, and then when it came back on, the SAN was all kinds of fucked. On top of that, we didn't have backups for everything because they didn't want to pay for more storage. They were losing like $100K+ every hour they were down.

The speed at which they approved all-new hardware inside a colocation facility after The Event™ was absolutely hilarious, I'd never seen anything approved that quickly.

Trust me, they're going to keep putting it off until you have your own version of The Event™, and they'll deny that they ever disregarded the risk of it happening in the first place, even though you have years' worth of emails saying "If we don't do X, Y will occur." And when when Y occurs, they'll scream "Oh my God, Y has occurred, no one could have ever foreseen this!"

It'll happen. Wait and watch.

You're literally describing the system that controlled employee keyscan badges a couple of jobs ago...

That thing was fun to try and tie into the user disable/termination script that I wrote. I ended up having to just manipulate its DB tables manually in the script instead of going through an API that the software exposed, because it didn't do that. Figuring out their fucked-up DB schema was an adventure on its own too.

I don't even let things communicate on /30 networks via HTTP/cleartext...this whole thing is horrifying.

"No, I can't come out tonight, I'm optimizing my CONFIG.SYS file so I can have a mouse AND my Soundblaster work at the same time!"

The fact that a majority of even the older Gen Z (like me) have been reported to not understand file systems or general tech and internet knowledge is scary.

I think it's to be expected. When the majority of your tech use is with a phone/tablet, concepts like filesystems are abstracted away from you.

The same goes for troubleshooting that tech, as the most helpful error message you generally get from those kinds of devices boils down to a graphic of a sad face and a completely useless "Something went wrong" type of error message.

"I don't need to comment this code at all, it's pretty self-explanatory, I'll remember this 100% no problem."

Scene cut:

Me six months later, staring blankly at the code like the monkeys & The Monolith in 2001: A Space Odyssey, desperately trying to unravel the workings of my ADHD brain and just exactly why the seemingly innocent and innocuous-looking function named "dontFuckingTouchThis" is the lynchpin preventing the whole goddamned thing from falling over and going tits-up.

I still use reddit for researching problems at work, but that's it.

Man I loved Encarta. I would spend hours in that shit just going through random stuff.

Yeah, you could do it in AWS with ECS or Fargate.

That sounds like emacs-user talk. We don't take kindly to you folks around these parts...

Deleting an entire line by hitting x repeatedly

The first time I ever touched Double Ds was in vim.

docker (while you don't need it to host things, it makes your life 10x easier)

...until you have a single extra space character hiding 20 lines into your compose file and the whole thing falls over the next time you try to bring the containers up.

Lint your code and configs every time!

You're a good man, Charlie Brown.

I think that'll always be the case with the Fediverse.

Look in to Rocky Linux. It was started by the original developer of CentOS the day Red Hat announced that CentOS would be moving upstream of RHEL. They've already put out an announcement saying that it's essentially going to be business as usual for them.

Fedora isn't the testing distribution for RHEL, CentOS is. Fedora is upstream of CentOS and could be viewed as the bleeding edge in that regard. CentOS used to be downstream of RHEL, but that changed a few years ago when IBM did its first shitty thing at Red Hat. The tree is like:

Fedora (Top of code stream, "unstable" from a business perspective)

|

|

v

CentOS (midstream, much less frequent feature updates)

|

|

v

RHEL (end of stream, stable/predictable/reliable/etc)

And I couldn't disagree more about RHEL adding little value. You're not going to run a server on Fedora for something you want/need to rely on, and especially rely on not to change much/cause breaking changes. That's what RHEL is for and it is the gold standard in that regard.

And that's not even mentioning the fact that Red Hat support is some of the absolute best in the world. Motherfuckers will write a bespoke kernel module for you if that's what it takes to fix your issue. Not sure if that's still true after the IBM takeover though, but that was my experience with them before that.

Why can't it be both?

The existence of Javascript and Groovy is strong evidence that God has abandoned his creation.