The best analogy I have is to think of your smartphone from the perspective of a normal user. You're used to it working fine. But suddenly it stops working fine. So a technical friend hooks up a cable and turns on debug logging and all you see is a wall of gobbledygook. [1] You ask what's going on and he starts describing an enormously complicated array of components and systems, and explains that he doesn't really know how most of them work, and that there are a bunch he probably hasn't even found yet. He can try this and that and the problem maybe gets better and maybe gets worse. You're forced to realize that the phone you trusted and thought you understood is beyond your ready comprehension.
Even that analogy fails in that a) minds are much more complicated, b) they aren't designed, so there's no expectation that they should make sense under the hood, and c) you cannot buy a new brain. If it's broken, well, maybe it'll get better and maybe you'll just have to get used to it being kind of broken and be grateful it works at all.
[1] https://logmatic.io/blog/a-how-to-guide-to-debugging-with-an...