liveBook · Manning

Quality principle

As explained in Build High Value Software Systems

A Lean principle of building correctness and defect prevention into work rather than relying on later inspection.

Quality means building correctness and defect prevention into work, rather than relying on later inspection. Make architectural constraints visible before implementation so developers and AI agents can follow them from the start. section 1.2.4

Make the constraints actionable with checks that:

  • Flag forbidden database access with linter rules and clear build errors; keep the pattern in an architecture decision record and code templates. section 1.2.3
  • Run load tests for database changes before staging, failing the build when query times exceed thresholds or locks are detected. section 1.2.3

A constraint enforced early

When storage work must follow event sourcing, a linter can reject direct database access during the build instead of leaving the violation for code review to catch. section 1.2.3

Figure 1.4 Work loop with Lean interventions, addressing specific failure modes from the notification preferences scenario.

See where quality checks fit in the delivery work loop alongside other Lean interventions. section 1.2.4

How Build High Value Software Systems covers it

How deep it goes
Shows constraints enforced through linters, decision records, templates, and load tests, but does not detail their implementation.
Examples
Uses linting to catch event-sourcing violations and pull-request-triggered load tests for database changes.
What you can do after
Operate automated checks that flag forbidden database access and fail builds when load tests detect threshold breaches or locks.
How it connects
Connects quality with event sourcing, linters, architecture decision records, pull requests, and load testing.

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.