BUG, Inc. Case Study

Design, manufacture and sale of recording devices used by buggy law enforcement agencies to intercept and record sounds and sounds. BUGS Employees write software to support bugs. BUG currently has an exclusive contract with most state and federal law enforcement agencies within the United States. BUG is considering expanding its market to an international level; manufacturing factories are divided into foreign countries and the United States. Patents, copyrights, trademarks, trade secrets and names of intellectual property rights are intellectual property rights.

Overall, "This is a line of code hooligans" or "This is a mistake" is a wonderful case study on blame transfer. Let's try to solve this problem from a new perspective. The code itself does not generate errors or deadlocks. The function is intentional, but the error is also intentional. Or at least if you want to solve this pandemic problem, you need to think like this. Please acknowledge this difficult fact. The error in our code is not a side effect. It does not have any damaging genetic material surrounded by protein covers for evolution, so the code itself does not create anything. Please take a look at it in a new way. In other words, this bug is intentionally designed carefully and strategically placed. If you can no longer see it as a side effect, you can start talking about why the world is full of encoders. And there are only a few good ones, there is always a shortage of encoders.

If you are not a software developer, this is called an irreproducible error. This means that you know that there is an error, but you can not copy it yourself. If you can not play it, you can not study it to understand what it is bad and you can not confirm if you modified it. This kind of brought developers a cold sweat and a nightmare. Since the problem only happens on some Android devices running Chrome, I get all Android devices and I can try to reproduce what I saw. I checked the registration code until my eyes turned red, and I could not see the obvious reason to happen. I started testing the developer tool over and over and why I did not see an event suggesting what this should happen.

Listening to actual customer errors is different from conducting usability studies on potential users. It really helps to prioritize errors. Sometimes when I find errors on their own, they are usually cases of some strange edges, and as 80% of users may not care. But when I heard a bug in someone's mouth, what does it mean? I read it somewhere, and when you hear the error, it is possible that 20 times people encountered the same problem. Finally, the best part to listen about mistakes is that if I wear a researcher's hat, I have a chance to dig deeper into their psychology. Ask some "reasons" and perhaps discover the underlying cause of their frustration. You can not obtain this valuable knowledge from developers who design test cases.