
A Microsoft developer examines the problem of programming "bugs, " showing how and where developers make mistakes along the development process and providing ways users can detect errors early. Original.
Writing Solid Code is over 30 years old, and has techniques that are still completely relevant, today (some have become industry standard).
Reading that, was a watershed in my career.
It has many techniques described, that have since become Canon, and a number that have not aged so well.
One that is probably impractical, these days, is Step Through Your Code. He recommends stepping through every line of your code in a symbolic debugger, making sure that the code flow is what you expect, and the app state is appropriate.
Every now and then, I can do it. Often, when I’m already there, for something else. It really does work.
Many of the techniques, therein, are now standard practice.
It also espoused a basic philosophy of Quality, which doesn’t seem to have aged as well.
'Software Fundamentals' by Hoffman and Weiss,
'Writing Solid Code' by Maguire,
'Code Complete' by McConnell
