matt_creager

We should take a page out of mobile developments book and provide a pretty graphic that illustrates the 'new project' flow for a web app!

Good point, I joke a lot about being 'victorious' at hackathons, but the truth is, knowledge > than a t-shirt :)

Great, let me know if you run into any issues!

I'm really interested in your feedback, we need an optimal hackathon configuration :)

Hey Zypho, thanks for your feedback :)

I mentioned that I really built Column to solve my own problems first (my fiance might say I need medication, not more software), I happen to be a real-time/node/web-app developer, and participate in hackathons, so you've hit the nail on the head with your last statement :)

I'm hoping that just bringing some attention to this issue, and how we're trying to solve it will help teams recognize that preparation is critical, and an easy way to make participating in a hackathon both more fun, and more informative.

One important point that I think you're making here, is that we need to defend each choice, for example: What makes Swig a good hackathon templating solution?

Debate is important, debate will help us reach some consensus over which tools make appropriate defaults and why. So when the argument begins (hopefully prior to the hackathon), why this tool? You can point them to a landing page which provides the key benefits of each tool, with links to the documentation, and whatever else might help a team get started.

A number of challenges exist, one of them as you mentioned is just a matter of people having different opinions, another is peoples specializations, if you don't frequently work with client-side tools you might not have been introduced to LiveReload for example.

Prescribing an approach beforehand is exactly what I'm advocating, the best way I know how, with an example :)

I think what we need right now is opinions, mine, yours, anyone with expertise and the willingness to apply it to this problem really, so we can begin the process of iterating on it, improving it.

It won't be the best tool for every hackathon, but we can create a solid foundation.

Thanks, honestly, that was my personal preference intervening too, the goal was to use something that allowed you to drop logic into a template (yup, that's a bad practice but it's a hackathon, so who cares?) and didn't scare of someone potentially unfamiliar with template languages (as you mentioned Jade is very different from HTML at first glance).

If you find anything else you think would be useful, let me know. I've got my eye on https://github.com/stephenplusplus/grunt-bower-install as a means of quickly dropping script tags in, and I think some method for simple heroku / aws deployment might be handy too.

Column, like the majority of the side-projects I've been involved in, is the result of my own personal failures & frustrations. Namely:

"Why is it always such a f^*k#ng pain in the ass to get a hackathon group organized!"

I'd like to believe the majority of the dev community is regularly participating in hackathons, they should be, hackathons are a fantastic way to put down our day-to-day responsibilities and remind ourselves why we pursued this career in the first place: it's ridiculously fun. Fun to learn, play with new tech and get a bit competitive.

You know what isn't fun? Endless discussion over which server-side framework to use, which folder structure makes the most sense, which client-side package management system to use, how to bring everyones preferences together. That stuff has a time and place, but during a hackathon? Not so much.

Column is my first attempt to make choices suitable for a hackathon: Which tools will allow us to co-ordinate effectively, to work on different parts of the project without stumbling over each other?

It's a start. Let's build tools that enable us to focus on what's important during a hackathon: winning... I mean having fun.

Thanks Adam, that's awesome, looking forward to your feedback!