Some obscure programming facts
As a programmer, I learned a lot about how software is created. Here are some facts that may surprise you.
A programmer spends 10–20% of his time writing the actual code, and most programmers write only 10–12 lines of code per day that end up in the final product, regardless of their level. Good programmers spend most of the remaining 90% of their time thinking, researching and experimenting to find the best solution. Bad programmers spend this time debugging, random changes in the code and then checking it for operability.
A good programmer is 10 times more productive than the average. An excellent programmer is 20-100 times more productive than the average. And this is not an exaggeration - studies conducted since the 1960s clearly show this. A bad programmer is not just unproductive: he not only fails to do his job, but also creates problems that others have to solve.
The best programmers spend very little time writing code. At least one that gets into the final product. Programmers who spend a lot of time on code are either too lazy, or too illiterate, or too arrogant to look for existing solutions to old problems. Excellent programmers are masters of defining and using standard approaches. The good ones are not afraid of constant refactoring in search of the perfect architecture. The bad ones write code that lacks conceptual integrity, brevity, hierarchy, design patterns, and it is incredibly difficult to refactor. Simply throw a bad code in the trash and start over, than to change something in it.
')
Programs obey the law of entropy, like everything else in the universe. Continuous changes cause program disruption, which violates the integrity of the original architecture. This is inevitable, but programmers who do not take into account the integrity issues write programs that collapse so quickly that they become unnecessary even before they are completed. Entropic integrity error is probably the most common error leading to project failure. And the second most common - is the creation of a program that goes against the wishes of the client. Destruction of programs slows development progress exponentially; therefore, many projects come to an avalanche of growing budget and deadlines, and this continues until they are completely destroyed.
In a study of 2004, it was found that most of the software projects (51%) face critical problems ( failure to meet deadlines, budget overruns, failure to fulfill obligations, functional disruption, etc. ), and 15% are completely fail. This is better than in 1994, when the latter was 31%.
Although most of the programs are created by teams, this is not a democratic activity. Usually only one person is responsible for the architecture, the rest are only coders.
Programming is hard work. This is a very intense mental activity. Good programmers think about working 24 hours, 7 days a week. They write the best code in the soul and in their dreams. Since the most important work is done away from the keyboard, the development of software projects cannot be accelerated, forcing people to work more in the office, or adding new people to the project .
From the translator. Probably, these facts are not so little known or unique. But they seemed to me somewhere amusing, somewhere instructive, and certainly worth the attention.
A programmer spends 10–20% of his time writing the actual code, and most programmers write only 10–12 lines of code per day that end up in the final product, regardless of their level. Good programmers spend most of the remaining 90% of their time thinking, researching and experimenting to find the best solution. Bad programmers spend this time debugging, random changes in the code and then checking it for operability.
“A good turner works several times better than the average, but a good programmer costs 10,000 times more than a regular one”
Bill Gates.
A good programmer is 10 times more productive than the average. An excellent programmer is 20-100 times more productive than the average. And this is not an exaggeration - studies conducted since the 1960s clearly show this. A bad programmer is not just unproductive: he not only fails to do his job, but also creates problems that others have to solve.
The best programmers spend very little time writing code. At least one that gets into the final product. Programmers who spend a lot of time on code are either too lazy, or too illiterate, or too arrogant to look for existing solutions to old problems. Excellent programmers are masters of defining and using standard approaches. The good ones are not afraid of constant refactoring in search of the perfect architecture. The bad ones write code that lacks conceptual integrity, brevity, hierarchy, design patterns, and it is incredibly difficult to refactor. Simply throw a bad code in the trash and start over, than to change something in it.
')
Programs obey the law of entropy, like everything else in the universe. Continuous changes cause program disruption, which violates the integrity of the original architecture. This is inevitable, but programmers who do not take into account the integrity issues write programs that collapse so quickly that they become unnecessary even before they are completed. Entropic integrity error is probably the most common error leading to project failure. And the second most common - is the creation of a program that goes against the wishes of the client. Destruction of programs slows development progress exponentially; therefore, many projects come to an avalanche of growing budget and deadlines, and this continues until they are completely destroyed.
In a study of 2004, it was found that most of the software projects (51%) face critical problems ( failure to meet deadlines, budget overruns, failure to fulfill obligations, functional disruption, etc. ), and 15% are completely fail. This is better than in 1994, when the latter was 31%.
Although most of the programs are created by teams, this is not a democratic activity. Usually only one person is responsible for the architecture, the rest are only coders.
Programming is hard work. This is a very intense mental activity. Good programmers think about working 24 hours, 7 days a week. They write the best code in the soul and in their dreams. Since the most important work is done away from the keyboard, the development of software projects cannot be accelerated, forcing people to work more in the office, or adding new people to the project .
From the translator. Probably, these facts are not so little known or unique. But they seemed to me somewhere amusing, somewhere instructive, and certainly worth the attention.
Source: https://habr.com/ru/post/102620/
All Articles