liveBook · Manning

AI assistance

As explained in Build High Value Software Systems

AI-assisted development is software development in which artificial-intelligence systems support activities such as coding, design, testing, or documentation.

AI assistance makes code creation faster, but it does not make software delivery frictionless. Generative AI can produce code, suggest architecture, and draft tests or documentation. The harder work often shifts to understanding what the output means, validating it, integrating it, and maintaining it across the software development lifecycle. section 1.0 section 1.1

A passing test is not a product decision

An AI-generated endpoint returned a conflict response for cancelled orders. Its tests passed, and the pull request looked sound, but nobody had specified or chosen that rule. The team discovered the assumption only after deployment. Review had checked the implementation without establishing whether its behavior was intended. section 3.0

Treat AI as a fast executor within boundaries, not an authority on what the system should do. A developer who only edits and approves generated output may miss where decisions are being deferred or unnecessary work is accumulating. Human judgment remains responsible for value, correctness, and whether a change is sufficient. section 3.1.1 section 3.1.3

Practical boundaries keep that responsibility visible:

  • Write a human statement of intent for each AI-assisted change: the problem, decisions made, and what was left out. section 3.4.2
  • Use AI more freely for reversible exploration and scaffolding; retain human control over final behavior, semantics, and contracts. section 3.4.2
  • Before review, require generated code to compile and pass existing tests. Tie production-code prompts to a specification or contract. section 3.4.2
  • Keep shared boundaries near the work, such as in repository instructions, pull request templates, or saved prompts. section 3.4.2

How Build High Value Software Systems covers it

How deep it goes
Explains shifted delivery constraints and gives practical boundaries for prompting and review, without detailing AI implementation internals.
Examples
Uses an AI-generated endpoint with an unintended order rule and rules for intent statements, tests, and specification-linked prompts.
What it assumes
Assumes familiarity with pull requests, builds, tests, and specifications; introduces the shift from code creation to validation and integration.
What you can do after
Practice/perform AI-assisted changes with explicit intent, review-ready code, and human ownership of final behavior.
How it connects
Connects AI assistance to Lean thinking, waste, flow, code review, testing, and software specifications.

Also explained in

Compare how 5 books explain AI assistance →

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.