More like automotive software is absurd PITA to work with. If you ever touched Autosar and ARXML files for configuration you would know that getting pin to change state every 10ms is operation for at least a week.

The models for ECUs are coming in specification files, which is PDF of 20000 pages and those documents are just page after page of Matlab Simulink-like schemas. Then these two are being compiled into few megabytes of firmware which may do what you want.

Debugging is also fun when you are watching RAM of whole ECU and then digging through state machines and why this state machine triggered? Oh because Fr_Tpt_Arghux_X has been set to 1. Why? Because signal from BCM module said so. Why? You don't have NDA for that, so write down bug report and have a meeting with team working on BCM to fix the issue.

Newcomers who are not constrained by Autosar and writing models in Matlab and also having access to whole architecture will be always able to get much better software out of the door.