%0 Book %1 Martin2008 %A Martin, Robert C. %D 2008 %I Prentice Hall PTR %K design encapsulation %T Clean Code: A Handbook of Agile Software Craftsmanship %U http://www.amazon.com/exec/obidos/redirect?tag=citeulike07-20&path=ASIN/0132350882 %X Even bad code can function. But if code isn't clean, it can bring adevelopment organization to its knees. Every year, countless hours andsignificant resources are lost because of poorly written code. But it doesn'thave to be that way.Noted software expert Robert C. Martin presents a revolutionary paradigm with\_**Clean Code: A Handbook of Agile Software Craftsmanship**\_. Martin hasteamed up with his colleagues from Object Mentor to distill their best agilepractice of cleaning code ” on the fly” into a book that will instill withinyou the values of a software craftsman and make you a better programmer—butonly if you work at it.What kind of work will you be doing? You'll be reading code—lots of code. Andyou will be challenged to think about what's right about that code, and what'swrong with it. More importantly, you will be challenged to reassess yourprofessional values and your commitment to your craft.\_**Clean Code**\_ is divided into three parts. The first describes theprinciples, patterns, and practices of writing clean code. The second partconsists of several case studies of increasing complexity. Each case study isan exercise in cleaning up code—of transforming a code base that has someproblems into one that is sound and efficient. The third part is the payoff: asingle chapter containing a list of heuristics and ” smells” gathered whilecreating the case studies. The result is a knowledge base that describes theway we think when we write, read, and clean code.Readers will come away from this book understanding * How to tell the difference between good and bad code * How to write good code and how to transform bad code into good code * How to create good names, good functions, good objects, and good classes * How to format code for maximum readability * How to implement complete error handling without obscuring code logic * How to unit test and practice test-driven developmentThis book is a must for any developer, software engineer, project manager,team lead, or systems analyst with an interest in producing better code. %7 1 %@ 0132350882

@book{Martin2008, abstract = {{Even bad code can function. But if code isn't clean, it can bring adevelopment organization to its knees. Every year, countless hours andsignificant resources are lost because of poorly written code. But it doesn'thave to be that way.Noted software expert Robert C. Martin presents a revolutionary paradigm with\_**Clean Code: A Handbook of Agile Software Craftsmanship**\_. Martin hasteamed up with his colleagues from Object Mentor to distill their best agilepractice of cleaning code ” on the fly” into a book that will instill withinyou the values of a software craftsman and make you a better programmer—butonly if you work at it.What kind of work will you be doing? You'll be reading code—lots of code. Andyou will be challenged to think about what's right about that code, and what'swrong with it. More importantly, you will be challenged to reassess yourprofessional values and your commitment to your craft.\_**Clean Code**\_ is divided into three parts. The first describes theprinciples, patterns, and practices of writing clean code. The second partconsists of several case studies of increasing complexity. Each case study isan exercise in cleaning up code—of transforming a code base that has someproblems into one that is sound and efficient. The third part is the payoff: asingle chapter containing a list of heuristics and ” smells” gathered whilecreating the case studies. The result is a knowledge base that describes theway we think when we write, read, and clean code.Readers will come away from this book understanding * How to tell the difference between good and bad code * How to write good code and how to transform bad code into good code * How to create good names, good functions, good objects, and good classes * How to format code for maximum readability * How to implement complete error handling without obscuring code logic * How to unit test and practice test-driven developmentThis book is a must for any developer, software engineer, project manager,team lead, or systems analyst with an interest in producing better code.}}, added-at = {2010-12-04T15:26:07.000+0100}, author = {Martin, Robert C.}, biburl = {https://www.bibsonomy.org/bibtex/2e989add7d0098e40f1b3795ded21e070/jimbarritt}, citeulike-article-id = {3766584}, citeulike-linkout-0 = {http://www.amazon.ca/exec/obidos/redirect?tag=citeulike09-20&path=ASIN/0132350882}, citeulike-linkout-1 = {http://www.amazon.de/exec/obidos/redirect?tag=citeulike01-21&path=ASIN/0132350882}, citeulike-linkout-2 = {http://www.amazon.fr/exec/obidos/redirect?tag=citeulike06-21&path=ASIN/0132350882}, citeulike-linkout-3 = {http://www.amazon.jp/exec/obidos/ASIN/0132350882}, citeulike-linkout-4 = {http://www.amazon.co.uk/exec/obidos/ASIN/0132350882/citeulike00-21}, citeulike-linkout-5 = {http://www.amazon.com/exec/obidos/redirect?tag=citeulike07-20&path=ASIN/0132350882}, citeulike-linkout-6 = {http://www.worldcat.org/isbn/0132350882}, citeulike-linkout-7 = {http://books.google.com/books?vid=ISBN0132350882}, citeulike-linkout-8 = {http://www.amazon.com/gp/search?keywords=0132350882&index=books&linkCode=qs}, citeulike-linkout-9 = {http://www.librarything.com/isbn/0132350882}, day = 11, edition = 1, howpublished = {Paperback}, interhash = {67eea554509df8399f59d17b4517421b}, intrahash = {e989add7d0098e40f1b3795ded21e070}, isbn = {0132350882}, keywords = {design encapsulation}, month = {August}, posted-at = {2009-03-08 14:09:44}, priority = {3}, publisher = {Prentice Hall PTR}, timestamp = {2010-12-04T15:34:10.000+0100}, title = {{Clean Code: A Handbook of Agile Software Craftsmanship}}, url = {http://www.amazon.com/exec/obidos/redirect?tag=citeulike07-20&path=ASIN/0132350882}, year = 2008 }