Recently I found article about maintenance.
It is pretty old(2010) but looks still valid. One of the principal factors affecting maintenance complexity mentioned in the article is "Preserving knowledge".
From my experience, there could be such ways to achieve that:
- Document every process and algorithm used: keep at least high level overview.
- Split all project's code into areas and identify who would maintain each of them. If the person decides to leave project, then he should share his knowledge with his successor.
Which ways do you use at your projects?
If you use 2nd approach, then how do you achieve it? Do you use any tools?
Top comments (0)