dojosp / participant-s-projects
- Source
- Commits
- Network (2)
- Issues (0)
- Downloads (0)
- Wiki (1)
- Graphs
-
Tree:
feb0f43
Dojo (author)
Mon Jun 22 19:44:12 -0700 2009
commit feb0f4307a2d14abea28b3bdfaecd07de80755eb
tree afe627a34029c0ee94e7c315d6c418d779e1e1ee
parent fbb30f2ee00d96259ce234342f191b256a15ee44
tree afe627a34029c0ee94e7c315d6c418d779e1e1ee
parent fbb30f2ee00d96259ce234342f191b256a15ee44
README
Most Dojo meetings are now being commited here with comments showing what pairs produced that commit and what was its intent. Regular dojo sessions are committed as folders containing the number of the session and the name of problem. Example: 53-Haskell-basico There is a parallel session for "UberDojo" in which folders have a serial number, the name "UberDojo" and the language it was written in. Example: 01-UberDojo-Python There is also a project we built to help us have dojos in C: Dojo Unit - a small library for testing C programs.

