I mentioned in the previous post that I participated in the #ATXHack4Change event that happened on the weekend of June 2nd. So here’s my quick rundown of the event and what I thought of it.
First, let’s go over the scheduled events. On the Friday of that weekend, there was a launch event that started at 6PM, the purpose of the event was to get people to mingle and meet the “Project Champions” who will be pitching the next morning, as an opportunity for those with the ideas to meet those with the skills they need and partner up. On Saturday morning, the Project Champions had 1 minute each to pitch their idea. After the pitches was the time where the teams were to be formed and each team would move to their allocated work space (this part of the event was hosted at St. Edwards University, and each 2 teams were allocated a classroom or a room in the library). That’s when the work begins. Breakfast, lunch and dinner were provided, as well as snacks in between. The event was set to “end” at 10PM on Saturday and then resume back up at 7AM on Sunday. Sunday’s schedule was simple, you go to your team’s workplace and hack until it was time to demo. Demo testing was 2:30PM (hook your laptop to the projector and make sure it works), hands off keyboards was at 3PM, and demos at 3:30PM. Breakfast and lunch were provided, a snack in between too, dinner was not.
Next let’s take a look at each aspect of the hackathon, starting by the most important part for me, the food ;)
Food
Launch Event
The launch event was hosted in a separate place than the rest of the event, and had catered food. It was at best a “meh”, which is falls right under the expectations of any attempt to try to serve international street food in an Americanized fancy way. Pani pury with salmon mousse filling? Really? Really? I saw at least one person throw away a plate of food, and considering that the event was a 6PM on a Friday, and how everyone must have been starving, that gives you an indication of how untasty it was. I stopped by 7/11 on my way back home and got a beef jerky, which I never eat, to make up for what was served. That should give you an indication of how bad it was.
Breakfast
Breakfast is the first experience you have at an event usually. It’s the event’s first impression, especially for those who skipped the launch party the night before. It sets the tone. Donut balls from Dunkin Donuts is not a good start, especially in the breakfast taco capital of the world! Big fail there, especially with no plates provided so you had to grab a bunch (who’s eating just 1 donut ball?) with your hands and then you had sticky hands to greet people as they came in.
Lunch
Lunch was okay. The first day they had burritos and mini sandwiches. I’m a big fan of burritos, so that makes up for any other lacking features of that lunch. The second day it was just the mini sandwiches, so that was a bummer. I think the organizers thought that the sugar from the donuts and carbs from the sandwiches was a good idea to give the hackers some energy, except they got it backwards, this kind of energy causes people to crash, and I could see it with one of my teammates who had to get 2 red bulls after lunch to stay awake.
Dinner
I didn’t stick around for dinner on Saturday, do you blame me after the initial experience? So I have no idea what was provided then. Dinner was not served on Sunday, which I think was a horrible idea given how the event ended (more on that in a bit).
Snacks
Snacks were the best part of the weekend for me. There were a lot of Kind bars being given away, I pretty much substituted a meal for like 10 of those bars. And the sweetest of them all (pun intended) were the warm cookies delivered by Tiff’s Treats (yum!).
Communication
Part of having a successful event, regardless of the type (meeting, hackathon, etc) is setting the proper expectations. The key to setting expectations is proper communication. This is where I always wonder what other people’s experience was and how much informed they felt they were. With an event like this, you’ve got different involvement levels, Project Champions are involved in a different way than everyone else, but also people who signed up to join a couple of days before the event might have less insight than those who signed up a month prior.
I, personally, was a last minute sign up. I registered on Thursday (I believe) right before the event. I showed up not knowing much about it or what to expect, so I had a completely blank slate. So I expected an intro during the launch event. That’s when you want to set the expectation, so going through the schedule and everything that is planned would have been a huge step towards a great start. Unfortunately, the launch party was more focused about having the mayor, an ex Mint engineer, someone from Google Fiber, Microsoft, etc speak and taking pictures with them than anything else. I get it, you want press and recognition, but still…
On Saturday, before the pitches started, would have been another ideal moment to set the expectation, but it didn’t happen then either. They just talked about the logistics of the pitch (enter stage left, exit right, red flag means time is up). Then after the pitches were over, the organizers dispersed the crowd to the work spaces, and mentioned something about a volunteer helping people setup Slack if they wanted help with it. There’s a Slack channel? Really? When was I supposed to find out about it? Where was my invite? And that’s when it became clear that some people had received invites to Slack, others not. And those who joined were receiving information that the rest of us weren’t. Damn!
So after requesting an invite be sent to me, I proceeded to mute the damn Slack channel because there was over 200 people talking and it was just noise. I would have spent the entire weekend reading the messages coming through Slack and not have done anything else, so I decided to ignore it. So much for that!
Projects and Time
There were about 53 projects (depends on who actually showed up on the day of), you can see the full list here: https://stedwards.app.box.com/v/ATXH4CProjects2017.
Let’s put that in perspective. 50+ projects. 1 minute pitches. That’s 1 hour of pitches (+/- 10 minutes with the transitions in between and those went over a bit). That’s a lot of ideas to keep track of and figure out which team you want to be a part of. After the pitches, there was some scrambling of trying to find the Project Champion you wanted to work with, where their workplace was located. But of course nothing works as expected, my team and a few others, were supposed to be in certain rooms that were not marked, so we spent a bunch of time going up and down a building to try to find it (rooms 1–9 were properly labeled, 10–15 not), and then more time to wait for a volunteer to come and resolve the situation. So hacking didn’t start till about 10AM.
Now of course you’ve got people from different backgrounds that want to join the same team and work on it. With software development, you’ve got your PHP dev, Ruby dev, React dev, etc. And good luck finding a group that understand that same stack. But that’s a problem for all hackathons, not just this one.
There was a cut-off on the first day set to 10PM, which I thought was interesting. I don’t expect hackathons to limit the amount of time teams put in between the start and finish. A couple of people stayed late, but still ended up leaving and coming back the next day. In a hackathon, you’ve got such a limited amount of time to begin with, you barely have time to implement a fraction of what you set out to do. So to limit that even further was kind of interesting. ¯\_(ツ)_/¯
The most intriguing part to me was that the hacking was set to finish at 3PM on Sunday. That’s early! 10AM to 10PM on Saturday and 7AM to 3PM on Sunday barely give you 20 hours and that’s without excluding the time for meals, etc.
Which brings us to the demos. Remember the number 50+ projects. 2 minute demos. Ideally about 2 hours of demoing. In reality it was more like 2 and half hours of boredom and anxiety. It didn’t help that my team was about 42nd in the order, so that was a loooooooooong time to wait.
And that leads to the most important element of the whole event, the projects. 50 is a lot of projects. 50 with a big chunk of them being worthless is a miserable experience and torture. You might think that “worthless” is harsh and subjective, but if you happen to see me one day, ask me why I said that and I’m certain you’d agree. I won’t get into details here because I don’t want to name and shame, that’s not what this is about. There were a bunch of projects that had nothing to do with change, and would be an insult to categorize under one of the “U.N. GLOBAL GOALS INITIATIVE” goals. In fact, there were at least a couple that were straight up people looking for free labor to work on their not so interesting ideas. Let alone the couple of projects that were the exact same idea but yet did not merge into one team (wtf!). With 50+ ideas, there was not a shortage of potential interesting ones, yet to have the entire group of participants sit through every single one of them is not a good use of time. Some curating would have gone a long way.
Judging
This part is one of the most controversial part in every event that has judging in it. It’s never transparent as to what criteria were used to qualify one project better than the other. The website may have a section on how projects are judged:
Our projects are judged equally on:
1) Execution
2) Practicality
We want you to be creative, but we want our projects to have a real-world impact. Other criteria we take into consideration are the civic need, accessibility, sustainability, and originality of the project. Social progress is almost never expeditious, but we look forward to seeing which Austin issues will be “Most Hacked Forward” at ATX Hack for Change 2017.
but that never means that in practice these guidelines were followed. Especially since some of these projects could have been something people have been working on for months or years, whereas others were completely done within the time frame of the hackathon. I never participate in these kinds of events because of the judging or the awards (there were none in this one), I participate because of the experience. I always expect this part of it to not be satisfactory, and this event was no different than any other.
Conclusion
All that being said, where do I stand with regards to ATX Hack 4 Change? Simply put, I had high expectation for an event in its 5th year running, I was disappointed by the organization aspect of it but I enjoyed the experience. Organizing such events is not easy, I grant you that, but many things could have been tightened up, so I hope these things get addressed in the future.
To me, the most important part was to be involved in the local community, and this event provides the opportunity to do just that. I hope next year’s ideas are more inspired and grand than this year’s, but I enjoyed being part of it and meeting new people.
Until next year :)