Clean Code : Import Edition :Multi colour book: A Handbook of Agile Software Craftsmanship (Robert C. Martin Series)

I have loved writing code for a very long time. Overtime, I have realized that writing awesome code needs much more discipline than skill. This book emphasizes this very fact in a unique way. The author "uncle Bob" does make very strong & clear remarks with very good supporting examples & rationale. This book can thoroughly embarrass good / great code that lacks discipline & hence foresight. I recommend reading this book more than once for those... who would like to write code... who would like to read code... who would like to review code... who would like to maintain code... who would like to design software... who would like to be part of a software development team for over 2 years... Irrespective of your experience in writing / reading / designing code you think is great (or good enough) you must read this book to know what "clean code" feels like..! and then look past your ego and go back to correct your code :)

This book is a must read for all the engineers who want to read more clean and understandable code. Book is beginner friendly, I loved it.

The book helps you identify how bad code looks like and suggests how it should have been written in the first place. Lot of code snippets have been shown to consolidate our understanding about a particular topic in consideration. Of course, it will be difficult to remember all the concepts by just one time reading. As such, this book will have to be read and referred multiple times by the reader to have the concepts etched in the mind.

The book was delivered in good condition. After looking at the reviews I am in doubt if the book is original or not. But I will give it the benefit of the doubt and anyways It doesn't matter even if it is fake but has all the content of the original book.

Well, if you are still thinking whether or Not to purchase this one, please stop thinking. Just get it already. Its WORTH every penny. When going through this master piece, you connect with a developer deep down in your subconscious who was subdued in writing crappy code by Deadlines and Circumstances. If you are the person to stand up and do the RIGHT thing, this gem would guide you to WHAT the RIGHT THING is!And guess what, even that's worth it. If you want someone to write Maintainable, Readable Code; ask them to go through this once. Not specific to Java developers. I am a .Net Developer. Would recommend this over Refactoring by Mr.Fowler(even that's a great read though)

This book didn't teach something out of the box but it stressed on keeping code readable, one should always see the projects from the eye of readability such that eventually they are easy to collaborate on, if one keeps this perspective all rules / suggestions in this book will come to you.

This is a good book to get knowledge about clean coding but paper quality is very bad

Will help you develop a new perspective of computer programming.

Tengo más de 8 años de experiencia como ingeniero en software y a pesar de eso, no puedo dejar de recomendar este libro. Es simplemente demasiado bueno, no sólo en enseñarte reglas que te ayudarán a tener un código más limpio y fácil de extender, sino también para recordarte esos puntos que quizás fuiste dejando atrás con el tiempo, ya sea porque tu empresa no lo exige, porque en algún proyecto la presión no permitió que las cosas se hicieran de la manera correcta o simplemente porque cuando lo viste la primera vez no le prestaste importancia, pero la misma experiencia te enseñó a valorar más esos consejos. No importa cual sea el motivo o tu nivel, no deja de ser un excelente libro que todo ingeniero en software debe leer.

Every so often, a book comes along that codifies best practice in a way that manages to illuminate the path from where things are right now, to a better place that we'd rather be -- things like Fowler et al. Refactoring: Improving the Design of Existing Code (Object Technology Series) or the Gang of Four Design patterns : elements of reusable object-oriented software . This is one of those books. And if much of the material is the sort that seems obvious in hindsight -- well, that is the mark of a well written book, to make the concepts that clear. Taking a series of real world examples -- open source projects with significant user bases, including FitNesse and JUnit -- a series of worked examples take us from good, or at least adequate, code, to a form which is better factored, and easier to read, with the steps along the way clearly marked. Yes, even some of Kent Beck's code is put under the microscope, and carefully polished that extra stage or two more. The reader is cautioned that, without working long hours to follow these examples, this will be just another of those feel-good books. I don't quite agree -- spending just a little time to follow the transformations, and then reflecting on one's own outpourings should be enough to make this a feel-bad book. All the sins from obscurely named variables to sprawling functions that gaily mix abstraction levels, we've all done them (especially programming in FORTRAN on minicomputers with slow stacks and a rule of thumb that 1 call ~ 40 loc in terms of performance). The maxim to take from the book is based on Baden-Powell's "Try and leave this world a little better than you found it", and owes to the same school of thought as "whenever you are in the garden, pull at least one weed". The meat of the book is in distinguishing what are the weeds from the intended crop. So read it, understand the examples, and then refer to it often -- like the other titles mentioned, it is a reference work, and should join them as among the most thumbed on your bookshelf.

.

Está centrado en el lenguaje Java, pero puede ser útil con otros lenguajes de programación porque se explica bastante bien. El libro pasa por casi todos los aspectos que se puede encontrar durante la codificación de un programa. Indica las situaciones en las que nos encontramos a menudo, y cómo resolverlas teniendo en mente que lo que quedará de nuestro trabajo es el código. Y siempre se vuelve al código, ya sea un mismo u otra persona. La idea principal es que éste debe ser claro, limpio y lo más descriptivo posible, lo que pasa por evitar vicios y soluciones sofisticadas. Vale la pena sin duda, y sirve para darse cuenta que todo lo que nos pasa por la cabeza cuando se codifica, nos pasa a todos, darnos cuenta de ello y decidir lo qué queremos hacer. Si ya tienes unas pautas de estilo bien marcadas, quizás no sea tan provechoso como para un principiante.

This is a great book. I have found the concepts informative and helpful. I'm glad I decided to get it. As an aid, I listened to the audio book version while I followed along reading it. This made taking notes a dream. I am now on my way to leveling up my programming skills.