Note that during the software development 2.0 thing

Bloggers first to the second development project, along the way being beaten constantly. in conclusion


First, in any case do not move the original project development time

  In the actual secondary development, you may need to make some adjustments on the functions of the existing function or interface, this time because we feel that if small changes and move the original code, it is easy to go wrong in the post-test or maintenance, because of this change is small, so often we do not care, but in fact those of the original project may be very influential!

Second, when the secondary development of its own code written to categorize, annotate, try to distinguish coherent

  1. The benefit of this is that you can not find overturned at the time of submission. 2. give maintenance personnel and their own convenience.

Third, the secondary development requirements may not be more clear, so be sure to confirm in detail and interactivity

  Second development is an iterative optimization refers to the function, it is inevitable that the development process will not feel as good as iteration, this time for a new feature or that the control must be used with superiors or colleagues confirm the new requirements, to prevent differences when interacting .

Fourth, the development of the secondary part of the code can be reused, no heavy head

  Some secondary development just a few simple iteration and maintenance, a lot of code that can be directly re-used, but I do not know which features are already implemented, they must be interactive and responsible person, do not like me silly and that he wrote again

  

 

Guess you like

Origin www.cnblogs.com/ttzsqwq/p/11129030.html