On-robot and systems code needs tight control of memory and layout. This is the language of actuators, drivers, and performance-sensitive control loops.

Go is for fleet-side services, tooling, and concurrent IO: ingest, APIs, pipelines. It is usually the wrong choice for hard real-time actuator control (garbage collector pauses, no deterministic timing), which stays closer to C++.

Know which part of the robot stack should be learned and which should stay classical, and what can go wrong when a model is in the loop.

Diagnostics is where telemetry, fault detection, and safety meet. Study material only: I have not used CAN or UDS professionally.