For this dojo, instead of working on a challenge from scratch, we’ll start from an existing solution and try to improve it.

The starting point will be the Minesweeper implementation created on a previous coding dojo. It contains only 272 lines of Java code (source + tests) and a lot of room for improvement.

Some guidelines for the session:

• Two programmers will work on the code for 7 minutes. After this period, one of them switch his place with someone from the audience.
• The pair decides their next step and make sure the audience understand what they’re doing. Discussion with the audience is acceptable, but the final word is always from the pair.
• The pair should follow the 3 Rules of TDD:
1. You are not allowed to write any production code unless it is to make a failing unit test pass.
2. You are not allowed to write any more of a unit test than is sufficient to fail; and compilation failures are failures.
3. You are not allowed to write any more production code than is sufficient to pass the one failing unit test.
• At the end there will be a retrospective to identify all the lessons learned.

	nicolas yuen accessibility API in Flex Nicolas Yuen : 17th Mar 2010
	Software Craftsmanship Ideas & Eden Chris Parsons : 10th Mar 2010
	Software Craftsmanship Terminology Corey Haines : 10th Mar 2010
	PrimeFaces: Next Generation JSF Componen Cagatay Civici : 3rd Mar 2010
	Integrating JSF with Spring Web Flow Karl Widmer : 3rd Mar 2010
	Flex and Spring Integration Rick Evans : 17th Feb 2010
	Hydra and Hypermedia Ian Robinson : 11th Feb 2010
	Rails & iPhone Integration Paul Ardeleanu : 10th Feb 2010
	Bowline: A Ruby GUI Framework Alex MacCaw : 10th Feb 2010
	Architecture of Birdpie, a Twitter Appli Anup Narkhede : 10th Feb 2010
	Fibers in Ruby 1.9 Murray Steele : 10th Feb 2010
	Introduction Murray Steele : 10th Feb 2010
	Show Off, a Ruby-Based HTML Presentation Joel Chippindale : 10th Feb 2010
	Decorating the Domain Brent Snook : 10th Feb 2010
	Using Websockets with EventMachine Ismael Celis : 10th Feb 2010