Understand the Fail Fast Principle
With modern software, it’s easy to embrace a culture where mistakes are not stigmatized but addressed directly. The fail fast principle surfaces errors immediately and close to their origin, preventing costly surprises later.
You must identify and report problems as early as possible. Instead of letting issues quietly propagate through the system, you should break the flow and demand attention and repair. This keeps your codebase robust. It ensures that the real issue is addressed right away instead of discovering it far down the execution line when it’s buried in logs, far removed from the root cause.
Understand Modern Software
In the 1950s, computing errors were costly. The process of running code involved punch cards, compilers, and long waits between each stage. If your program failed, discovering the cause of the problem could take hours or days. Back then, fast feedback was crucial to avoid wasting precious machine time. Fast forward to today, the systems and processes have evolved and although good products have daily builds and releases,the need for early detection of issues is still a goal of clean and reliable code.
Detect the Problem
Imagine building a trip planner. You input your destination, departure date, and list of activities. The trip planner should validate this information as soon as it’s entered. If someone types in an impossible destination (like “Atlantis”) ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access