11 ms·
Three reasons: 1. The code is the same but the people using it forget / never knew the reasons it was built that way - and so it looks rotten for the job 2. B
by lifeisstillgood 10y ago
Three reasons:
1. The code is the same but the people using it forget / never knew the reasons it was built that way - and so it looks rotten for the job
2. Because requirements change and people try to make the old code do new things without cleaning up / refactoring correctly - so it now does neither job well, and looks rotten.
3. Because the environment / platform changes, the FTP server is moved to a new data center and the timeouts kill the jobs etc. It looks rotten.
"Rot" more accurately is just not keeping the code inside the code base up with entropy outside the code base
- cpeterso 10y agoOr when the operating system or build tools change or are no longer available. Your code hasn't changed and suddenly it no longer compiles.
- akkartik 10y agoYour reasons are very similar to mine: http://akkartik.name/about http://akkartik.name/about. A. Backwards compatibility considerations. B. Churn in personnel. C. Vestigial features. Awesome! Comparing the two, I merged your 2 and 3 into a single reason, considering both as cases of environmental change. In its place I have a new one: changing personnel causing evaporation in system knowledge. Did you consider this? Now I think about it, maybe it overlaps with your 1 (my C). So the final mapping is perhaps: 1 <-> B, C 2, 3 <-> A
- mamon 10y agoI think that point 1. is caused by the fact, that the industry tends to divide programmers in two categories: most competent ones become architects and lead developers and are hired when you need to build new software system from scratch. After the system is built you let the people who created it go, because you can't afford their salaries and hire younger, less talented people to maintain it. So, instead of "software rots" i would say "software evolves to reflect the competency level of it's current maintainers"