Originally submitted at O'Reilly
Get 97 short and extremely useful tips from some of the most experienced and respected practitioners in the industry, including Uncle Bob Martin, Scott Meyers, Dan North, Linda Rising, Udi Dahan, Neal Ford, and many more. They encourage you to stretch yourself by learning new languages, looking ...
Professional guidance at your hands
By ederandres_an from Paipa, Colombia on 1/11/2011
Pros: Well-written, Concise, Easy to understand
Best Uses: Novice, Student
Describe Yourself: Developer, University Student
I describe this book as one of the kind "Developer, did you know ...?" because it highlights the best practices that every programmer must keep in mind for a software engineering project. These 97 development practices are organized in 19 categories such as coding style, design principles, project planning, usage of tools, collaborating with pairs, and design for the end user.
Within these 97 best practices are those that should always be applied and those that must be balanced or avoided completely. For example, organizing the source code in an easy, expressive and compact manner (pp. 26–27); and creating designs conceptually correct that reduce the collateral effects of applying the singleton OO design pattern (pp. 146–147).
Each practice is described in one short, concrete article in no more than two pages. Many developers learn the best practices after reading several books, magazines and blogs, but this book organize those practices in one single place. However, it is necessary clarify that this is not a programming book, and for really applying a practice the respective technology documentation must be read.
If you are a junior developer or recent graduated student, this book is a good road to achieve the knowledge acquired by senior developers.
Maybe, a discussion about UML would have been interesting to include.
Note: This review was in exchange of the O'Reilly Blogger Review Program (http://www.oreillynet.com/oreilly/bloggers/)
Within these 97 best practices are those that should always be applied and those that must be balanced or avoided completely. For example, organizing the source code in an easy, expressive and compact manner (pp. 26–27); and creating designs conceptually correct that reduce the collateral effects of applying the singleton OO design pattern (pp. 146–147).
Each practice is described in one short, concrete article in no more than two pages. Many developers learn the best practices after reading several books, magazines and blogs, but this book organize those practices in one single place. However, it is necessary clarify that this is not a programming book, and for really applying a practice the respective technology documentation must be read.
If you are a junior developer or recent graduated student, this book is a good road to achieve the knowledge acquired by senior developers.
Maybe, a discussion about UML would have been interesting to include.
Note: This review was in exchange of the O'Reilly Blogger Review Program (http://www.oreillynet.com/oreilly/bloggers/)
(legalese)
No comments:
Post a Comment