Why good programmers write good programs.
While reading this provocative post, why a good programmer will never write a good program , could not resist not writing his opinion about who is a good programmer and what is a good program?
In my opinion, a good program is primarily a program that has been used for a long time. The fact of prolonged 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 replacement is pretty quick. And there is a demand for good programs. And at the same time, it doesn’t matter at all with what technology and which programming language the 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 shortcomings, as a rule, become smaller. In this sense, a great example of a good Windows program. :)
If we draw analogies, it may not be entirely appropriate, but a good programmer is one whose services have been used for a long time. With this, the possession of certain technologies will always go by the wayside, in comparison with such features of a good programmer as:
- accurate fulfillment of all requirements of the specified specifications for development
- the ability to critically evaluate the received task for consistency
- the minimum percentage of failed requirements
- transfer of tasks for testing with a minimum number of bugs
- high speed of writing code
- well, and finally, a good programmer should like it.
And as soon as a programmer stops "screaming" 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 the technologies, but then for a long time they will be able to apply the acquired technologies as they were intended and solve the assigned tasks, given only to good programmers. At the same time, it does not matter whether he sets himself tasks, or whether others are involved in the formulation.
And as the author of this comment rightly noted :
In most cases, no one needs a good programmer, namely, a professional is needed - a person who solves the tasks of others (and not a genius who comes out of badoon, who programs a spherical horse in vacuum).
Good programmers write good programs because they are always in demand, those who know how to formulate requirements for good programs, can design user-friendly interfaces, choose the best development tools, attract investment and move good programs to users.
Original
In my opinion, a good program is primarily a program that has been used for a long time. The fact of prolonged 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 replacement is pretty quick. And there is a demand for good programs. And at the same time, it doesn’t matter at all with what technology and which programming language the 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 shortcomings, as a rule, become smaller. In this sense, a great example of a good Windows program. :)
If we draw analogies, it may not be entirely appropriate, but a good programmer is one whose services have been used for a long time. With this, the possession of certain technologies will always go by the wayside, in comparison with such features of a good programmer as:
- accurate fulfillment of all requirements of the specified specifications for development
- the ability to critically evaluate the received task for consistency
- the minimum percentage of failed requirements
- transfer of tasks for testing with a minimum number of bugs
- high speed of writing code
- well, and finally, a good programmer should like it.
And as soon as a programmer stops "screaming" 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 the technologies, but then for a long time they will be able to apply the acquired technologies as they were intended and solve the assigned tasks, given only to good programmers. At the same time, it does not matter whether he sets himself tasks, or whether others are involved in the formulation.
And as the author of this comment rightly noted :
In most cases, no one needs a good programmer, namely, a professional is needed - a person who solves the tasks of others (and not a genius who comes out of badoon, who programs a spherical horse in vacuum).
Good programmers write good programs because they are always in demand, those who know how to formulate requirements for good programs, can design user-friendly interfaces, choose the best development tools, attract investment and move good programs to users.
Original