upvote
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.

reply
My favorite Feynman video (which the OP references but completely misunderstands) is this one: https://m.youtube.com/watch?v=MO0r930Sn_8

It's not so much an explanation of magnetism as a meta-discursive about explanations, and why a "simple" explanation is often not really possible. (In this case because our notion of what is weird and requiring of an explanation ("things pushing things at a distance") and what is normal and not requiring one ("the glass doesn't fall through the table") aren't scientifically grounded).

I think it's precisely the situation seanhunter is describing in their example

reply
It’s a much better example indeed, but - and now I’ll have to reference Rich Hickey a bit - simple isn’t necessarily easy.

An explanation can be simple yet difficult to understand.

reply
I don't remember where I first heard this idea, but using 2 orthogonal axes of simple-complex and easy-hard provide a good framework for evaluating concepts. On this plane I would describe income taxes as easy, but complex. Juggling is simple, but hard.
reply
An explanation can be simple, and holding the entire chain of simple ideas in your head to 'understand' some bigger idea can be difficult.

At some point, you have a body of knowledge, your 'understanding' that satisfies your curiosity (or you get exhausted and move on).

reply
As an example of this, you can have complex code made of entirely simple and easy to understand functions. But the complexity appears in the combination. That complexity can be far higher than were you to have more complex functions in the program. Which this is a common mistake people make that lead to tech debt. A lot of people try to simplify code by making it "understandable" without setting a floor to who needs to understand it and with how much time. If you don't, that floor gets lower each year.

If you can't think of an example of the first case, most machine learning models suffice. Take a simple feed forward ReLU model. It's trivial to understand ReLU. It's nearly trivial to understand the individual neuron. Yet I, as someone who wrote their PhD thesis on neural architectures, would call bullshit on anyone claiming they "really" understand what's going on in a deep network.

reply
For sure. Binary is another example: it's just 1's and 0's, a bunch of on and off states that only make sense when you consider the entire sequence.

And in physics, everything is reduced down to 'simple' forces of nature. A bunch of interactions and relationships that add up, and if you can keep up and perceive it all, you can sometimes stay ahead of all those interactions and imagine how it works through intelligence.

Eventually, you reach a state where you understand enough about the environment to translate ideas from one mind to another through language and your understanding of the world.

And so some will have deeper understandings, and in different areas, and all manner of conflict and resolution arises as people with different understandings try and understand one another.

There's no end in either direction you look, but zooming in always reveal some simple interactions at work.

reply

  > There's no end in either direction you look, but zooming in always reveal some simple interactions at work.
This is why I actually hate the phrase "from first principles". I can't tell you what the first principles are, but I can sure tell you that when someone says that they almost certainly are not starting from first principles and almost surely are (often unknowingly) making major assumptions. First principles are something you need to find, not start with.
reply
You're right, and it's subjective because of priority. First principles should be tied to whatever thinking requires the most concern in the moment.

If you're in charge of budget, you probably put budget before some other minor concern. If you're in charge of delivering a software feature, bug, patch, etc, you probably put something else first. It all depends on when something is due, or if something could jeopardize long-term prospects.

Everyone is on the hook for something. First principles thinking might be: think of your customer, and what they expect. Will whatever it is I'm doing affect them over the long-term? What about short-term?

If there's no clear answer, there's a lot of latitude to do whatever you think is best.

reply
Honestly, I think you're pointing at something important that a lot of people miss. I make the claim that Apple was only successful because of both Steves. Jobs gets all the credit and tech people idolize Woz. Both are critical to the success though, just in different directions.

I actually think this is why a lot of software is going to shit now (even before AI slop). There's supposed to be contention between marketers and engineers (and even contention between types of engineers). If the engineer has too much say you build a great product but make no money and the business flops. If the marketers have too much say you build absolute shit and make money but you also forefeet a lot of potential revenue (opportunity cost). I think currently we've given the marketers too much say. Every time I talk to engineers they ask me where the "value" of something is and there's a constant followup with "no, I understand this helps the user, but how does it make money?" That's not the primary job of the engineer. This also creates problems because if a marketer can't understand the "value" of something then it just doesn't get built. So it shifts the objectives while people don't recognize that there is this baked in bias.

To tie back, I think a lot of arguments come to an impasse because people are working with different priors but assuming the other party has the same priors. It isn't uncommon to see people on HN (or Reddit) arguing what are essentially duals of problems. We just think that because we are using the same language that we're actually communicating. Like you said, there's no clear answer. Most of the problems in the world have no global optima. So how do you solve them? You have to define your constraints. But I rarely see that actually happen, though when it does conversations are really efficient.

reply
As far as simple not being easy, its worth noting that Feynman only really hits his stride in the second half of his answer. That's how hard it is, a genius theorist and genius communicator still took a few sentences to start making it simple when given a backwards question.
reply
deleted
reply
A thing being more or less complex refers to the amount of information needed to encode its description.

"Simple" therefore means "reduced in information content".

The topic being explained has a certain minimal information content, and if you reduce beyond that, you are telling a fiction which bears analogies to the topic.

A simpler description is not necessarily short; rather, it is a description of something simpler.

When descriptions (of a given complexity, being held constant) are short, that can make them harder to follow, because encodings have to be clever in order to achieve compression, and that has a complexity of its own.

reply
And there are entire categories of phenomenon that don't arise or are imperceptible in a simple context. Chaos is an emergent phenomenon that requires a surprisingly deep knowledge of a situation to predict where it will arise.

The way I understand the problem with explaining things in simple terms is this: We usually introduce quantum mechanics students to a toy model -the infinite square well- to build up intuition. However, depending on the teacher and the students, it may well take years for those students to recognize and understand that the boundary conditions we apply to literally every other QM calculation are violated by the infinite square well, and while we ultimately recover the expected conclusion via successive approximations, it takes a much deeper understanding of the material to understand why the "simple" explanation is actually wrong. That is, while it turns out that the solution to the infinite-square well is, at the limit, identical to a very deep square well, showing that is actually quite a bit harder.

The simple explanation causes incorrect intution about the situation.

reply
I'm not sure how you measure this in practice, when one way that explanations are simplified is to externalize a lot of information by reference to some specific terms of art (jargon, really). Where is the boundary for measuring the content, when we always have the implicit compression dictionaries of the speaker and listener to contend with?

This is also where the ironic part of simple explanations arises. Whether the explanation serves any purpose depends on the alignment of the speaker and listener background knowledge. An explanation between two experts versed in the topic may seem coherent, concise, and meaningful while it fails to teach the concept to someone new.

Sadly, it also works between cranks, who can agree on misleading or incorrect explanations. Or, sometimes novice listeners can believe they've learned, but they learn a different crank concept than what the expert believes was being states. A good teacher needs to be aware of these potential problems, attempt to ascertain the background knowledge of the listener, and adjust the explanation for that background rather than their own teaching knowledge. And followup testing attempts to ascertain whether the new concept got delivered or not.

Now that we have novices asking LLMs for explanations, I find this all quite troubling in a practical sense.

reply
Fully agree. Some of the best textbooks I’ve had are verbose and try to explain the same concept using different words several times.
reply
While verbose explanations have their place, i think it is being abused nowadays which actually obscures/obfuscates the essential points that need to be grasped.

I am a fan of old Science/Mathematics/CS books precisely for the reason that they are generally concise and succinct. There are no rambling asides/anecdotes, silly analogies, unnecessary pretty colourful pictures etc.

The best examples are the books from old Soviet-era "MIR Titles" and Dover Publications.

reply
But length correlates with the prior knowledge of an audience. I love math, it is a great language, but it is dense as fuck and if you're not already familiar with a topic then natural language words are going to help explain the concepts.

  > There are no rambling asides/anecdotes, silly analogies, unnecessary pretty colourful pictures etc.
Obviously some go overboard and I won't defend that, but this style has been around for centuries. They won out because it's effective. People are "multimodal" if you will
reply
I thought a lot of those Feynman videos on YouTube were AI fabrications. How do you know which ones are real?
reply
Provenance.

For example, this video explaining fire, uploaded in January with a clickbait title, is AI: https://www.youtube.com/watch?v=vdop32yJqWg

Whereas this video explaining fire, uploaded 14 years ago, is real: https://www.youtube.com/watch?v=edQ08Eze0jM

14 years at least rules out certain techniques of video generation. With a little digging, we can find the original source is a 1983 BBC series called Fun to Imagine: https://www.bbc.co.uk/webarchive/https%3A%2F%2Fwww.bbc.co.uk...

reply
Well, the one on fire specifically is from a BBC series called Fun to Imagine released in 1983, and it’s been on YouTube for 17 years. So, you know, probably not an AI fabrication
reply
I hope someone is archiving the pre-AI internet. It may be very valuable in the not-too-distant future.
reply
Archive.org's Wayback Machine, accepting only results pre-2022 (set your threshold whenever suits you).
reply
Too many broken links there. It's probably only 1% of the actual internet.
reply
I assumed that the publishing date was for sale if you paid Google enough.
reply
I don't think the people making AI-slop-videos have enough money to bribe google.
reply
That's my excuse for being long, verbose, and rambley about everything :)
reply
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.

reply
Exactly! I think this is a general problem in math, where we have this very "advanced" in some sense, definition of compactness. And mathematicians love such definitions, in the sense that it's quite easy to state and it covers a very general case. But it's simultaneously very unhelpful to actually understand why it's even interesting to talk about that concept, if all one knows is the most general definition.

I think rigor should be part of it from the beginning, but it's often best to start with the least general definition and then just explain each generalization step-by-step, and make it feel motivated and sensible.

reply
> I think rigor should be part of it from the beginning, but it's often best to start with the least general definition and then just explain each generalization step-by-step, and make it feel motivated and sensible.

This an important part of good explanations. We can add providing plenty of examples and applications of the principles being explained.

However, when it comes to people, it all boils down to motivation. If the person writing is only trying to write the next year's edition of an every-year-updated textbook, the motivation is far from making things clear - then even step by step explanations and a lot of listed applications can be written in a way that only mystify the subject. Conflicts of interest is where the real problem is.

I'm hoping on AI, but I see some of it is following the erroneous path too, only open source AI can remedy this.

reply
And as we all know, a monad is just a monoid in the category of endofunctors.

So simple!

reply
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

reply

  > Your definition; "a set is compact if and only if every open cover has a finite subcover", requires a lot of prior knowledge to actually make sense of.
That is seanhunter's entire point.

Simple to who? Simple given what prior knowledge? Is a simple explanation one that can be understood with an elevator pitch? Over drinks? Over several days? Longer? And to what degree of accuracy? I can give you explanations for things and it'll be simple and yet different experts who do understand will argue over if it is a good enough explanation or not.

  > Explain it in a way an attentive 5 years old kid could understand
So I don't think this Einstein misattribution is a meaningful bar. It isn't even about attention. Some concepts simply need a lot of prior knowledge to meaningfully understand. Believing a 5 year old could understand nearly everything were it explained well enough would suggest that expertise is an illusion. Yet expertise exists because complexity increases exponentially as understanding converges (all those little nuances end up mattering).
reply
I had no idea what any of that meant and your explanation did nothing at all but confuse me, and Claude explained it to me in a few minutes.

The example is terrible because they aren't explaining it, they are defining it. It's like asking to explain electricity and getting "it is the set of physical phenomena associated with the presence and motion of matter possessing an electric charge." That's not explaining it and no amount of effort on the part of the listener helps.

reply

  > and Claude explained it to me in a few minutes.
What did Claude say to you? Did it use more words? Do you have memory on? What did Claude tell you about this comment and what I'm insinuating? HN is a wide audience and I don't know you well enough. Is letting you infer a bad thing? I don't know how much I need to spoon feed you. Is spoon feeding you a bad thing? I'm actually curious what Claude will tell *you*
reply
deleted
reply
Exactly, it just shows Kottke's truism/platitude is wrong and absurd and thus pedagogy should be left to actual experts, there is some irony that today only people who understand advanced math are experientially qualified to point out just how mistaken the OP title is.
reply
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.

reply
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.
reply
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.
reply
> 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...

reply
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.

reply
This is why when people ask what I do I change the subject, unless I want them to start looking for someone else to talk to.
reply
When asked about the topic of my main career, I usually say, "I can explain it in 5 minutes if you want", aiming for a tone of "you probably don't want this, but who knows, maybe you do". If asking about one of my obsessions, after the secodn follow-on question, I'll say "I can talk about this literally for hours; so I'll try to answer in short sentences. I'll keep talking as long as you ask questions; whenever you've had enough, just stop asking and we can talk about something else." Because my social circle is full of geeks, many of whom get just as excited about my obsessions as I am.
reply
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.

reply
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(?)
reply
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.

reply
Sure, but then you are entirely avoiding the problem of not being able to simplify something complex even if you are an expert - which was my point exactly, i.e. sometimes it just is hard to explain.
reply
You keep the software factory running.
reply
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.

reply
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.

reply
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."
reply
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.

reply
I think you misunderstand math, but in a common way. Math is a language. More precisely, it is a formal language. We invented these formal languages because they are well suited for things that need no ambiguity and high precision.

  > Like outlining a program with method names that are unicode symbols.
Code is math. But the reason math says solve for "x" instead of solve for "betterVariableNameHere" is because it is traditionally done with pen and papaer and far predates the electronic computer. You could look at early computer programs, where they were constrained by space and you'll see that they too use minimalism. The reason we use long and meaningful names now is because we have tools like autocomplete.

  > That makes math full of indirection and cryptic symbols.
But this is true of any language. "It's all Chinese to me." It takes a lot of time and effort to understand any language. It's also hard to understand purely from a book and needs to be understood through its culture and the people who speak/write it. Same is true for math. Same is true for programming languages.
reply
I'm not talking about names mostly. I am talking about all the different ways that math notation employs recursion and quantification. They are all fundamentally different parameterizations that are contained in the lambda cube, it's just that writing all the different kinds of parentheses is (I agree) not what people wanted to do, or even knew they were doing, on paper.
reply

  > I am talking about all the different ways that math notation employs recursion and quantification. They are all fundamentally different parameterizations that are contained in the lambda cube
FYI, this is a subset of mathematics. But the reason lambda calculus generally has all those parentheses is because the formulation of that (sub-)language. Grouping those together and writing something nice and tidy is something that is done, but it also has drawbacks.

There is a purpose to the language and to that craziness. You aren't the audience and that's not a bad thing. Your lack of understanding is not a fault of yours. I wouldn't consider you stupid if you didn't know Cantonese. But I also wouldn't expect a Cantonese speaker to speak English to you. It is just a different language and people are using the language that is most effective to communicate with their peers. You don't have to be their peer. You're more than welcome to become one and I'm sure plenty of people would be happy to help you, but it will take time and effort to get there, just as it would were you to learn Cantonese.

reply
> by extracting out potential common parts / definitions as well as introduce notation to make it short.

We don't really do that to make things short, we do that to make things more understandable. People underestimate how important good notation is to properly understanding things, and mathematicians spend an inordinate amount of time just refining notation until it makes things easier to follow.

reply
The "good notation" that makes things easier to follow: Symbols that no layman can so much as name.
reply
Math is a tower of babel situation, and thankfully proof systems like Lean are now powerful enough and have enough momentum that the rendering of math for humans will be syntactic sugar over a more regular computational modeling (which is what was happening all along, just obscured by syntax).
reply
Why would I, an English speaker and writer on a website that's using mostly English, create a symbol targeted at people who can read/write Tagol?
reply
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.

reply
Pretty sure you would not get by speaking Spanish in ancient Rome.
reply
I don't know... I had to take Latin for 4 years as a kid. Latin declensions make it much harder, obviously, but what's Spanish except vulgar Latin? It might take a few weeks, or a few days in bed with a Roman lady.

Not sure how to explain Uranium. Plumbum, but more gravitas?

reply
“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
reply
Exactly. Or, they blame the explainer because they lack the foundational knowledge to understand said concepts.
reply
a.k.a as calling out gatekeeping.

But there is only so much one can do explaining when person on the other side is not putting work to understand stuff.

reply
There are a couple things that come to mind when you say this. The first is that it is indeed not entirely desirable to make the content easy to understand, as it leads to provably lower learning outcomes [1]. It therefore stands that this method is asymmetrically good for the one explaining. The second is the most natural use case for AI is 'summarize this in an easier to digest way' which robs that desirable difficulty. So effectively, a good way to learn with AI is to explain to it, which is counterintuitive.

1. https://bjorklab.psych.ucla.edu/wp-content/uploads/sites/13/...

reply
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.

reply
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...

reply
Agreed. Sometimes people confuse simple with familiar. Even if what is explained is simple, it might seem complex just because it's not familiar.
reply
My favorite pet example is the Burrows-Wheeler transform and its application to compression
reply
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.

reply
> You may get a really fantastic explanation in simple terms from someone who deeply understands the topic, but if you don’t put in the effort you’re not going to understand it yourself. That’s not the fault of the explanation. It’s not an easy concept to grasp so you have to climb the ladder of understanding. The explainer can’t do that for you.

This is why we give recommended reading and pointers to those who really want to understand the topic.

reply
I see it as the opposite - where labwork brilliant professors (who should remain in the lab) are forced in being teachers and managers, so they fake their way through awful lectures and poor pedagogy.

They write complicated derivations on the board with no real teaching, where I can go into a book and read the derivation myself.

I’m there to learn, not watch you rewrite the textbook on the board. If you can’t make the textbook simpler, there is no need for you.

reply
> 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.

reply
I think this is a test for the teacher and not the student.
reply
No.

A Teacher can only do so much; even the best ones. It is the Student who has to put in Self-Effort to study/understand/analyze/think/modify and finally apply/practice.

reply
That is not what I meant. I meant that this is something that should be applied in a student/teacher context. But something that should be introspective...
reply
Not clear what you mean; elaborate?
reply
I mean, it is not something a student should ask about the teacher, but something a teacher should ask about themselves...
reply
I agree a lot with your take about people not wanting to put effort into understanding a complex concept and blaming the definition, but I do think your specific example of compactness and the definition you focused on potentially illustrates the other side. For me, I think the point of compactness is easier to understand in terms of sequences. A big part of why compactness as a definition matters is because it specifies when a sequence will "run out of room" and be forced to converge to a point, so you can take limits and do calculus things with it. In finite dimensions, closed bounded sets are always compact, so it's hard to intuit why this matters. When you get to infinite dimensions, it's no longer true. You don't run out of room because you always have a new dimension you haven't been to to take the sequence in. That's where you see more of the value of a definition like "compactness" - it distinguishes where closed and bounded sets let you assume you're going to be able to force sequences to eventually converge and prove things with that assumption. For me, personally, encountering that sort of example helped me understand compactness much better and why I was studying it, even though I had spent a lot of time learning to prove things with the more abstract definitions. For me, it was a forgettable definition without finding the motivation for it.

I think there's a tension in how people mean "understanding". On the one hand, the example I gave (in my opinion, at least) helps understand the motivation of compactness and why anyone cared to define it in the first place. It makes it easier to understand why the abstract definition is stated the way it is, and provides some intuition that can stimulate approaches to proving things with it. Some of the sibling comments have discussed the tendency in math to distill education to focus on the top-level, abstracted definitions and discard the motivations that led to them. I think finding a way to incorporate those motivations is something that is often overlooked, at least in my experience, and may be some of what this point about "explaining in simple terms" (at least for me, in the example above it's "simpler" than the one you gave).

That is a particular form of "understanding", though, and it doesn't take away from your point. You can't take the intuitive, motivating example I gave and use that to make arguments about compactness without doing the effort of making connections to a more formal definition like the one you gave. In that sense, even if the example I gave were to help someone "understand" in the sense of getting a reason behind the motivation for compactness and what it's used for, it doesn't help them "understand" in the sense of giving them facility in actually working with it. That's where I see a lot of value in your point. Like you said, even if there are examples that may be more intuitive, there is a tendency to not acknowledge that really understanding some complicated things just takes some work.

I feel similarly about complaints I sometimes see about variable naming in programming. Descriptive names make a huge difference in some cases, but the reason a person who hasn't spent time to study differential equations and has trouble seeing the point of

dx_n = dx_p + dt * (-kx_p -cdx_p) / m

doesn't fully understand what's going on if it's written

derivative_of_position_at_next_time = derivative_of_position + change_in_time * (-stiffness_of_spring * position_at_previous_time - damping_constant * derivative_of_position_at_previous_time) / (mass)

...even if those words might help them some picture. I feel like a rough analogy for the concept might be, a person who really "understands" the concept, could probably come up with these variable names to explain the convention, as opposed to someone who has memorized the formula - but (oversimplifying at the risk being unfair to these arguments) there are also people who suggest the only reason they don't understand what the code is doing is because people don't write variables like in the second case.

reply
“A set is compact when its points live in a finite number of neighborhoods.”
reply
[dead]
reply
[flagged]
reply