Sign in with Facebook
Loading...
9th out of 18 books
—
36 voters
The Clean Coder: A Code of Conduct for Professional Programmers
Programmers who endure and succeed amidst swirling uncertainty and nonstop pressure share a common attribute: They care deeply about the practice of creating software. They treat it as a craft. They are professionals. In "The Clean Coder: A Code of Conduct for Professional Programmers, " legendary software expert Robert C. Martin introduces the disciplines, techniques, too...more
Paperback, 210 pages
Published
May 13th 2011
by Prentice Hall
(first published January 1st 2011)
Friend Reviews
To see what your friends thought of this book,
please sign up.
Community Reviews
(showing
1-30
of
1,192)
Uncle Bob is again extreme and depicts a person, who is our asymptotical goal, not something anybody can achieve.
The super-human (a.k.a. The Clean Coder) is always responsible for her actions, can say No even in the toughest times and to the toughest managers and clients, sleeps at least 7 hours per day, spends 20 hours per week for her personal professional development, regularly does programming kata, does TDD 100% of the time, doesn't write features unless there are acceptance tests, doesn't...more
The super-human (a.k.a. The Clean Coder) is always responsible for her actions, can say No even in the toughest times and to the toughest managers and clients, sleeps at least 7 hours per day, spends 20 hours per week for her personal professional development, regularly does programming kata, does TDD 100% of the time, doesn't write features unless there are acceptance tests, doesn't...more
Yes, "The Clean Coder" is a sequel to Uncle Bob's "Clean Code." This is a great book and drills what being a professional developer really means as delivered by a well respected source.
The book is very readable and contains advice mixed with stories from the author's past and dialog. I like the use of dialog to show communication issues like saying "done" or over committing. Even the foreword was a story.
I think there was too much repetition of the stories across chapters. Almost like the chapte...more
The book is very readable and contains advice mixed with stories from the author's past and dialog. I like the use of dialog to show communication issues like saying "done" or over committing. Even the foreword was a story.
I think there was too much repetition of the stories across chapters. Almost like the chapte...more
In popular culture, computer programmers, sometimes confused with sysadmins, are often described as teenage punks, sitting in a dark, lit only by the glow of their monitor, empty cartons of pizza and Mountain Dew bottles scattered strategically around, frantically hacking away on their keyboard.
What does it mean to be a professional programmer? Is it wearing a suit and tie to work? Is it having certifications or diplomas decorating the walls of your office? Is it working hard, sometimes overtim...more
What does it mean to be a professional programmer? Is it wearing a suit and tie to work? Is it having certifications or diplomas decorating the walls of your office? Is it working hard, sometimes overtim...more
As someone already said, it's common to find books that teach you something, a lot of books that can inspire you, but there are a few who does both things good enough.
What I really liked about this book is that its principles can be applied (and extended) to a lot of different areas, including my own: Medicine. It's not a dense book, and "Uncle Bob" has an amazing way to teach at the same time he is telling you a enjoyable experience.
The book is divided into 14 chapters, each one treating a diff...more
What I really liked about this book is that its principles can be applied (and extended) to a lot of different areas, including my own: Medicine. It's not a dense book, and "Uncle Bob" has an amazing way to teach at the same time he is telling you a enjoyable experience.
The book is divided into 14 chapters, each one treating a diff...more
Simply phenomenal. I liked this book so much that I literally read the entire thing in a single sitting in about 4 hours. I simply could not put it down.
I'm adding this book to my list of "absolute must-reads for programmers" right alongside The Pragmatic Programmer.
Uncle Bob's new book, The Clean Coder, is a perfect companion to Clean Code. Whereas Clean Code dealt specifically with how a professional programmer treats his or her code, The Clean Coder is more about how a professional programmer...more
I'm adding this book to my list of "absolute must-reads for programmers" right alongside The Pragmatic Programmer.
Uncle Bob's new book, The Clean Coder, is a perfect companion to Clean Code. Whereas Clean Code dealt specifically with how a professional programmer treats his or her code, The Clean Coder is more about how a professional programmer...more
A brilliant book about professional behavior as a programmer. It gives hints about how to divide your time, how late hours are counter productive, how one gives more reliable estimates and a lot more.
It lists several benefits of different programming techniques (Pair Programming, TDD).
It is, however, not at all focused on the code itself. If you are interested in the code side of being a professional, you should probably lead Roberts other book: Clean Code: A Handbook of Agile Software Craftsman...more
It lists several benefits of different programming techniques (Pair Programming, TDD).
It is, however, not at all focused on the code itself. If you are interested in the code side of being a professional, you should probably lead Roberts other book: Clean Code: A Handbook of Agile Software Craftsman...more
I tend to read at least one of these "how to be a more professional programmer" books every year. Historically they haven't impressed me. This one was the rare exception - it really spoke to me, for some reason.
Nothing in this book is truly new or unique. But Martin raised a lot of really good points and some things that I had never really put much thought into in the past all of a sudden clicked for me.
I guess it really boils down to presentation - Martin (for the most part) presented "the same...more
Nothing in this book is truly new or unique. But Martin raised a lot of really good points and some things that I had never really put much thought into in the past all of a sudden clicked for me.
I guess it really boils down to presentation - Martin (for the most part) presented "the same...more
Bra bok med exempel från verkligheten. Mycket härstammar från den agila världen. Om man jobbat agilt kanske det inte är jättemycket nytt men som sagt jag gillar hans återblickar.
Saker jag lärt mig
* Jag skall försöka är numera bannlyst. Hans poäng är att man redan sagt hur mycket tid en uppgift skall och den tiden är professionellt satt. Då går det inte att klämma in extra uppgifter utan att rucka på slutdatumet.
* The zone är inte något man skall eftersträva. Man kan lätt tappa överblicken och t...more
Saker jag lärt mig
* Jag skall försöka är numera bannlyst. Hans poäng är att man redan sagt hur mycket tid en uppgift skall och den tiden är professionellt satt. Då går det inte att klämma in extra uppgifter utan att rucka på slutdatumet.
* The zone är inte något man skall eftersträva. Man kan lätt tappa överblicken och t...more
The word professional and its variants is thrown around a lot, especially "unprofessional". Uncle Bob has his opinions and doesn't mince words. Nevertheless I agree with him in most places and I recommend this book for anyone working in software developement (or management thereof). He does a good job in the important parts of giving perspective to support his advice. Goes on a bit more about TDD and some other pet prefrences/details then I think nessisary (there are other places to be get brow...more
This is the first book I've read on this topic by virtue of it being available as an e-book from my local library.
I found this to be a very interesting and quick read with some well aimed points on what it means to be a software 'professional'. It reads like a mix between a memoir and advice guide.
I liked his examples, though some of it started getting repetitive and the tooling was a bit more detailed than I found necessary. I guess that's expected since it was the appendix.
Some major points
Pra...more
I found this to be a very interesting and quick read with some well aimed points on what it means to be a software 'professional'. It reads like a mix between a memoir and advice guide.
I liked his examples, though some of it started getting repetitive and the tooling was a bit more detailed than I found necessary. I guess that's expected since it was the appendix.
Some major points
Pra...more
Can't tell that this book is 'must read' for every programmer, but it is 'must read' for me. Actually there are thousands of books on subject, and there are a dozen of them that's really good. So it's a question of finding one that's right for you. 'Clean Coder' is that one for me.
It's easy to read, like a fiction novel, but it covers almost every topic that programmer needs to make his life easier and his programs better.
The book doesn't answer every question, but to know what the right questio...more
It's easy to read, like a fiction novel, but it covers almost every topic that programmer needs to make his life easier and his programs better.
The book doesn't answer every question, but to know what the right questio...more
Many "war stories" about the profession of software engineer, I enjoyed reading most of them.
He focus a lot on the concept of being responsible for decisions without forgetting that you're hired for helping someone. Even if an engineer "say No" (for some management/client unreasonable request), that doesn't mean that one shouldn't do his best to help the company. As an engineer you can come up with different ways to help.
Another interest points: practicing vs. performing, his ideas about focusin...more
He focus a lot on the concept of being responsible for decisions without forgetting that you're hired for helping someone. Even if an engineer "say No" (for some management/client unreasonable request), that doesn't mean that one shouldn't do his best to help the company. As an engineer you can come up with different ways to help.
Another interest points: practicing vs. performing, his ideas about focusin...more
Wow.
Frankly I never heard about "Uncle Bob" before but the book hooked me from the first page and reads smoothly until the last one.
I completely agree with "Bob" that it is neither managers role nor business attitude to develop "clean code". And there will never be enough time to develop and test properly. It should not be "common approach" to exclude broken unit test to make a build and be ready for the the live demo in front of stockholders in one hour.
The professional behavior for the develop...more
Frankly I never heard about "Uncle Bob" before but the book hooked me from the first page and reads smoothly until the last one.
I completely agree with "Bob" that it is neither managers role nor business attitude to develop "clean code". And there will never be enough time to develop and test properly. It should not be "common approach" to exclude broken unit test to make a build and be ready for the the live demo in front of stockholders in one hour.
The professional behavior for the develop...more
Every developer on my team is going to read this book. It's got very little to do with how to program, and a lot to do with how to be a professional software developer. The chapter on "How to say No" should be required reading for every entry-level developer around the world. His description of what it means to "be professional" as a developer will likely scrape across the nerves of every coder under the age of 30, especially if they envision themselves as bohemian freelancers, masters of their...more
I read this for work, so I wouldn't recommend it for anyone not in the industry. There were some interesting stories about the way the field of programming developed, but for the most part, this was a book full of hints about how to do my job better. And I think that happened. I implemented several of his suggestions, and after doing so, received a big fat raise and the best job performance review I have ever had.
This title It shows how we, as developers, can behave as a professionals and as a result be perceived and treated like professionals. Robert C. Martin basing on his experience shows us how to improve or change our habits, our communication and collaboration skills to become more valuable part of our team, our company and finally our client. More about this book can be read in http://tomaszdziurko.pl/2011/11/clean....
An overview of soft skills for technical professionals, derived from the author's years of experience; how to say "no" to an unreasonable request, how to provide estimates, how to manage time, meetings, superiors, and team members. I liked the way many of the lessons were presented with a story of how things could go horribly (and humorously, from the outside) wrong, and how doing it in such a way might help avoid that.
Good, even a few gems of wisdom in there (such as the PERT technique for improving one's estimates), but could probably have been merged into the previous Clean Code book. I just don't quite see the need for another volume touting pretty much the same values.
Still, if you haven't read any other book from Uncle Bob then this one is not necessarily the worst one to begin with. Though probably not the best either.
Still, if you haven't read any other book from Uncle Bob then this one is not necessarily the worst one to begin with. Though probably not the best either.
Decent book on being a "professional" coder. Not about the hard skills but rather the soft skills of working in teams, making honest estimates, saying "no" to unreasonable requests. He does talk about TDD (test driven development) but without going into the technical aspects of it. Started it one day then finished it one afternoon by skimming parts.
Agile patterns and practices - výborná kniha.
Clean code - nadprůměrná kniha.
Clean coder - (pod) průměrné vyprávění o poučení z krize vývoje SW a metamorfóze obyčejného vývojáře v komunikativního a odpovědného geroje, z nějž "ne" manažerům, "ano" TDD a pravidelný spánek dělá navíc kódujíciho supermana s morálním profilem Gandiho. ;)
Clean code - nadprůměrná kniha.
Clean coder - (pod) průměrné vyprávění o poučení z krize vývoje SW a metamorfóze obyčejného vývojáře v komunikativního a odpovědného geroje, z nějž "ne" manažerům, "ano" TDD a pravidelný spánek dělá navíc kódujíciho supermana s morálním profilem Gandiho. ;)
Decent follow-up to Clean Code. Much of the book has been talked about in other avenues. The professional attitude discussion was decent, but mostly common sense. I liked the book, but have seen the content before. Nothing really new here. Definitely meant more for new developers and would wholeheartedly recommend it for that group of people.
Great guide to recognising the craft of developing software. It's full of advice on how to stick to the craft and how to position yourself in the workplace so that such craftsmanship is recognised by management. Especially good are the areas of the book that give you the confidence and the reasons to say "No" to a requirement.
Good advice on professionalism, delivered with a heavy hand. I'm impressed with Uncle Bob's ability to introspect and to eloquently state his findings. At times this text has the eerie familiarity of my own inner dialog. A must read for all "professionals" involved in software development.
There's a lot of good content in this book, but I didn't like the presentation. I don't get on well with the aggressive tone: if you don't do what Martin suggests, then you aren't professional. This book is a set of dogmatic rules for novices, which is fine, but not for me.
This book is written around programmers, however, the lessons and guidance presented in it are applicable to almost any job, especially technology jobs. I cannot recommend this book strongly enough. I will be actively recommending this book to every person in my organization.
Decent book, worth reading even if you're not a software developer, but just a person involved in IT. Good points made, important things explained. No revelations though.
One nitpick: a professional software developer should be able to research topic properly, and don't confuse 'manna' with 'mana' :D
One nitpick: a professional software developer should be able to research topic properly, and don't confuse 'manna' with 'mana' :D
The book gives some underlying principles in terms of attitude and commitment for the "IT guys" to become "professionals". Needless to say that sometimes business enforces violation of some of the described practices, thus not everything described is applicable.
It's good for beginners/intermediate (time-being-empoyeed rather than programming skills) software developers.
It's good for beginners/intermediate (time-being-empoyeed rather than programming skills) software developers.
A good overview of the things a professional must keep in mind.
If you're new in the field, it's a must read to help you avoid mistakes. If you've been around a few (or more) years, it's a good reminder of what to keep doing.
If you're new in the field, it's a must read to help you avoid mistakes. If you've been around a few (or more) years, it's a good reminder of what to keep doing.
Going beyond the topic of software development, this book provides solid advice on how to be a professional software developer: how to work with your manager, how to communicate with your clients, and how to manage expectations.
This book should be required reading for all software developers. TDD, estimations, communication and the importance of understanding the business needs are discussed along with examples from the authors successes and failures.
There are no discussion topics on this book yet.
Be the first to start one »
Goodreads is hiring!
Share This Book
No trivia or quizzes yet. Add some now »
“Slaves are not allowed to say no. Laborers may be hesitant to say no. But
professionals are expected to say no. Indeed, good managers crave someone who
has the guts to say no. It’s the only way you can really get anything done.”
—
2 people liked it
professionals are expected to say no. Indeed, good managers crave someone who
has the guts to say no. It’s the only way you can really get anything done.”
“What would happen if you allowed a bug to slip through a module, and it cost
your company $10,000? The nonprofessional would shrug his shoulders, say
“stuff happens,” and start writing the next module. The professional would
write the company a check for $10,000!”
—
2 people liked it
More quotes…
your company $10,000? The nonprofessional would shrug his shoulders, say
“stuff happens,” and start writing the next module. The professional would
write the company a check for $10,000!”
updated Jun 09, 2011 08:52am