This post originated from an RSS feed registered with .NET Buzz
by Udi Dahan.
Original Post: Template methods, without generics
Feed Title: Udi Dahan - The Software Simplist
Feed URL: http://feeds.feedburner.com/UdiDahan-TheSoftwareSimplist
Feed Description: I am a software simplist. I make this beast of architecting, analysing, designing, developing, testing, managing, deploying software systems simple.
This blog is about how I do it.
Martin Fowler recently brought up a code smell (or maybe it's a whiff) he named "Call Super". It rang particularly true for me this time (some of his posts take a while to sink in) for the project I'm currently working on.
I'd say that most of the thought I put into a given architecture is identifying the places where a programmer MUST remember to do something, minimizing the number of places it occurs, and maximizing the abilitiy to find out if/when it happens. The use of the Template Method pattern is commonplace, but its not always trivial to find out where you need it. From my experience, nothing beats a couple sequence digrams showing what can be run in base classes, and how their subclasses will need to fit in.
There is another field which I give special attention to, and that's...
Previous Topic
