Should You Try Learning More Than One Thing at a Time?

How many different subjects should you try to learn at once? It’s obviously not impossible to learn more than one thing at a time—in school you often have to learn many different subjects simultaneously. Is there a compelling reason to stick to learning only one thing? Or will you learn more if you try to learn different things concurrently?

I don’t think there’s a clear-cut answer to this question, but it is one I’ve given a lot of thought. In this essay, I’ll try to explain what I think the compelling reasons are for learning things one at a time and in parallel, and then suggest some different strategies that cope with both.

The Case for Focused Learning

The case for focused learning, in my mind, doesn’t really have much to do with learning at all. Instead, I see the benefits of focusing on a single learning project as the same benefits for doing a limited number of any kinds of projects—learning, self-improvement, work, etc.—simultaneously.

Working on a project that you’ve planned yourself is complicated. You have to organize your efforts over many days or weeks to get it done. You need to juggle it with your background responsibilities of work and home. For self-started projects, it’s very easy for them to fade into the backburner of non-urgent tasks.

Having more projects increases this mental overhead, and makes coordinating your efforts on completing them much more complicated. Have one project? Easy, just work on it when you have time in your schedule. Have six projects? Just figuring out which you should work on can be a chore, nevermind doing the actual work.

Another pattern I’ve noticed when dealing with multiple projects is that we tend to push them forward when that’s easy to do. Unfortunately, learning new things is often very frustrating. So precisely when we need to be applying more effort to get over those humps is when we pull back.

By focusing your learning, it’s easier to push forward even when projects get difficult because you’ve committed yourself to not working on something else until you complete it.

Although the MIT Challenge certainly could have been set up as a side activity pursued over a decade, it’s not clear to me I would have pushed through some of the hardest times if there were other, easier, goals in competition for my attention.

The simple case for focused learning is the same reason you focus with anything—to avoid crowding out your attention with things that are easier to to, but less important.

The Case for Parallel Learning Goals

Despite the advantages of focusing for getting projects finished, there are a number of compelling reasons from cognitive psychology to at least consider running learning goals in parallel.

The first is the spacing effect. The evidence here is very robust: we learn things better when we don’t cram it into a short period of time. Learning something spread over multiple days will produce longer, stronger memories, than learning something over a long burst on one day.

The reasons for this are not entirely understood yet. One of the reasons might be because of memory consolidation. That cramming too many repetitions of an concept in a single studying session may only result in a single act of consolidation, so the extra repetitions are wasteful. Another reason might be because learning is stronger when you’re switching frames or contexts—having to “boot” the information, so to speak, makes the memory more robust than thinking about it when you’ve just been thinking about it recently.

The spacing effect definitely strikes a blow against intense projects like the MIT Challenge. Although I did work to mitigate these problems later on, by running multiple classes in parallel, I doubt I was as successful as I could have been having learned over a longer timeframe.

Another, somewhat less robust effect is called interleaving. This is where you switch between different subjects to increase your amount learned. So in one day you’d study a bit of biology, chemistry, physics and philosophy, instead of splitting them up.

Interleaving may work by the same principle of spacing—that switching frames improves learning, or it may work from an entirely different mechanism. While spacing argues indirectly for parallel learning goals, interleaving argues for it quite directly.

The simple case for parallel learning goals is that you might learn more efficiently if you spread your studying out and switch between learning tasks.

What Should You Do? Examining Learning Structures

A learning structure is what I call an overall strategy to learning something. One of these structures I’ve already mentioned—setting up a project. A project structure involves commitment, planning and usually few or zero other competing projects.

However, that’s not the only way to learn things and there are other structures that also work. A habitual structure works by making the studying activity a habit—something you do regularly every week consistently. With a habitual structure you can manage a lot more learning goals in parallel.

A third structure, might be a casual structure—where you learn something when you have interest in it. This requires the least organization and is the default structure for most people, but sometimes it’s a good one to use if your interest is high, frustration is low and you want to minimize the stress of learning.

So how do you decide whether to learn via a project, habits or more casually? I use all three in my own learning efforts. The question to me is simply which aligns best with your goals and how do you offset its weaknesses.

Project Structure: Strengths and Weaknesses

The strength of the project structure is that it maximizes focus. This means it’s far easier to work on learning projects that are particularly difficult, frustrating or intense. It’s also easier to make progress in a timely fashion. While habits and casual structures are in it for the long haul, a project can make progress quickly which might be nice if you have some deadline (say an exam or job interview) when you want the skill to be ready before.

The weakness of projects is that you can’t do too many at once, maybe no more than one. This means you have to be selective about what you intend to learn (not always a bad thing), and you can’t benefit as much from spacing or interleaving as you might with another structure.

I’ve found there’s a couple ways to mitigate these weaknesses while still sticking with the project structure:

  1. Use short projects. If you rotate between shorter projects, you can make progress on multiple goals over a longer period of time. The Year Without English used a project structure, but we ended up learning four languages in one year, quite a diverse set of goals.
  2. Use within-project spacing and interleaving. This means doing spaced review of things you’ve already learned within the project and switching between subtopics to study. I partially used this during the MIT Challenge and it offset some of the effects of cramming.
  3. Follow up a project with habits. A project can get you a lot of distance with a learning goal particularly fast. Once you’re done, however, you might want to switch to a habit structure to maintain what you’ve learned. That way you can get benefits from spacing in holding the knowledge in place.

Habitual Structure: Strengths and Weaknesses

The strength of a habitual structure is that you can get the increased efficiency due to spacing and interleaving, and you can learn multiple things simultaneously. Habits also force you to be patient with learning new skills, which can alleviate frustration by switching the task from being results-oriented to process-oriented.

The big weakness of habits is that if you hit large bouts of frustration or complexity, they can get completely derailed. Anyone who has been on vacation for awhile and seen their exercising habit fall apart can attest to that.

My reason for not using this structure exclusively is that sometimes there are learning goals which are too difficult or frustrating to make for smooth habits. You might be able to do flashcard review as a habit, but speaking a new language for the first time is often so frustrating it doesn’t benefit well from only receiving a fraction of your attention. Similarly, doing hard calculus problems isn’t something you relish jumping into when you’ve never done it before.

Here’s some thoughts on mitigating these weaknesses while still sticking to a habitual structure:

  1. Identify rough patches and reinforce those spots. This means when you know something will be frustrating, you give it your priority for a certain period of time and then lay off again when things get easier. This requires some intuition, but it effectively temporarily turns your habit into a project and then releases it when you can learn more smoothly again.
  2. Focus on input not results. If your habits are set around investing a particular amount of time doing a particular learning activity, regardless of how much progress you make, this can reduce some of the frustration.
  3. Run a mini-project to make strides through rough patches. This was what I did with my Portrait Drawing Challenge. I have been working on art as a casual learning process for over a year, but faces were giving me a lot of frustration and I wanted to improve them, so I switched gears temporarily. Now I’m back to the casual approach again.

Casual Structure: Strengths and Weaknesses

The strength of a casual structure is that it doesn’t require much willpower. You just let your interest level decide what you want to learn. This means you can learn many things at the same time.

The downside is that your progress will be heavily dependent on your motivation and can be easily derailed by frustrations. If your interest is really high and the subject is relatively smooth, then this might not be an issue.

I hesitate to talk about this structure because it’s a default approach for so many people. But that doesn’t mean you should avoid it completely. I’m making slow but steady progress on my cognitive science challenge, treating it mostly as a casual learning activity. The reason is that reading books is fairly enjoyable, and if a book gets too dense or boring, I switch books to keep my interest engaged.

Seeing as the casual approach to learning works when interest is greater than frustration, the key to avoiding its weaknesses is to note when this is no longer the case. If you start feeling like learning is a chore, you may want to either suspend learning that subject for a while or switch it to a project to push past the obstacle.

Casual learning also suffers because there isn’t an explicit set of priorities. While things that are more important tend to become more interesting, this isn’t always the case. So a casual approach sometimes has you learning more interesting things at the expense of more important things. Again, the solution here is to recognize when this is happening and switch to a more rigorous structure as needed.

Conclusion

Unfortunately I can’t offer an easy conclusion that learning should always be done with focus or in parallel. Instead, I think these are both valid strategies which work well in different cases for different goals.

Think about what you’re trying to learn right now. Are you trying to learn something important that is difficult enough to require focus? Try a project. Or are you trying to learn multiple things out of interest but often forget to work on them? Try establishing them as habits. Of course some things will inevitably just be learned casually, and perhaps that’s how they should remain!

Write in the comments what things you’re trying to learn right now and make a decision about whether you want to focus on them as a project, habits or just learn them casually. It’s okay to admit that something you want to learn requires a project but you can’t pursue it right now. At least being aware of that can bring the situation into clarity.


How Should I Learn Cognitive Science?

My usual approach on this blog is to write about a strategy once I’ve already got it working. This time, I thought it would be interesting to instead focus on a current learning challenge I have, and my thinking process about resolving it.

One of the big learning challenges I’m working on right now is to learn cognitive science. Here’s a quick summary:

  1. Cognitive science is a multidisciplinary field crossing psychology, neuroscience, computer science, linguistics and philosophy, all using different tools to answer the question of how the mind works.
  2. My current benchmark for the curriculum is UC San Diego’s reading list for their incoming doctoral students with backgrounds in other fields. This consists of about 40 textbooks.
  3. My first goal is to read these textbooks, but I’ve also studied from outside this list when appropriate. For instance, when struggling with a Neurobiology textbook, I did Duke’s Medical Neuroscience class via Coursera first.
  4. So far I’ve completed about eight of the textbooks, with another few partially completed.

The challenge is still early on, and since I’ve opted to not make this one heavily time-constrained, I’m still figuring out what’s the best way to learn as I go.

How Do You Practice a Theoretical Subject?

One of the key ingredients of all of my other ultralearning projects was practice. The MIT Challenge had tough final exams. The Year Without English had immersive conversation practice. My Portrait Drawing Challenge was almost entirely practicing drawing.

Part of the reason for practice is simply as a way to test yourself. If I hadn’t done the final exams for MIT, my confidence as to how well I had learned the material would be pretty low. After all, it’s certainly possible to watch a lot of lectures or read a book and not be able to use the knowledge.

However, verifying your ability is only a small part of the benefit of practice. Doing practice is actually a much better way to learn the material. Exams didn’t just confirm I knew the MIT material, it was how I actually learned it.

Practice, therefore, is a crucial ingredient to learning well. But how do I practice cognitive science?

This has been a tricky problem because my curriculum is fundamentally a reading list, not classes. So there are no exams, assignments or projects. The nature of the material also makes practice difficult. While reading a programming textbook might not require practice, it will suggest some possible projects after. But what practice does a neuroscience textbook suggest?

I’d like to share some of what I’ve been trying to cope with this problem, discuss the strengths and weaknesses, and share some of my future attempts to resolve this problem going forward.

#1. Writing Book Summaries

My first attempt was an effort of least resistance—writing book summaries. After I finished a book, I would write a 1000-2000 word article, summarizing the contents of the book. I’ve done this for most of the books I’ve completed so far. I usually go chapter-by-chapter to prevent skipping.

The advantage of this approach is that it is quite easy to do, maybe an hour of work for a book that took 10+ hours to read. It also provides notes for the book, so you can later review a condensed version. Finally, summarizing forces me to think about what the big ideas were and organize my thinking.

Despite this, there’s some clear disadvantages to this approach. Importantly, a lot of depth is sacrificed in a review. Taking 600+ pages of tersely written description into 2-3 pages of summary means I’m simply dumping 99% of the information provided.
Because there’s no exact criteria of what I need to include, this compression also allows me to be selective in what I write, meaning I can write about the things I understood well and avoid those I didn’t.

The book summary approach also doesn’t practice any technical skill. So if I’m reading a book on natural language processing, I have zero experience working with any of those systems. If I’m reading a book about Boltzmann machines, I’ve never used any of the equations. I know from doing the MIT Challenge, that this kind of practice was more than half of the actual learning experience, and it’s being entirely omitted by just summarizing.

#2. Taking Question & Answer Notes While Reading

Something I attempted for one book was to take notes which were in question-form, with a note to the page number in the book. My idea was that this would mean reading created its own practice questions later.

The advantage of this approach, versus just taking notes, was that when reviewing them, I could do active recall instead of passive review.

The problem, which I hadn’t anticipated using this technique, was that I tended to write very difficult questions that referenced an obscure detail of the chapter. Rather than focus on what were the big ideas, I got caught up quizzing myself on some obscure facts or opinions of the authors.

This led to the questions being almost entirely unanswerable, and reviewing them again, I felt they didn’t capture the spirit of what I was trying to learn from the book.

#3. Teaching Selected Lessons and Recording Them

Later, I tried flipping the problem around. Maybe, if my main goal was to understand cognitive science well enough to write about it intelligently, then I shouldn’t be focused on practice questions but on teaching. I could teach selected lessons from each book and that would ensure I understood it.

The advantage of this approach is it does foster a deep understanding of what you’ve covered. The downside is that it is incredibly time consuming and covers far, far less than the looser book summary approach.

I still think this method could work well if the book were about arguing a single thesis. However, most of the books I’m reading are surveying large literatures, so teaching specific lessons is going to omit almost everything else.

For my first attempt with this method, I took the book Human Memory by Alan Baddeley, and figured I would do a 5-minute lesson on some of the chapters (there were over a dozen). By the end, my recorded lesson was 20+ minutes and covered only briefly the first part of just one chapter.

What Should I Do Instead?

As I mentioned in the beginning, I still haven’t resolved this challenge. But here are some further experiments I’ve been thinking about to get at solving this issue of practice:

#1. Post-reading Question Book

I’m beginning to suspect my failure with writing my notes as questions came because it’s difficult to think of intelligent questions while also managing the cognitive demands of reading a book. Given more time and space, I might be able to create a list of questions after reading that capture what stood out to me as the important points.

The idea here would be that, after reading, I would create 25-50 questions for each book, as well as my own answer at the time. I could then keep two electronic files (one with just the questions, one with questions and answers) and randomly quiz myself on these later.

#2. Supplementary Classes

It may just be that books aren’t going to cut it for some topics. So I may need to actually find classes (either MOOCs, OCW, or just begged/borrowed real class materials) that will have included practice components.

I’ve already done this with Neurobiology, taking Medical Neuroscience and passing the exams, made a huge difference in how much I was able to understand and retain from that class. Perhaps I’ll just do this for all of the topics I want to explore more deeply.

Although this is a completely valid solution, it also strikes me as a bit of a cop-out. Why read the books at all if you’re just going to take classes on them later?

#3. Personal Project

Another alternative might be to read the materials and accept, at least for the moment, the insufficiency of my understanding. But, once the reading is done (or nearing completion) switch to working on an implementation project. The project would force me to go back and assemble knowledge I’d previously learned in a richer way.

Examples could include: attempting to write/publish a journal article on the topic, designing some kind of computer model to simulate some of the work or recording a set of lectures around key themes of cognitive science.

This approach appeals to me as well, but I don’t like the idea of delaying practice so far into the project.

What Would You Do?

I didn’t bring this up simply to show that I, too, suffer from learning challenges. Instead, I wanted to showcase my thinking about these difficulties. Having done big, mostly successful self-education projects, I’m acutely aware of what needs to be done to make them work.

I suspect that many people would look at my reading list and not see a problem at all. Heck, just reading all those books is going to be challenging enough, why worry about additional practice on top of it?

But I suppose that’s also what motivates me to improve my understanding of how learning works. I’m always eager to try exploring what might be the deficits of my current approach and see if there are ways they can be overcome.


AS SEEN IN