Note: This post is less of an instructional "how to bootstrap your own hackathon" and more of a historical summary and lots of shout-outs. But feel free to take any useful bits or get in touch about the former.
When thinking about how to start a post detailing what might be the largest project (in scale at least) I've been involved in, I went back to my retrospective of PennApps that I wrote a year ago. This quote shows up near the end:
PennApps offered me a fantastic first large hackathon experience, and we're hoping to try and replicate that experience at RIT going forward.
Wow. Even when we first got started with codeRIT we didn't plan to make anything bigger than a ~50 person hackathon1 by the end of spring 2015, if that. The main plan was to set up a team of RIT students we could bus out to hackathons every weekend. Maybe get jerseys and flags and propel RIT into the hackathon community. And yet, my wishful self wished for a hackathon at RIT. This is the story of how it happened.
Somehow PennApps Spring 2014 got onto my radar. I had been undergoing an identity crisis of whether games or the web would be my future, and that hackathon gave me a chance to play around with my web side. The promise of free travel and food and programming was too good to pass up. And boy did the team at UPenn deliver.
A week later I found myself talking to Carl Domingo about how incredible the whole experience was. I bemoaned the nonexistence of a hackathon or even a hacking community at RIT2. Carl and his go-getter personality decided to take action, and so we began weekly meetings for codeRIT3. To further compliment Carl, he began writing an agenda and taking notes so that we can now relive the beginning. The first meeting notes from April 2nd, 2014 give a short summary into our direction:
- Need more members (students + faculty)
- Need organization
- Constitution, Mission Statement
- Need a way to conglomerate all information about RIT hackathons
- Need a way to find out about off-campus hackathons
- Need ways to organize and fund attending those hacks
The next week there is one note in particular I like for its random inclusion since we weren't planning a hackathon at the time:
Hackathons should have "hack" in the name.
After a couple more meetings in April, there is a meeting with the Dean to formally present our plans. While I was not there, I believe it can best summarized as, "Surprise! You get to host a hackathon now!" As it turns out, some company named Datto was opening an office in Rochester and had recently approached the college with a fistful of cash and a desire to fund a hackathon. And just like that, we were a student group with a dual mission: build up the RIT hackathon community and create the largest hackathon ever hosted at RIT. Or written more formally:
- Create an organization for all RIT hacking resources
- Establish connections with other hacking organizations
- Participate in other college hacks
- Ultimately, to create our own RIT hackathon
The last two meetings of the semester went long with how much we had to begin planning for. We also brought in speakers to share sage advice: Remy Decausemaker, resident hacker community builder and the driving force behind many smaller hackathons at RIT4. Amy Chen, a member of HackRU, offered us advice and a template for the organization. Brynn Claypoole5, the director of PennApps, gave us insight into running a large-scale hackathon. The team left for the summer feeling energized and excited for what we had accomplished in such a short period of time. Plus Tyler Somers gave us the best logo anyone could ever ask for:
We started back up in the fall in high gear. Before our first group meeting we met to brainstorm a hackathon name and landed on BrickHack6. During our first meeting, we had a surprise showing of a few freshman who had no business knowing that we existed, ready to help out in whatever way they could. One of those freshmen, Stefan Aleksic, had been trying to organize a small hackathon for incoming freshmen and worked with Ben Cohen, RIT hacker extraordinaire, to try and get it going. Stefan's plans didn't work out, but we managed to get him and some of his new friends on-board for BrickHack. We also gained Jen Lamere, who had helped organize WiC Hacks the year prior.
We held a public codeRIT meeting a couple weeks into the semester. We hoped it would drive awareness of the RIT hacker team we still wanted to build, as well as act as a recruitment campaign for anyone interested in creating a hackathon. As appears to be the trend in this story, the event worked better than expected and we had 29 people volunteer to join the group.
With all the success on the hackathon creation front, we nearly forgot the original goal of codeRIT was to attend hackathons. However, by the end of the semester all of the organizers had attended at least one hackathon. I did a hat trick of hackathon weekends, attending PennApps X, Software Freedom Day at RIT, and Big Red Hacks. By sending codeRIT members to hackathons, we grew awareness among other RIT attendees and made connections with the organizers at other schools.
Hands down, the largest problem we dealt with in the fall was locking down a date and a venue. There is no sage advice to share after going through that experience. We were a student-run group that had deliberately avoided being an official RIT club, we had never hosted a hackathon before so we had no prior credibility, and apparently we tried to book a venue too late7. Finally out of pity we were granted GCCIS, which worked out really well in the end.
My own efforts were small, but I am likely the most qualified to write about them. At the beginning of the semester we created an organizational structure, and for some reason I ended up being told to lead the Travel & Outreach team8. This manifested into budget planning, bus route planning, and speaking with organizers about how they planned their events. I made sure to dodge the bullet of implementing those plans and graduated in December, but thankfully Stefan Aleksic, Brandon Nieves, and Velizar Demirev were able to pull through and get it done.
One event I am happy to have helped with was the initial
shakedown begging for money at the fall Career Fair. Brandon led the Sponsorship team at the time and invited Colden and I along since we had jobs lined up and didn't need to use the career fair for its intended purpose. We knocked on Google's door first because Brandon knew the recruiter and why wouldn't they want to sponsor? Of course we got the hardest questions with answers we hadn't yet come up with, leaving us dead in the water. But we rebounded with a couple easy wins from Microsoft and Apple9, and the smaller companies were so engaging. A lot of them were just happy to have someone to talk to that didn't require a sales pitch about their own company. In an unexpected turn of events, the Staples representative responded with such enthusiasm that we left the booth with a heaping pile of swag and they ended up being one of the biggest sponsors.
From the time I graduated to the big event on April 18-19, I basically had no more contributions. Returning for that weekend was an incredible victory lap. We had more than 300 hackers attend, roughly half from outside schools. BrickHack was on the Major League Hacking Spring 2015 roster and the Democrat and Chronicle wrote an article about it. A couple news stations aired evening segments. But most importantly, the feedback from hackers and sponsors throughout the event was very positive. Of course there are things that went wrong or could have gone better, but the trailblazing hackathons at other schools gave us a model for success even in round one.
I didn't set out to make a big successful hackathon. Nor did I. All I did was spend 3 years hanging around other people who get stuff done and convince them that this was worth doing. Most of the early codeRIT team hadn't even attended a large hackathon before they began planning one10. Half of us were planning to graduate in the fall, and even with senioritis the train kept chugging forward because of the dedication that team has.
Now I get to look forward to the future of this event, hopefully for years to come. Maybe one day they'll shell out some money to bring me back like we did with Gregory Koberger, the creator of RIT48 among many other things. Never did I imagine this being a part of my legacy at RIT, but I'll take it.
For those of you who don't know what a hackathon is, I will include a great summary by Scott Bureau: "The 'hack' in hackathon refers to the problem solving and exploratory programming that occurs during these 12-, 24- or 36-hour coding competitions, not someone who breaks into a computer system. But hackathons are more than coding. They have become a popular way for students to impress future employers, give back to the community and socialize." ↩
I was ill-informed as to what was actually available for weekend hackers outside of game jams, but at least I was correct that RIT did not have a big annual hackathon. ↩
In those early days, we had Colden Cullen, Brandon Littell, Piper Chester, Veronica Wharton, Nate Perry, Craig Cabrey, Ben Kantor, Michael Timbrook, Tyler Somers, and likely a couple others I am forgetting. Thank you everyone for helping set up the group before having any idea what it would become. ↩
I can't speak highly enough of Remy. He fought for years to get a Free and Open Source Software & Free Culture minor at RIT, which Colden and I were the first to graduate with after taking a class with Remy in Spring 2014 and subsequently packing the remaining classes into our schedules for our last semester. He made the FOSSBox into a welcoming hacker community long before codeRIT ever existed. He ran plenty of RIT hackathons. And now he has the opportunity to scale up his abilities by working with Red Hat. ↩
Since the last couple footnotes turned into thank-you notes, thank you Brynn for giving me Advil at 3:00am at PennApps X. It was a small thing, but I had a splitting headache and would've been in terrible shape otherwise. Oh, and for making PennApps great. ↩
It took awhile to officially remove the space from "Brick Hack," which came down to aesthetic preference. I wish we had a picture of the whiteboard with all the names, there were a couple good alternatives that escape my memory. Ultimately BrickHack won because it highlighted a unique feature of the school, had "hack" in the name (suck it PennApps), and it has a great double meaning since hackers can "brick" their hardware. ↩
Seriously, who are all these people booking the Field House for every weekend slot a year in advance? Stop it, some of us live more spontaneously and need to book that thing only nine months in advance. ↩
This role greatly amuses my mother, who raised an introverted child that would never voluntarily put "Outreach" in any of his professional titles. My dad and I still let her do the talking in social situations, it's just so much easier. ↩
We got about one sentence into our pitch before Myke Olson offered us money and dinner at Nick Tahoe's that night. Greatest feeling ever. ↩
Carl's first big hackathon was PennApps X in the fall. Less than a year later he's getting paychecks from Major League Hacking. ↩