How to deal with bugs? The first solution is to implement a control chain – an inspection process. Each part of the project (e.g a module, script, documentation) will be controlled by a number of people or systems during the development.
Quality Engineer: Hey, I have detected a bug that should be fixed till the end of the week.
Developer: Oh, ok. I will fix it as soon as possible.
This is a standard dialogue between developer and quality engineer during the development process. The bug was detected and probably it will be fixed as developer said “as soon as possible”. From the quality engineer perspective it is something what should be done here.
Housing estate resident: Unauthorized cars shouldn’t be here!
Housing estate administrator: Oh… I will install RFID based car authorization system, then we solve the problem. We need 10k dollars to implement such system.
Another voice: Why unauthorized cars are the problem? Is it true that there are no parking for the guests? The RFID based car authorization system will deepen the problem only. This is not what you want!
How many times the bug solution is a reason of the next, more serious bug? To solve bugs we have to think about the whole context not the bugs only. We should learn how to ask about the reasons. How dilbert comic is related to the article? The bug is a lie. The more serious bug is an unsatisfied client. The most serious bug is a company culture represented by the manager.