WEBVTT 00:00:00.000 --> 00:00:03.680 OK, let's start with a scenario. I think you've 00:00:03.680 --> 00:00:05.820 probably been there. Oh, almost certainly. Right. 00:00:06.019 --> 00:00:09.500 Maybe you spent weeks like prepping for a huge 00:00:09.500 --> 00:00:12.259 presentation or you read some massive policy 00:00:12.259 --> 00:00:14.679 brief, 100 pages long. Yeah, you felt totally 00:00:14.679 --> 00:00:17.160 on top of it. Totally. You can recite every figure, 00:00:17.300 --> 00:00:19.379 every precedent, market trends, whatever it was. 00:00:19.820 --> 00:00:23.399 You felt ready, prepared, confident. Exactly. 00:00:24.420 --> 00:00:28.179 But then maybe just a few days later, a colleague 00:00:28.179 --> 00:00:31.440 asks you something. Slightly different. A related 00:00:31.440 --> 00:00:33.979 problem, but a bit of a curveball. And suddenly 00:00:33.979 --> 00:00:37.880 blank. Completely blank. Or worse, you know the 00:00:37.880 --> 00:00:39.820 information's in there somewhere, but you just 00:00:39.820 --> 00:00:43.020 can't access it for this new thing. It's just 00:00:43.020 --> 00:00:45.000 sitting there. Idle. That information you ate 00:00:45.000 --> 00:00:47.359 the test with or nailed the meeting Q &A with. 00:00:47.500 --> 00:00:51.670 Now it's useless. Stuck. So why does that happen? 00:00:51.750 --> 00:00:53.750 That's a really fundamental question about learning, 00:00:53.990 --> 00:00:55.909 isn't it? It is. And today we're doing a deep 00:00:55.909 --> 00:00:58.390 dive into, well, one of the classic critiques 00:00:58.390 --> 00:01:00.530 on this very problem. It's the idea of inert 00:01:00.530 --> 00:01:03.649 knowledge. A powerful concept. Our mission here 00:01:03.649 --> 00:01:08.069 is to figure out why just, you know, receiving 00:01:08.069 --> 00:01:10.290 information often doesn't actually lead to real 00:01:10.290 --> 00:01:13.400 learning. or applicable skill. And we're drawing 00:01:13.400 --> 00:01:15.579 mainly from the work of Alfred North Whitehead 00:01:15.579 --> 00:01:17.620 for this. That's right. The British philosopher 00:01:17.620 --> 00:01:21.439 and mathematician, specifically his essay from 00:01:21.439 --> 00:01:25.500 1929 found in the Aims of Education. A really 00:01:25.500 --> 00:01:27.540 influential piece. Yeah, Whitehead was sounding 00:01:27.540 --> 00:01:30.540 this warning, this alarm about ideas we pick 00:01:30.540 --> 00:01:33.349 up that just... stagnate, they don't do anything. 00:01:33.469 --> 00:01:35.530 They just sit there. So we're going to unpack 00:01:35.530 --> 00:01:37.969 the difference, the critical difference between 00:01:37.969 --> 00:01:40.689 just knowing something, having it stored away, 00:01:41.150 --> 00:01:43.849 and actually being able to, well, use it. Deploy 00:01:43.849 --> 00:01:46.010 it, combine it with other things, use it to tackle 00:01:46.010 --> 00:01:47.969 something new. And what's really striking, I 00:01:47.969 --> 00:01:50.189 think, is that Whitehead wrote this nearly a 00:01:50.189 --> 00:01:53.959 century ago. Yeah. It feels so incredibly relevant 00:01:53.959 --> 00:01:56.920 today, doesn't it, with this constant flood of 00:01:56.920 --> 00:01:58.480 information we're all dealing with? Totally. 00:01:58.719 --> 00:02:01.140 So contextually, he was reacting to? Well, he 00:02:01.140 --> 00:02:02.939 was looking at an education system back then 00:02:02.939 --> 00:02:05.700 that was heavily focused on rote memorization. 00:02:06.019 --> 00:02:08.099 Right, learning facts for their own sake. Yeah, 00:02:08.139 --> 00:02:10.500 often classical subjects, kind of disconnected 00:02:10.500 --> 00:02:13.719 from immediate use or application. OK. And he 00:02:13.719 --> 00:02:15.939 looked at that system and came up with this core 00:02:15.939 --> 00:02:18.139 idea, the definition we really need to grasp. 00:02:18.400 --> 00:02:21.479 He called them inert ideas. Inert ideas. And 00:02:21.479 --> 00:02:25.219 his definition was, let me get this right, ideas 00:02:25.219 --> 00:02:27.599 that are merely received into the mind without 00:02:27.599 --> 00:02:30.719 being utilized or tested or thrown into fresh 00:02:30.719 --> 00:02:33.539 combinations. Without being utilized, tested, 00:02:33.939 --> 00:02:36.159 or thrown into fresh combinations. That's the 00:02:36.159 --> 00:02:38.939 key point. That's the core of it. It's like, 00:02:39.479 --> 00:02:41.699 imagine downloading a piece of software onto 00:02:41.699 --> 00:02:44.229 your computer. But you never actually install 00:02:44.229 --> 00:02:46.669 it. It's just sitting there, taking up space 00:02:46.669 --> 00:02:48.669 on your hard drive. Right. It's present, but 00:02:48.669 --> 00:02:51.250 it doesn't do anything. Exactly. It's non -functional. 00:02:51.270 --> 00:02:53.090 It hasn't been integrated. You know, I think 00:02:53.090 --> 00:02:55.870 the paradox there is what gets confusing for 00:02:55.870 --> 00:02:58.110 people, for you, the listener, maybe. Because 00:02:58.110 --> 00:02:59.830 inert knowledge isn't really about forgetting, 00:03:00.090 --> 00:03:02.930 is it? No, not necessarily. That's a really important 00:03:02.930 --> 00:03:05.370 distinction. It's about being able to successfully 00:03:05.370 --> 00:03:09.250 retrieve the information, but only. Only in the 00:03:09.250 --> 00:03:11.430 exact same way you learned it. Precisely. The 00:03:11.430 --> 00:03:15.389 moment the context shifts, even slightly, poof, 00:03:15.789 --> 00:03:18.229 it fails. Can we make that more concrete? Maybe 00:03:18.229 --> 00:03:20.509 an example. Oh yeah, absolutely. Let's take something 00:03:20.509 --> 00:03:23.189 many listeners might encounter. Say, learning 00:03:23.189 --> 00:03:26.240 a new programming language. Let's pick Python. 00:03:26.460 --> 00:03:29.199 OK, Python. So passive learning might involve 00:03:29.199 --> 00:03:31.800 just memorizing all the function definitions, 00:03:32.139 --> 00:03:35.639 the syntax rules, the order of operations. Like 00:03:35.639 --> 00:03:37.979 studying flashcards for the definitions. Exactly. 00:03:38.500 --> 00:03:41.219 And if I give you a multiple choice quiz asking, 00:03:41.379 --> 00:03:42.879 you know, what's the difference between a list 00:03:42.879 --> 00:03:45.599 and a dictionary in Python, you might get 100%. 00:03:45.599 --> 00:03:47.939 You know the definitions. OK, sounds like success 00:03:47.939 --> 00:03:50.909 so far. Ah, but is it? According to Whitehead, 00:03:51.150 --> 00:03:53.629 maybe not. Because now, what if I ask you to 00:03:53.629 --> 00:03:55.650 take those definitions, those rules you memorized, 00:03:56.250 --> 00:03:58.270 and write a short script, maybe one that scrapes 00:03:58.270 --> 00:04:00.889 some data from a website, structures it somehow, 00:04:01.229 --> 00:04:03.090 and then uses those elements to solve a little 00:04:03.090 --> 00:04:05.389 puzzle I just made up? Okay, a practical task. 00:04:05.650 --> 00:04:08.110 And let's say the script has a small bug in it. 00:04:08.219 --> 00:04:11.300 A subtle error. That's the real test. Right. 00:04:11.659 --> 00:04:14.780 Can you apply the knowledge? Can you deploy those 00:04:14.780 --> 00:04:17.480 facts you memorized, the definitions, the syntax 00:04:17.480 --> 00:04:20.399 to figure out the bug, or to structure a solution 00:04:20.399 --> 00:04:23.199 to this new puzzle? And if you can't? Then even 00:04:23.199 --> 00:04:25.019 though you still know the definitions for the 00:04:25.019 --> 00:04:27.620 quiz, those facts are inert. They're useless 00:04:27.620 --> 00:04:30.319 for this practical task. So the knowledge is 00:04:30.319 --> 00:04:33.550 like... Trapped. It's in memory, but it won't 00:04:33.550 --> 00:04:36.110 come out unless you ask the exact same quiz question. 00:04:36.230 --> 00:04:37.970 Pretty much. It's siloed. It doesn't connect 00:04:37.970 --> 00:04:39.810 to other things. It's not activating outside 00:04:39.810 --> 00:04:42.269 that initial very narrow context. Like files 00:04:42.269 --> 00:04:45.050 that won't link together. Exactly. It's siloed 00:04:45.050 --> 00:04:47.589 and, crucially, unusable for building anything 00:04:47.589 --> 00:04:50.670 new on top of it. Ah, OK. So Whitehead argues 00:04:50.670 --> 00:04:54.730 that even that 100 % quiz score, it still shows 00:04:54.730 --> 00:04:57.110 inert knowledge if you can't connect those dots 00:04:57.110 --> 00:04:59.610 later. The failure isn't retrieval per se. It's 00:04:59.610 --> 00:05:02.040 application. It's the inability to solve new 00:05:02.040 --> 00:05:05.379 problems or, and this is key, to use that information 00:05:05.379 --> 00:05:08.000 as a foundation, to build new knowledge structures 00:05:08.000 --> 00:05:10.879 on top of it. It's like a dead end. You learn 00:05:10.879 --> 00:05:13.240 this thing, but it doesn't lead anywhere else. 00:05:13.420 --> 00:05:15.699 A knowledge dead end. That's a good way to put 00:05:15.699 --> 00:05:17.920 it. OK, but this really challenges how we usually 00:05:17.920 --> 00:05:20.300 think about learning, doesn't it? I mean, we're 00:05:20.300 --> 00:05:22.779 often trained to believe in a sequence. Definitely. 00:05:23.259 --> 00:05:26.019 You know, first, consume the information, get 00:05:26.019 --> 00:05:29.779 the facts. Second, store them. And then third, 00:05:29.920 --> 00:05:33.319 maybe much later, apply them. Right. The assumption 00:05:33.319 --> 00:05:35.800 is, how can they possibly use the information 00:05:35.800 --> 00:05:39.279 until they know it first? Many teachers, many 00:05:39.279 --> 00:05:42.019 managers still operate this way. And that feels 00:05:42.019 --> 00:05:44.500 logical on the surface. I mean, if you're studying 00:05:44.500 --> 00:05:47.040 for something like, say, professional certification 00:05:47.040 --> 00:05:50.480 or the bar exam, don't you need to know the sacks 00:05:50.480 --> 00:05:54.189 first? How can Whitehead argue against that basic 00:05:54.189 --> 00:05:56.350 sequence? Well, that's a really critical point, 00:05:56.389 --> 00:05:58.810 and it gets us right into the core of Whitehead's 00:05:58.810 --> 00:06:01.829 argument. He's not actually arguing against knowing 00:06:01.829 --> 00:06:04.370 facts or learning foundational content. Okay, 00:06:04.389 --> 00:06:06.689 so it's not anti -fact. Not at all. He's arguing 00:06:06.689 --> 00:06:08.670 against passive acquisition. That's the target. 00:06:09.170 --> 00:06:12.009 Passive acquisition, meaning just taking it in 00:06:12.009 --> 00:06:15.000 without doing anything. Yes. He's challenging 00:06:15.000 --> 00:06:18.360 the whole idea of the mind as like a blank slate 00:06:18.360 --> 00:06:20.980 or an empty bucket that you just passively pour 00:06:20.980 --> 00:06:23.680 facts into. Hoping they'll somehow become useful 00:06:23.680 --> 00:06:26.339 later on their own. Exactly. Hoping that application 00:06:26.339 --> 00:06:28.899 will just magically spark down the road. That's 00:06:28.899 --> 00:06:31.800 what he says doesn't work. So why doesn't it 00:06:31.800 --> 00:06:35.500 work according to him? Or maybe how does learning 00:06:35.500 --> 00:06:38.860 actually work if not like that? Well, If we look 00:06:38.860 --> 00:06:41.560 at it through a modern cognitive science lens, 00:06:41.800 --> 00:06:43.660 which aligns really well with Whitehead, actually, 00:06:44.060 --> 00:06:46.339 we understand that learning isn't about filling 00:06:46.339 --> 00:06:48.839 a bucket. It's about building mental models or 00:06:48.839 --> 00:06:51.939 what psychologists call schemas. Schemas. Like 00:06:51.939 --> 00:06:55.300 frameworks. Sort of. Frameworks, networks, interconnected 00:06:55.300 --> 00:06:57.480 structures of understanding. And these are built 00:06:57.480 --> 00:07:00.120 not by just passively receiving stuff. But by 00:07:00.120 --> 00:07:03.189 doing something with it. Yes. By actively synthesizing 00:07:03.189 --> 00:07:05.290 information, connecting it to what you already 00:07:05.290 --> 00:07:07.689 know, testing it, revising your existing structures, 00:07:08.029 --> 00:07:10.370 it's an act of process. So if information comes 00:07:10.370 --> 00:07:12.449 in and you don't immediately try to connect it 00:07:12.449 --> 00:07:15.089 or use it to adjust your existing mental map, 00:07:15.370 --> 00:07:18.149 then it's very likely to just float away, be 00:07:18.149 --> 00:07:21.089 forgotten. Or worse, it sticks around but becomes 00:07:21.089 --> 00:07:24.490 that inert, unusable stuff. OK, so when I just 00:07:24.490 --> 00:07:27.870 passively read that policy brief, even if I highlight 00:07:27.870 --> 00:07:30.490 it, If I'm not arguing with it in my head, or 00:07:30.490 --> 00:07:32.970 trying to connect it to other policies, or imagining 00:07:32.970 --> 00:07:35.269 explaining it to someone. You're likely failing 00:07:35.269 --> 00:07:38.470 to build or update the schema you need. The structure 00:07:38.470 --> 00:07:40.970 required for you to actually use that information 00:07:40.970 --> 00:07:43.769 later in a new situation isn't being built. Which 00:07:43.769 --> 00:07:46.069 brings us back to Whitehead challenging that 00:07:46.069 --> 00:07:49.970 sequence. No first, use later. Absolutely. He 00:07:49.970 --> 00:07:52.750 argued the mind isn't passive, it's fundamentally 00:07:52.750 --> 00:07:55.529 active, it's curious, it's always doing something. 00:07:55.689 --> 00:07:57.269 Always trying to make sense of things. Always. 00:07:57.529 --> 00:07:59.750 And this leads to, I think, his most powerful 00:07:59.750 --> 00:08:02.750 rebuttal. He said, the mind is never passive. 00:08:03.170 --> 00:08:05.750 You cannot postpone its life until you have sharpened 00:08:05.750 --> 00:08:08.810 it. Wow. OK, you cannot postpone its life until 00:08:08.810 --> 00:08:11.850 you have sharpened it. Yeah. Think about that. 00:08:11.990 --> 00:08:14.029 That just completely flips the common model. 00:08:14.170 --> 00:08:16.529 It's saying the sharpening, the activity, the 00:08:16.529 --> 00:08:19.149 using that is the learning process itself. It's 00:08:19.149 --> 00:08:21.560 not something that comes after. Exactly. The 00:08:21.560 --> 00:08:23.360 mind is trying to make sense of the world right 00:08:23.360 --> 00:08:25.759 now. If you just force feed it facts that have 00:08:25.759 --> 00:08:29.360 no immediate connection, no utility now. It resists. 00:08:29.540 --> 00:08:32.080 Or finds a shortcut. It resists. Or, yeah, it 00:08:32.080 --> 00:08:35.080 finds the absolute bare minimum path to meet 00:08:35.080 --> 00:08:38.549 the immediate demand. Which might just be memorizing 00:08:38.549 --> 00:08:41.850 the arbitrary link between fact A and test question 00:08:41.850 --> 00:08:44.330 A. Well, nothing deeper. No real integration. 00:08:44.409 --> 00:08:46.710 No real integration. No connection to fact B 00:08:46.710 --> 00:08:49.629 or real -world problem C. Okay. This is really 00:08:49.629 --> 00:08:52.549 important then for you, the listener, especially 00:08:52.549 --> 00:08:54.470 in a professional setting. Hugely important. 00:08:54.570 --> 00:08:56.269 If you're sitting in a high -stakes meeting, 00:08:56.990 --> 00:09:00.029 data is being presented. If you just nod and 00:09:00.029 --> 00:09:02.470 mentally file it away under data from meeting. 00:09:02.830 --> 00:09:05.429 That data is probably already on its way to becoming 00:09:05.429 --> 00:09:07.610 inert for you. So to make it real knowledge, 00:09:07.649 --> 00:09:10.009 you have to force the utility right then and 00:09:10.009 --> 00:09:12.730 there. You have to force it. Ask yourself immediately, 00:09:12.950 --> 00:09:17.710 OK, how does this new piece of information challenge 00:09:17.710 --> 00:09:19.850 what I thought I knew? How does it change my 00:09:19.850 --> 00:09:21.750 current strategy? How does it connect to that 00:09:21.750 --> 00:09:23.950 other project? That questioning, that struggle 00:09:23.950 --> 00:09:26.049 to connect, that's the utilization Whitehead 00:09:26.049 --> 00:09:28.769 is talking about. That is the utilization. That's 00:09:28.769 --> 00:09:31.789 the mind being active, being sharpened in the 00:09:31.789 --> 00:09:34.009 moment, not postponed. I'm thinking back to high 00:09:34.009 --> 00:09:36.580 school physics now. You know, I could ace the 00:09:36.580 --> 00:09:39.580 tests on conservation of momentum. Formulas, 00:09:39.860 --> 00:09:43.580 definitions, standard problems, no problem. Right. 00:09:43.980 --> 00:09:46.899 But then I remember trying to rig up some simple 00:09:46.899 --> 00:09:49.039 pulley system in my garage to lift something 00:09:49.039 --> 00:09:51.360 heavy. And I just couldn't figure out why it 00:09:51.360 --> 00:09:53.840 wasn't working properly. The classic disconnect. 00:09:53.940 --> 00:09:56.379 Yeah. The knowledge was supposedly there, but 00:09:56.379 --> 00:09:59.840 it felt locked away, stuck in exam mode. Textbook 00:09:59.840 --> 00:10:02.600 knowledge, not usable knowledge. So how do we 00:10:02.600 --> 00:10:05.509 consciously force this process, this combination 00:10:05.509 --> 00:10:08.690 and utilization. What does throwing into fresh 00:10:08.690 --> 00:10:11.210 combinations, as Whitehead put it, actually look 00:10:11.210 --> 00:10:13.269 like day to day? That's the million dollar question, 00:10:13.370 --> 00:10:15.529 isn't it? It's about being proactive. Whitehead's 00:10:15.529 --> 00:10:17.269 solution wasn't about teaching less stuff, but 00:10:17.269 --> 00:10:19.830 teaching it differently. How so? Ensuring that 00:10:19.830 --> 00:10:22.529 relevance, application, combination, these are 00:10:22.529 --> 00:10:25.049 always front and center, not afterthoughts. Okay, 00:10:25.129 --> 00:10:28.470 so for yourself, if you want to avoid creating 00:10:28.470 --> 00:10:31.210 inert knowledge as you learn, You have to deliberately 00:10:31.210 --> 00:10:33.750 build those links. Force the connections yourself. 00:10:33.929 --> 00:10:36.610 Like how? Give me some practical steps. Okay. 00:10:36.870 --> 00:10:39.929 Let's say you're tackling some dense new technical 00:10:39.929 --> 00:10:42.649 concept. Don't just read the manual or watch 00:10:42.649 --> 00:10:44.950 the tutorial video and highlight things. Right. 00:10:44.970 --> 00:10:48.850 Avoid the passive stuff. Instead, step one. Maybe 00:10:48.850 --> 00:10:51.970 try creating a simple flow chart. Show how this 00:10:51.970 --> 00:10:54.789 new concept interacts with, say, three old concepts 00:10:54.789 --> 00:10:57.090 you already feel comfortable with. Force the 00:10:57.090 --> 00:10:59.549 connection. Okay. Visualize the relationships. 00:10:59.919 --> 00:11:03.700 Makes sense. Step two. Try to explain this new 00:11:03.700 --> 00:11:05.620 technical thing to someone who knows nothing 00:11:05.620 --> 00:11:08.320 about your field. Use an analogy. This is sometimes 00:11:08.320 --> 00:11:10.519 called the Feynman technique, or the beginner's 00:11:10.519 --> 00:11:13.240 mind test. If you can't simplify it, you probably 00:11:13.240 --> 00:11:15.240 haven't truly integrated it. Right. Teaching 00:11:15.240 --> 00:11:17.639 forces understanding. What else? Step three. 00:11:18.179 --> 00:11:21.190 Engage in some mental simulation. Imagine a scenario 00:11:21.190 --> 00:11:23.909 where misunderstanding this concept leads to 00:11:23.909 --> 00:11:26.929 a disaster, a project failure, a wrong diagnosis, 00:11:27.090 --> 00:11:30.450 whatever. Then try to mentally debug that failure 00:11:30.450 --> 00:11:33.230 using your understanding of the concept. Ah, 00:11:33.429 --> 00:11:35.669 so you're forcing yourself to apply it, even 00:11:35.669 --> 00:11:38.029 hypothetically, to solve a problem. You're creating 00:11:38.029 --> 00:11:41.009 the fresh combination. Precisely. you're shifting 00:11:41.009 --> 00:11:43.350 the focus from just learning about the thing. 00:11:43.490 --> 00:11:45.750 To learning to do something with the thing. Exactly. 00:11:46.190 --> 00:11:48.309 And that's why Whitehead said that information 00:11:48.309 --> 00:11:50.789 itself, when it's divorced from utility, from 00:11:50.789 --> 00:11:54.590 application, he said it's not a useful concept 00:11:54.590 --> 00:11:57.169 when we consider learning. It really reframes 00:11:57.169 --> 00:11:59.269 everything. It's not about how much raw data 00:11:59.269 --> 00:12:02.740 you can absorb. No. It's about the agility, the 00:12:02.740 --> 00:12:05.320 flexibility, the depth of the connections you 00:12:05.320 --> 00:12:07.600 forge between the pieces of data. The learning 00:12:07.600 --> 00:12:10.240 is the connecting, the combining activity itself. 00:12:10.460 --> 00:12:12.840 That's the heart of it. If the facts you take 00:12:12.840 --> 00:12:16.120 in aren't used immediately to reshape your mental 00:12:16.120 --> 00:12:19.000 landscape, your schemas, they might as well be 00:12:19.000 --> 00:12:21.879 dead storage. They're inert. Okay, let's circle 00:12:21.879 --> 00:12:23.960 back briefly to that challenge I raised earlier. 00:12:24.500 --> 00:12:27.179 The person studying for like the bar exam or 00:12:27.179 --> 00:12:29.720 a big financial regulation test, there's just 00:12:29.720 --> 00:12:32.179 a massive volume of specific facts they have 00:12:32.179 --> 00:12:34.779 to memorize and recall under pressure. Right, 00:12:34.860 --> 00:12:37.179 that's a real constraint. If we take Whitehead's 00:12:37.179 --> 00:12:39.960 critique seriously, how should that person study? 00:12:40.600 --> 00:12:43.759 Should they just not memorize? That seems impossible 00:12:43.759 --> 00:12:45.480 for those kinds of tests. No, no, absolutely 00:12:45.480 --> 00:12:48.019 not. Whitehead isn't saying don't learn the foundations. 00:12:48.799 --> 00:12:50.679 Foundational knowledge, especially in fields 00:12:50.679 --> 00:12:53.600 like law or medicine, often does require significant 00:12:53.600 --> 00:12:56.799 initial memorization. The critical error, Whitehead 00:12:56.799 --> 00:12:59.899 would argue, is stopping there, making memorization 00:12:59.899 --> 00:13:02.759 the end goal. So what's the alternative when 00:13:02.759 --> 00:13:05.720 facing that mountain of facts? You build in the 00:13:05.720 --> 00:13:08.259 utilization step right alongside the memorization. 00:13:08.639 --> 00:13:11.899 So if you're studying, say, two different legal 00:13:11.899 --> 00:13:14.940 statutes for the bar exam, don't just memorize 00:13:14.940 --> 00:13:17.649 Statute A and Statute B separately. What then? 00:13:17.789 --> 00:13:20.370 Force a connection. Create a quick hypothetical 00:13:20.370 --> 00:13:22.769 case study in your head, or even scribble it 00:13:22.769 --> 00:13:25.549 down, where Statute A and Statute B potentially 00:13:25.549 --> 00:13:28.330 conflict. How would you resolve it? Which takes 00:13:28.330 --> 00:13:31.210 precedence. Why? Ah, so you're forcing a fresh 00:13:31.210 --> 00:13:33.669 combination, even with rote material. Exactly. 00:13:33.769 --> 00:13:35.889 You're making your mind do something with the 00:13:35.889 --> 00:13:38.450 facts beyond just storing them. Or, back to the 00:13:38.450 --> 00:13:41.029 Python example, you learn a new function syntax. 00:13:41.279 --> 00:13:44.279 Fine, memorize it, but immediately. Try to use 00:13:44.279 --> 00:13:47.360 it. Yes. Immediately try to weave that new function 00:13:47.360 --> 00:13:49.539 into a tiny project you're already working on. 00:13:49.960 --> 00:13:52.279 Make it interact with a library you learned last 00:13:52.279 --> 00:13:54.980 week. Force it to work together with other pieces. 00:13:55.019 --> 00:13:57.399 You're using the facts to create something, even 00:13:57.399 --> 00:14:00.139 something small, not just recall them on demand. 00:14:00.399 --> 00:14:03.200 Precisely. And that process, that active creation 00:14:03.200 --> 00:14:06.320 and connection, starts transforming that fragile 00:14:06.320 --> 00:14:09.399 temporary retrieval pathway into a more robust 00:14:09.399 --> 00:14:13.190 functional mental model. A schema. Exactly. A 00:14:13.190 --> 00:14:15.850 schema that you can actually deploy more flexibly 00:14:15.850 --> 00:14:18.809 later on in situations you haven't explicitly 00:14:18.809 --> 00:14:21.289 practiced. Because the life of the mind, as Whitehead 00:14:21.289 --> 00:14:23.870 put it, wasn't postponed. It began immediately 00:14:23.870 --> 00:14:26.250 with the activity. You know, the biggest takeaway 00:14:26.250 --> 00:14:29.730 for me here, thinking about this, is realizing 00:14:29.730 --> 00:14:32.330 that feeling we get after consuming a lot of 00:14:32.330 --> 00:14:34.649 information. Yeah, that feeling of accomplishment. 00:14:34.750 --> 00:14:36.750 That satisfaction. Yeah, whew, finished that 00:14:36.750 --> 00:14:39.169 report or got through that whole textbook chapter. 00:14:39.740 --> 00:14:41.960 That feeling can actually be pretty misleading, 00:14:42.220 --> 00:14:44.919 can't it? Very misleading. It often signals passive 00:14:44.919 --> 00:14:48.100 consumption, not active integration. True learning 00:14:48.100 --> 00:14:52.179 seems to require more friction, more struggle, 00:14:52.580 --> 00:14:54.600 forcing the new stuff against what's already 00:14:54.600 --> 00:14:57.220 there until something new clicks or gets built. 00:14:57.539 --> 00:14:59.820 That's a great way to frame it. Friction, struggle, 00:15:00.220 --> 00:15:02.950 active combination. So let's try to summarize 00:15:02.950 --> 00:15:05.350 the core takeaway for you, the listener. OK. 00:15:05.669 --> 00:15:07.990 Successfully retrieving a fact for a specific 00:15:07.990 --> 00:15:11.009 test or just recognizing a term when you hear 00:15:11.009 --> 00:15:14.750 it again. That's the hallmark of static, potentially 00:15:14.750 --> 00:15:18.169 inert knowledge. Static. Not dynamic. Right. 00:15:18.409 --> 00:15:20.889 Useful knowledge, the kind Whitehead advocated 00:15:20.889 --> 00:15:23.669 for, is dynamic. It's resilient. It's the knowledge 00:15:23.669 --> 00:15:26.250 you can actively deploy, synthesize with other 00:15:26.250 --> 00:15:29.129 knowledge, and combine in new ways to solve problems 00:15:29.129 --> 00:15:31.210 you weren't specifically prepared for. Problems 00:15:31.210 --> 00:15:33.330 the original textbook or lecture never even mentioned? 00:15:33.529 --> 00:15:35.610 Exactly. That's the real test. And it implies 00:15:35.610 --> 00:15:37.549 that if you're constantly taking in information, 00:15:37.789 --> 00:15:40.629 articles, meetings, podcasts, courses, whatever, 00:15:41.529 --> 00:15:43.490 the moment you let that information just sit 00:15:43.490 --> 00:15:46.259 there, passively received without immediately 00:15:46.259 --> 00:15:48.899 trying to connect it or use it, you're actually 00:15:48.899 --> 00:15:50.799 slowing yourself down because you're building 00:15:50.799 --> 00:15:55.340 up this this inert knowledge. It's like cognitive 00:15:55.340 --> 00:15:58.519 debt. It takes up space but doesn't contribute 00:15:58.519 --> 00:16:01.149 to future learning or problem solving. That's 00:16:01.149 --> 00:16:03.649 a powerful metaphor, cognitive debt. I like that. 00:16:03.710 --> 00:16:06.029 It makes the next step harder. Which really leads 00:16:06.029 --> 00:16:08.710 us to a final thought, a provocation for you 00:16:08.710 --> 00:16:11.470 to consider as you continue your own deep dive 00:16:11.470 --> 00:16:13.649 into learning and skill building. Okay, let's 00:16:13.649 --> 00:16:16.750 hear it. If you accept Whitehead's premise that 00:16:16.750 --> 00:16:19.950 utilization, testing, combining must happen immediately 00:16:19.950 --> 00:16:22.669 to prevent knowledge from becoming inert, from 00:16:22.669 --> 00:16:25.870 dying on the vine, then what is the very next 00:16:25.870 --> 00:16:28.110 concrete action you will take maybe right after 00:16:28.110 --> 00:16:32.330 this finishes to actively deploy, test, or synthesize 00:16:32.330 --> 00:16:34.850 the last significant piece of information you 00:16:34.850 --> 00:16:36.769 encounter today? Don't just let it sit there. 00:16:37.269 --> 00:16:39.070 Don't let it become inert. Go and activate it 00:16:39.070 --> 00:16:39.509 now.