Re:The undocumented Android change that led to aCropalypse w...
by ncphil on Saturday April 01, 2023 @10:44AM
(#35400680)
The salary range in a professional track does not _have_ to be too low. That's a choice, a value judgment, by management. Some companies do things differently. In at least one company I know, the professional track runs parallel to the management track: engineers can earn as much or more than senior managers, architects as much as directors. It's all up to whether the organization really values the services it's independent contributors provide. Sadly, many companies are not only indifferent, but hostile to the whole concept: playing at cost reduction theater and outsourcing to satisfy the avarice of simpleton investors. Bottom line is that tech pros need to take charge of their own futures and avoid the latter kinds of companies like the plague, when they have a choice. People need to make a habit of asking questions about professional compensation structures during interviews.
I agree; the problem with an engineer track is that the salary ceiling is too low, and you have to move to management to get higher salary. but then you end up not using your engineering skills, and waste potential.
What needs to happen is a way for people management to be done without a hierarchical structure. Aka, the senior engineer sits not under their manager, but that the manager is subservient.
Joel spolsky have written about this "problem" already in the last couple of decade: https://www.joelonsoftware.com/2009/03/09/how-to-be-a-progra...
> To make sure that the debate happens respectfully and on a rational basis of facts, it’s absolutely critical that the program managers and developers be peers. If developers report to the program manager, at some point during the debate the program manager is going to get sick of the whole thing and just say, “OK, enough talking, now we do it my way.”