hack-a-thon?

1 view
Skip to first unread message

Sean Copenhaver

unread,
Nov 10, 2011, 1:35:55 PM11/10/11
to ColaCodeDojo
So I wanted to bring up the idea of the dojo getting together for an all day Saturday hack-a-thon in the next month or two.

Basically come up with a problem and a couple of arbitrary technology decision and see where we get. I'm suggesting that one of the arbitrary decisions could be to use JavaScript for as much of the stack as possible. Continues with our focus of JavaScript and possible mimic the idea of node knockout. Perhaps the problems we run into will give us an idea for the next one.

I think I would prefer it kept small or if needed we break into teams, each come up with a random idea and run with it. A potential project could be a system to compile UnQL statements to CouchDB (or MongoDB) views and queries. Could be a bit much for a day but never know.

Anyone have any ideas, expectations, interest?

--
“The limits of language are the limits of one's world. “ - Ludwig von Wittgenstein

"Water is fluid, soft and yielding. But water will wear away rock, which is rigid and cannot yield. As a rule, whatever is fluid, soft and yielding will overcome whatever is rigid and hard. This is another paradox: what is soft is strong." - Lao-Tzu


Bryan Matthews

unread,
Nov 24, 2011, 10:56:13 AM11/24/11
to colaco...@googlegroups.com
Sounds good.  I would however suggest that we try to keep it simple, since we have yet to have success with a project of any magnitude.

--
You received this message because you are subscribed to the Google
Groups "ColaCodeDojo" group.
To post to this group, send email to colaco...@googlegroups.com
To unsubscribe from this group, send email to
colacodedojo...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/colacodedojo?hl=en

Bryan Matthews

unread,
Nov 24, 2011, 10:58:33 AM11/24/11
to colaco...@googlegroups.com
I do like the idea of breaking up into small teams.  We could break into teams to tackle small, focused problems and then reconvene periodically to see what everyone came up with and then rinse, repeat (perhaps even mixing up the teams).
Reply all
Reply to author
Forward
0 new messages