Difference between revisions of "Talk:1319: Automation"

Explain xkcd: It's 'cause you're dumb.
Jump to: navigation, search
Line 8: Line 8:
  
 
The title text reminds me of the old joke about the definition of politics -- "poli-" meaning "many" and "tics" meaning "blood sucking creatures". --[[Special:Contributions/108.162.219.202|108.162.219.202]] 12:31, 20 January 2014 (UTC)
 
The title text reminds me of the old joke about the definition of politics -- "poli-" meaning "many" and "tics" meaning "blood sucking creatures". --[[Special:Contributions/108.162.219.202|108.162.219.202]] 12:31, 20 January 2014 (UTC)
 +
 +
Or the definition of polygon; "poly" = parrot and "gon" = gone (i.e., deceased). Therefore,
 +
"dead parrot" [[Special:Contributions/141.101.99.236|141.101.99.236]] 09:55, 21 January 2014 (UTC)
  
 
Why do the lines on the "Theory" graph converge shortly after automation takes over?  Surely, the idea behind writing a code in this example is to save time.  Therefore, the original task line should remain relatively constant and the coding line should plunge below it, no? {{unsigned|Jevicci}}
 
Why do the lines on the "Theory" graph converge shortly after automation takes over?  Surely, the idea behind writing a code in this example is to save time.  Therefore, the original task line should remain relatively constant and the coding line should plunge below it, no? {{unsigned|Jevicci}}
  
 
: Once the automation takes over, the programmer will no longer have to do anything, the program will take care of it [[User:Raestloz|Raestloz]] ([[User talk:Raestloz|talk]]) 00:22, 21 January 2014 (UTC)
 
: Once the automation takes over, the programmer will no longer have to do anything, the program will take care of it [[User:Raestloz|Raestloz]] ([[User talk:Raestloz|talk]]) 00:22, 21 January 2014 (UTC)

Revision as of 09:55, 21 January 2014

Why is this administrator protected? Did an admin lock it just to make sure they'd be the first person to explain it? --Mynotoar (talk) 07:12, 20 January 2014 (UTC)

It is not protected. Check the logs. 108.162.246.117 07:39, 20 January 2014 (UTC)

Alright, done the preliminary explanation. I think I got the joke right, and I'm a programmer myself so I can relate to the graphs. However, laymen may not understand the circumstances of programming world, so maybe simpler words could be used, or a real-life example given. That and I'm not a native English speaker, so someone else should do some grammar check. Also, I posted that from my mobile, it's not really convenient (editing the post itself is already a bit hard) so I'll do some fact checking and citation-linking once I got home. I did check on the screwing definition with TheFreeDictionary, don't have time to do better search now. Raestloz (talk) 08:55, 20 January 2014 (UTC)

Note that in reality, many tasks can be automated successfully: while the programming takes longer that expected, may not simplify the task as much as expected and the program feels unfinished, outside circumstances can force the programmer to abandon ongoing development and use the program for partial automation instead. -- Hkmaly (talk) 09:54, 20 January 2014 (UTC)

The title text reminds me of the old joke about the definition of politics -- "poli-" meaning "many" and "tics" meaning "blood sucking creatures". --108.162.219.202 12:31, 20 January 2014 (UTC)

Or the definition of polygon; "poly" = parrot and "gon" = gone (i.e., deceased). Therefore, "dead parrot" 141.101.99.236 09:55, 21 January 2014 (UTC)

Why do the lines on the "Theory" graph converge shortly after automation takes over? Surely, the idea behind writing a code in this example is to save time. Therefore, the original task line should remain relatively constant and the coding line should plunge below it, no? -- Jevicci (talk) (please sign your comments with ~~~~)

Once the automation takes over, the programmer will no longer have to do anything, the program will take care of it Raestloz (talk) 00:22, 21 January 2014 (UTC)