The cranky user, To err(or) is human
Write error reports that help developers fix the problem
From the developerWorks archives
Date archived: May 16, 2019 | First published: October 06, 2004
It is not enough to say the software's awful. How do you help developers get it right on the next iteration? Cranky user Peter Seebach illustrates the difference between good and bad error reports and demonstrates how you can craft an effective error brief.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some content, steps, or illustrations may have changed.