(d) in particular is worth stressing. There is no difficulty in attracting and retaining talent. There is simply an unwillingness to pay them what they're worth and give them an environment in which they'd want to work.
Supply and demand. It's pretty simple.
Yet so many (typically business types) want to treat engineers as an interchangeable cost center. "5 years ago an engineer cost $100k so I refuse to pay more than $100k now to keep my costs in check".
The fact that it's taken this long for engineers to be recognized (financially) for the huge impact we have and the vast differences that can exist between individual engineers speaks volumes about us. As a whole, we're just not as good as the business guys at this compensation game and, a lot of the time, it's not our primary motivation. Give us something interesting to do and stay out of our way and we're happy.
...erm, actually, students are remarkably goddamn insensitive to their future salaries when it comes to picking a major. And the other way S&D could equilibrate here is by fewer companies even trying to hire programmers because they know they can't afford them. What's really needed - considering the Camel Has Two Humps effect where some people have the magic programming gear and some people don't - is a mass effort to take students in journalism studies or, heck, smart unemployed adults, and administer some simple tests to see if they have large amounts of hidden programming talent, screw the college degree. But that effort would benefit lots of companies equally, and that means it's a commons problem. Not sure the Market Economics Fairy can easily solve this one.
Two years ago we appeared to have discovered an exciting and enigmatic new predictor of success in a first programming course. We now report that after six experiments, involving more than 500 students at six institutions in three countries, the predictive effect of our test has failed to live up to that early promise.
http://www.eis.mdx.ac.uk/research/PhDArea/saeed/paper3.pdf
Also, assuming this were not the case, it's hardly clear that searching for magic programming gear is a commons problem. Why couldn't Google/Facebook administer the simple tests and keep the results secret?
I forgot, they already try to do this, but it doesn't give them enough applicants: http://www.mentalfloss.com/wp-content/uploads/2008/02/Google... http://www.facebook.com/careers/puzzles.php
Or why couldn't a trusted third party, like Microsoft, Cisco or Red had charge journalism majors/unemployed adults to take the test?
I forgot, they already try to do this, but they just don't do a very good job and their tests have little predictive power: https://learningnetwork.cisco.com/community/certifications/c... http://www.microsoft.com/learning/en/us/certification/mcse.a... http://www.redhat.com/certification/rhce/
My only point is that the problem isn't creation of a public good, the problem is that reliably identifying good people/good matches is really hard.
Smart companies already do things to skirt credentialized recruitment paths, because credentials (especially academic ones) are extremely inefficient, at least in software.
This isn't so much "insightful" as it is a basic obvious direct result of the law of supply and demand.
I helped them as much as I could but none of them are now programmers because it's just too much work for no return to learn this stuff. You have to be interested in it, and supply and demand doesn't make more people actually interested in it...
Let's put it this way: how many people who go into investment banking are actually interested in investment banking? How many fooled around with financial models in middle school, then realized they wanted to parlay that passion into a career at Goldman Sachs? Maybe the odd freakshow here and there, but by and large, people enter the field for the moolah.
Right now, programming is still dominated by people who became programmers because they enjoy it. That they're well compensated is nice, but many of these people would probably be programming even if it didn't pay handsomely.
The Market Economics Fairy would indicate, however, that that'll change eventually. More and more would-be business or marketing or even journalism majors are going to choose CS when the salary average disparity becomes wider and more widely known.
This is the huge fucking source of programming talent that has remained largely untapped ever since CompSci became a recognized standard for employment qualification, due to the "monkey see, monkey do" best practices effect in businesses across the US. That blind best practices urge in hiring processes, in fact, keeps many actual programmers unemployed while firms in need of programming talent lobby congress to make it easier to import talent from other countries to fill the void created by their own hiring practices.
It's a perverse market right now.
What engineers really need to do is to put more skin in the game. Push for more equity, even if it means accepting a smaller salary. All too often I see programmers who just want a 9-5 that pays 6 figures even if the company is seeing hard times, but that won't improve the situation. Most of those business types you mention see engineers in the same way that engineers see themselves: wanting a large, stable paycheck. The business types shoot for the large end of year bonuses, which in general only get paid if the company does well (ignore the TBTF banks for a moment)
As an example of what I mean, most celebrity endorsements are lump sum payments plus a very small variable upside. William Shatner, taking a longer view, pushed Priceline to compensate him (for his celebrity appearance) in the form of equity, and now he's laughing his way to the bank. In this case, he was willing to take the risk.
A lot of engineers I know are like this because they were badly burned earlier on in their careers with promises of equity (while working below-market paying job for that equity) that turned into dust (due to massive dilution and other factors) even when the company had a very successful exit.
One could argue there they only have themselves to blame for not being sure of the actual value of their position in all possible exit situations, but now you're arguing they shouldn't just be engineers but also financial/contract law experts, which is especially unrealistic when they are just getting out of school.
What other options are there? Guaranteed end of year bonuses? Commissions in the form of profit sharing?
In major law firms, the associates aspire to become partners in the firm, which is analogous to my interpretation when saying "equity".
I'm not sure it would work, but if it did, it could be a perfect solution for keeping a great team together for the long haul.
It's a consulting company not a product company; it may be significantly different when "making partner" at a product company. However, from what I've heard, each partner at Accenture essentially runs his or her own business within the larger scale of the organization. Success is directly tied to the success of the internal mini-businesses. It is, however, an example of a company where IT professionals can become equity stakeholders in a private firm.
I imagine a product company would need to make the partners in charge of one product each (or maybe a couple of partners on one product) in order to avoid the "Too many cooks in the kitchen" problem.
Accounting and law firms may be a better example, though even they aren't as entrepreneurial as you think. They have their own regulations and internal politics.
Seems to be largely working within the specific space of Silicon Valley YCombinator-funded startups, but I'm not sure how well it scales. There's a pretty sharp filter for getting into YC, and for someone without access to PG's connections, the chance of hitting it big or getting acqhired may not be worth the risk they take.
I don't want an incentive scheme to help make you money. Pay me 20-25% of the revenue I generate for the company and give me a non-zero chance to be a stakeholder and I'll work my ass of for you.
At Andersen, at one point, I heard the number was $10M/yr of revenue.
It would be harder to figure out how much revenue is generated by an individual contributor (even if they are a superb coder).
Also, partnership usually involves leadership decisions
As for making partner in a BigLaw firm, folks I've talked to describe it as "a longshot" to "nearly impossible." A firm like Skadden will hire 500+ new associates a year (worldwide) and name maybe 4-6 partners, not all of whom started as associates. Unlikely the chance of going from associate to partner breaks 1%.
(Updated #s after asking someone who worked for Skadden.)
As for the chances of making partner, it depends heavily on the firm and the year. Skadden is something of an outlier[1]. The other big NYC firms bring aboard about ~100-120 associates per year, and promote between 5-15 depending on the economy. The last few years it's been around 5 and during the boom it was around 15. At medium-sized firms outside NYC, the %-age is more like 20-35%, though profits-per-partner at those firms are more like $300-500k/year, versus $2m+ at Skadden.
[1] Though your numbers seem grossly exaggerated. Worldwide Skadden brought aboard ~200 this year, which was a big crop. The two years before that were ~100 put together. And over the last few years, the partners promoted counts have been: 2007 (29), 2008 (25), 2009 (8), 2010 (6), 2011 (8).
"though this is not as good as equity as there is still no real ownership incentive." <-- this was the largest complaint to the investment banks transforming from partnerships to corporations (in the former case, the partners were personally liable for losses)
"There's no shortage of smart, hardworking engineers. There's a shortage of smart, hardworking engineers willing to work for very little money." ~ David "Pardo" Keppel
If you're having trouble hiring, it's probably because you're not paying enough. It turns out that talented people are worth paying a lot for.
$250k developer salaries invalidates much of that pressure.
So yeah, I think a lot of people would be jealous if they thought they received a 100K offer from google while some other person received 250K.
HN has lots of readers. Most probably make less than $250K even though quite a number make more. Still, most of those who make less than $250K probably aren't venture capitalists.
A million dollar deal doesn't get anyone chiming in with "but my deals aren't million dollar" 'cause they don't have deals of any sort. $250K salaries, on the other hand, do get exactly that reaction.
Is there anything here that isn't screamingly obvious?
According to OED (oxford english dictionary):
"A word formed by blending sounds from two or more distinct words and combining their meanings. Also more generally: a term or phrase which encompasses two or more meanings."
</language geekery>
(had to dig out a dictionary :/) According to OED (oxford english dictionary) a portmanteau is:
"A word formed by blending sounds from two or more distinct words and combining their meanings. Also more generally: a term or phrase which encompasses two or more meanings."
The key conditions here (each of which must be satisfied) are:
- constituents must be words
- blending sounds from the words
- combining meanings of the words
"blending sounds from two or more distinct words"
(note emphasis)
The word "brunch" is widely regarded to be a portmanteau, and does not consist of whole words.
This satisfies the 3 conditions:
- constituents must be words
"brunch" is a combination of "breakfast" and "lunch"
- blending sounds from the words
the beginning sounds like "breakfast" and the end sounds like "lunch"
- combining meanings of the words
described above.
-Constituents must be words
"cartelicious" is a combination of "cartel" and "delicious"
-Blending sounds from the words
the beginning sounds like "cartel" and the end sounds like "delicious"
-Combining meanings of the words
It's delicious cartel action, for repugnant values of delicious. I don't think this one is a strict requirement, in any case. This is getting a bit too pedantic.
Let's all agree that, before saying something like "a portmanteau, if you want to get technical", you are 100% sure that it is correct. Maybe that should be in the HN guidelines ...
I only brought up this issue because technically it's not a portmanteau (at least according to how OED and a bunch of other dictionaries define the word), and probably wouldn't have made a remark if the phrase "if you want to get technical" wasn't used ...
I lay down my guns ... now
If we believe the miscellaneous crowdsourcers of Urban Dictionary it comes to us by way of Beyoncé's coinage "bootylicious", which makes it pretty obvious that it derives from "delicious".
I'm amused by this part:
Parents and middle-aged talk show hosts often use this to parody the ghetto culture, much as they latched onto the suffix "izzle".
I do believe the Urban Dictionary has just called me a clueless white talk-show host! Oh well, if the shoe fits... ;)
a) Many of us watched our classmates go into management consulting, investment banking, finance, medicine, law, etc. These are all fields where $250k is not exactly outlandish for a 29 year old.
b) We have a lot of friendly, accessible fellow posters who write computer code and are financially very successful.
c) We talk about $X million valuations and $YY million acquisitions and $Z billion IPOs the way catering company owners discuss the price of tomatoes.
d) We have heard many credible people complain of how difficult it is to hire and retain engineers. So difficult, in fact, that they'd pay $10k+ just for an introduction or $50k+ for an actual placement.
e) We understand incentive structures and equity grants exist.
f) We routinely read industry news like "Google and Facebook in heated war for talent", "The going rate for an acquisition-to-hire is $1 million per engineer", "Four large technology firms were engaged in a gentlemen's agreement to conspire against their employees until the government told them it was cartelicious", "Productivity per engineer is going through the roof", "Company Z supports Q00,000 paying customers per engineer", "Efforts of individual engineers have succeeded in adding millions to billions of dollars of value to some companies", etc etc etc, and generally seem to be at least as savvy as C-students in Microecon 101.
and yet
g) Talk of engineers receiving wages above some magic threshold is met with disbelief, scorn, and a wee bit of jealousy.
It isn't hugely interesting to me what any particular person at a particular company is making, but is $250k an outlandish total compensation number? No, it is clearly achievable. Do you have to be programming demigod to achieve it? No, compensation moves along with several different axes and programming ability isn't the main one. Is this anecdote a freak of nature which we'll never see again? No, signs point that this will become increasingly more common over time.