How to get out of project development mistakes

    During the development of software, changes are inevitable, especially in the development of project types. The goals of project changes are often unclear. If trial and error is performed on multiple targets, or multiple trials and errors are performed on one target. And these trial and error will not bring the final experience and value to the user, so these trial and error development is meaningless.

     In this case, it is a waste of time to work hard, to fail again, and to exhaust it three times. This leads to delays in realizing the real value that users need, a proliferation of defects in the development process, and the end result is a proliferation of costs.
   
    From the programmer's point of view, what should we do in the face of this situation?

   1. Inside: First, after entering the project team or during the development process, you need to understand the overall structure of the system, understand the overall style of the system, and whether there are specific development requirements to avoid unnecessary rework! It is necessary to have a correct understanding of the members, systems, and value points of the development team. And, in the process of development, it should be noted that the overall structure and style of the system are changing. Need to observe calmly, anticipate obstacles, and act flexibly!
  
   2. Outside: Change is inevitable and sometimes irregular. To have good insight and the ability to analyze data. Always keep analysis first. For example: if there are many bugs, the pressure is also high. Time management method GTD can be used to analyze and classify all bugs. Understand what is the cause of each type of problem? Turn problems into actions. This saves effort and fixes problems quickly and efficiently.
           For each requirement change, developers also need to analyze and predict to establish the nature of the change. As the saying goes, everything is foreshadowed.

  3. For yourself:
     In the process of development, the programmers themselves should keep the modules we make as simple as possible on the basis of analysis.
     Only by keeping it simple can it be clear, reliable, and the correct solution to the problem can be obtained, reducing the probability of errors!
   
   
    Dear time management expert Mr. Yongxi, In the training course, he quoted this sentence:
Although there is a lot of information in this world,          it will eventually be dominated by the information creators.          These people can          synthesize the right information at the right time,          think critically,          and make important decisions wisely.                  - Edward. Osborne. Wilson                    Edward Osborne Wilson in the development team, both the external environment and the internal environment, are in a state of change. So the conditions of the problem are also changing. We should be an information creator, think correctly, critically, and make the right decisions at the right time!    

       
        








   
         

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=326256860&siteId=291194637