3 ms·
I wouldn't call them legacy if they are a money maker of your core business. 1. when you change the code you should be updating the documentation. 2. you should
by sharemywin 12y ago
I wouldn't call them legacy if they are a money maker of your core business. 1. when you change the code you should be updating the documentation. 2. you should have a system that documents support tickets and the solutions when you have production problems 3. if you know where the buggiest code is by number of production problems you can focus on re-factoring that part of the system. 4. make sure your experts know that part of they're yearly objectives(raises) is training and mentoring. Part of your job descriptions for senior level people should be about sharing knowledge and mentoring.