Let's Stop Calling them 'Bugs' - Software Quality is Our Responsibility

Let’s name things the right way.

According to Wikipedia:

There are many historical references to the word Bug. Thomas Edison used it even before the first electrical computer.

During computing early days on Mark III, the large computing facilities were a source of heat, therefore attracting real bugs like moths.

Computer pioneer Grace Hopper coined the term while looking for a system malfunction.

70 years later, data centers have become clean facilities (leaving no space for people or insects). Even our home computers are almost free from malfunction caused by real bugs.

We still name our software glitches as bugs instead of faults and this is keeping us from confronting the real problems, real defects, and our own responsibilities.

Software quality is under our control. It is our responsibility to deliver quality products.

Language is continuously evolving. We recently got rid of the master word on our GIT repos.

To embrace the future and our own responsibilities, we need to be very careful with names, not only with our classes, methods, and variables but also with our artifacts.

Find the root fault (caused by ourselves or previous developers), embrace the problem, write an automated test, and fix it. Easy as that. 🐞

We need no bug trackers. We just need to care for incidents, and not all incidents are faults. Surprisingly, many of them are related to misunderstandings, lack of definition, ambiguities etc. 📋

We don’t want to fix all software faults. A good deal of mature software have known bugs. Now called known defects. ✔️

Let’s start by calling things by their name.

We look forward to comments and suggestions on this article.