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.

	High Performance Python Russel Winder : 31st Jan 2012
	What's happening in Wordpress Chris Adams : 19th Jan 2012
	Wordpress Responsive Design Mark Mitchell : 19th Jan 2012
	Scaling WordPress Peter Westwood : 19th Jan 2012
	HTML5 & Android Webview Dave Springgay : 19th Jan 2012
	Titatnium & PhoneGap... Jonathan Anthony : 19th Jan 2012
	Trends & Patterns Andy Richardson : 10th Jan 2012
	I18n Chris McGrath : 9th Jan 2012
	Judge Joe Corcoran : 9th Jan 2012
	BrowserID Christian Heilmann : 13th Dec 2011
	Usable APIs : 12th Dec 2011
	HATEOS : 12th Dec 2011
	Heroku platform Chris O Davies : 5th Dec 2011
	Deploying Java Apps to Heroku Nicola Tassini : 5th Dec 2011
	The Why, What and How of Heroku John Beynon : 5th Dec 2011