Even if you can't name the tunes, you've probably heard them: from the iconic "dun-dun-dun-dunnnn" opening of Beethoven's Fifth Symphony to the melody of "Ode to Joy," the German composer's symphonies are some of the best known and widely performed in classical music. Just as enthusiasts can recognize stylistic differences between one orchestra's version of Beethoven's hits and another, now machines can, too. A Duke University team has developed a machine learning algorithm that "listens" to multiple performances of the same piece and can tell the difference between, say, the Berlin Philharmonic and the London Symphony Orchestra, based on subtle differences in how they interpret a score. In a study published in a recent issue of the journal Annals of Applied Statistics, the team set the algorithm loose on all nine Beethoven symphonies as performed by 10 different orchestras over nearly eight decades, from a 1939 recording of the NBC Symphony Orchestra conducted by Arturo Toscanini, to Simon Rattle's version with the Berlin Philharmonic in 2016. Although each follows the same fixed score -– the published reference left by Beethoven about how to play the notes -- every orchestra has a slightly different way of turning a score into sounds.

In accordance with the mobile revolution, and the web before that, machine learning will cause us to rethink, restructure, and reconsider what's possible as we implement artificially intelligent solutions in business, healthcare and in our personal lives. This meet up will look at where we've been and where we're headed with intelligent algorithms and automation. We will discuss specific challenges facing those who work directly or indirectly with machine learning, including but not limited to: acquiring quality data, automating machine learning, the democratization of data, and the processing power and computing infrastructure needed in the wake of the AI revolution. Programming descriptions are generated by participants and do not necessarily reflect the opinions of SXSW.

We just finished our Lean LaunchPad class at UC Berkeley's engineering school where many of the teams embedded machine learning technology into their products. It struck me as I watched the teams try to find how their technology would solve real customer problems, is that machine learning is following a similar pattern of previous technical infrastructure innovations. Early entrants get sold to corporate acquirers at inflated prices for their teams, their technology, and their tools. Later entrants who miss that wave have to build real products that people want to buy. I've lived through several technology infrastructure waves; the Unix business, the first AI and VR waves in the 1980's, the workstation wave, multimedia wave, the first internet wave.

We just finished our Lean LaunchPad class at UC Berkeley's engineering school where many of the teams embedded machine learning technology into their products. It struck me as I watched the teams try to find how their technology would solve real customer problems, is that machine learning is following a similar pattern of previous technical infrastructure innovations. Early entrants get sold to corporate acquirers at inflated prices for their teams, their technology, and their tools. Later entrants who miss that wave have to build real products that people want to buy. I've lived through several technology infrastructure waves; the Unix business, the first AI and VR waves in the 1980's, the workstation wave, multimedia wave, the first internet wave.