During our Retrospective yesterday, several Pivots, especially our remote employees, mentioned that they missed the Standup blog posts that we used to post. Shall we start to post them again? And if so, does anyone have posting format suggestions? The old posts reflected our current real-life Standup format:
- Ask for Help
- Interesting Things
Unless anyone suggests changes, we’ll keep the same format.
I’m really starting to enjoy the selection of green teas in the office. I especially enjoy the ones with… well.. $#!+ in them. Popped rice, puffed rice, browned rice, black soy beans, and various other clippings and debris. It’s kind of like drinking tea with Rice Krispies in it, but in a good way. And the ingenuiTEA containers are very handy.
The only exception to my new-found enjoyment is a green “tea” named Angel, which must mean the Angel of Death, or perhaps the Angel of Turpentine; it’s easily the most foul and bitter substance I have consumed in a very long time.
So many of my colleagues have some degree of trouble with their
hands/wrists/arms. It’s a serious occupational hazard. Agile coding is a slightly different ballgame for me in terms of wrist problems.
My physical therapist for my first, worst episode — the episode that
left me with permanent nerve damage, nearly 20 years ago now –
stressed to me that damage is cumulative. Young coders can think
they’re invulnerable, but I’m here to preach to you: the pain can end
up being permanent. If it hurts to type, stop typing — please don’t do what I did, viz., shrug and keep going.
In the Agile/pair programming world the setup for workstations tends
to be a flat table, no special equipment, so that workstations are
interchangeable. No keyboard trays, nothing — not the best ergonomically. Here’s how I cope:
- I have a great chair, an armless ZackBack (um, yes, I’ve written my name on it in big black letters, why do you ask?). Posture can be really important to keeping your arms healthy.
- I use a flat keyboard, with as light a touch as possible — Macally is working well for me.
- I put the keyboard in my lap, which creates a better angle for me.
Alas, sometimes it maketh my typing to suck, but usually it’s okay.
- I use two alternative mice: a Roller Mouse for clicking and most steering, and a pen mouse for the rest of the steering. It’s best for my hands if I use both of them to mouse at once. Clicking with the pen mouse once caused a flareup, and the roller mouse gets a little wild for precision steering, which means I put my hand in a bad position trying to control it. I used to use a foot mouse, and I recommend that too if you don’t mind a loud clomping sound every time you click. High learning curve with the steering, but great low-impact clicking. My fabulous former boss Lynne Cameron thought of it. (Miss you, Lynne!)
- I turn on Sticky Keys, which means I don’t have to hold multiple keys at once. Unfortunately, it can be hard on my pair if we forget to turn it off. Sorry, folks. Think of it as a variant of Dvorak. Note that it’s a good idea to disable the “beep when a modifier key is turned on” option if you value your sanity, and enable “Press shift five times to turn on or off”. (Also that, arghh, the new Apple keyboard goes a little berserk with Sticky Keys turned on. The arrow keys don’t work at all, for example.)
- I make sure the monitor (we’re an all-iMac shop) is on a riser or phone book or something so that the top of the screen is level with my eyes. Bent neck equals bad posture.
All these help to make the setup sustainable for me. The other thing
about pairing that makes sense ergonomically is, of course, the fact
that your hands get a break whenever your pair is typing (if you ever
let them type — I am a confirmed keyboard hog, but I’m trying to mend my ways!).
Just one more wrist hazard of agile coding: all the self-applauding and high-fiving — paired code is so much better than code written solo.
How do you cope with your wrist limitations?
Want to avoid feeling like a chump and spending countless hours troubleshooting a crazily-stupid-simple problem?
<script> tags off the front and back.
You probably knew that already. Why didn’t you tell me sooner?
Again, thanks to Steve.
“So, who needs a pair?”
(See also Bush Violates Standup Rules)
in my spare time, I’ve been poking at DRM/DRI code in OpenBSD. right now its been imported (but disabled). the code is not ready, but its far enough along to be hacked on in-tree.
one of the things I’ve been doing is going through and removing the i386-isms that tagged along with the FreeBSD/NetBSD code. a few gross things, like vtophys(), and some code that assumes 32-bit procs. in the process, I’m learning little things like C, Kernel Interfaces, IOCTL, and allocating memory for hardware devices. Fun stuff, and a few chunks are actually working.
of course, someone else is the actual maintainer, I’m just poking at things, with the hope that I’ll figure it out and make not-sucky patches. :)