1425: Tasks

Explain xkcd: It's 'cause you're dumb.
Revision as of 06:00, 24 September 2014 by Athang (talk | contribs) (Explanation: fixed the incomplete tag)
Jump to: navigation, search
In the 60s, Marvin Minsky assigned a couple of undergrads to spend the summer programming a computer to use a camera to identify objects in a scene. He figured they'd have the problem solved by the end of the summer. Half a century later, we're still working on it.
Title text: In the 60s, Marvin Minsky assigned a couple of undergrads to spend the summer programming a computer to use a camera to identify objects in a scene. He figured they'd have the problem solved by the end of the summer. Half a century later, we're still working on it.


Ambox notice.png This explanation may be incomplete or incorrect: Basically just a summary, little in the way of an explanation
If you can address this issue, please edit the page! Thanks.

Cueball appears to be asking Ponytial to write an app that determines if a given picture is of a bird in a state park. These two requirements, while seemingly about equally hard to a human, vary greatly in difficulty for a computer. CS stands for computer science. The title text expands on the information already given, saying that a project to develop a system that could recognize objects was intended to last for only a single summer but instead continues to this day.


[Ponytail sitting at a computer with Cueball standing behind her]
Cueball: When a user takes a photo, the app should check whether they're in a national park...
Ponytail: Sure, easy GIS lookup. Gimme a few hours.
Cueball: ...and check whether the photo is of a bird.
Ponytail: I'll need a research team and five years.
In CS, it can be hard to explain the difference between the easy and the virtually impossible

comment.png add a comment! ⋅ comment.png add a topic (use sparingly)! ⋅ Icons-mini-action refresh blue.gif refresh comments!


the source of title text maybe is Szeliski, Computer Vision: Algorithms and Applications (2010), p. 10. --valepert (talk) 06:59, 24 September 2014 (UTC)

Google’s Artificial Brain Learns to Find Cat Videos might be useful as a description of the problem 08:34, 24 September 2014 (UTC)

Sorry for editing your comment but external links have different syntax that internal links so it wasn't working. -- Hkmaly (talk) 11:21, 24 September 2014 (UTC)

Nice Superman joke there, Pudder! -- 10:26, 24 September 2014 (UTC)

It had been removed in an edit, so I shoehorned in back in :P --Pudder (talk) 12:25, 24 September 2014 (UTC)

Isn't there an xkcd where the estimate of 5 years of work is equivalent to "might take forever?" Rtanenbaum (talk) 13:16, 24 September 2014 (UTC)

I'm pretty sure you're refering to 678. 15:00, 25 September 2014 (UTC)

The link in the description is to a document by Seymour Papert and the book on the project is also by Papert. Is there any contemporary evidence that it was actually Minsky who assigned the project? I think he just got interested in it later. 14:17, 24 September 2014 (UTC)

678: Researcher Translation is probably what you're thinking of, Rtanenbaum. Ndgeek (talk) 17:44, 24 September 2014 (UTC)

Is it possible that Randall's selection of bird rather than another naturally occurring object is a subtle reference to the Birdsnap app (http://engineering.columbia.edu/it-crow-or-raven-new-birdsnap-app-will-tell-you-0) which has solved some of the aspects of this problem? 22:02, 27 September 2014 (UTC)

Hopefully I can add that this also seems to make reference to the U.S. Forest Service intention to make everyone have a permit to take pics, etc., in national parks. https://www.yahoo.com/travel/dont-take-that-picture-the-u-s-forest-service-might-98484656432.html (talk) (please sign your comments with ~~~~)

Post the picture to an online forum, say it's a bird, if it's not everyone will correct you as per http://xkcd.com/386/, so scrape forum and if there's a lot of attention it's not a bird, if there isn't much attention it probably is a bird. 23:06, 3 October 2014 (UTC)

A dev team at Flickr took this comic as a challenge, and set up a PoC at http://parkorbird.flickr.com/ (that seems to work fairly well). -- 20:08, 20 October 2014 (UTC)

I was duly impressed. It doesn't recognize big bird very well, though. ;) Suspender guy (talk) 20:26, 17 February 2016 (UTC)

A 'picture of a bird' from a CS perspective is a reverse engineering problem. The picture is a 2 dimensional rendering of a 3-dimensional world and a 'bird' is a 3-dimensional object. It takes years for the mind of a newborn human to be able to recognize a majority of objects based on their 'first look' at a stereoscopic (two-eyes) image presented by their visual cortex. The software equivalency of this would be to create a 3 dimensional representation of objects and create a linear-algebra algorithm that can define the statistical probability that any given shape is within a certain degree of exclusion a matrix representation of the target shape (area) of the 3 dimensional object (bird) based on distance (using spacial reconstruction). It's not impossible, it's just really really hard. - nerd answer (talk) (please sign your comments with ~~~~)

To be honest I don't think it is impossible to replicate any function of human intelligence and mental capacity on a computer system. It just requires sufficient processing ability, appropriate hardware, and of course, an understanding of how humans do it in the first place. -Pennpenn 03:29, 17 September 2015 (UTC)

Or just give Google a little less than two years, and they'll make Google Cloud Vision API for you Gpk (talk) 20:39, 13 June 2016 (UTC)

I read somewhere that when you ask CS/IT specialist for a probable ETA for solving an interesting problem, you need to multiply the given time to the ETA by 4 and take the next larger unit (a minute becomes 4 hours, an hour becomes 4 days etc.). Can't find the source of that though. 15:47, 12 September 2016 (UTC)

GIS being "easy"

All these years later, I still struggle with the classification of "are we in a national park" as "easy"..

It 'only' requires a functioning GPS-system. A military super-project, whose initial setup cost 12 billion, still costs ~2 million a day, and whose principles of operation depend on both special and general relativity for correctness. And that's before we add the record-keeping and (internet?)logistics involved with providing each phone an accurate GIS-database. The OpenStreetMap (most likely free/gratis source of this type of data, for a cheap app) is a massive undertaking!

(sarcasm on) GIS-lookup sure is easy! Only took a minor Manhattan-project, a literal Einstein, and an army of internet volunteers to solve!(sarcasm off)

(I'm leaving out mobile internet access while in said National Parks (Telecom operators are among the wealthiest companies in the world, and those phone-towers-disguised-like-trees don't come cheap...), because the App would probably be shipped with a hardcoded park-database, not do live queries.)

-- Jules @ 08:13, 18 May 2020 (UTC)

This is about implementation of something existing, not inventing it from scratch. The use of the word "app" implies, that this comic is happening in the smartphone area, so GPS on phones should be a regular thing. --Lupo (talk) 09:57, 18 May 2020 (UTC)
"app" sets the real-world context, but the punchline is about the comparative hardness in CS.
For the pragmatic app-developer, "previously solved" equals "easy"; for a doctorate in computational theory, it doesn't :-)
-- Jules @ 12:16, 18 May 2020 (UTC)
That might be true, but this comic is definitely about developing an app, so it doesn't matter if GPS involves complicated hard- and software setups outside of the app or not. And unless you focus on the theoretical work also for a computer scientist, it is easy to use established GPS methods. --Lupo (talk) 12:45, 18 May 2020 (UTC)

now deep learning is common you not need research team and five years anymore

And it took about five years since the comic was posted to get to that point...

This comic is referring to doing a GIS lookup which is a glorified sql Query which has nothing to do with GPS and the the USGS spatial data a GIS database is commonly populated with is not derived from GPS information anyway. A GIS Lookup IS easy. Gathering the spatial data is difficult, though as previously mentioned its already widely and freely available for use. --PlatterMonkous

The GIS data is being looked at to determine if GPS-derived metadata lies within one of its boundaries, surely? Without GPS, the query has no sensible question to ask.
(Then again, none of my own pictures have that sort of EXIF information. Either they're taken on a 'dumb' digital camera, that doesn't have inbuilt GPS, or even if they're done via my GPS+Camera-equipped tablet (rare) I've likely not allowed the one to be fed data that the other one knows. If it's even turned on. But the comic scenario clearly assumes otherwise.) 20:21, 10 November 2022 (UTC)

I think that, like in a number of other comic explanations, the explanation of the humour has given way to the technical exposition of the situation. What made me chuckle about this comic is the old adage in the software industry that: It takes 5% of the time to implement the first 95%, but 95% of time to complete the last 5%. Even when experienced programmers correctly identify the difficult element of a problem and attempt to compensate for that difficulty in their implementation schedules, they can still be wildly off the mark. In this case, 60 years and counting... 10:55, 9 August 2023 (UTC)