On Tue, Jun 24, 2008 at 10:49 AM, Brian Kotek <[EMAIL PROTECTED]> wrote: > involved. Each pattern has consequences, and not all of them are good. The
This is the key issue I tried to raise in my design patterns talk at MAX last year (there's a recording on UGTV of the preso I gave later to IECFUG I think). So much of the patterns talk shows pattern + code instead of pattern + tradeoffs which is by far the more important aspect of patterns. > unfortunate reality is that truly groking OOP takes a long time and a major > shift in mindset. There's no easy route to getting there, but one route that Agreed. But when I tell people that, sometimes they react badly thinking I'm being elitist or implying they are "too stupid" to learn OO. The reality is: it's hard. I started learning OO in '92 and my first few years worth of code was embarrassing. Fast forward 16 years and I'm still learning and shifting my focus on OO issues. One of the key lines in Hal's preso was "forget the database" and if you want to design a reasonable OO system, you really do have to try to do that. Clearly, if you have a very data-centric app with almost no "behavior" (i.e., it's almost pure data entry or pure reporting) then OO might be a waste of time for you - or maybe only parts of the app will benefit from OO, perhaps at a very high level in the service layer. -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
