Overhead is overhead does not really matter the context of computing.
We could translate as overload. The literal translation would be "above the head." It would indicate that it is above the person's normal size.
Just be aware that in our context the term is simplified and in fact it is the overhead cost . So the translation is "paying an extra price for something."
It is very common that the creation of an abstraction causes some overhead , but the holy grail of computing is to achieve abstractions without overhead . The opposite is getting an overhead without a gain in some other way.
This overhead can be processing, memory consumption, general time, transmission, storage, source code size, final code, use, learning, architecture, it does not matter, it's overhead you need something more to get what you want, usually compared to something else that in theory does not have overhead , at least comparatively.
Do not understand it as something inherently bad. It may have a compensating gain. Not all overhead can be eliminated, even if you give up something unimportant.
Overhead example is what is not payload , is what you pay extra cost to be able to transmit the data.
A TCP has an overhead compared to UDP, but it does have some advantages so it has higher cost.
A very complicated code has an overhead to understand. There is overhead an object needs for memory a>.
A function needs to prepare and finish running the code that it has to execute.
A indirection is an overhead .
It can also be exemplified by using a VM.
Finally, thousands of examples can be cited.
OOP can have multiple overheads and in addition to the more technical, already demonstrated in question linked , there is learning since it is not easy to learn to do right and not to abuse and the code becomes larger.
The pronunciation is "ververréd". Listen .