← Back to article

Equation 5 · What Changes When a Whole Team Adopts Claude Code, Not Just One Developer

What does this equation mean?

S(g)=1(1−p)+p/g,lim⁡g→∞S(g)=11−p.S(g) = \frac{1}{(1-p) + p/g}, \qquad \lim_{g \to \infty} S(g) = \frac{1}{1-p}.

Read the formula alongside the article passage below. Each part has a deeper page with its role in the equation, the supporting passage and nearby citations.

Start with1
Divide by(1-p) + p/g
This relates toS(g)
How to read the two sides of this formula. Follow the article passage for the meaning of each quantity.

This equation states an equality: the expressions on both sides have the same value under the article’s assumptions. Read the equation part by part below; each part has a contextual explanation and a link to its mathematical background.

Read it piece by piece

SS

Symbol S

S is part of the quantity the equation computes from the expression on the right.

Understand this part →

gg

Symbol g

g occurs below the fraction bar. The quantity above the bar is divided by this expression; zero is excluded as a denominator.

Understand this part →

pp

Symbol p

the share of a change’s total cycle time that code generation itself used to consume before Claude Code, so (1-p) is the share consumed by review and everything else.

Understand this part →

=

=

The expressions on both sides represent the same quantity under the stated assumptions.

Understand this part →

See an illustrated explanation →
fraction

fraction

Divide the expression above the line by the one below it.

Understand this part →

See an illustrated explanation →
addition

addition

Add the term after the plus sign to the term or group before it.

Understand this part →

subscript

subscript

The lower label selects a particular version, component, or indexed member of the quantity. For example, x₀ and xₜ can be values at different positions.

Understand this part →

11

Numerator: 1

The complete quantity above the fraction bar.

Understand this part →

(1−p)+p/g(1-p) + p/g

Denominator: (1-p) + p/g

The complete quantity below the fraction bar; it must be nonzero for this division.

Understand this part →

11

Numerator: 1

The complete quantity above the fraction bar.

Understand this part →

1−p1-p

Denominator: 1-p

The complete quantity below the fraction bar; it must be nonzero for this division.

Understand this part →

How to interpret it

With a fixed numerator, increasing a nonzero denominator reduces the fraction. Read it with the definitions, units, and assumptions supplied by the article.

What the article says around this equation

That framing is worth making precise, because it is a structural claim, not a figure of speech. Let p be the share of a change’s total cycle time that code generation itself used to consume before Claude Code, so (1-p) is the share consumed by review and everything else. If generation alone speeds up by a factor g , total cycle time scales as (1-p) + p/g , and the achievable speed-up in total cycle time is S(g)=1(1−p)+p/g,lim⁡g→∞S(g)=11−pS(g) = \frac{1}{(1-p) + p/g}, \qquad \lim_{g \to \infty} S(g) = \frac{1}{1-p}. Amdahl’s law was originally about parallel processors, not engineering teams, but the constraint has the same shape: a serial bottleneck that does not scale caps the benefit of accelerating everything around it, no matter how large g gets. For a team, review is that…
Read the full surrounding passage
That framing is worth making precise, because it is a structural claim, not a figure of speech. Let p be the share of a change’s total cycle time that code generation itself used to consume before Claude Code, so (1-p) is the share consumed by review and everything else. If generation alone speeds up by a factor g , total cycle time scales as (1-p) + p/g , and the achievable speed-up in total cycle time is S(g)=1(1−p)+p/g,lim⁡g→∞S(g)=11−pS(g) = \frac{1}{(1-p) + p/g}, \qquad \lim_{g \to \infty} S(g) = \frac{1}{1-p}. Amdahl’s law was originally about parallel processors, not engineering teams, but the constraint has the same shape: a serial bottleneck that does not scale caps the benefit of accelerating everything around it, no matter how large g gets. For a team, review is that bottleneck.

Read the equation in its article →

Sources cited in the article section

These citations give research context. Read each source to check which claims it supports.

Return to What Changes When a Whole Team Adopts Claude Code, Not Just One Developer

See this formula across 1 published context →

Browse the mathematical compendium →