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.

	Re-writing Java classes in Scala - and m Colin Howe : 8th Feb 2010
	Using Cucumber for BDD and Agile accepta Gojko Adzic : 4th Feb 2010
	Rob Nicholson: Global Technology Outlook Rob Nicholson : 27th Jan 2010
	Dragonfly Mark Evans : 13th Jan 2010
	Redcar Daniel Lucraft : 13th Jan 2010
	Waking up to the New Economics of IT Emma McGrattan : 15th Dec 2009
	REAL-TIME APPLICATIONS WITH HTML5 Peter Lubbers : 9th Dec 2009
	DDD Alex Young : 9th Dec 2009
	Javascript Stories Rob Holland : 9th Dec 2009
	ParkBench Panel Discussion, Pizza & drin Russ Miles : 9th Dec 2009
	Groovy & Grails eXchange Keynote Guillaume LaForge : 9th Dec 2009
	Gant, the Groovy targeted scripting fram Russel Winder : 9th Dec 2009
	Easy & secure SOAPful Web Services Tareq Abedrabbo : 9th Dec 2009
	Building DSLs & Groovy Metaprogramming Venkat Subramaniam : 9th Dec 2009
	Building Killer RIAs with Flex and Grail Tomas Lin : 9th Dec 2009