|
|
|
|
|
by Nextgrid
216 days ago
|
|
I think the whole tech career/ladder and concept of permanently employed software engineer is flawed and leads to unnecessary complexity and endless churn in the ecosystem. Despite what the techbros will claim, software once built requires very little (sometimes zero) maintenance. Similarly, not all software requires exceptional skill to create. But the career progression and compensation frameworks don't currently reflect that, which means there's an incentive for engineers to artificially increase complexity of their solution, introduce churn/unneeded maintenance, all to boast their own track record, get promoted and stick around, ultimately at the expense of the company who would be much better off with a functioning product and paying for one-off maintenance/alterations as needed. There's little correlation between someone's level on some company's progression framework and their actual engineering skill beyond a certain baseline; if anything I would say it is the opposite (the more "experienced" in traditional tech career progression the more likely they will deliver an overengineered solution, as opposed to a junior delivering a PHP script that fulfills the requirement simply because they don't know any "better"). I would only trust such a level if the person was lucky to be at the right place and time and their engineering efforts actually contributed to building/extending a useful product, as opposed to made-up busywork (with after-the-fact resume justification) which is closer to art (in terms of inventing creative ways of extracting salary from a company) than engineering. Ideally software engineering would be closer to trades like building or electricians/plumbers/etc. They get called on a job, paid their quoted amount, and are then responsible to deliver the quoted work ideally as fast as possible (for their own good, since they'd get paid the same but could enjoy the free time or go to the next job). They won't get paid to stick around so there is little incentive to make up busywork, and the work is closer to actual engineering which is to figure out a technical solution within the agreed requirements and budget. |
|