{
"path": "/posts/2024/learning-how-to-learn",
"site": "at://did:plc:mracrip6qu3vw46nbewg44sm/site.standard.publication/self",
"tags": [
"learning",
"productivity",
"coursera"
],
"$type": "site.standard.document",
"title": "Learning How to Learn",
"updatedAt": "2024-06-13T19:42:38.000Z",
"publishedAt": "2024-06-13T19:42:38.000Z",
"textContent": "I completed Barbara Oakley's \"Learning How to Learn\" course on Coursera.\nThe target audience seems to be students, but I found there were helpful takeaways for me as well, as someone who is a decade out of my last university classroom.\n\nThe course introduces a mental model (no pun intended) for how the brain works by contrasting two modes: focus mode and diffuse mode.\nBeing in one of these modes prevents you from being in the other.\nFor me, it helped provide some insight into why at some times things like coding, being creative, and writing can be more difficult than others.\n\nThe course also provided corroborating evidence for a few approaches to getting \"unstuck\" that I've learned after a lot of trial and error.\nIf I get stuck on a problem, my first intuition is often to spend more time and energy trying to solve it.\nWhat often happens is as soon as I step away from the problem, whether it be doing something else or taking a break, a novel approach comes to me that helps me get unstuck.\nThe course explains this phenomenon through the brain's fluctuations between the focused and diffuse modes of the brain.\n\nBecause it's somewhat focused on students, there is some content on test-taking tips.\nThe most salient tip in the course about test-taking is to read the hardest problem first, then go back and do the easier ones.\nIt is quite literally like a background thread in your brain starts thinking about that problem while you answer the other easier questions.\nOnce you get to the hard question, you have all this useful context readily available and maybe even some insight into how to tackle the issue.\n\nThis approach seems to work with many things.\nIf I am writing a technical design document for a system, I look at the most complex question I have to answer, then start writing the more straightforward parts of the document, returning to the more complex parts later, in a primed state.\n\nAt a high level, I found this course useful for thinking about how to operate my brain more effectively and make better use of my time.\nGetting stuck on a hard (or even silly) problem is inevitable.\nWhat matters far more is how you respond to getting stuck.\nSpending a lot of energy and effort to push through can eventually yield results, but being aware that this is not necessarily the fastest approach is important if you want to do the best job you can do.\n\nIt's a far better outcome to work for 30 minutes, take a 10-minute walk, then work for 30 more minutes than to work nonstop for 70 minutes, even if it results in the same work product.\nWhen I take the latter approach, my energy gets drained.\nWhen I take breaks or put intentional space between work sessions, I find I am eager to get back to the task because I have new ideas for things to try that I came up with in the interim.\n\nThe brain doesn't come with an instruction manual.\nI find knowledge like this empowering and it makes life more enjoyable.",
"canonicalUrl": "https://www.danielcorin.com/posts/2024/learning-how-to-learn"
}