I wouldn't worry to much about understanding the GoF book (although Head First Design Patterns is great). I'd focus on just making your code easier to maintain. That's the end goal after all :->
Know how you feel though - it really does take a while to feel like you're starting to "get" OO, and software engineering isn't a solved problems, so as soon as you "get" OO, you become aware of the problems that it doesn't solve either . . . Best Wishes, Peter On 11/7/07 7:08 PM, "Alan Livie" <[EMAIL PROTECTED]> wrote: > > Sam, Peter, thanks. > > I'm all for trying to do things 'right' first time but with OO I would > never get a line of code written :-) > > All good advice. I'll stick to method chaining and keeping the DAO's > doing only what they are meant to be doing. > > Until today I had been using lots of singleton composition - Services > composed of other services, DAO's, Bean Factories etc but hadn't > actually used composition with beans themselves and ways to persist > the data. > > Onwards and upwards! At this rate, by 2012 I may even understand the > Go4 book :-) > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
