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

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

Leaving eyeo

Thirteen blog posts later, this one notes my departure from eyeo after 4 years and 3 months. I joined eyeo around the headcount of 80 employees, and now I think there's just over 250 people there. My role coming in was as operations manager, doing a mix of infrastructure engineering and technical project management. I later on took on organizational development to help the company deal with its growing pains . We introduced cross-functional teams, departments (kind of like guilds), new leadership structures, goal-setting frameworks, onboarding processes and career frameworks.  And all of this in a rapidly growing distributed company. I'm proud and happy that for a long time I knew every employee by name and got to meet every single new-hire through training them on company structure and processes.  At some point, we had enough experienced leaders and organizational developers that I could zoom back in on working in one team, consulting them on  Git and continuous integration

Using Voice-Chat for Gamers in Distributed Teams

This is a post going into the usefulness of live voice-chat tools in distributed teams. If you've ever seen the Leeeeeroooooyy Jeeeenkiiins video of World of Warcraft fame, you've heard this kind of tool in action. It's how the participants in the video are speaking with each other - this is not a feature built into the World of Warcraft game - it's a separate team-oriented VoIP software, and it's all about letting gamers communicate orally while gaming.  Since these tools are for gamers, they have to be fast (low latency) light (as not to steal CPU-cycles from heavy games graphics)  moderate in bandwidth usage (as not to affect the game server connection) There are several options around: TeamSpeak , Ventrilo , more recently the massively grown Discord , and finally Mumble , which is the open-source alternative of the gang. A few years ago, when I joined eyeo (a distributed company), several of the operations team were avid gamers, and had a TeamSp

Joining eyeo: A Year in Review

It's been well over a year since I  joined eyeo . And 'tis the season for yearly reviews, so... It's been pretty wild. So many times I thought "this stuff really deserves a bloggin", but then it was too inviting to grab onto the next thing and get that rolling. Instead of taking a deep dive into some topic already, I want to scan through that year in review and think for myself, what were the big things, the important things, the things I achieved, and the things I learned. And then later on, if I ever get around to it, grab one of these topics and elaborate in a dedicated blog-post. Like a bucket-list of the blog posts that I should have written. Here goes: How given no other structures, silos will grow by themselves This was my initial shock after joining the company. Only a few years after taking off as a startup, the hedges began growing, seemingly almost by themselves, and against the will of the founders. I've worked in silos, and in companies wit