http://silkandspinach.net/2009/01/04/too-much-templatemethod/ development, by example Mon, 19 Mar 2012 12:48:20 +0000 hourly 1 http://wordpress.com/ http://silkandspinach.net/2009/01/04/too-much-templatemethod/#comment-15360 Thu, 12 Mar 2009 15:30:23 +0000 http://silkandspinach.net/?p=915#comment-15360 I remember chatting with you about the use of Strategy in Ruby – compared to the pain in most other languages – early last year sometime, so I’m surprised you’ve not been rolling it out more. I suffer the reverse problem, where I’m happy to start with an empty object and build it. The ultimate Factory?

]]> http://silkandspinach.net/2009/01/04/too-much-templatemethod/#comment-15305 Sun, 04 Jan 2009 16:12:40 +0000 http://silkandspinach.net/?p=915#comment-15305 Always seemed to me that Template Method worked best to enable extensibility – that is, to allow subclasses to attach additional behavior to algorithms. Also works well within Strategy itself to allow partial strategization. You’re right, though – too much is not a good thing.

]]>