News for hackers. Stuff that matters.
Re:The Coming Collapse of Average Managers and Employees by kamaal on Monday November 05, 2012 @12:35AM (#4742361)
Its not going to happen.

The problem is most places don't even have a way to find out a average manager. The reason is that management layers in almost every big company works like a cartel, they know darn well how to preserve their self interests. Generally you don't get to know until its often too late to do anything about it. The people who suffer the most are not bad performers, but those who fall out of managements favor or people who just can't get political and benefit out of it. The actual performers are likely to be named arrogant mavericks who are bad at team work. They won't be fired, but they will be treated so badly, until they themselves see the wisdom in leaving.

Also this whole GE analogy in these kind of articles is MBA speak. That is talking at high abstract levels, without absolutely knowing what they are talking about. Stack ranking worked at GE not because Stack Ranking is awesome, but because there was some one like Jack Welch to make it work.

Adhering to stack ranking to the letter but not in spirit will basically amplify the problem. Guess who gets the least rank in a political system?

Re:The Coming Collapse of Average Managers and Employees by yuhong on Monday November 05, 2012 @02:09AM (#4742562)
Reminds me of this about Google:

http://news.ycombinator.com/item?id=4331584

Re:The Coming Collapse of Average Managers and Employees by yuhong on Thursday November 08, 2012 @02:24AM (#4756803)
Re:The Coming Collapse of Average Managers and Employees by raghava on Wednesday November 07, 2012 @04:06AM (#4752781)
From the article

>> There's arguably never been a worse time to be a mediocre, average or typical employee. For most firms today, mediocrity is a cost to be managed and a burden to be borne, not a potential to cultivate or a resource worthy of serious investment. Indeed, if an app, web service or an outsourcer can deliver 80% of typical or average performance at 35% to 60% of the cost, then why pay for average employees? These days, no organization can afford to pay a premium for mediocrity.<<

The Indian outsourcing and bodyshopping cartels which thrive on mediocrity and cost-arbitrage would actually consider that to be awesome news, for it hints that they will get more work to keep costs low. But what they fail to realize is that another cheaper destination is emerging elsewhere. :) One man's poison is another's pie.

Re:The Coming Collapse of Average Managers and Employees by flyinRyan on Monday November 05, 2012 @09:00AM (#4743433)
Even for Welch, as I understand it, he was mostly firing areas that were under performing by the metrics they had. So they did have something: we reach the sales numbers we expect from that division or it gets the ax. I don't think this kind of strategy will work for all kinds of companies.
Re:The Coming Collapse of Average Managers and Employees by michaelochurch on Monday November 05, 2012 @08:09AM (#4743256)
The core insight-- that mediocrity and failure provide about the same payoff (zero) in a modern technological economy-- is accurate.

Here's where the divergence happens. Being a top performer requires a lot, and not all of it's intrinsic. Fit with tools and project are important, and so are relationships. There aren't intrinsic A and B players. For example, most software projects have one or maybe two "blazers" who write most of the new code and make the important decisions, and many more who spend the bulk of their time keeping up. It's a lot better for your career to be in the former category; get out if you're in the latter. This is what language and tooling wars are often about in companies: people wanting to change the landscape so they can be the trailblazers and the others end up as the followers. This is why it's economically worth it (in a corporate context) to invest so much energy into tooling and language fights instead of on the work itself: if you win the battle, the leverage it applies to your work is immense. The truth is that most projects have a rank ordering that becomes self-perpetuating, because the high-ranking people take the best work and progress faster. There isn't one global equilibrium where the "best" people are magically matched to the best work, but N! stable equilibria, where N is the number of participants.

Why is this important? Well, the correct insight is that the payoff curve (between input factors and output) is now convex. In a concave world, you wanted to manage toward the middle: reduce variance, bring up the slackers. This is what management is good at: bringing everyone in to the middle of the performance curve. That's also why traditional management is failing in the technological world. Maximizing a concave function is equivalent to minimizing a globally convex one, which is the easiest class of optimization problems (there's one global optimum). For these, incremental evolution (gradient descent) works: you converge to an optimal solution (in economic terms, an equilibrium). It's not equipped to handle the convex world where there are zillions of possible local optima and non-local insight is required in order to find better solutions.

What's inaccurate is the idea that there are "intrinsically" mediocre vs. excellent people and that the former should just be discarded. Why do we have to stay in school until we're in our mid-20s? Because our economic contributions are worthless until we've had an amount of schooling that would be considered immense by historical standards. The reason for all this schooling is to increase the probability of a person ending up as a "10x" contributor in an economy that has no place for 1x contributors.

As for stack ranking, that's something separate, and it's actually harmful to the top performers. Stack ranking is about intimidation-- nothing else. The idea is ancient: Romans called this method of intimidation and punishment decimation. Split the regiment into groups of 10, of which one will die. Sometimes it was random (drawing lots) and sometimes the groups voted. The reason for the 10% cut was because (a) it's not enough of a force reduction to "disrupt continuity" but (b) it was large enough to scare the shit out of people. People use "decimation" as a synonym for "devastation" but that's not correct, because "decimation" is a controlled, small reduction of force. Stack ranking is the same concept, but with political infighting used instead of randomness to make the decisions, and the "divide-and-conquer" campaign it wages against the proles is intentional.

Intimidation's effect is performance-middling. It kills creativity and innovation, and the top performers suffer, but it brings the slackers closer to the median. Traditional, intimidation-based management worked well in a concave world where people were mostly doing low-margin commodity work and one slacker could cancel out 5 good workers, but it fails catastrophically in the convex world.

Re:The Coming Collapse of Average Managers and Employees by lucisferre on Monday November 05, 2012 @10:10AM (#4743808)
Are you suggesting that different languages and tooling would make different players on the team 'A' players? Sorry, but I find this to be an extremely dubious claim.

At the risk of coming off as a completely arrogant ass, I've been an 'A' player in two completely different language, stack and tooling environments so far. Now I find myself shifting the lion's share of my coding time from back-end to front-end work, but aside from an initial adjustment period, I don't find this to be a huge hit to my productivity or effectiveness.

I'm pretty confident most other 'A' players can do the same easily, probably more easily than I can. Am I unhappy in an environment that forces to use tooling that I find to be unproductive, sure. I've been here before, but nonetheless I was still one of the 'A' players.

A players are not different because of having the right fit with tools or projects, or because of more (or less) education. They are different because they have a good fit with their purpose combined with passion for what they do.

Re:The Coming Collapse of Average Managers and Employees by michaelochurch on Monday November 05, 2012 @07:13PM (#4746552)
Are you suggesting that different languages and tooling would make different players on the team 'A' players? Sorry, but I find this to be an extremely dubious claim.

It depends how far apart they are.

Having written the code is a huge advantage. Getting to write code is a major advantage (if most of your time is spent reading code, your odds of transferring to a new-dev role on the same team are low). Picking tools that one knows well is also an advantage, but probably less of one, because there are far crappier corporate codebases than in-use open source tools (in general).

If the people are very far apart in ability, then those kinds of changes won't permute the ranking... on the other hand, if there's that much spread among programmers of equal rank, then you have an unusual team and a recipe for chaos.

Re:The Coming Collapse of Average Managers and Employees by arohner on Tuesday November 06, 2012 @12:06AM (#4747308)
> It depends how far apart they are.

Totally disagree. A level programmers are almost by definition, A level programmers in every language they've ever encountered.

For B level programmers, you're right, it's worthwhile to play tug-of-war on languages and tooling.

Re:The Coming Collapse of Average Managers and Employees by michaelochurch on Tuesday November 06, 2012 @09:24AM (#4748467)
It's not just about languages. It's about environments and coding practices as well. Sure, an A programmer can write quality code in any language. It doesn't take very long to learn a new programming language itself. Learning a corporate codebase and an environment (often broken) takes a lot longer. Three to six months, easily. Reputations are formed, and people are slotted rather inflexibly into the pecking order, in less time than that.

Being an A programmer won't stop you from writing quality Java code if you get to develop from scratch. The crappiness of the language may hold you back, but not at a career-killing rate, and it won't bring you below expectations because no one expects high productivity when Java is the language of choice. However, if you're dropped into an existing codebase and the code has a bunch of VisitorFactory garbage, being an A programmer hurts you. Good programmers just don't have much patience (or experience, if they can help it) with shit code.

Re:The Coming Collapse of Average Managers and Employees by lucisferre on Tuesday November 06, 2012 @10:23AM (#4748750)
But I think that really invalidates this whole premise that there is no such thing as 'A' players and that they are primarily a product of the tooling and environment.

Teams with shit code and poor unproductive environments, pretty much by definition, don't have 'A' players and the ones they do have don't stay long. Someone once told me "it's easy to retain mediocrity in a company, it's the talented people that are hard to keep." This is a chicken-and-egg problem, but in my mind it is the lack of quality team members and managers that leads to a poor environment all around.

That being said I've worked in environments like this, where tooling was poor, the build chain almost non-existant and there was a legacy of extremely poor architecture. I was still able to make improvements, bring in better code, architectures and dev practices (albeit slowly). For that matter, so was every other 'A' player I know that worked there. The main thing is none of us stayed there more than a year.