I sometimes find that every time I read a book on software architecture, it messes me up and I design worse programs.
This is my fundamental concern with being too attached to the "right" design pattern. I suggest you write your program in the way that makes most sense to *you*. The goal of design patterns is to write code that *you* can understand. It is of course possible that you will come to believe at some point that you have made some design or architectural mistake. In fact, consider it a strong likelihood. I believe one of the most important lessons you can learn is to become comfortable refactoring your code. And do it often. Your will have a good design not if you make perfect initial decisions, but if you are flexible, and when you see that you could do something better, you do it. Don't be afraid to make a wrong first step. But more importantly, be fully prepared to fix a wrong first step. Regards, Hank _______________________________________________ [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
