http://www.sqlservercentral.com/blogs/robert_davis/2012/03/31/reflections-on-leaving-microsoft/

Printed 2014/04/18 05:28AM

Reflections on Leaving Microsoft

2012/03/31

Reflections on Leaving Microsoft

Reflections of Microsoft

Reflections of Microsoft By Jeff Sandquist (http://www.flickr.com/photos/jeffsand/)


Several members of my SQLFamily have made adjustments to their career path recently. Several of us got together for #SQLNomz yesterday to celebrate our job changes, though granted, we don’t generally require an excuse to get together. Yesterday (Friday, 3/30/2012, in case you’re reading this in the future) was my last day at Microsoft. I join the wonderful team at Idera Software on Monday as a Sr. Product Consultant (more on what that means in a future blog post). Likewise, it was my good friend and pre-con cohort Argenis Fernandez’s (blog|@DBArgenis) last day at Coinstar, and he is joining Microsoft Consulting Services (which sounds like a pretty cool position) on Monday.

Another friend, Dev Nambi (blog|@DevNambi), had his last day at Microsoft just a few days before mine. He wrote a great blog post on it: Retrospective: Leaving Microsoft. This blog post has inspired me to write my own retrospective blog post on leaving Microsoft (hint: you’re reading it right now).

Reflections of Microsoft

I spent a little less than 5 years of my career at Microsoft. In DBA years*, that’s at least 8 ½ years. Here are some stats for that time:

* DBA years = the time it would take you to put in the number of actual hours worked if you did it without going over 40 hours per week. For the record, I just made this term up, and I claim copyright on it henceforth.

Reflections on Developers

We database administrators really like to poke fun at developers, and I’m just as guilty of that as anyone. But the truth is that I worked with some really great developers at Microsoft. The best engineering team I have worked with to date in or outside of Microsoft was the CAP engineering team. I worked with the CAP team as both a SQL developer and as an operations engineer. They are a highly skilled and dedicated team who work really hard to make sure they are producing efficent code in the client application, middle-tier, and in the database. Yes, you heard me right. They write efficient, performant SQL code. They have to. CAP is a highly critical application for Microsoft and performance is very important. CAP also interfaces with a lot of other internal critical applications (too many to remember them all), and if CAP is down or slow, they are all down or slow to some degree.

Some of the things that I think the CAP team does right (other than right good code):

* I would be remiss if I didn’t also point out that Melissa is also a very gifted chocolate maker. Her chili pepper chocolates are to die for!

Reflections on Relationships

More than anything, what I will take with me when I leave are some friendships that I am fortunate to have. There are several people that I want to call out. this is by no means the complete list, but these people have been really key for me.


Copyright © 2002-2014 Simple Talk Publishing. All Rights Reserved. Privacy Policy. Terms of Use. Report Abuse.