News for hackers. Stuff that matters.
Re:Car companies are in a billion-dollar software war by FrankWilhoit on Sunday May 11, 2025 @02:01PM (#43955604)
Embedded-systems programming is not taught, and no one is willing to pay for training. The result is that development is outsourced to entities that claim, falsely, to have the knowledge. Eventually the consequences of the fact that they do not have the knowledge surface in an undeniable manner, and the only way to cover is to make a great show of a fresh start. (This affects all industries, not just automotive, but right now that is where the spotlight shines.)
Re:Car companies are in a billion-dollar software war by kevin_thibedeau on Sunday May 11, 2025 @03:29PM (#43956371)
Automotive has the problem of overwrought frameworks and no-code tooling that make it hard to fix problems and make improvements. Once the original devs are burned out or laid off the codebase rots and gets handed off to maintenance devs who barely know how anything works.

I'm waiting for a recall fix for the underpowered Sync 2.5 system to correct a backup camera problem. I'm not looking forward to worsening of all the current bugs with USB audio file playback that cause the UI to hang or not show a fully rendered display.

Re:Car companies are in a billion-dollar software war by tcmart14 on Sunday May 11, 2025 @02:49PM (#43956033)
I took an embedded course in university where we programmed the AVR AtMega 328p on the Arduino UNO not using the Arduino libraries and compiler. Make files and setting up an environment.

But yea, a single class probably isn't sufficient and also I image a lot of embedded companies have a preference to hire someone already familiar with the chip they are targeting and the toolchain for the stack. I also see a lot of asking for experience with RTOS, which in my class, we didn't use an RTOS.

Re:Car companies are in a billion-dollar software war by FrankWilhoit on Sunday May 11, 2025 @03:16PM (#43956255)
Programming embedded devices is not the same thing as "embedded-systems programming". The latter means, first and foremost, that the software is not allowed to crash, ever, for any reason, else it is people's lives.

I did some initial requirements work on a system to monitor continuous-web papermaking machinery; the line had to be stopped, physically and completely, within 100ms if anything went wrong, because an uncontained web of paper can literally cut people in half. They wanted, in order to be able to hire, to use one of the embedded flavors of a well-known consumer-grade OS, and I had to prove to them that there was no way to make any of them safe, at any cost. And they knew their hardware, because they had built it themselves.

The absolute last resort is a watchdog timer that hits the reset button if N milliseconds go by without the software telling it it's okay. This is what you have to implement if you are dealing with buggy and undocumented hardware -- as, all too often, you are. Sometimes you can get some doco for $ and an NDA, but then in order to get the real doco it is much more $$$ and a much tighter NDA, and the existence of that option is not even divulged until after things have already gone very far south.

If it were only a matter of reading the top-level doco for this or that chip, there would be no issue.

Re:Car companies are in a billion-dollar software war by sillystu04 on Sunday May 11, 2025 @03:23PM (#43956317)
Why do the hardware companies make things so difficult?

If I were selling hardware I’d want it to be as open and well documented as possible. So that more people buy it and so that I get credit for all the great stuff people make with my products.

Re:Car companies are in a billion-dollar software war by bigfatkitten on Sunday May 11, 2025 @06:05PM (#43957560)
Because then customers would see how rubbish the hardware actually is.
Re:Car companies are in a billion-dollar software war by jmb99 on Sunday May 11, 2025 @11:57PM (#43959518)
There are a few reasons, using the hardware manufacturers’ logic.

1) The more you open up your design and its behaviour, the more your competitors can learn about your product and how to possibly improve their own. Even stuff as basic as what specific features/capabilities a specific SKU at a specific price point has can be useful information.

2) The behaviour may be sufficiently undefined as to make documenting it impractical (or a bad look). Specs may also be padded (“up to 14 bits of SNR” may mean you’re getting 8 most of the time unless you’ve got a golden sample, and you’re not getting the distribution without paying big bucks and signing a big NDA). This ties in with 1) - if your competitors know your exact yields, they might be able to advertise being better/more reliable more truthfully, or even cheap out on their manufacturing a bit to drop their own yields down to match or just slightly beat yours.

3) The behaviour might be unknown. There’s obviously a crazy amount of validation testing that goes into high-end chips, but even the best test plan can miss things. This is especially true when you’re talking about high-speed stuff and anything involving power delivery/voltage fluctuations, or async/pipeline executions, or a million other things that can go wrong. Again ties into 1) - if your competitor knows that your chip might deadlock the radio with an obscure pattern of inputs and control signals, that could give them insight into how you’ve laid out your silicon and might give them optimization ideas.

4) If all the available info is given out freely, then potential customers can easily compare manufacturers and pick the best one. The manufacturers don’t want this, unless they’re the best, for obvious reasons. And, because everything’s locked down so tightly, no one knows if they’re the best until the chips are on the market and the volume contracts are already signed. And those contracts are hard to break, since the specs agreed upon are pretty vague due to 1-3.

5) The manufacturer knows their chips suck, but needs them moved anyways. This is rarely the case from most non-discount manufacturers, but it can happen. In this case, you don’t want to give away anything you don’t have to, because most info you give out is going to drive customers away to a better option. Good example in the consumer space is Intel refusing to publish acceptable voltage specs for their 12-14th gen Core chips, which resulted in motherboard manufacturers overvolting and killing high-end CPUs to try to meet the frequency specs Intel was advertising. If Intel was truthful in their voltage and frequency specs, there’d be a minuscule percentage of chips that could actually hit the advertised frequency at safe voltages, and 99% would have worse performance than expected, which would almost definitely result in lower sales.

6) The behaviour may be highly dependent on external factors. Basic example, a chip with external DRAM might have its execution pipeline stalled more or less frequently based of DRAM spec, or a wobbly voltage regulator might be known to cause lockups when certain executions are happening. Are you going to tell your customer those problems, or just say “we recommend high-speed DRAM and high-quality VRMs?” Especially if the other guy just says “we recommend high-speed DRAM and high-quality VRMs?”

The world would likely be a better place without such logic, but the incentive is there. Until someone comes and breaks the paradigm, I don’t see things changing.

Re:Car companies are in a billion-dollar software war by nickff on Sunday May 11, 2025 @03:02PM (#43956137)
RTOS-based development varies significantly from RTOS to RTOS, so I’m not sure how much it’d help to learn to use one. On the other hand, most fundamental OS knowledge is fully transferable to RTOS, so that would be helpful for embedded developers to understand.
Re:Car companies are in a billion-dollar software war by ghaff on Sunday May 11, 2025 @03:09PM (#43956195)
Yes, there’s a ton of specificity. Could probably say that about kernel dev too. But there is a ton of things people do that’s a lot more generalized. Of course I’ve used very little of specific things I got tested on in my day to day over the years.
Re:Car companies are in a billion-dollar software war by blueflow on Sunday May 11, 2025 @03:02PM (#43956138)
It is safe to say that Computer Engineering has a problem with enabling knowledge transfer.
Re:Car companies are in a billion-dollar software war by jauntywundrkind on Sunday May 11, 2025 @05:35PM (#43957356)
Yes! But it's also obvious that the industry doesn't have a prayer to ever reform. Stuck between proprietary and NDA's chips everywhere, using proprietary and NDA's toolchains and development kits, to product proprietary DRM'ed products.

This is an industry that is about as far from the light of science & enlightenment as it is possible to get, ensnared as deeply in the entangling anti-human anti-science Intellectual Property qualgmire-hell as can be got. Oh sure plenty of science goes it! It's fantastically interesting & technical! But aside from some Application Notes write-ups trying desperately to help move the practice along, move it out of jank, knowledge goes in, but it doesn't ever come out! There's such a lack of peershios with which to practice science, to report your findings to, to replicate works on.

The software world talks about its patterns and practices. The biggest industries on the planet are building software like wild AND are mad into open source. But... computer engineering is the shadowland, where no talk nor victories that happen there are allowed to be shared, where nothing escapes confinement. What a fucking plagued awful land of people unable to ever do the right thing, unable to bring their work out of the dark & into real civilization.

Re:Car companies are in a billion-dollar software war by nyarlathotep_ on Sunday May 11, 2025 @10:05PM (#43959001)
I can find 1000s of posts or blogs or whatever on every React nuance, Rust thing, LLM trend, or whatever, but nothing even describing what "real" embedded programming looks like in any fashion (I'm not counting blinking an Arduino LED here).

What does writing ABS module software look like? I'd actually love to know--it's not an area where you can "vibe code" your way to a 'working' product.

Re:Car companies are in a billion-dollar software war by gmueckl on Monday May 12, 2025 @02:52AM (#43960289)
Can't speak for cars specifically, but other software built to comparable standards requires a super rigorous process including detailed specs, risk analysis and mitigation, detailed design, comprehensive automated and manual testing against the soec including test coverage, tons of documentation on everything and finally a third party certification on everything.

The process is so far removed from typical web and business slop that it's an entirely different world of its own.

Re:Car companies are in a billion-dollar software war by odiroot on Sunday May 11, 2025 @03:24PM (#43956328)
I've been taught 8051 programming at my university. But I'm an older Gen Y, this could be going away for all I know.
Re:Car companies are in a billion-dollar software war by dmoy on Sunday May 11, 2025 @03:36PM (#43956437)
Embedded programming is definitely still taught... in EE.
Re:Car companies are in a billion-dollar software war by tonetegeatinst on Sunday May 11, 2025 @02:36PM (#43955924)
This is all the more frustrating as I'm in the security side if IT, and have been trying to teach myself C and assembly for embedded development and understanding how malware and vulnerability exist in this ecosystem and how I can help address these issues.
Re:Car companies are in a billion-dollar software war by maldev on Sunday May 11, 2025 @02:49PM (#43956031)
You can find router firmware sourcecode online and find pretty egregious vulnerabilities if you're really trying to learn.

Alot of embedded stuff is outsourced and doesn't want to waste the computing power for stuff like stack canaries. I recall the following from making a tool for a dlink? router?

//Reads a file name foo ReadFilePath() { // Get file name // TICKET 21321: Fixed crash by increasing buffer size char FilePath[100]; ReadFileName(&FilePath); }

It sticks out to me, since the crash was clearly from a buffer overflow, and they had this documented in the source code that increasing the buffer size fixes it. What they didn't realize was that the bug would still happen and you could get a buffer overflow from this and do whatever you wanted. This is the level of programmer you're dealing with who's writing embedded software in an overseas sweatshop. And the talent isn't even there domestically since they're severely underpaid compared to someone writing simple javascript.

Re:Car companies are in a billion-dollar software war by FrankWilhoit on Sunday May 11, 2025 @03:23PM (#43956325)
The people who actually can do it are not underpaid. These days they are brought in to do cleanup. They can name their price and pick their assignments.
Re:Car companies are in a billion-dollar software war by HideousKojima on Sunday May 11, 2025 @06:40PM (#43957829)
>The people who actually can do it are not underpaid.

The pipelines to create more such people are sorely lacking though

Re:Car companies are in a billion-dollar software war by jmb99 on Sunday May 11, 2025 @11:38PM (#43959420)
Only if you’re looking for top dollar when you graduate. Which unfortunately a lot of people are. It makes sense, most people pick this field for the salary and not out of passion (like the vast majority of professions).

But if you take a couple C/assembly/systems electives, look for internships at hardware companies, build a couple of toy projects on the side, and graduate with even a modicum of embedded experience, there will be companies that will hire you, pretty much guaranteed. You won’t be making 250k out of the gate, but you should still be making a more-than-livable salary (and frequently in a lower cost of living area than, say, the Bay), and if you pick companies correctly, you can be working with and learning from some truly genius engineers.

The pipeline’s there, it’s just not attractive (read: $$$$$$$) enough to pull in most people in the industry.

Re:Car companies are in a billion-dollar software war by bluedino on Sunday May 11, 2025 @03:31PM (#43956391)
Everything is just outsourced to the lowest bidder anyway
Re:Car companies are in a billion-dollar software war by tonyhart7 on Sunday May 11, 2025 @03:41PM (#43956481)
ok but why tho??? I have a lot of interest in embedded system

can someone tell me if there are any course that taught this??

Re:Car companies are in a billion-dollar software war by jeffrallen on Sunday May 11, 2025 @03:45PM (#43956518)
I learned embedded in the school of hard knocks.
Re:Car companies are in a billion-dollar software war by tonyhart7 on Sunday May 11, 2025 @08:04PM (#43958352)
Yeah but I want to make my time effecient, because failure which cost hardware can be expensive
Re:Car companies are in a billion-dollar software war by tehjoker on Sunday May 11, 2025 @02:08PM (#43955677)
I'm not sure this is exactly the problem. It sounds like turning the car into a platform with changeable parts has caused both organizational and technical problems.

To be fair, im still not sold that this is an advancement except maybe in simplifying the number of components. I'd prefer the car to work without "updates" and DLC. Why does my car need a firewall??

Re:Car companies are in a billion-dollar software war by cosmicgadget on Sunday May 11, 2025 @02:17PM (#43955748)
It needs two! One to keep engine fires out of the passenger compartment[1] and one to keep unauthorized users or code out of your infotainment and control systems.

[1] https://wikipedia.org/wiki/Firewall_(engine)

Re:Car companies are in a billion-dollar software war by DonHopkins on Sunday May 11, 2025 @03:36PM (#43956433)
All cars and should be equipped with two firewall extinguishers, one for the network and one for the passenger compartment.
Re:Car companies are in a billion-dollar software war by AlotOfReading on Sunday May 11, 2025 @02:18PM (#43955751)
It's not practical to produce a car that never needs updates. That would be a bug-free system, which is impossible. Since they're going to ship updates anyway, a lot of focus is on minimizing the cost and hence OTA.

For what it's worth, I work in this industry and the general rule of thumb is that every increase in validation from QM (standard quality) up to the various levels of safety critical code has up to 10x the cost per line of code of the previous level.

Re:Car companies are in a billion-dollar software war by v9v on Sunday May 11, 2025 @02:56PM (#43956088)
> That would be a bug-free system, which is impossible.

Why? If the rest of the car can function within design specifications for years, why can't the firmware?

I'm fine with updates to add compatibility with new protocols and such, but to me a bug implies there's a standing problem with the current system that's not due to some sort of wear/changing standard/component damage etc. While one can point to examples of cars with defective mechanical designs, I don't think anyone considers it impossible to create designs without such defects (where defects are defined wrt. specifications), why is this the view in software engineering?

Re:Car companies are in a billion-dollar software war by AlotOfReading on Sunday May 11, 2025 @04:11PM (#43956750)
The rest of the car doesn't function within specifications for years. That's what recalls are fixing. These days, a lot of software recalls are being issued to work around physical design "bugs". The Tesla cybertruck frunk pinching issues are a well-publicized example.

But, do you have an example of a software project anywhere that's bug-free? I'd include the space shuttle code, but even that famously high quality development process produced a (low) number of bugs.

Re:Car companies are in a billion-dollar software war by jmb99 on Monday May 12, 2025 @12:22AM (#43959627)
Not open source but mostly reverse engineered, and automotive: the PCM code for GM’s LT1 engines. The only thing that could be considered a bug is the behaviour of wide-open throttle fuelling, which was completely acceptable from the factory but made aftermarket tuning a bit tricky. Specifically, the fuel calculation routine would use the most recent BLM (short- and mid-term air-fuel ratio correction factory as measured by the O2 sensors) when calculating fuel delivery when wide-open, rather than locking it to a constant; the “most recent BLM” may be for a completely different area of the tune (like mid-RPM low throttle), where things like vacuum leaks or even just intake runner inefficiencies have a much greater affect on AFRs than when wide-open. This can result in either too much or too little fuel being injected, and under- or over-shooting the target AFR.

The reason for this is a physical limitation: the cars weren’t shipped with wideband O2 sensors, so there’s no way to measure the AFR when wide-open (since it’s targeting a significantly richer mixture, and narrowband O2 sensors can only signal whether a the combustion is stoichiometric, or rich or lean relative to stoichiometric, with no further info). The implantation is probably not a bug but rather a compromise; in an ideal world, the “most recent” BLM will hopefully be from an “almost wide open” part of the map, and the general rich/lean characteristics will be close enough. And, the fuel table in the factory tune is quite safely rich when wide-open, so even with a leaking injector causing the idle BLMs to be way off, the fuel being pulled when wide open will still be completely safe.

Aside from that, 128k of bug-free code.

Re:Car companies are in a billion-dollar software war by umanwizard on Sunday May 11, 2025 @02:34PM (#43955890)
> It's not practical to produce a car that never needs updates

Exactly that was done for decades.

Re:Car companies are in a billion-dollar software war by bronson on Sunday May 11, 2025 @02:47PM (#43956010)
Until 1994, the year of the first software-only recall, maybe. Things have changed.

Heck, manufacturers were issuing service bulletins to fix the fuel maps in their cars in the 1980s.

Re:Car companies are in a billion-dollar software war by AlotOfReading on Sunday May 11, 2025 @02:47PM (#43956013)
It was not. Recalls have included software updates (sometimes via component replacement) since ECUs became common in the 1980s. Reverse engineering the binaries and flashing updated parameters is actually how ECU tuning used to be done.
Re:Car companies are in a billion-dollar software war by miohtama on Sunday May 11, 2025 @02:45PM (#43955992)
But those cars are no longer competitive. There is only a marginal buyer group who wants to drive these "bricks", which would also unlikely pass the requirements set for new cars.
Re:Car companies are in a billion-dollar software war by rjsw on Sunday May 11, 2025 @02:40PM (#43955964)
Updating the software in the computers that control the car has traditionally been combined with providing diagnostic support for it through the dealerships, not done OTA. Having an OBDII connector has been mandated in vehicles for a long time, you plug something into it that lets you either listen to CAN bus traffic or reprogram an individual Electronic Control Unit (ECU).

Now that all vehicles have entertainment systems connected to the internet, I guess it is tempting to use that to reprogram ECUs, I haven't been working in this area recently though.

The first use case of connecting entertainment systems to a vehicle bus that I can remember was to read some engine settings and turn up the volume on the radio at higher speeds.

Re:Car companies are in a billion-dollar software war by gjsman-1000 on Sunday May 11, 2025 @02:46PM (#43955999)
> The first use case of connecting entertainment systems to a vehicle bus that I can remember was to read some engine settings and turn up the volume on the radio at higher speeds.

Is anyone actually begging for this though? And why do you need a full bus? This feels like a luxury car problem that could be solved over I2C or something.

I’m reading this whole SDV thing, and outside of using less ECUs, it seems like an overengineered solution to what was hardly a problem. If we can update ECUs already with OBD-II, step 1 is just making a virtualized OBD-II port that the infotainment system can talk to. Everything else can then stay unchanged until later.

Re:Car companies are in a billion-dollar software war by rjsw on Sunday May 11, 2025 @02:58PM (#43956103)
One problem is that the ECUs are fairly dumb, they each have a limit on how fast you can send CAN frames to them without overflowing receive buffers. The protocol to reprogram them starts by asking the target ECU how much of a delay is needed between each frame then needs to keep to quite tight timing constraints when sending the new flash image, I have written a Linux network protocol module to do this.
Re:Car companies are in a billion-dollar software war by vel0city on Sunday May 11, 2025 @03:07PM (#43956171)
I absolutely enjoy speed compensated volume. It's nice to have about the same apparent volume inside the cabin as road noise increases while not being very loud when going slow speeds or stopped.
Re:Car companies are in a billion-dollar software war by AlotOfReading on Sunday May 11, 2025 @03:07PM (#43956172)
I2C is also a bus, just one that's less reliable and involves more custom work to use.

A "virtualized OBD-II" is really just a UDS server if I understand what you're trying to convey. UDS is a dumpster fire of a protocol that should be expunged from existence, but my personal feelings aside can be run anywhere you want. That exists. I'm not aware of many systems that directly connect the infotainment processors directly to critical CAN buses. Usually there's an intermediary component to isolate them.

Re:Car companies are in a billion-dollar software war by tehjoker on Sunday May 11, 2025 @03:13PM (#43956230)
If you get updates at the dealership, you don’t need a network firewall.
Re:Car companies are in a billion-dollar software war by encom on Sunday May 11, 2025 @02:54PM (#43956069)
>That would be a bug-free system, which is impossible.

Yes, but code that doesn't get written does not have bugs. And I don't want to control the rear window defroster, wipers, climate control, fog lights or whatever, on a touch screen menu buried 7 levels deep while going 130 km/h. It's bad enough that coffee makers, light bulbs and tooth brushes now have updatable firmware.

Re:Car companies are in a billion-dollar software war by mrheosuper on Sunday May 11, 2025 @11:37PM (#43959419)
the people that design UI/UX is not the same people that write software
Re:Car companies are in a billion-dollar software war by nyarlathotep_ on Sunday May 11, 2025 @10:10PM (#43959026)
> It's not practical to produce a car that never needs updates. That would be a bug-free system, which is impossible. Since they're going to ship updates anyway, a lot of focus is on minimizing the cost and hence OTA.

What was wrong with ECU and ABS etc software prior to the OTA era that we're now apparently entering?

I've had plenty of cars--too many--and outside of a few warranty repairs involving re-flashing ECU/ABS(maybe), this was a very rare occurrence.

(Not counting deliberate tunes or re-flashes for modification purposes)

Re:Car companies are in a billion-dollar software war by mrheosuper on Sunday May 11, 2025 @11:34PM (#43959406)
They are not complex, so less breaking point to begin with. Also some bugs are considered not critical enough to do recall, they can be fixed when the owner return their car for maintainence. But now even those small bugs will be fixed by OTA update
Re:Car companies are in a billion-dollar software war by AlotOfReading on Sunday May 11, 2025 @11:00PM (#43959241)
Purely from a manufacturer's perspective (not personal opinion):

One, it's expensive. If your update takes half an hour to apply, under the old model someone's being paid half an hour to apply it. Either the manufacturer cuts the billable hours to the dealer and the dealer loses, or the manufacturer is paying that half hour out of increased prices to the consumer. With an OTA system there's usually no cost to anyone besides network traffic. This amounts to billions of dollars in savings for manufacturers.

Second, owners hate 1) paying for updates and 2) getting notifications about it in the mail. It generates bad press and bad experiences for the manufacturer.

Three, it makes the production line more efficient.

Four, the old systems sucked to maintain and for techs to use. They were also insecure and retrofitting security is impossible in a standards compliant way. The internet people have done a much better job with their standards.

Five, most owners are not like you and I. It's a feature for them that their car gets improvements and fixes automatically.

Six, you can be pretty certain what the rollout distribution is. Regulators don't like it when owners are driving around with years old recalls active because they forgot to schedule a dealer appointment. Manufacturers don't like keeping the inventory around.

Seven, "networked services" can piggyback on the same infrastructure and provide additional revenue streams. Certain corporate types think of this as one of the main benefits. Remember how manufacturers used to sell annual maps updates that no one bought? Some consumers also enjoy these sorts of networked services, which frankly I find a bit baffling.

Re:Car companies are in a billion-dollar software war by jmb99 on Monday May 12, 2025 @12:11AM (#43959571)
> It's not practical to produce a car that never needs updates. That would be a bug-free system, which is impossible.

Hmm, I disagree. Bug-free systems are expensive and hard, and get more expensive and harder as complexity increases, but you can absolutely produce a car that never needs updates. The vast majority of computer-controlled cars from the 80s to the early 2010s never needed updates, and the ones that did were performed at dealers (and were usually for non-critical things, because the critical things were simple).

GM had a good run in from the mid-90s to the mid-00s producing bug-free cars, even with some complexity. I don’t know of any software issues on any cars with LT1 or 3800 engines, nor with any of the tech in the Northstar Cadillacs. Displacement-on-demand could be considered a buggy implementation, but it was working as designed, and never got patched out, so I don’t think it counts.

That’s of course ignoring the decades of cars that had no computers at all. No software bugs being patched out with OTA updates in a carburetter (you have other problems obviously though, namely terrible fuel economy and emissions, and generally lower reliability).

If you make it a hard requirement for a car to be bug-free (maybe outlaw OTA updates and force physical recalls on any software problem?) I can guarantee manufacturers can make a bug-free car. It’ll just be way less complex and have way fewer flashy features, and will either cost more or have lower margins. It’s been done in the past, it can be done again.

There is a sweet spot for the level of computerization in cars. We had it somewhere around the year 2000, then waaaaay overshot, and haven’t corrected back.

Re:Car companies are in a billion-dollar software war by bitwize on Sunday May 11, 2025 @04:25PM (#43956856)
Companies are not willing to pay what the people who know embedded deserve. $150,000, $200,000 and up for a JavaScript webshit "engineer", $100,000 max if you work in embedded, unless you have a super specialist knowledge maintaining software on NASA's remaining PDP-11s or whatever that they can't afford to lose.
Re:Car companies are in a billion-dollar software war by jmb99 on Monday May 12, 2025 @12:01AM (#43959537)
Fortunately that is incorrect. I mentioned in another comment, but I’m well over $100k USD equivalent in salary alone as an embedded engineer, working in a relatively low cost of living area in Canada, graduated 3 years ago. Working for a “regular” company.

Maybe things just really suck for embedded in the states? But since my last year of university I’ve been inundated with recruiters for embedded positions, and I’ve never had a problem finding work. ~75th percentile in salary alone for software engineers in my area, ~55th-60th for Canada. I make more than every JS developer I know who graduated with me, except for the ones who moved to Seattle, Vancouver, or the Bay.

Re:Car companies are in a billion-dollar software war by bitwize on Monday May 12, 2025 @03:54PM (#43966868)
That's good to hear. Maybe Canada's got its head screwed on straight when it comes to assigning value to software roles.
Re:Car companies are in a billion-dollar software war by sarchertech on Sunday May 11, 2025 @06:24PM (#43957681)
My CS degree concentration is embedded systems. I love embedded programming, but it would probably cost me $200k a year to do it versus the backend distributed systems stuff I do now.
Re:Car companies are in a billion-dollar software war by jmb99 on Sunday May 11, 2025 @11:29PM (#43959378)
Admittedly I don’t know your salary or market, but it is possible to make decent money in embedded. Connections & market timing are both vital though, in my experience, as well as being actually good at your job. I’m in Canada so numbers are way different, but salary-wise I’m in the ~75th percentile software engineers in my area, my title is embedded engineer, and I’m fairly junior (3 years out of university, ~6 years full-time experience). I’m working with some other embedded people who are in the 95th percentile for software engineers in the country. The main problem is there are very few high-paying embedded jobs; conversely though, there seem to be even fewer highly-skilled embedded engineers looking for work. I recently interviewed at a company paying 50th-85th (based on experience) percentile trying to hire pretty much any competent embedded engineer, and their problem isn’t insufficient salary, it’s just a lack of applicants or any skill level. From what I’ve heard, the same seems to be true pretty much everywhere.

Now sure, if you’re looking for 500k+ jobs, embedded isn’t the area to be in, unfortunately. But I prefer low-stress, fun-environment embedded jobs, and don’t mind trading off salary for that. Different strokes.

Re:Car companies are in a billion-dollar software war by Zanfa on Monday May 12, 2025 @02:19AM (#43960144)
Problems like this always come down to salary. I love embedded (hardware in general, really) and would absolutely love to do it, but during my entire career, the salaries for embedded have been so much lower than you get for slinging JS/web shit. And now with 15 years in, the gap is even worse.

At this point, when I wanted to get back into hardware, it made more financial sense to outfit my home office with all the measuring instruments, debuggers, tools and other equipment necessary for embedded work and do it as a hobby. If I had the space, I could even get full-size CNC machines and still come out ahead cash wise. It’s insane.

It’s no wonder they can’t find experienced embedded devs, when it makes no financial sense to stick with it over a decade.

Re:Car companies are in a billion-dollar software war by rangestransform on Monday May 12, 2025 @01:43PM (#43965616)
it is possible to get an embedded-adjacent job that pays well over 500k (my friend was bit banging FPGAs), it'll just be at an HFT instead of a car company
Re:Car companies are in a billion-dollar software war by sarchertech on Monday May 12, 2025 @07:08PM (#43968299)
It’s definitely possible. There are probably a few embedded engineers making over $1M. But those are all outliers. It’s a whole lot easier to make $500k in web dev.