The Engineer's Obligation

In the AI Story

The recognition did not lead Moore to oppose the technology. He did not argue for slowing the exponential. He did not advocate regulation or caution in the language contemporary AI safety researchers use. His position was more characteristic of an engineer than a philosopher or policymaker. He measured. He observed. He stated what he saw. He acknowledged what he could not see. And he left the social consequences to the society that would experience them. Whether this constitutes adequate response is a question Moore's framework can pose but cannot answer — the framework is descriptive, not prescriptive.

Moore's Law is, at its core, a law of amplification. Each doubling amplifies the computational power available to every system using the chip. The amplification is neutral: it does not distinguish between applications, amplifying medical imaging and surveillance systems with equal fidelity, scientific computation and addictive game mechanics, the tools that connect families and the tools that fragment their attention. Edo Segal frames the AI moment in the same terms: AI is an amplifier, and the most powerful one ever built. The amplifier does not judge the signal. It carries whatever signal is fed into it.

The engineer's obligation, in Moore's framework, is not to control the systemic signals — that is beyond individual competence and authority. The obligation is to measure the consequences with the same rigor applied to measuring the amplification itself. To see the shadows alongside the gains. To account for the full system, not just the user-facing layer. To resist the professional temptation to celebrate capability while ignoring cost.

Moore's career embodied this obligation imperfectly, as all lives do. He built Intel, which produced the chips that powered the personal computer revolution, with consequences that included outcomes he would not have chosen. His philanthropic foundation, established in 2000 with an endowment exceeding five billion dollars, funded the open-source tools — Jupyter, NumPy — that became infrastructure for modern AI research. The chain from Moore's philanthropic investments to the current AI moment is direct and traceable: an engineer who drew a line on a graph in 1965 also funded the software tools that enabled the training of systems that learned human language. The connection was not planned; it was the consequence of values — measurement, open access, diffusion of capability — that produced, through compounding, outcomes no single act of planning could achieve. This is both the glory and the burden of engineering at the exponential frontier.

Origin

The obligation framework is articulated in this volume as a synthesis of Moore's stated positions (particularly his 2008 IEEE Spectrum contribution and various interviews in his later years) with the engineering-ethics literature descending from Norbert Wiener's The Human Use of Human Beings (1950) and Joseph Weizenbaum's Computer Power and Human Reason (1976). The specific framing — measurement as obligation — draws on Moore's career-long practice of descriptive rigor over prescriptive advocacy.

Key Ideas

Measure what you build. The engineer's obligation is not to control consequences but to measure them, making the accounting available to the society that will decide.

Intelligence is not one-dimensional. Moore's warning against treating intelligence as quantifiable on a single axis applies with force to contemporary AI benchmarks.

Amplification is neutral. The curve does not judge the signal; it carries whatever is fed into it, at scale.

Systemic signals are collective. Market incentives, institutional structures, regulatory frameworks, and cultural norms determine which signals get amplified — and these are beyond individual builder control.

Unplanned consequences compound. Moore's philanthropic investments in Jupyter and NumPy made modern AI possible; the connection was not planned, but followed from values applied consistently over decades.