It's been a while since I read this book and found it very interesting. Wish I had posted before. He talks about best practices in programming and development (serving both for developers and for project managers). Have you ever tried to explain to someone who was participating in the same project you he needed to use the same naming standard that all team, only he knew not say why (except that it was to be best for the team)? Or when you know intuitively that it is necessary to use keys in a block with if to improve the readability of code, just say you do not know why that's good (ok, crude example, but it's the best I can think of!)? Things in the book of this type are analyzed and displayed based on statistics in various development environments, Also taking examples from NASA and IBM!
It is highly recommended reading for those who do not believe Coding Standard is a necessary requirement for any project. Of course it is also reading for all who want to improve their knowledge in this area!
The author shows problems encountered in various languages and development environments in a fun way and conscious, the result of several years of experience. Read it and then tell me what you think!
P.S.: The book is in English this here for those who prefer.