Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I also think that often others benefit more when people write like this.

I think of it like how we say it is good to be lazy. Not lazy as in do no work, but lazy in be efficient and don't put off what is easily done now but hard later.

When writing for yourself you are writing for people like you. People with interests in similar topics, that are facing similar problems, and probably think somewhat like you too. After all, most of us really aren't that different. It's easy to notice small differences because we're similar.

Instead, when you write for others you don't chase those things that make you unique you chase what you think a more average person (in whatever niche) wants. You distance yourself from them just as you distance from yourself. You become more likely to just create more of the same stuff that's already out there. You follow instead of lead.

There's tons of exceptions of course and the qualifiers shouldn't be ignored. All I'm trying to say is that the different approaches come with different biases. You should definitely be writing code documentation to general audiences but your blogs? Imo, that should be you. Not everything needs to be work. Just be the fucking nerds that you are



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: