• 02 Jun 2014

    Ergonomics Without the Office Furniture Look

    In my last post I talked about my switch to a mechanical keyboard and in that expressed that one of my chief concerns (and reasons for not getting one earlier) was the fact that the keyboard was not ergonomic. On further inspection, I concluded that the bulk of the problems related to keyboards in general had less to do with their own ergonomic features and more to do with the fact that the typical desk is too high to type on top of. By that, I mean that, unless you are exceptionally tall, typing with the keyboard directly on top of a standard desk means that your wrists will not end up angled downward towards the keyboard, thereby putting unnecessary strain on wrists, arms, etc. In my case, I had grown very accustomed to using wrist rests, and negatively sloped ergonomic keyboards (the negative slope is actually a really good thing, btw) - but because keyboard was still sitting too high, all that did was cause me to stop touch typing and get lazy with my wrists.

  • 15 May 2014

    My New Old Keyboard

    If you follow Jeff Atwood, then you’ve no doubt read his articles on designing the Code keyboard and his thoughts on mechanical keyboards more generally. I’m not going to even attempt to provide an equivalent level of insight into all of the details on the different types of keyboards. However, I will share my experience now that I finally took the plunge and got my very first mechanical keyboard.

  • 24 Mar 2014

    My Spring Speaking Schedule

    Spring is in there air (well, intermittently here in the Pacific Norhwest), and that means - the spring conference season is shaping up. With three kids at home who are all 6 years old and under, I’m still trying to keep my travel under control. However, I will be venturing out a bit, so here’s where I’ll be over the next couple of months. If you’re in the area, I would love to catch up - so let me know!

  • 24 Mar 2014

    Surprise! JavaScript Guard Clauses

    I spent more time then I had planned this weekend debugging an issue in some code I wrote, and at the end of it all, discovered a JavaScript language feature that I had read about a while ago but never used (intentionally, that is). To explain, consider the following predicate function definition (and yes, I know that Underscore has this function - my specific case would have brought in some additional concepts, so I’m simplfying here).