Ai-Native-Software-Engineering on Armstrong Yan

AI-Native Software Engineering, Part 1: Mental Models in Agentic Coding

Sat, 23 May 2026 20:33:47 +0800

AI can generate code. Harnesses can validate behavior. But who builds understanding?

This is Part 1 of the AI-Native Software Engineering series.

The series asks a larger question:

When AI lowers the cost of implementation,
what remains scarce in software engineering?

This article starts with the first scarce resource:

Understanding.

Over the past few months, I’ve been experimenting heavily with AI-assisted software development.

Not autocomplete.

Not AI as a coding copilot.

Sat, 23 May 2026 20:33:47 +0800

Why the most important part of AI-native software engineering may not be generation, but constraint.

This is Part 2 of the AI-Native Software Engineering series.

The previous question was:

If understanding no longer comes mainly from writing code,
how do humans build mental models in an agentic workflow?

The next question is:

If implementation is delegated,
where does correctness come from?

The conversation around AI-assisted software development often focuses on one thing:

Sat, 23 May 2026 20:33:47 +0800

When implementation becomes abundant, engineering starts to look less like construction and more like navigation.

This is Part 3 of the AI-Native Software Engineering series.

The first article asked:

How does understanding form when implementation is delegated?

The second article asked:

How does correctness form when generation is cheap?

This article asks:

If implementation keeps getting cheaper,
what are engineers actually doing?

Here, constraints shift meaning.

Sat, 23 May 2026 20:33:47 +0800

You can automate implementation. You can automate evaluation. But judgment remains stubbornly human.

This is Part 4 of the AI-Native Software Engineering series.

The first article asked how understanding forms.

The second asked how correctness forms.

The third argued that software is starting to look like search.

This article pushes back on a dangerous misunderstanding:

If we have agents, harnesses, and constraints,
software can produce itself.

That is not true.