As I have already stated, I write code and quite a lot of it. By its nature, the process of writing code means introducing "bugs".
Without requirements or design, programming is the art of adding bugs to an empty text file. (Louis Srygley)
I have always had an aversion to that term, though. Although it has an interesting origin 1, is no longer very descriptive of 21st century software development activities.
What we commonly call "bugs" are really merely the manifestation of a behavior we did not expect. Usually it is an undesireable behavior; a side-effect of some other intentional process. Otherwise we would call it a "Feature".
I want to HEREBY PROPOSE that an update to the terminology used in the Industry. My recommendation is to hereon call them Generally Unexpected Behaviors (GUB).
Think of it as the anti-bug (like an "anti-pattern"; a terribly overused term in the software industry).
1: According to Wikipedia:
In 1946, when Hopper was released from active duty, she joined the Harvard Faculty at the Computation Laboratory where she continued her work on the Mark II and Mark III. Operators traced an error in the Mark II to a moth trapped in a relay, coining the term bug. This bug was carefully removed and taped to the log book. Stemming from the first bug, today we call errors or glitches in a program a bug.