Happy Friday from freezing cold Amsterdam!
This week I've thought, written, and talked a lot about "attacking" new skills strategically. Revisiting my notes from the book Ultralearning, I noticed how much I've assimilated the concepts. But common sense about learning isn't so common, which is why I'm further deconstructing the skill of learning how to learn.
As in previous weeks, the resources in this newsletter are mostly videos. Wherever possible I've shared my written notes, as well as writing prompts to help you get started planning your next learning project.
Finally, I'm very close to rebranding the site and community to Think Stack Club. Not much will change apart from the name, but I am still looking for a logo designer. If you design logos or know someone who does, please reply to this email. I'm happy to pay well, even if you just connect me to the right person.
For now, on to the resources!
✅ How to plan your next learning project
On Wednesday we had the third workshop in the series of "learning how to learn" sessions. This time we used frameworks from the books Ultralearning and The First 20 Hours to deconstruct, plan, and learn any skill in one month or 20 hours of deliberate practice.
💨 How to learn anything fast
If you're not familiar with the Ultralearning approach, or if you want a refresher on the nine Ultralearning principles, you cannot miss this conversation with Scott Young.
My friend Dominic Zijlstra interviewed Scott to talk about the principles of metalearning, directness, focus, drills, retrieval, feedback, retention, intuition, and experimentation. Learn to apply these principles, and you can slash the time of acquiring a skill by 75%.
📝 Using Logseq to learn from technical notes
In the video below, Bryan Jenks shows how he collects questions about programming languages, learns about them, and then processes his notes for easy reference. This workflow also works perfectly in Roam, as it leans on the Daily Notes Page for entry, TODOs for review, and linked references for the inbox.
🧑🍳 An analogy of cooking and knowledge work
Ever since I've read Tiago Forte's article on mise-en-place for knowledge workers, I've been obsessed with the analogy. The more I learn about cooking, the more I see the relation to thinking for a living.
That's why I like Jeffrey Webber's system so much. He treats information like food that goes through the stages of being on the menu, getting ordered, and finally getting prepared through different steps. Jeffrey uses Roam to prepare knowledge and serves the final "dish" to his future self in Obsidian.
💬 Roam-esque comments in Logseq
Let's end this week's newsletter with a nifty plugin for Logseq. It's been about two months since I've started to gradually transfer my workflows from Roam to Logseq, and I'm stunned by the development speed of both the Logseq team and plugin enthusiasts.
If you rely on block references to take notes on your highlights (or other notes), you were already in good hands with Logseq. But now the handy block comments feature from Roam has been ported over by plugin developer Richard Yu. With it, you can easily create a comments history for individual blocks.
Click here for installation instructions. Want to see how it works first? Watch the 3-minute demo below.