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: 1, Insightful) by Anonymous Coward on Wednesday October 03 2018, @01:10AM (2 children)

    by Anonymous Coward on Wednesday October 03 2018, @01:10AM (#743172)

    Then you are to code yourself out of a job. Only THEN have you done your job right!

    I worked at one place that they paid me to STOP coding. and improving the system for 2yr. They were trying to release the product on a new platform and the 12 coder/designerss and 10 QA staff, could not keep up with one person and an AUTOMATED development system that was working across 3 platforms, including the new that they wanted to do by hand. They systems where tied together with a Bisync-Async converter and synced the systems nightly, including mass compiles.

    Note: this was not "make" or other system, but a in-house built to understand our product. This was when in RPG (yes it is a language long before role playing computer games) with some assemble helpers. It would intersept your compile and map out what was in it, and addded "missing' function stanadradized includes/functions including intertask communication, so 64kB object was not limit any more. Oh did I note... pre internet. 75 users sharing a single "286" powered processor. 1mB of memory on a 16/24 bit address bus with 2 64MB drives.

    Now that was processing. I left the company 3 years alater when the owner needed to build new things outside of the corp structure.

    Starting Score:    0  points
    Moderation   +1  
       Insightful=1, Total=1
    Extra 'Insightful' Modifier   0  

    Total Score:   1  
  • (Score: 2) by MichaelDavidCrawford on Wednesday October 03 2018, @08:58PM

    by MichaelDavidCrawford (2339) Subscriber Badge <mdcrawford@gmail.com> on Wednesday October 03 2018, @08:58PM (#743670) Homepage Journal

    And I repeat myself: why do we need so much memory today to earn our keep?

    In 1992 the code I wrote on an 8 MB 68030 grossed three million dollars.

    Now I have a 2-core i5, a 4-core i7 and a total of 24 GB RAM, 3 TB disk yet I can barely feed myself.

    Surely I'm missing something.

    --
    Yes I Have No Bananas. [gofundme.com]
  • (Score: 0) by Anonymous Coward on Thursday October 04 2018, @03:09PM

    by Anonymous Coward on Thursday October 04 2018, @03:09PM (#744115)

    geez dude, take a minute to spellcheck before submitting