liveBook · Manning

Feedback

As explained in Build High Value Software Systems

Information about the effects or results of work that can guide subsequent decisions or changes.

Feedback reports the effects of work so people can decide what to change next. Delayed validation turns feedback into waiting; visible intent helps reviewers judge whether a change serves its purpose. section 6.5.2 section 3.6

Use feedback to protect flow and improve decisions:

  • Keep validation timely. When tests and scans make commits queue, layer or parallelize validation rather than weakening necessary safety. section 6.5.2
  • Make PR feedback explain the failure mode and possible fixes, not just prescribe an action; this teaches principles that transfer to future changes. section 15.2
  • Constrain AI output to reduce downstream work, and expose intent and deferred decisions during review. section 3.6

When validation becomes the bottleneck

A pipeline grew from 12 to 42 minutes after more integration coverage and sequential scans were added. Three commits queued, delaying feedback; reducing validation wait mattered more than reducing coding time. section 6.5.2

Listing 15.2 A PR comment that teaches error boundaries
This component works great for the happy path. One thing to consider:
if the API returns a 500 or the network times out, this will throw
an unhandled exception and crash the entire dashboard — not just
this chart.
 
Two options:
 
1. Wrap the fetch in a try/catch and render a fallback UI:
 
   try {
     const data = await fetchChartData(endpoint);
     setChartData(data);
   } catch (err) {
     setError("Unable to load chart data. Retry?");
   }
 
2. Add a React Error Boundary around this component so a failure
   here doesn't take down the whole page:
 
   <ErrorBoundary fallback={<ChartError />}>
     <DashboardChart endpoint={endpoint} />
   </ErrorBoundary>
 
Option 2 is generally better because it protects the parent
page even if we miss an error case inside the component.
 
The pattern: any component that fetches external data should
either handle its own errors or be wrapped in a boundary that
does. That way one flaky endpoint doesn't break everything.

A PR comment about API failures contrasts a bare instruction with feedback that explains the risk and offers error-handling options. section 15.2

How Build High Value Software Systems covers it

How deep it goes
Explains feedback through CI/CD delays and PR coaching, without presenting a general feedback framework.
Examples
Uses a 12-to-42-minute pipeline and a PR comment about API failures and error boundaries.
What it assumes
Assumes software-development experience but no prior Lean or formal process-improvement background.
What you can do after
Apply feedback by reducing validation waits and writing review comments that explain failure modes and reusable solutions.
How it connects
Connects feedback to CI/CD, pull-request review, coaching, Lean flow, and AI-assisted development.

Also explained in

Compare how 25 books explain feedback →

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.