How to Decide What Bugs to Fix When
by Harun Yayli on Friday, August 12th, 2005 at 4:28 pm under Communication, Ideas
The Top 10 worst ways to decide:
10.Fix only the bugs that annoy your CEO.
9. Fix every bug (never ship).
8. Don’t fix any bugs (ship today!).
7. Fix only the bugs that annoy your CEO’s spouse/daughter/pet hamster.
6. Require approval for every decision from the most annoying and least intelligent person in your organization (possibly redundant with No. 10).
5. Start on a bug at random, and when you’re halfway finished, switch to another. Repeat.
4. Play bug hot potato. Don’t fix bugs, just keep assigning yours to someone else.
3. 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.)
2.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.
1.Spend all available time debating whether your current process appears on this list.
a nice article is available on OnLamp.
Recent Entries
- memcache.php flushes servers
- memcache.php can delete keys now
- memcache.php is now part of pecl/memcache
- memcache.php goes PECL
- memcache.php stats like apc.php
- oci_bind_by_name maxlength is not so optional
- Is Sun going to buy PHP too?(PHP Quebec 2008)
- PHP APC apc_shm_create error on CLI
- Facebook’s Buggy Spam Detection
- Is it Firefox or Zend Debugger? Cookie Standards