documentation - What are effective strategies for documenting a large legacy .Net platform as the main developer just quit? -
There is a limited understanding available in the remaining limited junior developers. Please share your strategies. 1) If you still have access to a senior developer, then ask him a document that is available for the system. Provides a high level map, so that you can know which classes work with which class, and which parts of the app are responsible for the functionality in the system. This will give you time to understand how the whole thing should work together.
2) I have heard some time ago that a person's comment is only valid "do not change it" in that sense, ask the senior god in the list of all "sensitive" pieces of the system, and tell why they are sensitive Are / pay attention to You want to know what you can change without worrying, and which places are my area.
3) On system unit testing, if this unit has not been tested yet, a great way to make documentation and understand how things actually work.
Comments
Post a Comment