Timeline for Do We Have a Responsiblity to Improve Old Code?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 16, 2015 at 18:34 | comment | added | cregox | Cost (or value, etc)is indeed the keyword for the right answer. It should add value in the whole sum, also considering that touching old code might break stuff (remove value) no matter how much more optimized it might look like. | |
| Feb 18, 2012 at 16:18 | history | made wiki | Post Made Community Wiki by tdammers | ||
| Feb 18, 2012 at 11:53 | comment | added | MathAttack | @justinC - exactly! Your example captures both another reason, and opportunity cost. | |
| Feb 18, 2012 at 9:35 | comment | added | JustinC | To borrow from a real example not in software, some transport companies will pay employees to clean and polish their rigs, for a variety of reasons, often because it helps the drivers/operators build pride in 'their' unit, so they take better care of it, and pay closer attention to it; averting problems quickly and conveniently. On the same token, if there are miles to make, get in the truck and drive it and worry about cleaning it after a few more thousand miles (going coast to coast). | |
| Feb 18, 2012 at 2:19 | history | answered | MathAttack | CC BY-SA 3.0 |