Software evolution storylines

In a follow up to code_swarm, a visualization to show the development of software projects, Michael Ogawa has another look with Software Evolution Storylines:

My previous software visualization experiment, code_swarm, turned out pretty good. But some wanted a more analytic view of the data — one that was more persistent. I wondered about what this could look like, and came across 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?

The difference between this and the xckd comic is that instead of fictional characters, there are now developers, and instead of characters crossing paths, developers cluster when they work commit changes to the same file. The histogram on the bottom provides information on the type of files that were committed during any given time. Roll over any line to focus on a specific devleoper.

The above is the Apache Webserver storylines.

Here are the storylines for Python. Development began with a few and then surged like a big ol’ bag of spaghetti.

[Storylines | Thanks, Michael]

Favorites

Life expectancy changes

The data goes back to 1960 and up to the most current estimates for 2009. Each line represents a country.

Interactive: When Do Americans Leave For Work?

We don’t all start our work days at the same time, despite what morning rush hour might have you think.

Real Chart Rules to Follow

There are rules—usually for specific chart types meant to be read in a specific way—that you shouldn’t break. When they are, everyone loses. This is that small handful.

Graphical perception – learn the fundamentals first

Before you dive into the advanced stuff – like just about everything in your life – you have to learn the fundamentals before you know when you can break the rules.