How do you save a hackathon project from drowning in a sea of dead apps, inactive websites and outdated data? It’s a common criticism about hackathons, the weekend-long marathon coding events where software programmers volunteer their time to build technical solutions to real world problems.
The events are heavy on creativity and good for launching efforts but short on execution and bad for maintaining them. After the weekend’s over, it’s hard to drum up the same kind of excitement — or time — to work on the projects.
Enter: The ‘Finishathon.’
Hackathon organizers, like the Hacks for Democracy last fall, the students behind PennApps and the team behind February’s TechCamp education hackathon, are now hosting these follow-up events where hackers can tie up loose ends and think about how to share their apps more broadly. It also helps convey the message that projects begun are best served when they are put in the hands of someone who can own and continue the effort.
And that’s one way to save a hackathon project from a watery death.-30-
Hacking naloxone: These graphs show effectiveness in saving PA lives from opioid overdoses
Watch: What is chaos engineering, and how does it work in practice?
Watch: How to take an internal hackathon project to scale
A Temple grad student won a global COVID-solutions hackathon with this social campaign
Sign-up for daily news updates from Technical.ly Philadelphia