On Wed, 2008-02-27 at 08:25 -0600, Ray Hauge wrote: > There is also such a thing as too much. I heard a talk a while ago > about code maintainability. The speaker mentioned a co-worker of his > ran into his cube almost exhausted and proclaimed, "I finally did > it!. > I used every one of the design patterns in my program!" Just a few > months later the speaker ended up being in charge of maintaining that > program, and it was a nightmare. > > To make a long story short. I generally do what's easiest. It's > typically faster to develop and easier to maintain. Unnecessary > complexity can start a snowball effect. You bring up a good point... knowing how to refactor crappy code is also a great skill to have. Cheers, Rob. -- .------------------------------------------------------------. | InterJinn Application Framework - http://www.interjinn.com | :------------------------------------------------------------: | An application and templating framework for PHP. Boasting | | a powerful, scalable system for accessing system services | | such as forms, properties, sessions, and caches. InterJinn | | also provides an extremely flexible architecture for | | creating re-usable components quickly and easily. | `------------------------------------------------------------' -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
