The first Orlando Code Dojo will be held one week from today, Thursday, December 10th, 7 PM at CoLab Orlando (http://www.colabusa.com/). Are you up for the challenge?

Here is what to expect:

7:00 to 7:15 - Introduction and team forming.

At the start of the meeting teams will be formed. In order to facilitate the group formation, we've created a google doc so you guys can sign up for the language you're interested in for this session. Your choice should not be based on performance, memory usage or anything like that. It's just a matter of what you feel like coding in. You're also free to change your mind in case you see someone suggest a language you might be interest in learning.

http://docs.google.com/Doc?docid=0AV60EzcLMaXtZGN3Y2NidjZfNDdjcXFwczVkOQ&hl=en

7:15 to 7:30 - Code challenge introduction

I will be the challenge master for this meeting and do a quick presentation of a code challenge, and give everyone access to a git repo where they can fork to get started on the project. The git repo will also contain detailed instructions on the challenge itself. Don't worry if you don't know Git, there will be plenty of people to help if you don't know it. Just be sure you have git installed on your machine if you want to program on it (http://git-scm.com/).

7:30 to 8:30 - Make the Codez

Each team will attempt to get as far as they can in the challenge, keeping in mind that quality matters over completeness. Writing tested code is recommended but not required, and aspiring to do TDD is certainly something worth your time.

8:30 - Code Checkin

Everyone will checkin their code into git, let us know if you need help doing so. Since everyone will fork from an initial repo, that means everyone will be able to quickly access everyone else's solutions (after 8:30, and later at home).

8:30 to 9:00 - Present your codes

Based on github checkins I'll call one team up at a time to give a 3-5 minute walkthrough of how they solved the problem on the projector. Be warned that you'll be using my computer to show your code on github. Having to switch computers on the projector takes too long, and this means you MUST have your code checked in to present.

9:00 - All Done & Retrospective

We'll wrap up and have a retrospective on the dojo itself, collecting ideas on how to make the DoJo better.

Feedback is most definitely welcome, and please do us a favor and send this email to a few people to spread the word.

Gregg Pollack