Keynote: How Many Heads Do You Need?
'Jam-oriented programming' is the joke name of a new style of audio development that is no joke at all. It adopts the practices and mentalities of an informal jam session to an extreme extent.
In a typical jam, there is no one in charge and anyone can make any sound they want at any time they choose. In jam-oriented programming, it's the same. Anyone can add, edit or delete code without any permission. Everyone is admin, nothing is certain and anything can happen. It sounds like chaos and it is. But it's also surprisingly successful, with entire audio tools appearing overnight out of the multi-headed process and even a published academic paper to accompany it all.
How and why is this even possible? And what does it tell us about the way we collaborate as audio developers?
Lu Wilson