On writing, and not writing.
Most company blogs are SEO bait. Posts engineered to hit keywords, padded to fifteen-hundred words, structured for skimming, optimized for engagement metrics that don’t correlate with anyone learning anything. They exist because someone decided publishing twelve times a quarter is what a serious company does. They are correct that publishing twelve times a quarter is what someone does. They are wrong that it’s what a serious one does.
We’re building infrastructure that runs inside customers’ mobile apps in production. The engineering takes years. The trust takes longer. The publishing should reflect the engineering, not the marketing calendar. If there’s a hard week, we’ll write about what we learned the expensive way. If there’s a category observation worth your fifteen minutes, we’ll write that. If there’s nothing worth saying for three months, we’ll say nothing for three months.
This is Issue Zero. There is no Issue One yet. The first real essay lands when the runtime ships, which will be when it’s honest to write the thing we’ve been thinking. The drafts are real — you can see them below. The cadence is not a content calendar. It’s the cadence of having something to say.
If you want infrastructure thinking now, the manifesto is the longest piece we’ve published. It’s closer to a founder’s memo than an essay, but it’s honest about why this category needed to exist. Start there.
What you’ll get from this publication when it lands: long-form essays that respect your time by being longer than fashionable, drier than engaging, and more useful than convenient. Field notes from a hard problem, written by people doing the work, edited for the reader who already knows what AOT means.
The mailing list is your inbox. The publishing schedule is when something is worth saying. The signal is the signal.
— The Editor