Saturday, September 24, 2005
How to Decide What Bugs to Fix When, Part 1
Here is the golden rule of organizing bugs: fix bugs in the order most likely to result in success. Sounds obvious, right? Wrong. I'd bet that more than half of the buggy and unreliable software you've ever used was that way not because the developers didn't have time to make it better; they simply fixed the wrong bugs. Wanting to fix the right bugs and knowing how to do it are two different things
Subscribe to:
Post Comments (Atom)
Popular Posts
- as400 iSeries NetServer Disabled user profiles
- Create a Custom Live Linux CD - Leveraging BusyBox and OpenSSH
- Encode HTML Entities - Showing code in blogs
- Search for text in vi or vim
- Library list for Web server
- IBM eServer iSeries - iSeries NetServer: Command Line Setup
- Super $500 Myth Project
- HOW TO make a Powerbook in to a Wi-Fi access point!
- Reno County is preparing to move from an AS400 computer system to a personal-computer-based system
- Thomas Dudziak's Weblog
No comments:
Post a Comment