Explanation on vshuraeff — Infrastructure. DevOps. Cloud.

Why agent-first principles

Mon, 01 Jan 0001 00:00:00 +0000

The shift in who reads code

For most of software history, design principles were written for a reader with a particular set of limits and strengths: a human sitting in an IDE, holding a rough mental map of the codebase, able to ask a colleague when the map runs out, and slow enough that a little extra indirection rarely mattered. SOLID, DRY, and layered architecture all assume that reader.

That reader is no longer the primary one. In an agent-first codebase, code is written, reviewed, and analyzed primarily by an agent — an LLM-driven program that reads, writes, and reviews code via tools. Humans still set intent and constraints, and still approve the changes that matter, but they rarely read the code line by line anymore. The code itself is authored and re-authored by agents, commit after commit, often faster than any human could review in full.

The garden model

Mon, 01 Jan 0001 00:00:00 +0000

A codebase as something tended, not built once

The metaphor GARDEN takes its name from is deliberately unglamorous: a codebase is a garden that agents continuously tend, not a building that is constructed once and then occupied. A building, once erected, mostly just stands there; a garden left alone does not stand still — it grows wild. Paths close over, beds run into each other, one aggressive planting crowds out everything nearby. Tending is not a one-time setup cost; it is an ongoing practice that has to keep pace with how fast the garden grows.

Relation to classic principles

Mon, 01 Jan 0001 00:00:00 +0000

GARDEN did not invent six principles from nothing. Each one inherits from an established line of software design thinking, and each one also weakens or rejects a specific part of that lineage where the classic formulation assumed a reader GARDEN no longer treats as primary: a human navigating by accumulated familiarity, in an IDE, with time to ask a colleague. This document walks the lineage classic principle by classic principle, states what each contributes, what is kept, what is weakened, and what is rejected, and grounds each judgment in agent mechanics rather than taste. The condensed "inherits from / rejects" line for each principle appears in GARDEN principles; this file is the expanded reasoning behind it.