Post

Sam Rose
@samwho.dev

Heard from a few folks that they procrastinate publishing because they want to make sure it’s good enough and I totally get it, I worry about that too. But I’ve gotten pretty good at deciding enough is enough and going ahead anyway so here’s a thread with things I don’t like but decided were fine.

Simon Willison
@simonwillison.net

I like to remind people that nobody else will ever know how good the thing you WANTED to publish was, so all of those flaws that stand out to you are invisible to them (And you just posted them all here for everyone to see, with screenshots!)

Simon Willison
@simonwillison.net

My favorite advice for blogging remains that you should hit publish while you are still actively unhappy with what you have written, because the only alternative is a huge folder full of drafts and never publishing anything at all

25 reposts182 likes

Jukka Niiranen
@jukkan.bsky.social

Also, if you make your blog posts too complete and aim to address every possible question - there will be nothing left to comment on. It's far better to push something non-polished out there, get people to engage with it and be open to feedback and new perspectives. That's kinda the whole point.

Bite Code!
@bitecode.dev

I have the opposite problem. I want to publish something as soon as it's ready, but I know it's crap. I have to force myself to read it again and fix it. Ideally, hold again until the day after to see what I missed and only post then. When I don't, I always find horrible stuff right after posting.

Alex Kraieski
@kraieski.dev

I think it's easy to lose sight of the "logging" metaphor that blogging came from. Logging in-process knowledge acquisition candidly is largely the opposite of how schooling conditions us. In blogging, it feels like you can develop theses better to have an "A" paper, but constraints differ totally.