Software Evolution Storylines, Inspired By XKCD
jamie tips this mind-blowing data visualization concept from (naturally) data visualization researcher Michael Ogawa, who explains that it was inspired by "this XKCD comic. It represents characters as lines that converge in time as they share scenes. Could this technique be adapted for software developers who work on the same code?"
I thought that too.
The xkcd comic is itself inspired by Charles Minard's 1869 flow map of Napoleon's march to Moscow, a celebrated map in visualisation, and most recently popularised by Edward Tufte, one of the most well known data visualisation experts.
Why would someone, who is supposed to be a data visualisation researcher, not have seen this celebrated work of his own field before he saw a knock-off cartoon?
Does my bum look big in this?
Very often it is difficult to see at a glance whether a project is mature and stable or just dead. It would be interesting to see whether this type of visualisation can tell you at a glance how healthy the project is. If so it would be nice to have this view on sourceforge, etc.
knock-off cartoon
Superbly executed knock-off cartoon, if you please.
I bet the Windows timeline looks like the one for Primer.
Probably he did, but citing xkcd granted him an article on /.
Sure; we've tried every other fad that's come along, might as well try this one also.
Am I part of the core demographic for Swedish Fish?
I'd be interested in seeing XKCD's take on Being John Malkovic though.
...but XKCD pretty clearly was inspired by http://en.wikipedia.org/wiki/The_Wallchart_of_World_History (first version 1890).
It's a pretty cool visualization, illustrating in a very superficial way how each state mutates and evolves politically into its descendants.
-Styopa
I think you need the surface of a Klein bottle to draw that graph.
That must be awkward ... most file extensions do begin with . after all.
Not the way I understand (or my organisation uses) swimlanes.
As is implied by the word swimlane, the diagram shows several horizontal 'lanes', these represent individual people or organisations. Then a flowchart is overlayed onto the swimlanes. Whenever an action is performed by a organisation, the flowchart box for that action is in their lane.
This shows for instance who is responsible for what in a process.
I believe that if, say, LOTR was to be shown as a swimlane. You could have the characters that come into contact with The Ring as lanes across the diagram. And a line moving from one lane to the next as the ring passes ownership but going from left to right as it stays in their grasp.
The diagrans in the article show, in many ways, the opposite. The lanes come together and separate over time showing who is in contact rather than who is doing what.
If this were really happening, what would you think?
Generally speak, humor is found in the unexpected. If you don't expect to see that reference in the given context, and it is made, or if it's being applied in a context that is unexpected, that is funny. At least to the observer that both gets the reference and doesn't expect it.
That said, SQL injection attacks are not only unexpected in a child's name, but I've forwarded that comic on to a number of developers of a large commercial database product (as well as many others) as a way to teach people to USE F*CKING PLACEHOLDERS. It has been fairly successful, I might add. After spending 15 minutes trying and failing to get across to them why "SELECT * FROM MYTABLE WHERE FOO = $foo" is bad, I go look up the xkcd comic and show it to them. In 30 seconds, xkcd's author gets across what I can't in 15 minutes over the phone (perhaps I could do it in person with a whiteboard to share).
Now, maybe a troll will come along and say that I'm not a very good teacher. Although I have plenty of experience to the contrary, let's assume this to be true. My point still stands: those comics teach against SQL injection more effectively than I can, thus it's an invaluable tool. The unexpected reference makes it funny enough for me to remember it, the pointed truth of it makes it a good teaching tool.
Why would someone, who is supposed to be a data visualisation researcher, not have seen this celebrated work of his own field before he saw a knock-off cartoon?
You're either a) new to IT / Computer Science, or b) too young to have experienced a revolutionary new paradigm that matches either anything discovered at Xerox PARC Labs or in general 20-30 years ago by professionals who are now "grey beards," but commonly referred to as old fogies when they point our that even IT / Computing and Computer Science has a history.
Examples include Alohanet (vs. Wi-Fi / "wireless Internet"), time-sharing systems (vs. thin computing or virtualization), IM (vs talk / irc), CU-SeeMe (vs video IM, ChatRoulette), Jennifer Ringley (vs cam-girls), Xanadu (vs. iBooks, Google Books), and Nikola Tesla (vs. "wireless power" and numerous other things he invented, prototyped, or predicted).