Not everything about a subject would be immediately relevant to you. In fact, you can go very far without knowing certain elementary things in a domain. You could drive a car for a long time without knowing anything about how the engine works.

There can be things about any craft that you don't even have to learn at all. There is a chemistry to how molecules interact with each other when you are cooking, but you can be an excellent chef without knowing anything about it

Coding is an intellectual endeavour, and there are things about it that are absorbing and interesting. I believe in hiding complexity, but I don't agree with oversimplifying things. Imagine learning a new language and not being taught a single line of poetry or an expression. Where is the excitement in that?

It would be tough to learn how to play poker by just reading about it. At some point, you need to practice your learnings to get better at it. Coding is like that too. You can read all about it but what you learn needs to be enforced by exercises and examples.

I try to have relevant and applicable examples to real-life situations. I personally find it painful when I come across a coding exercise that is not applicable or so niche that I can't even bother to learn what is being discussed. Using Star Wars characters when teaching might be fun if your audience is into that universe but can be a barrier when they haven't seen the movies.

If I am learning statistics and being taught about it over an example of baseball, that means there are now two new things for me to worry about. There are much simpler examples to draw from and keep it to teaching one complex thing at a time.