Blog
Building in public.
Notes on shipping, and on marketing your work without becoming a marketer.

LinkedIn post generators for developers: what they get wrong
Paste a topic, get a post. That loop works fine until the person using it is a developer with something real to say, and the missing ingredient shows.
5 min read

Ship notes: what to write down when the work was not a commit
Your commit log is an excellent record of what happened in a codebase, and a blank record of everything else you shipped. A ship note is the one-line fix.
5 min read

Webhook or access token: what to give a tool that reads your repo
Two asks that look equally routine in a setup wizard, and are not equivalent in what they can see, what they hold, or what a breach at the vendor costs you.
6 min read

What to post on the weeks you shipped nothing
Usually the answer is nothing, and that is not a cop-out. But four kinds of post are honest on a week with no release in it, and one test rules out the rest.
5 min read

Build in public without becoming a marketer
Building in public works. Becoming a marketer to do it does not. The difference is whether the posts come out of your work or out of a content calendar.
6 min read

Marketing for solo developers who hate marketing
You do not need a funnel, a personal brand, or a content calendar. You need people to find out that the thing you built exists. Those are different problems.
6 min read

How to turn GitHub commits into LinkedIn posts
Your commit history already records everything you shipped. How to turn it into LinkedIn posts, by hand first, and then without doing it by hand.
7 min read

Why PeerPost stays quiet when you have not shipped
Every content tool is sold on volume. Ours sometimes writes nothing at all, on purpose - the most important decision in the product, and the reasoning.
6 min read