I think this idea is often misunderstood and used as an excuse by people who don’t want to make any effort to understand a complex concept and want to blame the results of their laziness on the explanation or the explainer.
There are things where you may be given an explanation in simple terms, but the concept requires effort on the part of the recipient of the explanation to really understand. I’ll give an example: compactness. Probably anyone who has done analysis is familiar with how this concept is usually taught. Typically how it goes is you do open and closed sets and then they hit you with “a set is compact if and only if every open cover has a finite subcover”. Now this definition is extremely profound but very dense and it’s highly non-obvious why that in particular is the property you want (a finite subcover for every open cover)[1], how you could go about proving that every possible open cover in a certain situation could have a finite subcover etc etc.
In this case it’s actually quite easy to give simple explanations of the separate parts of the definition (open and closed sets, what an open cover therefore means, what a finite subcover then is etc) but actually understanding the concept of compactness requires something above and beyond whatever explanation you are given: it requires the reader to get out pencil and paper, try out some sets, go for some walks, think about it in the bath etc.
You may get a really fantastic explanation in simple terms from someone who deeply understands the topic, but if you don’t put in the effort you’re not going to understand it yourself. That’s not the fault of the explanation. It’s not an easy concept to grasp so you have to climb the ladder of understanding. The explainer can’t do that for you.
[1] it took the mathematical community years to settle on this being the definition, so you shouldn’t expect to understand why this is the definition straight away.
Nah that is just not a good definition for beginners. It shouldn’t be somebody’s first introduction to compactness. There are other definitions that are less general but more intuitive, such as sequential compactness: every sequence has a subsequence that converges to a limit in the space. For beginners working only in metric spaces, there’s no difference anyways.
Directly teaching the most general definition misses the steps it took mathematicians to arrive at this definition and is unhelpful. In set theory classes nobody starts by teaching ZFC; instead we start by the general comprehension principle, discover paradoxes and then introduce ZFC.
That’s also the reason high schoolers taking an introduction to calculus class aren’t immediately taught the epsilon delta definition. Start with something more intuitive. Rigor can come later. Newton and Leibniz didn’t start with rigor either.
While I agree that the receiver needs to make an effort to understand, I don't think I agree with this explanation
Your definition; "a set is compact if and only if every open cover has a finite subcover", requires a lot of prior knowledge to actually make sense of. When you say "explain it in simple terms", you are expected to explain all the needed concepts too
So what is a cover? what is an open cover? what is a subcover? what is a set!? heck, even what is finite/infinite? and what are all the new concepts you have to introduce to explain each of those?
The idea of explaining something in simple terms doesn't necessarily mean using a short, strictly formal explanation. It means making someone who is willing to pay attention understand everything (and this can usually be a long explanation). This requires a lot more effort than people usually think. Explaining forces you to remember concepts you assume others understands because with your own experience that feels already natural
In summary: - Don't confuse "compressing an idea" with "explaining it on simpler terms" - Explain it in a way an attentive 5 years old kid could understand
> I think this idea is often misunderstood and used as an excuse by people who don’t want to make any effort to understand a complex concept and want to blame the results of their laziness on the explanation or the explainer.
I agree to some extend. I work in DevOps and even though I've got 10+ years of experience in DevOps, many of those in senior roles, I have a very hard time explaining what it actually is I do, to my family. Take Kubernetes for example: it's an incredibly complex system which requires familiarity with many other complex concepts and theory (e.g., microservices and Continuous Delivery), it cannot be "dumbed down" easily even by those who understand it very well.
I could probably prepare a description of my work to my family which they would understand, but I wouldn't be able to do it on the spot. Not in a meaningful way anyway... "I produce and sometimes invent the automation steps and failure resilience for large numbers of computers and programs to operate" is just as vague as it is accurate, but I highly doubt any of my family members would be any wiser...
Because simple and short are not the same.
Simplicity means made out of essential concepts, but you still need to understand the concepts.
To me this boils down to being able to separate what is essential from what is not, and to do so you have to be knowledgeable.
Math has a factoring problem in that it's a very common tendency to want to minimize a formula, theorem, proof, etc by extracting out potential common parts / definitions as well as introduce notation to make it short. Like outlining a program with method names that are unicode symbols. That makes math full of indirection and cryptic symbols. Too much indirection overflows human intuition and makes things hard to understand.
It's not just math that does this, but it seems to be extreme in math.
Yes, ideally an explanation has all the irreducible innate complexity of the concept, but no more.
The extra complexity can come from struggling to polish and simplify an explanation, or the opposite, intentionally making it sound hard to trying to sound smart.
Idk. I kinda go the other way. I spend a lot of nights trying to fall asleep thinking, "could I explain how to generate electricity to ancient Athenians, based off natural observations" or, "supposing I was dropped into ancient Rome, and I could get by speaking Spanish, could I explain nuclear weapons to them?"
I don't really understand precisely every aspect of electric generators or nuclear weapons, mind you, but it's a good mental exercise: If I could build up a neat explanation to a Roman of what some magical thing is, in anachronistic terms obviously, then I probably have somewhat of a grasp of it.
Then I ponder whether I could actually help them build those things, and I think, yeah maybe if I had 50 years and unlimited slave labor I could get them part of the way there.
“It can scarcely be denied that the supreme goal of all theory is to make the irreducible basic elements as simple and as few as possible without having to surrender the adequate representation of a single datum of experience.” - Albert Einstein
Exactly. Or, they blame the explainer because they lack the foundational knowledge to understand said concepts.
There are a couple things that come to mind when you say this. The first is that it is indeed not entirely desirable to make the content easy to understand, as it leads to provably lower learning outcomes [1]. It therefore stands that this method is asymmetrically good for the one explaining. The second is the most natural use case for AI is 'summarize this in an easier to digest way' which robs that desirable difficulty. So effectively, a good way to learn with AI is to explain to it, which is counterintuitive.
1. https://bjorklab.psych.ucla.edu/wp-content/uploads/sites/13/...
I think a lot depends on the definition of simple terms.
For me simple terms means: assume the reader / your counterpart knows almost nothing about your subject.
Then divide your complex topic into steps large enough to make progress but small enough to become simple.
Then start by explaining step 1 and make sure the reader understands it.
Then proceed to step 2 and so on.
I meet a lot of people who can’t do that. They spend so much time explaining details at step n, where they spend most of their time but can’t properly explain how to get there.
At least when it comes to physics, I think it is how many "laws" you have to depend on when you are explaining something. The more laws you need to quote, the less you understand the thing.
And if you can explain it with no laws at all, then you really understand how it works...
Agreed. Sometimes people confuse simple with familiar. Even if what is explained is simple, it might seem complex just because it's not familiar.
My favorite pet example is the Burrows-Wheeler transform and its application to compression
It's actually recursive. The idea that this is misunderstood is often itself misunderstood, by people who don't understand a topic, and used as an excuse for their lack of understanding. "Oh, my audience just isn't willing to make any effort to understand, it's not ME who doesn't understand it well enough to explain it!"
And a level deeper, someone who does understand and explain something simply, could be mistaken for someone who doesn't understand, simply because they claim that the audience needs to do some legwork to understand.
Like most adages, you get out of it what you put into it. If you're the type to lie to yourself to feel like you win arguments, considering this concept won't help at all. If you're an introspective sort, it can help remind you to check that you really do understand a topic when your audience is confused. That's all.
> You may get a really fantastic explanation in simple terms from someone who deeply understands the topic, but if you don’t put in the effort you’re not going to understand it yourself. That’s not the fault of the explanation. It’s not an easy concept to grasp so you have to climb the ladder of understanding. The explainer can’t do that for you.
This is why we give recommended reading and pointers to those who really want to understand the topic.
I see it as the opposite - where labwork brilliant professors (who should remain in the lab) are forced in being teachers and managers, so they fake their way through awful lectures and poor pedagogy.
They write complicated derivations on the board with no real teaching, where I can go into a book and read the derivation myself.
I’m there to learn, not watch you rewrite the textbook on the board. If you can’t make the textbook simpler, there is no need for you.
> I think this idea is often misunderstood and used as an excuse by people who don’t want to make any effort to understand a complex concept and want to blame the results of their laziness on the explanation or the explainer.
It is even worse. They feel entitled to an understanding without putting in any self-effort at all! This has now become pervasive because we as a society have prioritized inanities like ego-soothing, everybody-is-a-unique-snowflake, get-a-sticker-for-everything-trivial, everything-should-be-fun etc. over actual striving and learning through effortful study/work. Everything is the fault of the teacher/book and there is no personal responsibility.
A Chinese Martial Arts saying which i often quote;
To show one the right direction and the right path, oral instructions from a Master are necessary, but mastery of the subject only comes from one's own incessant self-cultivation.
A good authoritative book can also be the stand-in for a Master in which case there is more discipline and effort required of the Student.
I agree a lot with your take about people not wanting to put effort into understanding a complex concept and blaming the definition, but I do think your specific example of compactness and the definition you focused on potentially illustrates the other side. For me, I think the point of compactness is easier to understand in terms of sequences. A big part of why compactness as a definition matters is because it specifies when a sequence will "run out of room" and be forced to converge to a point, so you can take limits and do calculus things with it. In finite dimensions, closed bounded sets are always compact, so it's hard to intuit why this matters. When you get to infinite dimensions, it's no longer true. You don't run out of room because you always have a new dimension you haven't been to to take the sequence in. That's where you see more of the value of a definition like "compactness" - it distinguishes where closed and bounded sets let you assume you're going to be able to force sequences to eventually converge and prove things with that assumption. For me, personally, encountering that sort of example helped me understand compactness much better and why I was studying it, even though I had spent a lot of time learning to prove things with the more abstract definitions. For me, it was a forgettable definition without finding the motivation for it.
I think there's a tension in how people mean "understanding". On the one hand, the example I gave (in my opinion, at least) helps understand the motivation of compactness and why anyone cared to define it in the first place. It makes it easier to understand why the abstract definition is stated the way it is, and provides some intuition that can stimulate approaches to proving things with it. Some of the sibling comments have discussed the tendency in math to distill education to focus on the top-level, abstracted definitions and discard the motivations that led to them. I think finding a way to incorporate those motivations is something that is often overlooked, at least in my experience, and may be some of what this point about "explaining in simple terms" (at least for me, in the example above it's "simpler" than the one you gave).
That is a particular form of "understanding", though, and it doesn't take away from your point. You can't take the intuitive, motivating example I gave and use that to make arguments about compactness without doing the effort of making connections to a more formal definition like the one you gave. In that sense, even if the example I gave were to help someone "understand" in the sense of getting a reason behind the motivation for compactness and what it's used for, it doesn't help them "understand" in the sense of giving them facility in actually working with it. That's where I see a lot of value in your point. Like you said, even if there are examples that may be more intuitive, there is a tendency to not acknowledge that really understanding some complicated things just takes some work.
I feel similarly about complaints I sometimes see about variable naming in programming. Descriptive names make a huge difference in some cases, but the reason a person who hasn't spent time to study differential equations and has trouble seeing the point of
dx_n = dx_p + dt * (-kx_p -cdx_p) / m
doesn't fully understand what's going on if it's written
derivative_of_position_at_next_time = derivative_of_position + change_in_time * (-stiffness_of_spring * position_at_previous_time - damping_constant * derivative_of_position_at_previous_time) / (mass)
...even if those words might help them some picture. I feel like a rough analogy for the concept might be, a person who really "understands" the concept, could probably come up with these variable names to explain the convention, as opposed to someone who has memorized the formula - but (oversimplifying at the risk being unfair to these arguments) there are also people who suggest the only reason they don't understand what the code is doing is because people don't write variables like in the second case.
“A set is compact when its points live in a finite number of neighborhoods.”
[dead]
[flagged]
I like to think that a “simple” explanation doesn’t necessarily have to be a short one. 3blue1brown is a good example of that. It took multiple videos for him to explain LLMs, but it’s simple and relatively easy to understand.
Actually, Feynman himself is a good example of that as well. His explanations are rarely short, but very simple. He has a series of YouTube videos where he explains all kinds of concepts like fire, but it still takes him at least 15 minutes to explain it.
So I’d argue that thinking it needs to be condensed into one or two sentences is getting the meaning of the expression wrong.