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.
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.
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 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.
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.
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.
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(?)
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.
While I agree that the receiver needs to make an effort to understand, I don't think I agree with this explanation
Your definition; "a set is compact if and only if every open cover has a finite subcover", requires a lot of prior knowledge to actually make sense of. When you say "explain it in simple terms", you are expected to explain all the needed concepts too
So what is a cover? what is an open cover? what is a subcover? what is a set!? heck, even what is finite/infinite? and what are all the new concepts you have to introduce to explain each of those?
The idea of explaining something in simple terms doesn't necessarily mean using a short, strictly formal explanation. It means making someone who is willing to pay attention understand everything (and this can usually be a long explanation). This requires a lot more effort than people usually think. Explaining forces you to remember concepts you assume others understands because with your own experience that feels already natural
In summary:
- Don't confuse "compressing an idea" with "explaining it on simpler terms"
- Explain it in a way an attentive 5 years old kid could understand
I think 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.
“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
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."
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...
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.
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.
> 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.
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.
Doesn'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)?
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.
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.
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.
> 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
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.
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.
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/
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.
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.
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.
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 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.
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.
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!
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.
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.
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:
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.
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.
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.
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
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.
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)
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.
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.
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.
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.
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")
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.
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.
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.
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.
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.
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 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.
Fully agree. Some of the best textbooks I’ve had are verbose and try to explain the same concept using different words several times.
That's my excuse for being long, verbose, and rambley about everything :)
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.
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.
Because simple and short are not the same.
Simplicity means made out of essential concepts, but you still need to understand the concepts.
To me this boils down to being able to separate what is essential from what is not, and to do so you have to be knowledgeable.
> 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.
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.
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.
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(?)
You keep the software factory running.
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.
While I agree that the receiver needs to make an effort to understand, I don't think I agree with this explanation
Your definition; "a set is compact if and only if every open cover has a finite subcover", requires a lot of prior knowledge to actually make sense of. When you say "explain it in simple terms", you are expected to explain all the needed concepts too
So what is a cover? what is an open cover? what is a subcover? what is a set!? heck, even what is finite/infinite? and what are all the new concepts you have to introduce to explain each of those?
The idea of explaining something in simple terms doesn't necessarily mean using a short, strictly formal explanation. It means making someone who is willing to pay attention understand everything (and this can usually be a long explanation). This requires a lot more effort than people usually think. Explaining forces you to remember concepts you assume others understands because with your own experience that feels already natural
In summary: - Don't confuse "compressing an idea" with "explaining it on simpler terms" - Explain it in a way an attentive 5 years old kid could understand
I think 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.
“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
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."
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...
Exactly. Or, they blame the explainer because they lack the foundational knowledge to understand said concepts.
Agreed. Sometimes people confuse simple with familiar. Even if what is explained is simple, it might seem complex just because it's not familiar.
My favorite pet example is the Burrows-Wheeler transform and its application to compression
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.
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.
“A set is compact when its points live in a finite number of neighborhoods.”
> I think this idea is often misunderstood and used as an excuse by people who don’t want to make any effort to understand a complex concept and want to blame the results of their laziness on the explanation or the explainer.
It is even worse. They feel entitled to an understanding without putting in any self-effort at all! This has now become pervasive because we as a society have prioritized inanities like ego-soothing, everybody-is-a-unique-snowflake, get-a-sticker-for-everything-trivial, everything-should-be-fun etc. over actual striving and learning through effortful study/work. Everything is the fault of the teacher/book and there is no personal responsibility.
A Chinese Martial Arts saying which i often quote;
To show one the right direction and the right path, oral instructions from a Master are necessary, but mastery of the subject only comes from one's own incessant self-cultivation.
A good authoritative book can also be the stand-in for a Master in which case there is more discipline and effort required of the Student.
I think this is a test for the teacher and not the student.
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.
> ...simple terms
Doesn'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)?
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.
Simple for your audience to understand. Which means you posses understanding deep enough that you can explain it any any level of detail.
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.
I think the formulation staying at an audience of 1 gets the point across.
“Also you have to be good at educating groups” doesn’t add anything meaningful IMO
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)
(not a closed category)
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.
> But you do have to study them.
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.
> 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
All of these remarks are addressed in the article.
In which sentence, may I ask? Or did we read two different articles?
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.
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.
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
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.
That means you don't really understand it
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.
Erm... I think you've gone too far.
> 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.
The problem with your NP explanation is not the level, but that it is wrong, based on a common misunderstanding. The correct simple explanation is:
NP = "Things that are easy to verify"
What you were thinking was probably the concepts of NP-hard or NP-complete.
Many problems are easy to verify but hard to solve. It's a very important and interesting property, especially in the last two years.
Most of such problems are not NP.
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/
4/5
Spent a while looking at that. Not a clue
I'm sure my father will understand what Heartbleed is when I show him that cartoon. Yes, I'm being sarcastic.
Counterpoint by another famed physicist, Feynman: https://www.youtube.com/watch?v=Q1lL-hXO27Q
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.
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.
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.
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.
This is exactly what the article says. If you find it hard to explain in simple terms then you do not understand it enough.
Doesn’t mean it’s true
Yep.
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".
So Feynman didn't understand magnets enough?
Competence in one field often doesn't translate into competence in other fields.
It may be that sone things can’t be explained in simple terms, but perhaps they are just not understandable?
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.
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 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.
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.
"How does weight loss work?"
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.
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!
The interesting thing about weight loss is, that it happens mostly via breathing:
https://www.medicalnewstoday.com/articles/287046
That would be an oversimplification.
> How does weight loss work?"
> Calorie Deficit
Trying to change mass by reducing energy, that might be the very most simple explanation of why calorie counting is misguided.
It's neither simple nor correct explanation.
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.
You do not need to "speculate" on how TDEE (total calorie burn of the day) changes in response to a deficit; we've documented it here:
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...
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.
"If I could explain it to the average person, it wouldn't have been worth the Nobel Prize."
- Richard P. Feynman
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:
https://github.com/janestreet/agent_skills
Everyone working on how Claude communicates would benefit from reading this.
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.
Doesn't mean Claude isn't super useful though.
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
There are skills which try to force Claude Code to use Feynman technique like [1] and many others
[1] https://github.com/TheJavaGuy/tjg-claude-marketplace/tree/ma...
Well surely claude struggles here because it doesn't '''understand''' anything.
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.
Any fool can build something complicated, the genius of a construction is in its simplicity.
- Sergei Korolev
Most fools can't build anything.
Any fool can come up with a random quote, the genius of a quote is in its veracity.
- iLoveOncall
Did you recursively curse yourself. :)
Well no because my quote is true :)
you re-iterated it. here's an upvote for you (you'll understand why if you're a programmer).
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.
You have the correlation wrong.
"Everyone who understands X can explain it in simple terms" =/= "Anything explained in simple terms is done so by someone who understands it"
Nice - clearly explained in simple terms.
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.
> The internet is a series of tubes [...] and not a big truck.
If they have no idea what they're talking about, then they haven't explained anything to you.
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.
Also, "explaining X" doesn’t mean "explaining Y, where Y is a poorly understood version of X".
if they do this intentionally, it's called the Dr. Fox effect. if not, then the Dunning-Kruger effect.
still wrong
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
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.
I think the caveat is, simple to me might not be simple to you.
You need to understand the subject to explain, and the audience you're explaining it to.
https://m.youtube.com/watch?v=SxdOUGdseq4&t=346s&pp=2AHaApAC... comes to mind
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.
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
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.
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)
Maybe words come easily, but maybe they are not simple words, but are words that for instance rely on not well-known concept / abstraction / ...
This was the motivation behind xkcd's "Up Goer" and "Thing Explainer", wasn't it?
https://xkcd.com/1133/ https://en.wikipedia.org/wiki/Thing_Explainer
I hate that stupid myth.
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.
Exactly. The saying is "if you can't exain it simply," not "if you can't explain it concisely."
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.
Being able to explain things is a skill. Not having that skill does not mean you don't understand things.
This is one of those catchy aphorisms that sounds deep until you think about it for like 10 seconds.
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.
That would mean that no-one understands quantum mechanics.
Which is indeed an often made claim, including by Feynman.
And its what the Quantum Mechanics adage of "Shut up and calculate" is meant to confer to students as well.
Well if this applies to making softwares, then we will have a lot to explain, are we still shipping it or not?
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.
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")
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.
Couldn't have made a more lazier shallow take.
More lazier
ITT: people not realising they don't understand things.
5/5
I'm genuinely surprised at the amount of pushback this idea is getting here.
because it's wrong
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.
ITT: people confusing understanding something and being able to convey the fact you're understanding it to others
It would be nice to support bold claims with evidence, not quotes from famous people
I agree. This is the sort of problem that plagues sophomores in the English department... :)
Writing is hard.
yet to hear any explanation of quantum computing, that makes any sense....
> I couldn’t reduce it to the freshman level. That means we don’t really understand it.
Pretty big ego
can we pls shut up about feynman my dudes enough is enough
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.
1Know it exists.
2Know how it’s used.
3Understand it.
In that order.
You don’t need to understand everything. Delegation is the greatest invention of humanity.
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.
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.
80IQ idea.
Yeah I was also not impressed by the 'physics textbooks' of his.
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.
Explain to me how to become billionaire
Get lucky.
Be born with it, marry into it or try work your entire life for it and succeed 0.0001% of the time.
this is dumb
how come tech bros have this superiority complex it is so exhausting