Table Viewer for Music Hackday

This entire weekend was taken up by Amsterdam Music Hackday for which Alex, Dirk and I had planned to build a prototype version of a surface table projector for music discovery.

The functionality we envision helps ad-hoc groups of people who find themselves in the same location/venue/party to compare their music tastes and see where the overlaps and where the holes are. The table would be a turn-taking jukebox with tangible interactions and nice visuals for all users and spectators.

Easier said than done, of course. We spent a great part of the week and most of the weekend hacking, building, eating, drinking coffee, staying up to the wee hours, literally stabbing ourselves with scalpels, cursing a great deal and drinking whisky to get the thing together, when finally on Sunday in the last hour before the presentation we managed to integrate everything to the level that we could shoot a demo video.

Pictures of the proces and demo videos below:

Real men eat meat!


Top view

Point to interface

What we built was just an initial step on the way to the jukebox I described above, but it seemed to look promising enough to net us the first prize from at Music Hackday for which we were very happy.

We like to thank, the organizers and the participants of Music Hackday. It was a great event and for us it was a great occasion to finally get this project started.

We will develop the table further and build out the functionality we had envisioned to make it a real locus for social music discovery. It should be hanging in one of our studios soon, so get in touch and visit if you want to try it out.

Obstakels in het werken met open data

Presentatie gegeven over open data en de obstakels waar je in de praktijk mee te maken krijgt. En passant ook een open data maturity model gemaakt wat wel enig hout snijdt.

Dit was leuk om te doen en ik ben benieuwd of Rotterdam snel kan handelen op dit vlak. Zie mijn favorieten op Twitter voor de reacties.

Rotterdam Open Data, April 21 2010
Nog een foto van het event.

New disciplines for a real-time data world

Some posts that had been sitting in my browser tabs for a while combined together in a brand new job guide for 2010. You can also read this as a follow-up post to my previous post on Why developers are important, this is which developers are important. This post has been lying in my drafts folder for a while, but it has actually only become more relevant.

Some interesting jobs for the coming year(s):

Scalability Engineer

These are already highly sought after ever since Twitter was failwhaling half of the time. Having the competency to keep a website running while it is experiencing massive growth is going to be highly sought after. Some technologies such as Google App Engine promise to make this easy, but they introduce a set of problems of their own. Traditional relational databases are abandoned more and more for the looser often schemaless variety of BigTable-like NOSQL databases that live in the cloud (CouchDB, HSQL, Cassandra, MongoDB, Tokyo Cabinet etc.) or can be scaled at will. If you want to get up to speed on this stuff really fast, there’s a NOSQL conference in London April 20-22nd.

Also knowing your Scala, Tornado, Twisted, NodeJS or other non-blocking framework is increasingly important, since we’re slowly moving out of the request/single response paradigm for the web.

Key skills: Everything command line, functional programming, traditional database management, SQL, virtual machine configuration, puppet

Client Side King

The web based client already was the biggest delivery mechanism for functionality and experience, but it is going to become more and more important. Functionality which you would not have thought possible in a web application, will become available. Some apps may at first be functionally inferior to their native versions, but the fact that they are web native and inherently social will draw people in. After a while either the apps will become more capable or the users won’t care anymore.

Developments in HTML5 bode well for those of us who would like to abolish slow and crashy plugins (yes, Flash). Audio, video, hardware accelerated 3D graphics and much more will soon be native to the web. Just look at Quake II written in JavaScript. There is still a place for adding Silverlight and Flash to certain sites, but the benefits of those technologies are much harder to argue for.

Key skills: JavaScript all variants, styles and frameworks; web-native UI design; marginal IE skills required (since you will not be building for that platform but you should know its limitations); iterative development; guerilla user testing

Algorithm Cook

Ridiculous amounts of data requires strong analytics, very capable navigation and a new sort of editorial proces. These databases draw more and more information from the real world:

“The advent of inexpensive high-bandwidth sensors is transforming every field from data-poor to data-rich,” Edward Lazowska, […] said (NYT) and “Today,” he added, “you have real-time access to the social structuring and restructuring of 100 million Facebook users.” (same source)

Better algorithms will allow us to make better sense of all this data and will provide inputs for the other fields. Everything can have an interestingness in a given context for a given person.

Key skills: multivariate statistics, data wrangling, screen scraping, machine learning, data mining, Excel, SPSS, R/SPlus, Matlab, NumPy, digital signal processing

Visualization Artist

Making sense of all the information requires condensed views with aesthetic qualities. There is simply too much data out there for us to be able to grasp it, so being able to filter and mine the datasets with the help of the other disciplines is essential. But after that step any data needs to be refined, represented and made interactive.

“Decode” ends with “Network,” which examines the interconnections of mobile technologies and the Internet. It also illustrates how digital imagery is helping us to make sense of a frenzied, often confusing world. (NYT)

There are tons of frameworks, tools and libraries in a variety of languages for anybody who wants to try out visualizing stuff. In the end no single one will fit the bill and the best result is achieved combining, mixing and writing something by yourself.

There’s a new O’Reilly book coming out for anybody in the finer arts who’s interested in getting their feet wet with Processing: “Processing for Visual Artists” Then after a while you may be able to produce stuff such as:

Key skills: aesthetic sense, 2D/3D graphics, cognitive psychology, Processing, OpenGL, JavaScript, SVG, design tools, Tufte

And we haven’t even treated the Natural Language Processer, the Urban Information Planner and the Machine Vision Trainer yet but there’s considerable overlap with the above disciplines. If you have any other that we should look at, please suggest them in the comments.

Update: And the New York Times is just looking for somebody with roughly this description.