liveBook · Manning

Review overhead

As explained in Vibe Engineering

Review overhead is the engineering-time cost of manually evaluating generated code or other proposed changes.

Review overhead is the senior engineering time required to evaluate agent-generated code and proposed changes. It is a hidden cost alongside licenses, compute, and tokens, and can exceed all three combined. section 10.3.6

Counting subscriptions or pull requests alone makes automation look cheaper than it is. Measure the full delivery cost, because people reading output may be the dominant expense even when auto-merge absorbs much of the queue. section 10.3.6 section 10.7.2

A feature-level cost dashboard

A six-developer team paid $240 monthly for licenses, about $800 for infrastructure, and over $2,000 for tokens. Yellow and Red pull requests still required senior review at $150 each, making review overhead larger than the other costs combined. Linking pull requests to Jira tickets allowed the team to roll licenses, compute, tokens, and review time into a cost-per-feature measure. section 10.3.6 section 10.7.2

How Vibe Engineering covers it

How deep it goes
Defines the cost category, quantifies its dominance in one team, and extends measurement from pull requests to complete features.
Examples
Uses senior review of Yellow and Red pull requests and Jira-linked feature-cost dashboards as concrete measurement examples.
What you can do after
Operate a cost dashboard that aggregates review time with licenses, compute, and tokens for each delivered feature.
How it connects
Connects review overhead to CI compute, tokens, auto-merge, pull requests, and cost-per-feature measurement.

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.