This episode continues adding to the 5-day email course that shows you how to build a game. The emails contain descriptions of the code. This episode mainly focuses on how the habit of continuous delivery and making distinct steps will help you write better software. Especially when there’s a team involved.

At one point, we move some output text to it’s own method called playGame and I explain why this is important and why you should consider refactoring your code first before making any functional changes.


What's on your mind?
On a scale of 0 to 10, how likely are you to refer us to friends?