Programmers sometimes say they don't like abstractions (which hide implementations) because it requires them to manage a larger mental map of how everything works.
But for me, having fewer abstractions requires me to manage a larger mental map of how everything works.
But for me, having fewer abstractions requires me to manage a larger mental map of how everything works.
Comments
It's about striking a nice balance. The best abstractions I have used are simple, flexible, and solve complex problems.
When the balance is off, oh boy do you feel it.
But I imagine if abstractions are accurately named to describe what they do, then you don't need to hop around to comprehend things.
I can't keep track of the 5 sets of nested parenthases in a single line sometimes.
Notably, some people can.