More Bugs, Please

A bug
is something we find in a software product that "doesn't look right" (this
is my personal definition). A bug can be hidden or visible; it can be
"already fixed" or "still present"; it can be critical or cosmetic; it
can be urgent or of a low priority. What is important is that the
more
bugs we are able to find and fix before our customers see them, the higher
the perceived quality
of the software. Simply put, bugs are a
very good thing,
if they are found by us, not our customers.
We pay our programmers for
each bug
they find. Here is a cheat sheet for them, showing where
and how they can find those bugs, to make more money.

Obviously, if something is broken, it's a bug; no need to mention it here.
However, when a product is more or less stable,
not too many things are
visibly broken. But we still pay for bugs. What should you look out for? Read on. This
list (in no particular order) will help you.

Also, it's worth mentioning that minor, cosmetic, or poorly formulated
bug reports will most likely be rejected or not paid for. If you want us to pay for your bug reports,
make sure they sound right,
in order to help us move the project forward to a better state.