My programmer experience made me understand something about software development. The following are some surprising things in programming:
- A programmer spends about 10%-20% of his time coding, and most programmers, regardless of their level, on average, only 10-12 lines of code per day will eventually enter the final software product. This is because excellent Programmers spend 90% of their time thinking, investigating, and researching the best designs. Poor Programmers spend 90% of their time debugging code, modifying the code at will, and trying to make the code work.
"A great lathe operator commands several times the wage of an average lathe operator, but a great writer of software code is worth 10,000 times the price of an average software writer."-Bill Gates
"A good car worker has several times the salary of a common car worker, but the code written by a good programmer is worth 10 thousand times more than a common programmer. -- Bill Gates"
- A good programmer is 10 times more productive than an ordinary programmer. The productivity of an excellent programmer is 20-times higher than that of an ordinary programmer. This is not an exaggeration (since the study in the 1960s s, it has been a fact ). A bad programmer is not just not productive-they not only do not work, but also create a lot of headaches and problems to solve.
- Good Programmers spend a small amount of time writing code-the code will appear in the final product. Programmers who spend a lot of time writing code are actually very lazy, ignorant, or arrogant, so they cannot use existing solutions to solve existing problems. Excellent programmers are proficient in identifying and reusing common models. Good programmers are not afraid to constantly refactor/rewrite their code until they reach the ideal solution. Poor programmers basically lack conceptual consistency, lengthy code, and a lack of layers and patterns, making it difficult to refactor. Therefore, rewriting their code is much easier than restructuring their code.
- Software follows consistency rules like everything else. Continuous changes will only turn the software into a mess, undermining the conceptual consistency of the original design. Software products are inevitable, but software products become more efficient because programmers do not consider software Concept consistency, this speed may be less valuable when software products are not completed. The failure of Design Concept consistency usually leads to the failure of the software project (the second cause of the failure of the software project is that the released software is not what the user wants ). The speed at which software turns into mud is decreasing exponentially, and too many projects are facing a surge of time and cost before they are completed.
- A 2004 study report points out that most software projects (51%) have problems at key points. 15% of projects were completely failed. Of course, this was a great improvement over 1994. At that time, 31% of projects were completely failed.
- Although almost all software products have some development teams, they are not democratic. Generally, only one person is responsible for the design, and the rest people are responsible for implementing the details.
- Programming is a hard job. It is a powerful mental labor. Good programmers are thinking about their work 24 × 7. They generally write the most important software code in their bath and dreams. Because the most important work can only be done out of the keyboard, it is impossible for software projects to work overtime or add people to speed up the process.
