The FATE main page exposes a lot of data. The manner in which it is presented has always been bounded by my extremely limited web development abilities. I wrestled with whether I should learn better web development skills first and allow that to inform any improved design, or focus on the more useful design and invest my web development learning time towards realizing that design.
Fortunately, Mans solved this conundrum with an elegantly simple solution:
The top of the page displays a status bar that illustrates — at a glance — how functional the codebase is. The web page source code identifies this as the failometer. It took me a few seconds to recognize what information that status bar was attempting to convey; maybe it could use a succinct explanation.
Mini-Book Review
Before Mans took over, I thought about this problem quite a bit. I needed inspiration for creating a better FATE main page and aggregating a large amount of data in a useful, easily-digested form. Looking around the web, I see no shortage of methods for visualizing data. I could start shoehorning FATE data into available methods and see what works. But I thought it would be better to take a step back and think about the best way to organize the data. My first clue came awhile ago in the form of an xkcd comic: Blogofractal. Actually, the clue came from the mouseover text which recommended Edward Tufte’s “The Visual Display of Quantitative Information”.
I ordered this up and plowed through it. It’s an interesting read, to be sure. However, I think it illustrates what a book on multimedia and compression technology would look like if authored by yours truly– a book of technical curiosities from epochs past that discusses little in the way of modern practical application. Tufte’s book showed me lots of examples of infographics from decades and even centuries past, but I never concisely learned exactly how to present data such as FATE’s main page in a more useful form.
Visualization Blog
More recently, I discovered a blog called Flowing Data, authored by a statistics Ph.D. candidate who purportedly eats, sleeps, and breathes infographics. The post 11 Ways to Visualize Changes Over Time: A Guide offers a good starting point for creating useful data presentations.
I still subscribe to and eagerly read Flowing Data. But I might not have as much use for data visualization now that Mans is on FATE duty.
A bit off topic: is anybody who is familiar with the ffmpeg codebase looking at the test failures to identify whether it’s definitely a compiler bug or an ambiguity (i.e. whether a mythical standards conforming compiler would be allowed to interpret the source code in that way)? And in cases of real compiler bugs, submit them to the appropriate bug tracker? Getting code important to you to be part of a compiler’s testsuite can be a win.