HomeGroupsTalkMoreZeitgeist
Search Site
This site uses cookies to deliver our services, improve performance, for analytics, and (if not signed in) for advertising. By using LibraryThing you acknowledge that you have read and understand our Terms of Service and Privacy Policy. Your use of the site and services is subject to these policies and terms.

Results from Google Books

Click on a thumbnail to go to Google Books.

Clean code : a handbook of agile software…
Loading...

Clean code : a handbook of agile software craftsmanship (edition 2008)

by Robert C. Martin

MembersReviewsPopularityAverage ratingMentions
1,3262514,443 (4.27)1
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. Clean Code is divided into three parts. - The first 13 chapters, fully contained in the audio, describes the principles, patterns, and practices of writing clean code. - The second part, chapters 14 to 16, consists of several case studies of increasing complexity and is included in a pdf that comes with your purchase. 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. 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. - The third part, chapter 17. It 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. Listeners will come away from Clean Code 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 development This book is a must for any developer, software engineer, project manager, team lead, or systems analyst with an interest in producing better code.… (more)
Member:stevesydney
Title:Clean code : a handbook of agile software craftsmanship
Authors:Robert C. Martin
Info:Upper Saddle River, NJ : Prentice Hall, 2008.
Collections:Your library
Rating:
Tags:to-read

Work Information

Clean Code: A Handbook of Agile Software Craftsmanship by Robert C. Martin

Loading...

Sign up for LibraryThing to find out whether you'll like this book.

No current Talk conversations about this book.

» See also 1 mention

English (20)  Hungarian (3)  Spanish (1)  Dutch (1)  All languages (25)
Showing 1-5 of 20 (next | show all)
Cuando lo leí me ayudó mucho con mi iniciación a la programación, más concretamente con el lenguaje de programación Java. Este libro (y muchos de por entonces) asentó las bases de lo que a dia de hoy se conoce como "buenas prácticas" en el ámbito del desarrollo. ( )
  diegocorral | Mar 14, 2024 |
Code is clean if it can be understood easily – by everyone on the team ( )
  muhammadishaque | Aug 17, 2023 |
Great principles for code writing. I can't say I agree with everything, but it's a lot of (good) food for thought. ( )
  zeh | Jun 3, 2023 |
I wanted to love this book, but instead I just sort of liked it. This book is a member of the extensive genre of books on how to write clean code. It sits alongside books like Code Complete by Steve McConnell[1] and many others. Where Clean Code promised to differentiate itself was in the use of three case studies -- about a third of the book -- showing Martin's code cleanup techniques in action.

However, I was disappointed by that section. As someone who codes and reviews code professionally, the case studies were not particularly enlightening. As seems obvious in retrospect, watching someone clean-up code in fairly straightforward ways is not interesting if you do and see that everyday. What I really wanted was a book on being a better code reviewer with advice on how to spot areas for improvement and convince others of the value of those improvements.

The examples could be useful for someone who isn't in a code-review-heavy environment. Martin does a reasonably good job of taking code that may seem reasonable on the surface and improving its readabilty. That said, his comments indicate that he often has a higher opinion of the cleanliness of his end result than I do.

As for the general advice and discussion of how to make clean code, I agree with a lot of his tips and disagree with others. Code cleanliness is an area where the core of just-plain-good ideas is surrounded by a nimbus of sometimes contradictory standards that people pick and choose from. The details of what you choose from the nimbus generally does not matter so much as consistency. (Of course, the real trouble occurs when people don't agree on what belongs in the core and what belongs in the nimbus.)

The book definitely was not a bad read, but it did not fit my needs.

[1] Still my favorite in the genre. ( )
  eri_kars | Jul 10, 2022 |
I have very mixed feelings about this book. Early on, it made me quite mad. But somewhere in the middle, it suddenly started to make sense. By the end, even though I still didn't agree with everything, I really appreciated the point that it's trying to make, and can agree with it.
Don't get me wrong, there are plenty of problems: so many of the examples are either bogus or have glaring problems of their own, there's a lot of bloat and back-patting in the prose, and to say this book is programming language agnostic is a massive lie. There are large sections devoted to the most Java-centric issues and examples, and it renders a lot of the advice from these sections meaningless for anyone using a different language.
My recommendation: start with the last chapter. If you feel like anything it says doesn't make sense or is unjustified, go back and read the related section. Reading the whole thing is a recipe for frustration. ( )
  nitemice | Dec 28, 2020 |
Showing 1-5 of 20 (next | show all)
no reviews | add a review

Belongs to Series

You must log in to edit Common Knowledge data.
For more help see the Common Knowledge help page.
Canonical title
Original title
Alternative titles
Original publication date
People/Characters
Important places
Important events
Related movies
Epigraph
Dedication
First words
Quotations
Last words
Disambiguation notice
Publisher's editors
Blurbers
Original language
Canonical DDC/MDS
Canonical LCC

References to this work on external resources.

Wikipedia in English (4)

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. Clean Code is divided into three parts. - The first 13 chapters, fully contained in the audio, describes the principles, patterns, and practices of writing clean code. - The second part, chapters 14 to 16, consists of several case studies of increasing complexity and is included in a pdf that comes with your purchase. 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. 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. - The third part, chapter 17. It 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. Listeners will come away from Clean Code 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 development This book is a must for any developer, software engineer, project manager, team lead, or systems analyst with an interest in producing better code.

No library descriptions found.

Book description
Haiku summary

Current Discussions

None

Popular covers

Quick Links

Rating

Average: (4.27)
0.5
1 1
1.5
2 1
2.5 2
3 29
3.5 2
4 77
4.5 8
5 90

Is this you?

Become a LibraryThing Author.

 

About | Contact | Privacy/Terms | Help/FAQs | Blog | Store | APIs | TinyCat | Legacy Libraries | Early Reviewers | Common Knowledge | 206,679,341 books! | Top bar: Always visible