Thursday, December 16, 2004
Design patterns presentation by Holub
Holub, a renowned author of OO & design patterns presented pieces from his new book : 'Real world application of design patterns'
He used the 'game of life' example to reinforce a number of design patterns, mainly from the 'gag of four' book. Demonstrated difference between static object model vs. diagrams that focus on pattern relationships; the importance of those.
Then went deep into design patterns and how they are implemented in the game of life. As always happens, critique found that few patterns could have been avoided (e.g. neighborhood / grid of 8x8 ; flyweight could be simplified into dumb array)
Also, certain patterns (e.g. visitor, strategy, command) patterns were left out, they could have been implemented as well.
upon my asking the question on automated design doc generation etc., he was extremely negative. 'Patterns cannot be documented in the code'; 'Roundtripping only documents garbage' etc. Overall, strong view points on how design should be done and use of patterns.
One definition I liked : "For those who understand them, patterns are redundant ; for those who don't understand them, they don't make sense anyway" .... Also, why use patterns at all if you are an expert? An easier way to document and explain the design of your application.
He used the 'game of life' example to reinforce a number of design patterns, mainly from the 'gag of four' book. Demonstrated difference between static object model vs. diagrams that focus on pattern relationships; the importance of those.
Then went deep into design patterns and how they are implemented in the game of life. As always happens, critique found that few patterns could have been avoided (e.g. neighborhood / grid of 8x8 ; flyweight could be simplified into dumb array)
Also, certain patterns (e.g. visitor, strategy, command) patterns were left out, they could have been implemented as well.
upon my asking the question on automated design doc generation etc., he was extremely negative. 'Patterns cannot be documented in the code'; 'Roundtripping only documents garbage' etc. Overall, strong view points on how design should be done and use of patterns.
One definition I liked : "For those who understand them, patterns are redundant ; for those who don't understand them, they don't make sense anyway" .... Also, why use patterns at all if you are an expert? An easier way to document and explain the design of your application.
# posted by Rahul Jain @ 1:20 AM 
