I know, but it’s better for me to grasp *something* than to understand nothing at all and just give up completely. You shouldn't base your reasoning on what *you* can do—or what you think you can do— or what you should do (because everyone does the same) because my way of thinking is different from yours. The same goes for me: I can't expect you to understand concepts the way I do; you’ll understand them in your own way. The method I suggest might suit you perfectly, or it might not. In my case, the way the developers chose to explain their concepts doesn't align with how I process information, so I have to find my own ways to understand them. There’s nothing that can be done about that. You could go on forever about the importance of reading / understanding man pages, but it would be a waste of time—not because I don't *want* to, but because I'm not able. Fortunately, though, I’ve found my own methods for understanding what I read: finding sources that use less technical jargon, comparing them, and asking questions to AI.
NB : Check the picture attached to realize that I'm not using IA just because you think that IA put "—" in the sentences. This show how you are in bad faith. It's not the IA that puts "—",but the google translator.