Skip to content

jonocode – a developer's blog

I moved! –>

(Or a good PHP blog, or a good MySQL blog … )

This blog is only days old. I don’t have much authority in writing about what makes a good blog. So I’ll just highlight what I think a good technical blog should do.

1. Be simple, be clear and to the point.

Don’t write any filler. Most readers don’t have time to read it. If you have a lot of background to fill in, or a lot of technical information, make sure your content is well-summarized, easy to print, and available in PDF.

2. Write in simple English whenever possible.

For many developers, English is a second language. No one should have to consult the dictionary to read your high-level English.

3. Be an engineer. Or ask your readers to be engineers.

Developers are like engineers, and engineers like to solve problems. Post a problem and your solution. Ask for alternative solutions. Or post a problem and ask for solutions.

4. Be corrected.

Every time someone corrects you, they improve you. They improve your content, and they improve anyone who reads your content. They are taking time out of their day to do you a service.

I can’t tell you how many times I’ve searched Google for an answer to my problem, and either found the same question asked but not answered, or answered but have to pay to get it. (Experts Exchange! Gah!)

Every time you are corrected, or you correct someone else, you are building on a library of shared and free knowledge.

5. Be grateful.

Thank anyone who takes the time to help you improve. Even if they haven’t helped you solve your problem. Just by contributing they are letting you:

6. Be a community.

I think of all the blogs together as a giant discussion board, or a community network. When someone contributes to your blog, visit them in return and contribute something back.

Do you have any other ideas on how to improve blogs? Or on how to improve the development community in general?

Please comment!


Tags: , ,

%d bloggers like this: