The New Engineering Problem

Engineering reorganizes when a constraint moves.^** The intuition is familiar from Amdahl's law: accelerating one part of a computation increases the relative importance of the work that remains ¹1. Gene M. Amdahl, “Validity of the Single Processor Approach to Achieving Large Scale Computing Capabilities,” in “Proceedings of the AFIPS Spring Joint Computer Conference,” special issue, Proceedings of the AFIPS Spring Joint Computer Conference (Atlantic City, NJ), 1967, 483–85.. Goldratt's Theory of Constraints states the broader operational version: system performance is governed by a constraint, and improving that constraint eventually moves attention to another ²2. Eliyahu M. Goldratt and Jeff Cox, The Goal: A Process of Ongoing Improvement (North River Press, 1984).. The same constraint logic applies to software-engineering economics. Steam radically reduced the cost of mechanical power. Integrated circuits did the same for computation. Coding agents are now reducing the cost of software implementation. A scarce factor constrains output, so it draws investment and attention. Implementation was never the only scarce input to software engineering, but for most of the field's history it consumed enough expert effort to limit what teams could attempt and how quickly they could change a system. As its marginal cost falls, other constraints become more visible: deciding what to build, representing a large system well enough to reason about it, producing evidence that a change is acceptable, and enforcing consequential engineering decisions across many changes.

Founding premise

Commodity intelligence makes implementation abundant relative to engineering judgment.

Engineering effort concentrates around what limits reliable production. As implementation capacity becomes cheaper and more abundant, judgment, representation, evidence, and enforcement become relatively scarcer. Engineers can delegate more realization work, but remain responsible for retaining sufficient control over the resulting system. Engineering effort moves with the constraint.

Abundance does not make implementation unimportant; it changes where additional engineering effort earns the greatest return. A factory with unlimited machine capacity and one inspector has not stopped manufacturing. Inspection has become the throughput constraint. In software, agents can now produce changes faster than engineers can specify, understand, validate, and govern them. Models let later work reuse representations across many acts of implementation; validators and gates can likewise reuse selected engineering judgments by evaluating and enforcing them repeatedly. Engineering effort therefore moves toward deciding what to represent, what evidence to require, which obligations to enforce, and how the surrounding environment should preserve those decisions across later work. This Part asks what follows from that shift: what remains hard, which properties of the new substrate matter, and what engineering problems they leave us to solve.