I saw a particularly interesting question that someone was discussing: Why can’t programmers have lifelong responsibility for their code?
Seeing this problem, I feel that as a programmer, it is necessary to explain and popularize it. Otherwise, it feels like we programmers are irresponsible.
From a professional role perspective
What is a programmer called? The more pleasant one is called: code farmer, the more unpleasant one is called: IT migrant worker. In the final analysis, programmers are just brick movers. Have you ever seen a dilapidated building where the workers who were moving bricks were arrested? The project leaders and company legal persons were arrested.
Therefore, from the perspective of professional roles, for an ordinary migrant worker, the lifelong responsibility system cannot be traced back to the ordinary individual, but must be traced back to the leader.
After all, the salary earned by working as a worker cannot support the lifelong responsibility system for programmers.
From the point of view of the nature of work
Software development is different from other industries because the code requires long-term maintenance and constant iteration. The code may have to be written by many people and iterated by different people. In the end, it is impossible to determine whose code has a problem. There is no accountability for this change and it is not suitable for accountability.
This is different from the lifelong liability policy in the construction industry. Once the building is completed, it will not be changed for life. The software is different.
Moreover, when the product is updated, the business logic is often updated and changed. The code from two years ago does not adapt to the current business logic, and it is really impossible to determine who is responsible.
Furthermore, software must run in a suitable environment and system to run stably. Many browsers and systems have been constantly updated in the past two years, which will also affect the stability of the code. How can you be sure it belongs to someone? Is there something wrong with the code?
Moreover, the final formation of a product must be completed through the joint efforts of the team. The design of the product, as well as the communication of product design concepts and functions may not be accurate. It is not necessarily a problem with the code, and after the code is written, it needs to be tested. , in the end, it requires the signature of the product owner and team leader before it can go online. Finally, it is inappropriate for you to pass the responsibility to a certain programmer.
The complexity and variability of code development are very strong, unlike some major production safety liability accidents, once completed, they will remain unchanged. The complexity of the business also determines the complexity of the code. Many codes are coupled, which affects the whole body. Changes in other codes may also cause changes in other functions. This kind of variability is not suitable for life-long accountability.
Therefore, when an accident occurs, the person who caused the accident is usually punished and will not be held accountable for life.
From the perspective of safety hazard
If you look at the things that require lifelong liability, they are generally production safety accidents that endanger human life and health.
If there is a problem with the code, it does not endanger human life and health. At most, the server crashes and the data is lost. The data can be restored after rescue. Therefore, the degree of harm is much smaller and there is no lifelong liability.
Click on the official account card below to follow me
In the public account dialog box, reply with the keyword "1024"
Get a free practical tutorial on making money from sideline business
