Build in Public

# Week 12 — Anchor: "The 100% open rate was me" Type: Newsletter issue section + the seed for all Week 12 posts — Ninety days in, the number I am least proud of is the one I quoted most: a 100% open rate. Here is what it actually measured. For thirteen consecutive sends, my … Read more

# Week 11 — Anchor: "The track that was already a copy" Type: Newsletter issue section + the seed for all Week 11 posts — A store rejected one of my tracks for matching a stranger's file. The license was valid. That turned out not to matter. Here is what I did wrong, because that … Read more

The revenue report I promised you is $0 — and that is exactly why I am publishing it. Four weeks ago I put a public API on the internet from a server in my house. Last issue I promised to report revenue "whatever it is." It is $0. Here is the whole sheet, because hiding … Read more

# Week 9 — Anchor: "I launched a writing tool this week — the one I built because I kept forgetting my own fantasy world." Type: Newsletter issue section + the seed for all Week 9 posts — I launched a writing tool this week — the one I built because I kept forgetting my … Read more

This week I launched the AI resume optimizer I built as a physician — with a rule most AI tools refuse: it cannot invent anything. Every resume gets read twice: once by software, once by a human. Software goes first, in seconds, and it punishes formatting that buries the words it scans for. That's how … Read more

I put a public API on the internet this week — from a server in my house. For months, yt-transcript-api was a script I ran for myself: paste a YouTube URL, get the captions, get a summary, move on. It saved me hours. Then I realized the interesting question was not whether I could build … Read more

Why a doctor builds AI businesses at night — the systems, teardowns, and lessons from shipping software as a side-projecting physician.

The Sunday review ritual that fixed David Moniz’s content system — a repeatable teardown process for build-in-public workflows.

How a near-midnight auto-post almost shipped in the middle of the night — and the scheduling safeguards that prevent it.

The version number that lied and wrecked 19 environments — trust-but-verify lessons for automated deployments.

Two hours chasing a 403 that was never about the password — a debugging teardown with actionable lessons.

The 63 GB temp folder that killed the assistant three times — RAM tmpfs, OOM, and infrastructure limits in practice.