How to make a stable product that works well for all clients on all devices? One of the key answers here is a bugless software. A bug is about all the inconsistency and lack of functionality on the project. But how to prevent bugs? Is it possible at all to do this? The actual answer is no. Any software contains an unlimited number of bugs. It doesn’t matter how many software engineers and testers are involved in a project. What is more, it doesn’t matter how much money is spent. So how to low the risk of unstable and buggy product? There are some major points to search for: Lack of documentation. This is a hugely widespread issue on most of the projects. A customer is not providing enough details. Programmers are not asking a customer how to implement all aspects of the tasks they have. This gap in documentation and communication provides a lot of hidden issues which are hard to find with edge cases. Lack of tests. This one is about laziness and a poor understanding of a testing process. The software engineer is not covering all critical aspects of a program and tester is not testing all the cases he has to on all possible devices. Lack of time. Proper testing requires about 25% of software development time. The more time management is allocating for a proper testing - the more bugs will be found. Bugs are evil. This is the main misunderstanding in software development. To be honest, everybody thinks that bugs are evil and if software contains them software engineers are people who should be blamed. But the truth is - the more bugs will be found during the process of development - the less it will be found by users in the real field. So bugs should be found on all stages of development. The more - the better. In KeyToTech we are encouraging all team members to find as many bugs as they can and not hiding any of them from the client.