> -----Original Message-----
> From: [email protected] [mailto:[EMAIL PROTECTED] Behalf
> Of Alan Livie
snip
> I would also advise people try building their own and move to
> frameworks as soon as. In the sample app I would also avoid
> services, factories etc and just create some objects and get them
> doing things!
+1!
I pipe up here every now and then and say this - if you want to *learn* OO,
forget about databases. The whole business of dealing with relational
databases, even with an ORM, can massively distort the domain model. It's
like trying to learn to drive a car by practicing on an earthmoving machine
with backhoe and dozer blade. So I would advocate introducing OO in the
parts of one's app furthest from the database.
If the *whole* app is close to the database - well, I wouldn't be the first
to suggest that OO may not be a massive win in that situation. A seasoned
OO programmer can make it fly, but as a learning experience it's just about
a worst case.
Jaime Metcher
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
