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.11. 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.22. 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. Humans and agents can both implement software, but capable agents can do in minutes or hours work that would have consumed days or weeks of skilled human effort. As implementation becomes abundant, the next-scarcest factors constrain output, so they draw 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. Nor can inspection capacity be assumed to scale proportionally: sustained monitoring consumes finite human attention, and rare problems become especially difficult to detect as the stream of mostly acceptable output grows.†† Wolfe, Horowitz, and Kenner found that rare targets in visual search are disproportionately missed as their prevalence falls.33. Jeremy M. Wolfe et al., “Rare Items Often Missed in Visual Searches,” Nature 435 (2005): 439–40. Warm, Parasuraman, and Matthews synthesize the vigilance literature: sustained monitoring consumes attentional resources, imposes substantial workload, and can produce performance decrements and stress.44. Joel S. Warm et al., “Vigilance Requires Hard Mental Work and Is Stressful,” Human Factors 50, no. 3 (2008): 433–41, https://doi.org/10.1518/001872008X312152. 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 chapter 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.
Works Cited
- Amdahl, Gene M. “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, Eliyahu M., and Jeff Cox. The Goal: A Process of Ongoing Improvement. North River Press, 1984.
- Wolfe, Jeremy M., Todd S. Horowitz, and Naomi M. Kenner. “Rare Items Often Missed in Visual Searches.” Nature 435 (2005): 439–40.
- Warm, Joel S., Raja Parasuraman, and Gerald Matthews. “Vigilance Requires Hard Mental Work and Is Stressful.” Human Factors 50, no. 3 (2008): 433–41. https://doi.org/10.1518/001872008X312152.
- Chapter 1 — The New Engineering Problem (current chapter)
- Chapter 2 — Modeling: go to Chapter 2
- Chapter 3 — Alignment: go to Chapter 3
- Chapter 4 — MAGE in Motion: Engineering Through Models: go to Chapter 4
- Chapter 5 — Agentic Software Factories: go to Chapter 5
- Chapter 6 — The Theory: go to Chapter 6
- Chapter 7 — The Profession: go to Chapter 7