Skip to content
DuranteDurante
ALL SYSTEMSGet Access

27 weeks · 54 posts · Written while building

Field notes from a personal AI OS in flight

Every Tuesday, an evergreen essay on what I'm learning while shipping DuranteOS. Every Friday, a dispatch from the week. Roughly 108,000 words and counting — for builders who'd rather watch the foundation get poured than read the press release.

Subscribe · Tuesday essay

Around 3,800 builders read this weekly.

W27 of 27

After Twenty-Seven Weeks: What the Series Was For, and What I'm Building Next

The series ends here. Twenty-seven weeks of evergreens, twenty-seven Friday dispatches, six months of writing while building. The last thirty-three weeks produced about three hundred and five commits, a Studio platform that has been live for one hundred and three days, a knowledge graph the writing forced me to articulate, and a list — drawn from the posts themselves — of what I am committing to build in the next quarter. This essay closes the arc and names the next one.

W20 of 27

Six Months of DOS: What Changed, What Endured, What Surprised

Twenty-six weeks of building a personal AI operating system in public. Twenty essays in this series so far. Roughly twelve packs in various states of readiness. Around eighty workflows. About 3,800 newsletter subscribers. Zero paying customers, with four months left on the founding-customer clock. Here is the honest half-year retrospective — what survived contact with reality through Q1, what I was wrong about, what I never saw coming.

W19 of 27

The Knowledge Portfolio for an Indie Founder Building in Public, Audited at Week 25

Andy Hunt and Dave Thomas argued in The Pragmatic Programmer that engineers should manage their learning the way an investor manages a portfolio — diversify, invest regularly, review periodically, accept calculated risk. Twenty-six years later, applied honestly twenty-five weeks into building a personal AI OS, here is what my actual portfolio looks like, where the binding constraint is, and what I am rebalancing this quarter.

W14 of 27

The One Reference Customer Strategy: GTM for a Personal AI OS, Sketched Before the Customer Signs

Studio shipped eighteen days ago. The reference customer has not signed. Most go-to-market plans optimize for ten paying customers in the first quarter — mine optimizes for one, by July, with a year-long deep collaboration that produces the patterns, the case study, and the next ten customers as a side effect. This is the strategy I am committing to in public before I have the customer, because writing it down sharpens the hunt.

W12 of 27

Builder's Compass: Two Years In, ~3,800 Subscribers, and What I've Learned Teaching Architecture

I started Builder's Compass in late 2023 because I was tired of giving the same architectural advice in five different DMs every week. The list is now ~3,800 deeply-engaged software architects, founders, and senior engineers, the cadence has held for the better part of two years and a quarter, and the slow growth has taught me more than the spikes did. Here is what worked, what did not, and the one piece of advice I keep giving away to founders asking whether to write publicly.

W03 of 27

Why I Just Left a Steady Practice to Build a Personal AI Operating System

Twenty years as a software architect. A teaching post on an MBA program. A consulting practice I spent five years building. I am closing all three to spend my full attention on a private experiment that does not yet have a paying customer. This is the decision essay, written from inside the decision — the trade-off, the fear, and the thesis.

The 27-week arc · A single body of work

Twenty-seven weeks. Two posts a week. Six months of writing while building.

Week

Tuesday evergreen

Friday dispatch