SommR - time in Automotive

When writing software in for the automotive field using domain specific communications protocols is inevitable. Those protocols are usually implemented by stack suppliers as closed source products. We will start our with the daemon which is center piece of the communication and find out why we need things like cloneable connections. Apps and the protocol they use to communicate with the daemon and subsequntily with other apps in the network is our next stop over. Here we disucss why we kept things simple, and peek into a very special serde dataformat. Before we reach our final destination – testing is another site we visit on our journey. By extending / overwriting our beloved #[test] macro we made testing more accessible and fun. Before we end we also check where we left the path to happiness, detoured and sometimes got lost which in our case boils down to versioning and observerability. We almost reached our final destination and all our experiences are collected in a journal, so writing documnation is the theme of the last leg.