Program testing can be used to show the presence of bugs, but never to show their absence!
Software is written by humans and therefore has bugs.
Don’t fix bugs later; fix them now.
Writing Solid Code: Microsoft's Techniques for Developing Bug-Free C Programs by Steve Maguire
ISBN: 1556155514 This book is available from Amazon
Never allow the same bug to bite you twice.
Beware of bugs in the above code; I have only proved it correct, not tried it.
Version 1 of any software is full of bugs. Version 2 fixes all the bugs and is great. Version 3 adds all the things users ask for, but hides all the great stuff in Version 2.
It's not a bug - it's an undocumented feature.
When you spend time to find & fix all the bugs in your project, you can't complete the project in your life time.
Don't wait until you have a bug to step through your code.
With good program architecture debugging is a breeze, because bugs will be where they should be.
If debugging is the process of removing bugs. Then programming must be the process of putting them in.
3 Biggest Software Lies: - The program's fully tested and bug-free. - We're working on the documentation. - Of course we can modify it.
Let he who has a bug free software cast the first stone.
