Home | Blog | Software | Reviews and Features | Forum | Help | Donate | About us
topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • December 10, 2016, 04:51:22 AM
  • Proudly celebrating 10 years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Author Topic: How to decide which bugs to fix (and when)?  (Read 2681 times)

zridling

  • Friend of the Site
  • Charter Member
  • Joined in 2005
  • ***
  • Posts: 3,292
    • View Profile
    • Donate to Member
How to decide which bugs to fix (and when)?
« on: October 17, 2005, 03:49:52 PM »
Scott Berkun wrote a two part article back in August titled, How to Decide What Bugs to Fix When (Part two is here). He's primarily discussing corporate software, but much of it can also be transferred to individual software authors. For that translation, just replace the phrase "your CEO" with "you." Here's a snip:

THE TOP 10 WORST WAYS TO DECIDE:
  • Fix only the bugs that annoy your CEO.
  • Fix every bug (never ship).
  • Don't fix any bugs (ship today!).
  • Fix only the bugs that annoy your CEO's spouse/daughter/pet hamster.
  • Require approval for every decision from the most annoying and least intelligent person in your organization (possibly redundant with No. 10).
  • Start on a bug at random, and when you're halfway finished, switch to another. Repeat.
  • Play bug hot potato. Don't fix bugs, just keep assigning yours to someone else.
  • Put bugs in alphabetical order and fix them from A to Z, skipping vowels. (Hint: if you relabel bugs appropriately, this is equivalent to No. 8.)
  • Create a complex parliamentary system of delegates elected by two-thirds majority to draft a charter of bylaws and rules of order for the formation of three bilateral subcommittees empowered to moderate future strategic defect management discourse.
  • Spend all available time debating whether your current process appears on this list.

Hopefully, you've never seen any of these in action; and now that you've been warned, you can avoid them in the future. Should your manager suggest any of these, please stand up, turn around quietly, and run as fast as you can.


mouser

  • First Author
  • Administrator
  • Joined in 2005
  • *****
  • Posts: 36,434
    • View Profile
    • Mouser's Software Zone on DonationCoder.com
    • Read more about this member.
    • Donate to Member
Re: How to decide which bugs to fix (and when)?
« Reply #1 on: October 17, 2005, 05:02:40 PM »
Quote
Start on a bug at random, and when you're halfway finished, switch to another. Repeat.
i wish this didn't strike so close to home...

you have to check out this site about apple lore that mark0 told me about yesterday, its related:
http://www.folklore.org/index.py

especially see this post which your top 10 list reminded me of:
http://www.folklore....te&detail=medium

excerpt:
Quote
"... We all gathered around as Chris showed the calculator to Steve and then held his breath, waiting for Steve's reaction. "Well, it's a start", Steve said, "but basically, it stinks. The background color is too dark, some lines are the wrong thickness, and the buttons are too big." Chris told Steve he'll keep changing it, until Steve thought he got it right. ..."

zridling

  • Friend of the Site
  • Charter Member
  • Joined in 2005
  • ***
  • Posts: 3,292
    • View Profile
    • Donate to Member
Re: How to decide which bugs to fix (and when)?
« Reply #2 on: October 18, 2005, 12:15:53 AM »
Wow what a great site! I spent a hour there before having to run.