Commits  committed bb44693

Add "If it ain't broke, don't fix it."

  • Participants
  • Parent commits 79a9863

Comments (0)

Files changed (3)

File t2/humour/fortunes/fortunes-shlomif-ids-data.yaml

       date: 2008-07-04T09:17:00Z
       date: 2008-07-04T09:17:00Z
+    szabgab-on-if-it-aint-broke-dont-fix-it: 
+      date: 2010-08-29T15:41:21Z
       date: 2009-11-11T15:49:28Z

File t2/humour/fortunes/shlomif-fav.xml

+    <fortune id="szabgab-on-if-it-aint-broke-dont-fix-it">
+      <meta>
+        <title>What does "If it ain't broke, don't fix it." really mean?</title>
+      </meta>
+      <quote>
+          <body>
+I keep hearing and reading this nice proverb <b>if it ain't broke, don't fix it</b>. The latest
+apperance was in response to <a href="">Shlomi Fish</a>
+suggesting that some Ancient Perl code should be replaced by Modern Perl code.
+I am not saying that every pices of code should be rewritten every 6 months but in my understanding
+that sentence actually translates to <b>let's wait till it breaks and then panic</b>.
+I think people who say that sentence are afraid that the new version will break something. Sure 
+there is always a chance that a change introduces an error but if we are afraid to touch the code 
+what will happen when later on we encounter a case where it does not work? For example if we
+need to use it in a new environment. Will we have the courage to change the code then? How much will it 
+cost in money, time, and lost sleep?
+I think we have been trying to teach ourselves that we should have really good test coverage of our
+code and then we can easily refactor it and get rid of technical debt. So why do we keep hearing
+that sentence?
+          </body>
+          <info>
+              <author>Gabor Szabo</author>
+              <work href="">What does "If it ain't broke, don't fix it." really mean?</work>
+          </info>
+      </quote>
+    </fortune>

File t2/humour/fortunes/ver.txt