Not everything needs to be dumbed down.
Some concepts cannot, do not, and should not have a “simple” explanation and should be covered with all their nuances. Some concepts are inherently complex because they solve a complex problem.
I am not against simplifying explanations; they are an excellent starting point. But, as you progress in your career, you might not find a beginner-friendly explanation for some things you are working on. The only way out will be to go through the tough explanation, some not-so-well-written doc, or some obscure code.
So, it is crucial to build a habit of reading more detailed, in-depth content, even as a starting point.
When something is dumbed down, nuanced details get lost in the process. Going through such over-simplified stuff gives you an illusion of mastery, but in reality, it has given you an extremely superficial understanding. This is precisely what makes people say things like “I will use NoSQL because SQL doesn’t scale”.
So, when you find time do hard things - read blogs, read papers, watch conference videos, explore OSS code, etc. you know the drill. By doing this consistently, you develop abstract thinking, which allows you to see patterns across different domains and helps you understand a complex system without getting lost in the details.
To be honest, abstract thinking is one skill that separates good engineers from great ones.
So, whenever possible, do not seek out the simplest explanation and challenge yourself. The goal is not to understand everything immediately, but to stretch your mental models, gradually build a deeper understanding, and in the process become a better engineer.