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.
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.
It's not so much an explanation of magnetism as a meta-discursive about explanations, and why a "simple" explanation is often not really possible. (In this case because our notion of what is weird and requiring of an explanation ("things pushing things at a distance") and what is normal and not requiring one ("the glass doesn't fall through the table") aren't scientifically grounded).
I think it's precisely the situation seanhunter is describing in their example
I don't remember where I first heard this idea, but using 2 orthogonal axes of simple-complex and easy-hard provide a good framework for evaluating concepts. On this plane I would describe income taxes as easy, but complex. Juggling is simple, but hard.
As an example of this, you can have complex code made of entirely simple and easy to understand functions. But the complexity appears in the combination. That complexity can be far higher than were you to have more complex functions in the program. Which this is a common mistake people make that lead to tech debt. A lot of people try to simplify code by making it "understandable" without setting a floor to who needs to understand it and with how much time. If you don't, that floor gets lower each year.
If you can't think of an example of the first case, most machine learning models suffice. Take a simple feed forward ReLU model. It's trivial to understand ReLU. It's nearly trivial to understand the individual neuron. Yet I, as someone who wrote their PhD thesis on neural architectures, would call bullshit on anyone claiming they "really" understand what's going on in a deep network.
For sure. Binary is another example: it's just 1's and 0's, a bunch of on and off states that only make sense when you consider the entire sequence.
And in physics, everything is reduced down to 'simple' forces of nature. A bunch of interactions and relationships that add up, and if you can keep up and perceive it all, you can sometimes stay ahead of all those interactions and imagine how it works through intelligence.
Eventually, you reach a state where you understand enough about the environment to translate ideas from one mind to another through language and your understanding of the world.
And so some will have deeper understandings, and in different areas, and all manner of conflict and resolution arises as people with different understandings try and understand one another.
There's no end in either direction you look, but zooming in always reveal some simple interactions at work.
> There's no end in either direction you look, but zooming in always reveal some simple interactions at work.
This is why I actually hate the phrase "from first principles". I can't tell you what the first principles are, but I can sure tell you that when someone says that they almost certainly are not starting from first principles and almost surely are (often unknowingly) making major assumptions. First principles are something you need to find, not start with.
You're right, and it's subjective because of priority. First principles should be tied to whatever thinking requires the most concern in the moment.
If you're in charge of budget, you probably put budget before some other minor concern. If you're in charge of delivering a software feature, bug, patch, etc, you probably put something else first. It all depends on when something is due, or if something could jeopardize long-term prospects.
Everyone is on the hook for something. First principles thinking might be: think of your customer, and what they expect. Will whatever it is I'm doing affect them over the long-term? What about short-term?
If there's no clear answer, there's a lot of latitude to do whatever you think is best.
Honestly, I think you're pointing at something important that a lot of people miss. I make the claim that Apple was only successful because of both Steves. Jobs gets all the credit and tech people idolize Woz. Both are critical to the success though, just in different directions.
I actually think this is why a lot of software is going to shit now (even before AI slop). There's supposed to be contention between marketers and engineers (and even contention between types of engineers). If the engineer has too much say you build a great product but make no money and the business flops. If the marketers have too much say you build absolute shit and make money but you also forefeet a lot of potential revenue (opportunity cost). I think currently we've given the marketers too much say. Every time I talk to engineers they ask me where the "value" of something is and there's a constant followup with "no, I understand this helps the user, but how does it make money?" That's not the primary job of the engineer. This also creates problems because if a marketer can't understand the "value" of something then it just doesn't get built. So it shifts the objectives while people don't recognize that there is this baked in bias.
To tie back, I think a lot of arguments come to an impasse because people are working with different priors but assuming the other party has the same priors. It isn't uncommon to see people on HN (or Reddit) arguing what are essentially duals of problems. We just think that because we are using the same language that we're actually communicating. Like you said, there's no clear answer. Most of the problems in the world have no global optima. So how do you solve them? You have to define your constraints. But I rarely see that actually happen, though when it does conversations are really efficient.
As far as simple not being easy, its worth noting that Feynman only really hits his stride in the second half of his answer. That's how hard it is, a genius theorist and genius communicator still took a few sentences to start making it simple when given a backwards question.
A thing being more or less complex refers to the amount of information needed to encode its description.
"Simple" therefore means "reduced in information content".
The topic being explained has a certain minimal information content, and if you reduce beyond that, you are telling a fiction which bears analogies to the topic.
A simpler description is not necessarily short; rather, it is a description of something simpler.
When descriptions (of a given complexity, being held constant) are short, that can make them harder to follow, because encodings have to be clever in order to achieve compression, and that has a complexity of its own.
And there are entire categories of phenomenon that don't arise or are imperceptible in a simple context. Chaos is an emergent phenomenon that requires a surprisingly deep knowledge of a situation to predict where it will arise.
The way I understand the problem with explaining things in simple terms is this:
We usually introduce quantum mechanics students to a toy model -the infinite square well- to build up intuition. However, depending on the teacher and the students, it may well take years for those students to recognize and understand that the boundary conditions we apply to literally every other QM calculation are violated by the infinite square well, and while we ultimately recover the expected conclusion via successive approximations, it takes a much deeper understanding of the material to understand why the "simple" explanation is actually wrong. That is, while it turns out that the solution to the infinite-square well is, at the limit, identical to a very deep square well, showing that is actually quite a bit harder.
The simple explanation causes incorrect intution about the situation.
I'm not sure how you measure this in practice, when one way that explanations are simplified is to externalize a lot of information by reference to some specific terms of art (jargon, really). Where is the boundary for measuring the content, when we always have the implicit compression dictionaries of the speaker and listener to contend with?
This is also where the ironic part of simple explanations arises. Whether the explanation serves any purpose depends on the alignment of the speaker and listener background knowledge. An explanation between two experts versed in the topic may seem coherent, concise, and meaningful while it fails to teach the concept to someone new.
Sadly, it also works between cranks, who can agree on misleading or incorrect explanations. Or, sometimes novice listeners can believe they've learned, but they learn a different crank concept than what the expert believes was being states. A good teacher needs to be aware of these potential problems, attempt to ascertain the background knowledge of the listener, and adjust the explanation for that background rather than their own teaching knowledge. And followup testing attempts to ascertain whether the new concept got delivered or not.
Now that we have novices asking LLMs for explanations, I find this all quite troubling in a practical sense.
While verbose explanations have their place, i think it is being abused nowadays which actually obscures/obfuscates the essential points that need to be grasped.
I am a fan of old Science/Mathematics/CS books precisely for the reason that they are generally concise and succinct. There are no rambling asides/anecdotes, silly analogies, unnecessary pretty colourful pictures etc.
The best examples are the books from old Soviet-era "MIR Titles" and Dover Publications.
But length correlates with the prior knowledge of an audience. I love math, it is a great language, but it is dense as fuck and if you're not already familiar with a topic then natural language words are going to help explain the concepts.
> There are no rambling asides/anecdotes, silly analogies, unnecessary pretty colourful pictures etc.
Obviously some go overboard and I won't defend that, but this style has been around for centuries. They won out because it's effective. People are "multimodal" if you will
Well, the one on fire specifically is from a BBC series called Fun to Imagine released in 1983, and it’s been on YouTube for 17 years. So, you know, probably not an AI fabrication
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.
Exactly! I think this is a general problem in math, where we have this very "advanced" in some sense, definition of compactness. And mathematicians love such definitions, in the sense that it's quite easy to state and it covers a very general case. But it's simultaneously very unhelpful to actually understand why it's even interesting to talk about that concept, if all one knows is the most general definition.
I think rigor should be part of it from the beginning, but it's often best to start with the least general definition and then just explain each generalization step-by-step, and make it feel motivated and sensible.
> I think rigor should be part of it from the beginning, but it's often best to start with the least general definition and then just explain each generalization step-by-step, and make it feel motivated and sensible.
This an important part of good explanations. We can add providing plenty of examples and applications of the principles being explained.
However, when it comes to people, it all boils down to motivation. If the person writing is only trying to write the next year's edition of an every-year-updated textbook, the motivation is far from making things clear - then even step by step explanations and a lot of listed applications can be written in a way that only mystify the subject. Conflicts of interest is where the real problem is.
I'm hoping on AI, but I see some of it is following the erroneous path too, only open source AI can remedy this.
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
> 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.
That is seanhunter's entire point.
Simple to who? Simple given what prior knowledge? Is a simple explanation one that can be understood with an elevator pitch? Over drinks? Over several days? Longer? And to what degree of accuracy? I can give you explanations for things and it'll be simple and yet different experts who do understand will argue over if it is a good enough explanation or not.
> Explain it in a way an attentive 5 years old kid could understand
So I don't think this Einstein misattribution is a meaningful bar. It isn't even about attention. Some concepts simply need a lot of prior knowledge to meaningfully understand. Believing a 5 year old could understand nearly everything were it explained well enough would suggest that expertise is an illusion. Yet expertise exists because complexity increases exponentially as understanding converges (all those little nuances end up mattering).
I had no idea what any of that meant and your explanation did nothing at all but confuse me, and Claude explained it to me in a few minutes.
The example is terrible because they aren't explaining it, they are defining it. It's like asking to explain electricity and getting "it is the set of physical phenomena associated with the presence and motion of matter possessing an electric charge." That's not explaining it and no amount of effort on the part of the listener helps.
What did Claude say to you? Did it use more words? Do you have memory on? What did Claude tell you about this comment and what I'm insinuating? HN is a wide audience and I don't know you well enough. Is letting you infer a bad thing? I don't know how much I need to spoon feed you. Is spoon feeding you a bad thing? I'm actually curious what Claude will tell *you*
Exactly, it just shows Kottke's truism/platitude is wrong and absurd and thus pedagogy should be left to actual experts, there is some irony that today only people who understand advanced math are experientially qualified to point out just how mistaken the OP title is.
I think you might have misunderstood me. In no way do I think that definition is an explanation in simple terms.
I said in this case each of those concepts that goes into the definition can be explained in simple terms but actually understanding what you get when you put them all together takes thought.
That's an unwieldy amendment to the idea. Even Feynman's target audience was a college freshman. There's a hard limit to what you can explain to a 5 year old.
I’m guessing you haven’t interacted with many five year olds lately. Attentive or not, there are a lot of concepts that you’re not really going to be able to explain to them no matter how attentive they are. Or rather, they’ll take years to explain.
> 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...
I think this is a good example. Often each step is easy to explain in terms of previous steps. OK, you've got text. But you want to say where paragraphs are, where headers are, what's emphasized; so you add HTML. Ok, now every time you want to change how one type of thing looks, you have to change it everywhere in the document; so instead you invent CSS -- change the look once, it changes everywhere in the document. OK, so now every time you want to change something, you have to reload the whole page; so you invent AJAX. Ok, now... and so on and so forth. Going from zero to React is nearly impossible; taking things one step at a time makes sense.
Same thing with Kubernetes. OK, so you've got a bunch of servers. But that has problems, so let's to server virtualization. But that has problems, so let's do the cloud. But that has problems, so let's do microservices. But that has problems, so...
And in any case, nobody's going to listen to you explain microservices for 5 minutes and then be able to go actually manage a load of microservices; reality has a surprising amount of detail.
When asked about the topic of my main career, I usually say, "I can explain it in 5 minutes if you want", aiming for a tone of "you probably don't want this, but who knows, maybe you do". If asking about one of my obsessions, after the secodn follow-on question, I'll say "I can talk about this literally for hours; so I'll try to answer in short sentences. I'll keep talking as long as you ask questions; whenever you've had enough, just stop asking and we can talk about something else." Because my social circle is full of geeks, many of whom get just as excited about my obsessions as I am.
I usually use construction and maintenance of houses, factories, chemical plants and whatnot as an analogy.
You’re the person that designs and deploys and maintains reusable machines that are used across multiple chemical plants, and if something that seems very small goes wrong the whole factory grinds to a halt.
I don’t know the ins and outs of kubernetes. My takeaway from your description is you help keep complex systems up to date and running, systems people presumably rely on each day and could relate to(?)
Ops here, I just tell my family that I manage rented servers. But what is a server? Well, it's a computer, just more flat, more expensive and more loud. They are located in US somewhere in Virginia.
My family doesn't need an explanation what kube-apiserver is.
Sure, but then you are entirely avoiding the problem of not being able to simplify something complex even if you are an expert - which was my point exactly, i.e. sometimes it just is hard to explain.
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.
I think you misunderstand math, but in a common way. Math is a language. More precisely, it is a formal language. We invented these formal languages because they are well suited for things that need no ambiguity and high precision.
> Like outlining a program with method names that are unicode symbols.
Code is math. But the reason math says solve for "x" instead of solve for "betterVariableNameHere" is because it is traditionally done with pen and papaer and far predates the electronic computer. You could look at early computer programs, where they were constrained by space and you'll see that they too use minimalism. The reason we use long and meaningful names now is because we have tools like autocomplete.
> That makes math full of indirection and cryptic symbols.
But this is true of any language. "It's all Chinese to me." It takes a lot of time and effort to understand any language. It's also hard to understand purely from a book and needs to be understood through its culture and the people who speak/write it. Same is true for math. Same is true for programming languages.
I'm not talking about names mostly. I am talking about all the different ways that math notation employs recursion and quantification. They are all fundamentally different parameterizations that are contained in the lambda cube, it's just that writing all the different kinds of parentheses is (I agree) not what people wanted to do, or even knew they were doing, on paper.
> I am talking about all the different ways that math notation employs recursion and quantification. They are all fundamentally different parameterizations that are contained in the lambda cube
FYI, this is a subset of mathematics. But the reason lambda calculus generally has all those parentheses is because the formulation of that (sub-)language. Grouping those together and writing something nice and tidy is something that is done, but it also has drawbacks.
There is a purpose to the language and to that craziness. You aren't the audience and that's not a bad thing. Your lack of understanding is not a fault of yours. I wouldn't consider you stupid if you didn't know Cantonese. But I also wouldn't expect a Cantonese speaker to speak English to you. It is just a different language and people are using the language that is most effective to communicate with their peers. You don't have to be their peer. You're more than welcome to become one and I'm sure plenty of people would be happy to help you, but it will take time and effort to get there, just as it would were you to learn Cantonese.
> by extracting out potential common parts / definitions as well as introduce notation to make it short.
We don't really do that to make things short, we do that to make things more understandable. People underestimate how important good notation is to properly understanding things, and mathematicians spend an inordinate amount of time just refining notation until it makes things easier to follow.
Math is a tower of babel situation, and thankfully proof systems like Lean are now powerful enough and have enough momentum that the rendering of math for humans will be syntactic sugar over a more regular computational modeling (which is what was happening all along, just obscured by syntax).
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.
From TaxLaw 101: "Everything is income, unless it isn't". That is the entire subject in once sentence, but is also a flippant oversimplification, a tax lawyer trying to sound smart. A proper contextualized version would be "All income is taxable income, unless a bit of tax code declares otherwise."
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.
I don't know... I had to take Latin for 4 years as a kid. Latin declensions make it much harder, obviously, but what's Spanish except vulgar Latin? It might take a few weeks, or a few days in bed with a Roman lady.
Not sure how to explain Uranium. Plumbum, but more gravitas?
“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
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.
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...
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.
A Teacher can only do so much; even the best ones. It is the Student who has to put in Self-Effort to study/understand/analyze/think/modify and finally apply/practice.
That is not what I meant. I meant that this is something that should be applied in a student/teacher context. But something that should be introspective...
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
...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.
The article is just a bunch of quotes from Richard Feynman and John Gruber. There is little insight and I even think the article is misrepresenting the quotes.
Feynman said "if you can't explain it on a freshmen level". Leaving out that qualifier distorts the statement.
The other quote about the magnets is also overly reductive. Saying "I don't understand it in terms you're more familiar with" is not an admission that scientists as a group don't understand it at all.
You could go into what it means to understand something, but unfortunately the article isn't doing that.
Besides, the claim on magnetic force already serves as a counter-example to the main claim of the article.
Unless the article means to say that Feynman didn't understand the magnetic force, they have to admit that the magnetic force was perfectly understood, but impossible to explain in simple terms.
I think Feynman might have been referring to how spin was not understood (even by him), and magnetism is a result of a bunch of little spins adding up. I mean—even today—there are not really explanations that are correct and also understandable by a freshman. There's the belt analogy but, well, it doesn't really explain the physics.
That's not how I read it. Feynman started with the story of a girl going to the hospital because she broke something after slipping on ice. His point was that you can only explain things in terms that you simply accept without further explanation, otherwise you'd keep asking "why". Then he muses about imagining little rubber bands between magnets, but those only have their property in the end because of electromagnetism, so it's a circular explanation and thus unsatisfactory. To him, the magnetic field and its properties simply are, there is nothing underneath it.
Didn't Feynman mean "layman terms" when he muses how he doesn't quite know how to begin to explain magnetism to his interviewer (but goes about doing so in 'simple' terms, anyway)?
I would agree that there is a degree of survivor bias in Feynman’s context for that statement. You’ve survived the cull to incoming physics undergrad, which is always has some casualties. You have the potential to be interesting, and therefor worth bringing into the fellowship. You’re not an idiot, but you are ignorant and simple explanations do best to address that distinction.
These understandings and their accidental complexity also often inform composition of many distinct concepts into a solution to a complex problem. The brain must bear the burden of most of them simultaneously, even if you outsource the finer points to specialized teams during execution.
I think of learning as layers and depending on where the scientist is and the receivers are, there can be a huge mismatch in understanding. The difference between simple terms and familiar terms is why I can’t take the article as a rule or reference in life.
Explain to what level? E.g some topics common here. How do you explain NP in simple terms? "Things that are hard to compute?" That's simple, but not much of an explanation. It leaves the listener with a practically useless definition. And how do you explain even something practical as Heartbleed or Rowhammer? Etc.
And then there's another barrier, of course: the audience. You may use simple terms, and tell a lengthy story, but some things are hard to understand. Relativity and Monty Hall come to mind. They can be explained in simple terms, but how many people get them? Probably just the ones that also understand a detailed explanation.
So, should you also understand your audience, too? Is that ever possible? What if there's 300 people who listen to you with their own worldviews, viewpoints, health conditions (see different colors), life experience?
Literally yes, as much as possible. When preparing for an audience, you generally want to consider who your audience is when you're preparing your communication.
It doesn't matter what you know or understand, if you show up to a Spanish class and give a lecture in French.
But that doesn't have anything to do with understanding a subject. You can understand a subject perfectly without being able to explain it well to a large audience.
> You can understand a subject perfectly without being able to explain it well to a large audience.
The whole point of this discussion is this exact thing. It's about what "knowing" and "understanding" actually mean. Your second sentence is nearly the post title verbatim: You can know a subject perfectly without being able to explain it. That's literally the difference between knowing and understanding.
I don’t know why you sound surprised but the answer to your question is an obvious yes. It’s a no-brainer for any public speaker to understand their audience no matter how big. There’s no excuse.
Then the 300 people must understand that they can’s hope the same tailored custom presentation that the lecturer could maybe provide in a one-to-one exchange, and hopefully the lecturer will try to adapt as well as they see possible to the audience known general level and what are the expected outcome that the audience acquire in term of acquaintance with the topic exposed.
So that might be:
- pure general diffusion just to make general society expectation broadly aligned and don’t waste too much time on topics closed since literal millennia, but repeating the basics is not avoidable and even never enough (earth is not flat)
- the audience become aware of the topic be it in the most over simplified manner with the hope that if they cross a situation where it could help to know that some knowledge body exists on the matter and could be possibly leverage on (GPS is possible only because general relativity is taken into account)
- the audience are aiming to become expert in a domain where this knowledge is known to be useful for practical purposes, though it needs actually just enough background to situate the useful tricks (studying some engineer level domain)
- the audience is expected to gain epistemological meta-critical knowledge on the topic, such that they don’t only become fraction of last decile most knowledgeable on the matter itself but also how it emerged through history and how this influenced the shape of the theory and are expected to be able to teach everything on the matter at that level as an outcome (a group of people all having 7 postdocs each all in distinct domains, I guess)
I don't think explaining NP is that bad. Most people can understand what an algorithm is, some basic problems like sorting a list or TSP. If you just want to distinguish polynomial-time from non-polynomial-time algorithms, it's straightforward to give "obviously bad algorithms" (like brute-force search) and "obviously better algorithms" (pick your favourite) and to make that intuitive distinction precise.
Practical things like computer vulnerabilities are pretty easy to explain. I think anyone I know could understand what a buffer overflow is and why it's bad. The computer is a dumb machine and clobbers whatever you tell it to.
Relativity and monty hall are much better examples, I think. Relativity is well-studied enough that the explanations available for teenagers are pretty good, and if you study them you can get a pretty comprehensive understanding. But you do have to study them. Both are vulnerable to a certain kind of passive understanding, where correct arguments and incorrect arguments can both sound equally convincing.
> Most people can understand what an algorithm is, some basic problems like sorting a list or TSP.
Not sure I agree with this. Maybe most people have a vague idea of an algorithm as "something a computer does". Most people I don't think would grasp that you can have fundamentally different algorithms to solve the same problem.
I'm not sure most people have any comprehension about how computers (as in the devices they use) work - but they definitely understand the concept of a list of steps being followed to carry out a procedure (just not necessarily the part where that's what computers do).
Phrase a search algorithm as finding out if a card exists in a deck of cards with the rule that you want to look at as few cards as possible is more likely to be useful than saying you have an array of data on a computer. (To be able to do this faster than "look at them all" you should probably also say the deck is sorted)
> Most people I don't think would grasp that you can have fundamentally different algorithms to solve the same problem.
Most people do grasp arithmetic though, and I think you could easily describe a parallel in math to explain how there are different ways to get the same result
10+5=15
20-5=15 as well but subtraction takes longer for the computer to calculate
1+4+7+3=15 too with only addition but it has multiple steps so it takes longer for the computer to calculate
I think most people could draw a very rudimentary understanding of how algorithms take different amounts of time from that explanation
I think you could explain it as the fastest possible computer program for doing the task. Not the fastest made, but the fastest that ever could be made.
Then you can talk about how this optimal program behaves. If you double the size of the input (people can understand this in terms of file size), does the time double, or quadruple, or...? I wouldn't mind trying to explain NP to a lay audience. I think you could get it across pretty well.
You can probably do Monty Hall by enumerating all of the possibilities. There are only nine possible combinations of where the car is and which door you choose. The difficulty, I think, comes from overanalyzing the problem, and a simpler explanation actually makes the job easier.
Relativity is a goo example though. I don't understand relativity beyond the most superficial level. As far as I can tell, the teenager-level explanations of relativity are not right. They convey some aspects of relativity on a conceptual level, and even some basic things on a mathematical level, but they're omitting important aspects of it. You might read A Brief History of Time (or whatever your favorite explainer is) and come away with an understanding of relativity, but your understanding will be some combination of wrong and extremely incomplete.
I think that's the crux. If you don't get down to the level of your audience, it's sure to go over their heads (mixing metaphors here, but they seem apt). So, the article may have a point, but needs to change to "simple for your audience", indeed. But then the audience really needs to apply their intellect, too. At that point, you might just as well be educating your audience to understand the basics and a more complex vocabulary.
> How do you explain NP in simple terms? "Things that are hard to compute?"
There's a very common answer to this question: NP is the space of questions for which, when someone claims to have the answer, it's easy for you to tell whether they're right.
E.g. NP is a problem that's easy to check, but not easy to solve. NP is type of a problem like one for finding people: it's easy to confirm (is Mr. X in the room?), but there's no quick way to find solution (where is Mr. X).
This kind of explanation is arguably doing more harm than good, for at least several reasons:
- The property of a problem being "easy to check, but not easy to solve" is an extremely useful one[0]. It's also not inherent to NP problems. Most problems that have this property are not NP.
- The explanation omits entirely a different aspect, that's closer to a characteristic of NP problems: that they're all equivalent to each other mathematically, so if you find an efficient solution for one, you found it for all of them.
--
[0] - Especially so in the age of LLMs, as it's almost a definition of "what LLMs can beat humans at today"/what we can reliably use them for.
Very roughly, P = "easy to solve", and NP = "easy to check whether a proposed solution is correct". All problems in P are also in NP. The P =? NP question is whether the reverse is also true. A problem is "NP-hard" if it's at least as hard (in some very particular sense) as every problem in NP, and it's "NP-complete" if it's NP-hard and also itself in NP. It's these NP-complete problems which are in some sense all equivalent to each other.
There are still a lot of technical details omitted here. To scratch the surface:
"Problem" aka "Language" = "yes-no questions about strings", so for example "is this string the base-10 representation of a square integer?" (in P, and therefore also in NP) or "does this string represent a square grid of numbers that's a Sudoku (generalized to allow larger grids than 9x9) with at least one solution?" (in NP, and in fact NP-complete). "Easy" = "there exists a deterministic Turing machine which correctly answers the question on every input, and always runs in a number of steps which is less than some particular polynomial in the length of the input string". (In the real world, though, "polynomial-time" is not the same thing as "easy".) A language L being NP-hard means that for any NP language M, there's a polynomial-time deterministic Turing machine which maps M-inputs to L-inputs, where yes-instances map to yes-instances and no to no. Swapping yes and no is not allowed. For NP problems you only have to be able to check solutions in poly-time if the solution indicates that the answer is "yes". The corresponding family where you can check "no" quickly is called co-NP, and it is believed that NP != co-NP. Etc etc etc.
And yet the same explanation is used as computer science courses in universities. Simplifications have their limits. In short P and NP boils to polynomial and non-polynomial solution space.
Yeah no. No proper CS course claims that NP is defined to be “hard” problems (whatever you plugin for “hard”). NP is defined in a way where computation models EXIST (be it non deterministic Turing machine or witnesses).
The connection to solution space is also iffy and usually not how people introduce or primarily think of NP.
All your claimed definitons imply that NP and P are disjoint which clearly isn’t the case. I would be more careful
I can't explain these since I don't understand them. I can at most regurgitate some points about each that are true.
If you truly understand something, I don't think it would pose a problem to explain it to a three year old using only vocabulary that the three year old knows.
Realizing you can't do that is realizing you do not truly understand something.
You clearly have no experience with small children. Until the age of 10 or so, they can mainly grasp concrete ideas. Take the famous Piaget experiment. You can explain height vs volume to them in their terms, but they'll still reach for the tallest glass. At the age of 3, they cannot understand NP, Heartbleed, relativity or Monty Hall, no matter how it's explained. If that were true, we would all have graduated age 6.
There's a difference between explaining and teaching. Someone smarter than me can explain to me how quantum physics works, but that doesn't mean I will understand how quantum physics works afterwards.
If explaining was all it takes to acquire knowledge, everyone leaving school would have a deep understanding about every subject.
Lets put it this way - you shouldnt be a teacher probably if you can't even wrap your head around this while everybody else seemingly can.
I have yet to meet a single problem that when broken down to atomic parts wasn't trivial to grok. Every single piece of software. I am not saying 3 year old should understand details of general relativity, thats not the point.
> I have yet to meet a single problem that when broken down to atomic parts wasn't trivial to grok.
For one thing, we don't know how to break every problem down to "atomic parts". More seriously, the important things to grok in life are the things that are not atomic parts! If you look at quantum mechanics as a system of fancy mathematics with arbitrary rules, it is possible to become an unthinking machine that calculates outcomes. But that is not at all what it means to "grok" quantum mechanics! Likewise with relativity - it is very easy to have Lorenz transformations memorised but be totally unable to explain how e.g. the twin paradox works. Saying that's trivial to grok is utter BS.
It seems like you don't understand those things. I can envision explaining them in simple terms. NP isn't very complicated. xkcd had a great Heartbleed explanation in visual form https://xkcd.com/1354/
It was written when Heartbleed was in the news cycle. If you've never heard of it this comic won't help. If you've read about it but don't quite grok what it meant, the comic is great.
If he's never heard of it then yes. If he knows the context that Heartbleed was a mistake in server programming that caused them to leak private data? The comic is aimed at people who had heart of it on the news so they knew that basic context, but didn't really understand what it meant.
Whenever I see this I think to myself, “I can explain something in simple terms, but it will take more time than you have.”
Or in other words, “simple” does not imply ”short.”
However I’ve seen a lack of appreciation of this distinction play out in some exec meetings where “clarity” is prioritized above nuance. There is definitely great skill involved in crafting a message for an audience, and it’s critical to internalize that execs care about different things than you. But a minimum level of shared context is required before a discussion can fit into a 30 minute meeting. That’s why Feynman’s quote mentions “freshman level.”
I understand that execs deal with an avalanche of information and uncertainty, so clarity is a highly precious commodity. But I get the sense that “clarity” often means “just give me a simple answer”, which glosses over opportunities hidden in the nuance.
I don’t think this is true because it makes an assumption that reductionism is always possible, you can always distill every increasingly complexity into something less and less complex and maintain the overall behavior. I don’t think complexity is always reducible because sometimes the detailed nuance is absolutely critical to the distinction.
You may be able to take core ideas from something and distill them but when you have multiple interacting core ideas you may not necessarily be able to reduce them to simple terms. And almost always when you do there’s a big asterisk that the analogy has a lot of flaws.
Its just a way dumb people can counter with something that *sounds* profound and makes their ignorance look acceptable. Id also say it's similar to the modern american trend of "my ignorance is worth as much as your expertise and education".
I think it's not really about making simple analogies, because they don't really "explain" anything in the proper sense of the word. An analogy might make somebody feel like they understand it, but it doesn't really give actual understanding (see pop sci explanations of quantum mechanics).
It's more about breaking down stuff into simpler parts. For example, you want to explain a buffer overflow exploit in a web server. Then you'll ask your audience, do you understand addressing / memory allocation, and do you understand HTTP? If they say no to any of those, then you'll have to explain e.g. memory allocation first. And if they don't know how a CPU / RAM / caches operates, then you'll have to explain that first. And maybe you'll have to explain boolean algebra and how to build an adder from logic gates. And so on.
So I would claim that "reductionism is always possible". More complex things just take longer to distill into less complex things, but it can always be done. The exception would be things that "nobody really understands", like Feynman says about magnetism:
> I really can’t do a good job, any job, of explaining magnetic force in terms of something else you’re more familiar with, because I don’t understand it in terms of anything else you’re more familiar with.
Well I would push back on that claim because I don’t feel like you’re reducing things. You’re filling in gaps in understanding of something they already understand across the entire conceptual landscape it’s just masked by prior knowledge, they already know other concepts in detail and using a strategy to break a larger problem into smaller parts to make it digestible over time, you’re still dealing with the full set of complexity.
I think reductionism absolutely is possible in a lot of cases but I tend to agree with Stephen Wolfram’s concept of “computational irreducibility” or concepts we essentially know from compression in information theory (like Shannon entropy, Kolmogorov complexity) that there are limits to just how much you can reduce an idea or concept, and the bound for the human mind is likely much higher than those lower limit concepts.
Magnetic force is pointed out because it’s a more unique experience people don’t have a lot of prior knowledge and experience baked in that you can leverage as an assumption to reduce the concept, I think this holds true with lots of things. That isn’t to say we shouldn’t try to explain things simpler, just that that big caveat asterisk becomes ever more important when we use reductionist explanations. It’s not unlike when people try to explain spacetime curvature with a ball on a rubber sheet and things rotating around it… sure, that kind of gets at the idea, but there’s a huge asterisk that it’s simply not what’s really going on, it hints at the concept of curvature on a 2D plane you need to somehow conceptually extrapolate to other dimensions.
IMO understanding and explaining are two very different skills. I understand many topics, but I'm bad at explaining most of them, simply because I'm not good at explaining things, even mundane trivial things.
If your working as a teacher or professor like Feynman, then understanding and explaining may be equatable. In such a profession you are very practiced at explaining things and explaining something you understand should be easy.
However, the "in simple terms" part also makes a crucial difference for explaining. "Simple" for what audience? Simple mean very different things for a five year old, a college freshman and something completely different again for a tradesperson.
To explain things in simple terms you don't just need to understand the concept your explaining, you also have to understand what your audience already knows and understands and you must understand those concepts yourself too.
I think the real skill in explaining is recognising and utilising this overlap between your knowledge and your audience's.
CS Lewis, an academic in a completely different field (literature: Professor of Medieval and Renaissance Literature at Oxford), said something very similar.
Being able to break things down into simple explanations (maybe many of them though?) is a sign of rigorous thinking. Not being able to do so (which seems common in some fields) is a sign of the opposite.
The classical-Persian-speaking hakeems (sage) were of two categories: writing prose, and those writing poetry. The former (among them Ibn Sina [Avicenna], Razi, Alberoni, Al-khuarezmi [Algorithm named in his honor] would use prose because the topic needed a uniform deep treatment (philosophy, medicine, history [Baihaqi, e.g]). The explanations would start from simple and then build up into complex.
The latter group were poet-thinkers. They would write their findings (spiritual, mystical, social [social psychology, sociology, political science]) in poetic forms so elegant that these were at once both simple and complex. To the layperson with little insight and knowledge, they would make elementary sense and benefit them. But the more you knew, the more sophisticated you were, the deeper the meanings you could unearth.
So the latter group (Sanaii, Attar, Rumi, Nezami, Sa'adi, Hafez, I could go on) were masters of words and skill in presenting extremely rigorous ideas in the simplest, sweetest, most meaning-packed verses possible, without even appearing to break a sweat doing so. Rumi wouldn't even write, he would be in states of mystic ecstasy and send forth verse after verse which were hurriedly copied by the apprentices (mursheds).
PS (I am just a lifelong student of 'Oriental' languages.)
I've always considered understanding of a concept and being able to explain a concept as different skill sets. In many jobs, those two skill sets are combined and extremely useful when used together. But I've met some people who really do understand a concept, but for a variety of reasons, are not able to articulate it in simple terms.
I like Early Retirement Extreme's take on this[1], which notes that you can identify 'pseudo-experts' who don't really understand the subject matter by their tendency to parrot a collection of rules or tips when asked to explain concepts.
In terms of teaching and understanding, I experience two types of simplicity. There's the type where you understand it at a surface level, so you repeat the simple terms. Then there's the type where you understand it at a level deep enough that you then understand how to simplify the complex web of concepts well enough for the situation in front of you, whether that's teaching a beginner, or making planning decisions.
The problem I experience is that it's often hard to tell which type someone is if you're not also an expert.
I think applying this idea broadly is at risk of underappreciating the challenges of communication. Feynman was A) An exceptional communicator and B) understood the topic in depth. Absorbing an idea through language depends on presentational structure. People who haven't mastered that can still understand something in depth.
I'd argue that the ability to explain something in simple terms proves that you understand it, but it is not the only proof and understanding doesn't depend on it.
That said, it is a useful heuristic to adopt. The challenge of explaining something is itself an opportunity to find a deeper understanding.
It’s not even an explanation. How do calories translate to mass? What about water weight? You can lose weight a lot faster by dehydration than by calorie deficit!
Calories are saved by body into fat cells.
You can initially lose few pounds of water weight then it stops. So, you cannot really keep on losing water weight for several weeks, after first few weeks it will stop.
A calorie is a unit of energy, a fat cell is made up of matter. How does a fat cell store calories?
Remember, you’re explaining to a five-year-old. You can’t stop a five-year-old from digging deeper and deeper. They aren’t discouraged by hand-wavey explanations.
That depends entirely on the context. Within the bounds of how weight loss typically comes up, calorie deficit is indeed the simplest answer, and the best starting point to learn the rest on your own. That its over simplified misses the point a little bit. An adequately reductive explanation must account for both a comprehensive understanding of the subject matter and also an understanding of the context within which it is presented, to be any good. That is why its a great rubric for how well one understands something.
It is not intended to be anything more than a mental model for evaluating how well people you don't know understand something you don't understand yourself.
The more correct one would be pointing out that humans aren't dumb matter-to-energy converters. For many people, the body will happily down-clock quite hard in response to a calorie deficit; for others, it'll create irresistible psychological urges to fight the limit.
I'd probably go towards scenarios: imagine the body is a block of flats, and the municipal government decides for some reason to cut the city heating allocation for the block by half during a harsh winter.
Things that will happen include some combination of desired outcomes (people improving insulation, replacing radiators with newer ones, closing windows more) and undesired outcomes (people losing jobs and staying home and not paying bills, people starting fires indoors, tapping infrastructure to direct more heating to themselves, sabotaging neighbors, outright threatening or murdering neighbors to take their fuels, going out to the streets and rioting or attacking neighboring buildings or city council, etc.).
There's probably a simpler explanation to give, but I currently don't know an example of "self-regulating system" that most normies would understand. "Homeostasis" would be a perfect term, because it's something kids are taught about in primary education - unfortunately, as far as I know, most adults have no first clue what it means.
Yes. And we're not even considering whether weight loss is beneficial for everyone.
There will be so many studies at population level of how lower BMI correlates with people overall healthier, but that doesn't guarantee that slightly obese people would get healthier through weight loss.
It's misguided, but it works reliably on every human. If you are not losing weight you haven't reduced calories enough. If you don't lose weight on zero calories for a year you are lying.
Also, (simplified) mass is a form of energy, so I am not following how that assessment would explain the fault with the approach.
Why not jump to a more simple theory of mass in/mass out then? Why care about calories at all, especially as they're not a biological unit either ?
Trying to actually and reliably measure what happens on food intake at an individual level is near impossible anyway, so keeping the explanation simple would be a step in some direction IMHO.
Also understanding comes in different forms. You can understand something conceptually, in which case you can re-express it with alternate, more familiar metaphors, like LLMs are trained to do. But you can also understand something via aligned embodied execution. Like you understand how to balance on a bicycle, where you're not aware of your hip movements but you do them.
Ppl diminish things when they have a narrow conceptual scope of them, so ppl can diminish understanding to conceptual understanding if they live in a highly dissociative way, meaning they live inside their head more than most. So it's safer to say we 'have an understanding of smg' implying less totality, because there are usually angles and scopes to the thing that are still beyond us.
Yes, this is often obscured when working with code because it's relatively easy to judge its correctness. When using Claude to write documents, describe a system or organize requirements it becomes clear very quickly that Claude doesn't really understand what it is writing, it just puts probable things close together.
I think the problem here is the coding agent that we are working with are not familiar with the degree of knowledge we have around the system
It's like throw a lot of concepts at once that were just created 5mins earlier but the agent doesn't care that the human supervisor isn't aware about them and how they function, so it doesn't know what simple explanation in relative terms should be provided next
I think this is also implied in the article in the ending paragraphs
When making such strong claims that could easily devolve into semantics, it would be valuable to explain what you understand to be the definition of the semantic fulcrum of the claim.
In this case, that semantic fulcrum is what it means to '''understand''' something. Because the question of whether Claude understands things hinges much more on the criteria for understanding, than it does on our belief on the capabilities that Claude has.
Sure, I was mostly saying that to be a bit adversarial. I will say though that claude has had much less RL in certain areas, such that an explanation of e.g. why FTL travel violated causality is mostly remixing answers that are in the training data rather than a serious effort to facilitate understanding.
A too simple explanation can cause all sorts of non experts make opinionaded assumptions that you then must deal with. Physics and medicine are fields where amateurs roam freely with opinions
It’s a fact of human nature that people also talk about things they don’t fully understand, and sometimes even about things they don’t understand at all.
I’m not convinced that this is as big a problem as people try to make me believe, and I’m most certainly not convinced that the proposed “solutions” aren’t much worse than the problem.
Roughly speaking, to understand something is to be familiar with the details of its description statically, and also all of the dynamic relationship of its parts.
All of that adds up to an encoding of a certain amount of information; if less information is used to explain it, then what is being described may be simpler, but doesn't match the real topic.
Sometimes what requires less information is a useful abstraction: something being explained contains details which are not relevant to a certain class to which it belongs. If you can't explain it in simpler terms, that could indicate that you only understand the instance very well, not the class.
A student could not get the distributive property in a Math class. Just could not get it. Looking him in the eye I asked him about going to the store and buying a package with 5 pencils and 3 erasers...and how many of each you'd get if he bought 4 packages.
He got so angry when he realized how simple it was. Who knows how stupid he'd felt because no-one had explained it that way before?
It's a subtle relationship of meanings between conveyor and recipient. There are many minds out there that need a fourth or fifth different explanation.
Sometimes, the easiest, simplest way to explain something complex is in complex terms, because it is irreducible to simplest-possible explanation.
Complex explanations are either reducible, or they're not. Advanced mathematics requires years of compressed knowledge to explain something within itself.
Said differently, the same way you can't summarize any of the Nassim Taleb books (he takes pride in that). OR how watching a movie trailer and then the movie itself later, the experience gap will be very wide.
There are also complex topics that even lack a complex 'language for explanation'--for instance, quantum physics. The math works but not even the persons responsible for discovering it know why.
People can drive a car without understanding it deeply enough to be able to troubleshoot and repair it. But few drivers are under the delusion that they are car mechanics.
You don't need understanding to use something. For example, I have a grasp on both sarcasm and irony. I recognize it when used, but maybe not always. I can use both myself. But I have trouble explaining the concept of irony, since I do not truly understand it. Sarcasm on the other hand is easy to explain. It's mocking someone with nice words.
A lot of work went into transformation of the car into something that is easy to use and easy to explain to a degree that makes it usable. Much of the complexity is hidden behind simple interfaces. This happens everywhere to provide simple building blocks so people in other domains can use them. Often it doesn't come for free but usually it's worth it.
When I first learned programming, I could explain it to a layperson because the things I learned were fresh in my mind. Now, I've internalized so many lessons that I don't even think about them consciously when I pick a paradigm to approach a problem. I have to really dig deep to think about why I'm making certain choices.
This discounts the existence of a lot of neuro-divergent scientists, mathematicians, etc. who not only understand their fields, but also can vividly visualize thing in their minds. But explaining thing in simple ways may not be their forte.
A lot of folks in the comments seem a bit offended by this notion. Perhaps it works better the way David Graeber defined bullshit jobs: it’s a bs job if the people doing it think it is. So, try to explain something as simply as possible and if you fail, ask yourself: hmm, I wonder if I don’t really grasp the core insight here as well as I thought I did?
Isn't this sort of a mild continuation of Ludwig Wittgenstein's 1921 masterpiece: that thought, language, and reality share the exact same boundaries? Going back to brain cells from my college days, which are very old and crusty here. But the basic gist as I was taught it was if you can't say it or write it down, you can't really think it.
Found this on HN, last week I think, so I am sure a fair people know about it, but if you are messing with AI currently and agree with this line of thought, Jane Street put out a socratic-tutor skill that pseudo tries to break it down to this level and challenge those assumptions that make things flowery in business language, but often happen when we are taking the risks and overextending our technical competencies in order to impress clients. Maybe that is more telling of myself, but if you haven't, take it for a spin:
i have had plenty of people confidently explain things in a simple manner to me, but they have no idea about what they are talking about. humans and other entities do it online all day long.
It is possible (although unlikely) that someone could explain something to you without understanding it themselves. For the most trivial example, you can imagine a television host reading something off of a teleprompter. I suppose you could counter that such things do not count as “explaining” though.
That's the converse of the claim, which is (understanding something) => (being able to explain it in simple terms). This doesn't imply (being able to explain it in simple terms) => (understanding something) which is what you're considering.
So, I sued to think that, but I now reached the point of my self where there are many things in my life that I understand but can't explain.
First, because "understanding" is not the one size fit all word people think it is.
E.G: you understand riding a bike, but none of your explanations, no matter how detailed (and they are going to suck), are going to lead someone to bike.
Second, because communicating requires a channel, usually a common vocabulary and a shared set of experiences, to be able to exchange on the topic.
E.G: there are things that are such internal or personalized experience there is not much to transmit to the other party like some things that happen during meditation.
And both points at the same time: what the experience of seen is to a blind. Communication is useless. Knowing more about it (the frequency of light for example) is not going to help.
Third, they are just things that "you know". "You understand". "They are perfectly clear to you". You didn't gain this understanding; it emerged, or it seems like it was already there. You can use the fruit of this understanding in a perfectly fluent way, and there is no doubt in your mind, plus your experience has always confirmed it.
And yet, you can share that.
So yes, while the initial idea is true for many things, I'll add this 3 nuances.
> E.G: you understand riding a bike, but none of your explanations, no matter how detailed (and they are going to suck), are going to lead someone to bike.
> And both points at the same time: what the experience of seen is to a blind. Communication is useless. Knowing more about it (the frequency of light for example) is not going to help.
I think you're arguing against a point nobody is making, that the ability to explain something must also somehow faithfully transmit the ability for the other party to perfectly comprehend and replicate it for themselves. Indeed, that is probably never the case, for any idea or concept.
My reading of the argument is that it only really concerns your own comprehension of the concept, and the subsequent ability to distill it down to its essential bits, and not if the other party is in a position to comprehend it fully. For example, a good pastry chef could break down the concepts behind baking choux, in a way that another baker who's unfamiliar with it to understand the concept, maybe even replicate a decent version of it. It obviously isn't going to work if the other person has no concept of baking, or what an oven is. Your examples require all those background concepts and contexts to also be somehow transmitted in the explanation.
Bike into the direction of tilt. It's an inverted pendulum. I could explain it to a Kindergartner. Just like balancing an upright racket on their hand takes some practice and standing upright takes some practice, balancing on a bike takes some practice to build the system 1 pathways to make the adjustments at low enough latency. That practice is not a matter of understanding.
I would like someone to explain magnetism on simple terms and not make assumptions about my knowledge and experience. Simple terms tend to be less accurate if kept short or overly verbose if trying for accuracy. At some point I have to build upon the knowledge that I presume you have and you have to make the effort to see what knowledge you need to call upon to make use of that knowledge. Feynman can't explain "magnetic force in terms of something else", therefore he doesn't understand quantum mechanics or magnetism, which is obviously absurd if we take the point of the article as true. The title seems more like an "aspirational" than actual statement of fact. Most things that would interest people can be explained in simple terms that satisfy most people, and explaining that not everything can be explained in simple terms is part of that.
As everything, I think it depends. When the topic under discussion is complex and requires extensive background knowledge, it’s still possible to explain it in simple terms but the risk is to oversimplify it and loose important details.
The alternative would be to analyse every sub-topic until the required knowledge is reached, but that’s no longer explain something in simple terms, it’s just delaying the proper explanation to when the audience is prepared to tackle it.
And yes if some topic needs tensor or whatever abstract algebra structure to get it, there is no way to escape learning it first, though the way to teach it might be from tailored gentle companionship to a harsh read the dry book on the matter disconnected from any contextual presentation.
First, you can know topic intrinsically but just be bad at communication. The knowledge of the topic and communication skill to present it are two completely unrelated skills. The people that originally peddled it just couldn't imagine not being great at communication.
Second no, you can't explain complex term to someone that misses every basic piece of knowledge that is required to understand even the basics. That doesn't mean you don't understand it, that just means the topic is very complex.
You can simplify it (to the point of uselessness usually) so the other person have inlking what are implications but not, but they won't exactly know it.
>> First, you can know topic intrinsically but just be bad at communication. The knowledge of the topic and communication skill to present it are two completely unrelated skills.
Its not a myth. They are separate skills that when combined demonstrate your mastery of a topic. If you can not do both you do not understand the topic. Its the equivalent of someone who says they understand a topic but can't pass a test or demonstrate an example of the topic.
Communication is critical in everything you do on a daily basis and should be a skill you are always working on. Shying away from improving communication as a skill is a tell of lack of understanding.
> you can't explain complex term to someone that misses every basic piece of knowledge that is required to understand even the basics
Yes you can, you just need to explain every basic piece of knowledge to them first. Because if you truly understand it, that means you understand all those pieces of knowledge (to a certain degree, of course you'll need to look stuff up, but you'll know what you need to look up, etc.).
That doesn't mean you'll actually have to explain it to somebody with no background knowledge in practice (it would take a really long time), but you yourself was once a person with no background knowledge.
As Feynman says
> “I couldn’t do it. I couldn’t reduce it to the freshman level. That means we don’t really understand it.”
Note that he here targets the freshman level, not somebody with no schooling at all. But of course he could explain it to such a person, he'd just have to bring them to the freshman level first.
Feynman tried to prepare a freshman lecture on why spin-1/2 particles obey Fermi-Dirac statistics. He gave up and said, "That means we really don't understand it." At least he applied the rule to himself.
This is right in "spirit" but wrong in practical, objective fact.
If you can't explain something to your self in terms you find simple and certainly true would be the correct standard.
It simply is neither the case that an unspecified listener is necessarily going to be able to understand even if you've attained it, nor is it the case that phenomena in general have the required simplicity.
The correct form of this specifies an adequately prepared interlocutor.
The community of these peers is how public knowledge advances, not what can be simply understood by the ignorant masses.
It is the opposite of satire. Much of what i say and do would be considered over the top from a normie perspective. I have what could be considered a radical commitment to reason, which since early life I have defined as "the careful use of concepts".
In french, we have this sentence that sums that idea pretty well :
"Ce que l'on conçoit bien s'énonce clairement, et les mots pour le dire arrivent aisément"
Nicolas Boileau (author)
i think a big part of my non-programming IT work is pedagogy: many people build systems (even before AI) without being able to explain why/how they work
Some things, many things, require a large amount of built up knowledge and understanding to be even remotely capable of comprehending the idea in a meaningful way. There is an element of anti-intellectualism that drives people who think the world can be understood using an executive summary.
Even a simple explanation of quantum physics barely conveys a true understanding of the concepts underpinning the theory. Dunning-Kruger kicks in pretty hard as a result.
This topic always brings up a predictable discussion:
But what about things that are actually so complicated they can’t possibly be explained simply? What if the simplification removes substance and makes the explanation inaccurate?
Valid concerns, but the point is more that deep understanding of anything requires understanding intermediate concepts it’s composed of, and then the things those are composed of.
It's worth noting that simple terms needs to be relative to make sense. And I always though this quotation was a proxy for "explaining something minimally and naturally". Because I can explain prime ideals very well and I understand them very well but it wouldn't be considered simple for the average person.
Personally, I think this quotation, being a proxy for a different phenomenon, is inaccurate and asinine.
Love a blog post that just plops a bunch of quotes and then finishes with "kinda makes ya think, huh?" without any further exploration.
The comments I've perused that resonate with me the most center around: "for what purpose". Why does the person want to know. What will they do with this information. At what level of depth will they feel as if they now "understand" the concept.
A half-decent analogy is resolution. Sure, you can express the concept of a mountain with a 32x32 set of pixels, but what is the purpose of this "picture". Who's going to be looking at it and for what purpose. If a 9 year old asks you how the heart works, you can just say its a pump that drives blood through your circulatory system. But this is a woefully inadequate explanation for a medical student. At some point, reducing the resolution (reliance on already understood concepts/terminology) becomes an actual impediment to expressing the idea in a way that is useful to anyone at all (a 2x2 pixel arragnement).
There is something to be said about knowing your audience, communicating what is important to them, while also acknowledging that the nuance in any field is in the details and glossing over them or using non-academic terminology is necessarily lossy.
So if Feynman is taken as a given, then does anyone here know of anyone in software who they would nominate to be our honorary Feynman? Hoare perhaps was, particularly in the 70’s, but he has passed which limits his utility. Liskov perhaps? Beck even?
I can explain it in simple terms for you, but I can't understand it for you.
Almost every single time I've heard the "if you can't explain it simply" statement, what people were actually saying is that they wanted someone else to do the understanding for them. Not how it works, not how any of it works.
Modern big it corp is everything opposite of the title. The more cumbersome and poorly documented system you create - the more job security you and your peers (hired to untangle the mess) have.
Anyone have tips explaining (or to begin asking a question) a new concept, while in process of learning something new? I find it difficult, for example to recall new words and definitions making it all harder.
How about a good any good framework to write out a question to get answer to something you don't understand.
I think I would start by finding analogies to something familiar, then dig into detail comparison to find where that analogy breaks down. Refine your mental model on the way, like how textbook memorisation breaks down when encountering practice problems.
Communicating effectively although important - is a different skill than understanding that thing. Understanding is usually communicated by exhibiting that skill in real world. Having a great understanding of something and being able to translate that understanding into words are different things. For example, plenty of senior engineers often struggle with this.
Coincidentally this take usually comes from people who are great at communication but often have very little understanding (often seen in low-skill executives who rise due to brown-nosing / sheer people skills for the lack of a better word)
Being good at communication only means you are good at communication. Nothing more.
there are plenty of things in this world that are full of complexities and nuances.
just because someone explains a general concept to you doesn’t mean you magically understand the intricacies.
the implication that if a statistician can’t explain statistics to a 10 yo doesn’t mean they don’t know statistics.
don’t even get me started on the fact that many people have better things to do with their time than constantly explaining complex shit to people who refuse to do the homework on their own. the number of people recently who think they’re owed explanations from subject matter experts is unreal. and they lean on this very sentiment so often, i see it online constantly “oh, if you won’t tell me, you must not understand.”
plenty of very skilled & smart people are bad teachers of the very thing they excel at.
when concepts are handled at high speed on the daily they become part of your neural circuitry independently of speech or even words, doesn't mean you suck at it, it just means you never had to explain it.
I'm not sure you've understood the discussion then, nobody has claimed that "you suck at it" if you can't teach it, that's obviously not true. Knowing what to do do, and knowing _WHY_ that what is the right thing to do, are different things.
Performance doesn’t require understanding. It’s kinda how everyone who has thrown something knows the trajectory is parabolic even when they don’t know that word or the equation of motion involved.
But to transmit the knowledge, it first requires a lot of thinking. Which involves breaking things into components, labeling them and stating their relationship. That’s what understanding is.
This was very satisfying when taking math at the undergraduate level, because everything was broken down into proofs from first principles, or theorems from earlier courses, so if you just paid attention you could discover how everything's built from the ground up.
Unfortunately the deeper into graduate studies I got the more it seemed that math "lost its way" and less focus was put on taking the time to really understand things such that you yourself was convinced of it working. Not just the proofs themselves but also the definitions, which often seemed to appear "out of thin air". Whoever pioneered the field probably spent years getting the definitions just right, but as a student we got served the final product with very little explanation of the technical details.
In that sense it felt a lot like primary / secondary school math where the teacher would often reply "it just works that way", which to me is a little disappointing.
In undergrad and early grad, you're praised for your ability to be a persnickety auditor of every little rigorous step. It took me too long to realize that later in grad, you're meant to gloss over the details of things up until it's actually necessary (e.g. you identify the paper you're reading is relevant to your research goals, so you need to dissect it carefully).
Producing didactic material is hard, let alone for the bleeding edge of a niche field. Most of the practical mental models and convincing intuitions you describe happen at conferences and the like, precisely because they're personal, imperfect, and don't really fit in the publishing world. I too wish that knowledge could be collected and disseminated more accessibly.
> you're meant to gloss over the details of things up until it's actually necessary
Right, that's of course true. My feeling was rather that many people will skip this step:
> you identify the paper you're reading is relevant to your research goals, so you need to dissect it carefully
Or at least have a different understanding than me of what "dissect carefully" entails.
> Most of the practical mental models and convincing intuitions you describe happen at conferences and the like, precisely because they're personal, imperfect, and don't really fit in the publishing world.
I'd argue that the point of publishing math is to explain the results to the world, not just make some cryptic note of "I proved this thing, trust me bro (or come talk to me or derive the proof yourself)". But, it seems that's a view held by very few people who are actually working with math, so I suppose I might just not understand them properly. In any case, I'd say that including even an imperfect intuition of what the author is going for, is better than publishing as succinct a paper as humanly possible.
Marvin Minsky is widely quoted as saying, "You don't understand anything until you learn it more than one way" (also phrased in The Emotion Machine as "If you understand something in only one way, then you don't really understand it at all")
There's a popular excuse for not being able to explain a thing simply.
To quote authority is to speak truth. It doesn't matter if you understand it or not. So for that reason you are excused from having to explain the thing.
So ya, the power of authority runs strong in our knowledge. That's important to keep in mind.
Also, to quote authority is to to launder your opinion through an authoritative source. Which is great for arguing.
I was thinking about this as I read a 30 page specification that is part ai slop, part pretentious prattling that states things in the most impenetrable and vague way possible.
This is a simple versus easy problem. In the fewest words:
* Simple - numerically fewer
* Easy - least immediate effort
Don't over think that. Simple is not easy. There are many people who cannot express the effort to arrive at simple. I have a kiddo with ADHD/ASD and frequently he cannot arrive at simple. Sometimes the path to easy is a pathological lie that results in greatly extended effort. That inability to arrive at simple could be due to the perceived extended effort required or due to a disgust of executive functioning. It matters almost nothing what the motive behind that inability is as the output is the same.
One of the most important things I have learned from a career in software is that narcissists almost universally cannot measure abstract things with numbers. The required effort is too expensive and too differential to their interests. If you want to know if somebody is a sociopath give them a task with two outputs: the first output requires very little effort and looks amazing, but the second output requires a bit of extended effort and does not look impressive aside from completely dismissing the other output. I have seen this come up dozens of times for numerous people.
What's most interesting about the above paragraph is that narcissists cannot introspect, so they cannot see the obviousness of the above test even when repeated frequently. Everybody else sees this clearly even when they don't realize the absurdity of what they are looking at.
It is very common to hear people express things in jargon these days. Words such as "stakeholder", "resilience", semi-abusive generational labels and we also see the rebranding of words such as "actor" & "narrative" being used to blur the line between truth and fiction.
Trying to get someone to explain a concept in other terms can help them get out of cultic thinking and there is a lot of it now. But there is a tendency nowadays in medicine, science and soft sciences to alter terminology on a regular basis. I have a long term condition which to my knowledge has been relabelled at least five times since my diagnosis. I still have the same thing but not necessarily the in-group terminology.
I'm reading this thread purely to find all the people butthurt and trying to rationalize the opposite because they are realizing that their over wrought and complicated explanations for everything are not very good.
Most people in Big Tech and Silicon Valley describe LLM's and AI as a black box. Obviously, it's not and anyone serious about AI can explain what's going on layer by layer and neuron by neuron. The grand incompetence is astounding.
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.
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.
It's not so much an explanation of magnetism as a meta-discursive about explanations, and why a "simple" explanation is often not really possible. (In this case because our notion of what is weird and requiring of an explanation ("things pushing things at a distance") and what is normal and not requiring one ("the glass doesn't fall through the table") aren't scientifically grounded).
I think it's precisely the situation seanhunter is describing in their example
An explanation can be simple yet difficult to understand.
At some point, you have a body of knowledge, your 'understanding' that satisfies your curiosity (or you get exhausted and move on).
If you can't think of an example of the first case, most machine learning models suffice. Take a simple feed forward ReLU model. It's trivial to understand ReLU. It's nearly trivial to understand the individual neuron. Yet I, as someone who wrote their PhD thesis on neural architectures, would call bullshit on anyone claiming they "really" understand what's going on in a deep network.
And in physics, everything is reduced down to 'simple' forces of nature. A bunch of interactions and relationships that add up, and if you can keep up and perceive it all, you can sometimes stay ahead of all those interactions and imagine how it works through intelligence.
Eventually, you reach a state where you understand enough about the environment to translate ideas from one mind to another through language and your understanding of the world.
And so some will have deeper understandings, and in different areas, and all manner of conflict and resolution arises as people with different understandings try and understand one another.
There's no end in either direction you look, but zooming in always reveal some simple interactions at work.
If you're in charge of budget, you probably put budget before some other minor concern. If you're in charge of delivering a software feature, bug, patch, etc, you probably put something else first. It all depends on when something is due, or if something could jeopardize long-term prospects.
Everyone is on the hook for something. First principles thinking might be: think of your customer, and what they expect. Will whatever it is I'm doing affect them over the long-term? What about short-term?
If there's no clear answer, there's a lot of latitude to do whatever you think is best.
I actually think this is why a lot of software is going to shit now (even before AI slop). There's supposed to be contention between marketers and engineers (and even contention between types of engineers). If the engineer has too much say you build a great product but make no money and the business flops. If the marketers have too much say you build absolute shit and make money but you also forefeet a lot of potential revenue (opportunity cost). I think currently we've given the marketers too much say. Every time I talk to engineers they ask me where the "value" of something is and there's a constant followup with "no, I understand this helps the user, but how does it make money?" That's not the primary job of the engineer. This also creates problems because if a marketer can't understand the "value" of something then it just doesn't get built. So it shifts the objectives while people don't recognize that there is this baked in bias.
To tie back, I think a lot of arguments come to an impasse because people are working with different priors but assuming the other party has the same priors. It isn't uncommon to see people on HN (or Reddit) arguing what are essentially duals of problems. We just think that because we are using the same language that we're actually communicating. Like you said, there's no clear answer. Most of the problems in the world have no global optima. So how do you solve them? You have to define your constraints. But I rarely see that actually happen, though when it does conversations are really efficient.
"Simple" therefore means "reduced in information content".
The topic being explained has a certain minimal information content, and if you reduce beyond that, you are telling a fiction which bears analogies to the topic.
A simpler description is not necessarily short; rather, it is a description of something simpler.
When descriptions (of a given complexity, being held constant) are short, that can make them harder to follow, because encodings have to be clever in order to achieve compression, and that has a complexity of its own.
The way I understand the problem with explaining things in simple terms is this: We usually introduce quantum mechanics students to a toy model -the infinite square well- to build up intuition. However, depending on the teacher and the students, it may well take years for those students to recognize and understand that the boundary conditions we apply to literally every other QM calculation are violated by the infinite square well, and while we ultimately recover the expected conclusion via successive approximations, it takes a much deeper understanding of the material to understand why the "simple" explanation is actually wrong. That is, while it turns out that the solution to the infinite-square well is, at the limit, identical to a very deep square well, showing that is actually quite a bit harder.
The simple explanation causes incorrect intution about the situation.
This is also where the ironic part of simple explanations arises. Whether the explanation serves any purpose depends on the alignment of the speaker and listener background knowledge. An explanation between two experts versed in the topic may seem coherent, concise, and meaningful while it fails to teach the concept to someone new.
Sadly, it also works between cranks, who can agree on misleading or incorrect explanations. Or, sometimes novice listeners can believe they've learned, but they learn a different crank concept than what the expert believes was being states. A good teacher needs to be aware of these potential problems, attempt to ascertain the background knowledge of the listener, and adjust the explanation for that background rather than their own teaching knowledge. And followup testing attempts to ascertain whether the new concept got delivered or not.
Now that we have novices asking LLMs for explanations, I find this all quite troubling in a practical sense.
I am a fan of old Science/Mathematics/CS books precisely for the reason that they are generally concise and succinct. There are no rambling asides/anecdotes, silly analogies, unnecessary pretty colourful pictures etc.
The best examples are the books from old Soviet-era "MIR Titles" and Dover Publications.
For example, this video explaining fire, uploaded in January with a clickbait title, is AI: https://www.youtube.com/watch?v=vdop32yJqWg
Whereas this video explaining fire, uploaded 14 years ago, is real: https://www.youtube.com/watch?v=edQ08Eze0jM
14 years at least rules out certain techniques of video generation. With a little digging, we can find the original source is a 1983 BBC series called Fun to Imagine: https://www.bbc.co.uk/webarchive/https%3A%2F%2Fwww.bbc.co.uk...
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.
I think rigor should be part of it from the beginning, but it's often best to start with the least general definition and then just explain each generalization step-by-step, and make it feel motivated and sensible.
This an important part of good explanations. We can add providing plenty of examples and applications of the principles being explained.
However, when it comes to people, it all boils down to motivation. If the person writing is only trying to write the next year's edition of an every-year-updated textbook, the motivation is far from making things clear - then even step by step explanations and a lot of listed applications can be written in a way that only mystify the subject. Conflicts of interest is where the real problem is.
I'm hoping on AI, but I see some of it is following the erroneous path too, only open source AI can remedy this.
So simple!
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
Simple to who? Simple given what prior knowledge? Is a simple explanation one that can be understood with an elevator pitch? Over drinks? Over several days? Longer? And to what degree of accuracy? I can give you explanations for things and it'll be simple and yet different experts who do understand will argue over if it is a good enough explanation or not.
So I don't think this Einstein misattribution is a meaningful bar. It isn't even about attention. Some concepts simply need a lot of prior knowledge to meaningfully understand. Believing a 5 year old could understand nearly everything were it explained well enough would suggest that expertise is an illusion. Yet expertise exists because complexity increases exponentially as understanding converges (all those little nuances end up mattering).The example is terrible because they aren't explaining it, they are defining it. It's like asking to explain electricity and getting "it is the set of physical phenomena associated with the presence and motion of matter possessing an electric charge." That's not explaining it and no amount of effort on the part of the listener helps.
I said in this case each of those concepts that goes into the definition can be explained in simple terms but actually understanding what you get when you put them all together takes thought.
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...
Same thing with Kubernetes. OK, so you've got a bunch of servers. But that has problems, so let's to server virtualization. But that has problems, so let's do the cloud. But that has problems, so let's do microservices. But that has problems, so...
And in any case, nobody's going to listen to you explain microservices for 5 minutes and then be able to go actually manage a load of microservices; reality has a surprising amount of detail.
You’re the person that designs and deploys and maintains reusable machines that are used across multiple chemical plants, and if something that seems very small goes wrong the whole factory grinds to a halt.
My family doesn't need an explanation what kube-apiserver is.
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.
It's not just math that does this, but it seems to be extreme in math.
There is a purpose to the language and to that craziness. You aren't the audience and that's not a bad thing. Your lack of understanding is not a fault of yours. I wouldn't consider you stupid if you didn't know Cantonese. But I also wouldn't expect a Cantonese speaker to speak English to you. It is just a different language and people are using the language that is most effective to communicate with their peers. You don't have to be their peer. You're more than welcome to become one and I'm sure plenty of people would be happy to help you, but it will take time and effort to get there, just as it would were you to learn Cantonese.
We don't really do that to make things short, we do that to make things more understandable. People underestimate how important good notation is to properly understanding things, and mathematicians spend an inordinate amount of time just refining notation until it makes things easier to follow.
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.
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.
Not sure how to explain Uranium. Plumbum, but more gravitas?
But there is only so much one can do explaining when person on the other side is not putting work to understand stuff.
1. https://bjorklab.psych.ucla.edu/wp-content/uploads/sites/13/...
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.
And if you can explain it with no laws at all, then you really understand how it works...
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.
This is why we give recommended reading and pointers to those who really want to understand the topic.
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.
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.
A Teacher can only do so much; even the best ones. It is the Student who has to put in Self-Effort to study/understand/analyze/think/modify and finally apply/practice.
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.
Feynman said "if you can't explain it on a freshmen level". Leaving out that qualifier distorts the statement.
The other quote about the magnets is also overly reductive. Saying "I don't understand it in terms you're more familiar with" is not an admission that scientists as a group don't understand it at all.
You could go into what it means to understand something, but unfortunately the article isn't doing that.
Unless the article means to say that Feynman didn't understand the magnetic force, they have to admit that the magnetic force was perfectly understood, but impossible to explain in simple terms.
Didn't Feynman mean "layman terms" when he muses how he doesn't quite know how to begin to explain magnetism to his interviewer (but goes about doing so in 'simple' terms, anyway)?
These understandings and their accidental complexity also often inform composition of many distinct concepts into a solution to a complex problem. The brain must bear the burden of most of them simultaneously, even if you outsource the finer points to specialized teams during execution.
And then there's another barrier, of course: the audience. You may use simple terms, and tell a lengthy story, but some things are hard to understand. Relativity and Monty Hall come to mind. They can be explained in simple terms, but how many people get them? Probably just the ones that also understand a detailed explanation.
It doesn't matter what you know or understand, if you show up to a Spanish class and give a lecture in French.
The whole point of this discussion is this exact thing. It's about what "knowing" and "understanding" actually mean. Your second sentence is nearly the post title verbatim: You can know a subject perfectly without being able to explain it. That's literally the difference between knowing and understanding.
“Also you have to be good at educating groups” doesn’t add anything meaningful IMO
So that might be:
- pure general diffusion just to make general society expectation broadly aligned and don’t waste too much time on topics closed since literal millennia, but repeating the basics is not avoidable and even never enough (earth is not flat)
- the audience become aware of the topic be it in the most over simplified manner with the hope that if they cross a situation where it could help to know that some knowledge body exists on the matter and could be possibly leverage on (GPS is possible only because general relativity is taken into account)
- the audience are aiming to become expert in a domain where this knowledge is known to be useful for practical purposes, though it needs actually just enough background to situate the useful tricks (studying some engineer level domain)
- the audience is expected to gain epistemological meta-critical knowledge on the topic, such that they don’t only become fraction of last decile most knowledgeable on the matter itself but also how it emerged through history and how this influenced the shape of the theory and are expected to be able to teach everything on the matter at that level as an outcome (a group of people all having 7 postdocs each all in distinct domains, I guess)
(not a closed category)
Practical things like computer vulnerabilities are pretty easy to explain. I think anyone I know could understand what a buffer overflow is and why it's bad. The computer is a dumb machine and clobbers whatever you tell it to.
Relativity and monty hall are much better examples, I think. Relativity is well-studied enough that the explanations available for teenagers are pretty good, and if you study them you can get a pretty comprehensive understanding. But you do have to study them. Both are vulnerable to a certain kind of passive understanding, where correct arguments and incorrect arguments can both sound equally convincing.
Not sure I agree with this. Maybe most people have a vague idea of an algorithm as "something a computer does". Most people I don't think would grasp that you can have fundamentally different algorithms to solve the same problem.
Phrase a search algorithm as finding out if a card exists in a deck of cards with the rule that you want to look at as few cards as possible is more likely to be useful than saying you have an array of data on a computer. (To be able to do this faster than "look at them all" you should probably also say the deck is sorted)
Most people do grasp arithmetic though, and I think you could easily describe a parallel in math to explain how there are different ways to get the same result
10+5=15
20-5=15 as well but subtraction takes longer for the computer to calculate
1+4+7+3=15 too with only addition but it has multiple steps so it takes longer for the computer to calculate
I think most people could draw a very rudimentary understanding of how algorithms take different amounts of time from that explanation
Then you can talk about how this optimal program behaves. If you double the size of the input (people can understand this in terms of file size), does the time double, or quadruple, or...? I wouldn't mind trying to explain NP to a lay audience. I think you could get it across pretty well.
You can probably do Monty Hall by enumerating all of the possibilities. There are only nine possible combinations of where the car is and which door you choose. The difficulty, I think, comes from overanalyzing the problem, and a simpler explanation actually makes the job easier.
Relativity is a goo example though. I don't understand relativity beyond the most superficial level. As far as I can tell, the teenager-level explanations of relativity are not right. They convey some aspects of relativity on a conceptual level, and even some basic things on a mathematical level, but they're omitting important aspects of it. You might read A Brief History of Time (or whatever your favorite explainer is) and come away with an understanding of relativity, but your understanding will be some combination of wrong and extremely incomplete.
I think that's the crux. If you don't get down to the level of your audience, it's sure to go over their heads (mixing metaphors here, but they seem apt). So, the article may have a point, but needs to change to "simple for your audience", indeed. But then the audience really needs to apply their intellect, too. At that point, you might just as well be educating your audience to understand the basics and a more complex vocabulary.
There's a very common answer to this question: NP is the space of questions for which, when someone claims to have the answer, it's easy for you to tell whether they're right.
"Where are my keys?" - NP.
"Should I marry my girlfriend?" - not NP.
(Where "easy" is defined as polynomial time.)
- The property of a problem being "easy to check, but not easy to solve" is an extremely useful one[0]. It's also not inherent to NP problems. Most problems that have this property are not NP.
- The explanation omits entirely a different aspect, that's closer to a characteristic of NP problems: that they're all equivalent to each other mathematically, so if you find an efficient solution for one, you found it for all of them.
--
[0] - Especially so in the age of LLMs, as it's almost a definition of "what LLMs can beat humans at today"/what we can reliably use them for.
Very roughly, P = "easy to solve", and NP = "easy to check whether a proposed solution is correct". All problems in P are also in NP. The P =? NP question is whether the reverse is also true. A problem is "NP-hard" if it's at least as hard (in some very particular sense) as every problem in NP, and it's "NP-complete" if it's NP-hard and also itself in NP. It's these NP-complete problems which are in some sense all equivalent to each other.
There are still a lot of technical details omitted here. To scratch the surface:
"Problem" aka "Language" = "yes-no questions about strings", so for example "is this string the base-10 representation of a square integer?" (in P, and therefore also in NP) or "does this string represent a square grid of numbers that's a Sudoku (generalized to allow larger grids than 9x9) with at least one solution?" (in NP, and in fact NP-complete). "Easy" = "there exists a deterministic Turing machine which correctly answers the question on every input, and always runs in a number of steps which is less than some particular polynomial in the length of the input string". (In the real world, though, "polynomial-time" is not the same thing as "easy".) A language L being NP-hard means that for any NP language M, there's a polynomial-time deterministic Turing machine which maps M-inputs to L-inputs, where yes-instances map to yes-instances and no to no. Swapping yes and no is not allowed. For NP problems you only have to be able to check solutions in poly-time if the solution indicates that the answer is "yes". The corresponding family where you can check "no" quickly is called co-NP, and it is believed that NP != co-NP. Etc etc etc.
And yet you haven't pointed it out. I'd recommend reading this blog post that mentions the limits and consequences of simplifications: https://nedbatchelder.com/blog/201711/toxic_experts
The connection to solution space is also iffy and usually not how people introduce or primarily think of NP.
All your claimed definitons imply that NP and P are disjoint which clearly isn’t the case. I would be more careful
If you truly understand something, I don't think it would pose a problem to explain it to a three year old using only vocabulary that the three year old knows.
Realizing you can't do that is realizing you do not truly understand something.
If explaining was all it takes to acquire knowledge, everyone leaving school would have a deep understanding about every subject.
I have yet to meet a single problem that when broken down to atomic parts wasn't trivial to grok. Every single piece of software. I am not saying 3 year old should understand details of general relativity, thats not the point.
> I have yet to meet a single problem that when broken down to atomic parts wasn't trivial to grok.
For one thing, we don't know how to break every problem down to "atomic parts". More seriously, the important things to grok in life are the things that are not atomic parts! If you look at quantum mechanics as a system of fancy mathematics with arbitrary rules, it is possible to become an unthinking machine that calculates outcomes. But that is not at all what it means to "grok" quantum mechanics! Likewise with relativity - it is very easy to have Lorenz transformations memorised but be totally unable to explain how e.g. the twin paradox works. Saying that's trivial to grok is utter BS.
NP = "Things that are easy to verify"
What you were thinking was probably the concepts of NP-hard or NP-complete.
Most of such problems are not NP.
4/5
2/5
1/5
Or in other words, “simple” does not imply ”short.”
However I’ve seen a lack of appreciation of this distinction play out in some exec meetings where “clarity” is prioritized above nuance. There is definitely great skill involved in crafting a message for an audience, and it’s critical to internalize that execs care about different things than you. But a minimum level of shared context is required before a discussion can fit into a 30 minute meeting. That’s why Feynman’s quote mentions “freshman level.”
I understand that execs deal with an avalanche of information and uncertainty, so clarity is a highly precious commodity. But I get the sense that “clarity” often means “just give me a simple answer”, which glosses over opportunities hidden in the nuance.
You may be able to take core ideas from something and distill them but when you have multiple interacting core ideas you may not necessarily be able to reduce them to simple terms. And almost always when you do there’s a big asterisk that the analogy has a lot of flaws.
Its just a way dumb people can counter with something that *sounds* profound and makes their ignorance look acceptable. Id also say it's similar to the modern american trend of "my ignorance is worth as much as your expertise and education".
It's more about breaking down stuff into simpler parts. For example, you want to explain a buffer overflow exploit in a web server. Then you'll ask your audience, do you understand addressing / memory allocation, and do you understand HTTP? If they say no to any of those, then you'll have to explain e.g. memory allocation first. And if they don't know how a CPU / RAM / caches operates, then you'll have to explain that first. And maybe you'll have to explain boolean algebra and how to build an adder from logic gates. And so on.
So I would claim that "reductionism is always possible". More complex things just take longer to distill into less complex things, but it can always be done. The exception would be things that "nobody really understands", like Feynman says about magnetism:
> I really can’t do a good job, any job, of explaining magnetic force in terms of something else you’re more familiar with, because I don’t understand it in terms of anything else you’re more familiar with.
I think reductionism absolutely is possible in a lot of cases but I tend to agree with Stephen Wolfram’s concept of “computational irreducibility” or concepts we essentially know from compression in information theory (like Shannon entropy, Kolmogorov complexity) that there are limits to just how much you can reduce an idea or concept, and the bound for the human mind is likely much higher than those lower limit concepts.
Magnetic force is pointed out because it’s a more unique experience people don’t have a lot of prior knowledge and experience baked in that you can leverage as an assumption to reduce the concept, I think this holds true with lots of things. That isn’t to say we shouldn’t try to explain things simpler, just that that big caveat asterisk becomes ever more important when we use reductionist explanations. It’s not unlike when people try to explain spacetime curvature with a ball on a rubber sheet and things rotating around it… sure, that kind of gets at the idea, but there’s a huge asterisk that it’s simply not what’s really going on, it hints at the concept of curvature on a 2D plane you need to somehow conceptually extrapolate to other dimensions.
If your working as a teacher or professor like Feynman, then understanding and explaining may be equatable. In such a profession you are very practiced at explaining things and explaining something you understand should be easy. However, the "in simple terms" part also makes a crucial difference for explaining. "Simple" for what audience? Simple mean very different things for a five year old, a college freshman and something completely different again for a tradesperson. To explain things in simple terms you don't just need to understand the concept your explaining, you also have to understand what your audience already knows and understands and you must understand those concepts yourself too. I think the real skill in explaining is recognising and utilising this overlap between your knowledge and your audience's.
Being able to break things down into simple explanations (maybe many of them though?) is a sign of rigorous thinking. Not being able to do so (which seems common in some fields) is a sign of the opposite.
The latter group were poet-thinkers. They would write their findings (spiritual, mystical, social [social psychology, sociology, political science]) in poetic forms so elegant that these were at once both simple and complex. To the layperson with little insight and knowledge, they would make elementary sense and benefit them. But the more you knew, the more sophisticated you were, the deeper the meanings you could unearth.
So the latter group (Sanaii, Attar, Rumi, Nezami, Sa'adi, Hafez, I could go on) were masters of words and skill in presenting extremely rigorous ideas in the simplest, sweetest, most meaning-packed verses possible, without even appearing to break a sweat doing so. Rumi wouldn't even write, he would be in states of mystic ecstasy and send forth verse after verse which were hurriedly copied by the apprentices (mursheds).
PS (I am just a lifelong student of 'Oriental' languages.)
Here journalist asks Feynman to explain why magnets attract and repel.
Instead of doing that Feynman spends 15 minutes explaining how the journalist doesn't have the foundation to understand the explanation.
At some point journalist will have to accept that things are the way they are instead of understanding why.
https://www.sciencenorway.no/culture-history-history-of-scie...
https://news.ycombinator.com/item?id=50536813
But the scientist tried anyway; the journalist's end product was, inevitably, gibberish.
- [1] https://earlyretirementextreme.com/experts-and-pseudo-expert... (2009)
The problem I experience is that it's often hard to tell which type someone is if you're not also an expert.
I'd argue that the ability to explain something in simple terms proves that you understand it, but it is not the only proof and understanding doesn't depend on it.
That said, it is a useful heuristic to adopt. The challenge of explaining something is itself an opportunity to find a deeper understanding.
Calorie Deficit
"Does it work on all people?"
Yes, without a doubt.
"But humans are not bomb calorimeters."
Doesn't matter; minor differences in metabolism/absorption <<< calorie deficit.
Many people know X matters, Y matters, and Z matters, but very few are able to quantify how much X matters in relation to Y or Z.
This is why many people miss the forest for the trees.
Here's the proof of a calorie deficit working: https://i.ibb.co/F41dPj99/e53d5859da28.png
Each row in the table is a week.
Remember, you’re explaining to a five-year-old. You can’t stop a five-year-old from digging deeper and deeper. They aren’t discouraged by hand-wavey explanations.
https://www.medicalnewstoday.com/articles/287046
It is not intended to be anything more than a mental model for evaluating how well people you don't know understand something you don't understand yourself.
> Calorie Deficit
Trying to change mass by reducing energy, that might be the very most simple explanation of why calorie counting is misguided.
The more correct one would be pointing out that humans aren't dumb matter-to-energy converters. For many people, the body will happily down-clock quite hard in response to a calorie deficit; for others, it'll create irresistible psychological urges to fight the limit.
I'd probably go towards scenarios: imagine the body is a block of flats, and the municipal government decides for some reason to cut the city heating allocation for the block by half during a harsh winter.
Things that will happen include some combination of desired outcomes (people improving insulation, replacing radiators with newer ones, closing windows more) and undesired outcomes (people losing jobs and staying home and not paying bills, people starting fires indoors, tapping infrastructure to direct more heating to themselves, sabotaging neighbors, outright threatening or murdering neighbors to take their fuels, going out to the streets and rioting or attacking neighboring buildings or city council, etc.).
There's probably a simpler explanation to give, but I currently don't know an example of "self-regulating system" that most normies would understand. "Homeostasis" would be a perfect term, because it's something kids are taught about in primary education - unfortunately, as far as I know, most adults have no first clue what it means.
https://i.ibb.co/HThyPcSX/f0b1704b2cf3.png
https://i.ibb.co/vCFYB87j/7ee73cd7ce4d.png
method of maintenance tracking: https://macrocodex.app/knowledge/rethink/adaptive-tdee/#macr...
There will be so many studies at population level of how lower BMI correlates with people overall healthier, but that doesn't guarantee that slightly obese people would get healthier through weight loss.
Yes, none of it simple.
Also, (simplified) mass is a form of energy, so I am not following how that assessment would explain the fault with the approach.
Trying to actually and reliably measure what happens on food intake at an individual level is near impossible anyway, so keeping the explanation simple would be a step in some direction IMHO.
Ppl diminish things when they have a narrow conceptual scope of them, so ppl can diminish understanding to conceptual understanding if they live in a highly dissociative way, meaning they live inside their head more than most. So it's safer to say we 'have an understanding of smg' implying less totality, because there are usually angles and scopes to the thing that are still beyond us.
- Richard P. Feynman
We solve this problem by throwing millions of humans to study one human brain and then generalize.
Doesn't mean Claude isn't super useful though.
It's like throw a lot of concepts at once that were just created 5mins earlier but the agent doesn't care that the human supervisor isn't aware about them and how they function, so it doesn't know what simple explanation in relative terms should be provided next
I think this is also implied in the article in the ending paragraphs
[1] https://github.com/TheJavaGuy/tjg-claude-marketplace/tree/ma...
In this case, that semantic fulcrum is what it means to '''understand''' something. Because the question of whether Claude understands things hinges much more on the criteria for understanding, than it does on our belief on the capabilities that Claude has.
I’m not convinced that this is as big a problem as people try to make me believe, and I’m most certainly not convinced that the proposed “solutions” aren’t much worse than the problem.
All of that adds up to an encoding of a certain amount of information; if less information is used to explain it, then what is being described may be simpler, but doesn't match the real topic.
Sometimes what requires less information is a useful abstraction: something being explained contains details which are not relevant to a certain class to which it belongs. If you can't explain it in simpler terms, that could indicate that you only understand the instance very well, not the class.
He got so angry when he realized how simple it was. Who knows how stupid he'd felt because no-one had explained it that way before?
It's a subtle relationship of meanings between conveyor and recipient. There are many minds out there that need a fourth or fifth different explanation.
Complex explanations are either reducible, or they're not. Advanced mathematics requires years of compressed knowledge to explain something within itself.
Said differently, the same way you can't summarize any of the Nassim Taleb books (he takes pride in that). OR how watching a movie trailer and then the movie itself later, the experience gap will be very wide.
There are also complex topics that even lack a complex 'language for explanation'--for instance, quantum physics. The math works but not even the persons responsible for discovering it know why.
You don't need understanding to use something. For example, I have a grasp on both sarcasm and irony. I recognize it when used, but maybe not always. I can use both myself. But I have trouble explaining the concept of irony, since I do not truly understand it. Sarcasm on the other hand is easy to explain. It's mocking someone with nice words.
- you can analyze it in simple blocks (order and entropy)
- these contain the deep fundamental intuition (it is a mathematical result of the law of large numbers and based on biblical distribution)
- you can apply it in any occasion (like ordered lego pieces get mixed up when shaken)
https://github.com/janestreet/agent_skills
- Sergei Korolev
Any fool can come up with a random quote, the genius of a quote is in its veracity.
- iLoveOncall
"Everyone who understands X can explain it in simple terms" =/= "Anything explained in simple terms is done so by someone who understands it"
First, because "understanding" is not the one size fit all word people think it is.
E.G: you understand riding a bike, but none of your explanations, no matter how detailed (and they are going to suck), are going to lead someone to bike.
Second, because communicating requires a channel, usually a common vocabulary and a shared set of experiences, to be able to exchange on the topic.
E.G: there are things that are such internal or personalized experience there is not much to transmit to the other party like some things that happen during meditation.
And both points at the same time: what the experience of seen is to a blind. Communication is useless. Knowing more about it (the frequency of light for example) is not going to help.
Third, they are just things that "you know". "You understand". "They are perfectly clear to you". You didn't gain this understanding; it emerged, or it seems like it was already there. You can use the fruit of this understanding in a perfectly fluent way, and there is no doubt in your mind, plus your experience has always confirmed it.
And yet, you can share that.
So yes, while the initial idea is true for many things, I'll add this 3 nuances.
> And both points at the same time: what the experience of seen is to a blind. Communication is useless. Knowing more about it (the frequency of light for example) is not going to help.
I think you're arguing against a point nobody is making, that the ability to explain something must also somehow faithfully transmit the ability for the other party to perfectly comprehend and replicate it for themselves. Indeed, that is probably never the case, for any idea or concept.
My reading of the argument is that it only really concerns your own comprehension of the concept, and the subsequent ability to distill it down to its essential bits, and not if the other party is in a position to comprehend it fully. For example, a good pastry chef could break down the concepts behind baking choux, in a way that another baker who's unfamiliar with it to understand the concept, maybe even replicate a decent version of it. It obviously isn't going to work if the other person has no concept of baking, or what an oven is. Your examples require all those background concepts and contexts to also be somehow transmitted in the explanation.
some thinking and understanding is conceptual, spatial, bound to mind-muscle, smells, etc.
a good chef understands the ingredients' cooking dynamics perfectly and may still have trouble putting this into words
You need to understand the subject to explain, and the audience you're explaining it to.
And yes if some topic needs tensor or whatever abstract algebra structure to get it, there is no way to escape learning it first, though the way to teach it might be from tailored gentle companionship to a harsh read the dry book on the matter disconnected from any contextual presentation.
First, you can know topic intrinsically but just be bad at communication. The knowledge of the topic and communication skill to present it are two completely unrelated skills. The people that originally peddled it just couldn't imagine not being great at communication.
Second no, you can't explain complex term to someone that misses every basic piece of knowledge that is required to understand even the basics. That doesn't mean you don't understand it, that just means the topic is very complex.
You can simplify it (to the point of uselessness usually) so the other person have inlking what are implications but not, but they won't exactly know it.
Its not a myth. They are separate skills that when combined demonstrate your mastery of a topic. If you can not do both you do not understand the topic. Its the equivalent of someone who says they understand a topic but can't pass a test or demonstrate an example of the topic.
Communication is critical in everything you do on a daily basis and should be a skill you are always working on. Shying away from improving communication as a skill is a tell of lack of understanding.
Yes you can, you just need to explain every basic piece of knowledge to them first. Because if you truly understand it, that means you understand all those pieces of knowledge (to a certain degree, of course you'll need to look stuff up, but you'll know what you need to look up, etc.).
That doesn't mean you'll actually have to explain it to somebody with no background knowledge in practice (it would take a really long time), but you yourself was once a person with no background knowledge.
As Feynman says
> “I couldn’t do it. I couldn’t reduce it to the freshman level. That means we don’t really understand it.”
Note that he here targets the freshman level, not somebody with no schooling at all. But of course he could explain it to such a person, he'd just have to bring them to the freshman level first.
If you can't explain something to your self in terms you find simple and certainly true would be the correct standard.
It simply is neither the case that an unspecified listener is necessarily going to be able to understand even if you've attained it, nor is it the case that phenomena in general have the required simplicity.
The correct form of this specifies an adequately prepared interlocutor.
The community of these peers is how public knowledge advances, not what can be simply understood by the ignorant masses.
Even a simple explanation of quantum physics barely conveys a true understanding of the concepts underpinning the theory. Dunning-Kruger kicks in pretty hard as a result.
https://xkcd.com/1133/ https://en.wikipedia.org/wiki/Thing_Explainer
But what about things that are actually so complicated they can’t possibly be explained simply? What if the simplification removes substance and makes the explanation inaccurate?
Valid concerns, but the point is more that deep understanding of anything requires understanding intermediate concepts it’s composed of, and then the things those are composed of.
Personally, I think this quotation, being a proxy for a different phenomenon, is inaccurate and asinine.
The comments I've perused that resonate with me the most center around: "for what purpose". Why does the person want to know. What will they do with this information. At what level of depth will they feel as if they now "understand" the concept.
A half-decent analogy is resolution. Sure, you can express the concept of a mountain with a 32x32 set of pixels, but what is the purpose of this "picture". Who's going to be looking at it and for what purpose. If a 9 year old asks you how the heart works, you can just say its a pump that drives blood through your circulatory system. But this is a woefully inadequate explanation for a medical student. At some point, reducing the resolution (reliance on already understood concepts/terminology) becomes an actual impediment to expressing the idea in a way that is useful to anyone at all (a 2x2 pixel arragnement).
There is something to be said about knowing your audience, communicating what is important to them, while also acknowledging that the nuance in any field is in the details and glossing over them or using non-academic terminology is necessarily lossy.
<clicks on link>
Oops.
So if Feynman is taken as a given, then does anyone here know of anyone in software who they would nominate to be our honorary Feynman? Hoare perhaps was, particularly in the 70’s, but he has passed which limits his utility. Liskov perhaps? Beck even?
Almost every single time I've heard the "if you can't explain it simply" statement, what people were actually saying is that they wanted someone else to do the understanding for them. Not how it works, not how any of it works.
Sure. It’s a handy aphorism, but it’s not a universal truth.
And its what the Quantum Mechanics adage of "Shut up and calculate" is meant to confer to students as well.
How about a good any good framework to write out a question to get answer to something you don't understand.
Coincidentally this take usually comes from people who are great at communication but often have very little understanding (often seen in low-skill executives who rise due to brown-nosing / sheer people skills for the lack of a better word)
Being good at communication only means you are good at communication. Nothing more.
Couldn't have made a more lazier shallow take.
there are plenty of things in this world that are full of complexities and nuances.
just because someone explains a general concept to you doesn’t mean you magically understand the intricacies.
the implication that if a statistician can’t explain statistics to a 10 yo doesn’t mean they don’t know statistics.
don’t even get me started on the fact that many people have better things to do with their time than constantly explaining complex shit to people who refuse to do the homework on their own. the number of people recently who think they’re owed explanations from subject matter experts is unreal. and they lean on this very sentiment so often, i see it online constantly “oh, if you won’t tell me, you must not understand.”
5/5
plenty of very skilled & smart people are bad teachers of the very thing they excel at.
when concepts are handled at high speed on the daily they become part of your neural circuitry independently of speech or even words, doesn't mean you suck at it, it just means you never had to explain it.
But to transmit the knowledge, it first requires a lot of thinking. Which involves breaking things into components, labeling them and stating their relationship. That’s what understanding is.
Unfortunately the deeper into graduate studies I got the more it seemed that math "lost its way" and less focus was put on taking the time to really understand things such that you yourself was convinced of it working. Not just the proofs themselves but also the definitions, which often seemed to appear "out of thin air". Whoever pioneered the field probably spent years getting the definitions just right, but as a student we got served the final product with very little explanation of the technical details.
In that sense it felt a lot like primary / secondary school math where the teacher would often reply "it just works that way", which to me is a little disappointing.
Producing didactic material is hard, let alone for the bleeding edge of a niche field. Most of the practical mental models and convincing intuitions you describe happen at conferences and the like, precisely because they're personal, imperfect, and don't really fit in the publishing world. I too wish that knowledge could be collected and disseminated more accessibly.
Right, that's of course true. My feeling was rather that many people will skip this step:
> you identify the paper you're reading is relevant to your research goals, so you need to dissect it carefully
Or at least have a different understanding than me of what "dissect carefully" entails.
> Most of the practical mental models and convincing intuitions you describe happen at conferences and the like, precisely because they're personal, imperfect, and don't really fit in the publishing world.
I'd argue that the point of publishing math is to explain the results to the world, not just make some cryptic note of "I proved this thing, trust me bro (or come talk to me or derive the proof yourself)". But, it seems that's a view held by very few people who are actually working with math, so I suppose I might just not understand them properly. In any case, I'd say that including even an imperfect intuition of what the author is going for, is better than publishing as succinct a paper as humanly possible.
This is one of those catchy aphorisms that sounds deep until you think about it for like 10 seconds.
To quote authority is to speak truth. It doesn't matter if you understand it or not. So for that reason you are excused from having to explain the thing.
So ya, the power of authority runs strong in our knowledge. That's important to keep in mind.
Also, to quote authority is to to launder your opinion through an authoritative source. Which is great for arguing.
So yeah there's that bullshit going on.
Writing is hard.
Pretty big ego
2Know how it’s used.
3Understand it.
In that order.
You don’t need to understand everything. Delegation is the greatest invention of humanity.
* Simple - numerically fewer
* Easy - least immediate effort
Don't over think that. Simple is not easy. There are many people who cannot express the effort to arrive at simple. I have a kiddo with ADHD/ASD and frequently he cannot arrive at simple. Sometimes the path to easy is a pathological lie that results in greatly extended effort. That inability to arrive at simple could be due to the perceived extended effort required or due to a disgust of executive functioning. It matters almost nothing what the motive behind that inability is as the output is the same.
One of the most important things I have learned from a career in software is that narcissists almost universally cannot measure abstract things with numbers. The required effort is too expensive and too differential to their interests. If you want to know if somebody is a sociopath give them a task with two outputs: the first output requires very little effort and looks amazing, but the second output requires a bit of extended effort and does not look impressive aside from completely dismissing the other output. I have seen this come up dozens of times for numerous people.
What's most interesting about the above paragraph is that narcissists cannot introspect, so they cannot see the obviousness of the above test even when repeated frequently. Everybody else sees this clearly even when they don't realize the absurdity of what they are looking at.
Trying to get someone to explain a concept in other terms can help them get out of cultic thinking and there is a lot of it now. But there is a tendency nowadays in medicine, science and soft sciences to alter terminology on a regular basis. I have a long term condition which to my knowledge has been relabelled at least five times since my diagnosis. I still have the same thing but not necessarily the in-group terminology.
It did not disappoint.