This is response to previous "native speaker” commenter.

Blog post is too good, too interesting and it looks like too advance for you. If you didn't understand the subject then buy "ASP.NET in 21 days”. I suppose it will help you better orient in programming.

I am sorry but I explode when see such comments about "native speaking". I am also not native speaker but it doesn't limit me to understand or explain architectural subjects. At least author has knowledge and courage to explain advanced things to others.

BTW: Author makes sessions for "native" speakers and I haven't seen anybody blaming about his "too bad" skills. He is speaking "very" good and about "very" interesting subjects.

I only disagree that collections are code smell. Generics are simplifying signature of collection but not Composite Pattern. Composite Design Pattern helps to build tree structure collection. For example whenever you need to manipulate with nested objects such as Family Tree, XmlNodes, WebControls, etc Composite Design Pattern is the best approach for it.

“The Rule of Thumb:
Usage of composite pattern is usually appropriate whenever there are hierarchical tree structures where all the tree nods are of the same type. “
Design patterns in real world use case scenarios, posted by Nikola Malovic - http://blog.vuscode.com/malovicn/archive/2007/08/16/design-patterns-in-real-world-use-case-scenarios-composite-part-2.aspx

Message for yesthatmcgurk, try to look at the Nikola Malovic blog post I mentioned above. Composite pattern is very simple, useful and unique.

Firefox problem has been fixed.

Sorry guys I have some layout problems under the Firefox. I will fix it as soon as posible.