Over three years ago in August 2010, my life changed drastically. I was working as a consultant for a consultant company that I like (and still like), with team members that I like (and still like), but for a project and client that I haaaaaaaated. I was miserable, and even my wife could tell. Though some good things eventually came out of my experience on that project, I couldn't wait to move on to a new client.

However, that time never came. Jim Holmes tweeted that his employer (at the time) was hiring a developer for a remote work position. I had some reservations at the time about working from home, but I figured...why not? I'll try something that really scares me. After a rigorous interview process with Jayme Davis, Josh Ledgard, and many others (Did I mention Rob Howard, founding member of Microsoft's original ASP.NET team?), they let me become part of the Telligent Analytics product development team.

Yes, Telligent. TELLIGENT. Not Telerik. Telerik is a different software company that makes very different products. Jim Holmes worked for Telligent then, but he works for Telerik now (belay that, he just left Telerik and is moving on to something else). Yes, I realize that makes it more confusing.

The twin frontiers of working from home and working on a product team were very challenging. Keeping up with a team of really sharp developers like Scott Watermasysk, Kevin Cunningham, Jose Lema, and others was difficult, but rewarding. I learned a lot, and I helped to ship some products. I got to work with Jim Holmes(!), and a great QA team including Miles Dunn. I annoyed Michael Monteleone, Wyatt Preul, and Ben Tiedt on a regular basis. I could list a dozen more awesome employees of Telligent (past and present) that I got to work with.

I also had a major life event while working from home: two broken shoulders caused by a major seizure. Telligent was incredibly accomodating, and if I weren't already working from home, my life could have been affected a whole lot worse.

Telligent eventually merged with (purchased) Zimbra from VMWare, and took their name.

This opened up a whole lot of amazing possibilities with email, database technologies, integration, and analytics. I got the opportunity to present a session at The Big Social, which is the annual Telligent/Zimbra conference. I helped to ship a major new release of the Analytics product--version 4.0, which was rebuilt entirely to take advantage of the Zimbra Community platform.

I got to work on a code base where I had plenty of input on design decisions, and I got to work with support helping customers on a regular basis.

I could absolutely see myself retiring as a Zimbra employee. Everyone I've worked with at Zimbra has been sharp, kind, professional, and if you are reading this blog post now wondering if you should apply to work there: yes, you should.

However, another opportunity presented itself that I just couldn't say no to. More on that next.

No Weekly Concerns this week, but don't worry: it'll be back next friday.