Last month I set out to learn how to learn faster. Over three weeks I tested three approaches on the same unfamiliar topic and kept notes. The short version is that rereading felt great and taught me least, watching felt productive and taught me a bit more, and explaining the thing to someone else showed me exactly what I did not know. If you want a way to study that holds up, this friendly comparison might save you some trial and error.<\/p>\n
Rereading is the comfort food of studying. You highlight, you underline, you flip back to the first page, and everything looks familiar. That familiarity is the trap. Recognising a sentence when it sits in front of you is a much easier job than producing the idea from nothing, yet the two feel almost identical in the moment.<\/p>\n
What I liked: it is quick, it asks for no courage, and it is easy to squeeze between meetings. What I did not: when I closed the page and tried to say the idea aloud, half of it had gone. I had confused “I have seen this” with “I understand this”.<\/p>\n
Videos and walkthroughs are a real step up because you see a process in motion. I watched a few and enjoyed them. But my brain stayed in passenger mode. I could follow every step, nod, and feel clever, then freeze when asked to repeat a single step without the screen.<\/p>\n
What I liked: it shows the order of things and the small habits that experts never bother to write down. What I did not: there is no friction, and friction is where learning lives. If you do pick this route, pause often and predict the next move before the presenter makes it.<\/p>\n
This was the uncomfortable one, and it won. I took a topic I had half-learned and tried to teach it to a friend who knew nothing about it. Within two minutes I hit a wall. I had used a word I could not define. I had skipped a step because it seemed obvious. I had memorised a rule without knowing why it existed. Every one of those stumbles was a hole in my understanding that the other two methods had politely hidden.<\/p>\n
Better still, the holes were specific. I walked away with a short list of things to go and look up, instead of a vague feeling that I should “study more”. The explanation also forced me to choose examples, and picking an example is a surprisingly demanding test of comprehension. If you cannot produce a single concrete case, you probably hold the rule without the meaning behind it.<\/p>\n
Here is how the three rounds stacked up once I laid my notes next to each other, using the same topic and roughly the same time for each.<\/p>\n
None of these is wrong. The mistake is stopping at the first two and calling it finished. I now treat them as a sequence: skim to get oriented, watch to see the motion, then explain to find out what really stuck.<\/p>\n
Spoken explanations disappear. Writing them down means the next person who is confused in the same place does not have to start from scratch, and it gives you something to correct later when you learn more. My own write-ups are rough, and that is fine; a clear explanation from someone one step ahead is often easier to follow than a polished one from someone twenty steps ahead.<\/p>\n
For a place to put yours, there is a blogging network called MyBlogPad<\/a> that hands each blog its own subdomain, lets people sign in with Google and, by its own description, costs nothing to join. Plenty of other homes exist, so pick whichever you will actually use.<\/p>\n The same idea shows up whenever people talk about learning anything seriously. For students, our walkthrough on finding tutors and degree options<\/a> is a good companion, because even a great tutor works best when you come back and explain the lesson in your own words. And if you are teaching yourself a technical trade, the career-path piece on tech skills and progression<\/a> shows how much of the early ladder is simply being able to describe what you did.<\/p>\n My bet is that the third round will feel clumsy and the most honest. That clumsy feeling is not a sign you are bad at the subject; it is the sound of holes being found while they are still cheap to fix. Share the result, even in a few paragraphs, and a stranger somewhere will thank you for it.<\/p>\n","protected":false},"excerpt":{"rendered":" I tried rereading, watching and explaining on one topic. Only the last showed me what I did not know, and it left something other people could read.<\/p>\n","protected":false},"author":6,"featured_media":1199,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[166],"tags":[],"class_list":["post-1198","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-business-technology"],"_links":{"self":[{"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/posts\/1198","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/comments?post=1198"}],"version-history":[{"count":1,"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/posts\/1198\/revisions"}],"predecessor-version":[{"id":1259,"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/posts\/1198\/revisions\/1259"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/media\/1199"}],"wp:attachment":[{"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/media?parent=1198"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/categories?post=1198"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/bhaso.com\/blog\/wp-json\/wp\/v2\/tags?post=1198"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Where this fits with other things I have read here<\/h2>\n
How to run your own three-round test<\/h2>\n
\n