Agentic Engineering at Scale

Chapter 3. Technology Iteration

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the 7th chapter of the final book.

If you’d like to be actively involved in reviewing and commenting on this draft, please reach out to the editor at [e-mail].

There are two reasons to change software: to make it different and to keep it the same. This chapter is about the latter.

This chapter opens Part III, on regenerative engineering, or keeping a system fit by continuously re-deriving it from intent supported by the harness, rather than editing it until it drifts and must be rewritten. Technology iteration is its minimal form—change that keeps the system the same. Business iteration (Chapter 8) drives change from new requirements. Phoenix Architecture (Chapter 9) is the purest expression of regenerative engineering, freshly generating the production code from spec on every cycle.

Seen this way, iterating on technology isn’t merely about paying down technical debt. Each change is also an investment in the harness around the system. The stronger that harness, the cheaper the next renewal becomes. Keeping your technology current is how you keep your renewal posture strong.

The understandable view of people not involved in engineering software is that software, once written, should ...