From his "executive bio":<p>"Scott holds an M.S. in computer science from Wake Forest University, a B.S. in computer science from Lynchburg College, and is an all-but-dissertation drop out from the computer science Ph.D. program at the University of Virginia." [1]<p>Props for not trying to paper-over that last part.<p>[1] <a href="http://news.microsoft.com/exec/kevin-scott/" rel="nofollow">http://news.microsoft.com/exec/kevin-scott/</a>
Kind of interesting because I assume Microsoft has deep technical talent in operating system kernel and user space design.<p>But they chose someone who I assume must be a distributed computing ("web/cloud") guy instead. I guess that's where they see the bulk of their business being in the future.
I think it should be noted that LinkedIn was recently acquired by Microsoft just last month. <a href="https://techcrunch.com/2016/12/08/microsoft-officially-closes-its-26-2b-acquisition-of-linkedin/" rel="nofollow">https://techcrunch.com/2016/12/08/microsoft-officially-close...</a><p>edit: link
The PR mentions he'll continue to serve on the LinkedIn executive team, so does that mean he'll continue to be based in MV? That'll be quite a change! (and challenge for him, I assume).
This is why I leave HN for a few weeks every once in awhile. People in this thread shitting all over the guy, meanwhile back in their own lives, they still have to argue with project managers over the "right" way to get code done.<p>The crabs are reaching out of the bucket hard today.
He will be out in 2 years or less. The problem with Microsoft is it has a massive old boys network. Once Ye Olde Microsoft mafia moves in, people who haven't been with the company for 15-20 years tend to move out, irrespective of their position. This is also why all Microsoft acquisitions where old boys network was allowed to intrude (basically all but Skype) have been promptly run into the ground within 2-3 years after acquisition.