If I am building an application, not a presentation, and it's not throwaway (going to be gone in 6 months) or I'm expected to maintain and/or upgrade it for awhile, then I will write MVC because of all the benefits it provides long-term and for future developers to follow behind me. Otherwise, I just code to get it done and there's nothing wrong with that. Knowing how to do both and when to do which is important when managing your stress level and time management skills.
MVC doesn't help you get a disposable, glorified power point presentation out the door faster and I've seen many intermediate coders over code something with views and controllers when it's just a screen with three buttons that swap a center movieclip with three different images. They might see it as practice, but it's not good practice to use the wrong tool to get the job done. If you're building a bird house, should you spend the time to get proper zoning, building permits and lay down a cement foundation, plumbing and wiring as if you were building a real house? :) _______________________________________________ [email protected] To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
