Writing Better
I recently got a note from Bianca asking about writing, which is a topic I’ve tried to write about before, some of what I’ve wrote on this topic:
- Writing for Consumption (2008!)- mainly included because I wrote it in 2008 and it’s funny to read my old writing style
- How to be a tech influencer (2021) - my advice on how to do tech content distribution
- Why and How I write (2021)
- What I learned writing An Elegant Puzzle (2019?)
- Experimenting with content and distribution (2018)
That said, I haven’t really nailed what I want to say, and this is just a collection of rough thoughts hence including it on Exuberant Sketches rather than Irrational Exuberance.
A paraphrased version of the question is:
You’re able to capture and explain thought processes and heuristics developed by engineers through experience. You explain in plain language social subtleties within organizations that everyone experiences but can be hard to describe. Is this type of writing a skill something that gets better with practice? I want to be able to write about engineering. I have the ability to articulate thoughts and ideas, but in fragments. I’m not able to organize them into something linear under a single topic.
I’ve developed a somewhat distinctive written style almost entirely by accident, and I think it comes down to a few things:
- Writing a lot - almost 650 posts over 14 years, albeit there was a stretch from 2012 to 2016 where I was struggling a bit and for the most part stopped writing
- Most of my early writing was tutorials with a focus on “no steps omitted.” I was frustrated with so many tutorials that left a lot of steps to the reader, and wanted to write tutorials that didn’t selectively abandon their readers. Some good examples of this are An Epic Introduction to PyObjC and Cocoa and Dreamier Dream Server with Nginx. Both of those are more than a decade old (and consequently very out of date), but that methodical writing style became an important pillar of my written voice
- Trying to keep the joy of writing alive by writing stuff that I enjoyed, including personal stories like Applying to the JET Programme, How the Digg team was acquihired, or about the Digg v4 Launch.
- I’m proud of my books, their reach, and their impact, but for the most part I center on the idea that I’m a niche writer who isn’t trying to write for everyone. For the most part I don’t write for anyone, instead I write to learn and to get ideas out of my head without forgetting them. For the most part I don’t edit my work, I often have typos and grammatical issues in my writing and so on. As my readership has grown a bit, I’ve finally come to the point of splitting out Exuberant Sketches as a way to annoy fewer people with my very rough work that I enjoy writing while still having a readership for my more finished work.
My writing is considerably better than it was a decade ago, and I think it could have gotten much better, much faster if I was more deliberate about writing for an audience rather than myself, but I found that less energizing so I didn’t and have gotten here a bit more slowly. A decade ago, I didn’t really have very interesting experience to write about or perspective to write from, so in some ways it’s been helpful to take a slower route to improvement.
My personal advice would be to look at everything you have, cluster some together, and try to coax it into a piece. Then publish that piece. Keep doing it until you run out of fragments to cluster together. I wouldn’t worry much about editing or the reader, just write. Publishing is a powerful thing, because it frees you from your obligation to what you’ve written. It’s also powerful because you will immediately have better ideas about what you should have done instead. Then you can go ahead and write another piece on the same topic.
When I tried to write the engineering strategy piece for Staff Engineer, the first version was Engineering strategy on Nov 5, 2020, and over the next 4 weeks I rewrote it entirely four times until I got to Write five, then synthesize. I really wanted to write the “canonical piece on engineering strategy,” although even though I’ve written five version I still don’t think it’s really struck much of a cord with folks yet (lol). That said, I almost never rewrite pieces at all, most stuff I just publish and move on, even if it’s bad.
Over time you’ll refine your approach a bit, and figure out what your best material is. At that point, you can work with a few friends on editing it into something more focused on the reader than the writer, if you want to. Until then, I’ve found that for the right reader the ideas will shine through and impact their lives even if your writing on a given piece isn’t that good. If you have an important perspective, sharing it in any format is a real gift to another person experiencing the same thing.
I guess I can end with an acknowledgment that I think folks with different backgrounds have a different experience writing on the internet. I occasionally have random folks ping me telling me that I have good ideas but my typos are embarassing and they don’t want to read what I write as a result. I don’t really know why people bother doing that, I went to a liberal arts school and I realize that my writing has typos in it? Oh well, I harbor some ill thoughts towards them but mostly try to ignore it, as I imagine most of them are trying to be helpful even they aren’t.