> -----Original Message----- > From: Rico Secada [mailto:coolzone@xxxxx] > Sent: Monday, August 29, 2011 3:42 PM > To: php-general@xxxxxxxxxxxxx > Subject: Code should be selv-maintaining! > > Dont get me wrong, I love programming! But what an absolute pain in the > ass it is when you re-use old code only to discover something "less > well > made". > > You all know about this right? > > You go into your homemade library of code to re-use some piece that you > already are using 12 other places in production. Now, last time you > worked on the code you thought it was almost perfect. While working on > the code this time you find an undiscovered bug or some part of the > code that looks like you where on drugs when you made it. > > Of course we develop experience and more skills all the time, and as a > good programmer we never stop doing that, but what a pain it is when > the above happens and you have to patch the code being used those 12 > other places too, and each place maybe has a slightly different usage, > so minor changes affect other stuff. And this goes on while your head > is spinning around trying to stay focused on the very task at hand that > originated the need for a quick re-usage of old code in the first > place. > > Why the hell can't code be self-maintaining!? :)) > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php In a framework this is not a problem, and easy to update. Development as a whole, is a living document ever growing and expanding it abilities. If taking advantage of the new ability is a long upgrade process then the design is stagnate . This is called the longevity of a design and is why many developers No longer use what is called as flat text programming. Thinking object oriented programming in frameworks is the only way I do business. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
