Errors
Errors
Bugs, Boo-boos, Blunders
About the Book
I'm placing this complete but unpolished version of Errors up for sale so my readers can provide feedback to make it better. Every purchaser will have access to free updates and revisions as they are made. I can be reached at jerryweinberg@comcast.net
Introduction
Part 1. How Do We Think About Errors?
1.1 Errors in Reasoning About Errors
1.2 Errors in Interpretation
1.3 The Semantics of Error.pages
1.4 Selection Fallacies about Errors.pages
1.6 The Quest for Perfection
1.5 Who Decides If It's an Error?
Part 2. What Do Errors Cost?
2.1 Some Very Expensive Software Errors
2.2 Universal Pattern of Costly Errors
2.3 Measuring Cost and Value
2.4 Mistakes that Win.pages
Part 3. Where Do Errors Come From?
3.1 The Art of Bugging
3.2 Eight Fs of Software Failure
3.3 Code is Not the Biggest Problem
3.4 Error-Prone Language
3.5 Predicting the Number of Errors
3.6. Cautions in Predicting the Number of Errors
3.7 It Shouldn't Even Be Done
Part 4. How Do We Get Rid of Errors?
4.1 Finding and Fixing Errors
4.2 Prevent Testing From Growing More Difficult
4.3 Especially Difficult Errors
4.4 Learn from Errors
4.5 Always Be Second
4.6 Fix Your Organization
4.7 If You Can't Fix It, Feature It
Part 5. How Do We Prevent Errors?
5.1 Keep It Simple
5.2 Throw It Away
5.3 Go Slow, Go Fast
5.4 Test as You Build
5.5 Improve Communication
5.6 Rethink Your Organization
5.7 Master Your Fear
Part 6. Living With Errors
6.1 The Humpty Dumpty world
6.2 The First Law of Error Defense
6.3 The Second Law of Error Defense
6.4 The Third Law of Error Defense
6.5 The Fourth Law of Error Defense
6.6 The Fifth Law of Error Defense
6.7 The Sixth Law of Error Defense
6.8 The Seventh Law of Error Defense
6.9 The Eight Law of Error Defense
Table of Contents
- Foreword
-
Introduction
-
- 1960’s Forbidden Mention of Errors
- We make errors quite regularly
- 1960’s Cost of errors
- “Trivial” errors can have great consequences
- Back to 1960 again
- Errors can escape detection for years
- How was it tested in 1960
- Sometimes the error is creating a program at all.
- The full process, 1960
- We must not confuse cost and value.
- Coding is not the end, even in 1960
- Programs can become erroneous without changing a bit.
- We keep learning, but is it enough?
- Testing for errors grows more difficult every year.
-
-
Part 1. How Do We Think About Errors?
-
1.1 Errors in Reasoning About Errors
- Errors are not a moral issue
- Quality is not the same thing as absence of errors.
-
1.2 Errors in Interpretation
- Who are the best and the worst programmers?
- Which is the good quality release?
- Why is someone working late?
- Why is the software late?
- Which process is eliminating problems?
- Who knows what’s right and wrong?
- What happens to control when interpretations are backwards?
- The Controller Fallacy
-
1.3 The Semantics of Error
- Names can influence the perceived severity of errors.
- Faults and failures
- Terms for System Trouble
- Keeping track of faults
- “Fault” does not imply blame
-
1.4 Selection Fallacies About Errors
- Completed vs. terminated projects
- Early vs. late users
- “He’s just like me.”
- Three questions to prevent selection fallacies
-
1.5 Who Decides If It’s an Error?
- Who thinks the customer is wrong?
- What did the consultant do?
- What can be done when there’s no agreement?
- Can you believe the tests and the testers?
- Who can we believe?
- So, what is an error?
-
1.6. The Quest for Perfection
- How the belief in perfection leads to error
- What are survival rules?
- How can meta-rules prevent change?
- Can rules be transformed into more useful guides?
- What’s the first step to better effectiveness?
-
1.1 Errors in Reasoning About Errors
-
Part 2. What Do Errors Cost?
-
2.1 Some Very Expensive Software Errors
- Why Concentrate on Failure?
- What Do Failures Cost?
-
2.2 The Universal Pattern of Costly Errors
- What’s the pattern?
- The universal pattern of management coping with a large loss
- The First Rule of Failure Prevention
-
2.3 Measuring Cost and Value
- Mistaking cost for value
- What is value?
- Perceived value
- Collapse of value
- The Second Law of Thermodynamics
- The First Law of Human Nature
- To know the cost of an error, we must measure quality
- Standards can be another secondary requirement
- A caution about measuring value
-
2.4. Mistakes that Win
- Profit from your errors
- Alexander Fleming’s Discovery of Penicillin
- Henri Becquerel’s Discovery of Radioactivity
- Errors are worthless, unless …
-
2.1 Some Very Expensive Software Errors
-
Part 3. Where Do Errors Come From?
- 3.1 The Art of Bugging: or Where Do Bugs Come From
-
3.2 Eight Fs of Software Failure
- The Second Rule of Failure Prevention
- Learning from others’ mistakes
- Frailty
- Folly
- Fatuousness
- Fun
- Fraud
- Fanaticism
- Failure (of Hardware)
- Fate
- What’s Next?
-
3.3 Code Is Not the Biggest Problem
- Assuming Fixed Requirements
- Error in English
- My favorite error
- What was the bug?
- What I learned from my error
- References
-
3.4 Error-Prone Language
- Heteronynms
- Heteronyms in software
- Hetero-sentences
- Left ambiguity
- Ambiguity in programs
- Central ambiguity
-
3.5 Predicting the Number of Errors
- A long-term experiment
- The history of error reporting
- Predicting error categories
- Assumptions underlying the method
- Application to software errors
- Are we ready to ship the app?
-
3.6 Cautions in Predicting the Number of Errors
- Using Beta-Test Results
- Fudging for non-independence
- Other applications
-
3.7 It Shouldn’t Even Be Done
- Zombie projects
- Euthanasia reviews
-
Part 4. How Do We Get Rid of Errors?
-
4.1 Finding and Fixing Errors
- Detection
- Location
- Resolution
- Prevention
- Distribution
-
4.2 Prevent Testing From Growing More Difficult
- Why is the situation growing worse?
- Why isn’t bigger actually cheaper?
- Keep systems as small as possible.
- Keep your model of “system” expansive.
- Build incrementally in isolated components with clear interfaces.
- Build the most significant functions first.
- Reduce the number of faults going in.
- Don’t underestimate the complexity of old, patched-up code.
- Keep your tools sharp.
- Encourage these matters to be discussed, as well as measured.
- Adjust process data as current experience indicates.
- Beware of using early returns as indicators of later results.
- Don’t think about testers as “the bad guys who prevent delivery.”
-
4.3 Especially Difficult Errors
- Hail Columbia!
- On the Beach
- Sexism? Bigotry?
- The disappearing act
- What makes errors especially difficult?
-
4.4. Learn From Errors
- Three Lessons from a Thirty-Year Error
- A learning paradox
- Other ways to learn
-
4.5 Always Be Second
- Does first come first?
- Where do new ideas come from?
-
4.6 Fix Your Organization
- A desperate letter
-
4.7 If You Can’t Fix It, Feature It
- Where did that feature come from?
- Develop incrementally from the top down
- Features Can Become Failures
-
4.1 Finding and Fixing Errors
-
Part 5. How Do We Prevent Errors?
-
5.1 Keep It Simple
- How we build makes a difference.
- Optimizing encourages errors.
- Fancy can be a synonym for complex.
- Use the Square Law of Computation.
- A stitch in time saves nine.
-
5.2 Throw It Away
- Reuse or reject?
- Things change
- Pay the true cost of retention
-
5.3 Go Slow, Go Fast
- Beware of the Quick Fix
- Rapid prototyping?
- Lessons of history
- Hurry
-
5.4 Test as You Build
- Reuse well-tested code
- Test all your ideas
- Start with the biggest risks
- Perform a Hudson’s Bay Start
- Prototype
- Deliver before you deliver
-
5.5. Improve Communication
- Interface treaties
- Enforcement
- What if they won’t sign?
-
5.6 Rethink Your Organization
- What’s needed for a normal project?
- What every organization needs
- Start with one little change
-
5.7 Master Your Fear
- Rhubarb Cakes for the Queen of the Forest
- The lesson
-
5.1 Keep It Simple
-
Part 6. Living With Errors
- 6.1 The Humpty Dumpty world
- 6.2 The First Law of Error Defense
- 6.3 The Second Law of Error Defense
- 6.4 The Third Law of Error Defense
- 6.5 The Fourth Law of Error Defense
- 6.6 The Fifth Law of Error Defense
- 6.7 The Sixth Law of Error Defense
- 6.8 The Seventh Law of Error Defense
- 6.9 The Eighth Law of Error Defense
- The End, for now
-
Appendix. Error Messages
- Message Irrelevant
- Message Contradictory
- Message Not Clear
- Clear but Misdirects
- Message Not Explicit
- Message Offensive
- No Message
- Some Conclusions
Other books by this author
Authors have earned$9,882,857writing, publishing and selling on Leanpub, earning 80% royalties while saving up to 25 million pounds of CO2 and up to 46,000 trees.
Learn more about writing on Leanpub
The Leanpub 45-day 100% Happiness Guarantee
Within 45 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
See full terms
Free Updates. DRM Free.
If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).
Most Leanpub books are available in PDF (for computers), EPUB (for phones and tablets) and MOBI (for Kindle). The formats that a book includes are shown at the top right corner of this page.
Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.
Learn more about Leanpub's ebook formats and where to read them
Top Books
C++ Best Practices
Jason TurnerLevel up your C++, get the tools working for you, eliminate common problems, and move on to more exciting things!
Functional Design and Architecture
Alexander GraninSoftware Design in Functional Programming, Design Patterns and Practices, Methodologies and Application Architectures. How to build real software in Haskell with less efforts and low risks. The first complete source of knowledge.
OpenIntro Statistics
David Diez, Christopher Barr, Mine Cetinkaya-Rundel, and OpenIntroA complete foundation for Statistics, also serving as a foundation for Data Science.
Leanpub revenue supports OpenIntro (US-based nonprofit) so we can provide free desk copies to teachers interested in using OpenIntro Statistics in the classroom and expand the project to support free textbooks in other subjects.
More resources: openintro.org.
R Programming for Data Science
Roger D. PengThis book brings the fundamentals of R programming to you, using the same material developed as part of the industry-leading Johns Hopkins Data Science Specialization. The skills taught in this book will lay the foundation for you to begin your journey learning data science. Printed copies of this book are available through Lulu.
C++20
Rainer GrimmC++20 is the next big C++ standard after C++11. As C++11 did it, C++20 changes the way we program modern C++. This change is, in particular, due to the big four of C++20: ranges, coroutines, concepts, and modules.
I am a Software Engineer and I am in Charge
Alexis Monville and Michael DoyleI am a Software Engineer and I am in Charge is a real-world, practical book that helps you increase your impact and satisfaction at work no matter who you work with.
In the book, we will follow Sandrine, a fictional character who learns to think in a new way enabling her to take a different course of action.
Invest In Digital Health - The Medical Futurist's Guide
Dr. Bertalan MeskoArtificial Intelligence and Digital Health are booming. In this book, we explain why now it's a good time to invest in Digital Health and give recommendations on where to invest by looking at the top 24 technological trends we find the most promising.
Atomic Kotlin
Bruce Eckel and Svetlana IsakovaFor both beginning and experienced programmers! From the author of the multi-award-winning Thinking in C++ and Thinking in Java together with a member of the Kotlin language team comes a book that breaks the concepts into small, easy-to-digest "atoms," along with exercises supported by hints and solutions directly inside IntelliJ IDEA!
The Hundred-Page Machine Learning Book
Andriy BurkovEverything you really need to know in Machine Learning in a hundred pages.
Mastering STM32
Carmine NovielloWith more than 600 microcontrollers, STM32 is probably the most complete ARM Cortex-M platform on the market. This book aims to be the first guide around that introduces the reader to this exciting MCU portfolio from ST Microelectronics and its official CubeHAL.
Top Bundles
- #1
Software Architecture for Developers: Volumes 1 & 2 - Technical leadership and communication
2 Books
"Software Architecture for Developers" is a practical and pragmatic guide to modern, lightweight software architecture, specifically aimed at developers. You'll learn:The essence of software architecture.Why the software architecture role should include coding, coaching and collaboration.The things that you really need to think about before... - #2
The Future of Digital Health
6 Books
We put together the most popular books from The Medical Futurist to provide a clear picture about the major trends shaping the future of medicine and healthcare. Digital health technologies, artificial intelligence, the future of 20 medical specialties, big pharma, data privacy and how technology giants such as Amazon or Google want to conquer... - #3
Cisco CCNA 200-301 Complet
4 Books
Ce lot comprend les quatre volumes du guide préparation à l'examen de certification Cisco CCNA 200-301. - #4
CCDE Practical Studies (All labs)
3 Books
CCDE lab - #5
"The C++ Standard Library" and "Concurrency with Modern C++"
2 Books
Get my books "The C++ Standard Library" and "Concurrency with Modern C++" in a bundle. The first book gives you the details you should know about the C++ standard library; the second one dives deeper into concurrency with modern C++. In sum, you get more than 600 pages full of modern C++ and about 250 source files presenting the standard library... - #6
Modern Management Made Easy
3 Books
Read all three Modern Management Made Easy books. Learn to manage yourself, lead and serve others, and lead the organization. - #7
Programming with Ease
3 Books
Alle drei Bände der Serie Programming with Ease in einem Paket. Darin findest du alles, was ich dir zu den wichtigsten Phasen der Softwareentwicklung im Hinblick auf Clean Code Development für langfristig hohe Produktivität sagen kann.Im Band Slicing findest du die Anforderungsanalyse im Rahmen eines iterativ-inkrementellen Vorgehensmodells aus... - #8
Vagrant Ansible
2 Books
Unveil the power of Ansible and Vagrant with this bundle at a special price. You'll have everything you need to get started with Vagrant - learn the basics and how to create your virtual development environments, using Ansible as provisioner! About Vagrant Cookbook Vagrant Cookbook is a complete guide to get started with Vagrant and create your... - #9
Mastering Containers
2 Books
Docker and Kubernetes are taking the world by storm! These books will get you up-to-speed fast! Docker Deep Dive is over 400 pages long, and covers all objectives on the Docker Certified Associate exam.The Kubernetes Book includes everything you need to get up and running with Kubernetes! - #10
Growing Agile: The Complete Coach's Guide
7 Books
Growing Agile: Coach's Guide Series This bundle provides a collection of training and workshop plans for a variety of agile topics. The series is aimed at agile coaches, trainers and ScrumMasters who often find themselves needing to help teams understand agile concepts. Each book in the series provides the plans, slides, handouts and activity...