4 ms·
I'm amazed that in this entire article Autosar wasn't mentioned once. The giant 2 ton elephant in the room here is automotives reliance on god-awful "kitchen si
by waiseristy 5y ago
I'm amazed that in this entire article Autosar wasn't mentioned once. The giant 2 ton elephant in the room here is automotives reliance on god-awful "kitchen sink" style standards. Try reading through the various Autosar docs and ask yourself if you expect robust bug-free code to be written to comply with it.
There needs to be a complete cleaning-of-house in automotive software.
I2C, Flexray, Ethernet, CAN/CANFD & OBD, LIN, what are we even doing?
ARXML, FIBEX, DBC, fuckin kill me.
"Unmanaged complexity" a.k.a "we've never thrown away a single technology or standard even once"
- obidan 5y agoI worked in the automotive industry and I can totally confirm. The worse thing is, there are now AUTOSAR experts and AUTOSAR tools and AUTOSAR Tool Experts and within that tool there’s a ARXML generator that’s generated with another tool … There’s no way this can ever become safe, robust, software. The worse part is, there’s so many careers that depend on this obscure skillset that I am unsure a change can come from existing companies.
- waiseristy 5y agoDont even get me started on the tooling. Vectors, Elektrobits, Dassaults, Conti's, tools are probably one of the biggest drains on collective computation power outside of crypto and ML. Not to mention working in this space is fucking soul consuming. I was considered an "AUTOSAR expert" for a time, and that essentially meant having enough programming and systems knowledge to work on the entire stack. But never writing a single line of code, only clicking buttons in these god damn tools and watching them crash constantly, loosing hours upon hours of work