Live data from Hacker News

A programmer automated their data-entry job. Now: tell their employer?

qz.com

1–10 of 20 posts

Re: A programmer automated their data-entry job. Now: tell their employer?

#3

This article is almost entirely direct quotes from a forum thread with little to no commentary or narrative on top of it.

Yeah, it's an aggregation of comments from HN, Reddit and Stack Exchange, and a couple of examples of this happening before. Might be helpful for people who missed it but kinda silly to post it to HN

Re: A programmer automated their data-entry job. Now: tell their employer?

#4
When I automated the documentation of nightly job processes using Tivoli Maestro configuration files and Visio, my employer didn't know what to do with me so they promoted me. It never crossed my mind not to say something. I wasn't there to produce output. I was there to bring value to the organization.

At another employer, I worked alongside a customer service rep who automated much of the time consuming work he had to do. He wasn't a programmer by trade, but having a hacker mindset, he learned to do so after tiring of the same old work. Despite the annoyance of the security team and other developers who felt threatened by his work, he was promoted to IT and they locked down the workstations so it wouldn't happen again.

Re: A programmer automated their data-entry job. Now: tell their employer?

#9
post #4

When I automated the documentation of nightly job processes using Tivoli Maestro configuration files and Visio, my employer didn't know what to do with me so they promoted me. It never crossed my mind not to say something. I wasn't there to produce output. I was there to bring value to the organization. At another employer, I worked alongside a customer service rep who automated much of the time consuming work he had…

> Despite the annoyance of the security team and other developers who felt threatened by his work

Depending on what he did the security team may have rightfully had issues with the work. I've seen it time and time again. Someone automates something, the tool gets released to users and it's full of SQLi, XSS, and RCE vulnerabilities, sometimes opening up a once protected data-set or systems to company or Internet wide exposure. It's shadow IT/Dev work like this which tends to be responsible for the most security incidents.

Post reply on HN