Boomer Humor Doomergod

Everyone is a senior engineer with an idiot intern now.

Describing what they want in plain, human language is impossible for stakeholders.

Yep, you’ve got it right.

As for me, I have a pretty beefy main server so I went with a multi-drive enclosure and set up a ZFS pool with the enclosure in JBOD mode.

I had been using the built-in RAID feature but it broke and even with formatted drives and a new enclosure it wouldn’t work, so I offloaded the RAID stuff to the server with ZFS.

It’s also how we accidentally shut them down before saving our work

Reminds me of Woz’s old saying “Never trust a computer you can’t throw out a window.”

Just needed a little bit of patience and a whole lotta Google Translate

Thanks now I’m having flashbacks

If you think German C is bad imagine Czech PHP.

Had to refactor an entire custom Magento plugin written in it.

As someone who sits in on those calls as a sales engineer, I wish I could interrupt the weird kabuki dance of all this and say “These guys are clearly not a fit and we are all wasting time.”

But I have bills and honestly I’m probably commenting here because I checked out as soon as the screenshare started and I could turn my camera off without anyone noticing.

Please don’t ask me anything because I’ll just say you broke up and I need you to repeat the question so I can bullshit an answer.

If something goes down my kids will be a more immediate and annoying alerting tool than anything I’ve used professionally.

A CIA-endorsed tactic for fighting fascism is calling a lot of pointless meetings.

Struggle requires sacrifice.

Usually it’s to help a customer create a proof of concept going so we can make a sale so it’s not entirely a selfless act.

Plus it keeps me from sitting on hours-long calls trying to walk them through ambiguous instructions.

I structure my tutorial docs (I write a lot of them for work) like the O’Reilly cookbook series for this reason.

The problem you’re trying to solve is at the top. Next comes a list of prerequisites for the instructions. Then clear, step-by-step instructions with no more than one command or action for each one, highlighting anything that’s different depending on environment.

Then at the bottom I’ll sometimes add a discussion of why each command does what it does, and finally a list of resources for whatever programs or systems the instructions are about.

You can customize and debug pretty easily, I’ve found. You can create your own Dockerfile based on one you’re using and add customizations there, and exec will get you into the container.

Learning this fact is what got me to finally dockerize my setup

I was thinking more like the legendary Bill Atkinson

Ultimate dev: Removes 2,000 lines of code, works an order of magnitude faster.

I’ve worked in enterprise software the better part of a decade and if there were security concerns about container escapes they wouldn’t be so widely used.

And the best part is the Ruby way accounts for leap years.

Yeah, but for one-off scripts that solve small problems it’s way better.

Add HTTParty for API calls and that’s like 90% of what I use Ruby for.