Cavallo Point — Birthplace of Adobe Creative Cloud

A New Adventure

When are you in SF next? I’d love it if you would come run engineering for NodeSource.
Umm…say what now?

It was two days before Valentines Day and I had just gotten home after another long day. During my commute, I was already in a foul mood and thinking ”I’ve gotta find something more interesting to do.” After a quick dinner, I decided to veg out in front of the TV and catch up on Twitter. That’s when I saw the DM from @dshaw. A few more tweets and we had a Google Hangout scheduled for the next day, Several weeks later, I had an offer and I made the decision to leave Adobe.

This was not any sort of statement about my employer but something that had been brewing for a few years. I had never intended to stay as long as I did. Three to five years MAX. I started off building the installer platform for the Creative Suite, followed by a metadata service and finally ended up leading the team that built the very first service for Adobe Creative Cloud, Creative Cloud Assets. A decade had passed.

In the grand scheme of things, I had nothing to complain about really. Between a technology platform that survived multiple suite cycles and being part of the birth of Creative Cloud, I had definitely established a reputation for Getting Things Done. I had been compensated well and promoted twice although the last one was extremely difficult and drawn out. Most important of all, I loved my team and my product.

Still, I was having trouble staying motivated. Getting features out the door was taking longer and longer as more and more stakeholders got involved. Technical decision-making by committee was increasing. My title far outstripped my actual levels of responsibility and accountability. There was no more challenge. I entertained many offers, but most were lateral moves and the few that interested me didn’t hit enough of my criteria to warrant leaving.

Enter NodeSource.

Honestly, the deciding factors were @dshaw, @joemccann and @rvagg. Not only did I respect them, but they showed they respected me. Additionally, they were offering me an opportunity to take on challenges that I needed to take on at this point in my career. There were no guarantees for success, but the odds looked pretty good. A strong founding team, great engineers and a mission that bridged the open source and enterprise worlds.

It was weeks after I decided to join NodeSource that I realized why their offer resonated with me so much. Five years ago, I wrote a post that detailed the criteria for my post-Adobe life. I had completely forgotten about it, but something made me go back to the archives and there it was. A quick re-read made it clear that NodeSource had ticked all the boxes for me. It felt right because it was right.

I will truly miss all my friends and co-workers from Adobe. We accomplished so much and I’m proud of the products and culture we built. Now, I’m looking forward to all of the things we’ll do at NodeSource. This time, I’m not setting any time limits for myself. The goal is to help build a successful company and I have no idea how long that takes.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.