When I deploy/publish software, there's usually nobody using it (just like my writing), but when eventually somebody actually uses it, I get to see what interactions they did. There's a lot of fine-grained, actionable feedback about what works and where users get lost. The first time a stranger succeeds in using my app to accomplish what they set out to do: woah, dopamine rush!
Each piece is it’s own small bet. You never know what’s going to resonate with people and often I surprise myself too. However, you also improve and your audience grows with you, rooting for you. I always enjoy reading whatever you’re writing Chao, so if you do enjoy it, keep writing :)
Another way to think about it - writing is you coming back to an idea and going deeper and deeper. Each time you get a little more clarity on the idea.
Each piece is it’s own small bet. You never know what’s going to resonate with people and often I surprise myself too. However, you also improve and your audience grows with you, rooting for you. I always enjoy reading whatever you’re writing Chao, so if you do enjoy it, keep writing :)
Thanks for the shout, Chao! I love this: I've come to realize that for writing, I am the "software".
To borrow a question I often here: "is it a bug or a feature?" By debugging our writing blocks, we discover the unique features of our writing
Thanks so much for the mention Chao, but this is just dawning on me that Thread Reader App is your product. Is that so??
Really glad to see this! Thanks for the shoutout.
Another way to think about it - writing is you coming back to an idea and going deeper and deeper. Each time you get a little more clarity on the idea.