liveBook · Manning

Code quality

As explained in Vibe Engineering

Code quality is the degree to which source code conforms to correctness, maintainability, architectural, and style expectations.

Code quality is an operating signal, not a fixed property. In AI-assisted development, it can erode gradually while every individual suggestion still appears plausible. The result is higher review effort, more bugs, lower first-attempt success, and declining trust in the tool. section 9.4.3

Treat deterioration as a configuration or workflow signal rather than automatically blaming prompts or developers. Watch generated output, recalibrate after repeated weak suggestions, and switch models when quality drifts instead of adapting indefinitely around poor results. section 9.4.3

Use lightweight checks to make quality visible before trust and productivity decline:

  • Sample a random set of merged AI-generated changes weekly and inspect naming conventions, architecture, and other issues that ordinary CI may not catch. section 9.4.3
  • Track aggregate indicators such as first-attempt success, bug reports, review effort, and developer behavior rather than judging isolated suggestions. section 9.4.3
  • Keep tool choice aligned with task scope: reserve agent mode for multi-file work and avoid using it for a single trivial change. section 9.2.2

The invisible decline

A 1% weekly quality decline can reduce first-attempt success from 81% to 73% over eight weeks. Weekly sampling can expose the drift before complaints, missed targets, or manual rewrites reveal its cost. section 9.4.3

How Vibe Engineering covers it

How deep it goes
Defines gradual erosion and gives monitoring practices, but stops short of specifying a complete quality rubric or automated metric.
Examples
Uses weekly samples of ten merged AI changes, an eight-week decline from 81% to 73%, and agent-mode task conventions.
What you can do after
Diagnose quality drift by sampling merged changes, tracking aggregate signals, and changing configuration or models when output degrades.
How it connects
Connects code quality with code review, continuous integration, production monitoring, developer productivity, and model selection.

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.