Good project handling methods for another developer

What good procedures should be followed when transferring a project to another developer in cases where the original developer will still be a couple of months to help with the transition? Consider a medium-sized web application if you need a specific example.

+3
source share
4 answers

I was at both ends. Capture the code base and transfer it.

You should:

  • Identify areas that are not completely obvious. So, if you have a directory called "xml", but your entire flash object gets its data from "flash / swfs / xml" you should document that.
  • , . , .
  • , , / .
  • , , , .
  • . , -, .
  • , , .
  • , , , . , .
  • .config, .

, -, , , , - .

+2

, , , . , - , ( var), , , , Java javadoc ; .

, , - , .

+3

, , , .

.

+1

, ( , , , ..), , , , smoke test .. , , , , .. -, .. , , .

+1
source

Source: https://habr.com/ru/post/1771541/


All Articles