Reviews
A co-founder and executive at a famous game company explains programming rules. The key point is that these are not abstract rules: they are practices actually used by the author's development team and are part of its culture. He says following them strictly contributed to success. Here are the points that impressed me most. Don't make people think. Consistency means making everything as mechanical as possible. If a team's naming rules leave room for judgment or make people think hard, they
Programming Rules was written to reduce the frustration and mistakes described in the author's note. It presents 21 rules for writing better code, based on the practices at the author's game studio, Sucker Punch. Readers unfamiliar with C++ may hesitate, since every example uses it. I usually program in JavaScript and paused at first, but the appendix's chapter on reading C++ for JavaScript programmers let me get through it quickly. There is also an appendix for Python programmers. I began with
The book Programming Rules, as the author says, was created to reduce frustration and mistakes. It offers 21 rules for writing better code, drawn from the programming practices of Sucker Punch, the author's game studio. If you open the book to learn about the rules, readers unfamiliar with C++ may hesitate because all examples use it. I usually develop in JavaScript and paused briefly, but fortunately there is an appendix on reading C++ code for JavaScript programmers, which I skimmed quickly.
The price is high, yet the book has gotten smaller. The type layout does not suit the reduced size and makes it much harder to read. I wish they had kept a format closer to the original; it's quite disappointing.
Chris Zimmerman: Rules of Programming
This book includes a guide to reading C++ code for Python and JavaScript developers. It brings together 21 programming best practices from Sucker Punch, the studio known for the mega-hit Ghost of Tsushima, which has sold nearly 10 million copies worldwide, and the Sly Cooper series. Organized into 21 rules, the book is packed with essential knowledge every programmer should know and insights that spark new ideas for development. It also covers debugging and optimization, as well as writing code, making it useful to programmers in every field, not just game development. Learn Sucker Punch’s distinctive programming techniques and take one step closer to becoming a programming expert.
Korean title: 프로그래밍의 규칙
Korean author: 크리스 짐머만
Korean publisher: 한빛미디어
ISBN-13: 9791169212328
Reviews
A co-founder and executive at a famous game company explains programming rules. The key point is that these are not abstract rules: they are practices actually used by the author's development team and are part of its culture. He says following them strictly contributed to success. Here are the points that impressed me most. Don't make people think. Consistency means making everything as mechanical as possible. If a team's naming rules leave room for judgment or make people think hard, they
Programming Rules was written to reduce the frustration and mistakes described in the author's note. It presents 21 rules for writing better code, based on the practices at the author's game studio, Sucker Punch. Readers unfamiliar with C++ may hesitate, since every example uses it. I usually program in JavaScript and paused at first, but the appendix's chapter on reading C++ for JavaScript programmers let me get through it quickly. There is also an appendix for Python programmers. I began with
The book Programming Rules, as the author says, was created to reduce frustration and mistakes. It offers 21 rules for writing better code, drawn from the programming practices of Sucker Punch, the author's game studio. If you open the book to learn about the rules, readers unfamiliar with C++ may hesitate because all examples use it. I usually develop in JavaScript and paused briefly, but fortunately there is an appendix on reading C++ code for JavaScript programmers, which I skimmed quickly.
The price is high, yet the book has gotten smaller. The type layout does not suit the reduced size and makes it much harder to read. I wish they had kept a format closer to the original; it's quite disappointing.
