Explain xkcd: It's 'cause you're dumb.
Title text: You can look at practically any part of anything manmade around you and think "some engineer was frustrated while designing this." It's a little human connection.
This strip depicts a common experience to most people, becoming frustrated with a device, system, or rule that appears to be badly made or have no purpose other than to frustrate the user (in this case, a traffic light that seems unreasonably, inexplicably long). One temptation we might have in these cases is to blame the designer of the system. Here, the designer appears and testifies to the amount of effort that went into the design, considering many factors. He challenges the driver to come up with a better solution, the implication being that without a similar amount of training an effort, any naive solution would have flaws the designer would be happy to point out. This demonstrates to the driver and reader that just because they were unlucky enough to encounter something in a way that was inconvenient for no obvious reason, doesn't mean there is no reason at all.
Of course, all of this has occurred after the designer leapt out of nowhere onto the hood of the car, so he may not be entirely stable. This is capitalized on in the final panel, wherein he finally admits that red light won't change until Tuesday (presumably a day or more beyond the current time), meaning that the timing scheme really was absurd after all.
The title text returns to the original point, reminding us that designers work hard and often encounter complex problems in doing their jobs. Their frustration may also be in part from the knowledge that future users will blame them for unavoidable problems and undervalue their work. With a little empathy, we can find a human connection to these problems rather than let them drive us crazy.
- [A man in a car, sitting at a red light.]
- Man: This light always takes forever. I'd like to smack the idiot who designed this intersection.
- [An engineer steps up onto the hood of the man's car.]
- Engineer: Hi.
- Man: Who the hell are you?
- Engineer: I designed this intersection.
- Engineer [arms spread outward] : You're right - I should have just made the light shorter! Never mind the hours of simulation and testing I did. Never mind that this intersection interacts with it's neighbors in a complicated way and it took me a week to work out timing sequences that avoided total jams.
- Engineer: Clearly, I'm a crappy engineer and you have a better solution. Go on, show me your proposed timings.
- Man: Get the hell off my hood before I start driving and fling you into traffic.
- Engineer: You can't. Light's red.
- Man: Well, when will it change?
- Engineer: Tuesday.
add a comment! ⋅ add a topic (use sparingly)! ⋅ refresh comments!
The driver seems to know that the light always takes forever and yet there he is. Sometimes people get what they deserve. -- 220.127.116.11 (talk) (please sign your comments with ~~~~)
when I'm at a long light like this, I don't blame the engineer of that light, I blame the city planner who decided to put that light at that intersection when a different system would have worked better (one that adjusts to time of day and/or uses sensors to notice that someone's waiting and there's no traffic). just sayin' 18.104.22.168 13:42, 25 April 2013 (UTC)
- Not that 22.214.171.124 will necessarily see this, but there are traffic engineers, who design intersections (not only the types, number, and arrangement of individual signal assemblies and sensors in a given intersection, but also any timing or sensor-based relationship with other intersections and several other things not signal-related). I think the engineer in the comic is one of these traffic engineers (maybe that's what ...16.171 is calling a city planner?). It's not the one that designed the actual assembly of bulbs, lenses, circuits and housing that makes up a given "signal" - which would also no doubt be an engineer (somewhere in the civil/electrical area I might venture to guess)Brettpeirce (talk) 18:28, 18 February 2014 (UTC
- I am a traffic engineer, and there are lots of reasons why intersections are designed as they are, and lots of reasons why they don't live up to expectations. Aside from the inherent difficulty of predicting traffic, there are issues centring around when the intersection was designed and when the user experiences it (this can be decades), the availability of data on the subject (in all but the densest/busiest areas most people would be surprised how little data there is, I think), and just the sheer expense of some "simple" solutions. For example, ...16.171's jurisdiction may not consider worth ~$100 000 to put in a sensor just so the occasional driver who wants to turn left from a low-volume approach only waits 20 seconds instead of 126.96.36.199.102 22:27, 26 May 2015 (UTC)
188.8.131.52 06:44, 27 April 2014 (UTC)Doesn't mean Cueball can't reverse away to get the engineer off his . Unless it's a one-way street.
- Or there's another behind him that we can't see because of reasons of artistic brevity. -Pennpenn 184.108.40.206 04:50, 6 February 2015 (UTC)
The punchline gets funnier based on how far away you are from the forthcoming Tuesday. Only share this comic on Wednesdays. 220.127.116.11 (talk) (please sign your comments with ~~~~)
- LOLing right now as it's monday and I scrolled down to see when it was posted (Friday) 18.104.22.168 19:04, 24 October 2016 (UTC)
It looks like the engineer comes out of the bumper :)22.214.171.124 20:15, 10 November 2016 (UTC)