on Blogs: don't just read All..

Hypothesis: Writing blogs yourself, would lead you to focus, on a limited set of blogs to read. One way to use blogs effectively.

Issue: There is no time to read ALL blogs, about a particular subject. We often feel like we are missing out.

Question:

(a) Do you need to read ALL blogs?

(b) How else can you make more use of blogs, available on a subject?

While this sounds interesting, many of you may have felt the same. There's just an awful lot of it available on the net and vast proportion of it "free". Where do we start; how much do we read? My view is - start "writing" blogs instead. Here's, why. In writing one, you will find reasons to plough deep into a topic or a sub-topic. For example, if you start looking for blogs in "Enterprise Architecture", and hope to "read it all" - where do you think that would lead? nowhere! Instead, if you start writing about a particular topic of your interest within the broader remit of EA - say, "Architecture Development methods", then that would get you somewhere. Again, there is a ton of material (blogs) available on that - not just TOGAF. Therefore, get even more specific. Architecture Development methods from TOGAF. Typically, you do this like you did when you chose a dissertation topic in school. Getting to a narrowed down research topic, solves at least the initial steps of clearing out aims, goals, methods etc. Likewise, narrowing down your search for a blog, would assist in achieving focussed set of blogs or articles to read. This all starts when you write a blog yourself. Your questions will naturally come to mind.