Working From Home

Throughout my career, I have worked from home for months at a time.  I find it very convenient for the most part- no morning dash to the shower, no morning commute, just a quick bite to eat and I’m at work with my coffee still warm from the kitchen.  I can get four hours of work done before lunch.

I’ve often wondered why video telecommuting doesn’t happen more often.  We have the technology (and we can rebuild him!) to get full video and voice going between multiple locations.  Skype, MSN Messenger, AIM and a host of other free software is easy to set up.  Webcams are cheap.  What gives?

I think Scott Hanselman has figured it out.  Turns out, it’s not the technology, it’s the way you set it up.  The “creep factor” of videoconferencing is a reality that has to be addressed.  There’s just something weird about realtime video conversation.  I’m sure my kids will think it’s no big deal, but it’s new enough that most people feel like they’re actually on TV.

168521-dellvostroaio_350

So, as the good Mr. Hanselman explains, your primary machine must not be the one you use for videoconferencing.  You don’t have your coworkers staring you in the face while you work.  If you want to talk to a neighbor, you back off your computer and turn around.  He and Phil Haack have each dedicated a PC in their home offices to the purpose of full-screen, high resolution video.

I’m intrigued by this setup, and I think it holds promise for broader adoption of telecommuting.  In fact, I think it could breathe life into a niche product: the PC-in-a-flatscreen.  The idea of a completely un-extendable, non-upgradable PC had always baffled me: who would want such a thing?  As a dedicated communication device for the home office, it makes sense.  I think it could be made very cheaply, given that all you need is enough horsepower to run a webcam stream.  A decent processor, network interface, and video card could be bundled into a slightly thicker-than-usual VGA flat panel with a VESA mount on the back.  Done deal!

Quick Tools Recommendations

As I was doing some work on my VSTime project I realized that my favorite source control tools might be of interest, so here they are:

TortoiseSVN

TortoiseSVN integrates directly into Windows Explorer and turns any old folder into a Subversion-controlled repository.  Free to all.

AnkhSVN

AnkhSVN is an open-source plugin for Visual Studio that connects to Subversion repositories.  Again, free.

Codespaces.com

This is by far the coolest of the bunch, though you need the first two to use it.  Codespaces.com is a Subversion host, and much more.  It’s not free, but $2.99/month is a very good deal for:

  • Multiple Users
  • Work Items
  • Card Wall
  • Document Repository
  • Wiki
  • As many code repositories as you have space for ($2.99/month buys 500MB)
  • Project Portal (you can share details about the project with outside stakeholders)

I’ve been using the service for several months and it’s awesome.  Very good for personal projects you want to keep backed up, especially if you work on multiple machines.

One caveat: if you set up these tools, don’t attempt to manage Visual Studio project checkins/checkouts through TortoiseSVN, use only AnkhSVN.  There’s some versioning issue between them, so if you try to use both on the same project you may end up with a versioning error.  Just stick to using AnkhSVN and you’ll be good to go.  This may have been addressed with the last release of AnkhSVN, but I haven’t tried it.

Follow

Get every new post delivered to your Inbox.