The term bug has long been used by engineers to describe an error or flaw,  that causes an incorrect or unexpected result or unintended behavior.

In the 1940s Grace Hopper immortalized the term software bug when she wrote about how a moth in the MarkII computer caused erroneous results.

Although this was not the first use by engineers of the term bug to describe a fault it has become famously ingrained as the first instance of a software bug.

Perception

If we are able to change our perception of a result from the unexpected to the expected arguably it is no longer a bug.  If the software performs unexpectedly we can save a lot of time and effort by simply successfully marketing it as an enhancement.

Assuming perception is a reality, using this approach bugs can actually be perceived as worthwhile and used to help sell the product.  In this case, all you need to do is sell the unexpected behavior as a positive aspect of the software program.

For example, you could say this gaming program is great because it is unpredictable.  You can never be sure if it will work or not, you don’t necessarily get the same experience repeatedly.  Exciting eh.

The Emperor has no clothes

Undoubtedly there will be detractors who smirk at this approach.   These are the folks that read the children’s tale “The Emperor has no clothes” and laughed at the Emperor’s plight.

The Emperor in the story believed the lack of clothes was in fact an enhancement.  It made him happy.   Who am I to question that.  When software I develop has bugs, I sell them as enhancements and move on.