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.
Although it actually became available last week, I hadn’t blogged about it yet, so correcting that oversight here…
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!
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).
I had been ignoring this inconvenience for a bit because it wasn’t something that was hugely messing up my workflow…until this morning, where I needed to grab a table of stuff from a Web site and massage it into an array. For this, the column-based multiple cursor feature of Sublime Text is a huge time saver.