Today many pedants rehash old lists of what the definition of OOP is and I think it's not useful. You see articles in broken English spammed to the Java discussion board on LinkedIn and the occasional person wanders into Hacker News traumatized by a job interview where they were asked to come up with a specific list, etc.

Abstraction is a basic principle for dealing with life, never mind software. For instance, imagine you are keeping track of bowling scores.

Well, you probably use the abstraction of "integer". Integer is overkill however because it can be negative, and could possible take an infinite amount of space to represent. Practically you might write the scores by hand with base-10 arabic numerals and you know how to execute an algorithm for abstract operations such as "addition".

Doing it on a computer?

Bowling scores can be as high as 300 so a "int8" is not quite big enough, but a "int16" is just fine and you wouldn't care if it was signed or unsigned.

In the 1960s you would learn how addition is implemented in circuitry if you studied computer science, today you might not -- you don't need to because Intel or ARM did it for you.

If there is a real problem with "Paradigm X" where "X" could be "OOP" or anything else, is that software tends to reify one particular view of a situation whereas different people involved in the situation see it differently.