Skip to main content

Using the Blog as an online research tool

I usually don't like meta-blogging (blogging about the concept of blogs), because a lot of other people do it .

But today John Udell raised an interesting example of interaction between (in lack of a better general term) enthusiasts as a result of the openness of the web (all the web2.0 thingies like blogs and podcasts, their links, comments and trackbacks). This reminded me of that I dared to write "I've experimented with the use of a blog as an online research tool" in the Method-chapter in my thesis, and continued:
While it lacks structure and rigorousness of this thesis, the blog is still chronological through time, and in a way, it represents the research in a more honest way. It also performs the role of a dynamic research tool, as updated resources are available through my blogroll and linkroll.
Kristin Helen was the fellow-CMS enthusiast that opened my eyes for getting away with this (by pointing me to this document (1), and now she has in fact published an entire master thesis (2) about it! Congratulations :)

Now, how did the blog affect my research?

Primarily, it's a notebook. Its a place for me where I can note down stuff before I forget about it.

It's also a way to get feedback. A blog quickly attracts other enthusiasts due to the transparency of the open web (web2.0, ugh), depending on the activity of the blogger (see below). Like in Udell's example, I've found trackbacks to my own posts, whose blogs again have posts with interesting comments from other bloggers who I subscribe to and so on and so forth. I didn't get too many comments over the last few months, but I did get invited to a conference, and got some hints and nudges. It is also somewhat motivating to see traffic on yer blog, which means that somebody in the world actually take an interest in what you're researching for your master's (I know some other thesi that don't enjoy this interest).

How to do it?

To get into the blogosphere and get yer researchin' started, do the following:

  • Write. Do it regularly and write interesting/relevant stuff on one topic (use tags if you write on several topics). It's more tempting to subscribe to a stable blog.
  • Read. Use Bloglines or another feed-aggregator every day. As an example of the daily digest: these are my subscriptions
  • Comment. When you comment you leave a link back to your own blog, which is probably about a related topic. The author of the blog where you commented is likely to have a look at yours.
  • Trackback. Write about what other people write about. I doubt John Udell will notice that this post is a trackback of his post (he probably gets a hundred trackbacks every day), but maybe Kristin will? (no offense :D )
  • Search and surf. Check out technorati and del.icio.us for blogs on similar subjects.

So the thing you have to figure out is how big a limit you should put on your blog-activity. I spend half-an-hour reading through my subscriptions (comment when I find something particularly interesting, trackback when I find something immensely interesting), and write ~1 post a week, which takes 10-30 minutes.

(1) Mortensen, T., Walker, J. 2002, "Blogging thoughts:personal publication as an online research tool", Researching ICTs in Context, Intermedia/UniPub, ch. 11, p. 249-279

(2) Andersen, K. H. 2004, "Student’s Use of Weblogs: Weblogs for Collaboration in an Educational Setting" Department of Information Science, University of Bergen, Norway


Comments

Post a Comment

Popular posts from this blog

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant

Considerations for JavaScript in Modern (2013) Java/Maven Projects

Disclaimer: I'm a Java developer, not a JavaScript developer. This is just what I've picked up the last years plus a little research the last days. It's just a snapshot of my current knowledge and opinions on the day of writing, apt to change over the next weeks/months. We've gone all modern in our web applications, doing MVC on the client side with AngularJS or Ember , building single-page webapps with REST backends. But how are we managing the growing amount of JavaScript in our application? Yeoman 's logo (not necessarily the conclusion of this blog post) You ain't in Kansas anymore So far we've just been doing half-random stuff. We download some version of a library and throw it into our src/main/webapp/js/lib , or we use it from a CDN , which may be down or unreachable when we want to use the application.. Some times the JS is minified, other times it's not. Some times we name the file with version number, other times without. Some

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do: # install vcsh & myrepos via apt/brew/etc vcsh clone https://github.com/tfnico/config-mr.git mr mr update Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files . No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed: config-atom.git     -> ~/.atom/* config-mr.git     -> ~/.mrconfig     -> ~/.config/mr/* config-tmuxinator.git       -> ~/.tmuxinator/* config-vim.git     -> ~/.vimrc     -> ~/.vim/* config-bin.git        -> ~/bin/* config-git.git               -> ~/.gitconfig config-tmux.git       -> ~/.tmux.conf     config-zsh.git     -> ~/.zshrc How can this be? The key here is to use vcsh to keep track of your dot-files, and its partner myrepos/mr for o

What I've Learned After a Month of Podcasting

So, it's been about a month since I launched   GitMinutes , and wow, it's been a fun ride. I have gotten a lot of feedback, and a lot more downloads/listeners than I had expected! Judging the numbers is hard, but a generous estimate is that somewhere around 2000-3000 have listened to the podcast, and about 500-1000 regularly download. Considering that only a percentage of my target audience actively listen to podcasts, these are some pretty good numbers. I've heard that 10% of the general population in the western world regularly listen to podcasts (probably a bit higher percentage among Git users), so I like to think I've reached a big chunk of the Git pros out there. GitMinutes has gathered 110 followers on Twitter, and 63, erm.. circlers on Google+, and it has received 117 +'es! And it's been flattr'ed twice :) Here are some of the things I learned during this last month: Conceptually.. Starting my own sandbox podcast for trying out everythin

Git Stash Blooper (Could not restore untracked files from stash)

The other day I accidentally did a git stash -a , which means it stashes *everything*, including ignored output files (target, build, classes, etc). Ooooops.. What I meant to do was git stash -u , meaning stash modifications plus untracked new files. Anyhows, I ended up with a big fat stash I couldn't get back out. Each time I tried, I got something like this: .../target/temp/dozer.jar already exists, no checkout .../target/temp/core.jar already exists, no checkout .../target/temp/joda-time.jar already exists, no checkout .../target/foo.war already exists, no checkout Could not restore untracked files from stash No matter how I tried checking out different revisions (like the one where I actually made the stash), or using --force, I got the same error. Now these were one of those "keep cool for a second, there's a git way to fix this"situation. I figured: A stash is basically a commit. If we look at my recent commits using   git log --graph --