Informal Session¶

Since March 2007, the dojo has gathered at local coffee shops to code in a shared environment (google calendar, rss. These sessions are free-form with a minimal process that helps ensure everyone has something interesting to work on. We work in ProgrammingPairs to work on a number of different projects that we try to make available as FreeSoftware.

Projects in development are available in the DojoRepositories. Project information (stories, status, participants) is available.

These projects are partitioned into a few categories:

Warmups (or "Katas")¶

Recently, the group has introduced Code Katas as a form of warm-up exercise for the evening. These are usually short programming exercises that take about an hour for a pair of programmers to complete.

Recent examples:

• Roman numerals: a roman numeral parser in Python
• List traversal: a simple linked list exercise in C

Community¶

In order to ensure that there are interesting things to do at the dojo, the community maintains a few ongoing projects. There will likely be a single programmer at the dojo who maintains the vision for the project in consultation with the rest of the dojo.

Current Projects¶

• ocsim: a public transit network simulation
• interval: a time-based milestone tracking tool for software teams
• codex: document organization/personal wiki/note taking (similar to tomboy)
• callsheets: organizing information about a movie crew into daily "callsheets:http://en.wikipedia.org/wiki/Call_sheet
• chores: a GTD application (like things or omnifocus) that runs well and synchs to mobile environments without requiring Internet access
• elevators: a rules-based simulation of elevator traffic in an office tower
• geohash on android: an implementation of the xkcd random geo-hash for Android

Previous Projects¶

• RSSQ: a simple programmer's story (work item) and velocity tracker
• ZONE: a multi-player game inspired by MOO

Pair Programmers' Interests¶

• Raju (chores, codex)

Individual¶

Each programmer in the dojo tends to arrive with their own interests and itches that they invite others help them with. Typically, the majority of the code in these projects is committed by a single programmer. The maintainer will probably tend to work on these projects outside of the dojo.

External¶

Programmers who attend the dojo are invited to suggest defects or BrokenWindows that they have noticed in free software. Since many of us, due to our day jobs, are maintainers of LegacySystems, these projects provide a way to practice our diagnostic and refactoring skills.