What does the A Life Engineered guest mean by control surfaces in an AI-built software project?

The guest frames understanding as control: the mental model and the knobs, sliders and inputs an engineer has into a project. The bad case is asking an AI for an application, getting 100,000 lines, and knowing only that the URL returns the right result, with no idea of the subsystems, database schema or microservices. The good case is being able to say which three components cause the latency and which module a styling change belongs in.

• The guest's example of a targeted change is giving the cat and dog sections of a site different styling by refactoring one specific module.
• He thinks knowing where internal engineering decisions were made will stay valuable in the long run, even as the way code gets written shifts.

Source: our own transcription of the episode. The full conversation is on A Life Engineered (2026-10-27). Read the whole episode summary →

▸More from this episode