aspose file tools*
The moose likes Agile and Other Processes and the fly likes Implementation Patterns - yet another set of Design Patterns? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » Agile and Other Processes
Bookmark "Implementation Patterns - yet another set of Design Patterns?" Watch "Implementation Patterns - yet another set of Design Patterns?" New topic
Author

Implementation Patterns - yet another set of Design Patterns?

Raghavan Muthu
Ranch Hand

Joined: Apr 20, 2006
Posts: 3355

Hello Kent,

I have gone through the book description. It looks very great and i am sure there are so much valuable inputs are waiting for the developers.

Is it again going to be some set of Design Patterns like GOF? or any other new strategies/methodologies?

Also looks like a bit of UML is associated with it. Aint I?

Thank you.


Everything has got its own deadline including one's EGO!
[CodeBarn] [Java Concepts-easily] [Corey's articles] [SCJP-SUN] [Servlet Examples] [Java Beginners FAQ] [Sun-Java Tutorials] [Java Coding Guidelines]
Kent Beck
author
Ranch Hand

Joined: Nov 07, 2003
Posts: 45
Dear Raghavan,

Implementation patterns are smaller scale than design patterns. While a design pattern describes relationships between objects, implementation patterns describe relationships within objects, like how the methods relate to each other or how the fields relate to the methods.

I use a few diagrams in describing the patterns, but they aren't in any formal notation.

Regards,

Kent Beck
Three Rivers Institute


Author of <a href="http://www.amazon.com/exec/obidos/ASIN/0596007434/ref=jranch-20" target="_blank" rel="nofollow">JUnit Pocket Guide</a>
Raghavan Muthu
Ranch Hand

Joined: Apr 20, 2006
Posts: 3355

Originally posted by Kent Beck:

Implementation patterns are smaller scale than design patterns. While a design pattern describes relationships between objects, implementation patterns describe relationships within objects, like how the methods relate to each other or how the fields relate to the methods.



That sounds interesting to know Kent.

Thank you
Hendy Setyo Mulyo
Ranch Hand

Joined: Dec 01, 2004
Posts: 219

Hi Kent,

Does your book teach us the best practices of how to use implementation patterns when we decide to build a framework? Is your book also suitable for Junior Level Programmer?
Thank you.


Hendy Setyo Mulyo
SCJP 1.4 (95%), SCWCD 1.4 (94%)
Lasse Koskela
author
Sheriff

Joined: Jan 23, 2002
Posts: 11962
    
    5
Originally posted by Hendy Setyo Mulyo:
Does your book teach us the best practices of how to use implementation patterns when we decide to build a framework?

Is there an assumption here about the best practices for building a framework being different? Is that necessarily true?


Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
ledc
Greenhorn

Joined: Nov 09, 2007
Posts: 2
Mr. Beck,

From what I have read of the various posts so far, a prime reason to use implementation patterns is to establish a common method of writing code so that the original code is more clear to future programmers that may maintain the code. Is this correct?

I am struggling to learn more than I did getting my undergrad degree. Do you feel implementation patterns should be taught in addition to development and design patterns?
Kent Beck
author
Ranch Hand

Joined: Nov 07, 2003
Posts: 45
Hendy and Lasse,

One thing I learned in writing this book is that implementation patterns for application writers and framework writers *are* different. In application development I assume I can refactor the whole code base, so I minimize complexity. In framework development, though, I can't refactor the whole code base but I need to maintain freedom to change the design in the future. In writing frameworks, then, I am willing to add some complexity to the design to preserve the ability to change the design in the future.

For example, if I add an operation to an interface in an application, I go to all the implementors and add the operation. In developing a framework, I might introduce a new version of the interface (FooListener2) with the additional operation. My code is more complex because it has to handle both interfaces (and probably with an ugly instanceof), but users aren't inconvenienced.

Regards,

Kent Beck
Three Rivers Institute
Kent Beck
author
Ranch Hand

Joined: Nov 07, 2003
Posts: 45
Laura,

The key change I would like to see in the undergraduate curriculum is to put programming in context. I would rather hire a programmer who knows less about how to program and more about why to program--business, social, and personal reasons. Implementation Patterns fits well into such a curriculum because it invites programmers to look beyond their interaction with the computer, to consider the needs of other programmers who will read this code later.

It sounds like you are a recent graduate. What do you wish you had learned in school that you didn't?

Regards,

Kent Beck
Three Rivers Institute
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Implementation Patterns - yet another set of Design Patterns?