Protip: Write for you

What surprises me most about the whole exercise is how overwhelmingly bad I am at writing. More than 80% of the content I've written has been thrown away. If I wrote code like this I'd have been out of work long ago, but I just can't bring myself to go on permanent record with half-baked poorly thought out blog posts.

I hate to put this so bluntly, but many people out there lack this kind of restraint. As a consequence, there's just a universe of truly awful writing online. The Joel Spolskys and Steve Yegges are really few and far between.

So yeah, write for you, but if you don't mind, could you do the world a service and write for the rest of us too? We'll all be better for it.

I was bored, so I did.

Within a few months, I had founded a magazine. My co-founder and I bootstrapped it, so we didn't have access to the highest caliber of writers. Consequently, we did a whole lot of development work; taking writers with passion and some technical flaws and working with them until they could bang out some good quality content.

I learned something really valuable working with young writers. The 'write for you' advice is great...to a point. If you really want to become a good writer, you need to write for an editor. Find someone you trust and get him/her to butcher your writing. Write for that person.

The problem with writing for yourself is that it is too easy to say, "well, the audience didn't come because x." (where x != my writing sucks)

The joy of writing for a good editor is that you will improve faster than you can possibly imagine. And then, you can say, "who cares about an audience, I'm a better writer now."

You can become a great writer...anyone can. Hell, if you can write code, you're already 95% of the way there. My email address is on my profile - if you want someone to edit your stuff, send me some mail...

Little controversial, but this is the first time in my life I actively care for a blog I've created. And the reason? I don't care about the statistics.

Previously my main priority was getting traffic. I became obsessed with looking at statistics to see how much traffic I'd gained. I spent far far too much time looking at statistics, when instead, I should have been doing, what I hope I'm doing now. Writing content that I will want to read again.

Other ways I deal with this need is carrying physical notebooks and a pen just about everywhere I go. Sometimes I turn them into blog posts. Sometimes I turn them into stories. Right now there are about six game ideas and four business ideas in the notebook next to me, as well as dozens of proto-essays. My blog likewise has almost twice as many "draft" essays than published posts.

This wasn't the norm for me two years ago. If you were to give me a page and a pen then, it would be blank for months. I made a decision to make it easy and effortless to write down ideas and thoughts. That meant carrying around a notebook and pen to many places I went. I also started doing stream-of-thought notes to try and jog my noggin when I was first starting out.

The takeaway here is to just get started. All my early stuff is garbage now, but it served as a good first wave to get me in the habit of writing.

The goal is to write things that come from the heart as well as the brain, that leverage your passions and appeal to an audience, all at the same time. In other words, the goal is, as usual, somewhere in the middle.

If your starting point is that you think nothing of your own passions, interests, and write whatever you think will please an audience, then yes, this advice is right on the ball for you: you should write for you, because it's about you.

If, on the other hand, your tendency is to boldly write what you care about, following your passions and interests and not giving the audience much of a second thought, then the opposite advice applies: write for your audience - because it's about them, not you.

Of course, "write for both the audience and yourself" doesn't make such a good sound bite...

I'm reminded of a quote, by Niels Bohr, I thin, which said that the opposite of a Deep Truth is another Deep Truth...

1.) Only post stuff I myself would be interested to read if somebody else had written it.

2.) Do not force myself to post simply because I haven't posted in a while.

3.) Do not simply regurgitate stuff I have read elsewhere.

A lot of articles on tech blogs violate rule #1 and the vast majority violate rule #3. Rule #2 seems to be violated by any site which is making a serious attempt at making money.

It is also greatly satisfying to share the lessons learned down the road.

So I don't think you shouldn't write for others. In the end, no one is Spolsky or Yegges except for themselves, but we shouldn't underestimate the benefit to the masses that may learn from you.

I am by no means an authority, but I get a few appreciative emails every so often and that brings me great joy.

Write what you want to read (but can't find elsewhere).

This simultaneously challenges you to learn the subject matter in depth, fills a needed gap in content that other like-minded devs are probably looking for, and may even yield a nice chunk of open-source or useful code snippets.

I use this strategy on my blog, albeit infrequently.

A couple years ago, getting RSS subscribers was the holy grail of blogging. But these days, people find your content via Twitter or HN anyways. So there's much less risk of losing your audience because you wrote a personal post that didn't connect with your readers.

I tend to find writing (or explaining) for other people and doing it for yourself blend. A lot.

The old adage that you don't truly understand something unless you can explain it to someone else holds particularly true with tech writing. When I'm writing to communicate something to someone else, I'm also helping myself understand the topic better. It's win-win.

Well if it's good writing, or useful writing, it's better to publish it because it might be useful for someone else.

http://www.youtube.com/watch?v=TFIanJS6fks