A certain game has a bug in the character attribute setting, which leads to the rampant plug-in, the collapse of the combat power system, and the loss of the final core users; A bug in the coupon function of an e-commerce platform caused a loss of tens of millions of yuan overnight; The latest version of a very large APP is set to expire after 3 days, but in fact there is no category email list updated version on the application market, which almost caused tens of millions of users to be unable to use the APP after 3 days; … When the version is launched, one of the things we are category email list most worried about is the occurrence of major bugs, especially for products that already have a large number of active users, once the new version has serious problems, it may cause irreparable losses.
After a problem occurs, when the company investigates and pursues responsibility for the cause of the accident, no matter who caused it, we, as the person in charge of the product, will take the blame and become the main responsible person or one of them. pot. It’s fine if it’s just memorized once in a while, most people can withstand the pressure, but if there are category email list always various problems, at this time, we may need to reflect on where the fundamental problem is. Is there any reason for it? What methods do we have at work to effectively reduce the category email list probability of bugs? When we first entered the workplace, we should have all experienced the process of taking the blame. It’s just that some people have strong comprehension ability and will soon find a way to cross this hurdle early. It takes a year or two to find a solution.
It's miserable. I belong to the latter category. For more than a year, I often encountered various problems after the version went online. Fortunately, I have summed up a few things from my past work. If you click on the method, there will be few major bugs after going online, and the career path will be smoother. Here I want to record the method and share it to help more people category email list find the key to this door. 2. How to avoid bugs Common bugs can be roughly divided into 3 types: requirements design defects, functional defects, and performance defects. We will category email list find ways to deal with them: 1. Defects in requirements design If there are loopholes in the logic made due to insufficient research and understanding of the requirements, or insufficient thinking when designing functions, and problems.