Articles

Lessons from building in the open: what worked, what didn't, what I'd do differently. They land here first, then in the newsletter.

  • Follow up on a cold email only when you can add one fact that did not exist when you sent the first one. Not a bump, not a polite reminder that you are still waiting: something the reader did not know before. Two follow-ups written that way beat six written in advance, because a sequence drafted before you send can only ever report that time has passed.

  • The right Repl.it alternative depends on which of Replit's four jobs you are replacing: the agent that writes the code, the browser environment, the always-on hosting with a public URL, and the bundled Postgres. Most disappointing switches come from swapping one of the four and discovering the other three were the part you actually relied on.

  • Replit alternatives fall into three lineages, and the useful move is to pick across them instead of inside one: browser IDEs that hand you a machine (GitHub Codespaces, CodeSandbox, Coder), agent builders that write the app for you (Lovable, Bolt, v0, Firebase Studio), and plain hosts that run whatever comes out (Vercel, Railway, Render, Fly.io).

Get ahead.

Get the best articles, carefully selected to save you time.

Featured

A pivot is often just the polite word we use with investors when the first company is dead and we have decided to build another one. And that is fine. Not because failure is noble, but because luck needs exposure: every market you enter, every product you ship and every channel you test is one more surface where something unexpected can land.

Projects

Brands

The essentials, by email.

What works, what does not, what I would do differently. Sent when I have something useful to say.