Take over the project as the operation, the technical team should provide the proper and normative handover documents and technical support

What should you pay attention to as a team to ensure the stable operation of later projects?
The risk of such things, account number, malicious modification, pits?
Some of the details of a large project may require support from a former team? After the handover of documentation and formalities, it is reasonable to ask for a technical consultancy service that is limited to a later hour or number of times.

Reply content:

What should you pay attention to as a team to ensure the stable operation of later projects?
The risk of such things, account number, malicious modification, pits?
Some of the details of a large project may require support from a former team? After the handover of documentation and formalities, it is reasonable to ask for a technical consultancy service that is limited to a later hour or number of times.

Problems such as malicious modification can depend on legal agreement and conscience, and confidentiality agreements are required, and the other party should be required to provide all possible host, account, password and other information and modify the password. Technical support is best friendly negotiation, leave contact, when there is a problem can ask, this can let you less detours, but will not help you solve any practical problems.
As for documents and so on, really do not expect, the document will never keep up with the changes in the code, so outdated documents in addition to pit you have no other use. Oneself slowly play, the pit is inevitable, the habit is good.
For emergency bug fixes, this kind of thing usually doesn't require you to know the whole project, just change the problem to the right.
Handover of the time when the predecessor always triumphantly tell you some glorious history, will never tell you any problems, the first damage their reputation, No. 20001 you let him change to put the people do, the third he did not know what the problem (no one will write the code that is wrong, so the bug will only be detected by others)
Come on, come on.

This is the conscience of life, you can think of it all . If the development team is professional enough, it may give you more detailed development documentation. Not professional may have no documentation, you want to temporarily write a make-up for you. Fuck the team is not hair, and then all are pits, the code is what eggplant cucumber tomato What, you study to go, a few months can understand a probably good. Now it's better to pray, good luck.

