this post was submitted on 12 Jun 2024
11 points (92.3% liked)

Programmer Humor

19154 readers
2012 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS
 
top 24 comments
sorted by: hot top controversial new old
[–] [email protected] 10 points 3 months ago

Dark blue on black is chaotic evil

[–] [email protected] 2 points 3 months ago (1 children)

Lawful evil should be: asks you to make a ticket, closes it immediately and tells you it's not an issue, it's working as designed.

[–] [email protected] 2 points 3 months ago (1 children)

Answer marked as duplicate

[–] [email protected] 1 points 3 months ago

Does not provide number of duplicate ticket

Tim Apple your ears are burning, we're talking about you

[–] [email protected] 1 points 3 months ago (1 children)

Lawful good is asking for trouble. Before they know it, they'll be inundated with e-mails to their personal company address with poorly worded help requests. They'll spend half their time making and updating tickets on the user's behalf that would have been mostly automatic if they'd gone the Lawful Neutral route. They need to insist requests are sent to the main support address. I'm assuming that's tied directly to the ticketing system.

When I was being Lawful slightly-better-than-neutral, I'd create the ticket and then put a paragraph in the reply telling them to please not e-mail me directly in future, because one day I might be unavailable and their e-mail could go unseen for hours or even days.

Repeat offenders would eventually do it at a time when things were busy too, so I'd be concentrating on the tickets and not things to my personal address, so that slight delay often helped it sink in.

[–] [email protected] 1 points 3 months ago

Funny, for me repeat offenders somehow always had a second request I couldn't find until 430pm on a Friday. Strange how it always happened. Oh well, sucks to suck.

[–] [email protected] 1 points 3 months ago (1 children)

Blue on black is pretty evil to me.

[–] [email protected] 1 points 3 months ago

Can we call this out on terminal text editors too? Some just color lines based on their content, and frequently comments end up being blue on black and it's impossible to read.

This comment describes the options for the next parameter in this config file, but I have no idea what it says, so I guess I'm fucked?

[–] [email protected] 1 points 3 months ago (1 children)

Lawful neutral cuz in 6mo when some “controller” punches three buttons to run a report and asks “Hey why’d you do that?” THEN I’ll have documentation. And a job.

Make ticket, receive assistance. Fight me on that and I’ll add you to my email inbox’s ruleset - I am now an LLM, and will gentle-tone you to death via faux misunderstandings

[–] [email protected] 1 points 3 months ago

Yep, hard-line lawful neutral. Though I lean chaotic evil when someone high enough on the food chain starts complaining.

[–] [email protected] 1 points 3 months ago

Also chaotic neutral: prioritizes issues by curiosity.

[–] [email protected] 1 points 3 months ago (1 children)
[–] [email protected] 1 points 3 months ago

Only if we like you.

[–] [email protected] 1 points 3 months ago (1 children)
[–] [email protected] 1 points 3 months ago (1 children)

Going by what OP thinks "Chaotic Evil" means for sysadmins, they have clearly never heard of BOFH.

[–] [email protected] 1 points 3 months ago

BOFH: hooked up the mains to the doorknob and asked a luser to bring their laptop over for personal attention and repair.

[–] [email protected] 0 points 3 months ago

Chaotic good.

Completing a 10 mins ticket for something you end up fixing in seconds. Fucking chore.

[–] [email protected] 0 points 3 months ago* (last edited 3 months ago) (1 children)

Chaotic evil is "creates ticket, but intentionally words the problem poorly before logging off, leaving the junior help desk worker to fend for himself and giving you the solution to a different problem that isn't relevant in your case"

[–] [email protected] 0 points 3 months ago* (last edited 3 months ago) (1 children)

Really, there's a vast number of ways for IT support to be evil or chaotic. I wonder if there was ever a viral fiction series in the early internet about it...

[–] [email protected] 0 points 3 months ago (1 children)

that would make someone a real bastard....

[–] [email protected] 1 points 3 months ago

Sounds like somebody straight from hell

[–] [email protected] 0 points 3 months ago (1 children)

I'm pretty sure I've done most of these at some point or another.

It really depends whether I like you or not.

Liking my users is entirely dependent on how much work you make me do, and how difficult that work becomes because of your personality.

I've gotten tickets that were literally "$thing is broken", or "help! Call me!" With no information given, not even a callback number. I've also gotten a rambling voicemail, in which a user describes an issue with a piece of software and doesn't identify themselves, not provide any callback information. The CID on the voicemail wasn't available either, and since I work with several companies doing support, I couldn't even identify the client, nevermind the specific user.

There's also the needy users that create tickets for every prompt, dialog, message, delay.... Pretty much anything that could happen at all ever, whether it affects their ability to do their work or not.

There's also the unavailable users, they are not available ever, at any time, for any reason. I have literally gotten critical tickets which require me to access the users workstation to fix, while it is logged in as the user, and I could call less than 5 minutes after they create the ticket, and they're busy. Email them and they have an out of the office message, or reply with something about them being in a meeting (with no information about when they will be free), or simply don't reply at all. After a few weeks of trying to contact them to connect and resolve their very simple (but "critical") issue and getting nowhere, close the ticket, only to be met with a flurry of emails from them about how the problem isn't solved. Immediately call or reply and you get voicemail and silence.

Most of my users do fine, and it's usually a minority that are troublemakers, and I want to make that clear.... But the troublemakers are the driving force for me to find ways to fix pretty much every problem without ever opening their system though remote control. I can do all kinds of things from registry edits and hacks, to writing and scheduling PowerShell scripts to fix their shit every time they log in, and deploy that by a remote PowerShell command prompt, and nothing more.

Yeah William, you might be the c-whatever bullshit, but if the issue is sooo fucking critical, make five goddamned minutes for me to fix your shit or it's not getting fixed. I don't care if you own the goddamned planet, I can't fix your shit without access.

[–] [email protected] 1 points 3 months ago (1 children)

There's also the needy users that create tickets for every prompt, dialog, message, delay.... Pretty much anything that could happen at all ever, whether it affects their ability to do their work or not.''

This could be weaponized incompetence. "Oh I keep having issues with my computer that interfere with my work, so I can't work and IT is incompetent and can't help me, look at all these tickets and how long IT takes. I just can't get any work done!"

[–] [email protected] 1 points 3 months ago

Oh yeah, I've seen that. People hit the most minor roadblock and just stop working until someone else fixes their shit.

It's an attitude of "we've tried nothing and we're out of ideas!"

I don't like those people either.