AidanMontareDotNet

You are on the old part of aidanmontare.net, which I am no longer maintaining. Newer versions of some of this content can be found on the active part of my site, which you can reach from my homepage.

Workrave: Three Weeks Later

About three weeks ago I decided to test Workrave, a program designed to help prevent Repetitive Stress Injury and other issues that can come from using a computer for extended periods of time. I hoped that the program would help lessen the hand pains that sometimes come from computer work, as well as give me regular breaks to relax my eyes. You can see the original article with my goals here.

The program works by tracking keyboard usage. When the user is working, the program counts down to the next break, which is either a short break (called a micro-break) or a longer one (a rest break). The length and spacing of these breaks can be configured in the settings.

It’s now been three weeks since I started using Workrave. I use the micro-breaks to stop tying and focus on something far away to give my eyes a break. During the rest breaks I get up, walk around, get a drink, etc.

So far, the program does everything it said it would. However, there are some things that make it annoying to use:

  • There is no server application that does not require a desktop environment. There is networking support in the application that allows other Workrave instances to connect and share usage statistics. That way whichever computer you are on, you still get evenly-spaced breaks (and also avoid having several computers yelling at you at once). But I don’t have any desktop systems that are always on, which makes figuring out where to put the server application a little difficult.
  • No Android version. The program runs on Windows and Linux, but unfortunately I wind up switching to my Kindle several times a day, and since that device’s usage isn’t being tracked, I wind up reading to long without a break. I would love for someone to write a version for Android.
  • Reading Mode is difficult to remember. Workrave tracks keyboard usage to determine whether a user is actually using their computer. If not, it pauses its timers because it assumes the user is not working. I often stop typing to read things, and this causes Workrave to only count the moments when I scroll the page. Reading Mode runs the timers even if input is not detected. However, I usually am switching between reading internet tidbits and using that knowledge in whatever I might be working on. I might be at my computer for 20 minutes, but if most of that was reading things, Workrave might only think I was there for 5 minutes. It can be hard to remember when to put on reading mode, and even harder to turn it off before you walk away from your computer!

I would like to see the project advanced to the point where I can use Workrave without having to think about it. However, the way I work, I still have to keep track of what mode I am in, and remember to take breaks when I am not on my main computer.

Finally, the idea itself is somewhat interruptive. Workrave has no way of knowing when it is a good time to take a break, and so it invariably prompts you to stop working as you are trying to finish a sentence (like right now as I write this). Workrave will delay your break if you keep typing and remind you again in a shorter period of time, but it’s still annoying.

To be clear, none of these issues are the developer’s fault, they just arise because of the way people like me use computers. Sometimes I find that taking a short break gives me some time to think about what I am doing and occasionally come up with a better method.

Despite these annoyances, I am going to keep using Workrave for the time being. It helps avoid the common pitfall of banging endlessly at something that is obviously not working or a waste of time. With all the computer projects I do, Workrave helps me make sure I spend time on other things.