The "fancy names" are kind of useful actually. Most of the patterns I've learned but I didn't know the "fancy/official" names for them. This caused some confusion when talking with my coworker as he would be simply using the names instead of the concepts and I'd have to stop and figure out which one he meant, or I'd spend extra time explaining what I was talking about when I could have just said the name and been done with it.
The names are useful as a common/shared way of referencing complex concepts. That said, the concepts are much more important than the names, as you can get by just fine with only the concepts, but fail miserably on with just the names. :) -Andy On 8/22/07, Ron Wheeler <[EMAIL PROTECTED]> wrote: > > > Dave Mennenoh wrote: > >>> How do you handle onLoad's famous scope? ... It is not magic or > >>> advanced. If a pattern was shown to a new programmer without giving > >>> it a fancy name, they would just accept it as the best way to do the > >>> task and would never give it moment's thought. > > > > Right. Delegate - ie Proxy. I agree. I wasn't saying patterns > > shouldn't be taught, or used - I doubt you could teach a Flash class > > these days without teaching Observer, but you might not ever call it > > that. In fact, I wonder who does call it that in a class? Actually, > > the more I think about it, I think for students it might be best not > > to call these patterns and just teach them. Then, once they know how > > to use them, tell them what they are. It's a bit like teaching > > encapsulation I think - if you just show your students how to write > > classes, and they see how classes work for organizing code, they will > > likely just use them. > > > > > That is what I have been saying from the start of this discussion. You > do not have to teach the fancy names. Just teach them to use proper > coding practices. OOP and Design Patterns are just names that we use to > group a bunch of best practices into theories so we can discuss the > theory and have a framework to critique code. I have a feeling that for > most of us, the word polymorphism is not much of a help and I see no > reason to even use the word on 14 year olds until the last week of class > and only then as a warning that someday someone might try to use it on > them in a discussion about design. > > Ron > > > > Dave - > > Head Developer > > http://www.blurredistinction.com > > Adobe Community Expert > > http://www.adobe.com/communities/experts/ > > _______________________________________________ > > Flashcoders@chattyfig.figleaf.com > > To change your subscription options or search the archive: > > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > > > Brought to you by Fig Leaf Software > > Premier Authorized Adobe Consulting and Training > > http://www.figleaf.com > > http://training.figleaf.com > > > > > _______________________________________________ > Flashcoders@chattyfig.figleaf.com > To change your subscription options or search the archive: > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > Brought to you by Fig Leaf Software > Premier Authorized Adobe Consulting and Training > http://www.figleaf.com > http://training.figleaf.com > _______________________________________________ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
