liveBook · Manning

Continuous improvement

As explained in The Coder Cafe

A feedback loop is a process in which system outputs or observations influence subsequent actions or system behavior.

A feedback loop lets system observations influence subsequent changes. In complex systems, observability helps teams get short feedback loops and improve changes using evidence rather than opinion. section 6.14.2

Observability supports improvement by making system behavior easier to understand:

  • Use high-dimensional telemetry to inspect system states, including unexpected ones, without shipping new code. section 6.14.2
  • When predictions are uncertain, replay past events or run deterministic simulations to assess a change before rollout. section 6.14.2

A change with hidden factors

A carefully designed change can still fail because of unaccounted factors. Replaying recorded inputs or testing controlled conditions can help assess its impact before rollout. section 6.14.2

How The Coder Cafe covers it

How deep it goes
Defines observability and describes its role in improvement, but gives no step-by-step feedback-loop procedure.
Examples
Uses an ineffective system change with unaccounted factors and proposes event replay or deterministic simulation.
What you can do after
Evaluate system changes using telemetry, short feedback loops, event replay, or deterministic simulation.
How it connects
Connects continuous improvement to observability, telemetry, and simulation testing.

Also explained in

Compare how 43 books explain continuous improvement →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of The Coder Cafe. The section links point to the parts of the book it draws on.