Introduction
- Recently in an old project to add new business functions, took some detours, special record the experience.
- The project requires a low reliance on the original old business as much as possible.
Let's do this first.
- Starting from the requirements discussion, some of the project team's old colleagues have been the new needs and the old business constantly doping together, here is the original, where the original is like that, here to pay attention to what, there to pay attention to what ... So all the way down to the code, only to find that the development of colleagues are bound to the hands and feet, feel everywhere is a pit, have to be careful to walk around ...
Actually, it's better.
- The new function of the early bold analysis and split modules, how to design how to design, with the quickest way to run the process. Then combined with old code, the reuse of the reuse, the optimization optimization, do not because of the project's historical reasons for the first time to set up too many rules and constraints on their hands and feet.
- It is also important: unclear points to find the UE as soon as possible, product-related personnel to communicate clearly.
Summary
Methodology-project development, less baggage, more chic