Slashdot Mirror
The Coders Programming Themselves Out of a Job (theatlantic.com)
Brian Merchant, writing for The Atlantic (condensed for space): In 2016, an anonymous confession appeared on Reddit: "From around six years ago up until now, I have done nothing at work." As far as office confessions go, that might seem pretty tepid. But this coder, posting as FiletOFish1066, said he worked for a well-known tech company, and he really meant nothing. He wrote that within eight months of arriving on the quality assurance job, he had fully automated his entire workload. When his bosses realized that he'd worked less in half a decade than most Silicon Valley programmers do in a week, they fired him. [...]
About a year later, someone calling himself or herself Etherable posted a query to Workplace on Stack Exchange, one of the web's most important forums for programmers: "Is it unethical for me to not tell my employer I've automated my job?" The conflicted coder described accepting a programming gig that had turned out to be "glorified data entry" -- and, six months ago, writing scripts that put the entire job on autopilot. After that, "what used to take the last guy like a month, now takes maybe 10 minutes." The job was full-time, with benefits, and allowed Etherable to work from home. The program produced near-perfect results; for all management knew, their employee simply did flawless work.
The post proved unusually divisive, and comments flooded in. Reactions split between those who felt Etherable was cheating, or at least deceiving, the employer, and those who thought the coder had simply found a clever way to perform the job at hand. [...] Call it self-automation, or auto-automation. At a moment when the specter of mass automation haunts workers, rogue programmers demonstrate how the threat can become a godsend when taken into coders' hands, with or without their employers' knowledge. Since both FiletOFish1066 and Etherable posted anonymously and promptly disappeared, neither were able to be reached for comment. But their stories show that workplace automation can come in many forms and be led by people other than executives.
About a year later, someone calling himself or herself Etherable posted a query to Workplace on Stack Exchange, one of the web's most important forums for programmers: "Is it unethical for me to not tell my employer I've automated my job?" The conflicted coder described accepting a programming gig that had turned out to be "glorified data entry" -- and, six months ago, writing scripts that put the entire job on autopilot. After that, "what used to take the last guy like a month, now takes maybe 10 minutes." The job was full-time, with benefits, and allowed Etherable to work from home. The program produced near-perfect results; for all management knew, their employee simply did flawless work.
The post proved unusually divisive, and comments flooded in. Reactions split between those who felt Etherable was cheating, or at least deceiving, the employer, and those who thought the coder had simply found a clever way to perform the job at hand. [...] Call it self-automation, or auto-automation. At a moment when the specter of mass automation haunts workers, rogue programmers demonstrate how the threat can become a godsend when taken into coders' hands, with or without their employers' knowledge. Since both FiletOFish1066 and Etherable posted anonymously and promptly disappeared, neither were able to be reached for comment. But their stories show that workplace automation can come in many forms and be led by people other than executives.
When I was fresh out of high school and in college, I had a data entry job in a silicon valley high tech company. Each day I received Excel reports from multiple sources ranging from dozens to a hundred attachments. My job was to organize them and enter into a database. Now I wasn't a programmer at all. In fact I only learned Visual Basic macro on my own and instead of formatting those reports into the format I want and merging before data entry, I used the VB macro to record my actions which turned directly into code. I fixed that code up a little bit so that it could read the entire directory (where I dropped the attachments) and processed an entire day of work in under a minute. Sure enough, I lost my job only a week after that because someone found out that I automated the job. Now if I was to set the macro to run one record every 10secs, I would have been able to keep my job for a while LOL.
I'm doing the same with my job. The nice thing is that I'm part of a fairly large organization with a lot of need, and as I free up my time, I'm in a position to help address other areas.
But yeah, I do less work now than I did two years ago. Gone are the days where this position manually does a lot of things. Some massive data QA that used to take weeks now runs in about a half day. That's generally a prelim run, some fixes, and a few more runs to make sure everything is good to go. If nothing was wrong, it would be under an hour.
If companies aren't pushing their technologically minded folks to automate things, they're throwing money away. Automate to free up time, use that free time to document the automation, rinse, repeat. The only downside is that this position is now going to require someone with more technical skill than it has historically had, and that costs a bit more money. The upside is that the quality of work being done is far higher, and the downstream effects are much more efficient, accurate, and productive processes and workers.
I've worked with people handling data and managing processes upstream and downstream of me to create a much more robust and unified system. I'm now working with them to do the same on the other side, and that's starting to create a web of pretty high quality work throughout the organization. Not what I was really hired to do, but management loves it. There are definitely some sticks in the mud who can't adapt to change, so for the moment, we're working around them. You insist on manually editing spreadsheets and leaving errors in them for someone else to correct? We'll write a script to identify the most common ones, and to create summaries which are likely to highlight the issues. That next person's job just got 90% automated.
I doubt I'll ever get to 100% not working, but I might hit 35% of my time monitoring and tweaking automation by the time I'm done.
Velociraptor = Distiraptor / Timeraptor
The thing is after you automate the task, you are no longer the one producing the results. The computer is.
Companies don't pay you for results, they pay you because your effort is worth more to them then what they are paying you for.
The guy automated a task, he got paid for his work to automate that task. But being he wasn't doing anything after that, his contributions had ended.
I have my code and my effort in place all around the world, helping other make a lot more money then Ill ever make. But they paid me for my effort, and I moved on.
I am not the one generating millions of dollars, it is the computer running the code that took me a few minutes-few months to create, is actually doing the work. I got paid for my work.
No for me to survive. I work on other projects. Because my net worth should be less then the total of my contribution.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
If you've automated one job, simply ask for another. If your employer won't go along with that, go work for someone else with a more intelligent approach.
Are you confusing paid employment with a hobby?
It sounds like you have this weird notion that work should be "fun" and that the more of it you do, the more fun you have. And that doing work is in itself sufficient motivation for doing more.
If I could free up my day by fulfilling my duties (more or less, I can't send a script to a meeting) then that permits me to engage in other, possibly more fulfilling things. Maybe even ones that my employer benefits from. But provided they are satisfied with the work-product they are paying me for, it is of little concern to them how it is produced.
While I have heard about people sub-contracting their tedious, repetitive, jobs to low-paid countries, that sort of activity contravenes most employers confidentiality conditions.
A further, more relevant question would be whether it is moral to automate someone else's job? If I was able to automate my work, then there is a good chance that the same automation could be applied to others in my team. Do I owe it to them to NOT do this. Should I be loyal to my colleagues or to my company?
politicians are like babies' nappies: they should both be changed regularly and for the same reasons
more than once.
These were people taking 60+ hours to do the same work I was doing in less than 20 hours a week. Automation of some of my work made it worse.
Management just tossed more work on my plate, and got rid of the slow people, with no financial inducement for me. I never said anything, and found plenty of time to surf /. and reddit while things ran batch jobs on another screen, or computer(s)
If you're serious about automating your job, make sure your apps do a directory check to make sure you're still employed before it does it's job.... /s?
I've ended up being that one guy that gets job offers because somebody I've encountered just wants me at the company because of this. Some of my employers have sat me at a desk for years knowing I had nothing to do because I solved all their problems in 6 months. They keep me around because I occasionally fix something else, or something breaks and I can fix it faster than anyone else, or they want to do something new and they stick it in front of me and ask how to engineer a better solution.
It makes for a good story, but I really don't like being the guy who has the answer to everything. The business keeps me around because I'm tangentially-useful and they occasionally get 10x my salary out of something I do. This often results in me being the only person with responsibility over a certain type or set of systems, so there's no back-up--I've protested this and they simply decide it's too expensive to hire two of me.
I've at times been the guy who wanders the building talking to people, then sits down and makes their work go away.
Support my political activism on Patreon.
... when I first hired on at a law firm.
My first day, I was on the job at 7:30 am and learned that the incumbent, who would be schooling me, would not show up until 10:00 am.
So, I looked around his office and spied an old abandoned notebook that had the line: "backup password is steelers."
I logged in (Novell 3.1) and inquired about the user "backup." It had god privilege.
I made myself an admin and started touring and documenting stuff, finding shit like a backdoor into the system via a dialup modem that the firm new nothing about.
When my mentor showed up, he said, "Well, the first thing is to make you admin."
I said, "No need. I already did that and, BTW, you're no longer admin on my site."
We worked until 11:00 pm each and every night. goddam
A week later he was gone and I ordered a dry erase and listed all the fucking reasons I was working until 11:00 pm.
I tackled each line item and cleaned up the mess, automating as much as I could (I threw the modem in the trash).
A month later, management said they noticed that I didn't work overtime anymore. I told them, that's true, and you don't pay me to so so.
By 3 months I had fully automated mundane tasks and sat in the rocking chair except for when new tech came along.
In my opinion, keeping things out of the ditches is a valuable talent.
No guilt here.
It little behooves the best of us to comment on the rest of us.
I worked a job for 11 years. The entire time my team and I are were automating everything we could. We were very good at it and our manager(s) encouraged us. Why? So we could automate something else and move to something else, etc. The value in the employee is the constant improvement, and it appears my team was lucky to have management which saw the value.
If you get rid of someone who automates their job, who will maintain it? Improve it? Update it? Very short sighted on the management to just fire them. In 6 months when a password changes, some data being used in the process moves, or a person who doesn't think this is automated job is doing anything and deletes it, what will you do then? Make someone else try and reverse engineer it and figure it out, if they didn't get rid of all the workers who could do this.
... about the mechanic, who upon request, produces an itemized receipt applies here.
-Tapping with hammer - $1
-Knowing where to tap - $399
OK, so you automated your own tasks, and they want to fire you as a result.
But wait a minute. With you gone, who understands the automation? Who can fix it when it breaks? Who can update it to handle new types of input, or when the environment changes around it?
Maybe it still makes sense to let you go, and hire a contractor now and then to adjust the automation. But maybe not.
Well, it's smart of him to automate his job, but stupid of hit to rest on his laurels. I am manager I used to have said something along the lines of: "if you want a promotion, make your existing job seem effortless." He was in legal, but the point remains.
If I hired a guy who automated himself out of his job, great! Let's pay you more, and put you somewhere that costs us a bunch since we don't do it efficiently.
Now, maybe they fired him out of ethical concerns for pretending to work. That could be grounds for dismissal in my book, but I'd have to weigh the workplace politics he was facing vs. the benefit of having a good coder automate more of my business.