Live data from Hacker News

Reflections on My Career at Microsoft

medium.com

91–100 of 177 posts

Re: Reflections on My Career at Microsoft

#91
post #38
post #32

Earlier quoted context omitted.

Making blanket, vague criticism against "millenials" isn't particularly great discourse. Edit: And after your edit just now adding a reference to Germany is _so close_ to being Godwin's Law? https://en.wikipedia.org/wiki/Godwin%27s_law

I referenced post-WW2 Germany for their demonstrated ability to deal with a past national sin. Sorry, I thought that was an obvious reference. Edit: Did you really miss the word "after" ?

> Did you really miss the word "after"?

Nope. That's why I said "so close".

Re: Reflections on My Career at Microsoft

#92
post #74

Earlier quoted context omitted.

There used to be a program at Microsoft where employees who were "destined to do great things" would be pulled out, given special training, and then have their careers accelerated. On one hand, it is sort of a good idea if you can truly pick the "winners" (and some of the people who went through the program did amazing things!) but, well, in hindsight I think everyone reading this can see how internal biases would be…

There were at least two programs when I was there. I heard a lot more about them under Ballmer than under Satya. HiPo -- for junior to mid level -- special training, networking, and seminars. MiniMSFT comments section mentions this from time to time. Bench -- for mid to later career, usually on the way to "partner" or above level -- same as HiPo, but may be asked to work on a project with others in Bench, may see att…

Ah thanks for jogging memory in regards to the names. :)

> Neither one had any official impact on ratings, rewards, or career velocity.

Ah interesting, my understanding was that people who can gone through HiPo were sorta blessed. Then again I guess in theory the people who get selected for HiPo should already be doing the work to make their career velocity look good.

I saw all sorts of interesting stuff while I was at MS. It was a crazy place to work. It was sort of like working at a company that does everything 5-8 years too early, and then tries again 2-3 years too late.

* Tablets * eBooks * MP3 players * Smartphones * Smart TVs (Micorosft bought Web TV in 1997!! That is what, 15-20 years too early?) * Tablets again * Cloud based document syncing (See: What Sharepoint tried to be)

They also made some sort of automation creation tool for business users that, IIRC, got cancelled after one release and replaced with something else. I only know about it because I signed up to do internal user testing for it.

This is on top of all sorts of crazy one off projects. (In 2011 I was on a team attempting to make an autonomous household robot! How long before those become a viable thing outside of Roombas?)

Re: Reflections on My Career at Microsoft

#93
post #35

I'm not so sure the problem with Microsoft was its toxic culture. So many of the key points in that article you could say ring true of Apple. Steve Jobs relished in the fact that people feared him. He literally built an entire company of yes men, right down to the chefs in the kitchen. It meant, when his strategy was right, the company did well. However, when it was wrong, it also hurt the whole company. Tim Cook is…

The Jobs model works when you have a Jobs, or Gates, or Musk, someone whose inherent talent is so strong that the organization can look to him for all decisions. But the strategy for running a company in the long term cannot assume such a pope. If you have Michael Jordan on your basketball team your strategy can be “give him the ball” — if you are just five ordinary guys you will need a philosophy.

This is exactly correct. Organizations that create dependency on such highly performing individuals can coast on their talent while they're around but once they're gone, its hard to replace them.

Usually these uber-productive individuals are required and necessary during the early stages of a corporation where you literally need that kind of productivity to survive. Once an org matures though, there is no such requirement.

Re: Reflections on My Career at Microsoft

#94
post #82

Earlier quoted context omitted.

> of so much of it ... but how do you know? How could anybody know that?

Believe it or not, on gender, it is actually possible for most of us (men) to verify this empirically. As a cis male, one way to do this is to represent yourself as female, and see how much more you get questioned. You don't have to go so far as to cross-dress -- you could simply sign an email with a majority-female name in the signature.

My experience of presenting as female online in video games is I got a lot more attention, help, and outright handouts.

I want to see an actual study, because my anecdata doesn’t match the claimed experience.

Re: Reflections on My Career at Microsoft

#95
post #77

>The Microsoft of the 2000s, under Steve Ballmer, was almost exactly the opposite (of gates). >Bruised and battered by the consent decree handed down by the DoJ for the very same ambition that brought it to dominance, Ballmer’s Microsoft was sales-forward and CAUTIOUS. >It was... nervously clutching its pearls at the approach of Google in its rearview mirror People bash Steve Ballmer for missing Search, Social Networ…

> Microsoft was Caged. Had it's wings clipped. Had a huge target on its back. In case you did't know, any complaint by say Google in its early days and Microsoft would have been broken up! So much this. During orientation on my first day a representative from legal came in and told us, among other things, what types of metaphors we were allowed to use in emails. "No football metaphors, no explicit or implied violence…

You can amp up a team by challenging them to give the very best possible user experience, so that your customers loves your product.

Exhorting the team to "crush the competition" or "dominate the market" is not necessarily the best way to amp up a team. In fact, I'd argue it's the worst possible way, since that means that playing dirty patent troll tricks or financing things like the SCO lawsuit is a legitimate way to "win", as opposed to winning by delighting the user.

Re: Reflections on My Career at Microsoft

#96
post #70

Earlier quoted context omitted.

I strongly agree on Office/Excel. Fantastic product suite (except maybe Outlook which is long in the tooth/essentially unimproved for the last ten years). Visual Studio I'll slightly disagree on. I resent it. When VSCode, an electron application, can run lag/stutter/micro-freeze free and Visual Studio an IDE written in C++ cannot you know the codebase has become unmaintainable. This isn't a recent phenomenon either.…

> Visual Studio I'll slightly disagree on. I resent it. I agree. Visual Studio has a tendency to make me actively angry.

What, you don't like your editor freezing when it tries to look up a symbol?

Re: Reflections on My Career at Microsoft

#97
post #74

An interesting article, which I think accurately describes my brief time at Microsoft during the Ballmer era (our startup was acquired after the bubble burst). But his definition of "made men" seems very vague and very convenient. The people who Nadella appointed to higher positions were almost entirely people who had been at Microsoft for many years. Why are some "made men" and some are not? The definition seems pri…

There used to be a program at Microsoft where employees who were "destined to do great things" would be pulled out, given special training, and then have their careers accelerated. On one hand, it is sort of a good idea if you can truly pick the "winners" (and some of the people who went through the program did amazing things!) but, well, in hindsight I think everyone reading this can see how internal biases would be…

I was part of this program during my tenure at Microsoft (the earlier HiPo one mentioned already). I can confirm that it was a tremendous networking opportunity, but -- anecdotally -- almost 100% of the people I connected with, including myself, are no longer at Microsoft.

Re: Reflections on My Career at Microsoft

#98
post #82

Earlier quoted context omitted.

Believe it or not, on gender, it is actually possible for most of us (men) to verify this empirically. As a cis male, one way to do this is to represent yourself as female, and see how much more you get questioned. You don't have to go so far as to cross-dress -- you could simply sign an email with a majority-female name in the signature.

My experience of presenting as female online in video games is I got a lot more attention, help, and outright handouts. I want to see an actual study, because my anecdata doesn’t match the claimed experience.

You don't think that getting more attention, help, and outright handouts isn't its own form of bullying? You don't think it hints at an ever-more underlying reason behind the attention, help, and handouts?

Re: Reflections on My Career at Microsoft

#99
post #43
post #35

Earlier quoted context omitted.

The Jobs model works when you have a Jobs, or Gates, or Musk, someone whose inherent talent is so strong that the organization can look to him for all decisions. But the strategy for running a company in the long term cannot assume such a pope. If you have Michael Jordan on your basketball team your strategy can be “give him the ball” — if you are just five ordinary guys you will need a philosophy.

That was distinctly not the philosophy of the Chicago Bulls and Phil Jackson.

"Eleven Rings: The Soul of Success" is a fantastic book that explains this at length. Great insight into champion mindsets.

Re: Reflections on My Career at Microsoft

#100
post #95
post #77

Earlier quoted context omitted.

> Microsoft was Caged. Had it's wings clipped. Had a huge target on its back. In case you did't know, any complaint by say Google in its early days and Microsoft would have been broken up! So much this. During orientation on my first day a representative from legal came in and told us, among other things, what types of metaphors we were allowed to use in emails. "No football metaphors, no explicit or implied violence…

You can amp up a team by challenging them to give the very best possible user experience, so that your customers loves your product. Exhorting the team to "crush the competition" or "dominate the market" is not necessarily the best way to amp up a team. In fact, I'd argue it's the worst possible way, since that means that playing dirty patent troll tricks or financing things like the SCO lawsuit is a legitimate way t…

> Exhorting the team to "crush the competition"

I worked on a consumer product in a highly competitive space. Our competition released products that dropped frames and had laggy UIs.

The discussion wasn't "We're going to make a smoother UI so our users have a wonderful and pleasant experience." it was "Hah, how the hell, they have literally 20x the CPU power, a GPU, over 1000x the RAM, and they are dropping frames? Let's show'em how its done!"

In certain domains, and when trying to perform at certain levels, you need every single human emotion you can draw on to get enough energy to find the motivation to do amazing work.

Is that needed 99% of the time? Nope. But MS sure as hell could have used someone pissed off about their mobile experience being terrible about, oh, say, 3 years earlier than what did happen.

Another example. Gmail launched 2004. Imagine if 2002 a senior leader at Microsoft had burst into a meeting of the Hotmail leadership team and started shouting "Why the hell do other email providers even still exist? And why the fuck do I have to still delete emails every couple of days? I want every other free email provider out of business right asap. Lose money on it, I don't care, just make us the best!"

But instead, someone at Google got upset about the same problem and made a product that completely dominated the entire consumer email market.

If you go into a competitive space (especially consumer!) with the idea of "we'll look at the market research and do what is needed to establish a place for ourselves" then no one cares about you.

"We're going to make a product that makes everyone else on the market look like incompetent jerks" is an actual mission statement that can be used to get things done.

The competition has a painful first run experience? Yours isn't better, it is perfect. Why? Because screw the competition. Your competitors have fat profit margins? Yours are razor thin, because screw the competition. There product has an industrial design comes in black and ugly grey, you have designer colors, because screw the competition.

If you are a multi-billion dollar company, and you have the resources to do everything better than anyone else in the field, then you either perform at that level, or you lose.

The iPhone launch was to be a tour de force of this ideology.

"They have ugly plastic buttons sticking out everywhere, we have metal and glass. They have a crappy joke of a keyboard, we'll reinvent the entire idea of an on screen keyboard. They have a shitty sales experience in stores? We'll partner with one carrier, and train the living daylights out of their sales people. Their UI is hard to use? We'll launch a world wide ad campaign where we show subtly people how to use the device during the ad."

I was at MS at the time. The idea there was "We'll let our OEM partners decide on how best to differentiate their product, they are after all the ones doing the main value ad and we rely on them for manufacturing."

Apple said screw that entire model, they just made it themselves, and they made it amazing.

There is an incredible energy on teams motivated by the ethos of doing the best and steam rolling the competition through sheer excellence. I'm not advocating for dirty business practices, but holy hell, telling your engineers "do good enough" is going to get you "good enough." When they wake up and go to work and the entire office is saying "we're going to make a product that puts everyone else to shame", you get a great product.

Post reply on HN