> I guess the reasons I am concered about the "rightness" of what I'm doing, > is because there ARE wrong ways of doing things and I'd like to fall into > bad practices, anaemic domain models for example. Making things easier for > yourself is one thing, I see writing good, stable and scalable code as > something else entirely?
I've yet to find a tutorial that will help you avoid poorly-designed models. This involves experience (and refactoring). Stability won't really be a factor, as you can write poor OO code or good OO code or spaghetti code for that matter and have it be equally stable. As for scalability, it depends on what exactly you mean - in the general sense of the term, how your application performs as load increases - again, poor OO code or procedural code can be just as scalable (or more). If, on the other hand, by scalability you mean how easy it is to manage and revise the code itself, you will be in a position to measure this yourself better than anyone else can measure it for you. This is what I meant by "making things easier for yourself" - if you follow OO precepts you will generally find your code easier to manage as changes are required. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;207172674;29440083;f Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:319445 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
