BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ
News Articles Presentations Podcasts Guides

Topics

Choose your language

QCon New York

Find real-world practical inspiration from the world’s most innovative software leaders. Attend in-person or online.
QCon San Francisco

Learn what's next in software from world-class leaders pushing the boundaries. Attend in-person or online.
The Software Architects' Newsletter

Your monthly guide to all the topics, technologies and techniques that every professional needs to know about. Subscribe for free.

InfoQ Homepage News Book Review: Implementation Patterns

QCon New York (June 13-15): Learn best practices from senior developers at early adaptor companies.

Book Review: Implementation Patterns

Bookmarks

Nov 06, 2007 less than one minute

Write for InfoQ

Join a community of experts. Increase your visibility.
Grow your career.Learn more
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.

Rate this Article

Adoption
Style

This content is in the Architecture topic

Related Topics:

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • Waiting for it for a long time

    by Michael Hunger,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    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

    Back to top
  • Re: Waiting for it for a long time

    by Amr Elssamadisy,

    Your message is awaiting moderation. Thank you for participating in the discussion.


    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.

    Back to top

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

BT