24 ms·
I've never met a manager that wouldn't rather pay four average people $100/hr to solve a problem that one smart person could solve in half the time for $400/hr.
by stickfigure 9y ago
I've never met a manager that wouldn't rather pay four average people $100/hr to solve a problem that one smart person could solve in half the time for $400/hr.
There seems to be some sort of quasi-religious belief in the fundamental averageness of humans; consequently the difference between developer salaries at any company varies by maybe 50%, whereas the productivity varies by at least a full order of magnitude.
Until "management" realizes this, the only way that a developer on the upper end of the productivity scale can capture their value is to found their own company. I sometimes wonder what would happen if some company simply offered to pay 3X the market rate and mercilessly filter the results.
- Spooky23 9y agoWe already do that all over. It's called consulting. The outcome isn't higher quality or better work, just capture of perceived value. The super productive developer has a risk/reward ratio. When you get a little older, stability has a value of its own.
- noitsnot 9y agoIsn't the biggest value that you don't have long-term full-time employee and benefits to pay out.
- arcanus 9y ago> I sometimes wonder what would happen if some company simply offered to pay 3X the market rate and mercilessly filter the results. I've always heard this is the Netflix model. > difference between developer salaries at any company varies by maybe 50%, whereas the productivity varies by at least a full order of magnitude. I like your thought process but do you really believe this is possible? There are few fields where you can observe order of magnitude differences in salary. As you said, human nature seems to reject this, likely because it does not really occur in the wild. Even in sports it is rare for a particular position to have pay disparity to that degree.
- eberkund 9y agoWhat do you mean even in sports? What metric are you using to compare on athlete to another? Obviously one golfer won't be able to hit the ball 10x as far or sink the ball in 10x fewer strokes than another. Obviously a gold medal sprinter won't run 10x as fast as the an amateur. But they very well may be better than 10x as many others and that small difference in speed is what makes the difference between winning and losing. The claim the parent poster is making is different, because programming is much different than sports in that he really is claiming that one programmer can create 10x as much valuable work than another. Very different from saying that one programming contest competitor is 10x better than the average programming contest contestant.
- thaumasiotes 9y ago> Obviously one golfer won't be able to hit the ball 10x as far or sink the ball in 10x fewer strokes than another. Obviously a gold medal sprinter won't run 10x as fast as the an amateur. What's obvious about that? I can pretty well guarantee the existence of golfers who need 10x the strokes of professional golfers. I can definitely guarantee the existence of people who can't manage 10% of the running speed of a gold medal sprinter.
- mattkrause 9y agoUsain Bolt's average speed was about 23 miles per hour[0] when he set the world record (9.58 sec/100m). Nearly everyone can "run" 2.3 mph for a quarter-lap; that's not even a brisk walking pace. The 10x programmer idea also applies to adults working as programmers. If you were to limit the runners to an analogous population (runners, I guess, or even healthy adults), I'd definitely take that bet. [0] His peak speed was a bit faster (~27 mph), but the point stands...
- ramblerman 9y agoExistence is not enough, you have to prove it is the average. The 10x programmer is not 10x vs the worst programmer, but 10x vs the crowd. Most people could beat a par 3 in less than 30 strokes given 1 week of exposure to golf.
- quickthrower2 9y agoYou'd need a way to measure productivity. In a team environment that is not so easy. Is it the code, the communication, the business sense, building a good team? Who made that million? And who only made 10 bucks?
- stickfigure 9y agoThis is a fair objection, and probably a rational basis for at least some pay overegalitarianism. If management can't figure out who the star performers are, there's not much point in differentiating the reward. On the other hand, this seems like a fundamental management failure. The identity of the star performers has not been a mystery to the actual engineers working on every team I've ever been a part of. The information is not unknowable. Also, we already have a pay grade of "10 bucks": Some people get fired.
- quickthrower2 9y agoWhat developers think is productive and what is productive may be 2 different things. Your idea works in teams where everyone at all levels is switched on and tuned in.
- nostrademons 9y agoInteresting to compare your response with the current top comment, particularly the 4th and 5th bulletpoints: https://news.ycombinator.com/item?id=15033386 https://news.ycombinator.com/item?id=15033386 Seems like management is damned if they do and damned if they don't. If they reward high performers in proportion to the value they generate, they kill the culture of the company. If they reward everyone fairly & equally, then all the high performers quit. Full employment theorem for entrepreneurs, I guess. If management is rational, they'll never put the whims of one high-performing employee over the culture of the company as a whole. If that employee is rational, he'll quit and take his work directly to the market. This creates a fresh stream of new startups, each of which either has to be bought back for their true market value, or else becomes the new hot company that hires the masses and hemorrhages its high performers.
- lobotryas 9y agoI don't see how that 4th and 5th bulletpoint in any way contradicts OP. Popular != productive, although it can be hard to tell this apart in real life situations.
- nostrademons 9y agoWill management be able to explain to the rest of the employees why this person gets 10x their compensation? If not, it doesn't matter what the facts are from management's POV, it will lead to the same effect on trust & morale. Most people believe they are high performers and the work that they do for the company is valuable; if they didn't, they probably wouldn't do that work. If you have a workforce who believes they are all solid performers and then they have to confront the fact that management believes one of them is 10x better, you've got a recipe for a toxic culture.
- deegles 9y agoOne thing that I've learned over the years is that evaluating your own performance and the performance of others is in itself a skill that needs to be developed. Being able to reward high performers requires them to first be identified! In absence of the specific knowledge needed to assess perf, people fall back to likeability and other biases.
- rb808 9y agoMaybe but that makes sense when this "smart person" leaves then no-one knows how to keep their stuff going and the system is likely to crash and burn taking the manager with it. If you have a 4 person team you can handle people coming in and out over time, using best ideas from the team.
- nlawalker 9y ago>> I've never met a manager that wouldn't rather pay four average people $100/hr to solve a problem that one smart person could solve in half the time for $400/hr. In many organizations, quadrupling the number of people that report to you is worth doubling the delivery time, hands down. Number of reports is an easy measure of influence.
- patmcguire 9y agoThat's harder to prove, what I definitely see is roles staying unfilled open because the extra $10k a year to snag somebody faster is an obvious cost but six months of lost productivity isn't.
- starky 9y agoHow do you propose filtering the candidates? The only way to know for sure how they perform is to actually hire them and see how they perform after some amount of time. Since you will be firing a majority of people this causes a culture of fear. Interviews are far too unreliable for filtering candidates like you are proposing.
- aytekin 9y agoExactly. If you hire 4 it is likely that 1 will be very good and 2 average and 1 bad. If you hire 1 you probably hired the one who knows how sell himself/herself.
- eksemplar 9y agoThere is an inherent safety in having four average employee write something rather than using your unicorn. It's safe because three of them will still be around to manage it when one of them gets a new job, cancer or retires. On top of that, your unicorns are only really worth their wages if they are solving problems no one else can or if they are mentoring others.
- tropshop 9y agoOr, the group of four writes something an order of magnitude more complex. It becomes difficult to make changes, estimates grow, and execution is consistently buggy. With the right unicorn, one can act swiftly, groom a lean architecture, and make instinctive calls that move the needle of the entire roadmap. Real unicorns present sound technical strategies and inspire new opportunities that help push the company to the next level.
- gaius 9y agowhereas the productivity varies by at least a full order of magnitude I think we need to put the myth of the 10x developer to bed. 99% of the time, the 10x guy is just someone who solved the same or similar problem at his or her last job and are simply exercising their experience. Sure there are outliers, but that's the same in every field - whereas in programming 50% of people believe that they're the 10x guy and that all their cow-orkers are slothful idiots.
- meric 9y agoI think I'm 10x in some tasks and 0.1x in others, not sure about everyone else...
- gaius 9y agoI think probably most of us are but the 10x guy is someone who believes themselves to be 10x across the board
- scalesolved 9y agoI have met and worked with a few people that fall under the 10x banner. Incredibly clever people who kept their intelligence in check with pragmatic solutions. Some tough problems that took other skilled developers months they could solve in a couple of days and they could consistently do it across the tech and domain sphere. I think the issue is people claim to be 10x, if you're claiming to be 10x then most likely you are not, the 10xers I've met have all been very humble.
- dasmoth 9y agoI'd suggest virtually the opposite: a good way to be an outlier is to have reasonably broad knowledge plus being good at learning new stuff, such that when faced with a new problem you can quickly bring the right set of skills/technologies/whatever at it.
- jaggederest 9y ago
- marcus_holmes 9y agoIn my experience, the 10x programmer is a bit of a myth. Where I have seen people do some incredible feats of productivity, it usually came with a clutch of bad stuff, too. Like: - they didn't work well with others and soaked up a lot of management time dealing with their shit. - they had really limited areas of expertise where they were amazing, but couldn't fill in for a sick colleague. - they worked in 2-3 day sprints for ridiculous hours, and then stayed home or might as well have. I'm sure there are incredible people out there who can 10x and also be great team members, and I'm sure management are idiots if they don't pay them 10x. But in my experience, the people who claim to be 10x are usually just insufferable egotists who have no idea of the pain they cause for everyone else.
- viach 9y agoThis. And also, code if this kind if 10x developers is often unmaintainable and untested, which brings 100x effort for their teammates in the future.
- kpil 9y agoMy experience is that the long term effects are more than 10x. I heard a joke once : Complicated problems requires complicated solutions. Unfortunately, all problems are a bit complicated if you are a bit thick. The gist is that complexity grows faster than it needs. Ignoring people that can't make things over a certain threshold, there is a large group of programmers that can make things work, but are not able to build things clean enough or put in the effort required to build testable and maintainable code, simplify support and reduce runtime costs. Knowing when to stop and what to spend some extra time on is also important. I'll hesitate to add reducing future development costs, because I've seen too much overly complex code written in a misguided attempt to handle unknown future requirements. All these costs can easily build up to 10x over time. A factor is that a team probably smoothes over the effects of one or two bad coders in a way that it's not noticeable at short term - the code is delivered and the worst bits are plastered over, but the long term performance is reduced.
- honestoHeminway 9y ago
- sidlls 9y agoThese 4x (or 10x or whatever outlandish multiple) developers are rare, if they even exist, unless one constrains the scope of their work to a tiny sliver of their particular expertise. Hiring for such micro optimization is inefficient at best, ineffective usually, and counterproductive at worst.
- jusssi 9y agoIn my experience, 0.1x and 0.25x developers don't seem to be all that rare. The existence of a 10x developer is a question of what you use as a reference point for your scale.
- sidlls 9y agoNot really. It makes it a question of context, at best. Most of the time it also relies on extremely subjective measures.
- nilkn 9y agoI think the folks discussing whether or not 10x developers exist are missing the more basic point here. In most companies, a manager's status is determined almost entirely by how many people he or she manages. It's absolutely in their best interest to hire more mediocre people than fewer exceptional people because the correct incentives haven't been put in place for managers in the company. At many places, the best thing that can happen to a manager is for their team to become "too big". Oops, now they have to split it into two teams, and suddenly they're a Director instead of a Team Lead (or whatever titles are used).
- deleted 9y ago[deleted]
- tome 9y ago> In most companies, a manager's status is determined almost entirely by how many people he or she manages That's interesting. Not the total compensation of the people she manages?
- groby_b 9y agoNope. Total compensation requires nuance and access to the data. Headcount, everybody can see. And so, off we go to empire-build. It's a pretty hard impulse to resist. Especially since many places consider "growth" the ultimate goal.
- afpx 9y agoWhat incentives would rectify this? What metrics should be tracked?
- karmakaze 9y agoTracking results of each team. This is a start, however subjective and susceptible to gaming it may be.
- corporateslave2 9y agoCompanies do. They're called quant hedge funds and Facebook/google. If you're really 10x, someone will pay
- SOLAR_FIELDS 9y ago"Management" will never realize this because to some extent the reasoning is driven by ego. It feels better to be in charge of 20 mediocre producers than 5 amazing ones. Of course there will be exceptions but the general rule follows.
- morgante 9y agoIt consistently astounds me how many companies would rather hire 2-3 average developers (for average or below-average salaries) rather than one great developer for 1.5x the price. Here in New York, this is especially acute. Many finance companies have thousands and thousands of developers. They'll have a team of developers (costing maybe $500k/yr total) working on a problem which a single excellent developer could easily accomplish (and be happy with $250k/yr). Tons of companies are penny-wise and pound-foolish, mostly because programming is still considered a low-status profession. > Until "management" realizes this, the only way that a developer on the upper end of the productivity scale can capture their value is to found their own company. I sometimes wonder what would happen if some company simply offered to pay 3X the market rate and mercilessly filter the results. There are companies which do this, but they're almost exclusively pure tech companies (ex. Netflix).
- TheOtherHobbes 9y agoIn many companies you get paid for status, not for productivity or value. Management doesn't want super-performers, because they can upset the power dynamic. Developers must have lower status than management, and super-performers can challenge that. Companies are actually social networks. Instead of gaining status by posting selfies of yourself in exotic locations with cool people, you gain status by making high status noises in emails, talking in a high status way, having many people reporting to you, and having equity. Sometimes getting things done is relevant too, but not as often as it should be.
- morgante 9y agoExactly, that's why I think this is one of the biggest examples of mismanagement out there. For me, it's actually not about the compensation for its own sake. It's that compensation is a strong signal of how the company thinks about the status of developers.
- e59d134d 9y agoThis is also part of redundancy. If you hire 1 10x programmer and they get sick, no work gets done. If they leave, you will have hard time finding their replacement. 3 average programmers who understand your code adds a lot of redundancy. And as an interviewer, it is really hard to identify who is 10x and who is not. But very easy to tell who has enough knowledge and pleasant personality. Programming in most companies is team sports, not a marathon.
- Steve44 9y agoYou're still not guaranteed that by spending $400 per hour on one person with excellent credentials you will have a better outcome than with 4 x $100. There is also a balance of risk especially on longer term projects, with the 1 x $400 person there will probably be less technical oversight and also if they get ill or leave then the project is is serious trouble. I'm not advocating employing talentless monkeys, they still need to be good at what they do but from a business perspective it's a more complex and wider ranging decision.
- frubar 9y agoIf you spend a lot of money you're not guaranteed to get the best. But if you go cheap you are nearly guaranteed to get a bad developer/product/whatever.
- jlebrech 9y agothe reason they'll rather hide 4x people that are half as slow, is that they have bums in seats that are available for whatever hairbrained idea they come up with. the x10 (sic) coder will get bored of the mundane stuff surrounding the complex stuff s/he loves
- nopatternhere 9y ago"I manage a team of one very productive person" vs "I manage a team of four PhDs". Which does a partner prefer to boast about?
- JepZ 9y agoBtw. your example is missing the bus factor. But I understand your point and actually I do not think that salaries are meant to depend 100% on performance. I think it is more like 90% of time the person invests and 10% performance bonus. That way the one with to 50% higher salary would probably be 5 times as performant as the average dev. If that is fair, is a different (and very difficult) question.
- Mtinie 9y agoPersonally, as a product design manager, I like to find the middle ground. Having a set of "4x" employees is useful when you also have a number of "1x"and "2x" employees that can learn and grow from the influence of the highest skill and/or productive employees. Attempting to build a "quantity over quality" organization is bad for the reasons you list, but "all quality, no quantity" is a close second in being detrimental. Each critical "4x" employee that you have is only beneficial if they stay at your company. Burning them out because a company is ruthlessly focused on keeping their staffing lean by only hiring "4x unicorn-ninja-guru-rockstar" developers is a quick way to trigger management to swing the pendulum too far in the opposite direction. Edit: fixed a typo
- afpx 9y agoThis is often an information problem. To find an expert or specialist takes a lot of time. While it would be nice to always have an expert solution, sometimes we don't have the luxury of time.
- tmat 9y agoI ran into this problem.. I felt like I was worth more than the best offers I was getting. I continued to get job offers, but I couldn't get one for more than 100k remotely or in my area(Burlington, VT). I've got many many years experience, can solve any challenge, and work at twice the rate of most of the developers I have worked w/ in the tech stacks I focus on(ruby, elixir, reactjs/javascript/ember/angular etc).. So I decided to go at it on my own and charge a rate I felt I was worth. Best career decision I've made so far. I think every developer reaches a point where the only way they can make more is to move into management and stop being a developer, or branch out on their own. I myself hate being a manager and love being a developer. Managers generally seem to think that a developer is a developer is a developer. When there is a clear difference between a $50/hr developer and someone who can charge $250/hr in the time it takes to solve the same problem. What takes a $250/hr dev 1hr to solve correctly, might take a jr dev 5hrs to just "get it working."
- le-mark 9y agoHow did you line up clients willing to pay for what you're worth?
- tmat 9y agoI started w/ word of mouth and networking through people I already knew. I also started with a lower rate. I raised my rates anytime I had to much work to do. I discovered this technique from another friend. I was complaining one day about having WAY to many clients. He said and I'll never forget it, "if you have to much work to do, you're not charging enough." I started 2.5 years ago at $70/hr and am now at $135/hr after several rounds of raising rates. Sometimes I would lose a client when raising my rates, but that was ok and really was the goal. They were usually the most painful to deal w/ anyway. My best clients usually never even balked at it. Just said ok and kept on paying. I then got to the point where I needed to give myself a brand and bring on another developer because I started taking on very large green field projects(this was something my lawyer and accountants suggested for insurance/legal/protection reasons). At that point I got more advanced and started doing some content marketing, facebook ads, and google ads to keep the pipeline running. The hardest part was keeping clients lined up in the beginning. Because I would get a client, work the client and during that time stop looking for new clients. Which lead to a lot of down cycles with no work to be done while I looked for the next client. This is still an ongoing thing we're working on at this time to improve our client acquisition techniques. I also use a pretty unique billing structure that my clients seem to really love. You can read all about how and why we chose to do it this way here https://blog.grillwork.io/why-we-no-longer-use-fixed-price-contracts-and-our-clients-love-it-20a4d871efc9 https://blog.grillwork.io/why-we-no-longer-use-fixed-price-c... My partner and I now do about 20-30hrs a week for clients pretty steady and spend the rest of the time working on projects we own fully that we hope can generate recurring revenue. It has been a really fantastic journey that I hope never ends. Every day get really inspired by the stories on indiehackers.com and just find this way of work extremely fascinating. Very rewarding both personally and financially so far and I don't think I'll ever stop doing what I'm doing if I have anything to say about it.
- anindha 9y agoI agree with hiring the four people over the one star. If that one person leaves or is on vacation you have a hole in your team. There is a chance of the four who are not as capable today, 1-2 might become a stars in the future. He/she will be more loyal because of the opportunity the manager gave them.
- Aaargh20318 9y ago> I sometimes wonder what would happen if some company simply offered to pay 3X the market rate and mercilessly filter the results. As a developer, what I want is kind of the opposite. I don't want to be paid more than others if I'm more productive, I want to work fewer hours. Pay me for the value of my work, not how long it took to do it.
- programd 9y agoNetflix is known for a policy of paying well for talent and being generous when dropping people who don't work out, for whatever reason. Their culture document is a great read. https://jobs.netflix.com/culture/#introduction https://jobs.netflix.com/culture/#introduction
- mmcnl 9y agoThis is simple risk management. The risks are too big that you're paying someone $400/hr without the expected benefits. There's just a too wide margin of error. Pay four people, things even out if and the whole thing just becomes more predictable (and thus easier to manage). Managers are often eager to pay the cost of predictability.