Live data from Hacker News

Resignation letter from Microsoft Employee

worldofsu.com

41–50 of 117 posts

Re: Resignation letter from Microsoft Employee

#41
post #33

Turns out that there’s a strong correlation between a student’s grade and their assessment of the professor’s abilities. Very interesting. I don’t listen too carefully when a poor performer tells me how awful their previous manager was. Wait, what? Are we confusing correlation with causation here? Let's say, for example, that a manager tends to give female employees poor ratings (or whatever BigCo calls a grade). Do…

Interesting data point for you. First, Break All The Rules found that average managers put most of their time into their worst performers. Great ones put most of their time into their star performers. The reason? Both groups can improve, and a 10% improvement in a star is worth a lot more than a 10% improvement in a dud.

I'd be interested in the study data. The data I've seen suggest that great managers put most of their time into manageable employees, the ones I called swing performers above. It could be that some stars swing between good and great, while some median employees swing between poor and good. If there are stars who have a 10% swing based on management investment, then yes there's a better ROI working with them.

I agree with the idea that it's a poor idea to spend most of your time with your worst performers. The problem with the worst employees is that many of them are irredeemable, so you can't get 10% improvement out of them, except possibly by micromanaging them to the point where you're doing their work)--and that doesn't scale. They're unmanageable in a negative sense, and thus you need proportionally more investment to get poorer returns.

One strong exception to a dictum against spending time with worst performers: Spending time identifying unmanageable poor performers does generate very high returns IF YOU FIRE THEM. In software, poor performers can actually have negative productivity: Their presence slows the rest of the team down.

Re: Resignation letter from Microsoft Employee

#45
post #37
post #36

Earlier quoted context omitted.

Facebook, behemoth that it is, is still a startup. We get a little carried away calling every little personal website project a startup and perhaps that's just right for the forum. But don't get tunnel vision. Facebook is a startup.

Then how do we categorize a startup if not by age (Facebook is already 5 years old) and size (hundreds of employees, billions in stock)?

It is pretty arbitrary and Facebook is a late-stage startup but hundreds of employees, sky-high valuation and five years of age are not unheard of and still within 'startup' range, to me. Mushy factors include things like culture, innovation, risk. I'd say 'run by founder' also adds startup points.

Re: Resignation letter from Microsoft Employee

#46
> Do you practice specific skills with repetition and intent?

This troubles me a bit for coding, because:

There need be no real danger of it ever becoming a drudge, for any processes that are quite mechanical may be turned over to the machine itself - Turing http://libreamoi.com/index.php/why-is-programming-repetitive...

--

However... there surely are skills in this process itself. What are they, and can they be practiced?

Concrete example: if you keep repeating code, you could (variously) write a function for it; a framework for it; a language macro; use an IDE that automates it; write a vim/emacs macro; etc

So perhaps one specific skill is to learn how to automate things with a concrete tool, and practice automating tasks (eg. writing a few vim macros as practice, to learn the syntax, API, pitfalls, conventions etc).

( EDIT: or, more generally, practice using your tools )

Deeper skills are recognizing repetition (and regularity in general), defining it clearly enough to know what an automation would need to do; and know how to verify that you're correct. Implementing it is a final step. Another skill is in assessing whether such precise analysis is worth it, given insufficient data to 100% nail the task; that the task may change (esp with new data); and of course that to estimate how much effort is involved in doing it "properly", verses a "good enough" solution, verses not automating at all.

But how does one practice those tasks with "repetition and intent"? They aren't like piano scales - each problem is unique and unknown. hmmm.

Re: Resignation letter from Microsoft Employee

#49
post #45
post #37

Earlier quoted context omitted.

Then how do we categorize a startup if not by age (Facebook is already 5 years old) and size (hundreds of employees, billions in stock)?

It is pretty arbitrary and Facebook is a late-stage startup but hundreds of employees, sky-high valuation and five years of age are not unheard of and still within 'startup' range, to me. Mushy factors include things like culture, innovation, risk. I'd say 'run by founder' also adds startup points.

I would suggest stock value more than 50x peak profit probably works. A 5 year old billion dollar company that is never made more than 1 million a year is probably still a startup. A 3 year old 10 million dollar company that made 500k last year is probably not.
Post reply on HN