①Entropy of software and the theory of "broken windows"
Since software also tends to increase in entropy during the development process, we need to find ways to suppress the tendency of the program to be disordered and rotten. And the most critical point is not to tolerate "broken windows", that is, bad writing style or small bugs that are checked out .
Because, when the program as a whole is perfect, no one has the heart to destroy this beauty, and every operation is careful, try to make your writing conform to the overall standard style, and fix a small problem immediately, even if it can't be repaired, it must be fixed. Annotate or isolate. However, once one day I tolerate some flaws due to inertia, I have this feeling - since the program is already like this (bad style or full of bugs ), I can write it casually and don't care too much about the details , If there are bugs , you can save them for final repair, even if the problem is not big in the end... If this goes on, the building of the entire program will eventually collapse.
②Theory and knowledge update of boiled frog in warm water
Warm water boiled frog theory: Throw the frog directly into hot water and it will jump out immediately, but put the frog in cold water and heat it slowly, the frog will eventually be cooked. This theory tells us not to indulge in the big picture in front of us. The times are constantly changing, and knowledge is constantly being updated. If we cannot adapt to new changes in time, we will be eliminated.
The same is true of learning software. We can’t expect to solve all problems with what we have learned. Software technology and programming technology are updated too fast. When facing new changes and new environments, we must be able to learn while doing. Quickly realize new knowledge. At the same time, we must have the awareness of investing in knowledge, such as learning a new language every year, reading a related book every month, etc. Only by constantly investing in knowledge can we adapt to changes in the industry faster.
③ Avoid repetition and maintain orthogonality
Most software development can follow the form of agile development, which requires that each module be separated as much as possible in the initial design to reduce code duplication. The more independent the code is, the more efficient the development will be, because every time you modify it, you only need to delete a small part in a targeted manner, otherwise, any repeated places will have to be reworked. The so-called orthogonality means that the two parts do not affect each other, and the change of one will not affect the other. Maintaining orthogonality in software development is not only conducive to the division of labor, but also reduces redundant communication and unnecessary communication among development members. 's dispute.