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
- Build Your Own PBX
- Spam king Adam Vitale busted by Secret Service
- Make del.icio.us bookmarks
- Three Languages For Java Programmers to Learn
- 10 Really as400 Helpful APIs
- as400 commands and APIs you'll use for handling messages
- Four Hundred Guru--Admin Alert: Moving Libraries Between i5/OS Partitions, Part 1
- Recommended PHP reading list
- Common Gateway Interface (CGI) on the as400 / iSeries
- Difference between SFLINZ and SFLCLR keyword?
No comments:
Post a Comment