Nobody asks me anymore because I insist on educating them on how to fix their issues. It paid off after a while.
They either fix their own stuff or ask somebody else lol
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.
This made me smile because it reminded me of building my late best friend’s PC. I had a lot of fun doing it, but I insisted on making him do parts of it so that he would understand the basics of what was going on
Nobody asks me anymore because I insist on educating them on how to fix their issues. It paid off after a while. They either fix their own stuff or ask somebody else lol
Most importantly: Never ask them how they did solve their problems!
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.
This made me smile because it reminded me of building my late best friend’s PC. I had a lot of fun doing it, but I insisted on making him do parts of it so that he would understand the basics of what was going on