Bug

What is a bug?

A bug is an error or unintended behaviour in software that makes it produce wrong or unexpected results. The word has been used in engineering since the nineteenth century and stuck in software after a 1947 incident, when a moth was found jamming a computer relay. The question with bugs is never whether they appear. It is how fast they get caught and how much damage they do first.

Bugs can start anywhere. In the logic of the code, in how two components talk to each other, in a wrong assumption about the shape of some data, or in an edge case nobody thought to handle. A checkout that works perfectly until someone orders zero items is a bug waiting in an unhandled edge case. They range from minor visual glitches to critical failures that lose data or open security holes.

Finding, reporting, and fixing bugs is a constant part of building software. Teams log them in tools like Jira, Linear, or GitHub Issues, assign owners, and track them to resolution. You cannot prevent bugs entirely, but code review, automated testing, and continuous integration cut how often they slip through and how much they cost to fix when they do.

Bugs at Dallonses

We don't set out to ship bugs, and we don't pretend we never will. Software is built by people, and people miss things. What we control is how we catch them and how we respond. Code review, automated tests, and acceptance testing in every sprint exist to find problems before a user does.

When a bug does reach a client, we own it. No blame games, no waiting. We reproduce it, fix it, and add a test so it stays fixed. Our software quality assurance work runs through the whole build rather than getting tacked on at the end, because the cheapest bug to fix is the one caught the day it was written. Honesty about this is part of how we keep client relationships intact.

Want software that's tested properly before it ships? Let's talk about QA.

Talk to us about quality assurance