I'm running into this at work lately. Suits are forcing everyone to move from one email sending service to another to save a few $, and I got stuck tracking the progress of everything that needed to be moved.

Entire departments that openly told me all they do for the company is manage software to generate reports that get sent out via email automatically. One of their guys is using python. One is using some SQL server plugin that mixes "no code" shit with straight C#. Another is using an entire suite of outdated software that has its own proprietary email generation logic, and the only part they're using is the email generation. The fucking lead? A god damn vbscript, used to dynamically construct a string that is sent to the command prompt to be executed. That string? Launch an existing PowerShell script that sends an email. I've seen the whole thing, that's all it fucking does front to back. Just fucking use PowerShell straight for the love of all that is holy instead of this awful rube goldberg mess.

In other departments, people whose entire job description is "I admin and support these three systems" being unable to do literally anything in their systems without relying on the vendor's help desk for the software. Shit that I was able to find out in 30 seconds with a search that got me the system documentation, they open a support case and are fucking helpless.

I just want to close the door and get back to working on my stuff, so I can stop taking mental damage from exposure to all the cognitive hazard messes these other supposedly technical teams have shit into existence.

[–] Zink@programming.dev 10 points 2 days ago

people whose entire job description is "I admin and support these three systems" being unable to do literally anything in their systems without relying on the vendor's help desk for the software.

I have run into a lot of engineers who would better be described as purchasers of equipment. And those roles are often very necessary, especially in fields like manufacturing engineering where you might have a single engineer specifying/buying/managing millions of dollars in capital equipment that makes money 24 hours a day if running and loses money 24 hours a day if not running.

And the usefulness or uselessness of those individuals varies, just as it does with all people. But to think of somebody with an admin title being SO helpless is pretty crazy. But maybe it's a win-win for the admin and the software vendor at the expense of the employer, lol.