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.

	Cross-Platform Mobile Apps Christophe Coenraets : 24th May 2012
	Native vs HTML5 Paul Ardeleanu : 22nd May 2012
	JavaScript with Gradle Luke Daley : 22nd May 2012
	Ruby’s bin men: a closer look at the gar Elise Huard : 14th May 2012
	Dependency Injection Tom Stuart : 14th May 2012
	CouchDB at the Hut Group Tom McMillen : 9th May 2012
	The Couchbase Server Tutorial John Zablocki : 9th May 2012
	Etherpad Lite Peter Martischka : 8th May 2012
	Buster.js and Phantom.js Tiago Rodriguez : 8th May 2012
	Is Everything Social? Gavin Bell : 8th May 2012
	Moving Beyond Objects Brian Sletten : 3rd May 2012
	Moving Beyond Objects Brian Sletten : 3rd May 2012
	REST & BDD Brian Sletten : 2nd May 2012
	State of the Web Dmitry Buzdin : 1st May 2012
	Simply Business Lukas Oberhuber : 23rd Apr 2012