Hopefully things have improved since then, but my perception at the time was that engineers in the field were paid and treated quite poorly compared to software engineers, despite having a significantly higher barrier to entry in engineering difficulty and technical knowledge.
The hardware team had a team lead at the staff level for years. Software, which had an equal headcount, was compartmentalized below the hardware team.
It was such a massive struggle to get equal salary, or a voice at the table for impacts to the software team.
At one point, IT added some new intrusion detection systems that increased our compile times from 10 seconds to over 600.... And we STRUGGLED to get our issue escalated because "it was a software problem" and the hardware team didnt really care about anything other than hardware issues.
Like imagine grinding an entire division to a halt, and not even raising that concern. Thats a Tier1 issue. It took over a month to get a workaround in place. IT wasnt ever really fixed. We were just told "youre not important enough so youre gonna have to deal with 3x compile times. tough"
But software in general - well, in America - got pulled up into the stratosphere by FAANG money. I feel that should have had more of an effect than it did on non-software orgs.
I’m still so dumbfounded by this. It’s almost 20 years since NVidia introduced CUDA. Developer tooling / experience appears to be something AMD does not understand, for some reason.
I remember my feelings when I learned how to use the Cell's SPUs and how much I didn't want to touch it with a barge pole after that.
I noticed that with mainframes and banks.
IBM makes some really amazing hardware at the very top of the market, but the companies who own those machines don't seem to think any competitive advantage can come from them - they are the cost of doing business. Because of that, the mainframe teams are often neglected.
I would even be happy to write code on the least sexy language ever invented, COBOL, just so it could run on the sexiest hardware ever built.
RF engineering, in particular, is punishing. The subject is viciously hard (you think shared mutable state is hard? Ha!) and, as people pointed out, for most companies, hardware engineering is considered a cost sink, not a revenue driver, something to be avoided if possible. The only parts where it's not is where companies do vertical integration instead of external suppliers.
At least you don't hate your job, I hope? The recent maturation of AI revealed how many people in software seemingly loathe their own profession.
I always had an inkling this was the case, but man it's been depressing to see it laid so bare. So many proudly screaming "I hated programming!". Well, I don't, I love it, and have my entire life, and imagine I'll continue to as long as they will let me...
More relevantly to the article and comment we're replying to: I miss doing firmware engineering. Gosh that is so much fun.
I remember my Apple II days (different platform, similarly constrained environment) where every game had a hard real-time multitasking core under all the code. In the Apple II it was particularly critical, because you didn't have programmable sound generators - you had to programmatically change the voltage of the speaker. If you were really crazy, you could do PWM and expect the electronics of the board would coerce your output square wave into something pleasant.
It never worked well, but it was still super cool.
The only thing I can see that acts as a bulwark is liability, bascially. The FW work I was doing requires a human and a large amount of careful review before acceptance. The "throw slop at the wall" that my current job is okay with won't fly there.
But there's _lots_ of FW jobs in consumer gear that is already filled with god awful slop, so maybe it won't take as long as I think.
For personal stuff? Sure.
But I certainly get why people get burned out on corporate programming. It's either tedious busywork following orders designed by architects whose last time writing code was 30 years ago and they never learned anything ever since, waterfall with glaring issues that the lowest rungs are supposed to magically make go away because upper management doesn't want to reset like they're supposed to, or it's "agile" in its various abominations. There's barely any time, budget or possibility left for actually experimenting a bit or for actually crafting out stuff that works. It's all output, output, output, and being micromanaged by Jira or whatever only adds to the dissatisfaction.
Personally, I left the field for good - I'm heading towards electrical engineering. Good luck coding a robot pulling physical wires.
Electricians might be temporarily safe from AI but EEs are knowledge workers too.
There will always be people who work to pay the bills, not to answer some inner call. I am happy - don't tell my boss, but I would do my work for free, including meeting users and extracting requirements (some colleagues say I'd be a master interrogator in another universe).
The AI trend and yet another redundancy foreced me to reckon with what I hate about software, which is a tech ethos of "move fast and break things" that runs contrary to "measure twice, cut once". AI also transforms my strengths into executive functioning tasks, which are a mental bottleneck.
I cannot disagree more.
Actually the synergy of software and hardware (primarily due to the increasing popularity of electromagnetics EM spectrums sensing like Radar/LIDAR/mmWave/THz/etc compared to sound) will create unprecedented beyond human perception and intelligence embodied and enhanced by physical AI. Heck the EXG sensings including ECG/EMG/EEG/etc that are technically part of EM, are now generating hundreds of papers/patents/articles everyday in which this product/patent/paper by Meta and its subsidiary CTRL-labs is only the tip of the iceberg [1],[2].
Please check my other comments for more contexts.
[1] A generic non-invasive neuromotor interface for human-computer interaction (Nature article):
https://www.nature.com/articles/s41586-025-09255-w
[2] Meta Ray-Ban Display (2025 - 962 comments):
China has followed Japan and Korea's lead in providing a low cost of capital for domestic companies, so they now have a generation of under-employed technical graduates, as automation replaces the "grunt work".
To build a $100M software company you need 5 capable friends and a cloud account. To build a $100M hardware company you need $500M.