I took part in a hackathon in Vilnius the other weekend (courtesy of Basedcollective) during the pink soup festival. I brought along an old rotary phone and our two-man team spent the next 48 hours sticking our fingers in it. We wired a Raspberry Pi into the phone which interfaced with all of its IO and communicated with our server via a single websocket connection which controlled everything from two-way audio, the bell ringer (with custom frequency and audio patterns) and the hangup switch. For the demo, we set up an AI agent which could research music, create playlists and play collections of niche music all via the Spotify API on request. Interpreting requests such as:

“play some music by artists who are alleged to be on the Epstein files”

“play some music by artists who are alleged to be on the Epstein files”

or

“create me a playlist of 70s Zambian psychedelic rock”,

“create me a playlist of 70s Zambian psychedelic rock”,

et cetera

We put the personality of a warm Yorkshire gentleman on the other end of the line (courtesy of ElevenLabs) and had good fun getting all the parts working together ready for the final demo under 48 hours later.

As is the evolving trend with writing code nowadays, neither me nor my team-mate looked at a single line of code over the entire weekend. Something which would have been unheard of just 12 months ago has become today's reality. As it was a hackathon, all we cared about was that it worked and the inner lines of code didn't matter.

For this reason, the focus of hackathons has completely shifted away from typing code with aching fingers and zero sleep, to thinking of the system as a whole (not a very unique opinion now, I know) and iterating on intricacies of implementation with radical refactors has become a trivial task. This leaves free mental RAM to actually faff with hardware and how it interfaces with the physical world.

All of this really makes me think:

What does a hackathon moonshot idea really look like nowadays?