liveBook · Manning

Code increment

As explained in Vibe Engineering

A code increment is a coherent set of changes that produces a stable intermediate version of a codebase.

A code increment is a coherent, reviewable set of changes that produces a stable intermediate version of a codebase. In migration work, its size is a deliberate tradeoff: tiny increments create process overhead, while oversized increments hide architectural mistakes and increase review difficulty. section 2.12

Treat each increment as an operational checkpoint:

  • Define one migration step and commit it clearly on a dedicated branch. section 2.3.2
  • Review the complete diff before accepting AI-generated changes; reject inferred future requirements, over-engineering, and architectural missteps. section 2.12 section 2.3.2
  • Test and encapsulate every step so later changes remain comparable with the legacy application. section 2.12 section 2.3.2
  • Keep sub-tasks separately committed when that improves traceability, even when they belong to one larger migration step. section 2.3.2

Layer-by-layer migration

A migration branch can contain one pull request for the data layer and another for the service layer. Cursor Plan Mode can propose the changes, show a unified diff, summarize the result as a conventional commit, and execute the commit only after review. section 2.3.2

How Vibe Engineering covers it

How deep it goes
Explains sizing tradeoffs, branching, diff review, testing, and commits, but stops short of prescribing a universal increment size.
Examples
Uses data-layer and service-layer migrations, Cursor unified diffs, migration branches, and conventional commits as concrete examples.
What it assumes
Assumes basic Git and repository concepts while teaching incremental migration structure and AI-generated diff review.
What you can do after
Apply via Git and Cursor by creating reviewable migration commits, inspecting diffs, testing steps, and comparing changes with the legacy baseline.
How it connects
Connects incremental migration with legacy modernization, Git, code review, testing, pull requests, and AI-assisted development.

Related concepts

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