Semi-Hemi-Lemmygod

Found John Oliver’s fediverse account

In my head it’s Dr. Frank-N-Furter

Or if you just want to inform management that more people won’t simply mean the work gets done much faster just give the example of “If takes 9 months for a woman to make a child, it doesn’t mean you can get 9 women and make a child in one month”

Management: “I don’t have time for theoretical discussions. Marketing says this releases in two weeks and you better get it done. Do you need more resources?”

Lemmy upvotes are more rare and therefore more valuable

Bring some iron and don’t eat or drink anything you’re offered

Kerbal Space Program has a similar vibe, and other space sims take themselves way too seriously to be fun.

RIP KSP2

If that game freezes is in paralyzed?

Earth: “Oh you want to pave things? Let me help”

Worf was as good of a father as he could have been to that whiny little shit

“It is… green”

The Discworld fandom is another one you can’t be in if you’re an asshole because you clearly didn’t understand the source material.

“Shuttle’s busted.”

“What happened now?”

“Harry fell in love with a nefarious alien woman.”

“Woo! I guessed right! Pay up!”

shot of betting pool titled “Reason for next shuttle rebuild”

Oracle is a law firm disguised as a tech company

Yep, an actual model of your network that you can tinker with

The guards didn’t mention it when they saw him climbing down the wall because it would be a little con descending

My cat won’t go after bugs but will empty out a nest of baby rabbits and leave them for me to step on in the dark.

I work with customers a lot, and it’s always impressive when I say “Yeah, just do these two things and it’ll fix your issue” and then it does. What they don’t see is the hours and hours I spent breaking shit, resetting the test environment, and breaking it again.

It’s like the apocryphal tale of the engineer who charged for knowing where to tap the hammer.

I would start with getting a good idea of how things actually work, like the TCP stack, DHCP, Wifi, etc. Learning these basics will help a lot in diagnosing issues, because you’ll be able to isolate it to specific parts of the network to look at. Having a good grasp of the basic principles of networking has really helped me a lot in figuring out issues.

A lot of the other stuff - like “how do I configure wifi in the office” - is highly vendor-dependent. The process for, say, setting up a guest network is going to be different depending on what hardware you have. But if you have a good grasp of the basics of networking you’ll be able to figure out what those settings actually do.

Sadly, I learned a lot of this stuff through trial and error and long frustrating attempts at getting wifi and routing and VPNs to actually work, so I don’t have any materials to recommend.

Edit: Another tip is to be able to build models of the systems you’re making so you can test changes. It’s incredibly helpful to have an environment you can break and rebuild quickly to test things. This goes for basically everything sysadmin related.

deleted by creator

The placebo effect is real and can be exploited.