← All parts of this equation

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

Numerator: 1

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}.
11

What this part means

The complete quantity above the fraction bar.

Its job in the formula

1 is one of the signed contributions combined to compute the quantity on the left.

The passage around this formula

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 this part in the article →

Learn the underlying idea

A fraction a/b means a divided by b. The top number is the numerator; the bottom number is the denominator, and it cannot be zero.

Open the illustrated fractions: division written vertically guide →

Sources cited in the article section

These citations provide research context; check each source for the exact claim it supports.