3 ms·
> I think the problem that developers may feel is that they want to earn more money for being a better developer, but not nessicarily accept more responsibility
by margorczynski 2y ago
> I think the problem that developers may feel is that they want to earn more money for being a better developer, but not nessicarily accept more responsibility or spend less time developing code.
Well the problem is some people don't get there is a limit of how much impact and additional revenue you can create for the company by writing better/more code. And that would serve as a basis for paying you more.
The thing is a guy helping out via mentoring 10 other people or recruiting better talent will create much more impact on how the company functions than if he wrote 2x better code or 2x faster. There is simply in almost all engineering effort a hard limit of how much a single person can contribute.
- betaby 2y ago> The thing is a guy helping out via mentoring 10 other people or recruiting >better talent will create much more impact on how the company functions than if he wrote 2x better code or 2x faster. There is simply in almost all engineering effort a hard limit of how much a single person can contribute. Very debatable. Not at all true where I work ( worked ). Better code clearly larger impact on larger timeframes ( think 5+ year ) that perpetually retraining incoming juniors.
- hawk_ 2y agoThis line of thinking applies to creating widgets on the assembly line but writing code combined with solving the right problems can totally have 10/20 even 50x impact. Automation can be levered up quite well with the right setup.