Ask HN: I want to create tech blog – what should I blog about?
What would you like to read?
Why do you expect that it would be interesting for others if you don't have something that's interesting for you to write about? Or something that you know in depth and you know most of the potential readers don't?
The right question would be something like "I have a lot of material about X, Y and Z but I can write only about one, let's vote."
And honestly, the first thing I thought reading your question was "somebody running a mechanical Turk web content farm asks for some new spamming ideas. Now he'll just collect the list of the answers here and give it to his slaves. On the second thought, he won't even bother making the list, he'll just send the link to the answers. The question was whole six words."
If all you have to contribute is discouragement, why bother saying anything.
Why blog? Why tech?
And as I've pointed to, we've already spent more time than he writing and thinking about it!
At least I won't anymore.
--
I see you mention your blog and I've taken a look
http://www.angularonrails.com/
I think it's a good idea, writing about something others don't write enough. I like that you write about something you really know. I don't think you did "market research" but decided to write your own experiences instead. I wasn't able to see the list of the articles or the way to browse through them though. Is this intentional?
Hey OP. I like hearing about new technologies and seeing examples of implementation, getting a feel for where they actually fit in the landscape. What kind of tech are you looking at blogging about.
Trying to pick a target topic is very difficult unless you have a deep interest.
I could probably try and write some articles about Angular, people seem interested in that. But I'm not that excited about it and would lose interest, and wouldn't make the distance.
I keep a to-blog journal and write topics down in that as the thoughts come to me. Only the things you're interested in are worth writing about - otherwise the writing will be dull, and you'll give it up because it is too much work.
So blog about whatever you are passionate about. It's really the only way you have a chance of sticking with it long enough to get any traction.
As has been said "If you cannot explain it simply, then you don't understand it well enough." Look for the complicated paradigms that have no simple explanations - things that fascinate you ideally; research them and cut through all the BS, connect the dots for people, explain the consequences and applications of the paradigms and make it simple for people to understand, don't dumb it down necessarily, but explain it in terms that non-genii can understand with real world metaphors that everyone has experience with ... and they will come. At least, I will :P
Or you could write things that are "googleable". Solve a hard python problem? write about it, found a bug in a framework? Blog about it.
People searching for those things will find it. It'll never make a "splash", but the tail is longer.
It depends on what you want to accomplish. Is the purpose of the blog to demonstrate to the world how "brilliant" you are? Or is it to genuinely help your fellow programmer man?
People searching for those things will find it. It'll never make a "splash", but the tail is longer.
This makes sense to me. I don't read any programming blogs on a regular basis; I never have. I read individual posts that I find in web searches when looking for specific information. I couldn't care any less what the rest of the blog is about (though if I like one post, I may well read a few more while I'm there).
Regardless, I think the writing practice is valuable and you can build up a stable of articles to give to people when they ask your opinion on something.
Sometimes people think writing a blog has to be "me telling you what I know." But it can instead be about you learning what you don't know. That allows you to start from a position of humility, and it's a lot less pressure.
Or to quote from a famous movie "Sometimes nothing can be a real cool hand." https://www.youtube.com/watch?v=zDYyg0QskRo
A site that covered new startups, products, and services could be nice too. TechCrunch / The Verge / VentureBeat, but without the fluff and filler and drama and politics and marketing's sickeningly glossy fingers all over everything. Imagine Gruber covering the startup scene (only maybe with a little less of other aspects of his personality).
I really enjoy reading elite, in-depth troubleshooting posts. jgc, jwz, and especially rachelbythebay all produce some fantastic content along those lines. The variety of different ways that things break in this industry never ceases to amaze me. You'd have to be pretty deep into the troubleshooting trenches to produce good content that way though.
For lighter fare, I think Silicon Valley needs more Onion. A tech blog that just poked holes in Silicon Valley's obsession with itself and its favorite subjects could be a nice change of pace (and might even help reform it a bit). You have to be a rarely talented writer to pull that off though.
Good luck!
Don't write for others, write for yourself.
>I am not going to pick one topic every day and write about something new. I don't want to write something rubbish just for the sake of writing it. I ultimately want to write because I have something to say. It doesn't have to be unique or ground-breaking. What matters is that I want to write about it.
Another quote on that draft is by James Erwin (writer of Rome Sweet Rome) from an AMA:
>if you're going to write, write what you want to write. The odds against any creator are insane. If you're going to devote months of your time, don't let it be for an idea you think will sell. Odds are it won't. Write something you want to write, or need to write. Write for yourself before anyone else. I'd rather read someone who is excited and passionate about what they want to say than someone who's obviously trying to say what they think I want to hear.
I call it the Roman Writer's Manifesto.
You can read the entire draft on github (https://github.com/captn3m0/captn3m0.github.com/blob/master/...)
1. What you know well.
2. What you want to learn about.