←back to thread

Sell yourself, sell your work

(www.solipsys.co.uk)
449 points ColinWright | 1 comments | 3/25/2025, 9:35:00 PM | HN request time: 0.4s | source
Show context
simonw ◴[3/26/2025, 3:06:00 AM] No.43478469[source]▶

I have a personal rule which has worked really well for me: if I do a project, the price of doing that project is that I have to write about it.

Back when Twitter threads didn't suck (they could be viewed by people without Twitter accounts) I'd use those - tweet a description of my project with a link, then follow it with a few photos and screenshots.

These days I use my blog, with my "projects" tag: https://simonwillison.net/tags/projects/

I blog all sorts of other stuff, but if I was ever to trim back the one thing I'd keep doing is projects. If you make a thing, write about that thing. I wrote more about that here: https://simonwillison.net/2022/Nov/6/what-to-blog-about/#pro...

Projects with a GitHub repository make this even easier: describe the project in the README and drop in a few screenshots - that's all you need.

(Screenshots are important though, they're the ultimate defense against bitrot.)

I have many projects from earlier in my career that I never documented or captured in screenshot form and I deeply regret it.

replies(9): >>43478641 #>>43479552 #>>43479671 #>>43480222 #>>43480307 #>>43480952 #>>43482474 #>>43482775 #>>43483574 #
brulard ◴[3/26/2025, 9:27:00 AM] No.43480307[source]▶

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?

replies(3): >>43480653 #>>43481722 #>>43483107 #
1. rpastuszak ◴[3/26/2025, 12:54:00 PM] No.43481722[source]▶

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.