dirk ottenheym

The twelve is the center of the target. A bullseye. When a student hit it for the first time, bow raised, one eye closed, breath held, you could see the recognition before they said anything. Something had landed exactly right. Over years of running school programs, high rope courses, GPS tours, raft building on Thursday afternoons, I watched that moment hundreds of times. The twelve always meant the same thing. Perfect contact.

I have one too. An inner center. When a spark hits it, something shifts immediately. Forward lean. Eyes open. Let's go.

A Monday morning in March. A café in Vietnam. I had not planned to watch a YouTube tutorial. Then I did. Someone building a local knowledge base from scratch, step by step, careful and excited. Around minute twelve I sat forward. I already built this. I remembered exactly the morning I figured it out. The wrong queries. The index that rebuilt too slowly. The moment it finally returned results in under a second. I kept watching. I was grinning. The twelve, hit.

The memory arrived before anything else. The figuring out. The phase before something works, when you are deep inside a problem that resists, and the resistance is interesting, and you stay because understanding is so close you can almost touch it. That phase. I love that phase more than the finished thing.

When something lands, a question, a broken system, the edge of something I have not yet understood, something wakes up. A very specific energy. Precise. Impatient. Delighted. It can show up in the night waking up. It can show up at five in the morning with the first tea still cooling. It just wants to know how the thing works. And then it wants to build it.

The System Is Always There

When I led school groups through a week, thirty teenagers at a youth hostel from Monday to Friday, building programs around high rope courses, raft building, bow shooting, GPS tours, canoe days on the lakes, I spent most of my time reading. The group. Every group is a living system and a living system broadcasts everything. Who is carrying more than their share. Who is one bad afternoon away from breaking. Which two people, placed together, create stability for everyone around them. The reading happened on its own, the way you notice the one loose wheel on a shopping cart the moment you pick it up.

Enter any room, any team, any workflow, and the question arrives on its own: where is the energy moving, where is it slowing, what is the one thing that, if it shifted, would shift everything else? I was reading Luhmann in a notebook on the U-Bahn during the Berlin years, his theory of social systems, dense and unforgiving, and recognizing with some surprise that he was describing something I had been doing since I was twelve.

The same curiosity that reads a group reads a codebase. Reads a morning routine. Reads the architecture of a website before a single line is written. The question is always the same. What are the parts. How do they connect. Where is the friction. And what wants to move.

In coaching sessions I built a visual tool, an interactive canvas where someone could place the elements of their life and watch the gravity between them become visible. The client would stare at it and say: I never saw it like that. That was the whole point. Make the invisible visible. Give the system a shape it can be looked at.

Let's Go

The reading is one half. The other half is what happens the moment the structure becomes clear.

In those groups it happened fast. A raft building challenge on day three and the team that looked cohesive on Monday has quietly fractured. You see it before anyone says a word. A different pairing for the afternoon. A GPS tour that puts the quiet one in front. And the system responds. You could feel it. The group's breathing changed. They breathed differently when the tension released. That speed, from reading to responding, from seeing to moving, was what made the work feel alive.

Building has the same shape. The understanding comes first: how a database query moves through an index, why one architecture is lighter than another, what the tool needs to see to do what I want. And the moment the structure becomes clear, something shifts. A forward lean. An energy that arrives before any conscious decision. Something says let's go.

I stay with a problem until that moment arrives. Until something opens. The bar is understanding. A workaround is just a postponed question, and postponed questions have a way of becoming expensive. I want the actual reason the thing works. That standard tends to turn one question into four, and those four are always more interesting than the one I started with.

There is a pleasure in precision that I find hard to describe without sounding obsessive, and maybe it is a little obsessive. A piece of code that does exactly what I asked it to do. A database query that returns the right result in the right shape in eighty milliseconds. A website born in an afternoon, live today, built by a human and an AI working together because the architecture was clear from the start. I know my tools. I know what I am building toward. And when it comes together, when the last piece fits and the whole thing runs, that is the twelve.

What This Looks Like on a Tuesday

Since May 2025, most of my days have had this shape: writing in the early hours, then building. Claude Code, Obsidian, Next.js, SQLite, Vercel, custom shell commands. Two websites built and deployed. A full review system running as AI commands inside my vault, pulling notes, calendar, and tasks into a single morning briefing with one keystroke. A coaching tool built in HTML and used live with a client. A personal finance dashboard. A full-text search index across a thousand notes, rebuilt in seconds when I add something new.

All of it from a backpack, a MacBook, and a succession of hotel rooms in Southeast Asia. The constraint turned out to be a design principle. Seven kilograms. One machine. Everything had to be light, portable, and genuinely necessary, or it did not survive the next move. Precision as a lifestyle, long before it became a method.

The curiosity is genuinely young. I remember the morning I understood how SQLite full-text search works, how it tokenizes words, how the ranking algorithm weighs frequency against document length, why proximity matters to relevance. I read about it for two hours because I had just built something that used it and I wanted to understand the thing I had made. The building creates the question. The question pulls deeper. Deeper generates the next thing to build. I have started so many Tuesday mornings with a completely different problem than the one I went to sleep thinking about, because something I built on Monday opened a door I had not seen before.

The Other Half of the Room

Everything I have published so far comes from the quieter side. Twenty-two articles about observation, presence, the quality of attention at a particular hour of the day. That writing is real and it is mine. It is also one half of what actually happens here.

The building half gets its address here.

This is the Forge. The place where I write about what I build and what I learn building it. The same voice, different terrain. Field notes from inside the work: what it feels like to watch a thousand notes become searchable in a second, what I learn about my own thinking when I try to make it legible to an AI, where a system broke and what the break revealed.

Something lands. The twelve gets hit. We get to work.