Accidentally hitting reply-to-all on a company wide email and more or less stating that I wanted to be transferred to another team.

There was a new team forming elsewhere, and in fairness, it was a great opportunity in a lot of ways. But... I didn't get the transfer until another batch of jobs opened a few months later.

That... was a long few months.

I'd get in the car and start driving. I'd go and have the conversation I've been afraid to have for years

... or I'd be paralyzed with fear like I've been for the rest of my life.

... or if I'm being honest, I'd most likely grab a bottle of tequila, fall off the wagon, and find out what I actually want to do that way.

I go with New personally, though I don't subscribe to all that much - I imagine that it would be a bit less pleasant if you're on a hundred different communities.

Had something along these lines - a mail server that ended up used almost exclusively for sending automated internal emails. We'd migrated to a third party for email sending because managing DNS etc for clients got pretty painful. Mail server got removed by the tech lead and repointed to our third party mail provider without telling anyone, and 3 days into the months we'd hit our billing limit, on the lead's day off. Turns out that one service had been sending an order of magnitude more email than all of our other services put together, as someone had been using email as a logging method.

That was a... fun day.

Glad someone made this point. My next printer will definitely be a tank printer. It's basically flipping the business proposal back to "pay for the printer up front" instead of "pay for the printer whenever you buy ink". My current printer was cheap enough that I basically spend enough on ink to buy a new printer every few years, given degradation of cartridges when they're left after opening.

I really want the Vim/VS Code one - as someone who professionally devs in an MS stack, but would choose Vim as a primary text editor otherwise... it speaks to me deeply.

Haha, yeah, I totally have proper backups...

Up until now I've been using docker and mostly manually configuring by dumping docker compose files in /opt/whatever and calling it a day. Portainer is running, but I mainly use it for monitoring and occasionally admin tasks. Yesterday though, I spun up machine number 3 and I'm strongly considering setting up something better for provisioning/config. After it's all set up right, it's never been a big problem, but there are a couple of bits of initial with that are a bit of a pain (mostly hooking up wireguard, which I use as a tunnel for remote admin and off-site reverse proxying.

Salt is probably the strongest contender for me, though that's just because I've got a bit of experience with it.

The language in the article does seem to forget that plenty of early smartphones had replaceable batteries... Yeah, it might add some bulk, but it's not exactly going to be a major hardship.

... but it seems like a good reverse step to me. Any consumer replaceable part is a good thing as far as I'm concerned.

I'll get QA to update the test plan