I build fast now. Agents write most of the first draft, I review and redirect and merge, and on a hot side project I'll push close to a hundred commits in a month.
Almost none of it gets seen.
That took me a long time to admit, because it isn't a tooling problem. It's me. I have a distribution problem wearing a productivity costume.
Four things I've worked out.
Nobody is grading you. I had a panel in my head. Senior devs, arms folded, waiting for me to post something so they could point at the parts an AI wrote. That panel does not exist. I checked. I posted things, some of them half-baked, and the reviewers never showed. What's actually there is my own taste aimed back at me, and my taste is always ahead of my output. That gap never closes, so I stopped waiting on it.
The people you're scared of are busy. Your launch is a two-second scroll in their day. The worst case isn't a roast. It's silence. Silence costs nothing, which is a strange thing to spend a career avoiding.
Volume beats polish. I kept trying to make the first thing good enough that showing it wouldn't hurt. The first one hurts no matter how good it is. What helps is number ten. By then it's boring, and boring is the point. A wall of "here's what I shipped this week" builds more trust than one big launch, because it shows a habit instead of a highlight reel.
Trying harder doesn't work, so build the thing. I treated this as a discipline problem for a long time. Be braver, post more. That worked for about a week, every time. What worked was making the behavior cheap. My failure mode had a shape. Merge a PR, feel good for ten minutes, never turn the diff into a sentence anyone could read. So I built Merge & Tell to do that part. Merge a PR, get a draft written from the actual diff, in my voice, sized for whichever channel it's headed to. I read it, fix a line, publish it or throw it out. The fear is still there. It just costs one click instead of an evening.
I've made 105 posts since launching two weeks ago. Before the app I would have had one or two.
The general version has nothing to do with my product. Find the exact step where you stall, and put a machine on that step. Not the fun part. You don't need help with the fun part.
Curious what everyone else does here. Do you have an actual forcing function for distribution, or is it still willpower and a Monday reminder?