https://www.smart-jokes.org/programmer-evolution.html
Most working programmers are in the middle near “seasoned professional.” They spend all their time thinking about how to manage complexity when they should be thinking about how to avoid it.
Eventually it might stop being such a cash cow - maybe thanks to endless numbers of teenagers hyping Fortnite.
I expected something basic that implements the login flow and some of the more important calls. Instead I found something that could be described as an C# architecture example application. If I wanted to learn C#, I think I could learn a lot about application patterns from it. MVVM, how to separate the concerns into separate "packages" for reusability and the likes. What I can't really learn from it (without already being a C# pro, I work in other environments) is how to use the API.
Then again I refuse to make FPGAs for HF trading firms, and apparently you can make bank there if you can put up with their crap.
Companies are realizing that the IoT node structure is not just a one-shot project that ships and is never maintained. It's part of the revenue stream. So the need for embedded Linux developers is increasing and the experience base out there isn't great. Again, having an RPi in your desk drawer doesn't make you an embedded Linux dev.
> So the need for embedded Linux developers is increasing and the experience base out there isn't great. Again, having an RPi in your desk drawer doesn't make you an embedded Linux dev.
Maybe things have changed, but in the past there hasn't been much financial incentive for devs to build up those skills beyond the "RPi in the desk drawer" (zing!) level. "Work hard, make a lot less than a web dev, be less hirable in the future because of your niche skills." I'm speaking as someone who actually did look into what training myself on some of Wind River's products would cost, about eight years ago, and looked into what the jobs paid.
edit: I can see by looking at a grandparent comment that we're probably in agreement
I worked for over 10 years doing Linux Kernel driver implementation. At Intel.
When I quit last year my base was $120k (150 TC). I couldn’t afford a house in the HCOLA I’m in. Remote wasn’t an option. For me a house is a prerequisite to starting a family.
So I left to get housing. Either making more or going remote and moving to a less expensive area.
Embedded is really fun for me, but it just can’t keep up in times of such inflation- especially WRT housing.
It's so satisfying to use 10,000x less resources to do something like full text search or handle 1,000 tps.
2. The people impacted are employees who now have a few days chilling. I would love to have this problem as an employee.
If anything they are part of the 25% of the company who just got a few extra paid vacation days.
You are only safe when you don't have bosses and all responsibility and power rests on yourself.
This is from 2018 and shows where you can actually have some rights as a worker. It's not hopeless: https://www.ituc-csi.org/IMG/pdf/ituc-global-rights-index-20...
My point was that tech probably isn't all that different from other professions where there are layers of management on top.
The parent comment made it seem like "tech" was worse than "other," which I'm not sure is true.
This doesn't really have that much to do with software. As with many other things, software can make it easier to have this kind of crap, but it is not the cause and not a prerequisite.
Case in point: Franz Kafka wrote The Trial 30 years before ENIAC.
A complete absence of tool selection, migration, or any preparation whatsoever, because the new tool couldn't be funded from leadership, so the horrible ship kept belching forward. Until it was shut down. End result was seventeen people sitting on their thumbs for years.. and a totally fragged publication environment that never recovered, the product of which will - at best - be waived on future contracts at some incredible cost. At worst, it will be yet another barrier to the already marginal business.
This was a management problem. They had a plan to retire obsolete devices, but no plan to replace them.
Cool and now I bet they have a new line on their procedures to ensure continuity of service (so that the next management can fumble this in new and creative ways)
I don't get the impression that this a tech-specific issue.
This is one of the primary reasons why I am totally done with Tech
The distance between users and builders is so excessively far apart now and the levels of abstraction for actually building things that are robust is just not even a consideration in software-centric design. Literally everything you have built after IDK 2000(?) will have exactly this issue. Just hope you're not at a scale that crushes people.
Software is the language of alienation and increasingly becoming unethical, as these systems are becoming increasingly impactful on the most vulnerable with no buttresses or supports preventing this kind of malfeasance.
It's not trivial. These are people's livelihoods at stake.