What can you do with me?
Posted: Mon Dec 23, 2024 4:29 am
, these are all manifestations of the value of our products and we need to take good care of them.For developers, page stability, access fluency, and ease of use are also goals that need to be considered. However, once you start to mess up, the so-called awe will disappear. Specifically speaking, the typical problems we encounter in development are: modifying functions without testing, and changing online content at will. Let's talk about modifying functions without testing first. This is determined by the special situation of our department. Because the department does not have enough staff, the current testing work is basically done by operation and maintenance personnel.
And before, our leader also said that the functions to kazakhstan dialling code be launched by development need to be tested internally before they are delivered to operation and maintenance, and finally accepted by the product manager. That is: development internal testing → operation and maintenance testing → product acceptance. But the current situation is that developers can make changes or release versions as they please, depending on their mood.For example, once the developer arbitrarily modified the venue reservation logic, which resulted in users being unable to make reservations during the morning rush hour. Finally, it turned out that the backend interface was tested yesterday and the version was released directly without changing the tested content.
Another time, the front-end developer hard-coded the payment amount when developing a function, resulting in the inability to modify the price when the function was delivered. There are too many examples like the above. In summary, it is too casual and too careless. Anyway, I just made the function and released it. I don’t care whether it can be used or not. Let’s talk about the arbitrary modification of online content. If the impact of the previous "modifying functions without testing" is not that great, then the severity of the problem of "arbitrary modification of online content" is much greater.
And before, our leader also said that the functions to kazakhstan dialling code be launched by development need to be tested internally before they are delivered to operation and maintenance, and finally accepted by the product manager. That is: development internal testing → operation and maintenance testing → product acceptance. But the current situation is that developers can make changes or release versions as they please, depending on their mood.For example, once the developer arbitrarily modified the venue reservation logic, which resulted in users being unable to make reservations during the morning rush hour. Finally, it turned out that the backend interface was tested yesterday and the version was released directly without changing the tested content.
Another time, the front-end developer hard-coded the payment amount when developing a function, resulting in the inability to modify the price when the function was delivered. There are too many examples like the above. In summary, it is too casual and too careless. Anyway, I just made the function and released it. I don’t care whether it can be used or not. Let’s talk about the arbitrary modification of online content. If the impact of the previous "modifying functions without testing" is not that great, then the severity of the problem of "arbitrary modification of online content" is much greater.