having hired an expert in this field, I can tell you they aren't really that sophisticated. I found myself with an absolute mountain of cash after an accident as part of a settlement. My medical insurance won't pay claims until I've exhausted that cash. The claims I had were much higher than even the mountain of cash. The lawyer I hired use a pretty effective strategy: he contacted all of the claims against me and told them we could engage in N-way negotiations amongst all the parties until we came to a settlement so everyone got their nibble of the pie. Or they could get X today, where X was some amount that was a bit less than the rate the industry actually gets paid for those services. They all accepted.

The discounts he negotiated left me with tons of cash & were in excess of the fee he charged me.

Maybe it should be "really learn about object-oriented programming (at a low level)".

Methods are functions, with an implicit argument usually called "self". Unless they are static, in which case, they are just regular functions. Classes are data structures, abstract methods are function pointers, inheritance adding data at the end of an existing data structure. In fact, inheritance is like a special case of composition.

Those who oppose object-oriented programming the most are typically the functional programming guys. But what is a function variable if not an object with a single abstract method, add attributes and you have a closure.

It will all end up as machine code in the end, and understanding how all these fancy features end up on the bare metal help understanding how seemingly different concepts relate.

Perhaps it was due to English not being my primary language, but it took me an embarrassing amount of time to learn that probability and likelihood are different concepts. Concretely, we talk about probability of observing a data given an underlying assumption (model) is true while we talk about the likelihood of the model being true given we observe some data.