I would love to do this as well, but I'm put off by the time it would take away from pushing the project itself forward. How much time does it generally take for you to make a blogpost for a project?
This gets much easier with practice. One exercise that that worked for me was to force myself to share anything (projects, til, ideas, experiments, advice) daily for 111 days. Then scale down.
Compare untested.sonnet.io and sonnet.io/projects
The latter took 10 years to have a list of projects. With the former, there’s almost no friction, although I have spikes and slower periods.
Also, people appreciate people who share and talk about their work, and that can lower the bar for things like correct grammar/vocab/clear structure.
To improve my overall fluency I made a writing tool that separates editing from writing: enso.sonnet.io.
Another thing that can work well are weekly updates/summaries. But this gets harder if you struggle with building habits and prefer shorter feedback loops.
PS. I'm not at Simon's level here although he is one of my inspirations - my main untested feed posts take 1-2 hours minimum, the smaller notes/branches can be < 20 min.
PPS. I'm working on a short list of actionable tips / places to share work. Hit me up via email and I'll send it over when it's done.
Five paragraphs, about an hour or less. Don't overthink it. Below are some examples from my woodworking, but I think they illustrate the concept. The important thing to remember is the blog post is not the project: it is a very quick overview pointing readers to the project. Built up over time, these quick overviews add up to a longer representation of your body of work, which you can use to sell yourself.
