stedalus

This is pretty good advice overall. One small change I suggest is to take it easy on Design Patterns and the like. I’ve seen people in OPs position (general smarts but limited production experience) turn into architecture astronauts and start overengineering everything. It can be useful if you’re working on a legacy codebase and need to understand the jargon that can appear in [possibly overengineered] existing codebases.

Tesla is the only major manufacturer using induction motors that I know of. Everyone else is using synchronous motors with permanent magnets.

Your Python example doesn't really support your argument. Python succeeded for data analysis and scientific computing in part because it provided easy access to existing numerical libraries written in C and Fortran. So you got the best of both worlds: ease of use and near-native speed. It would not have succeeded if everything was done in interpreted Python.

I was once a physicist and I never understood it either. Maybe because a lot of software they produce is a blob of code?

To be fair to Zakarin, the finish is substantially steeper than the section Peter was on, and he had just spent the 30 minutes on the rivet to get the stage win.

Or if the option grant has early exercise.