Game Programming Patterns

Game Programming Patterns By Nystrom, Robert Book – 2014

Programmers will want to read this book. Not just game programmers, but also any programmer. Program structure is important for maintainability of large or medium programs. C++ language programmers will get the most benefit from the book. Other languages are also discussed, and all languages require some attention to structure.

Nystrom’s book is very readable and, perhaps I should add, entertaining. He has a dialogue on the go: the margin notes (his inner critic) are in counterpoint to the main discourse.

He gives credit to the Gang Of Four book (noting that it is 20 years old now,) as a foundation for his proposed new set of patterns.

C++11 and C++14

Effective Modern C++ 42 Specific Ways to Improve your Use of C++11 and C++14, Scott Meyers, O’Reilly, 2014

Programmers will like this excellent, practical book. With the new C++ standards, it is much easier to write correct, maintainable C++ programs. The book explains, with colorized code examples, how to make use of the new features such as auto type declarations, move semantics, lambda expressions, and concurrency support.

With a language as complex as C++, one would not be surprised to get a thick weighty tome on this subject, but the book is a reasonable size at 300 pages. Get up to speed with the performance language!

21st Century C

21st Century C – C Tips From the New School, Ben Klemens, eBook – 2014

The C language has improved over the years. If have some knowledge of programming, and you want to make best use of this fast language, then read this excellent ebook. Yes, the info is all on the web somewhere. But I challenge you to find it in a readable form. This book has the legendary O’Reilly quality.

Better Programmer

Becoming a Better Programmer, Pete Goodliffe

New programmers will benefit from reading this book, and applying its recommended development practices. It is important enough that I will claim that your career will taken to a new level. My experience working with many programmers is that at least half of them needed to adopt the practices covered by this book (not you of course!).

Experienced programmers will get a queasy feeling, knowing they have cut some corners to get code delivered a day or so earlier, and that it will come back to bite them soon.

This is not an Extreme Programming (XP) book, though the author seems in favour of XP. It is more about how to program, design, and test well. I particularly liked the explanation of Technical Debt, which other books and blogs mention without explaining.

Read the e-book on the bus to work!