Implementation Patterns (Addison-Wesley Signature Series)

The title is misleading, as the book really isn't "Patterns." This is a good terse summary of principles to apply when writing code that others will need to work with.

While the book is light on details or examples, reading it can help you consider what coding and micro design conventions to apply to make your code more readable.

This is a good companion to Bob Martin's Clean Code: A Handbook of Agile Software Craftsmanship (Robert C. Martin Series), as Martin and Beck, excellent coders both, sometimes make opposite recommendations about the same situations. These contrasts drive home the point that rules for good code need to be considered, not just accepted without thought.

Most of the patterns are just common sense but in this case you will also get a practical explanation of its importance. The content's structure is very appropriate; each pattern is explained in concise way, with real world examples and some code snippets.

This book is too terse and the flow of thought is disorganized and lack clarity; at time too vague to know what he is thinking. Also lacking is subsections that branch off from main section. This book is about some implementation practices at code level.
I hope the author can revised this book.

The book is about writing readeable/maintanable code. It's an interesting/important subject.

The first few (1-3) pharagraph is good , they clearly explain the values/principles of the topic.
Then the book tries to apply these pricnciples in a structured way - classes, state, behaviour, methods. This is ok, but there's too much repetition going on. And the examples are very small/specific, some more complex/longer examples would be much better.

Then there's 2 whole paragraph about the performance characteristics of various collections (map,hash,etc.), and the description of the framework used to benchmark them. I don't think it has to do anyhting with the topic of the book, and it was probably included to increase the number of pages (by 30 to 150).

Finally, there's also a chapter "Evlolving Frameworks" which is mostly about JUnit 3->4 improvements done by the author. It's an interesting chapter focusing mainly on compatibility issues related to framworks.

So i think this topic from this author would deserve a much better book.

I typically enjoy reading pattern's books and this is going to be one of my all-time favorites. This time Beck talks about patterns "in the small", not the traditional kind of architectural patterns we are used to know. This book it's about those small decisions we make every time we write even a small piece of code. Somebody could think the word "patterns" is misused here, but I tend to disagree and, in the end, I don't even care that much. What really matters to me is that I found valuable advice inside this book and I really enjoyed reading it. In the past Beck's books were always worth reading for me, this one benefit from a more fluid and pleasant writing style too.