This book contains about 120 distinct recommendations. I could have included many, many more. In fact, I filled up a Rejects document as I wrote the book. Following the proven, “top-down” approach, I first came up with a list of best practices in each area of the language. Then I went through each area, filling in the descriptions, examples, and so on. As I did this, I encountered numerous “best practices” that surely were the right way to do things. The reality, however, is that few people would ever bother to remember and follow them, and if they did bother, it would not make a significant difference in their code.
I had realized, you see, that not all best practices are created equal. Some are much, much more important than others. And some are just better left out of the book, so that readers aren’t distracted by “clutter.” I hope that the result—this book—has an immediate and lasting impact. But even among the best practices I didn’t reject, some stand out as being especially important—so I’ve decided to award these best practices the following prizes:
If you follow each of these “best of the best” practices, you will end up with applications that are the joy and envy of developers everywhere!