Note: I'm still waiting for my Wibro modem to arrive. Couldn't wait to write another post before I get to test it!
My posts are usually long. Of course, it's not my intention to make it long when I start writing each post. However, it always ends up being longer than I originally plan. Maybe it's because of my ineptitude in following one of the Writing 101 lessons: "make it succinct."
My Korean blog posts are far longer. I write many theoretical articles on my Korean blog, on things like Web 2.0 economics, attention economy, tech & society, open business strategies, etc. They often come out to be way over 10 printed pages and feel like academic papers, seemginly endless when read. So what I did was to combine all the long articles into one long PDF book (all in Korean) and freely distribute it online. It's been downloaded over 30,000 times.
Anyhow, in all truth, I still want to stick to the short-and-modular-post approach.
Well, this post has already gotten far longer than I planned. So to make it short, here's my dilemma: I really want to present you guys with real good information on the digital generation over here and there's so much I can write. So should I keep the posts short and terse or make them long and have you really chew on them?
My posts are usually long. Of course, it's not my intention to make it long when I start writing each post. However, it always ends up being longer than I originally plan. Maybe it's because of my ineptitude in following one of the Writing 101 lessons: "make it succinct."
My Korean blog posts are far longer. I write many theoretical articles on my Korean blog, on things like Web 2.0 economics, attention economy, tech & society, open business strategies, etc. They often come out to be way over 10 printed pages and feel like academic papers, seemginly endless when read. So what I did was to combine all the long articles into one long PDF book (all in Korean) and freely distribute it online. It's been downloaded over 30,000 times.
Anyhow, in all truth, I still want to stick to the short-and-modular-post approach.
I long ago noted that one of the under-appreciated elements in the success of open source software projects was their modular design, which is an essential element of what I've elsewhere called an architecture of participation. It's easier for people to collaborate around small chunks, and to build up larger works piece by piece, than it is for them to work together on a large, complex project with many dependencies.Moreover, we're living in the age of such an abundance of information and of quick-pace that if you write long posts, chanes are your posts will be just skimmed through, not really "read".
Well, this post has already gotten far longer than I planned. So to make it short, here's my dilemma: I really want to present you guys with real good information on the digital generation over here and there's so much I can write. So should I keep the posts short and terse or make them long and have you really chew on them?
brought to you by
Prev