Symbol S
S is part of the quantity the equation computes from the expression on the right.
Read this term in its guide →Published equation contexts
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 . 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…
S is part of the quantity the equation computes from the expression on the right.
Read this term in its guide →g occurs below the fraction bar. The quantity above the bar is divided by this expression; zero is excluded as a denominator.
Read this term in its guide →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.
Read this term in its guide →The complete quantity below the fraction bar; it must be nonzero for this division.
Read this term in its guide →The complete quantity below the fraction bar; it must be nonzero for this division.
Read this term in its guide →With a fixed numerator, increasing a nonzero denominator reduces the fraction. Read it with the definitions, units, and assumptions supplied by the article.
A symbol can carry a different meaning in another article. Each occurrence keeps its own guide and term definitions.
Equation 5 · AI Agents & Systems
This equation states an equality: the expressions on both sides have the same value under the article’s assumptions.
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 . 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…