On the contrary, I think laying the bricks is plenty difficult in and of itself. But it's like wanting a share of the rent as a bricklayer of the apartment building that you are putting up.
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'.
While the comparison seems reasonable, it has one fatal flaw:
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.
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'.