Resignation letter from Microsoft Employee
21–30 of 117 posts
Re: Resignation letter from Microsoft Employee
#22Earlier quoted context omitted.
Does the "TL;DR" sentiment really belong at HN at all? I'd like to think this community is above that. The whole thrust of the site is about/for people who aren't interested in taking the easy way out.
I always appreciate the efforts of HN'ers who post a TL;DR summary. It's less about taking the easy way out, and more about saving time.
Re: Resignation letter from Microsoft Employee
#23I really don't like when critics put a cap on someone's future.
Re: Resignation letter from Microsoft Employee
#24Two things struck me, one kind of minor - a Pentium 66? In 1997 my desktop machine at my new startup job was a Pentium Pro 200. It replaced the SGI Indy R4400 200 from my previous startup job. No offices with doors, though, of course. The other thing was, and I don't mean these questions in a derogatory way, how do you start working for Microsoft in 1997, of all years. And how do you stay there for 12 years running?…
Good thing he's not going to a startup, he's going to Facebook.
Re: Resignation letter from Microsoft Employee
#25Really needs a TL;DR
Does the "TL;DR" sentiment really belong at HN at all? I'd like to think this community is above that. The whole thrust of the site is about/for people who aren't interested in taking the easy way out.
Re: Resignation letter from Microsoft Employee
#26Re: Resignation letter from Microsoft Employee
#27He had me until: "What’s your final level at Microsoft? Please don’t say CEO or Technical Fellow – I can almost guarantee you it’s not." He may be right, but there are some ambitious employees at Microsoft who truly do want to be CEO. If that's what they want, I hope they continue to bust their ass of to achieve it. I really don't like when critics put a cap on someone's future.
Re: Resignation letter from Microsoft Employee
#28Re: Resignation letter from Microsoft Employee
#29Re: Resignation letter from Microsoft Employee
#30You can think this way if your idea of "what the business needs most" is "what currently has the sales guys in a tizzy." Forget about everything else. Oh, and if your code only works for current customers, and has to have a bunch of tweaks and fixes applied for each new customer, then people will think your code is what allows them to sell to new customers. No kidding. If you write code that doesn't handle cases A, B, and C, then later you get credit for adding "support" for A, B, and C and making it possible to sell to customers X, Y, and Z. That's "visibility," because people from sales and marketing will mention your name appreciatively at high levels.
And for God's sake don't do any work on scaling or reliability, because a salesman never calls up your boss's boss and says, "It's been a long time since the scalability of your systems scotched a deal. I just want to say that's awesome and thank you." Wait until it breaks, make everyone thinks it's impossible, and then fix it.
EDIT: In a healthy organization, none of this will affect who gets promoted, but in an organization where people worry about "visibility," this is what they're talking about.