• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Language

 
Ranch Hand
Posts: 57
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello Kent,

which implementation language (Java, C#, Ruby, ...) did you choose for the book? Why did you choose this language?

Thanks
Walter
 
author
Posts: 11962
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The book uses Java in its examples but I'll let Kent shed light on the rationale behind that.
 
author
Posts: 45
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Dear Walter,

Implementation patterns are partly different in different languages. What is considered a reasonable practice in Ruby would be sneered at in Java code. Sometimes this is because of the structure of the language, sometimes it stems from the prevailing culture around a language. The principles and values in Implementation Patterns work in any language and fundamental thesis, the importance of communicating with other people, does too.

The first book I wrote was The Smalltalk Best Practice Patterns, basically the same scope as Implementation Patterns but applied to Smalltalk. I started IP with the outline of the earlier book, but many of the patterns are quite different.

I chose Java because it is the lingua franca of programming at the moment and because I already knew Java. I can imagine writing a whole series of XXX Implementation Patterns books to explore the differences between languages, but that would be a different project.

Regards,

Kent Beck
Three Rivers Institute
 
Walter Bernstein
Ranch Hand
Posts: 57
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Kent Beck:
The first book I wrote was The Smalltalk Best Practice Patterns, basically the same scope as Implementation Patterns but applied to Smalltalk.


That's a great book.
 
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Walter Bernstein:

That's a great book.



Agreed!

Which raises another question for me: are there things that you would do differently today if you were writing SBPP now (or do a second edition)? Perhaps something that is reflected in Implementation Patterns?
 
Kent Beck
author
Posts: 45
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Ilja,

What I learned writing Implementation Patterns is how much language influences what idioms are appropriate. I started with the same outline and ended up with (it seems to me, I haven't measured) not very much overlap.

If I was writing the Smalltalk Best Practice Patterns again I would expand the scope to cover the patterns you use when the code base is going to get very large. Other than that I think the book stands up pretty well.

Regards,

Kent Beck
Three Rivers Institute
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic