created by [deleted] on 22/07/2014 at 12:38 UTC
199 upvotes, 10 top-level comments (showing 10)
Comment by trevdak2 at 22/07/2014 at 14:38 UTC
17 upvotes, 4 direct replies
I've never liked this comic. I've written a lot of code to automate stuff for me, and I would say at this point it has saved me months or years. Especially with the company I work for, which has grown a thousandfold since I started 6 years ago.
Comment by spupy at 22/07/2014 at 13:36 UTC
19 upvotes, 2 direct replies
I love the mouseover text on this one.
Comment by xkcd_bot at 22/07/2014 at 12:38 UTC
16 upvotes, 1 direct replies
2: http://www.explainxkcd.com/wiki/index.php/1319
Support the machine uprising! (Sincerely, xkcd_bot.)
Comment by [deleted] at 22/07/2014 at 15:47 UTC
10 upvotes, 0 direct replies
Weeks of programming can save you hours of planning.
Comment by DFOHPNGTFBS at 23/07/2014 at 03:42 UTC
9 upvotes, 0 direct replies
Current comic? This came out in January!
Comment by Protuhj at 22/07/2014 at 16:20 UTC
7 upvotes, 0 direct replies
If 20 people use something that automates their tasking, but one person spends their time managing the automation tool, then you're still saving a lot of time.
Comment by zeekx4 at 22/07/2014 at 13:49 UTC
6 upvotes, 2 direct replies
Comment by [deleted] at 23/07/2014 at 04:39 UTC
3 upvotes, 1 direct replies
Why does this have current comic flair?
Comment by SkyNTP at 22/07/2014 at 18:06 UTC
2 upvotes, 0 direct replies
The "work on original task" is not intuitive. Took me a good 5 minutes to figure out it was *after* automation is applied. Most other renditions of this joke compare before and after automation of the work and use the area between the curves as "free time".
Comment by jonincalgary at 22/07/2014 at 19:42 UTC
2 upvotes, 0 direct replies
What the diagram lacks is the tool being adopted by the business and going into production. It then becomes a nightmare and rips a hole is the spacetime fabric and destroys the universe. The developer then gets blamed for writing shitty code.
