Clean Coder, The: A Code of Conduct for Professional Programmers (Robert C. Martin Series) 1st Edition, Kindle Edition

As with Clean Code, that other classic also by Robert C. Martin, The Clean Coder is one of these books I wish had fallen in my hands way before they did.There are many other books that teach you how to write good code - that is not the purpose of this book. Rather, Uncle Bob strives to show you how to be a good professional, and all that entails. If the concept makes you want to sneer, don't - there are lots of behaviors that we'd normally do which are not professional and hurt both your company as yourself. Have you ever said "yes" when pressed to commit to an unreasonable deadline? Pushed half-done work through? Given overly optimistic estimations that people thought of as deadlines? Felt forced to wade through a mess of (partly) your own making? Well, even if you haven't, odds are that you will at some time, as (sadly) every developer finds themselves at such situations at some point during this career. What this book aims to do is to help you identify these situations, explain why these are harmful and provide you with the tools to better respond to these. Oh, and of course, expect the usual useful insight on how to improve your programming practices.While Clean Code was a bit hard to read sometimes and made you stop every now and then, if only to get a better grasp of the concepts, this one feels so relatable that it reads in a breeze. What more can you ask for?Our craft would be a lot better if every programmer was given a copy of this before they started working. Or at the very least, I am certain that this book has helped me become a better professional and I expect its teachings will continue to do so.

I thought this would be about details of a type of coding or coding practice. I can't say I enjoyed the book but I learned a great deal from it. This book deals with the philosophy and ethics of being professional first, and being a coder second. It brought home a lot of flaws that I've displayed across the years. That's why it wasn't all that enjoyable; the writing was all too clear and direct.Although I've been around IT for some time, I've only recently started working directly with professonal developers. That was my motivation for buying the book -- so I could do a better job and maybe earn a bit of respect. It did introduce me to Test Driven Developement (that in itself ought to reinforce that professional coding is new to me). After just one day of trying it I find that I pick up after distractions much faster, cover more cases to test, and even write in such a way the code seems to document itself without the huge effort I've had to make in the past just to get so-so results. And it seems to make even some of the dreary parts more fun because you can almost imagine it as a game you play against yourself. So I'm sold on TDD.I'd begun to realize the importance of having good estimates and honest, timely reappraisals before starting to read the book, but the author certainly drives home how very critical this is to a professional coder and the rest of the team.If you've programmed essentially for yourself (as a systems admin or database admin) but are moving toward true development, this is an essential book to read. It will show you bad habits to avoid and drive home the professional behavior that will earn you respect. I admit that is based on only about three months of experience in working with developers, but over the past two weeks (since I started the book) I'm sure that I sense a greater acceptance and respect.

A colleague of mine recommended this book and its predecessor (Clean Code). I have not read Clean Code yet but decided to read this one first. This is a good book on professional code of conduct for those graduating out of university and venturing into professional arena - to these folks this book gives pretty good advice or at least provides a pretty good starting point. For those who already spent several years in the industry such as myself, a lot of what he has to say would be obvious - in that case one's own professional experience would have taught most if not all of what the author advises on. For instance consider the quote from chapter 2 - "Professionals have the courage to say no to their managers". I learnt this lesson (the hard way) in my career. Now it would have been better if I had learnt it sooner from other people's experiences. That said, I do believe that there is a limit to how much you can learn from experiences of others (and more importantly in some cases, there is no substitute for one's own personal experience). This book covers a lot of topics from mentoring, project management, test driven development, career enhancement, handling pressure etc. A few ideas took me by surprise - for instance, the author states that the true benefit of mentorship is for the mentor - I never thought of it that way. I certainly don't agree with everything in this book although I can appreciate the author's perspective most of the time. For instance, there are a fair number of references and comparisons to medical profession which in my personal opinion are not really appropriate given how different both professions are. On the other hand, I can validate others by looking back - for instance the author talks about allowing teams to gel and once that's done high productivity is achieved and therefore a gelled team shouldn't be broken. There are some good ideas in this book which I plan to try out and see how well they work. Overall this book is definitely worth a read for entry level folks and not really necessary for folks with profession experience.

I'm about halfway through and already its one of the most meaningful books in my career. It tackles a lot of the non-code issues in programming, such as being consistent on deliverables and communicating effectively.No matter how good of a coder you are, following the advice in this book will make you a better professional and more employable. Absolutely worth every penny.

Uncle Bob brings up quite a few important insights on how to behave professionally in as much aspects and situations as he could cover. It's a really good recipe on how to succeed professionally as a developer/team lead/tech lead/architect etc.

It's mandatory reading. If your career transitioned like mine or you are entering your first job, it has all the info you need to think, act, and work like a professional software developer. It will put you way in front of your peers if they haven't read it.

This book is perfect for those who want to see and learn tips to improve as a professional, an excellent book for my taste.

This is the best book to understand how to skill-up. From the first chapter till the last, you as a software dev will get evergreen wisdom and knowledge on how to become a professional developer. This book contains some terms which some freshers might not recognise, but that is for good. Robert Martin is a too good of an author and software developer. Do buy this book! It's a very good investment in your career!