A couple months ago I announced my departure from Commerce Bank.  I left my job as their lead developer of online banking, and joined RiverPoint Group as a contractor.

I'm not going to blog bile (see #5 on that list).  I'll just say this:  I don't think contracting is a good fit for me.  I wasn't as effective as I'm used to being, and it really hurt me to go from feeling like a leader, in control of my project and caring about its outcome as a reflection on me, to being a detached mercenary, without a whole lot of say in anything.  I also wasn't prepared to put in the time the client required of me, especially in light of my family life;  I just didn't have any time with my wife, Michelle, or our two awesome little boys, Connor and Cade.  That was the hardest thing for me to deal with:  Seeing my boys in the morning when I left for work, only to return home after they were in bed.

Be sure you understand me when I say I'm not blogging bile.  RiverPoint is a great company, and if you want to be a contractor, I think they're a great company to work for.  Our client, who has asked me not to disclose their name on this blog, is one of the best companies in the country to work for, and they deserve that reputation.  I just did not fully anticipate what my new role was and how it was going to affect me on a personal and professional level.

So I was talking with some friends of mine at Corillian (now a part of CheckFree), and I asked them if they thought I'd be a good fit there.  My friends gave me a good recommendation, then I went through a series of intense interviews, and now I've been hired.  On September 17, after taking a week off to relax, I will be joining Corillian/CheckFree as a Sr. Software Engineer/Technical Lead in their Professional Services division.  What this means is I will be doing a job very similar to my old job at Commerce, but I will be doing it for other clients of Corillian Pro Services. 

Ready for the best part?  I'll be working remotely from my home office.  This is the Holy Grail for me;  A job that suits my talents, that I enjoy doing, in a company whose values align with my own, that I can do from home.  I'm thrilled that the time I used to spend commuting can now be spent with the kids, or on open source projects, or going to Lodge meetings, or .NET user groups.  As much as I hate to leave a new job so soon, there are no words to describe how much I am looking forward to this.

I've been running Windows Home Server RC1 for two months now, and I love it. There's very little not to like about it.  I won't bother re-hashing what it is and what it does, because you can find plenty here, here, and here.

My experience with it has been awesome.  So far, the only things I can complain about are:

• It doesn't support the scanner function on my HP all-in-one printer. HP never released a Windows 2003 driver for it. So I can use it as a print server, but I have to pass the scanner through to a Windows XP VM to use it.
• Mozy's consumer offering doesn't support it. Admittedly, duplication puts my mind at ease regarding losing data to a hardware issue, but there's always that need in the back of my mind for off-site backup. The way I've worked around it, for the short term anyway, is to run Mozy on a Windows XP VM inside my WHS and do an hourly mirror of the most important 4 or 5 gigs worth of data (pix mostly) to the virtual machine so Mozy can back it up from there. I did try the one consumer-oriented online backup solution that supports Win2K3 (I think it's i-Drive), but I couldn't get it to reliably map the drives to backup if I wasn't physically logged in on the WHS box. Honestly, I'm thinking I may just revert to a semi-annual DVD going to the safe deposit box for my offsite backup.
• I had a motherboard die on me, and I tried simply replacing the motherboard with a new one (and upgraded to a dual-core CPU, too). WHS booted up, but, long story short, it left me in a less-than-satisfactory place (as I expected) so I went ahead and did the reinstall option. This went well, and recovered all of my shared folders nicely, but I had to recreate all my users, and for some reason, I can't set up the dynamic host name function anymore. As soon as I put in my Windows Live ID, it bombs out with unknown error "80072F19," which is apparently related to some sort of untrusted certificate coming from the Windows Live servers. I've tweaked some IE security settings, and added some IP addresses to the trusted sites, and still no dice. Weird.
• Up until today, I didn't realize that the shared folders had file versioning. It never really occurred to me to check the file properties for a previous version tab, and that this would only be viewable from a connected client (not the server), and then only if you're running XP, Vista Business, or Vista Ultimate. But I did stumble upon that today, and was very happy I found it. That's half the reason I use Mozy - so I can fix a "whoops."

I did have one moment of WHS-related sheer terror today. I noticed that about half of my 30 GB library of MP3s seemed to be unreadable. My pictures and documents are backed up via my XP VM running Mozy, but my backup strategy for music and videos relies on WHS.

So, as I was freaking out, seeing if my Creative Zen Vision:M supported copying my music off of it back onto the server, I rebooted the WHS box. When it came back up, everything was fine.

The best I can figure is that it has something to do with the extra external hard drive I added yesterday. I have a 120 GB external drive I was using to take work home, and, since I'm quitting that job this week, I decided to put that drive to better use as a member of my WHS storage pool. So I plugged it in, formatted, added it to the storage pool, and left it alone. I'm wondering if there was some kind of a hiccup or something in the file duplication process the next time it balanced storage (hence, why only some of the MP3s were hosed).

At any rate, I'm buying this as soon as NewEgg lists it.  It's 100% pure awesome, and worth every penny.

(Full disclosure: This post is made up primarily of snippets of forum postings I made on Scott Hanselman's forum...)

I've been invited to Infusion's Sleepless in NY training weekend. 

This sounds like a fun little trip, getting to hang out with some geeks, including one of my personal heroes, Carl Franklin.  SharePoint is a good technology, and while I'm not personally overly excited about it compared to other technologies (like Silverlight), this is free training, and it's a great opportunity to network and get my name out there a little. 

And who knows?  Maybe I'll bring home the grand prize, "Insomniac, the developer's machine that never sleeps..."

Today I'm 1D in hexadecimal, which I prefer because it makes me look like I'm still a teenager.  Or 11101 if you prefer binary.  Let's just not talk about how old I am in decimal, okay?

Alright, I'll put it this way...  The hippie adage is "Never trust anyone over 30."  Which means you can only trust me for another 366 days.

This is my first post since starting my new job.  I've been a smidge busy, as they threw me in immediately on a high-profile project utilizing Microsoft Office SharePoint Services, and, well, my working knowledge of MOSS was somewhere between zip and zilch.  That's changed significantly over the past few weeks, and while I've been hesitant to call myself a MOSS developer, I'm certainly getting my bearings and starting to kick much ass.

One problem our team has run into several times is source code control.  Pretty much everybody on the team was a SourceSafe user and didn't have any experience with SVN.  I initially balked at this, because, well, SourceSafe sucks.  I advocated SVN every chance I got, particularly when SourceSafe would eat somebody's changes or we fought over file contention. 

As luck would have it, the company is in the process of standardizing on SVN, and, when our VSS repository became obviously too corrupt to be much use, the technical architect on this project caved to my requests and we switched to SVN.

The problem with this is, SVN's Copy-Modify-Merge paradigm can be confusing for developers who are used to Lock-Modify-Unlock.  We've had several occurrences of changes mysteriously disappearing, and, since I'm the de facto SVN expert on the team, it was left to me to reconstruct exactly what happened.  To avoid naming names and pointing fingers, I’ll illustrate with Alice and Bob…

Let’s start with a file.  We’ll call it Text.txt.  Text.txt looks like this:

Alice and Bob both did an update and now have Revision 1 as their working copy.

Alice makes some changes and commits them.  She removes the line “Baz” and adds “42” and “Don’t Panic”.  She commits her changes as Revision 2.

Bob, meanwhile, makes some changes of his own.  Working with Revision 1 as his base, he adds “Quux”

Before committing, Bob does an update and realizes he has conflicts.

Now, what I think happened, is Bob made a mistake while merging, and chose to accept his entire conflict block as the merge output…

Bob then marked his conflicts as resolved and committed this as Revision 3.

The problem with this is that it negates Alice’s changes – She removed “Baz”, and she added “42” and “Don’t Panic”.  The next time Alice did an update, she updated to Revision 3 and the changes she previously made in Revision 2 were missing.  SVN gets blamed, making Cam look bad for being such a vocal SVN supporter, when it was really Bob’s fault.  (The “making Cam look bad” part was a joke.  Smile.)

What Bob should have done was take a good look at the differences between Revision 2 and his working copy…

…and asked himself, “what exactly did I change in my working copy?”  In this case, Bob did one thing and one thing only: He added “Quux”.  So Bob has to assume that any other changes to the file were done for a reason.  Somebody wanted “Baz” removed, and “42” and “Don’t Panic” added.  It’s then incumbent upon Bob to ensure that only his valid changes are included in the merge.  The resulting file could have looked like this:

The moral of the story:

Copy-Modify-Merge (like SVN) is more powerful than Lock-Modify-Unlock (like SourceSafe), but, as Uncle Ben Parker told Peter Parker, “With great power comes great responsibility.”  When you merge and commit, you have some responsibilities to live up to:

Update frequently.

When you merge, be sure you are not removing someone else’s important changes, and that you are only merging in the changes that you made that are relevant. 

When you commit, always read the file list to ensure you are not inadvertently committing changes to a file you did not mean to modify.  Also, it helps to do a diff of each file in the file list to be sure you are only committing code changes you mean to commit.

Good luck!

Well, not really.  Not in the flesh, anyway.

A few months ago he and I exchanged Wii Friend codes.  Nothing happened.  Months went by, and I spent less time with my Wii and more time with my Xbox 360.  Then my wife turned on the Wii to play Twilight Princess, and, lo and behold, we have a visitor.  Here's a shot of my Mii hanging out on Mii Plaza with Scott Hanselman's Mii.

Not a bad Mii, Scott.  But which is the better likeness;  Your Mii, or your avatar from A Conversation with Scott Hanselman?

I just got my first greenlit article on the social news site, Fark.com.  For those of you unfamiliar with Fark, what this means is I submitted a link to a news article, including a self-written funny headline, and the users of the pay version of the site (TotalFark) gave it sufficient votes to have it show on the front page of Fark.

I guess you'd have to be there to appreciate it.

Yay, me.

For almost seven years, I have been very proud to count myself as an employee of Commerce Bank.  Circa 2003 or so, I started to establish myself as the go-to guy for all things web technology-related in the bank as I took over primary responsibility as the lone developer on many of Commerce's retail Internet and intranet applications.  I was very successful in that role, and over the past few years, Commerce gave me the opportunity to lead the effort to move Commerce Bank's online banking development away from Corillian's professional services division and into our own development house.  With a great team of developers, QA testers, and project leaders, we succeeded with flying colors.  I put in many long days and had a great deal of fun, both in terms of technical problems and interpersonal interactions.

Then, one day a few weeks ago, I realized that I wasn't finding any joy in it anymore.  I was burnt out.  I haven't entirely pinpointed why.  There is a feeling of needing a new challenge, like I've done all there is for me to do at Commerce.  There's some minor dissatisfaction with finding clear direction for me to grow my career.  And, to be truthful, there's probably a little wanderlust, a need for a change in scenery.

Whatever it was causing my funk, it wasn't getting any better, so I acted on it.  And so it is with a mixture of regret, trepidation, and excitement that I announce that I have resigned my position at Commerce Bank as of July 11.

I have accepted a position as an Associate with the RiverPoint Group, taking a contract engagement with a local interactive media company.  This company has a reputation as one of the best environments for developers in the KC area, and has been named one of the best places to work in the country.  I'm thrilled that I get to experience that environment, and I'm looking forward to meeting the new challenges that are sure to come.

At the same time, I'm very, very nervous about my decision.  Commerce is all I've known for seven years.  I'm very comfortable there.  Everyone knows me.  I have a reputation as a guru on a range of topics.  I've put much of myself into our online banking system and our development process.  I consider my coworkers at Commerce to be my closest friends and family.  As excited as I am, all of this makes it very hard to let go.

However, I'm (mostly) confident I've made the right choice, and I know that, win, lose, or draw, this whole experience is something I have to do to understand what I'm really capable of and where I really fit in the developer community.  As my mom says, for every door that closes, another opens.

So, grieving over the end of this era be damned, I have to boldly stride forward and meet this challenge head-on.

Wish me luck.