This book was born from the need to explain others that they can facilitate a coderetreat. After many first-time facilitator training sessions during the 5 years organizing Global Day of Coderetreat, we realized that we need another medium to explain coderetreat. It is true that the depth of facilitating and hosting can be understood only after dealing with these tasks. This book will help anyone who wants to facilitate or host a coderetreat to make that transition faster and to be more productive during the learning process.

Check out some feedback from readers.

Modern software development is a game of ever-increasing frequency of change. This is why it is imperative to build systems that are flexible and can adapt to changing requirements, both expected and (more often) unexpected. That is why I've written this book.

From 2009 to 2014, I traveled the world working with software developers, both individually and in teams, to improve their craft. Primarily, I did this through a training workshop format called coderetreat. Over those years, I had the opportunity to watch 1000's of pairs of programmers work on exactly the same system, Conway's Game of Life. As time progressed, I began to see patterns arise. I noticed common techniques and designs that spanned languages and companies and crossed national borders.

As co-founder and a facilitator of coderetreat workshops, I had the unique opportunity to provide feedback, both direct and through questions, on improving the act of writing adaptable, simple code. Through the day, we worked on improving our ability to make good choices around the minute-by-minute decisions made while writing code.

This book is about those things I learned from watching these 1000's of pairs working on the same problem. It contains a large part of the feedback that I provide during a typical coderetreat. The primary focus is on the thought process behind refactoring, and how that is influenced by the 4 rules of simple design.

This book is not about Conway's Game of Life. Instead, it uses its domain as a backdrop to discuss the thoughts and ideas behind the 4 rules of simple design. It focuses on the small decisions made while designing your code with the goal of building robust, adaptable codebases that can stand the test of time.

With forewords by Joe Rainsberger and Kent Beck.

Curious what the book is like?

I've put together a free downloadable sample of the book with one of the examples (having test names influence the api) and a section on the ping-pong pair-programming style.