There were so many ways for Art Hackathon to go wrong, but more ways for it to go right than I realised too. Failure seemed so vivid in my mind’s eye, non-failure seemed so unlikely – at each step I couldn’t believe it all worked out.

Having vaguely committed to help Theo, Tom and Catherine put on a hackday about creativity and hardware (art?) I went on holiday for two weeks. I came back and discovered that tickets were going to be £20, and assumed this would be catastrophic or even fatal, but it wasn’t, and tickets sold. In fact they sold out. I was completely wrong to assume they had to be free, that was win number one.

Free because I knew we were going to have to promote it a lot, and as soon as people think you are making money they start mentally putting you in the spam category, which, I can say from experience, is incredibly disheartening. When I read this very touching blog about Hack Circus I instantly recalled the difficulties of promoting The Thing Is, a student magazine I helped run. We’d spend hours working to produce it, and then people would assign the most malign motives to us when we tried to get the word out. Forums (and hackspace mailing lists…) are incredibly hostile to people promoting things, even things that are highly relevant and not-for-profit.  Twitter, which didn’t exist when we did TTI, is fine with you promoting your projects. If you don’t like it, you can unfollow. Similarly, university internal mailing lists are very supportive.

For the record, we made no money and did not intend to. All of us, especially Theo and Tom, spent many many days on it.

Museum of Lies won the popular vote for best hack

Win number two was sponsorship. Theo got Ravensbourne Uni to sponsor us, effectively providing us with an amazing space for free. Unexpected lesson: open-plan office accoutrements are great for hacking. We were in the auditorium, but we were able to borrow big TV screens on wheels and also office dividers from around the Uni. Office dividers turned out to be great for making ad hoc structures for people’s hacks. Big TVs make hacking at scale possible.

Screen Shot 2015-05-19 at 00.37.21

Bare Conductive gave us conductive paint and it was a hit with hackers. Tessel were incredibly generous with us, gave us amazing hardware, and ended up hand delivering it from the US, because they are lovely (they were coming over anyway…)

Having seen these two bits go right, I started to worry that the dynamic on the day would be wrong. I imagined us finishing the talks, explaining all the hardware then saying “GO!” to the audience and them all just staring at each other, not knowing what to do. I got so paranoid about it that I caused an entirely pointless argument with Theo about the exact location of the chairs and tables, which I thought violated some kind of hacking feng shui, an entirely spurious concern.

We asked people to propose projects in our forum before the event, but very few people did. This only heightened my concerns. I should have had more faith, when we asked people to come to the front and pitch ideas about half of the participants did. There were too many ideas, not too few – fortunately teams were able to consolidate out of similar pitches and we ended up with a manageable number.

People at the front pitching ideas
People at the front pitching ideas

I can’t say if we could rely on that happening again, but it does make me think of a weird paradox in the way that I allocate time to the hackdays that I’ve been to. When I get emails from hack organisers I think “Don’t have time for this!”, and I never go and do whatever they want me to on their forum / google doc / IRC etc. Which makes absolutely no sense because I’m about to devote a whole weekend to the hack. In my mental accounting the hackday has to be boxed into a weekend timeline, otherwise I somehow feel it’s making an unreasonable demand on me. Perhaps other people feel like this.

And then at the end of it all people produced amazing hacks, hopefully we’ll have a proper video up soon. I wanted to use this space to record lessons learned, and the biggest one is that stepping out of your IT comfort zone is massively time consuming.

The winners (Scott Wooden and Chris Brown), who made a (highly addictive) web game, had an almost production ready app with animated transitions and beautiful graphics. Both of the team were using a language they use professionally (javascript), presumably using the tooling they use everyday at work. For them the hack was a chance to push what they already knew in a new direction, which they did very successfully.

Get The Banana, jury prize winner
Get The Banana, jury prize winner

Contrast that with a hack that starts with borrowing a Raspberry Pi from our hardware library. Even if you know Raspberry Pis a bit, there’s hours of flashing SD cards (if you want your preferred OS), finding out IP addresses, turning on SSH, discovering passwords before you can start. Wait, this is a Raspberry Pi 2? Does this library work with it? And so on…

I could do another post on the hostility of the Raspberry Pi as a platform, some of which I think is wilful, but there are two things I’d do differently if there was another chance and more resource. Two things other than sort out Raspberry Pi.

Firstly, I’d start out with hardware in functioning setups. Want a servo running off a Pi? Here’s one that we know works. Hack it if you want, but you can see it working now, so if it stops working you can probably work out why. If you really screw up, we could just flash you a new SD and rescue you.

Secondly, you can’t help teams very much when you are organising. I’d love to have spent more time helping hack, but I was too busy wrestling with an industrial scale coffee percolator or running the hardware library. There’s no solution to this except to have more people helping.

The hack was a laboratory too, we had two ethnographers looking at it, I was graphing the Twitter network around the event and there will be a follow up survey. Hopefully that will allow us to prove the value of the event to future sponsors, and also help us improve the next one, if anyone ever has enough energy to do one again.

A final lesson learned was the the output was so good that it was very sad to take it all apart after the show and tell – we could easily run an exhbition of the work which allowed more people to see what had been achieved. Next time…










Comments are closed.