Reputation: 231
When debugging a system is there any generally favored approach to which bugs to start with? Is it the easiest to fix, the hardest or the "most important" (whatever that means)?
Personally, I always do the easy ones first on the grounds that in the past I have discovered that they sometimes have knock-on effects, and fixing them can get rid of others. Or conversely, trivial bugs can mask more serious ones.
Upvotes: 0
Views: 85
Reputation: 21766
Usually bugs are prioritised by importance with importance being defined by the business added value after fixing this bug. There are different systems of prioritizing bugs, often developers score each bug on severity and priority. It is important to use both metrics as some severe bugs (crashing of application) may not actually have an high priority, for example if they occur in an experimental module of your product. This has been extensively discussed in the past, see this post for a more in detail discussion: How to prioritize bugs?
Upvotes: 1