Stories
Slash Boxes
Comments

SoylentNews is people

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, Informative) by VLM on Wednesday October 03 2018, @11:55AM

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

    If you're automating your work in an office, make sure you have a dummy program handy that makes it look like you're actually doing something.

    I think the whole "problem" is a super huge ultra mega international conglomerate problem not small companies.

    As a WAN guy (back when networking job titles were WAN vs LAN guys) at a 100 or so person financial services company working nights and going to school in the day, they had this insane dial-backup system where at least one line was always broken (out of hundreds) so proactively I had the joyous task of manually testing each phone line at night for basically an entire day or two per week. The entire task was done thru a terminal emulator (telix? procom?) at 9600 baud. I automated that into a moderately complicated telix (or was it procomm?) terminal emulator script and let it loose. Because it was a small company my stats for processing alerts and working line problems and closing out tickets were good compared to the previous manual laborer, making everyone happy, also I was much less bored. At a 100K person company, I would have nothing to do and get fired.

    Reason number 3421816813698 to work at a small company not a multinational megacorporation.

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

    Total Score:   3