Dark blue on black is chaotic evil
deleted by creator
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.
Answer marked as duplicate
Does not provide number of duplicate ticket
Tim Apple your ears are burning, we’re talking about you
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.
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.
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
Yep, hard-line lawful neutral. Though I lean chaotic evil when someone high enough on the food chain starts complaining.
Only if we like you.
Chaotic good.
Completing a 10 mins ticket for something you end up fixing in seconds. Fucking chore.
I fucking hate this.
Most days I spend more time accounting for my work than I do actually working.
Sometimes I’m neutral good and other times chaotic good. I’m at a relatively small company though, so I’d probably be different at a megacorp.
I went from the sole IT person at a small/medium business for 9+ years to a new role at a big company with divisions and shit. In my previous position, depending on the day, I fell in every category, but usually chaotic good on good days. Now I’m pretty much neutral to lawful good. I’ll dabble in the neutral evil as I see fit, because PEBCAK and ID10t issues have no bounds.
I’ve been a chaotic neutral more times than I would like to admit.
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”
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…
that would make someone a real bastard…
Sounds like somebody straight from hell
But none of these are real, in the real world IT won’t touch your issue unless you create a ticket, then when you do they just never do anything about it anyway
I encountered “lawful evil” once. My answer of “I know what the problem is. I know how to fix it. But because you have no clue about what this company actually does to make money, you took away my ability to do it. So now I’m here, wasting both our time” didn’t seem to go over very well.
Ehh. Depending on the industry and issue, thats wholley justified, not only from a “least privilege” sense, but from a regulatory one.
Step over into cybersecurity and you end up spending all day clamping down on usability because the company has legal requirements to meet to continue to exist. Many of the things we are compelled to do are overeager and overly pedantic, but it’s either “do it, pay up, or shut down.” The execs tend to prefer “do it” in my experience, which makes everyone’s day a bit more tiresome.
So its entirely possible that was out of their hands.
In this case, none of that applies. I do industrial programming. 99% of the ethernet networks I have to connect to don’t have a router, and nothing is running DHCP. They locked out my ability to manually change my IP address.
That shit is why I bailed on the cybersecurity industry completely, with no thought of ever returning. I’m an engineer (software aside, I also have an aero engineering background). I wanna build cool shit!
Not to mention, how frequently the “I can fix it on my own” guy ends up making things worse.
Like my coworker who insisted he knew how to install a monitor and then couldn’t figure out why the display port wouldn’t work with a usb-a adapter. It had a normal DisplayPort plug and didn’t have a thunderbolt adapter (it’s a desktop.)
Rather than update the ticket that got him the monitor, he created a new ticket.
I can’t complain too much. IT guy likes me so he took the extra monitor and gave me a third one.
In my experience I create a ticket, then after 3 days of not hearing anything they manually close it as resolved while having done nothing
I’m guilty of pushing massive commits with several different changes and just commenting “bump version”
Worked the first six years of my career using no version history tracking or backups at all on one of our main systems. Nobody knew we didn’t have backups and I didn’t know how to use git and figured it wasn’t so important since I was maintaining it alone anyway.
(I don’t do any of those things anymore)
All hail “squash and merge”
I’m chaotic good in my heart but lawful good because one needs a record of their work come review season.
Working the neutral way currently. There’re so many tickets, all of them more important than the other, I can just as well take from the stack.
Oh you actually use the stack? I’m surprised you don’t just put all the tickets in a heap. I can give you some pointers on how to do that if you’d like.
Sure let me know in a ticket, I’ll get to it eventually!
Files ticket, and references ticket in email to supervisor for visibility
I find that when a user continually makes a stink to get their ticket dealt with first, I gently try to correct them, and when that inevitably doesn’t sink in, and they call during a critical issue, I tell them quite firmly that things are down and nobody at x site can work, so your printer will have to wait. Log a ticket and I’ll address it when I’m done Brenda.
… They usually back off when you make it clear to them that they’re not the most important thing you’re dealing with at any given moment.
Chaotic neutral: If you complain a lot and keep saying your ticket has high priority, you’ll automatically have lower priority than the guy that doesn’t really care when I do something
I never I realized I was so evil, nor so neutral.
