For thirty years I’ve been writing software, designing systems, arguing in front of whiteboards, and quietly accumulating the kind of opinions that come only from being wrong enough times. Until now, almost none of it has left the rooms where it happened. No blog. No talks. No public trace.
That is, by any reasonable standard for someone at this point in a career, abnormal.
I have a few honest reasons for the silence. Some of them are even good ones. I never wanted to write for the sake of writing — I dislike content produced because the calendar said so. I tried a Go series years ago and abandoned it after a handful of posts because I couldn’t sustain the rhythm without resenting it. I’ve been suspicious of the genre itself: the LinkedIn confessional, the “10 things I learned” listicle, the breathless announcement of an architecture pattern that’s been around since 2003. I didn’t want to add to the noise.
But silence has a cost too, and I’ve started to feel it. A senior architect with no public artifacts is, in a real sense, a designer with no portfolio. The work exists, but only inside companies — protected by NDAs, dispersed across Slack threads, lost in the next reorg. When I talk to peers, I have stories. When someone outside my circle asks what I think, there’s nothing to point them to.
So this is the compromise I’ve made with myself. I’m going to write — but only when the writing is a byproduct of real work, not a substitute for it. Architect’s Notebook is meant to be exactly what the name says: a notebook. Not a magazine. Not a course. Not a brand.
What this is
I think of myself, increasingly, as a critical observer of my own profession as much as a practitioner of it. Thirty years gives you a strange vantage point. You watch the same battles refought every five years under new acronyms. You see ideas that were obviously good get rebranded as revolutionary. You see ideas that were obviously bad come back into fashion because the people who lived through them the first time have moved on or stopped speaking up.
This notebook is where I want to speak up.
Most of what I’ll write here will be field-level: real architectural decisions, real tradeoffs, real things that didn’t work and the reasons they didn’t. Not abstractions. Not best-practice posters. You won’t find Backstage setup tutorials here, or .NET how-tos with step-by-step screenshots. I’ll leave that to people who enjoy writing that kind of content — and there are already more than enough of them. What I’m interested in is the layer above: why you chose this approach, what you gave up by choosing it, and what you’d do differently with eighteen months of hindsight.
Personal anecdotes will appear when they serve a technical or professional point. They won’t appear because vulnerability is the LinkedIn currency of the moment.
Why now
The honest answer is that I’m at a transition. After many years in the same group, I’m preparing to take on more responsibility somewhere new — likely in a product company or scale-up where the architecture decisions matter and the people taking them are accountable for them. That kind of move doesn’t happen on the strength of a CV alone. The people I want to work with read what other people write before they meet them. Right now, there’s nothing for them to read.
So part of starting this notebook is, frankly, a portfolio decision. I’d rather say that openly than pretend otherwise. But I’ve also reached a point where I have things I want to say that I haven’t found written elsewhere — at least not from the perspective of someone who’s been in the engine room rather than commenting from the conference circuit. The two motivations align well enough for me to start.
What I’m asking of readers
Not much. If you find an article useful, that’s enough. I’m not building a mailing list, not selling a course, not inviting anyone to “join the journey.” If something I write irritates you — and some of it will, because I do hold opinions and I’m not going to hide them to keep the comment section friendly — write back. I’d rather have one sharp disagreement from someone who read carefully than fifty agreeable nods from people who skimmed.
The posts here will appear when they’re ready, not on a schedule. I’d rather publish six honest articles a year than fifty competent ones. If a topic doesn’t have something worth saying that I haven’t seen said better elsewhere, I won’t write it.
That’s the contract. Welcome to the notebook.