Stock Photo: Cover May Be Different
The Clean Coder: A Code of Conduct for Professional Programmers Paperback - 2011 - 1st Edition
by Martin, Robert
- Used
Description
NZ$24.33
NZ$6.66
Shipping to USA
Standard delivery: 2 to 11 days
More Shipping Options
Standard delivery: 2 to 11 days
Ships from BOMB BOOKS (Pennsylvania, United States)
Details
- Title The Clean Coder: A Code of Conduct for Professional Programmers
- Author Martin, Robert
- Binding Paperback
- Edition number 1st
- Edition 1
- Condition UsedAcceptable
- Pages 256
- Volumes 1
- Language ENG
- Publisher Pearson, U.S.A.
- Date 2011-05-13
- Features Bibliography, Index, Price on Product - Canadian, Table of Contents
- Bookseller's Inventory # 3U1IBA0031L6_ns
- ISBN 9780137081073 / 0137081073
- Weight 1 lbs (0.45 kg)
- Dimensions 9.1 x 7.4 x 0.6 in (23.11 x 18.80 x 1.52 cm)
- Library of Congress subjects Computer programming - Moral and ethical, Computer programmers - Professional ethics
- Library of Congress Catalog Number 2011005962
- Dewey Decimal Code 005.1
About BOMB BOOKS Pennsylvania, United States
Biblio member since 2021
From the rear cover
Even bad code can function. But if code isn't clean, it can bring a development organization to its knees. Every year, countless hours and significant resources are lost because of poorly written code. But it doesn't have to be that way.
Noted software expert Robert C. Martin presents a revolutionary paradigm with "Clean Code: A Handbook of Agile Software Craftsmanship." Martin has teamed up with his colleagues from Object Mentor to distill their best agile practice of cleaning code "on the fly" into a book that will instill within you the values of a software craftsman and make you a better programmer-but only if you work at it.
What kind of work will you be doing? You'll be reading code-lots of code. And you will be challenged to think about what's right about that code, and what's wrong with it. More importantly, you will be challenged to reassess your professional values and your commitment to your craft.
"Clean Code" is divided into three parts. The first describes the principles, patterns, and practices of writing clean code. The second part consists of several case studies of increasing complexity. Each case study is an exercise in cleaning up code-of transforming a code base that has some problems into one that is sound and efficient. The third part is the payoff: a single chapter containing a list of heuristics and "smells" gathered while creating the case studies. The result is a knowledge base that describes the way 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 codeHow to write good code and how to transform bad code into good codeHow to create good names, good functions, good objects, and good classesHow to format code for maximum readabilityHow to implement complete error handling without obscuring code logicHow 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.
Noted software expert Robert C. Martin presents a revolutionary paradigm with "Clean Code: A Handbook of Agile Software Craftsmanship." Martin has teamed up with his colleagues from Object Mentor to distill their best agile practice of cleaning code "on the fly" into a book that will instill within you the values of a software craftsman and make you a better programmer-but only if you work at it.
What kind of work will you be doing? You'll be reading code-lots of code. And you will be challenged to think about what's right about that code, and what's wrong with it. More importantly, you will be challenged to reassess your professional values and your commitment to your craft.
"Clean Code" is divided into three parts. The first describes the principles, patterns, and practices of writing clean code. The second part consists of several case studies of increasing complexity. Each case study is an exercise in cleaning up code-of transforming a code base that has some problems into one that is sound and efficient. The third part is the payoff: a single chapter containing a list of heuristics and "smells" gathered while creating the case studies. The result is a knowledge base that describes the way 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 codeHow to write good code and how to transform bad code into good codeHow to create good names, good functions, good objects, and good classesHow to format code for maximum readabilityHow to implement complete error handling without obscuring code logicHow 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.
Media reviews
Citations
- Reference and Research Bk News, 08/01/2011, Page 200