#systems

10 posts

UI Is a Conservation Layer

Why the user interface is the last to become regenerative

The Phoenix Architecture icon
The Phoenix Architecture
Jan 21, 2026

n=1 Is a Design Constrain (Not a Staffing Model)

Single-developer capability isn’t a productivity story. It’s the test that tells you whether your architecture is worth keeping.

The Phoenix Architecture icon
The Phoenix Architecture
Jan 7, 2026

The System Is the Asset

Why Regeneration Does Not Mean Starting Over

The Phoenix Architecture icon
The Phoenix Architecture
Jan 5, 2026

Conceptual Mass and the Compaction Discipline

As I mentioned in a previous post, at Wunderlist, we had a rule: any new service had to be "this big", a constraint I'd demonstrate by holding my fingers a few inches apart. The metric wasn't about lines of code. It was about replaceability.

The Phoenix Architecture icon
The Phoenix Architecture
Jan 2, 2026

Evaluations Are the Real Codebase

Why behavior outlives implementations

The Phoenix Architecture icon
The Phoenix Architecture
Dec 29, 2025

The Gradient of Trust

Better shapes beat better prompts

The Phoenix Architecture icon
The Phoenix Architecture
Dec 28, 2025

Code Was Never the Asset

Why AI makes the hidden economics of software unavoidable

The Phoenix Architecture icon
The Phoenix Architecture
Dec 24, 2025

Pace Layers and AI Integration

Not all software should change at the same speed.

The Phoenix Architecture icon
The Phoenix Architecture
Dec 23, 2025

The Death and Rebirth of Programming

Programming didn't die all at once. There was no single moment, no dramatic obsolescence event. Instead, something quieter happened: the core constraint that shaped software for seventy years dissolved. Writing code stopped being the hard part.

The Phoenix Architecture icon
The Phoenix Architecture
Dec 22, 2025

Regenerative Software

Software is entering a strange new phase.

The Phoenix Architecture icon
The Phoenix Architecture
Dec 21, 2025