[0] https://www.spiegel.de/international/business/we-know-where-...
[0] https://www.spiegel.de/international/business/we-know-where-...
Some organizations have some form of Enterprise Architecture group that governs technology and ensures that there is discipline though the maturity and scope varies. I would say most organizations are completely devoid of that type of supervision and oversight.
It's unfortunately far too counter to "move fast and break stuff" that startup space tends to be enamored of, because they tend to want you to do things safely and try to avoid a "Front page of the New York Times" type of security event.
I think they correctly believe security failures are at most a short term PR problem as far as the market is concerned.
You need a software first agile mentality from the leadership of the company on downwards and these legacy companies just dont have it.
Agile workflow for frequently updating non-critical software in devices that happen to be cars? Sure.
I can release a website with a list of known bugs. Do any govt allow release of cars with known bugs?
As long as you're reasonably confident that the bugs don't pose a safety issue I don't see the problem.
It's been an absolute disaster, with billions of dollars spent to produce delayed, buggy software.
https://venturebeat.com/offbeat/how-volkswagen-used-software...
The problem with software companies is they’re bad at hardware for the same reason.
User experience companies can be good at both. Maybe not as good at hardware as a hardware company, maybe not as good at software as software companies.
Apple’s the obvious example, but Google, Garmin, heck even Starbucks are also good examples. Start with the user experience, build hardware of software or whatever else is needed. Specializing in a tool has value, but limits you to that tool.
They build whatever hardware (in store) or software (mobile / back end) is necessary to give the user experience they want.
But you’re absolutely right — we can lump their mediocre coffee into hardware, or call it “goods” as a third category that you also don’t have to be the best at if you’re a UX company.
Safety-critical firmware is scrutinized fairly well (not because it's not a side project, but because of regulatory constraints combined with the small scope allowing the car manufacturers to treat it as a fungible good), but other software is not, even broken feedback loops interacting with that firmware.
If I could walk everywhere the rest of my life, I would.