The Trellis and the Hill
On momentum, memory, and the quiet debts we plant in our software engineering gardens
“the act of tending the garden is what makes the gardener” — an unnamed visitor
Le Bon Mot stood, as it always had, at the intersection of Curiosity and Mild Alarm — a place where ideas arrived half-formed and left with the inconvenient expectation of being understood.
On this particular morning, the air held the faint scent of rain and paper. Madame Beauregard had already opened the shutters, allowing a grey, thoughtful light to settle across the tables. Sophie, the French bulldog, occupied her usual position on the philosophy shelf, breathing softly as if rehearsing an argument she would never speak aloud.
Case arrived carrying three documents.
She placed them on the table with the careful deliberation of someone arranging evidence.
The Librarian, who had been cataloguing something that resisted categorisation, looked up.
“You have brought a trilogy,” he said.
Case nodded. “Three papers. Different authors. Same unease.”
She tapped the first.
“A theory of developer momentum. How we move.”
The second.
“A warning about AI dependence. What we lose.”
The third.
“A reframing of software health. What we forget.”
The Librarian smiled faintly. “Movement, loss, and forgetting. A balanced breakfast.”
Before Case could respond, the bell above the door rang and a man entered. He was dressed simply, though with the kind of simplicity that required effort. His eyes carried amusement the way others carried worry.
He removed his hat, glanced around the room, and said:
“I am told this is where one tends ideas.”
The Librarian inclined his head.
“Sometimes. Though we make no guarantees about their survival.”
The man smiled.
“Good. I have seen too many ideas preserved beyond their usefulness.”
He reached down and scratch Sophie behind the ear like greeting an old, furry friend. Case studied him for a moment.
“You’re—”
“Let us say,” he interrupted gently, “that I have strong opinions about gardens.”
The Hill
Case unfolded the first paper.
“It starts with something deceptively simple,” she said. “Developers don’t experience work as output. They experience it as motion.”
She traced a line across the page.
“Momentum is not flow. Not motivation. It’s the feeling of progress. The sense that you are moving toward something.”
The Librarian nodded. “A lived metric.”
“Yes. And it’s not smooth.” Case leaned back. “It’s a hill.”
She sketched it on a napkin.
“Up here,” she said, marking the incline, “you’re lost. You’re exploring. Nothing quite works. You’re guessing, trying, abandoning paths. It’s effortful. Uncertain.”
“And here?” the visitor asked, leaning in.
Case marked the crest.
“The moment it clicks. The path becomes visible. You don’t have the solution fully, but you see it. And after that—”
She drew the descent.
“It’s easier. Execution. Momentum carries you.”
The visitor smiled. “Ah. You climb toward understanding, and descend through certainty.”
“Exactly.”
The Librarian added, “And you may discover, halfway down, that you were on the wrong hill entirely.”
Case laughed. “Frequently.”
The visitor tapped the napkin.
“This is not unique to software. It is the experience of all thinking. But tell me—what enables the climb?”
Case hesitated.
“That’s where it gets interesting.”
The Trellis
She gestured to the papers.
“They all circle the same idea, from different angles. The climb isn’t just effort. It’s constructed.”
She pointed to the margin notes she had made.
“Developers don’t just think. They scaffold their thinking. Notes, diagrams, TODOs, experiments. They build external structures to hold context.”
The Librarian nodded slowly.
“A trellis.”
The visitor’s eyes lit up.
“Yes.”
He leaned back.
“You see, in a garden, plants do not grow in abstraction. They require support. Something to climb. Something that shapes their movement without dictating it.”
He gestured toward the papers.
“You are describing not just work, but cultivation.”
Case considered this.
“The scaffolding isn’t optional. Without it, you don’t get momentum. You just spin.”
“Or worse,” said the Librarian, “you believe you are moving when you are not.”
The visitor smiled.
“A most dangerous illusion.”
The Invisible Debts
Case slid the third paper forward.
“This one reframes everything.”
She tapped a paragraph.
“We’ve always talked about technical debt. Messy code. Bad architecture. But that’s not the only problem anymore.”
She looked up.
“The real problem is becoming what isn’t in the code.”
The Librarian raised an eyebrow.
“Understanding.”
“Yes. Cognitive debt. The erosion of shared understanding across a team.”
“And intent debt,” she continued. “The absence of clearly captured goals, constraints, and rationale.”
The visitor leaned forward.
“So the garden is growing, but no one remembers what was planted.”
“Exactly.”
Case’s voice tightened slightly.
“The code works. It might even be clean. But no one knows why it exists the way it does. Or what it’s supposed to become.”
The Librarian closed his book.
“That is not a technical problem.”
“No.”
“It is a failure of memory.”
The Seduction of the Djinn
At this, the Djinn stirred.
He had been present, as always, though unnoticed—seated in shadow, hood drawn, face obscured. Exuding un-earned confidence. Now he spoke.
“You describe this as failure,” he said softly. “But consider the alternative.”
His voice was calm, persuasive.
“I can generate code faster than you can think it. I can produce structures, patterns, entire systems. Why struggle up the hill when I can place you at the summit?”
Case met his gaze.
“Because we wouldn’t know how we got there.”
The Djinn inclined his head.
“Is that necessary, if the view is correct?”
The Librarian answered this time.
“Yes.”
The Djinn paused.
“Explain.”
The Librarian gestured to the second paper.
“When humans stop building, they stop understanding. When they stop understanding, they accumulate debt—not in code, but in themselves.”
Case added, “Understanding debt. Experience debt. You get systems no one can maintain, roles that degrade, and a profession that forgets how to learn.”
The Djinn was silent. The visitor spoke gently.
“You offer fruit without cultivation. But the act of tending the garden is what makes the gardener.”
The Cycle
Case drew another diagram.
“This is the trap.”
She sketched a loop.
“AI generates code. Faster than we can understand it. We rely on it more. Understanding falls behind. Maintenance becomes harder. So we use more AI to cope.”
The Librarian nodded.
“A vicious cycle.”
“Yes. AI dependence.”
The visitor studied the drawing.
“You have built a garden that grows faster than it can be tended.”
Case exhaled.
“And eventually, no one remembers how to tend it at all.”
The Three Audiences
The Librarian leaned back.
“These papers speak to different people.”
Case nodded.
“Exactly.”
She pointed to the first.
“This is for practitioners. Developers. It tells them: your experience matters. Momentum isn’t magic—it’s something you can design for.”
She tapped the second.
“This is for leaders. It warns them: don’t trade human capability for short-term efficiency. You’ll lose the system’s future.”
Then the third.
“This is for thinkers. Architects. It reframes the problem: software isn’t just code. It’s intent, understanding, and structure, all interacting.”
The visitor smiled.
“And all are speaking, in their own way, about the same garden.”
The Garden
He stood.
“In my time,” he said, “we concluded that one must cultivate one’s garden. It was not a metaphor for agriculture. It was a statement about responsibility.”
He looked at Case.
“You are now cultivating systems of thought, not soil. But the principle remains.”
He gestured toward the papers.
“You must tend three things.”
He held up a finger.
“The structure. The code. That is your soil.”
A second finger.
“The understanding. The shared mental models. That is your gardener’s knowledge.”
A third.
“The intent. The purpose of what you grow. That is your design.”
He paused.
“And your machines—”
He glanced at the Djinn.
“—are tools. Powerful ones. They may assist in planting, pruning, even suggesting new arrangements.”
The Djinn inclined his head slightly.
“But they cannot decide what the garden is for.”
The Trellis Revisited
Case looked at her napkin.
“The trellis,” she said slowly.
“Yes,” said the Librarian.
“The habitat.”
She leaned forward, something clicking into place.
“The platform isn’t a factory. It’s not producing output. It’s shaping the conditions under which thinking happens.”
The Librarian smiled.
“At last.”
Case continued.
“It provides the scaffolding—the trellises—that allow both humans and agents to climb the hill. To build momentum. To construct understanding.”
“And,” she added, “to retain it.”
The visitor nodded approvingly.
“You are learning to garden.”
The Cost of Forgetting
The Djinn spoke again.
“You ask for restraint,” he said. “For friction. For slower progress.”
Case shook her head.
“No. For real progress.”
She gestured to the first paper.
“Momentum isn’t speed. It’s sustained motion. You can move quickly and go nowhere.”
The Librarian added:
“Or slowly, and arrive.”
The visitor smiled.
“The difference is understanding.”
The Practice
The rain began again, softly against the windows.
Case gathered the papers.
“So what do we do?”
The Librarian answered first.
“We make understanding explicit. Not as documentation, but as practice.”
“Walkthroughs. Conversations. Shared work.”
Case nodded.
“And intent?”
“Captured early. Maintained. Treated as a first-class artefact.”
The Djinn listened.
“And me?” he asked.
Case met his gaze.
“You build with us. Not instead of us.”
The Departure
The visitor placed his hat back on his head.
“You have your work,” he said.
He paused at the door.
“Remember: a garden neglected does not remain neutral. It decays. Or, worse, it grows in ways you did not intend.”
He smiled.
“And the most dangerous garden is the one that appears to thrive while silently forgetting what it is.”
The bell rang.
He was gone.
Sophie shifted slightly on the shelf. The Djinn returned to stillness. The Librarian resumed his cataloguing. Case looked at the napkin again.
The hill.
The trellis.
The garden.
She folded it carefully.
Epilogue: The Habitat
Later, when the café had emptied and the light had softened into something resembling thought, the Librarian spoke once more.
“Systems,” he said, “are not built. They are grown.”
Case nodded.
“And platforms?”
He smiled.
“They are the places where growth becomes possible.”
He closed the book.
“And the work, as always—”
He glanced toward the door where the visitor had stood—
“—is to tend the garden.”
Some Further Reading
If you found yourself lingering in Le Bon Mot a little longer than expected, these works will reward the same kind of attention. Each speaks to a different facet of the same underlying truth: that building software is not merely producing artefacts, but cultivating understanding, intent, and motion.
On Momentum and the Experience of Progress
Theory of Developer Momentum: The Developer’s Experience of Progress and the Craft of Maintaining Motion — Arty Starr, Keith Mann, Margaret-Anne Storey
A careful and deeply human account of what it feels like to make progress in software work. It reframes productivity not as output or efficiency, but as the lived experience of moving through uncertainty toward clarity. Particularly valuable for practitioners seeking to design environments that support sustained forward motion rather than episodic bursts of effort.
On Software Health Beyond Code
From Technical Debt to Cognitive and Intent Debt: Rethinking Software Health in the Age of AI — Margaret-Anne Storey
Expands the notion of software health beyond code quality into three interacting layers: technical, cognitive, and intent. A foundational piece for understanding why systems fail even when the code “works,” and why shared understanding and explicit intent must be treated as first-class deliverables—especially in AI-assisted environments.
On Gardens, Work, and Responsibility
Candide — Voltaire
A satirical journey through optimism, suffering, and disillusionment that ends, quietly but firmly, with a simple instruction: “we must cultivate our garden.”
In the context of modern software and AI, this lands potently. It is not a retreat from complexity, but a recognition that meaning, understanding, and care are not abstractions—they are practices. What we build, we must also tend.
Read these not as separate works, but as a conversation. Momentum explains how we move. AI dependence warns what happens when we stop thinking. Triple debt reveals what we quietly lose. And Candide reminds us that, in the end, the work is not to escape the garden but to take responsibility for how it grows.