Why good programmers write good programs.
Reading this provocative post. Why a good programmer never writes a good program , couldn't resist not to write his opinion about that, and who is such a good programmer, and what is a good program?
In my opinion, a good program is primarily a program that is used for a long time. The fact of long-term use of the program is crucial. After all, no one will use the program for a long time, considering it bad. Bad programs always want to find a replacement. Almost nobody uses bad programs for a long time. And usually, a pretty quick replacement is found. And there is a demand for good programs. And at the same time it does not matter at all with the use of which technology and which programming language a program is created. A good program can have flaws, and flaws can be significant. But, if the program is used, then in the next versions of the program, significant drawbacks, as a rule, become smaller. In this sense, a great example of a good Windows program. :)
If we draw analogies, perhaps not quite relevant, but a good programmer is the one whose services are used for a long time. In this case, the ownership of certain technologies will always go to the background, compared with such features of a good programmer as:
- accurate implementation of all requirements of the specified specifications for development
- the ability to critically evaluate the task received for consistency
- minimum percentage of requirements not fulfilled
- transfer of tasks for testing with a minimum number of bugs
- high speed of writing code
- well, and finally, a good programmer should like his work.
And as soon as the programmer ceases to "shuffle" from the process of writing code, from the process of debugging and optimization, etc., he ceases to be a good programmer.
')
Many are capable of mastering technologies, but then for a long time they can apply the technologies they have mastered for their intended purpose and solve the tasks set, given only to good programmers. At the same time, it doesn’t matter whether he sets himself the tasks himself, or whether the others do it.
And as the author of this comment fairly noted:
In most cases, no one needs a good programmer, but a professional is needed - a person who solves the tasks of others (and not a genius who comes out of a badun who programs a spherical horse in a vacuum).
Good programmers write good programs because they are always in demand, by those who know how to form requirements for good programs, know how to design convenient interfaces, choose the best development tools, attract investments and encourage good programs to users.
Original
In my opinion, a good program is primarily a program that is used for a long time. The fact of long-term use of the program is crucial. After all, no one will use the program for a long time, considering it bad. Bad programs always want to find a replacement. Almost nobody uses bad programs for a long time. And usually, a pretty quick replacement is found. And there is a demand for good programs. And at the same time it does not matter at all with the use of which technology and which programming language a program is created. A good program can have flaws, and flaws can be significant. But, if the program is used, then in the next versions of the program, significant drawbacks, as a rule, become smaller. In this sense, a great example of a good Windows program. :)
If we draw analogies, perhaps not quite relevant, but a good programmer is the one whose services are used for a long time. In this case, the ownership of certain technologies will always go to the background, compared with such features of a good programmer as:
- accurate implementation of all requirements of the specified specifications for development
- the ability to critically evaluate the task received for consistency
- minimum percentage of requirements not fulfilled
- transfer of tasks for testing with a minimum number of bugs
- high speed of writing code
- well, and finally, a good programmer should like his work.
And as soon as the programmer ceases to "shuffle" from the process of writing code, from the process of debugging and optimization, etc., he ceases to be a good programmer.
')
Many are capable of mastering technologies, but then for a long time they can apply the technologies they have mastered for their intended purpose and solve the tasks set, given only to good programmers. At the same time, it doesn’t matter whether he sets himself the tasks himself, or whether the others do it.
And as the author of this comment fairly noted:
In most cases, no one needs a good programmer, but a professional is needed - a person who solves the tasks of others (and not a genius who comes out of a badun who programs a spherical horse in a vacuum).
Good programmers write good programs because they are always in demand, by those who know how to form requirements for good programs, know how to design convenient interfaces, choose the best development tools, attract investments and encourage good programs to users.
Original
Source: https://habr.com/ru/post/16351/
All Articles