When you’re working on an app, as an individual or in a team, it’s easy to let some of the smaller problems slide such as bugs that are not deemed to be high priority. But these small issues can pile up and before you know it they turn into a big problem that you can’t ignore. Here are four simple rules to fix this.
Software bug image from Shutterstock
Errors are bound to happen during an application development process and when a bunch of small niggling bugs crop up, it’s tempting to just set them aside for the sake of progress. But those tiny issues can come back and haunt you. It becomes difficult to track these errors or exceptions later in the development process and fixing them will be even harder, which can cause delays.
While it’s easy to say you won’t tolerate any exceptions in production, it can be overwhelming when you’re faced with hundreds of errors that have occurred already. According to a blog post by Yeller, a company that makes software exception tracker apps, there are a few simple rules that you can follow to address this problem:
- Fix new unique exceptions as they show up
- Expected exceptions get turned into metrics
- Add a regression test every time you fix an exception
- Start with the most painful exceptions
You can read more about these rules over on the Yeller blog.
[Via Yeller blog]