Rock Hymas

Around September, Kami and I decided we would dedicate some money to replacing our dying backup server. It was nothing fancy, just a simple box that backed up important stuff via FolderShare and provided access to our printer. With the impending release of Windows Home Server it made a lot of sense to just wait a bit and setup a new box with that for backup, printer sharing, and away-from-home access. A friend of mine had recently tried to convince me to start building my own PCs for the savings, the customization opportunities, and the ability to build something more likely to last longer. So after thinking about it a bit I decided to do just that, instead of just getting the HP MediaSmart Server. I’ll outline the process of building the box in this post, and later talk about installing and setting up the software.

You can see the computer I got as a NewEgg (but without the motherboard, which is no longer available). Some of the things I wanted over the MediaSmart server included dual hard drives with more total storage space, a faster, upgradeable processor and motherboard, and 1G of RAM instead of 512 MB. What’s cool is that I got all this for less than the price of the cheaper MediaSmart server.

So, everything finally arrived and I found an evening to put it all together. I basically followed the instructions that came with each part and used Jeff Atwood’s excellent Building a PC series to direct my efforts. I skipped the overclocking, since I don’t really care about that at this point, nor do I have the time to really put that kind of effort into this PC. However, I may do it with the new dev box I’m buying for home use next month.

I got everything set up and connected, and it worked! I have yet to install the software, because I have yet to get the software. I planned on using Microsoft’s company store to get a nice discount on Windows Home Server, but they’ve been out ever since I started working on this. And the discount is big enough that I can wait, praying that our old backup server doesn’t totally die in the meantime. So I’ll post about that soon.

So, my last post was all about how I’m trying to become more productive by learning a set of keyboard shortcuts that I can use for faster text/code editing. In this post, I’m going to argue against the premise that it could actually make you faster. The reasons I’ll outline include opportunity costs, lack of portability, anything else? Well, we’ll see, won’t we.

First, opportunity costs. Yes, the dirty little secret about using keyboard shortcuts is that it takes time to learn them. The same could be said of command line interfaces. The main reason that most users (i.e. non-power users, those poor souls) don’t use keyboard shortcuts, or command line interfaces, is because of the learning curve. And there is an obvious learning curve. I’ve spent too much of the last couple days working to remember the keyboard shortcuts and use them a lot so I can make them habits. “But wait!” you say, “It’s an investment!”. Sure, ok, I can buy that. Now let’s look at the numbers to see what the payoff on that investment is. This page seems to indicate that you could save 16 hours a year by using keyboard shortcuts. Two whole workdays. Um, that’s not much when you consider that it probably takes more than two full workdays to develop the muscle memory needed to really gain that much time savings. So you won’t really start to see a return until you’ve been doing it for a couple years. Of course, others state that the mouse really is faster, so I’m not sure why I even argued that point. Okey, I know, the point is that the mouse is faster for people who haven’t yet built up that muscle memory. But then again, maybe not.

Ok, now let’s talk about opportunity costs. What else could you do with the time invested in memorizing keyboard shortcuts and making their use habitual? Wisely invested, a few days each year could let you read lots of books, take training courses or attend seminars, develop personal productivity tools (more on this in a future post), start learning a new programming language, or listen to the 1000 songs that can fit on your iPod nano. Doh, I mean your Zune.
Anyway, the next challenge is portability. Sure, you might learn all the cool keyboard shortcuts for vim, or emacs, or Visual Studio, or whatever. But you can’t then use them in the others, or in Notepad, or a web browser, or a mail program, or whatever. Even the really basic navigation ones, much less the more interesting ones and potentially useful ones. This actually makes using other programs more difficult once you’ve mastered a lot of app specific shortcuts. Unless you want to go the route of the “Emacs As Operating System“, which may actually have benefits, but only for a very small subset of people.

Basically, those who would use Emacs As Operating System are people with a great memory. Those who can memorize, either in the head or in their muscles, thousands of useful commands. The rest of us are ok with a JIT use of commands. We find them and use them when we need them. Keyboard shortcuts are useful for commands we use more often then once an hour. That can actually include quite a lot of commands if you’re a developer who lives in a text editor of some type most of the day. But it probably doesn’t extend much beyond that. And trying to develop muscle memory of commands used less frequently will be very difficult.

Wow, I think I talked myself out of my latest project. Guess I’ll have to go find some other way to save 16 hours a year…

I recently started experimenting with emacs on the many suggestions of Steve Yegge. Unfortunately, just getting up to speed in emacs (i.e. working as quickly as I do in Visual Studio or even vim) was taking a long time and when time is short, as it is during milestone development here at Microsoft, that’s not the best way to spend it. So I’m putting off that experiment until work slows down, or until my parental leave in January. In making the decision to stick with VS for the next few months of coding, though, I definitely want to improve how I use the text editor and as I began working to do that I ran across this post by Noah Coad. So I thought I’d respond to Noah and share some of the things I’m doing to improve my keyboard use (and therefore, speed) during development.

My familiarity with the vim and emacs commands has led me to seek a keyboarding compromise. I love vim’s ability to navigate very easily on the home row keys. But I like the fact that emacs doesn’t have two separate “modes”, command and insertion. I always get thrown off in vi because of that. So my navigation keys are basically the vi navigation keys while holding down the Ctrl key. I’ve also adopted a hybrid of the emacs convention of using Alt to switch from characters to words, lines to sentences etc. So Ctrl-Alt-J moves my down a page, etc. And then, I like the windows convention of holding down Shift while nagivating to select text, so I’ve added mappings to do that, e.g. Ctrl-Shift-K to select up a line. I’ve also added some other navigation keys that follow this same pattern, such as Ctrl-0 to go home. Of course, I’ve also remapped the commands that are at those bindings by default to other bindings depending on how often I use them.

So far this seems to be going well. I’m still learning these keyboard shortcuts and that’s taking a little bit of re-education, but I feel faster than when I use the mouse, which is a good baseline to start from.

Now to respond to Noah. I am now trying to use visual studio for more of my text editing needs, and customizing it more so that I can. As I’ve started doing this I’ve been impressed at how much power is there that I didn’t know about, but also frustrated by the little things that are possible but not easy to do. Searching, replacing, and regular expressions is an area that could definitely stand to be improved. Opening files from the explorer or from visual studio into new instances easily would be nice (an SDI type mode). One thing that would be useful is to have keyboard mappings that can be applied and then removed easily. This would be similar to modes in other text editors, but allow for some specific behaviors in certain cases.

It’s time to buy a new phone. One of the cool benefits at Microsoft is discounts on phones and phone plans from most major carriers. So when my contract is up I go back to the discount web site to see what the latest deals are and if I should get a new phone. My current phone is a T-Mobile SDA that is falling apart because I dropped it when running across a parking lot in the rain. It’s a great little phone, but it would be nice to have one without a dorky rubber band around it. However, I have noticed other people with pretty beat up SDAs, so they must be reliably durable. However, having used it for a year and a half now, there are definitely some things I don’t like about it.

• Candybar style. It’s just to bulky to put in my pocket, so I carry it around in belt clip, but I’d much rather have it in my pocket. The candy bar shape also requires that I lock the keys (which I don’t) or I randomly call numbers consisting of an odd mix of 0’s and *’s. So yes, I randomly call numbers consisting of an odd mix of 0’s and *’s cause locking the keypad is too much of a hassle.
• No secondary display. I loved being able to look at my last phone (a flip phone) and see the time, missed call information, and number of messages. Now I have to push a key to get that and the information is mixed in with random stuff that the window mobile software puts on the home screen.
• Four useless buttons. Yes, I know there are hacks to customize the SDA’s media buttons, but again, I’m too lazy to do it. So I use the speed dial, which, instead of being speedy, requires me to hold down a button for a long time. Its better than nothing for launching key apps (Calendar, OneNote Mobile), but it could be so much better.
• Very tiny, but important, buttons. The home button, back button, and the two soft keys should not be the smallest buttons on the phone. And certainly not smaller than the media buttons. I’ll throw in here that the power button is difficult to use.

So yes, it could be better. Most of my qualms are with the hardware. However, I think the truly useful benefits and changes to phones could be done in the software. Before going further let me deal with the iPhone thing. The iPhone seems really cool. However, I doubt I’ll ever get one. Even if they sync with my outlook perfectly, have a flip phone, all that stuff. I just don’t want or need something so complicated. The same critique applies to the Windows Mobile phones out there. I want a phone that does three or four things perfectly.

• Making phone calls. I don’t make a ton of phone calls, but when I do I want it to be seamless, fluid. I want a nice big number keypad with good feedback when I hit the buttons. I want an integrated list of recent calls (in and out), my contacts, etc. Modern phones basically have this list working well enough for me. But most phones don’t have a good keypad, least of all the iPhone.
• Provide reminders. I want my phone to synchronize with all my calendars (home outlook, work outlook, etc.) and remind me of appointments and tasks. It should also be very easy to add one-off reminders for a relative or absolute time in the future. Those should be synced back to the appropriate calendar also.
• Provide a recording service. But I’m not just talking about the wimpy voice recorder found in Windows Mobile. I want a button on my phone that kicks off recording so that I can instantly start talking. Once that happens, I want a list on the screen of things to do with the recording. The default, for me, would be to put it in my email inbox so that I can be reminded of it. Other possibilities would include making it a task, an appointment, emailing it, etc. Each of these would be preconfigured and would take just one more button click. If I just hit the “End Call” button it should do the default one. And for each of those it should run voice recognition, extract the best guess as to what I said and include both the text and the voice recording.
• Provide voice access to information. I not only want the increasingly competitive 411 services automatically added to the speed dial (and a good speed dial would be nice), but I want a 411 service that allows me to access some of my own information that is in the cloud. I should be able to ask questions about my schedule, retrieve notes (like my wife’s library card number, which is currently in OneNote Mobile), and check for urgent emails.
• Preferably a slim flip phone. I want to put it in my pocket. I want to have an external display with the time and information about missed calls and appointments.

It’s important to note what I left out. I do not want

• An internet browser. They’re too much of a temptation when I’m sitting at my desk. I don’t need that with me all the time.
• A camera. I’m not a picture taker. If I were, I’d want a decent camera with me also, not a significantly degraded phone experience. That said, I’ll take a camera in my phone if it is very much a secondary feature.
• Driving directions, games, instant messaging, videos, a calculator, etc. Whenever something here is useful, it should be rethought as a phone number service I can call. Just as there are web services for many existing desktop apps, so most mobile apps should be phone services with voice as the main UI. Any time I need to enter text it should be possible to do so with my voice and decent voice recognition software, either on the phone or over the line.

At this point I don’t think there is a phone that meets my needs. I’ll probably settle for something that handles phone calls reasonably well, syncs my calendars, and is a flip phone. And it will have a bunch of stuff I don’t need or care about. But I can dream, right?