Have to join a big project

Good time of day!

From December to join a large project (delphi xe2 + firebird 2.5).
Megaton is not a documented code and a programmer who is self-employed (and not very interested in the fact that I really caught on). I will speak later as a programmer/representative of the customer. Assume that information about the project will have to hard. Advise what measures to take and how to spend them in this situation in order as quickly as possible and preferably without spoiling relations with the main programmer to join the project. In principle, we share with him, nothing will have, on the contrary, gelatelno that he had remained in the project but knowing the riskiness of this situation I want to be sure.

For yourself outlined the following plan.
1. Go with the programmer on the structure of the databases.
2. Go through the programs interface.
3. To run code programs.
4. To communicate with users of modules in order to identify what's not to like or not.
5. Make a plan of activities that should be corrected, write.
6. To try to document what they saw and heard.
In order not to ask again all in the future at all stages to record ekranow the picture in the video plus the sound of the discussion.

Thanks if anyone can something advise or send the link.
October 3rd 19 at 03:19
1 answer
October 3rd 19 at 03:21
Megaton is not a documented code and a programmer who is self-employed (and not very interested in the fact that I really caught on). I will speak later as a programmer/representative of the customer. Assume that information about the project will have to hard.

Already judging from this, it is best to try to fit in some other project. You can amass a bunch of hemorrhoids and in the end, you can blame all the bugs and weeds. As a variant — to start to rewrite bad code, and comment on what is already there.
Totally agree. Even in the relatively small and seemingly simple projects, archaeological excavations will take months (check for yourself). And in a large and complex project, and even with undocumented code and archiectural archaeology may be delayed for an indefinite period of time and the complexity/time compared to writing the entire system from scratch, and even more.
However, if due to some circumstances still have to do all this, then I would recommend to begin with a description of the overall architecture and the gradual detailing of the modules and down to the basic functions/procedures. Describe the key components of the system, and as necessary to have to go down to the lowest level and to dig the source code. - Aryanna_Hegmann commented on October 3rd 19 at 03:24

Find more questions by tags Other