A "known bug" is still a bug
Software engineering

A "known bug" is still a bug

What does a "known bug" or an update say our users?
Bartosz Mikulski
Bartosz Mikulski – 2 min read

Yesterday, I came across two known bugs. Two bugs in a row. Is this a lot? No user will ever see them. Those bugs were in an admin feature used mostly by developers. We have workarounds, but I felt frustration. Why can’t it just work?

Table of Contents

  1. Do we care?
  2. Updates
  3. Known-bug

I knew why it could not work. It could not work because we had more important bugs and features. It could not work because it was an internal tool. It could not work because there was always something else to do.

Do we care?

What does it tell about the developers? What about product owners? I know, I know we have explanations. I know we have excuses. I know we have priorities and must ignore some minor problems.

Is a “known bug” in any way better than an “unknown bug”? It is still a bug. We admit that we don’t care about that bug. What does it tell our users? Even worse, what does an update say to our users?

Updates

A few years ago, I met a person who complained that Linux is unstable and full of bugs because there are new updates almost every day. In the opinion of that person, a lot of updates = a lot of bugs.

For non-technical people, updates are annoying. They just want to use their computer, tablet, phone. They don’t care about updates. Updates interrupt their activity. They tried to play a game, not look at the game update screen. They wanted to upload a picture to Instagram, but the app has been restarted a second before they tapped the “Done” button, because of an update.

Known-bug

Are tech users in any way different? What happens when you see a popup which tells you that the OS update is ready to be installed? Do you click the “yes, please restart my computer and make it useless for 40 minutes” button or click “remind me tomorrow” and wonder why there is no “remind me next week” button?

The only time when I wanted to install an update was when the “BlueBorne” bug was disclosed. I wanted to use my smartwatch, but I had to disable Bluetooth because of a security vulnerability. For a year, my watch was just a dumb watch with a fancy interface ;) Apparently, for someone, it was just another “known bug.”

Older post

How to build a project inside a Docker container

How to safely run code downloaded from the Internet

Newer post

Programmers love new toys but hate new habits

We talk about toys. We love new buzzwords. We adore things that sound cool. Yes, we do.

Related Posts

Software engineering

Query string validation in Fastify

How to validate query parameters using Fastify
Published on: 25 Jan 2019

Software engineering

Assert object pattern

The easiest way to make your tests more readable and easier to maintain
Published on: 12 Dec 2018

Software engineering

Language is all about nouns

Programmers are afraid of nouns. We often replace them with poorly written descriptions of things.
Published on: 12 Sep 2018

Are you looking for an experienced AI consultant? Do you need assistance with your RAG or Agentic Workflow?
Schedule a call, send me a message on LinkedIn. Schedule a call or send me a message on LinkedIn

>