Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 18 submissions in the queue.
posted by martyb on Wednesday October 03 2018, @12:06AM   Printer-friendly
from the auto-programmatic-asphyxiation dept.

The Coders Programming Themselves Out of a Job

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. "I am not joking. For 40 hours each week, I go to work, play League of Legends in my office, browse Reddit, and do whatever I feel like. In the past six years, I have maybe done 50 hours of real work." 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. The tale quickly went viral in tech corners of the web, ultimately prompting its protagonist to delete not just the post, but his entire account.

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. (It's now been viewed nearly half a million times.) 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. Etherable never responded to the ensuing discussion. Perhaps spooked by the attention—media outlets around the world picked up the story—the user vanished, leaving that sole contribution to an increasingly crucial conversation about who gets to automate work, and on what terms.

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.

Career suicide: The most important job for programmers.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 3, Insightful) by goodie on Wednesday October 03 2018, @01:11AM (1 child)

    by goodie (1877) on Wednesday October 03 2018, @01:11AM (#743173) Journal

    If the job involves primarily working on non-value adding stuff, then it's ripe for automation and eventually, outsourcing or disappearance. The point of this is that you should automate to do other, value-adding activities. Of course there are many scenarios where you cannot (management won't let you, cannot work more than the others etc.) and doing these things just highlights how much inefficiency there is in many companies. We always talk about "lean" etc. as if there was no waste, but from what I've seen, it's not really entirely the case.

    Programmers are lazy so they automate a lot of stuff, it's not a bad thing. Look, in the past, we had people running builds, setting up servers and VMs etc. manually. Now a lot of that stuff can happen "automagically", which should let you have more time to do something more productive. But again, there is also a lot of inertia in companies...

    Starting Score:    1  point
    Moderation   +1  
       Insightful=1, Total=1
    Extra 'Insightful' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   3  
  • (Score: 2) by VLM on Wednesday October 03 2018, @11:59AM

    by VLM (445) on Wednesday October 03 2018, @11:59AM (#743345)

    non-value adding stuff

    I automated another process at a different job decades ago, that, insane as it sounds, boiled down to they printed out log files so that humans could grep by hand for errors and stuff. Absolutely insane.

    It was a value add, its just troubleshooting problems went from paying people to page thru hundreds of printed out log pages that were tossed out at the end of the day, to clicky clicky on a LAN connected database in less than a minute.

    There's a lot of value add processes being done out there that have insane designs.