On 9/15/05, John Farrar <[EMAIL PROTECTED]> wrote: > Guys... what is most important isn't the term... but the way to do > what you are saying.
You nailed, it, John. When I use a pattern name I'm saying, "This is what I think the problem is. Here's a detailed solution and here are the consequences of that solution." I'm assuming that all I have to do is mention the name, and either you'll know what problem/solution/consequences I'm talking about or you'll be willing to look it up. If you look it up and find a couple of different definitions you might have to come back and ask which definition I'm using. (I try to skip that step by referencing the defintion up front.) At that point we're literally on the same page. Once you've studied / considered the pattern, your response will probably be one of the following. - "No, that's not the problem I'm trying to solve. Let me explain it again." - "Yes, that looks like it would work. I'll try applying the solution described in that pattern to my problem." - "That looks like it might work. Can you help me apply this solution to my problem? Can you help me understand the tradeoffs of using this pattern vs. that other pattern?" > In fact it would be good to create a lexicon of terms on the site this > list is from. As Bill said, it would be hard for us to do that. But it's just as easy to refer to existing lexicons (pattern catalogs) such as GoF, P of EAA, and J2EE. Patrick -- Patrick McElhaney 704.560.9117 http://pmcelhaney.weblogs.us ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
