liveBook · Manning

Countermeasure

As explained in Build High Value Software Systems

A countermeasure is an action designed to address a problem’s cause and prevent or reduce its recurrence.

A countermeasure changes the system or how work is done to address a root cause and prevent or contain recurrence. A quick fix may hide a failure while leaving its cause intact. section 8.5 section 8.9

Countermeasures can change different parts of the engineering workflow:

  • Fix the defect in code, such as adding missing validation. section 8.5
  • Update standard work—templates, checklists, or procedures—so safer defaults carry forward. section 8.5
  • Add automated checks that catch the condition before production. section 8.5
  • Use observability to detect problems early; an alert that merely prompts manual intervention is not prevention. section 8.5

Make the migration safer by default

If a migration omitted ANALYZE, running it on the affected table fixes the immediate issue. Adding ANALYZE to the migration template changes the default for future work; a CI query-plan assertion can provide another guard. section 8.5 section 8.6

Table 8.3 Countermeasure versus quick-fix evaluation
Change
Type
How to tell
Schema migration prevents invalid data
Countermeasure
The invalid state cannot exist — the database enforces it
Rate limiter caps request volume
Countermeasure
Overload is structurally blocked before it reaches the service
Retry loop hides intermittent failures
Quick fix
The failure still happens; the retry just hides it
Input sanitization works around bad upstream data
Quick fix
The upstream service still sends bad data every time
Updated deployment template with correct defaults
Countermeasure
The standard work changed, future engineers get the right config without thinking about it
Circuit breaker with fallback mode
Countermeasure
The system handles the failure by design, not by luck

Compare structural controls, such as schema constraints and deployment defaults, with quick fixes that hide or work around failures. section 8.5

How Build High Value Software Systems covers it

How deep it goes
Distinguishes code fixes, standard-work updates, automated checks, and detection, but gives no detailed implementation procedures.
Examples
Uses a migration missing ANALYZE, an updated deployment template, and retry loops that mask failures.
What it assumes
Assumes root-cause analysis and directs readers to use established RCA tools rather than teaching them.
What you can do after
Evaluate proposed changes by asking whether they prevent recurrence or merely make it less likely.
How it connects
Connects root-cause analysis with standard work, automated checks, observability, and A3 reports.

Also explained in

Compare how 2 books explain countermeasure →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build High Value Software Systems. The section links point to the parts of the book it draws on.