#systems - Leaflet

UI Is a Conservation Layer

Why the user interface is the last to become regenerative

Jan 21

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.

Jan 7

The Phoenix Architecture

The System Is the Asset

Why Regeneration Does Not Mean Starting Over

Jan 5

The Phoenix Architecture

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.

Jan 2

The Phoenix Architecture

Evaluations Are the Real Codebase

Why behavior outlives implementations

Dec 29 '25

The Phoenix Architecture

The Gradient of Trust

Better shapes beat better prompts

Dec 28 '25

The Phoenix Architecture

Code Was Never the Asset

Why AI makes the hidden economics of software unavoidable

Dec 24 '25

1

The Phoenix Architecture

Pace Layers and AI Integration

Not all software should change at the same speed.

Dec 23 '25

2

The Phoenix Architecture

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.

Dec 22 '25

5

The Phoenix Architecture

Regenerative Software

Software is entering a strange new phase.

Dec 21 '25

4

Tag: #systems

UI Is a Conservation Layer

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

The System Is the Asset

Conceptual Mass and the Compaction Discipline

Evaluations Are the Real Codebase

The Gradient of Trust

Code Was Never the Asset

Pace Layers and AI Integration

The Death and Rebirth of Programming

Regenerative Software