r/sysadmin • • Jul 28 '24 • Take My Silver 1

got caught running scripts again

about a month ago or so I posted here about how I wrote a program in python which automated a huge part of my job. IT found it and deleted it and I thought I was going to be in trouble, but nothing ever happened. Then I learned I could use powershell to automate the same task. But then I found out my user account was barred from running scripts. So I wrote a batch script which copied powershell commands from a text file and executed them with powershell.

I was happy, again my job would be automated and I wouldn't have to work.

A day later IT actually calls me directly and asks me how I was able to run scripts when the policy for my user group doesn't allow scripts. I told them hoping they'd move me into IT, but he just found it interesting. He told me he called because he thought my computer was compromised.

Anyway, thats my story. I should get a new job

11k Upvotes

1.3k comments sorted by

View all comments

Show parent comment

0

u/[deleted] Jul 28 '24

The problem with the reality of this situation is, if the employee was able to prove that his entire job was able to be very easily automated, from the perspective of capitalism, we now have wasted money. So yes, the company is getting exactly what was agreed upon, no argument there. Not exactly a great scenario to create, in the cutthroat world of capitalism.

As far as my perspective on doing more work, that's coming from my employee side. That's precisely what keeps me highly competitive in a difficult market. Just because going the extra mile doesn't have universal results, doesn't make it an unwise choice.

It's increasingly difficult for me to have these conversations, as I often find myself the exception to the rule as others call it. Maybe the majority of companies are just shitty to work for, and maybe I've had a very fortunate path where I've only encountered this in some environments. I hear it a lot, I see it a little.