Writing vs Coding
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!
I am struggling to find a cadence in writing. It makes me question why I want to write and what purpose does my writing serve? And then, why is it so much easier for me to write software than to actually just write?
When I write software, I get an instant response. It's usually reporting an error, but then I fix the error and when it works it's instant gratification, due to something I did. There’s that familiar dopamine rush.
Writing is more lonely. When I put something out, even when I'm lucky and someone chances upon it, how do I know what they get out of it? A writing community like Write of Passage definitely helps. As
points out, an accountability group like the one we're both in helps provide feedback to one another's writing. I definitely recommend it.However, there's one aspect that I especially miss in writing software. When software is useful, folks actually come back over and over again and that is where the magical flywheel starts.
I've come to realize that for writing, I am the "software". I am successful when people do come back, but it's super rare that someone will come back again to something I wrote before. However, I can aspire that some folks will look forward to more of my future writing. So, they can come back again and again to read me or my writing.
And that's why a writing cadence and a virtuous cycle of improving my writing is so critical.
If coding is so different from writing, why don't I just stick to my knitting? Why do I write?
It boils down to two big reasons:
Writing helps me clarify my thinking and in so doing, helps me understand myself.
has explored quite a bit on this reason eg.
To borrow
’ excellent phrase, I have a connection craving. It's truly delightful to be in a community of writers and people who love ideas. In our last accountability group meeting, when I brought up this very topic of how coding and writing are different. I heard so many interesting product ideas of how we can create better tools to receive writing feedback. I can listen and brainstorm about product ideas all day!
All this is to say, I love writing especially when I am in the flow. But at other times, it’s a grind and a struggle and I feel the pressure to write regularly. How can I make the process more playful, experimental and fun? How do you do it? I’m all ears
Discoveries
Most Twitter threads are kinda ephemeral, but @ThreadReaderApp is all about finding the gems that are worth keeping. So, I’m experimenting with calling out threads that have stuck in my head for more than a week. Here are 3:
With Oppenheimer at the movies, it's a good time to learn about how *constructive* nuclear fusion can be, and @Andercot gives us a wonderful primer
- is a master storyteller, and this tale will leave you laughing and crying
Are these the future of advertising? @The_AdProfessor showcases some of the most engaging ads
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