Stories
Slash Boxes
Comments

SoylentNews is people

Reactions when Users Find Bugs in Your Software

posted by martyb on Saturday October 11 2014, @11:23PM   Printer-friendly
from the arachnephobia dept.

microtodd writes:

Some of the worst moments of my day happen when I get an email or a call from a customer who has found a bug in my released software product. It's even worse when I'm on site for training and they find the bugs there. No matter how rigorously I QA/test, it seems inevitable that a customer will find a way to break the software within the first few minutes of using it.

The key, then, is how do you respond? David Cummings has some thoughts on how to handle these scenarios. What's interesting is that there's an idea that maybe not all bugs need to be fixed, at least not right away. This is counter to The Joel Test where Joel Spolsky feels you should fix all known bugs right away, even before adding new features. Does this make sense? Is it more important to get new features out the door sometimes than to have as bug-free software as possible?

I'm reminded of this story, where adding a feature before fixing bugs actually saved the project.

 
This discussion has been archived. No new comments can be posted.
Reactions when Users Find Bugs in Your Software | Log In/Create an Account | Top | 51 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 1) by GeminiDomino on Sunday October 12 2014, @04:09AM

    by GeminiDomino (661) on Sunday October 12 2014, @04:09AM (#104971)

    Forgot to add, in most cases, fixing bugs is more important than adding features (looking at you Firefox)

    Yeah, but that gets rather tricky when you can't tell the difference (also looking at you, Firefox).

    --
    "We've been attacked by the intelligent, educated segment of our culture"