5 ms·

You're contradicting the problem that you've set out to solve. Now at a hackathon, when debating with my team which frameworks to use etc we now have another sc

by Zypho 13y ago

You're contradicting the problem that you've set out to solve. Now at a hackathon, when debating with my team which frameworks to use etc we now have another scaffolding tool to debate over. This involves those who might not like yeoman, may not prefer the template library you're giving them. As well there will be those who've looked at your repo and simply don't agree with the code your scaffolding. I like the idea, I really do, but the problem you're solving is all wrong. This isn't a solution for teams to get organized, because in the end you're just another member of their team saying "This is whats best". This is a solution for a team who finds themselves at a real-time/node/web-app hackathon working with technologies they don't know and its a quick way to guide them in "A" direction, weather its the right or not they will decide once they learn more.

matt_creager 13y ago
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.

by Zypho 13y ago

matt_creager 13y ago

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.