liveBook · Manning

Developer wait time

As explained in Vibe Engineering

Developer wait time is the time developers spend unable to proceed while waiting for AI-assisted operations or results.

Developer wait time is the time developers cannot proceed while waiting for AI-assisted operations or results. It is a hidden cost: it consumes developer time but does not appear on a subscription or API invoice. A lower token bill can therefore leave the largest cost nearly untouched. section 9.1 section 9.4.1

Wait time belongs in the total cost of an AI workflow alongside retries, context switching, and downstream bugs. A slower model may be cheaper per token but more expensive in developer time; a less accurate one can also cause costly reruns. Compare speed and first-attempt success with token price rather than optimizing any one measure alone. section 9.4.1 section 9.6

The cost behind the invoice

For a twelve-person development team, a monthly cost model puts visible AI spending at $1,407 and total cost at $9,407. Developer wait time accounts for $4,400, while retries account for another $1,480. The model assumes each developer works on one task while waiting for one response, so its 85% hidden-cost share is a ceiling rather than an invoice: parallel work can reduce the impact. section 9.4.1

Figure 9.6 Complete monthly AI cost - twelve-person development team.

Compare the modeled monthly cost categories for the twelve-person team. section 9.4.1

Evaluate changes by workflow. For interactive pair programming, latency and quality may matter more than the lowest token price; for CI review, cost and quality may take priority. Track first-attempt success and total cost so that savings do not simply move from the API bill into developer time or quality problems. section 9.4.1 section 9.6

How Vibe Engineering covers it

How deep it goes
Quantifies wait time in a team cost model and qualifies its single-threaded assumption as a ceiling.
Examples
Uses a twelve-person team's monthly cost breakdown and compares faster responses with cheaper tokens.
What you can do after
Evaluate AI workflows using developer time, first-attempt success, and total cost rather than token price alone.
How it connects
Connects wait time to latency, model quality, retries, context switching, and total cost.

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.