java hosting


Title
Author
Publisher
ISBN
Reviewed by
Review text
Category

Your search returned 2 matching documents




The Clean Coder: A Code of Conduct for Professional Programmers (Robert C. Martin Series)
by Robert C. Martin


Prentice Hall
1 edition
May 2011
256 pages

Reviewed by Jeanne Boyarsky, June 2011
  (9 of 10)



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 chapters were written in standalone form. I felt like I read about the same employer (introduced from scratch) a few times. It was interesting hearing about the punchcard world with lessons and how things have changed. Same for FitNesse. I get that it has unit tests.

The advice is excellent. My favorite three (that were fairly unique for computer literature):
1) difference between performance and practice
2) TDD on offense vs defense
3) focus manna on time management

The only advice I felt strongly against is being in the "flow" being a bad thing. As long as you define the problem out of the flow, I don't see the problem with isolating yourself from the big picture temporarily.

---
Disclosure: I received a copy of this book from the publisher in exchange for writing this review on behalf of CodeRanch.

Discuss book in the Saloon More info at Amazon.com



Prentice Hall
1 edition
May 2011
256 pages

Reviewed by Mohamed Sanaulla, December 2011
  (10 of 10)



I would say that this is a must read book for all the programmers. Its packed with much needed advice in the current scenario. If you aren't much exposed to the industry (may be you are freshmen), I dont think the book might make much sense. Because lot of ideas discussed in the book would directly apply to your daily activities. We always think that programmers are professionals, but author in the book clearly mentions what it takes to be a professional programmer.

Author takes us along each chapter using either anecdotes related to his life and work or by using conversations between key people relevant to the topic. This way you dont get bored while reading through the topics and can understand the possible type of implementation of the idea.

Author has covered testing and its related strategies over 3 chapters, this shows how important testing is for a product. I got to know in detail about TDD, and other testing strategies and now I can connect these ideas to my work.

Not only technical aspects but also personality development related topics are covered in the book giving the reader a possible all round development.

I found the anecdotes were a lot repeated, but its makes sense because few of them had lot of lessons to be learnt. Few specifications of computers were hard to understand, but it helped me to imagine the skill of the programmers in those 70s and 80s when the technology was still at a nascent stage.
I learnt a lot of new tool names, new testing techniques and few tips for improving my productivity at work and also to learnt the importance of continuous learning and practicing. Overall it was a really good read, managed to complete most of the chapters in one sitting

---
Disclosure: I received a copy of this book from the publisher in exchange for writing this review on behalf of CodeRanch.

Discuss book in the Saloon More info at Amazon.com




Clean Code - A Handbook of Agile Software Craftmanship
by Robert C. Martin


Prentice Hall
edition
2009
430 pages

Reviewed by Janeice DelVecchio, April 2010
  (8 of 10)


Robert Martin's Clean Code was an awesome read. This book illustrated the major points of writing readable and maintainable code. There were lots of code samples, and examples of how to make the code tell its own "story" and become readable to any programmer who comes along. It would be an appropriate read for someone at at least an intermediate level of understanding of programming. All the code examples are written in Java.

The entire last chapter was a summary of all the "code smells" that he had discussed throughout the book. This could make the book useful on a longer term basis as a reference book.

Although the book did light the desire in me to go and find programs to refactor, I felt the book as a whole dropped the ball a little when it came to depth. Each relatively short chapter (there are 16 plus the section with the rehash of code smells) could have been fleshed out with more substance -- especially the chapters about unit testing, data structures, and error handling, and the sections that discussed the costs of maintaining dirty code. There is an appendix adding to the concurrency chapter. I thought this might have sat better in the chapter itself and the other chapters extended.

Overall a great read, and a good foundation to build on when the goal is readable code.

Disclaimer: I received this book from the publisher in exchange for writing this review.

Discuss book in the Saloon More info at Amazon.com

 
The Bunkhouse administrator is Ankit Garg.