DeepRead
Cover of Why programs fail

Why programs fail

Andreas Zeller · 2005

Programming and computer science › Programmer careers and interviews

#4,889 most recommended

About the book

A textbook on finding and fixing the causes of software failures. It treats debugging as a process that runs from reproducing a failure, through locating the defect that produced it, to verifying the fix, and it covers techniques for working through that process in real programs. The central claim is that debugging should follow the scientific method: observe the failure, form hypotheses about its cause, and test them with controlled experiments instead of relying on guesses. The book argues that several steps can be systematized or automated, including reducing a failing input to a minimal failure-inducing case, tracing the chain of infected states back from the failure to its origin, and correlating failing and passing runs to locate suspicious code. These are presented as techniques a programmer can apply directly.

Written by Claude from what it knows of this book.

What Hacker News says 88% recommend · 0% critical

02420122015202020262019 peak · 4
This bookAverage book in Programmer careers and interviews

In the commenters’ own words

What Open Library readers say

No Open Library reader has rated it yet.

  • 2 want to read
  • 0 reading
  • 0 have read

Open Library’s page for the book

What critics say, via Wikipedia

No Wikipedia article about this book yet, so no critics to quote.

Reddit communities — coming later

The threads it came up in

Details

First published
2005
ISBN
9781558608665
Editions known
8 at Open Library
Open Library
OL5848374W

Debugging in computer science

Explore in the mosaic

Read next: its neighbours on the mosaic