Here are the choices for our next technical book meetups – the book rated highest will be the one we read for the March, 2017 meeting (and second place will be read for the August meeting). Voting closes on January 29.
- Mazes for Programmers: Code Your Own Twisty Little Passages by Jamis Buck
275 pages, 2015, $19 – $38
Unlock the secrets to creating random mazes! Whether you’re a game developer, an algorithm connoisseur, or simply in search of a new puzzle, you’re about to level up. Learn algorithms to randomly generate mazes in a variety of shapes, sizes, and dimensions. Bend them into Moebius strips, fold them into cubes, and wrap them around spheres. Stretch them into other dimensions, squeeze them into arbitrary outlines, and tile them in a dizzying variety of ways. From twelve little algorithms, you’ll discover a vast reservoir of ideas and inspiration. Through it all, you’ll discover yourself brimming with ideas, the best medicine for programmer’s block, burn-out, and the grayest of days.
- The Best Software Writing I – ed. Joel Spolsky
305 pages, 2005, $1 – $25
With a nod to both the serious and funny sides of technical writing, The Best Software Writing I: Selected and Introduced by Joel Spolsky is an entertaining read and a guide to the technical writing literati. Contains writings from many authors, such as: Ken Arnold, Raymond Chen, Cory Doctorow, Bruce Eckel, Paul Graham, John Gruber, Mary Poppendieck, Clay Shirky, and why the lucky stiff.
- The Dream Team Nightmare: Boost Team Productivity Using Agile Techniques by Portia Tung
304 pages, 2013, $11 – $24
This first-ever interactive Agile Adventure is the gripping tale of an experienced team struggling with agile adoption. In this unique mashup of a business novel written in the gamebook format, you’ll overcome common yet daunting challenges that come from using agile methods. As Jim, the agile coach, you’ll learn to apply a range of thinking tools and techniques to real-life problems faced by teams and organizations. Find out what really works and what fails miserably from the consequences of your choices. And, unlike in the real world, if at first you don’t succeed, you can make different choices until you get things right.
- Test Driven Development: By Example by Kent Beck
240 pages, 2002, $10 – $50
The book that coined the phrase and changed how software is developed, Test Driven Development: By Example follows two TDD projects from start to finish, illustrating techniques programmers can use to increase the quality of their work. The examples are followed by references to the featured TDD patterns and refactorings. By driving development with automated tests and then eliminating duplication, any developer can write reliable, bug-free code no matter what its level of complexity.