InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Book Review: Implementation Patterns

Posted by Amr Elssamadisy on Nov 06, 2007

Sections
Process & Practices,
Architecture & Design,
Development
Topics
Java ,
Agile ,
Object Oriented Design ,
Programming
Tags
Best Practices ,
Patterns
Kent Beck's new book, Implementation Patterns, is a book about writing code in Java.  The patterns in this book are based on Kent's reading of existing code as well as his own programming experience and habits.  These patterns are about developers communicating through code which is reminiscent of his earlier work on Smalltalk Patterns.  They are lower level than design patterns and about the same granularity as Larman's GRASP patterns.  The patterns in this book are meant to be a coherent view of how  to write code people can understand that serves human as well as economic needs. 

Kent provides us with his experience in an elegant and concise (the entire book, with appendices, is 156 pages) format.  He does not give rules, but gives values, principles, and rules of thumb:

There is no universal rule.  Programmers need to think, communicate, and learn.  That's part of being professional.

This is a book that is useful for both junior as well as senior developers - each will come away with something different.  Read the full book review for more detail.

  • This article is part of a featured topic series on Agile
Waiting for it for a long time by Michael Hunger Posted
Re: Waiting for it for a long time by Amr Elssamadisy Posted
  1. Back to top

    Waiting for it for a long time

    by Michael Hunger

    The values and principles discussion sound like the one from XP2. How does it differ from it and does it? What about the accountability Kent emphasises on so much and what about testing. Kent being one of the two JUnit guys and now an Agitar fellow the Implementation patterns should deal with testability as well?
    I also hope to reflect the stuff I'm doing. And become better at teaching these values, principles and patterns to my fellow developers.
    I'd really liked to have the Implementation Patterns as a Pattern Language as described by Kevlin, Frank and Doug in POSA5. There you have everything: vision, values, context, practices and pattern influencing context and each other in their application. I already wrote Kent on this. Unfortunately he thinks that covering XP and Implementation Patterns inside a pattern language distracts the reader to much from its core essence.
    Imho it would gain a lot from reevaluation as a pattern language.
    Another question ist the applicability of patterns. To decide when and how to apply a pattern and when to choos not to apply it. This ist the most difficult part for most developers.
    So I'm looking forward for my preorder to get here.
    Did you review the manuscript or the printed book?

    Michael

  2. Back to top

    Re: Waiting for it for a long time

    by Amr Elssamadisy


    The values and principles discussion sound like the one from XP2. How does it differ from it and does it?

    It is the same approach - values and principles - as in XP Explained, v2. The values are a subset of the XP values, which I assume is because programming is only a subset of the XP practices. As for principles, they diverge even more.

    As for pattern languages... This book reads very well. Kent's style is - IMHO - much clearer. Part of it is personal preference, the other part is the book itself is simple.

    Finally, I reviewed an early edition from the publisher and just got my official print yesterday.

Educational Content

Jesper Boeg on Priming Kanban

In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.