Chase Manhattan bank, the Netherlands branch, formerly the Nederlandse Crediet bank, about 3 years from when I was 19 to when I was 21, both as a systems level programmer as well as an application programmer.
> However they are conflating programmers and quants here
Yes, but I didn't, I only spoke about the programmers. They do not come up with the models, they just lay the bricks.
The algorithm developer has a different role here and is more than likely not the same guy as the one that codes it up.
a) Understand the model.
b) Come up with a fast algorithm for the specification.
c) Prove the algorithm correct.
d) Make no mistakes implementing the algorithm.
All of this has nothing to do with bricklaying. Moreover, it's quite ironic that the geniuses who come up with the models often "forget" point c) for their own work.EDIT:jacquesm, do you have a voting ring or why are your posts at 2 points (and mine at 0) the instant you post?
I can do both (lay bricks and code), and I think there is a distinct parallel between laying bricks and writing code. Both use simple, re-usable building blocks to create very complex systems that need to be built to high standards if they are expected to stand the test of time.
The equivalent between the architecture and the algorithm designer is a similar one.
To demand a share of the cake just for laying the bricks tells me that you should not be doing work for hire but that you should be working as an independent contractor or as a starter-upper. You can't expect 'none of the risks and some of the gains' in a position like that.
A 'mere' programmer, just like a 'mere' bricklayer can be replaced by another programmer or bricklayer.
An architect or an algorithm designer contributes something uniquely theirs without which an endeavour might not happen at all.
Programmers are a rare profession in that they seem to think that somehow their contribution to a project is unique enough that they by the simple act of transcribing a specification to a working prototype have become co-owners, no other discipline suffers from this misconception.
If you want a slice of the action put up your money, but don't just put in your time, expect a paycheck and a slice of the cake if all you do is code, you are more than likely to be found 'expendable'.
you are saying coders should be treated the same as bricklayers (salary); but are algorithm designers treated same as architects? I believe the former are paid percentage and later paid salary.
It seems financial sector do not follow the same rule as construction business.
If there is anybody on HN that has an aversion against voting rings it probably is me, and I wouldn't ever stoop so low as to cheat on something as silly as a conversation on a website (or anywhere else for that matter).
Whoever voted for me is free to step forward, I swear I haven't a clue who voted me up and you down.
edit: This sort of ticks me off by the way, within two days I first get this character calling me a troll: http://news.ycombinator.com/item?id=1556756 , now I have a voting ring? Way to go).
edit2: and if I had a voting ring my posting http://news.ycombinator.com/item?id=1560732 would not be stuck at 3 votes ;)
Wealth is all about percentages and the standard profit percentage share for professionals and engineers, "big-corp" or otherwise, is 0%. These programmers left to start their own trading companies, likely because the salary bumps being offered (a measly $45,000 extra on $150,000 base salary, in the example) were insulting compared to the revenue being generated directly from their work. That's demonstrable value. Consider: a 1% profit share from the example in the article would be over $300,000 per year. Not a large bonus at all for a financial managers or executive, but not an outlandish bonus for a highly valuable member of a lucrative enterprise, either.
Your last paragraph sounds a lot like, "keep your head down and be thankful you have a job." I assume you're just defending the status-quo and pointing out the tradeoff between sharing the risk/reward and being comfortably salaried. You can't possibly be implying that programmers or other skilled professionals shouldn't even try to negotiate better contracts, right?
When a welder helps to put together an oil rig that then either makes millions of dollars or explodes, sinks and causes billions in damage the fact that he did it as a salaried employee shields him from the damage just as much as it will insulate him from taking a share in the profits.
That's why it's work for hire. You get to decide up-front if that sort of thing is what you want.
So if someone offers you the opportunity to program a computer and make that company millions of dollars you are being compensated for your time, not for how much money your software will make.
The shareholders of the investment bank and the people that thought up the spec for the thing that you are building will have a much bigger claim to the profits than the guy that codes it up, and not surprising, they're the ones that will eventually make more money on it than you.
Why programmers should be different in this way from welders is not clear to me. Everybody that works for 'big-corp' makes the same kind of deal, and if you didn't make more money for the company than you cost you probably wouldn't have a job to begin with.