Live data from Hacker News

How to Learn Efficiently

lemire.me

21–30 of 72 posts

Re: How to Learn Efficiently

#21

> As an undergraduate student, I found that writing a summary of everything I had learned in a class was one of the best ways to study for an exam. I would just sit down with a blank piece of paper and try to summarize everything as precisely as possible. Ultimately, writing your own textbook would be a very effective way to learn the material. Amen. Back when I was tutoring a lot, I used to ask the students to keep…

Taking good notes on paper is lost art.

In college, I returned a textbook before I opened the shrink wrap when I realized the student next to me was highlighting verbatim from the textbook what the professor was talking about. Writing everything down saved me >$100 and earned me an easy A.

Re: How to Learn Efficiently

#22
post #2

Any thoughts on learning to code in an 'interleaved' manner? I.e. studying more than one language or concept at once?

My current quest is to take something from the business domain I work in and implement the bizarre math stuff (which I don't get all of) in a backend in F# with a frontend in Javascript (I'm fluent in neither). I've tried it before (with different technologies), and although it didn't make me an expert in either field, I've found it neatly ties most things together. Oh, and it's usually fun, especially if you put som…

If your goal is to learn those two languages, I'd instead pick a problem/domain you understand very well and then express the various aspects of that problem in both F# and JavaScript rather than implementing some aspects in F# and some aspects in JavaScript.

This will help you develop a better sense of how F# and JavaScript differ as languages, what ideas are natural in one but unnatural in another, the conventions and idioms around tackling certain problems, and so on.

Re: How to Learn Efficiently

#23
post #22

Earlier quoted context omitted.

My current quest is to take something from the business domain I work in and implement the bizarre math stuff (which I don't get all of) in a backend in F# with a frontend in Javascript (I'm fluent in neither). I've tried it before (with different technologies), and although it didn't make me an expert in either field, I've found it neatly ties most things together. Oh, and it's usually fun, especially if you put som…

If your goal is to learn those two languages, I'd instead pick a problem/domain you understand very well and then express the various aspects of that problem in both F# and JavaScript rather than implementing some aspects in F# and some aspects in JavaScript. This will help you develop a better sense of how F# and JavaScript differ as languages, what ideas are natural in one but unnatural in another, the conventions…

I once worked with an engineer who implemented the card game hearts in every language he learned. After the first implementation, you don't have to spend so much time thinking about the problem domain and can focus on finding the most idiomatic solution in the new language. The other benefit is that the project always has a clear endpoint.

Re: How to Learn Efficiently

#24

The Learning Style theory is junk with the flimsiest evidence, but tell that to any teaching institute in this arena so obsessed with constructivist ideals. The reason I did not continue on to teach physics was partially due to an insistence that it was teachers who needed to expend more effort to make classes "fit" a student's preferences so that their learning would be a gradual climb. You learn material by flailin…

Beep beep. Back the truck up.

I am a dyed-in-the-wool constructivist and I think the theory of "Learning Styles" as it's used today is rubbish. It's a mistake to think they're attached at the hip.

By "the theory of Learning Styles", I specifically mean the idea that some people are "auditory learners", "visual learners", "kinesthetic learners", etc. and that part of a teacher's job is to figure out which "learning style" best fits a given student and present them material in a manner consistent with that style.

I'll add that in the "literature" these things are called "learning modalities" and "learning style" refers to something else, but I've never heard someone use "learning style" and not mean learning modality.

It's also ironic that you use the phrase "constructivist ideals."

Constructivism has deep roots in the American philosophical tradition of Pragmatism[1]. C.S. Peirce coined the term "pragmatism" to contrast _specifically_ with the Kant's transcendental idealism. One of it's core epistemological tenets is that the only thing we can be sure of is that certainty is impossible.

In _The Quest for Certainty_[2], JohnDewey himself called out the "fallacy" of philosophers in taking abstract categories (e.g., "Visual Learners") for granted and not seeing them as conceptual tools invented to solve specific problems in a specific context.

Like you, I find it frustrating that many educational thinkers take these concepts for granted and deploy them in a classroom environment as if it would be absurd to ever do anything else. However, if you read any early Pragmatist thinkers like Oliver Wendell Holmes, Jr., C.S. Peirce, William James, or John Dewey, it's clear that rejection of this maneuver is one of the central themes in everything they write.

    [1]: http://en.wikipedia.org/wiki/Pragmatism

    [2]: https://archive.org/details/questforcertaint032529mbp

Re: How to Learn Efficiently

#25

Earlier quoted context omitted.

"Drive" by Dan Pink sort of talks about that. Your purpose should be something that you provide, not external factors, like grades and fears from what comes from them.

It's entirely possible to be internally driven and to still not function well in a school. (Unless you think the only purpose students should pursue is "succeeding in school".)

I think my story is a decent anecdote to support your statement. I spent half of college on academic probation with the main contribution to my terrible GPA being default failing status from skipping too much class.

I dropped out of school, got a job that was supposed to teach me something. It turned into answering the phone, but I used that time and title to land a Jr. software dev position and within just a few months I was being assigned solo projects and completing them ahead of schedule because I actually enjoyed learning the material outside of a structured environment.

I'm not a genius. I'd bet I'm not even that special. I think many people are just too conditioned to follow the wide beaten path, that even when they see a more appealing path they are scared to take it, and no one is actually encouraging them to take that path.

Re: How to Learn Efficiently

#26
post #6

Reading this, I couldn't help but draw the parallel with body building. The pain means new muscle is filling the micro-tears made during effort, and you train an other group the next day while the one you did today recovers.

Day 1: Raw DOM manipulation with jQuery to fill it with micro-tears. Day 2: D3.js/Socket.io to work the untouched parts of the DOM with different micro-tears. Day 3: Profit.

Re: How to Learn Efficiently

#27
> Interleaved practice feels much harder (e.g., “you feel confused”), and it feels discouraging because progress appears to be slow. However, this confusion you feel… that is your brain learning.

I'm sorry to be a grouch, but is this based on any scientific evidence or just the OP's opinion?

Re: How to Learn Efficiently

#28
There is a coursera course called "Learning How to Learn"[1] by Barbara Oakley that is starting soon. I took the previous session and it was very interesting. I liked the science[2] behind each part of the course (procrastination, memory, modes of thinking etc). The weekly interviews were certainly a big plus (however they were usually long at ~40 minutes).

It's a fun four week course with very little work and I recommend it.

[1] https://www.coursera.org/course/learning

[2] After each lecture there was a list of references to check out for more info.

Re: How to Learn Efficiently

#29
Something my high school Computer Science teacher told me was that I wasn't learning effectively if I didn't have to try to understand something at least three times before it clicked.

Roughly 15 years later, I've found his advice to at least smell true.

Stated more generally, learning is to some significant extent about gaining understanding[1]. When you don't understand something, it is confusing.

In my experience, if you are not experiencing confusion -- more specifically the removal of confusion through effort of some sort --the "learning" you are participating in would more accurately be called memorization..

[1] at least in this context

Re: How to Learn Efficiently

#30
I've found that the things I taught to others are the things that I learned the most completely. Not sure if it is the most efficient way but having to explain it to someone else always seemed to crystalize the details for me.
Post reply on HN