Skip to main content

The Worklog aka Diary

This is a pattern I've been applying for the last five years, ever since company wiki became the standard at my workplace. At some point I added it as an agile practice to the Cantara wiki, and named it "The Diary". However, I always end up calling it Worklog in practice. It's a bit of a GTD technique, with some positive side-effects.

Basically, on a day-to-day basis, write down what you're working on in a wiki page.

--------------

2010-10-04
- Fix the funky registration bug -
Bug tracker id #18355. 
--------------
2010-10-05
- Still the funky registration bug -
Jason committed a fix in r8040, but it didn't work. Writing unit-test.
-------------
2010-10-06
- Knowledge meeting -
Awesome stuff. Remember to upload the presentation to wiki.
- Registration bug -
Resolved task. Talked to Jason and product owner, done-deal.
-------------


Keep focused
I'm an easily distracted person. I'd be working with something, get side-trekked by a build-break, or a colleague needing assistance, and then when getting back to work on the original task, I've forgotten what I was doing, and start doing something different, like refactoring that ridiculous exception handling! How on earth did that get in there? Woops, there goes my personal WiP limit...If I've got the current task on top of my worklog, I'm more likely to get back on it. And any other incoming tasks, I can just paste in further down, and I'll get on them later.

Multiple paste buffer
Many people keep an txt on their desktop, simply using it as a quick copy/paste buffer. That SQL statement was rather handy, wasn't it? Better paste it into the worklog.txt for later use.

(By the way, Clips for OS X is awesome.)

Mini problem database
And dang, haven't I seen this exception message before? It was something manual that needed to be done when setting up a new server instance. Didn't I have the exact problem three months ago? Ah, I'll just search my worklog to see what it was that time.

Be transparent
Ever had a manager asking what you're working on last week? Ever had a colleague asking about what you're doing? The most transparent thing you could do is to put your worklog out there in open. Yes, on the company wiki. If you want people to be all agile and open about what they are really doing, you'll have to be first out there.

Keep history
It's great to have a quick look through the last week right before a Retrospective, or a meeting to make sure you've remembered the worst impediments and ideas you had. Freshen up what you're working on.

Some tips
Use notepad. Browsers generally suck. I've lost so much worklog from keeping my new content in a text field in the browser that crashed on me. Better keep your intermittent content in a wee text-editor, and paste it into the wiki page at the end of the day. Most recent entries on top works for me.

Archive old content. At the end of every year, archive your worklog-wiki page. We use MediaWiki at work, and I use my Talk page for worklog. At the end of the year, the page is usually quite a few MB's, so then I move it into a tfnico_worklog_2009 archive page.

Don't write too much. Yes, of course you'll regret not noting down some things at some points, but the key is to not make this into overhead work. Just do it as the worklog.txt, or notebook you always had, just that you store it on the wiki at regular intervals.

Are Yammer and CampFire better tools for this? Sure, but you haven't got those tools now; you've got a wiki. And if everyone catches on and does a worklog, invest in Yammer.

If you haven't got a wiki, you've got bigger problems.
Labels:

Comments

  1. Anonymous5/10/10 00:10

    Wow, that's a thorough work process. How would yammer and campfire help you with this? They're not well suited for neither sql queries nor exceptions. I think your wiki is better, but still very hard to maintain. Or is it?

    You might use google docs too, it's pretty simple and has a nice TOC. Better for the weekly retrospectives, I guess. Cheers!

    ReplyDelete
  2. tfnico5/10/10 09:48

    Thanks for the comment, Ole Morten!

    The reason I'm thinking of Yammer, is that often when I'm writing in my worklog, like "committing the big YYY fix", or "deploying test server", I miss having an internal Twitter, where I could broadcast these small but interesting events.

    The wiki page isn't so hard to maintain. I just push in new stuff in the top at the end of every day.

    I prefer it over a Google doc, cause it's much easier for my colleagues to stumble upon (if they search for something on the internal wiki for example, or look at Recent Changes). MediaWiki also has a nice TOC, and you can edit smaller parts of the page at a time, which is a real life-saver with a 3 MB page :)

    ReplyDelete
  3. Testbaudson6/10/10 09:38

    At our company some people are using the Pomodoro technique [1].

    A collegue created a small app based on Dzen [2], which requires you enter a description of the task you are about to address in the next focus unit. The descriptions are appended to a text file for archiving, quite similar to your approach.

    The cool thing is that we also make the status available to our co-workers, so people can check the current status via intranet. It's a good way to communicate you are in deep focus and don't want to be disturbed, or on the other hand, are available for team work.

    Thanks again for your talk at FrOSCon, it helped me addressing issues like continuous integration at our company.

    Christoph

    [1] http://baudson.cute-ice.de/serendipity/index.php?/archives/61-The-Pomodoro-Technique.html
    [2] http://sites.google.com/site/gotmor/dzen

    ReplyDelete
  4. tfnico6/10/10 10:04

    Hi Christoph, thanks for your comment. I'm glad the talk could help!

    I would love if there was more "integration", like you have at your place. Having this live status updating is even better. I'm still the only who does worklog (on the wiki anyway) here. Perhaps if we had some infrastructure like that, it would get easier adoption... Hmm, will have to think about this.

    ReplyDelete
  5. Anonymous6/10/10 15:21

    Sounds reasonable, actually quite close to what I'm doing. If you're an Emacs user (I suspect not) you might be interested in http://orgmode.org/. It's awesome for that kind of stuff and you can still seemlessly share text files with your colleagues.

    ReplyDelete

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...
6 comments
Read more

Encrypting and Decrypting with Spring

I was recently working with protecting some sensitive data in a typical Java application with a database underneath. We convert the data on its way out of the application using Spring Security Crypto Utilities . It "was decided" that we'd be doing AES with a key-length of 256 , and this just happens to be the kind of encryption Spring crypto does out of the box. Sweet! The big aber is that whatever JRE is running the application has to be patched with Oracle's JCE  in order to do 256 bits. It's a fascinating story , the short version being that U.S. companies are restricted from exporting various encryption algorithms to certain countries, and some countries are restricted from importing them. Once I had patched my JRE with the JCE, I found it fascinating how straight forward it was to encrypt and decrypt using the Spring Encryptors. So just for fun at the weekend, I threw together a little desktop app that will encrypt and decrypt stuff for the given password...
Post a Comment
Read more

The Git Users Mailing List

A year ago or so, I came across the Git-user mailing list (aka. "Git for human beings"). Over the year, I grew a little addicted to helping people out with their Git problems. When the new git-scm.com webpage launched , and the link to the mailing list had disappeared, I was quick to ask them to add it again . I think this mailing list fills an important hole in the Git community between: The Git developer mailing list git@vger.kernel.org  - which I find to be a bit too hard-core and scary for Git newbies. Besides, the Majordomo mailing list system is pretty archaic, and I personally can't stand browsing or searching in the Gmane archives. The IRC channel #git on Freenode, which is a bit out-of-reach for people who never experienced the glory days of IRC. Furthermore, when the channel is busy, it's a big pain to follow any discussion. StackOverflow questions tagged git , these come pretty close, but it's a bit hard to keep an overview of what questio...
Post a Comment
Read more

Git tools for keeping patches on top of moving upstreams

At work, we maintain patches for some pretty large open source repositories that regularly release new versions, forcing us to update our patches to match. So far, we've been using basic Git operations to transplant our modifications from one major version of the upstream to the next. Every time we make such a transplant, we simply squash together the modifications we made in the previous version, and land it as one big commit into the next version. Those who are used to very stringent keeping of Git history may wrinkle their nose at this, but it is a pragmatic choice. Maintaining modifications on top of the rapidly changing upstream is a lot of work, and so far we haven't had the opportunity to figure out a more clever way to do it. Nor have we really suffered any consequences of not having an easy to read history of our modifications - it's a relatively small amount of patches, after all. With a recent boost in team size, we may have that opportunity. Also the need for be...
1 comment
Read more

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...
Post a Comment
Read more