What I ask myself on new projects is "what parts of this can I reuse?" Can I put this behavior in a class or a component? It's more work up front to make your classes for your daily tasks (not much more work) but on project 2 or project 3 your work will pay off.
What's more, OOP design patterns often have powerful solutions to complex problems. If you get comfortable with OOP -- not just "using objects," but the true nature of "object orientation" -- you'll have an easier time when a really big problem hits you on the head.
_______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
