When reading this article, it seems to me that it is targetted at audiences having a limited experience in OOD because its content is quite poor for the more experienced guy I am.
The paradox is that, if that is the targetted audience, I believe explaining the basics of OO is a lot more important (inheritance and polymorphism). You're mentionning polymorphism with no explanation of what it is. By explaining and illustrating polymorphism, you would have achieved the same results.
Concluding this OOD related article, I would also have added a short introduction to patterns which is the more important next step.
A general remark for Builder.cmo: adding on top of all articles what is the targetted audience would be very useful information.
Discussion on:
View:
Show:
Be careful when choosing a Title for the Article. The title for this article should have been Polymorphism or Introduction to OOP. The title suggested that it was a high level article for software design.
Great intermediate article. I've read more than enough beginner articles on polymorphism. Getting to read something a little bit beyond that was refreshing.
I've studied my share of patterns, but these succinct rules were helpful and appropriate.I've not heard either of these terms before. I will definitely spread them around, and thank you for them.
I've studied my share of patterns, but these succinct rules were helpful and appropriate.I've not heard either of these terms before. I will definitely spread them around, and thank you for them.
This article is a re-cycle of original articles written by Robert Martin. You can find his original material, including more intermediate/advance design principles, at www.objectmentor.com and in his recent book Agile Software Development, Principles, Patterns, and Practices.
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
