If people just want to copy+paste it then mark a jira issue as complete, that's up to them.
However, for those of us who want to understand - sometimes it's better to see a working example and pick at it.
So I don't see a problem with any dev having a line of non-understanding as they work. Some peoples lines are lower than others, but we all work that way. So it is all good.
but that doesn't mean you don't understand it.
You can get away with not thinking about it - for example, the error correction algorithms and protocols in tcp, or memory access - and that's because the designers of those layers have thought hard and long about how to keep it from leaking.
For js ecosystem, the designers (?) didn't think much at all. It is hobbled together rather haphazardly over time. Leading to the mess today.