liveBook · Manning

Ai coding assistant

As explained in Build High Value Software Systems

A software tool that uses artificial intelligence to help generate, transform, explain, or review code.

An AI coding assistant helps generate and explain code, but faster code production does not necessarily mean faster delivery. A large generated change can shift work into pull-request review, defect correction, or maintenance. Treat the assistant as a tool for shortening the path from a human decision to feedback, not as a teammate making decisions on the team’s behalf. section 3.1 section 3.2.1

Start with intent: the problem, constraints, and success criteria. For an API endpoint, decide its responses before asking for code. The assistant can then prepare a handler skeleton while a developer writes tests and checks the behavior. This removes mechanical setup without delegating the contract. section 3.2.1

Listing 3.1 Handler skeleton with no design decisions
export async function getOrder(req: Request, res: Response) {
  // TODO: Implement order retrieval logic
  // TODO: Handle 404 case when order not found
  res.status(501).json({ error: "Not implemented" });
}

The handler skeleton leaves retrieval and the 404 case unimplemented. Its value is getting the agreed endpoint into a form that can be tested, not deciding how it should work. section 3.2.1

Before accepting generated code, ask:

  • Can another developer explain and review this change? What assumptions would they have to uncover? section 3.5
  • Did it add a dependency or establish a new pattern? A styling suggestion can spread into a second styling system with lasting build and maintenance costs. section 4.3.4
  • Did it solve the requested problem, or expand a webhook handler into queues, abstractions, and other unsolicited infrastructure? section 4.5.1

Generated explanations need the same boundary check. An assistant can help reconstruct an isolated module from its code, but may miss undocumented contracts across an event bus, shared database, or external API. Check those assumptions with people who know the wider system. Use AI to accelerate code-level understanding, not to replace system-level knowledge. section 13.4.1

How Build High Value Software Systems covers it

How deep it goes
Works through contract-based scaffolding, generated-code comparison, dependency risks, and limits of code-level understanding; does not specify assistant internals.
Examples
Uses an API handler skeleton, a handwritten-versus-generated change exercise, competing React styling patterns, and an unconstrained webhook prompt.
What it assumes
Assumes familiarity with endpoints and tests while defining Lean intent through problems, constraints, and success criteria.
What you can do after
Practice/perform constrained AI-assisted scaffolding and compare generated changes for reviewability, hidden assumptions, dependencies, and long-term ownership.
How it connects
Connects AI assistance to Lean value streams, API contracts, tests, pull-request review, dependencies, and collective ownership.

Also explained in

Compare how 3 books explain ai coding assistant →

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.