I recently purchased and installed a standing desk. While I normally don't blog about things in my personal life, I figured that this was permissible since it directly affects my ability to write code.
This standing desk is a Fredrik "computer work station," but let's be honest, here: it's a standing desk. It's pretty sturdy and removes the need to hack together various Ikea desks to produce reasonably-scaled tabletops. Pictured here is my desk, in its natural habitat. My workstation and hacked-apart AGP box both have their own monitor, and there is plenty of tabletop room for anything I need to have at my hands.
For those in the audience who aren't yet aware of standing desks, and don't want to read Wikipedia on standing desks, here are the abridged notes:
- Reduces back stress and pain after a few months
- Reduces risk of DVT
- When monitors are elevated, reduces neck stress and pain
- Slightly more expensive than sitting desks
- Hard to find
- Causes foot and ankle stress for the first few weeks
- Turns one into a hipster programmer
So, on the bright side, this desk has definitely improved my back pain. But, if I start writing Node.js code soon, we'll all know who to blame.
Last modified on 2012-01-31 11:42:00
It is a running joke in the X.Org community that X12 development will commence as soon as all of the X11 bugs in the FreeDesktop.org bug tracker have been closed. When I first heard this, my reaction was, of course, "Challenge accepted!" But where to start?
There were about 10,000 bugs open on the tracker at that point, a few years ago. We're definitely improving; there are about 9180 bugs open (at the time of writing) which could be considered relevant to any kind of desktop development. Many of those don't belong to anything in X11, but assuming they did...
Pretend that all of the card-carrying members of X.Org closed 92 bugs. That would be 1% per person. We could be done with X11! So, during XDC 2011, I pulled out my netbook, and started closing bugs. I picked, as my targets, things that nobody would miss, like Xprint.
I closed some Xprint-related bugs, before simply shuttering everything in the Xprint product. I also picked up a couple of stray bugs. Finally, with maintainer permission, I closed everything still assigned to xf86-video-nv.
- 24 Xprint-related bugs
- 37 bugs in Product: xprint
- 42 bugs in Component: driver/nv
- 37 bugs in Component: driver/nVidia (open)
- #9455, #28657, #29832, #30129
A total of 144 bugs. We can do this, guys!
Last modified on 2012-01-22 12:00:00
After accidentally hitting yet another window manager key combination this morning, I finally was fed up, and went off to read chromeos-wm source code to discover all of the key bindings. Here's the complete list:
- Ctrl-F5: Take fullscreen screenshot
- Ctrl-Shift-F5, Print Screen: Take region screenshot
- Alt-Tab: Cycle windows forward
- Alt-Shift-Tab: Cycle windows backwards
- Alt-1 through Alt-8: Go to window 1 through 8, 1-indexed
- Alt-9: Go to the last window
- Ctrl-Alt-t: Create a new shell window
- Ctrl-Shift-W: Kill the current window
These are only available in overlapping-window mode, which appears to be the default on at least Samsung Series 5 Chromebooks:
- F5: Toggle overlapping-window mode
- Alt-Comma: Expand current window
- Alt-Period: Shrink current window
Last modified on 2011-11-29 17:03:00