Broken Window Theory

"Don't leave "broken windows" (bad designs, wrong decisions, or poor code) unrepaired. Fix each one as soon as it is discovered. If there is insufficient time to fix it properly, then board it up. Perhaps you can comment out the offending code, or display a "Not Implemented" message, or substitute dummy data instead. Take some action to prevent further damage and to show that you're on top of the situation.

We've seen clean, functional systems deteriorate pretty quickly once windows start breaking. There are other factors that can contribute to software rot, and we'll touch on some of them elsewhere, but neglect accelerates the rot faster than any other factor."

impreuna cu unele articole:

http://www.economist.com/science/displaystory.cfm?STORY_ID=12630201

http://www.washingtonpost.com/wp-dyn/articles/A46381-2005Jan29.html

http://www.codinghorror.com/blog/archives/000326.html

http://www.itsfengshui.com/Repair,_Mend_or_say_Good_Bye..html

articole ce le-am gasit mai relevante decat ce era pe wikipedia.

Consider ca merita sa iti folosesti putin din timpul pretios pentru schimbari importante, se pare, din viata ta.

Probabil nu ramane decat sa inlocuiesc geamurile sparte, sa scap de / sau sa repar toate lucrurile stricate si sa ma mut din cartierul in care stau/locuiesc. :)

si mai era un proverb.. "bate fieru' cat e cald" ...