349 karma · joined June 12, 2013
previously: vp at godaddy. led cloud platform, infrastructure, authentication, FE, and eCommerce engineering through IPO.
partner at microsoft. worked on product & engineering for consumer services (outlook.com, onedrive, microsoft ID, windows update & store), search, security, and windows core OS.
founder at burkcolabs. advisory: cyber security, seed stage investing, health tech, cloud infrastructure.
example: https://cloudblogs.microsoft.com/industry-blog/microsoft-in-...
> Ms. Ford English was appointed to our board of directors in May 2020 and stepped down from our board of directors in May 2021.
> Mr. Hinrichs stepped down from our board of directors in May 2020.
> Mr. Jameel stepped down from our board of directors in July 2021.
> Mr. Kaul stepped down from our board of directors in July 2021.
> Mr. Sheriff stepped down from our board of directors in May 2021.
I'm happy to answer questions if folks are interested.
[0] https://en.wikipedia.org/wiki/Windows_Preinstallation_Enviro...
If you sold your company, aren't working at FB/goog/etc and are sitting on a ton of stock holdings, your income is going to show as near $0
this is different than the side-by-side (WinSxS) support that allows parallel versions of the same dll to live on the system. that used to grow at huge rates when you had lots of system updates + lots of apps.
https://blogs.msdn.microsoft.com/bharry/2017/05/24/the-large...
this actually isn't true. and I say this as the person who pushed for a 32->64bit upgrade path at microsoft in longhorn. at the most basic level - it is easy for the core OS. but any apps you've installed are going to be a crapshoot to see if they work, with their installers only expecting a 32bit OS, registry, etc.
upgrade is hard enough as it is so risking the experience to a customer of breaking many of their apps with no good path to resolution isn't worth it versus waiting ~3-5 years for a PC purchase cycle and their next preinstalled version of windows being 64bit and going from there.
the additional tradeoff you need to consider is that the smaller you make the patches, the larger the number of variations you need to test for later patches, updates, app compat, etc. that is why service packs were a thing - you could baseline after a period of many patches getting out there, and start the process again.
(full disclosure: I used to work on and around some of this at microsoft many moons ago)
having ways to anonymously get regular feedback from your team can help a lot. as well as getting as much second hand data from other teams / managers as possible.
[1] http://www.forbes.com/sites/victorlipman/2015/08/04/people-l...
it will be interesting to see how small these boundaries can become before it is too expensive to measure at the level of granularity sought. when you can spin up a container, run job, and destroy faster than you can even log.
[2] I worked on outlook.com and http://answers.microsoft.com/en-us/outlook_com/forum/oemail-...
[2] https://www.quora.com/Will-Google-deactivate-my-Gmail-accoun...