Let’s name things the right way. According to : Wikipedia "A software bug is an error, flaw or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways. The process of finding and fixing bugs is termed “debugging” and often uses formal techniques or tools to pinpoint bugs, and since the 1950s, some computer systems have been designed to also deter, detect or auto-correct various computer bugs during operations." The Past There are many historical references to the word . Thomas Edison used it even before the first electrical computer. Bug During computing early days on , the large computing facilities were a source of heat, therefore attracting real bugs like moths. Mark III Computer pioneer coined the term while looking for a system malfunction. Grace Hopper The present 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 instead of and this is keeping us from confronting the real problems, real defects, and our own responsibilities. bugs faults Software quality is under our control. It is our responsibility to deliver quality products. The term sounds like an excuse out of our scope infecting our systems. It is not. Bug The Future Language is continuously evolving. We got rid of the word on our GIT repos. recently master To embrace the future and our own responsibilities, we need to be very careful with , not only with our classes, methods, and variables but also with our artifacts. names We don’t need to software anymore. debug Find the root fault (caused by ourselves or previous developers), embrace the problem, and fix it. Easy as that. 🐞 write an automated test, We need no . 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. 📋 bug trackers We don’t want to fix all software faults. A good deal of mature software have . Now called . ✔️ known bugs known defects Let’s start by calling things by their name. We look forward to comments and suggestions on this article. Also published on: https://mcsee.medium.com/stop-calling-them-bugs-370db4691360

Winner of Noonies 2020 for the award Hacker Noon Contributor of the Year - REFACTORING.

2020 - Hacker Noon Contributor of the Year in REFACTORING

2022 - HackerNoon Contributor of the Year - Clean Code

2022 - HackerNoon Contributor of the Year - Debugging

2022 - HackerNoon Contributor of the Year - Github

2022 - HackerNoon Contributor of the Year - Machine Learning

2022 - HackerNoon Contributor of the Year - Quality Assurance

2022 - HackerNoon Contributor of the Year - Refactoring

2022 - HackerNoon Contributor of the Year - Software Architecture

2022 - the Greatest Storyteller

Share your ideas with me!

Read My Stories

Buy Me a Coffee

Nominated for 2022 - HackerNoon Contributor of the Year - Refactoring

Nominated for 2022 - HackerNoon Contributor of the Year - Quality Assurance

Nominated for 2022 - HackerNoon Contributor of the Year - Github

Nominated for 2022 - HackerNoon Contributor of the Year - Machine Learning

Nominated for 2022 - HackerNoon Contributor of the Year - Clean Code

Nominated for 2022 - HackerNoon Contributor of the Year - Software Architecture

Nominated for 2022 - the Greatest Storyteller

Nominated for 2022 - HackerNoon Contributor of the Year - Debugging

Software Engineer

Too Long; Didn't Read

Get free API security automated scan in minutes

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

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

Too Long; Didn't Read

@mcsee

RELATED STORIES