• palordrolap@kbin.run
    link
    fedilink
    arrow-up
    43
    arrow-down
    1
    ·
    edit-2
    5 months ago

    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.

    • Ookami38@sh.itjust.works
      link
      fedilink
      arrow-up
      17
      ·
      5 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.

  • Venator@lemmy.nz
    link
    fedilink
    arrow-up
    39
    ·
    5 months ago

    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.

  • Milk_Sheikh@lemm.ee
    link
    fedilink
    arrow-up
    34
    ·
    5 months ago

    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

    • waigl@lemmy.world
      link
      fedilink
      English
      arrow-up
      13
      ·
      5 months ago

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

    • MystikIncarnate@lemmy.ca
      link
      fedilink
      English
      arrow-up
      3
      ·
      5 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?

  • SatouKazuma@programming.dev
    link
    fedilink
    arrow-up
    11
    ·
    edit-2
    5 months ago

    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”

  • electric_nan@lemmy.ml
    link
    fedilink
    arrow-up
    10
    ·
    5 months ago

    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.

    • BassTurd@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      5 months ago

      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.

  • alekwithak@lemmy.world
    link
    fedilink
    arrow-up
    8
    ·
    5 months ago

    I’m chaotic good in my heart but lawful good because one needs a record of their work come review season.

  • variants@possumpat.io
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    2
    ·
    5 months ago

    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

    • IrateAnteater@sh.itjust.works
      link
      fedilink
      arrow-up
      7
      arrow-down
      1
      ·
      5 months ago

      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.

      • mosiacmango@lemm.ee
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        5 months ago

        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.

        • IrateAnteater@sh.itjust.works
          link
          fedilink
          arrow-up
          4
          ·
          5 months ago

          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.

        • SatouKazuma@programming.dev
          link
          fedilink
          arrow-up
          3
          ·
          5 months ago

          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.

        • FuglyDuck@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          5 months ago

          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.

    • BowtiesAreCool@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      5 months ago

      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

  • Bappity@lemmy.world
    link
    fedilink
    English
    arrow-up
    7
    ·
    5 months ago

    I’m guilty of pushing massive commits with several different changes and just commenting “bump version”

    • virku@lemmy.world
      link
      fedilink
      arrow-up
      9
      ·
      edit-2
      5 months ago

      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)