oznek.weblog

It's been a while since I read this book and found it very interesting. Wish I had posted before. He talks about good practices in planning and development (serving both for programmers and for project managers). Have you tried to explain to someone who was participating in the same project you he needed to use the same naming standard that everyone on the team, only that he could not tell why (except that it was to be best for the team)? Or when you intuitively know that you have to use keys in a block-if statement to improve readability of a code, but did not say why it's good (ok, lame example, but it is the best I can think of!)? In the book things of this type are shown and analyzed on the basis of statistics in various development environments, with examples also from NASA and IBM!

It is highly recommended reading for anyone who does not believe Coding Standard is a necessary requirement for any project. It is also clear that reading for everyone who wants to improve his knowledge in that area!

The author shows the problems encountered in various languages and development environments in a fun and conscious, the fruit of several years of experience. Read it and then tell me what you think!

PS: The book in English that is here for those who prefer.