[frogeyedpeas]

This comes down to the old saying "everything is memorization at the end of the day".

Some people literally memorize answers. Other folks memorize algorithms. Yet other folks memorize general collections of axioms/proofs and key ideas. And perhaps at the very top of this hierarchy is memorizing just generic problem solving strategies/learning strategies.

And while naively we might believe that "understanding is everything". It really isn't. Consider if you are in the middle of a calculus exam and need to evaluate $7 \times 8$ by calculating $7+7+7+7...$ and then proceed to count on your fingers up to 56 because even $7+7$ wasn't memorized. You're almost certainly not going to make it past the first problem on your exam even though you really do understand exactly whats going on .

Similar things are true for software engineering. If you have to stackoverflow every single line of code that you are attempting to write all the way down to each individual print statement and array access it doesn't fucking matter HOW well you understand whats going on/how clear your mental models are. You are simply not going to be a productive/useful person on a team.

At some point in order to be effective in any field you need to eventually just KNOW the field, meaning have memorized shortcuts and paths so that you only spend time working on the "real problem".

To really drive the point home. This is the difference between being "intelligent" versus "experienced".

[chmod775]

> Consider if you are in the middle of a calculus exam and need to evaluate $7 \times 8$ by calculating $7+7+7+7...$ and then proceed to count on your fingers up to 56 because even $7+7$ wasn't memorized. You're almost certainly not going to make it past the first problem on your exam even though you really do understand exactly whats going on.

This is not a counterexample because exams aren't an end goal. The process of filling out exams isn't an activity that provides value to society.

If an exam poorly grades a student who would do great solving actual real-world problems, the exam is wrong. No ifs. No buts. The exam is wrong because it's failing the ultimate goal: school is supposed to increase people's value to society and help figure out where their unique abilities may be of most use.

> Similar things are true for software engineering. If you have to stackoverflow every single line of code that you are attempting to write all the way down to each individual print statement and array access it doesn't fucking matter HOW well you understand whats going on/how clear your mental models are. You are simply not going to be a productive/useful person on a team.

If their mental models are truly so amazing, they'd make a great (systems) architect without having to personally code much.

[sim04ful]

I can't totally agree with your counter-counter example. Most non trivial problems are time bound, deadline exist, and no matter how well ingrained you are in first principles thinking you won't be useful if it takes months to come up with a solution.

[skhunted]

To know something includes speed of regurgitation. Consider a trauma surgeon. You want them to know, off the top of their head, lots of stuff. You don’t want them taking their time and looking things up. You don’t want them redefining everything from first principles each time they perform surgery.

Knowing a topic includes instant recall of a key body of knowledge.

[1659447091]

I would say knowing and understanding is not necessarily the same. In this example the surgeon having both understanding and memory/knowing is best/required. If I had to pick between the two, I want the one that understands my particular trauma, even if that means they have give instructions for someone else or a machine to performing it.

I think an example closer to the above posts would be: If I needed cpr or defibrillation, I would much prefer a paramedic be next to me and make that call and performance than a med student or a defibrillator manufacture's electrical engineer.

[westurner]

Maybe survey engineers with a first order derivative question and a PDE question n years after graduation with credential?

CAS and automated tests wins again.

A robosurgeon tech that knows to stop and read the docs and write test assertions may have more total impact.

[skhunted]

I’m ABD in math. It was 30 years ago that I decided to not get a Ph.D. because I realized that I was never going to be decent at research. In the last 30 years I have forgotten a great of mathematics. It is no longer true that I know Galois Theory. I used to know it and I know the basic idea behind and I believe I can fairly easily relearn it. But right now I don’t know it.

[westurner]

That's wild, we all use AES cipers w/ TLS/HTTPS everyday - and Galois fields are essential to AES - but few people understand how HTTPS works.

The field is probably onto post-AES, PQ algos where Galois Theory is less relevant; but back then, it seemed like everyone needed to learn Galois Theory, which is or isn't prerequisite to future study.

The problem-solving skills are what's still useful.

Perhaps problem-solving skills cannot be developed without such rote exercises; and perhaps the content of such rote exercises is not relevant to predicting career success.

[frogeyedpeas]

> Re: "this is not a counter example because exams aren't an end goal..." for any end goal with a set end time there are habits that need to be second nature and information that one needs to know in order to achieve that goal. If you lack those habits and don't know those facts it's going to be very hard to achieve that goal.

I used the example of a calculus test and not being able to do addition. But this really could be any example. It could have even been a Wide Receiver failing to read the play thats happening quickly enough despite being physically fit enough to execute the right play in hindsight.

>Re: they'd make a great (systems) architect...

But you wouldn't hire them as a programmer. My sentence was biased in the sense that "team" meant "team of software engineers". You would hire them for a different job sure.

Also good mental model here just means "Always knowing and being able to clearly articulate what I need to accomplish next to write my code". It doesn't even mean they are good at designing systems but lets go with that example anyways below:

The Architect version of this is that they perhaps have perfectly clear mental models of exactly how to code (memorizing very obscure language shortcuts and syntactic sugar and writing very clear code when they know what to build) but they cannot for the love of god think critically about what a design should be BEFORE they implement it far enough to reach a major issue.

And you would rightly say "well I would never hire that guy as an architect but I might have hired them as a programmer thats led by more senior folks". At the end of the day you are only hiring people for the parts of their mental models that are useful.

And the ability to clearly recall facts about that their domain is basically the fundamental detail here.

[1659447091]

I agree with you that memorization is an optimization for getting daily task done (maybe not as optimal when novel solutions are needed; understanding/mental model might win out here). But we have tools to help take the load off memorization. The person that `understands` addition not as 7 + 7 but as incrementing a number a certain amount of times can use a calculator to solve the problem in a more efficient way.

I would probably not make a developer who had great mental models but lacked coding chops my first hire. Nor the programmer that could make code do amazing things but can not grasp the domain model. I would, however, probably consider them(the mental model one) the 100th to clean up backlogged bug fixes, and the code whiz to implement the more technically difficult backend niche feature/optimization. As much as it pains me to say it, github copilot chat works surprisingly well IF you can give it a clear concise description of the model and expectations. Then someone with an excellent mental model can create the smaller lego pieces and put it together, minimal coding required. Not only for the popular languages, I play with it from time to time using clojure.

[pfortuny]

You can only think using memory.

[superposeur]

To support your point, I think the role of memory in creative work is highly underrated.

I’ve seen up close a few people who could fairly be described as “most creative researchers in the world” (in my field at least) according to metrics such as h-index and Nobel prizes. It always strikes me how essential exceptional memory is to what they do — they have detailed, immediate recall of the problems in their field and, to the extent this recall is no longer present, then they are no longer producing groundbreaking work. Their recall of facts outside the field is often nothing special.

Imagination, creativity, intelligence all seem to rely on memory in order to operate.

[throwuxiytayq]

> And perhaps at the very top of this hierarchy is memorizing just generic problem solving strategies/learning strategies.

I'm not sure this counts as memorization. I don't even think you can really "memorize" high level learning and problem solving strategies, even when explained by an expert. You kind of have to re-discover them internally. And then, there are people who "memorized" the explanation and are completely unable to put it into practice because to them it's just a word sequence, instead of an internalized change to the way you perceive and work with problems.

[frogeyedpeas]

You absolutely can. I remember struggling with some problems on AOPS and then reading in a book "always consider smaller $n$ when dealing with a problem that is difficult because of large $n$" and ever since then that habit has stuck. Whenever I have a problem thats hard and involves numbers and i'm stuck I just remember to ask "what if the numbers were smaller? what do we do then?"

If that isn't memorizing something and making a new habit as a kid then I don't know what memorizing means.

Said another way, the ability to remember to "____" when dealing with a problem of type "___" is what I mean by "memorize".

[throwuxiytayq]

> Whenever I have a problem thats hard and involves numbers and i'm stuck I just remember to ask "what if the numbers were smaller? what do we do then?"

I think you underestimate the amount of internalized understanding of the "unblock yourself on a difficult problem by solving a simpler version of it" strategy that you possessed or unlocked at learn-time which allowed you to notice its effectiveness. Isn't the sentence more of an easily-retrievable mnemonic for a concept that's much more complicated (than just the information transferred by language) and requires a particular background to recognize how useful it is?

[nickpsecurity]

They’re called heuristics in problem-solving literature. Both heuristics and meta-heuristics have been used in planning software. Heuristics from one system are sometimes reused in another system. So, you can memorized generic, problem-solving strategies.

I don’t know how much human brains do in that area vs non-memorization approaches. Ive read about how practicing rational, problem solving in specific domains to bake those heuristics into one’s intuition for faster responses. Most of us have done that, too. Any type of intuitive, problem solving probably involves memorization for that reason.

[TeMPOraL]

Memorization is caching. You need it because otherwise you'd be too slow at anything, but you can't possibly memorize everything, and the whole point of understanding is so you don't have to. And like with any caching, the more you store, the more it costs to maintain it, and the longer the lookups become. If you want to cram a lot of stuff into it, you may need to start doing actual, expensive work - e.g. spaced repetition - to keep it all.

AS for memorizing generic problem solving strategies - I don't think it's about not memorizing, but rather that understanding comes through examples, and if you learn high-level stuff without actually applying it in practice, and experiencing the process, then you haven't actually learned the high-level stuff, you just think so, and will parrot the description without comprehending it.

[bitshiftfaced]

Nah, there's such a thing as creative thinking, idea generation, and connecting existing ideas in new ways. I wouldn't mind a coder that has to look at stack overflow a lot but is able to figure out a new method to do something better.

[frogeyedpeas]

You absolutely would never hire a coder that needs to google "how to access an array by index" every-time they need to access an index of an array.

You can say a politically correct answer like "i don't care how they do it, as long as they get it done" but such a coder will DEFINITELY take months to finish what might take someone else hours.

Such a coder might still be able to suggest new methods to do something better and if there job description was "organizational optimizer" perhaps thats fine but as soon as you also expect software output out of this person you will quickly realize that you take for granted how valuable someone that has fully memorized a bunch of fundamentals up to and including some problem strategies truly is.

[youerbt]

That makes no sense to me. If this coder has to access array by index twenty times a day, then he is going to remember it, eventually, no? If is it rare that he has to do it, then why memorize it?

You really think there is more value in remembering how to do something in some arbitrary, shitty, programming language than understanding the concept of doing it? With understanding the idea you can do it in any language, at any time, it is just a few seconds away.

[mrmetanoia]

It makes no sense because it indeed makes no sense. People who successfully solve realworld problems understand concepts and ideas and how to apply them, they understand how to iterate and extrapolate.

I've met too many people who can do a specific thing but actually have no idea what's going on for the GP's logic to hold any water at all.

[kiba]

It's not about the value in remembering syntax. It's the value in being able to recall a concept from memory.

Memory is a key part of learning. Understanding is great for learning new concepts, but you want to already know a concept. That way lies knowledge and experience.

[paulpauper]

agree. how else do famous unsolved math problems eventually get solved?

[math_dandy]

It varies, but it often comes down to deep expertise combined with creativity, years of toil, and standing on the shoulders of giants. Cf. Fermat’s Last Theorem, bounded gaps between primes, the Weil conjectures, the Poincaré conjecture, etc.

[brigadier132]

Search.

[lo_zamoyski]

> At some point in order to be effective in any field you need to eventually just KNOW the field, meaning have memorized shortcuts and paths so that you only spend time working on the "real problem".

Yes, there is a "habitus" to mastery. It becomes you, or you become it, so to speak.

But pedagogically speaking, I think what people miss is that you can't really use or think about something you don't remember.

[bbor]

I love this long detailed conversation with many people jumping in, and 0 references to philosophers of the mind… gee guys, I wonder how we could crack this code? Even the paper itself cites one cognitive psychologist then moves on! A bit of relatable intellectual arrogance from us SWEs/mathematicians, I think — we are “on top of the world” right now.

FWIW I think you in particular are exactly right. I always think of Schopenhauer’s quote, and I think any software engineer might appreciate it: human memory isn’t storing items received from the world in a database, it’s more like folding creases into a napkin so that it naturally tends to fall into that shape in the future. In other words: remembering an event is equivalent to developing the skill of imagining a scene/dataframe that relates to that event.

In specific math terms: math is a collection of intellectual tools building on one another. You can certainly practice the ability to apply tools in new situations, but if you don’t also practice the ability to recall the tools themselves, it’s useless.

[fallingknife]

But is that actually what human memory is like? AFAIK nobody actually understands the internals. The "philosophers of the mind" who claim to know are the ones guilty of arrogance, not those who don't cite them.

[bbor]

Well, we should collect some evidence and write a book! If we did, it would be filed into the philosophy of mind section, I believe ;)

We don’t know everything, but we have more evidence than “it’s a black box” - in fact, that’s basically the scholastic / Aristotlean view that was conquered by our friends Bacon, Hume and Kant a few hundred years ago.

[wizzwizz4]

> If you have to stackoverflow every single line of code that you are attempting to write all the way down to each individual print statement and array access

Then you may be a perfectly adequate programmer. This, what, doubles the length of time it takes to type out the program? Triples? Typing out the program is not what takes the time!

I've just spent a couple of days writing a plugin in a language I don't know. (The system documentation spends two paragraphs explaining how hard it is to solve the problem I solved.) Yes, I had to look up absolutely everything (including basic language syntax – repeatedly), and that was really annoying, but most of my time and effort went into figuring out how to do the thing.

[kiba]

You already have programming knowledge that you can use to leverage toward that task. For a complete beginner, such a project might be a non-starter.

Like, once you learn a programming language, you already know the syntax for 90% of all languages.

[wizzwizz4]

Here's a collage of some of my favourite bits. (I've inlined some functions, but this is nearly as readable as the actual code.)

  open Option Parse Scan;
  (maybe embedded --| minus -- name >> (fn arg => ((if ! testing then #2 arg |> Output.writeln else (); #1 #> curry getOpt) arg (implode [])))) -- command_name "supply" >> (op ^)

What does this say?

[greentxt]

"everything is memorization at the end of the day"

Only somebody who has never thought about or studied human cognition would memorize such a thing. ;)

But in all seriousness, memory isn't even memory isn't just memorization. Much of it is attention, some would even say attention is all you need. ;)

In all seriousness though, arguably, reducing the human mind down to a single dimension like "recall" (or attention) while ignoring other dimensions like emotion, creativity and so on is probably good evidence that human cognition is neither simple, nor unidimensional, for some of us humans at least. Ymmv

[mhh__]

I think the antidote is driving education as a journey through the great questions of history.

What was Newton trying to do? What Faraday investigating? Darwin? Smith? Marx? Descartes and so on.

Everything is connected and there is something interesting for everyone, we just don't try.

[drewcoo]

> This comes down to the old saying "everything is memorization at the end of the day".

I certainly don't remember hearing that!

[FredPret]

Maybe understanding is simply having memorized a handy instantiation of the relevant concept

[jltsiren]

I'd say memorization and building expertise are orthogonal.

Expertise is lossy intuitive reasoning. It's pattern recognition based on practice and experience. Then there is logical reasoning based on memorized facts, which is a fallback mechanism people use when they don't have the necessary skills. It usually fails, because it's inefficient, it doesn't scale, and it doesn't generalize.

Sometimes memorization is necessary, but it's often not the actual point. When kids are asked to memorize the multiplication table, they are not really supposed to memorize it. They are supposed to build a mental model for multiplying numbers without resorting to first principles or memorized answers. Then if your model can calculate 7 * 8, you can also use it to calculate 7e10 * 8e11, even if you haven't memorized that specific fact.

[tsimionescu]

The multiplication table doesn't have patterns, or it only has a few. You really do need to remember all of the 100 results. I know what 7*8 is, and I know the rules for exponents, so I can compute 7e10*8e11. But I can't "deduce" what 7*8 is by any rule, it's just a fact I remember. I have certainly not added 7 to itself 8 times in decades.

[LouisSayers]

> I can't "deduce" what 7*8 is by any rule

But you can break this into a different problem knowing that 2^3 = 8, and doing 7*2*2*2.

This isn't as fast but is in a way more useful because while 7*8 is fairly easy to remember you're not going to remember 17*8 etc but you can problem solve it fairly quick.

There are other ways of seeing the multiplication table as well. For example 9 times something can be thought of as 9*x = 10*x-x.

I never learnt these, but simply realised over time that there are different approaches to doing calculations.

[Dylan16807]

> But you can break this into a different problem knowing that 2^3 = 8, and doing 7*2*2*2.

Doing that multiplication all the way through is super slow. When they said "can't" they meant in an effective sense, since they did mention repeated addition as an option. And that's not an effective way to get there.

> There are other ways of seeing the multiplication table as well. For example 9 times something can be thought of as 9*x = 10*x-x.

Yes, you can do that one. But that's just about the only fast trick there is.

[lelanthran]

> Yes, you can do that one. But that's just about the only fast trick there is.

I dunno about that. For division, anyway, there's a bunch of fast tricks that give you a decent approximation (i.e. decent precision, maybe to the nearest integer)

Someone recently was surprised that I worked out the VAT (Value Added Tax, 15%) on a very large number in a few seconds. It's because its 10% of the number plus `(10% of the number)/2`.

It's easy to get 10% of any number. It's easy to halve any number. It's a fast trick because there's two easy operations.

There's a bunch of similar "tricks": 1%, 10%, 25% and 50% are fast to calculate in your head (at most 2 easy operations, like `(half of half of N)`). Then you either add or subtract N. Or you multiply N by 2.

At most three easy operations gives you 1%, 2%, 4%, 5%, 10%, 11%, 12%, 14%, 15%, 20%, 21%, 24%, etc

To someone who doesn't know how you are getting the answer it might seem like you are a human calculator because you get so many of those quickly, and they don't see the ones you don't do in 3 easy operations (say, 13%, which is 10% + 1% + (1% * 2)).

IOW, it looks like a very impressive trick, but it isn't.

[Dylan16807]

> For division, anyway

Did you not see the neighbor comment where I made it extra clear I'm talking about times tables in particular?

There are tons of math tricks! But the multiplication table of the numbers between 1 and 10 is mostly rote.

[wizzwizz4]

Multiplication and division by 2 and 5 correspond to each other. Multiplication by 11 is shift-and-add. There are many such tricks.

[Dylan16807]

The first one doesn't help with remembering times tables. The second one is outside the 1-10 times table we were talking about.

[tsimionescu]

I completely disagree. First of all, at the time children learn the multiplication table, they definitely don't know the concept of exponentiation. Secondly, 7*2*2*2 is not some immediately obvious shortcut.

Also, learning multiplication with numbers higher than 10 still relies on knowing the multiplication table. 17*8 is 7*8=56, hold the 5, 1*8 + 5 = 13, so 136.

[LouisSayers]

> Also, learning multiplication with numbers higher than 10 still relies on knowing the multiplication table

You've actually just proved my point - you used a method of breaking down the problem into a different problem and then solving it rather than simply memorising.

If you give the same question to multiple people there will be numerous ways different people use to go about solving it.

As an example, I might solve this by doing

20*8 = 160 3*8 = 24 160 - 24 = 136

Or 10*8 = 80 7*8 = 56 80+56 = 136

And I might apply different tools like the one I originally mentioned within these calculations. I know that 80+20 is 100 and so "borrow" 20 from 56, so that I can easily add 100 and 36 together.

These ways of calculating happen in your mind very quickly if this is how you get used to calculating.

[tsimionescu]

Sure, but all of those work for numbers higher than 10, and all assume you know the multiplication table by heart. The multiplication table (the result of multiplying every number between 1 and 10 with each other) is something you have to memorize. You can get away with memorizing only some of these results and computing the others based on them, but it's basically impossible to do any more complex arithmetic if you don't know most of it by rote memorization.

[lelanthran]

> Also, learning multiplication with numbers higher than 10 still relies on knowing the multiplication table. 17*8 is 7*8=56, hold the 5, 1*8 + 5 = 13, so 136.

Interestingly, I do those less efficiently:

    17 * 8
     = (10 * 8) + (7 * 8)
     = (80) + (56)
     = (80) + (50 + 6)
     = 130 + 6

I think the reason I do it this way is because I get an approximation sooner when the numbers are very large i.e. I get the most significant digit first, and can stop calculating when I get the precision I require.*

[jltsiren]

Of course there is a pattern: (n+1)x = nx+x. Your brain can learn it just fine, and then it can multiply numbers without having to burden your slow inefficient symbolic reasoning machinery with rules and facts.

[tsimionescu]

How is that pattern useful for replacing memorization of the multiplication table? 7*8 = 6*8 + 8 - fine. I still need to memorize what 6*8 is, or go through the extraordinarily slow process of expanding this recursively: definitely not an option in school.

[jltsiren]

It's a linear function your brain can learn. Your brain, not the conscious you. A lot of learning is about bypassing the slow inefficient consciousness that thinks it's in charge.

In sports and other physical activities, you don't memorize the right moves. You practice them until you can do them automatically. The same approach also works with cognitive activities.

[tsimionescu]

If that were how people learned the multiplication table, you would see that people take longer to come up with the result of 9*9 than it takes them to compute 3*5. I have never seen anyone work this way, and so I believe it's far more likely people just remember the results in a table. "9*9=81" is simply a fact you have stored, not a computation you perform, even subconsciously.

Edit: I should also note that it's pretty well known people learn arithmetic as symbol manipulation and not some higher order reasoning. The reason this is pretty well established is that historically, the switch from Roman numerals to Arabic numerals led to a huge flurry of arithmetic activity, because it was so much easier to do arithmetic with the new symbols. If people had learned by subconsciously calculating the underlying linear functions and not through symbolic manipulation, the switch would have been entirely irrelevant. Yet for most mathematicians in Europe at the time, doing 27*3 was much easier than doing XXVII*III.

[iwsk]

When kids are asked to memorize the multiplication table, they are actually supposed to memorize it.

[brigadier132]

> It's pattern recognition based on practice and experience

This is arguably another form of memorization. Magnus Carlson is the best Chess player in the world because he memorizes everything without effort.

[jltsiren]

It's memorization in the same sense as an LLM is a database. You can think like that if you prefer, but I don't find it a useful perspective.