It’s too easy as a tester to regard some bugs as more prestigeous than other. A bug that is harder to find is more important or valuable than one that is easy to discover, or rather; bugs that takes less energy to find is less valuable than thos you’ve worked hard to find.

My own favoritebugs tends to consist mainly of bugs I spent a lot of energy on finding. I don’t consider it strange as I thrive on the rewarding feeling of putting in a lot of effort and overcoming obstacles to finally reveal a bug. It increases the feeling of knowing what you are doing. To just point out something that’s seemingly obvious is not quite as satisfying, it’s like winning a race when you’re the only contestant, the medal may be shiny but it doesn’t feel like victory.

What’s worse is that my own values does not always match those of the team or project. It may very well be a waste of time, from the projects poinit of view, to dig for the cool, hard to discover, bug. The project gains more from correcting the, to a tester, obvious bugs. Impact of the illusive bug may in many cases be close to none, a fraction of the users would have been affected if not fixed.

Visitors on a web site is firstly faced with the presentation layer, CSS and Java Script. Bugs in this layer can very well have a much bigger impact than a hard to find bug in the back end logic.