Build Daily at builddaily.io
Build Daily is the publication where I produce content consistently. A single surface — builddaily.io — covering field-notes essays, daily logs, project pages, a library, and a chat agent over the whole corpus. The thing being shipped is the publication itself, on a cadence.
What's on it
Essays as the work crystallizes.
Adobe APIs, consumer-lending engineering, StoryBrand, building local-first coding agents.
What got built today.
Short, dated, public. The discipline of writing what happened that day.
What I'm actually shipping.
Sage Daily, Paid Daily, and the work on the publication itself.
An agent over the whole corpus.
Ask it anything; it answers from what I've actually written.
Why a publication and not a portfolio
A portfolio is a brochure — frozen, descriptive, dated the moment it ships. A publication is alive. It updates. It produces. The cadence becomes its own proof: this person is doing the work today, not in 2024.
For an engineer who's selling AI capability, the difference matters. The buyer wants to know whether you ship. A publication that's been adding posts every week, with real projects on it, answers that question before they ask.
The schedule is the deliverable. Everything else — the chat, the project pages, the library — earns its slot because it's served by something that keeps shipping.
How the chat fits
The Personal Agent on the homepage reads the same corpus that drives the rest of the site — posts, projects, daily logs. Ask it what I've been working on, what my stack is, what I think about a tool — it answers from what's already published. The privacy review keeps anything not appropriate for public viewing out of the corpus; inference runs locally on Ollama; the chat is exposed through a Cloudflare Tunnel.
The chat isn't the product. It's an interface onto the publication.
Visit
Posts, daily logs, projects, the chat. Updating.