Writing a Blog Helps You Write Better
I know. Thank you Captain Obvious.
Seriously though, like anything, writing gets easier and better with practice. So, if writing is a part of your job, you might want to start a blog.
Take my job for instance. Development means a lot of writing, collecting requirements (the requirements document), describing what a product should do to meet those requirements (the functional design), describing how a product is to be built (the technical design or architecture), describing how to test the product (test plans), documenting what the product does (documentation) and how to use it (white papers), and promoting the product (collateral).
Surprising amount of writing for a technical profession.
Most of these documents have templates to make them consistent and to guide the author through want should be included. The templates tend to make them longer, and providing detail is easy, with words and screenshots.
So, these documents can easily pass 100 pages. I think a design I did years ago reached 200 plus pages. It was quite complex, but still, talk about tl;dr.
What does this have to do with blogging?
Three things:
1. Blogging hones your brevity skills.
From my own reading experience, I don’t like thick paragraphs; they are depressing. So, I use a lot of whitespace.
Also, my time is valuable, so I want to get to the point. When I read content from traditional journalists (e.g. the NYT, WSJ, Time, etc.), I wonder why they haven’t evolved. Skip the hook, make your point. I try to follow this in all my writing, with minor indulgences.
2. Practice helps you develop style.
Blogging is conversational, but that’s what makes it readable. This is exactly what is missing from so-called professional writing. It’s antiseptic.
Obviously, you must find a balance. Don’t drop a “dude” into your product documentation, unless you’re prepared to take heat from a heated customer. But, this is why you practice.
3. Practice makes it easier.
Even if you’re dreading the task, it’s easier if you’re accustomed to writing and the process of creating.
Bonus point, people appreciate good writing. What makes it good? It’s clear, short and not boring. If you write well, they might even miss the fact that you’ve no idea what you’re doing. He said, not at all from experience.
Thoughts? Find the comments.
Possibly Related Posts
- Types of Users Don’t Matter, What They Want to Do Does
- If Maslow Built Software
- Another Reason Product Development Should Blog
- Asking for Documentation Means You’ve Already Lost
- Testing is Tough
-
Chet Justice
-
http://twitter.com/oraclenerd/statuses/28947465445 oraclenerd (oraclenerd)
-
http://twitter.com/theappslab/statuses/28933595436 theappslab (theappslab)
-
uvox
-
http://twitter.com/jcollison/statuses/28948267911 jcollison (Jim Collison)
-
http://twitter.com/ultan/statuses/28950482020 ultan (ultmeistergeneral)
-
http://twitter.com/joelkallman Joel R. Kallman
-
http://theappslab.com Jake
-
http://theappslab.com Jake
-
http://theappslab.com Jake
-
uvox
-
http://theappslab.com Jake
-
uvox
-
joel garry
-
http://friendfeed.com/e/c3de89e7-cd2c-42e3-885d-8b668bfaf908 ivanwalsh (Ivan Walsh)
-
http://theappslab.com Jake
-
http://theappslab.com Jake
-
joel garry
-
http://theappslab.com Jake
-
http://twitter.com/Arleneuc Arlene Murchinson




