Bruce Derling posted some excellent instructions to running a Clojure Dojo - so that's how we'll spend our first actually-do-something meeting of 2014!
A Dojo is a safe space to play with new and unfamiliar technologies. We'll have experienced Clojurians on hand with whom team hack on the problem of choice (or another problem your group's decided to tackle!).
We won't be spending time hacking on environments tonight, so if you're going to bring your Clojure environment, please spend a few hours making sure everything's shipshape.
Derling's Dojo Directions (we're gathering for hand-shaking at 5.30, and will kick off at 6pm instead of 7pm):
1. Find your hosts, say hello. Make sure everyone is happy. Make sure newcomers feel welcome.
2. Make sure the food is arriving/has arrived.
3. Make sure there is enough to drink (beer, wine, soft drinks).
4. Get the projector for show and tell.
5. Set up a whiteboard. Write “Dojo Ideas” at the top. Put “Roman Numeral Calculator” as the first idea to avoid the tyranny of the blank whiteboard.
6. Greet fellow clojurians, eat food, drink whatever until 6PM.
7. Think of a silly question for the kick off.
8. At 6PM round everyone up for the kick off.
9. Thank everyone for coming, the sponsors for hosting and your fellow organisers.
10. Get everyone to introduce themselves, say how long they’ve been doing clojure for and answer a silly question.
11. Tell everyone that the dojo is a safe place to be a new to clojure and to try new things and learn things. Let experienced people know it is a great place to be surprised by things they didn’t know and to think hard about what they’ve learned and share it with everyone.
12. Vote on the task for the dojo. In the 1st round people can vote for more than one idea. Do run offs if necessary. In run off rounds you can ask people to only vote for one idea. Votes are approximate, unless it is important that they aren’t. Ties in voting are OK. You can do more than one thing. Teams are sovereign. If a team wants to work and present on something other than what was voted on then that is fine.
13. Make sure there are enough clojure environments/experienced team members to go around. Get them up front to act as the 1st member of each team if needed.
14. Divide into teams of 4-6 people. Teams of 4 are better, but 3 is too small.
15. Get the teams to spread out and start.
16. Do the dojo! This should be enough time for everyone to have 10 minutes at the keyboard and 20-30 mins of discussion. Usually 1 hour 20 minutes.
17. Tell people when each 10 minute period is up and remind teams to rotate. Everyone should write at least 1 working line of clojure code that evening, even if it is just a (println “foo”).
18. Make sure every team understands the problem, is able to get on to wifi, isn’t struggling too much.
19. Swap more or less experienced people from one team to another if a particular team is struggling too much. Ask them if they are still having fun first though. If they are having fun, then leave them alone.
20. After 80 minutes or so, round everyone up for show and tell at the projector.
21. Do show and tell. Thank everyone. Clean up. Go to the pub!