In real world problems, there are many different constraints, mixed in with legacy code and tests along with many new requirements. It's hard to wrangle through all of those 1000s of lines of code no matter how you slice it, abstractions or not. I think sometimes people just want to vent that if it's hard that there MUST always be a better way. That's not always the case.
It's not gong to get fixed by just thinking about cognitive load. It's a very delicate balance: increasing cohesion and encapsulation, adding robust tests, also adding new features, not spending ungodly amount of time refactoring, being mindful of how easy it is to review etc. Even cognitive load is not the right way to look at it. If the abstractions give you very desirable guarantees in terms of performance and correctness, you need to consider it too.
The only difference between 1-2 star rating (using it as a metaphor) people and 3-4 rating people might just be a difference in opinion about how nice they should be or just how to normalize their score.
People do it often because it's a cheap way to feel smart without putting in any effort. It's the same reason how people mention Dunnking-Kruger any chance they can.
I doubt adding full context would help much in terms of getting a quality answer. Someone who answers questions in good faith will answer if they are there. All it would do is remove all the XY people I guess
This thing is some sort anti-intellectualism that's rampant in StackOverflow. Along with saying that X is premature optimization or is "Not invented here" etc.
I think a lot of developers get infected by this mentality and stifle their learning by handwaving that it's not important instead of just diving deep and being able to solve any technical problem
It's not gong to get fixed by just thinking about cognitive load. It's a very delicate balance: increasing cohesion and encapsulation, adding robust tests, also adding new features, not spending ungodly amount of time refactoring, being mindful of how easy it is to review etc. Even cognitive load is not the right way to look at it. If the abstractions give you very desirable guarantees in terms of performance and correctness, you need to consider it too.