Podcasts about Zettelkasten

Welcome to a new season of Holy Wild Birth, which also represents a revitalization and recommitment to this podcasting project.In this casual conversation with Brooke and Lauren, you'll hear all about what we have in store for you! One of those things is this new "genre" of episode where we offer you our "Cup of Tea" and simply jabber about things going on for us or of interest to us. In this inaugural "cup of tea" episode, we chat about:That we aren't actually drinking teaOur branding photo failsHow cool it is to have teenagersRelationship to lightBrooke's milestone birthing and Lauren's anticipated milestone birthdayDark ParksRemodeling the prenatal roomGrowing community around the podcastQuitting social mediaA way of organizing informationand more!Mentioned in this episode:Lore Wilbert social media challenge — Let's Opt Out of Social Media TogetherZettlekasten - What's a Zettelkasten?Lauren's Prenatal Room Pinterest Collage - My prenatal room | Room, Save, PrenatalStolen Focus - Stolen Focus: Why You Can't Pay Attention--and How to Think Deeply AgainLauren's glasses - VivaRays - Eco-friendly Blue light blocking glasses.Brooke's newsletter - All The Birthy ThingsPodcast about relationship to light The Lie of 9 to 5: Fixing Your Circadian Rhythm | Thaddeus OwenMighty Networks Community Rooted in Eden PMA______________Connect:• Email us to say hi: holywildbirth@gmail.com• Apply to share your birth story on the podcast: Holy Wild Birth Podcast Guest Application • Become a holy, wild birthkeeper with us in the Hearthmother JourneyFrom Lauren:• Midwifery consultations: Email rootedinedenpma@gmail.comFrom Brooke:• Courses for homebirth/freebirth mamas• NewsletterIntro and Outra Music Credit -Betty Dear By Blue Dot Sessions is licensed under a Creative Commons License.

Alexandre Dana est le fondateur de LiveMentor, une plateforme de formation qui accompagne les entrepreneurs dans leurs projets, mais aussi éditeur, auteur, et penseur d'un monde plus attentif, plus conscient. Il vient tout juste de lancer un Carnet de curiosité, un objet qui m'a beaucoup parlé, car il entre en résonance directe avec ce que je cherche à faire avec ce podcast : approfondir, comprendre, ralentir.Dans cet épisode, j'ai eu le plaisir de recevoir Alexandre pour une conversation à la fois intime, dense et passionnée sur la place de la curiosité dans nos vies. Nous avons parlé de ce besoin vital d'explorer le monde, de ce que ça veut dire aujourd'hui d'être curieux à l'ère des contenus courts, des vidéos en boucle, des algorithmes qui nous enferment. Et surtout, comment reprendre la main. Comment ne pas se laisser happer par les feeds infinis et retrouver le goût du temps long.Alexandre m'a partagé la genèse de son carnet, ses influences (notamment le sociologue Niklas Luhmann avec sa méthode Zettelkasten), et son chemin personnel pour passer de la dispersion à la structuration. Il croit, comme moi, que notre attention est précieuse. Et que le papier est une arme puissante pour mieux apprendre, mieux penser, mieux vivre.J'ai aimé sa manière de voir la curiosité comme une boussole intérieure, mais aussi comme une résistance. Résistance à l'instantané, à l'hyper-spécialisation, à la perte de sens. On a aussi parlé d'éducation, de système scolaire, d'hyperconnexion, de fatigue numérique, de burn-out, de la joie de découvrir de nouveaux mondes, et même de confiance en soi.Si vous êtes du genre à collectionner les newsletters, à ouvrir 10 onglets sans les lire, à dire « j'aimerais prendre plus de temps pour lire mais je n'y arrive pas », alors cet épisode est pour vous. Il vous parlera, vous remuera peut-être, mais vous donnera surtout envie de sortir un carnet, un stylo… et de recommencer à penser vraiment.Citations marquantes« La vraie curiosité, celle qui devient une maîtrise, elle prend du temps. »« Prendre des notes sur papier, c'est déjà faire un premier pas vers la structuration. »« On ne résume pas la physique quantique en trois minutes. »« L'attention est devenue un acte de rébellion. »« La curiosité est peut-être le meilleur remède contre la peur de mourir. »10 questions posées dans l'interviewPourquoi as-tu décidé de créer un carnet de curiosité ?Quel est ton rapport personnel à la curiosité ?Comment as-tu pensé la structure de ton carnet ?En quoi le papier est-il une solution face à la fatigue numérique ?Comment structurer sa pensée à travers la prise de notes ?Pourquoi notre attention est-elle aujourd'hui en danger ?Quel est l'impact des algorithmes sur notre curiosité ?Comment retrouver une curiosité active et profonde ?Y a-t-il des contre-indications à la curiosité ?Comment choisir les sujets à creuser réellement ?Timestamps clés (format YouTube)00:00 Introduction et présentation d'Alexandre Dana02:00 Pourquoi la curiosité est essentielle04:00 La genèse du carnet de curiosité07:00 L'importance du papier dans l'apprentissage09:00 Le combat contre les contenus courts et la dopamine14:00 Structurer sa pensée avec la prise de notes20:00 Le concept de polymath et la pensée divergente25:00 Algorithmes, filtres et perte de curiosité32:00 Par où commencer pour ralentir40:00 Les différents usages du carnet de curiosité49:00 Curiosité, frustration et confiance en soi Suggestion d'autres épisodes à écouter : #295 Les étapes de la rencontre avec soi avec Anne Ghesquière (https://audmns.com/FBVhPXW) #206 Comment développer l'esprit critique chez les enfants? Avec Samah Karaki (https://audmns.com/dFSogCP) #230 Comment se connecter à son intelligence situationnelle? Avec Guila Clara Kessous (https://audmns.com/bLRrqSQ)Distribué par Audiomeans. Visitez audiomeans.fr/politique-de-confidentialite pour plus d'informations.

The Magic Mind team created a super offer for me to share with you guys.Get 45% off the Magic Mind bundle with with my link: https://www.magicmind.com/ERICJAN01:06 Chapter 1. Understanding the Structure of Learning.05:06 Chapter 2: Know How to Read Intelligently09:07 Chapter 3. Sharpening Your Memory13:07 Chapter 4. Be Strategic. Stay Organized.17:07 Chapter 5, Mastering MindsetBecome a Studying and Learning Machine: Strategies For the Top of the Class, Promotions, and Smashing Your Goals By Peter HollinsAre you ready to take your learning and studying game to the next level? Look no further than "Become a Studying and Learning Machine - Strategies For the Top of the Class" by Peter Hollins. In this episode, we dive deep into the strategies outlined in Book 27, exploring topics such as the STIC framework, scaffolding content, and the power of play in learning.Hear it Here - adbl.co/4hqQa5qWe'll also discuss how to use successive relearning, REAP methods for effective reading, smart highlighting techniques, and more. Peter Hollins shares his insights on mastering your memory with methods like Blurting and Memory Anchors, helping you stay organized with Zettelkasten and creating a skill tree. We'll even touch upon the importance of mindset and different thinking modes - focused or diffuse.This book and podcast episode will equip you with the knowledge to become a true learning machine. By implementing these strategies, you can expect to see improvements in your productivity, personal growth, and ultimately, your success across all areas of life.Don't miss out on this opportunity to revolutionize your studying habits and achieve your goals faster than ever before. Get your copy of "Become a Studying and Learning Machine" by Peter Hollins today and start your journey towards becoming the top student in your class or field.The best students, the top performers, the quickest learners - it's not by luck. They know what they're doing, and you can be like them too.We've never been taught how to learn. Yet learning is the keystone to any goal you want to achieve. Let's start changing your life with this very book.A learning structure and framework that takes you from A-Z, in what to do and how to approach it.STUDYING AND LEARNING MACHINE takes you on a psychological and physiological journey of your brain and how to work with it best. What your brain likes and hates - that will 1000% impact how quickly and effectively you learn. The more you learn, the more you earn! So let's go on this journey together of how to maximize your time, money, and life path!Master your approach and save countless hours.Peter Hollins has studied psychology and peak human performance for over a dozen years and is a bestselling author. He has worked with a multitude of individuals to unlock their potential and path towards success. His writing draws on his academic, coaching, and research experience.Smarter, faster, and better ways to achieve expertise.-What Descartes had to say about effective reading and retention-How to 'scaffold' content that you read for better memorization-The STIC framework and how it makes your brain want to help you learn better-Understanding various types of thinking modes and when to use each one-Play - how it helps learning and how you can speed up your learning 2x-How to climb a 'skill tree' to keep your progress efficient and effective

Du willst endlich dein eigenes Buch schreiben, Online Kurse veröffentlichen, oder zumindest einen Blog starten, doch irgendwie kommst du einfach nicht voran, sitzt vor dem blinkenden Cursor und hast eine Schreib-Blockade. Die Ursache ist nicht deine mangelnde Intelligenz oder der viel zitierte Schweinehund, der wahre Grund sind die Notizen, die du dir machst, wenn du Wissen aufnimmst! Denn dort entstehen die Fehler, die dich dann später nicht produktiv sein lassen. Notizen sind Nachrichten an dein zukünftiges Selbst und daher ist es wichtig, wie du diese schreibst. Ein revolutionäres System, das aber eigentlich schon hunderte Jahre alt ist, ist es einen sogenannten Zettelkasten anzulegen. Das klingt vom Namen her verstaubt, findet aber auf einer sensationellen Software statt, die zudem kostenlos ist! Auf diese Art und Weise richtest du dir ein Zweites Gehirn ein! Seit 2 Jahren führe ich einen solchen Zettelkasten - und der ist lange nicht so verstaubt, wie der Name vermuten lässt! Er ist auf einer genialen Software, die genauso funktioniert, wie unser Gehirn! Diese Info kann deine Art zu denken komplett revolutionieren! Mehr dazu erfährst du in der aktuellen Folge! Über meine Produktivität kann ich mich jedenfalls nicht beklagen:​​​​​​​​​​​​​​​​​​​​​​ ​​137 erstellte Online Kurse 4 Bücher (alle vielfache Amazon Bestseller) über 300 Podcast Folgen über 500 Blog-Artikel jährlich etwas 500 Newsletter https://www.meikehohenwarter.com/notizen

(NOTAS Y ENLACES DEL CAPÍTULO AQUÍ: https://www.jaimerodriguezdesantiago.com/kaizen/qa12-sistemas-de-aprendizaje-comunicacion-no-violenta-maternidad-y-paternidad-perfiles-hibridos-incentivos-al-educar-dolor-y-cambios-sociales/)¡Primer capítulo de preguntas y respuestas de esta temporada! Y con este, además, creo que me pongo al día de los mensajes acumulados. De hecho, me estoy planteando cambiar el formato y organizar de vez en cuando alguna grabación en streaming en la que podamos interactuar de forma más directa, pero no lo tengo del todo decidido y no sé tampoco si voy a tener realmente el tiempo de hacerlo, porque es probable que dentro de poco mi tiempo disponible se reduzca por un buen motivo, pero ya te lo contaré más adelante. Hoy el menú es de lo más variado, hablamos de sistemas de aprendizaje, de comunicación no verbal, de maternidad y paternidad, de cómo encajan los perfiles híbridos en el mundo laboral, del uso de incentivos al educar, del dolor y de cambios sociales. Casi nada.PATROCINADOR DEL CAPÍTULO: VDS.tech ¿Te gusta kaizen? Apoya el podcast uniéndote a la Comunidad y accede a contenidos y ventajas exclusivas: https://www.jaimerodriguezdesantiago.com/comunidad-kaizen/

 In this podcast you will learn: How to capture ideas so you don't lose themHow to think wildly using a centuries old notetaking techniqueHow to write constantly and never experience writers block againFor the past 20 years Bob Doto has worked with writers, spiritual aspirants, yogis, teachers, knowledge workers, teaching courses on Zettelkasten, PKM, social media, and spirituality. I had him on the podcast a few months ago and had a wonderful conversation. Now he's coming back on for round 2 to have a conversation about his new book, A System For Writing. Get A System For Writing: https://amzn.to/3z5lOooBob Doto Twitter: https://x.com/thehighpony?lang=en MY FREE ONLINE COURSES:

Zen, Zeroing In, Zones, Zigzagging, Zeitgeist, Zero Waste, Zooming Out, Zest, Zoning Out, Zipping Through, Zzzs (get some sleep), Zero expectations, Zero Inbox, Zettelkasten method (and Zettels)... Continue reading →

Lerne, wie Du den Wert Deiner Notizen in deinem zweiten Gehirn maximieren kannst, indem Du den digitalen Textmarker geschickt benutzt. In diesem Video zeige ich Dir die besten Strategien beim Hervorheben der Kernideen, von allem, was Du konsumierst. Mehr kreativer Output und eine höhere Produktivität sind garantiert. Egal, ob im Studium, beim Schreiben von Büchern oder Social-Media-Posts. Also, ran an den digitalen Textmarker und bringe Deine Notizen auf die nächste Stufe! 0:00 Textmarker 1.0 1:27 Textmarker sparen Zeit 3:06 Highlighting 2.0 8:40 Bezug zum Zettelkasten

Stephanie has a newfound interest in urban foraging for serviceberries in Chicago. Joël discusses how he uses AI tools like ChatGPT to generate creative Dungeons & Dragons character concepts and backstories, which sparks a broader conversation with Stephanie about AI's role in enhancing the creative process. Together, the hosts delve into professional growth and experience, specifically how to leverage everyday work to foster growth as a software developer. They discuss the importance of self-reflection, note-taking, and synthesizing information to enhance learning and professional development. Stephanie shares her strategies for capturing weekly learnings, while Joël talks about his experiences using tools like Obsidian's mind maps to process and synthesize new information. This leads to a broader conversation on the value of active learning and how structured reflection can turn routine work experiences into meaningful professional growth. Obsidian (https://obsidian.md/) Zettelkasten (https://en.wikipedia.org/wiki/Zettelkasten) Mindmaps in Mermaid.js (https://mermaid.js.org/syntax/mindmap.html) Module Docs episode (https://bikeshed.thoughtbot.com/417) Writing Quality Method docs blog post (https://thoughtbot.com/blog/writing-quality-method-docs) Notetaking for Developers episode (https://bikeshed.thoughtbot.com/357) Learning by Helping blog post (https://thoughtbot.com/blog/learning-by-helping) Transcript:  JOËL: Hello and welcome to another episode of The Bike Shed, a weekly podcast from your friends at thoughtbot about developing great software. I'm Joël Quenneville. STEPHANIE: And I'm Stephanie Minn. And together, we're here to share a bit of what we've learned along the way. JOËL: So, Stephanie, what's new in your world? STEPHANIE: So, as of today, while we record this, it's early June, and I have started foraging a little bit for what's called serviceberries, which is a type of tree/shrub that is native to North America. And I feel like it's just one of those, like, things that more people should know about because it makes these little, tiny, you know, delicious fruit that you can just pick off of the tree and have a little snack. And what's really cool about this tree is that, like I said, it's native, at least to where I'm from, and it's a pretty common, like, landscaping tree. So, it has, like, really pretty white flowers in the spring and really beautiful, like, orange kind of foliage in the fall. So, they're everywhere, like, you can, at least where I'm at in Chicago, I see them a lot just out on the sidewalks. And whenever I'm taking a walk, I can just, yeah, like, grab a little fruit and have a little snack on them. It's such a delight. They are a really cool tree. They're great for birds. Birds love to eat the berries, too. And yeah, a lot of people ask my partner, who's an arborist, like, if they're kind of thinking about doing something new with the landscaping at their house, they're like, "Oh, like, what are some things that I should plant?" And serviceberry is his recommendation. And now I'm sharing it with all of our Bike Shed listeners. If you've ever wondered about [laughs] a cool and environmentally beneficial tree [laughs] to add to your front yard, highly recommend, yeah, looking out for them, looking up what they look like, and maybe you also can enjoy some June foraging. JOËL: That's interesting because it sounds like you're foraging in an urban environment, which is typically not what I associate with the idea of foraging. STEPHANIE: Yeah, that's a great point because I live in a city. I don't know, I take what I can get [laughs]. And I forget that you can actually forage for real out in, you know, nature and where there's not raccoons and garbage [laughs]. But yeah, I think I should have prefaced by kind of sharing that this is a way if you do live in a city, to practice some urban foraging, but I'm sure that these trees are also out in the world, but yeah, have proved useful in an urban environment as well. JOËL: It's really fun that you don't have to, like, go out into the countryside to do this activity. It's a thing you can do in the environment that you live in. STEPHANIE: Yeah, that was one of the really cool things that I got into the past couple of years is seeing, even though I live in a city, there's little pieces of nature around me that I can engage with and picking fruit off of people's [inaudible 03:18] [laughs], like, not people's, but, like, parkway trees. Yeah, the serviceberry is also a pretty popular one here that's planted in the Chicago parks. So, yeah, it's just been like, I don't know, a little added delight to my days [laughs], especially, you know, just when you're least expecting it and you stumble upon it. It's very fun. JOËL: That is really fun. It's great to have a, I guess, a snack available wherever you go. STEPHANIE: Anyway, Joël, what is new in your world? JOËL: I've been intersecting two, I guess, hobbies of mine: D&D and AI. I've been playing a lot of one-shot games with friends, and that means that I need to constantly come up with new characters. And I've been exploring what AI can do to help me develop more interesting or compelling character concepts and backstories. And I've been pretty satisfied with the result. STEPHANIE: Cool. Yeah. I mean, if you're playing a lot and having to generate a lot of new ideas, it can be hard if you're, you know, just feeling a little empty [laughs] in terms of, you know, coming up with a whole character. And that reminds me of a conversation that you and I had in person, like, last month as we were talking about just how you've been, you know, experimenting with AI because you had used it to generate images for your RailsConf talk. And I think I connected it to the idea of, like, randomness [laughs] and how just injecting some of that can help spark some more, I think, creativity, or just help you think of things in a new way, especially if you're just, like, having a hard time coming up with stuff on your own. And even if you don't, like, take exactly what's kind of provided to you in a generative AI, it at least, I don't know, kind of presents you with something that you didn't see before, or yeah, it's just something to react to. JOËL: Yeah, it's a great tool for getting unstuck from that kind of writer's block or that, like, blank page feeling. And oftentimes, it'll give you a thing, and you're like, that's not really exactly what I wanted. But it sparks another idea, which is what I actually want. Or sometimes you can be like, "Hey, here's an idea I have. I'm not sure what direction to take it in. Give me a few options." And then, you see that, and you're like, "Oh, that's actually pretty interesting." One thing that I think is interesting is once I've come up with a little bit of the character concept, or maybe even, like, a backstory element...so, I'm using ChatGPT, and it has that concept of memory. And so, throughout the conversation, it keeps bringing it back. So, if I tell it, "Look, this is an element that's going to be core to the character," and then later on, I'm like, "Okay, help me brainstorm some potential character flaws for this character," it'll actually find things that connect back to my, like, core concept, or maybe an element of the backstory. And it'll give me like, you know, 5 or 10 different ideas, and some of them can be actually really good. So, I've really enjoyed doing that. It's not so much to just generate me a character so much as it is like a conversation back and forth of like, "Okay, help me come up with a vibe for it. Okay, now that I have a vibe or a backstory element or, like, a concept, help me workshop this thing. And what about that?" And if I want to say, "It's going to be this character class, what are maybe some ways I could develop it that are unusual?" and just sort of step by step kind of choose your own adventure. And it kind of walking me through the process has been really fun. STEPHANIE: Nice. Yeah, the way you're talking about it makes a lot of sense to me how asking it to help you, not necessarily do all of it, like, you know, kind of just spit out something that you're like, okay, like, that's what I'm going to use, approaching it as a tool, and yeah, that's really fun. Have you had good experiences then playing with those characters [chuckles]? JOËL: I have. I think it's also really great for sort of padding out some of the content. So, I had a character I played who was a washed-up politician. And at one point, I knew that I was going to have to make a campaign speech. And I asked ChatGPT, "Can you help me, like...here are the themes I want to hit. Give me a, like, classic, very politician-sounding speech that sounds inspiring but also says nothing at the same time." And it did a really good job of that. And you can tell it, "Oh, that's too long. That's too short. I want three sentences. I want five sentences." And that was great. So, I saved that, brought it to the table, and read out my campaign speech, and it was a hit. STEPHANIE: Amazing. That's really fun. I like that because, yeah, I don't think...I am so poor at just improvising things like that, even though, like, I want to really embody the character. So, that's cool that you found a way to help you be able to do that because that just feels like kind of what playing D&D can be about. JOËL: I've never DM'd, but I could imagine a situation where, because the DMs have to improv so much, and you know what the players do, I could imagine having a tool like that available behind the DM screen being really helpful. So, all of a sudden, someone's just like, "Oh, I went to a place," and, like, all of a sudden, you have to, like, sort of generate a village and, like, ten characters on the spot for people that you didn't expect, or an organization or something like that. I could imagine having a tool like that, especially if it's already primed with elements from your world that you've created, being something really helpful. That being said, I've never DM'd myself, so I have no idea what it actually is like to be on the other side of that screen. STEPHANIE: Cool. I mean, if you ever do try that or have a DM experience and you're like, hmm, I wonder kind of how I might be able to help me here, I bet that would be a very cool experience to share on the show. JOËL: I definitely have to report back here. Something that I've been thinking about a lot recently is the difference between sort of professional growth and experience, so the time that you put into doing work. Particularly maybe because, you know, we spend part of our week doing client work, and then we have part of the week that's dedicated to maybe more directly professional growth: our investment day. How do we grow from that, like, four days a week where we're doing client work? Because not all experience is created equal. Just because I put in the hours doesn't mean that I'm going to grow. And maybe I'm going to feel like I'm in a rut. So, how do I take those four days a week that I'm doing code and transform that into some sort of growth or expansion of my knowledge as a developer? Do you have any sort of tactics that you like to use or ways you try to be a little bit more mindful of that? STEPHANIE: Yeah, this is a fun question for me, and kind of reminds me of something we've talked a little bit about before. I can't remember if it was, like, on air or just separately, but, you know, we talk a lot about, like, different learning strategies on the show, I think, because that's just something you and I are very into. And we often, like, lean on, you know, our investment day, so our Fridays that we get to not do client work and kind of dedicate to professional development. But you and I also try to remember that, like, most people don't have that. And most people kind of are needing to maybe find ways to just grow from the day-to-day work that they do, and that is totally possible, I think. And some of the strategies that I have are, I guess, like, it is really...it can be really challenging to, like, you know, be like, okay, I spent 40 hours doing this, and like, what did I learn [chuckles]? Feeling like you have to have something to show for it or something to point to. And one thing that I've been really liking is these automated check-ins we have at the end of the week. And, you know, I suspect that this is not that uncommon for just, like, a workplace to be like, "Hey, like, how did your week go? Like, what are some ways that it was successful? Like, what are your challenges? Like, where do you need support or help?" And I think I've now started using that as both, like, space for giving an update on just, like, business-y things. Like, "Here's the status of this project," or, like, "Here's, you know, a roadblock that we faced that took some extra time," or whatever. Then also being like, oh, this is a great time to make this space for myself, especially because...I don't know about you, but whenever I have, like, performance review time and I have to write, like, a self-review, I'm just like, did I do anything in the last six months [laughs], or how have I grown in the last six months? It feels like such a big question, kind of like you were talking about that blank page syndrome a little bit. But if I have kind of just put in the 10 minutes during my Friday to be like, is there something that was kind of just for me that I can say in my check-in? I can go back and, yeah, just kind of start to see just, like, you know, pick out or just pay attention to how, like, my 40 hours is kind of serving me in growing in the ways that I want to and not just to deliver code [laughs]. JOËL: What you're describing there, that sort of weekly check-in and taking notes, reminds me of the practice of journaling. Is that something that you've ever tried to do in your, like, regular life? STEPHANIE: Oh yeah, very much so. But I'm not nearly as, like, routine about it in my personal life. But I suspect that the routine is helpful in more of a, like, workplace setting, at least for me, because I do have, like, more clear pathways of growth that I'm interested in or just, like, something that, I don't know, not that it's, like, expected of everyone, but if that is part of your goals or, like, part of your company's culture, I feel like I benefit from that structure. And yeah, I mean, I guess maybe that's kind of my way of integrating something that I already do in my personal life to an environment where, like I said, maybe there is, like, that is just part of the work and part of your career progression. JOËL: I'm curious about the frequency. You mentioned that you sort of do this once a week, sort of a check-in at the end of the week. Do you find that once a week is about the right frequency versus maybe something like daily? I know a lot of these sort of more modern note-taking systems, Roam Research, or Obsidian, or whatever, have this concept of, like, a daily note that's supposed to encourage something that's kind of like journaling. Have you ever tried something more on a daily basis, or do you feel like a week is about...or once a week is about the right cadence for you? STEPHANIE: Listen, I have, like, complicated feelings about this because I think the daily note is so aspirational for me [laughs] and just not how I work. And I have finally begrudgingly come to accept this no matter how much, like, I don't know, like, bullet journal inspirational content I consume on the internet [laughs]. I have tried and failed many a time to have more frequency in that way. But, I don't know, I think it almost just, like, sets me up for failure [laughs] because I have these expectations. And that's, like, the other thing. It's like, you can't force learning necessarily. I don't know if this is, like, a strategy, but I think there is some amount of, like, making sure that I'm in the right headspace for it and, you know, like, my environment, too, kind of is conducive to it. Like, I have, like, the time, right? If I'm trying to squeeze in, I don't know, maybe, like, in between meetings, 20 minutes to be like, what did I learn from this experience? Nothing's coming out [laughs]. That was another thing that I was kind of mulling over when he had this topic proposed is this idea of, like, mindset and environment being really important because you know when you are saying, like, not all time is created equal, and I suspect that if, you know, either you or, like, the people around you and the environment you're in is not also facilitating growth, and, like, how much can you really expect for it to be happening? JOËL: I mean, that's really interesting, right? The impact of sort of a broader company culture. And I think that definitely can act as a catalyst for growth, either to kind of propel you forward or to pull you back. I want to dig into a little bit something you were saying about being in the right headspace to capture ideas. And I think that there's sort of almost, like, two distinct phases. There's the, like, capturing data, and information, and experiences, and then, there's synthesizing it, turning information into learning. STEPHANIE: Yes. JOËL: And it sounds like you're making a distinction between those two things, specifically that synthesis step is something that has to happen separately. STEPHANIE: Ooh, I don't even...I don't know if I would necessarily say that I'm only talking about synthesis, but I do like that you kind of separated those categories because I do think that they are really important. And they kind of remind me a lot about the scientific method a little bit where, you know, you have the gathering data and, like, observations, and you have, you know, maybe some...whatever is precipitating learning that you're doing maybe differently or new. And that also takes time, I think, or intention at least, to be like, oh, do I have what I need to, like, get information about how this is going? And then, yeah, that synthesis step that I think I was talking about a little bit more. But I don't think either is just automatic. There is, I think, quite a bit of intention involved. JOËL: I think maybe the way I think about this is colored by reading some material on the Zettelkasten method of note-taking, which splits up the idea of fleeting notes and literature notes, which are sort of just, like, jotting down ideas, or things you've seen, things that you've learned, maybe a thought you had when you read a particular paragraph in a blog post, something like that. And then, the permanent notes, which are more, like, fully formed thoughts that arise out of the more fleeting ones. And so, the idea is that the fleeting ones maybe you're taking those in a notebook if you're doing it pen and paper. You could be doing it in some sort of, like, daily note, or something like that. And then, those are temporary. They were there to just capture information. Later on, you process that, and then you can throw them out if you need to. STEPHANIE: Yeah, that makes a lot of sense. This has actually been a shift for me, where I used to rely a lot more on memory and perhaps, like, didn't have a great system for taking things like fleeting notes and, like, documenting kind of [inaudible 18:28] what I was saying earlier about how do I make sure that the information is recorded, you know, for me to synthesize later? And I have found a lot more success lately in that fleeting note style of operating. And thanks to Obsidian honestly, now it's so easy to be like, oh, I'm just going to open a quick new file. And I need as little friction as possible to, like, put stuff somewhere [laughs]. And, actually, I'm excited to talk a little bit more about this with you because I think you're a little bit different where you somehow find the time [laughs] and care to create your diagrams. I'm like, if I can, for some reason, even get an Obsidian file open, I'll tab to Slack. And I send myself a lot of notes in my just own personal DM space. In fact, it's actually kind of embarrassing because I use the Command+K shortcut to navigate to my own personal DMs, which you can get to by typing me, like, M-E. And sometimes I've accidentally just entered that into a channel chat [laughs], and then I have to delete it really quick later when I realize what I've done. So, yeah, like, I meant to navigate to my personal notes, and I just put in our team chat, "Me [laughs]." And, I don't know, I have no idea how that comes up [laughs], what people think is going on. But if anyone's listening to this podcast from thoughtbot and has seen that of me, that's what happened. JOËL: You may not be the only one who's done that. STEPHANIE: Thank you. Yeah [laughs], that's good to know. JOËL: I want to step back a little bit because we've been talking about, like, introspection, and synthesis, and finding moments to capture information. And I think we've sort of...there's an unspoken assumption here that a way to kind of turbocharge learning from day-to-day experience is some form of synthesis or self-reflection. Would you agree with that statement? STEPHANIE: Okay. This is another thing that I am perhaps, like, still trying to figure out, and we can figure it out together, which is separating, like, self-driven learning and, like, circumstance-driven learning. Because it's so much easier to want to reflect on something and find time to be, like, oh, like, how does this kind of help my goals or, like, what I want to be doing with my work? Versus when you are just asked to do something, and it could still be learning, right? It could still be new, and you need to go do some research or, you know, play around with a new tool. But there's less of that internal motivation or, like, kind of drive to integrate it. Like, do you have this distinction? JOËL: I've definitely noticed that when there is motivation, I get more out of every hour of work that I put in in terms of learning new things. The more interest, the more motivation, the more value I get per unit of effort I put in. STEPHANIE: Yeah. I think, for me, the other difference is, like, generative learning versus just kind of absorbing information that's already out there that someone else's...that is kind of, yeah, just absorbing rather than, like, creating something new from, like, those connections. JOËL: Ooh. STEPHANIE: Does that [chuckles] spark something for you? JOËL: The gears are turning in my head because I'm almost hearing that as, like, a passive versus active learning thing. But just sort of like, I'm going to let things happen to me, and I will come out of that with some experience, and something is going to happen. Versus an active, I am going to, like, try to move in a direction and learn from that and things like that. And I think this maybe connects back to the original question. Maybe this sort of, like, checking in at the end of the week, taking notes is a way to convert something that's a bit more of a passive experience, spending four days a week doing a project for a client, into something that's a little bit of a more active learning, where you say, "Okay, I did four weeks of this particular type of Rails work. What do I get out of it? What have I learned? What is something new that I've seen? What are some opinions I have formed, patterns I like or dislike?" STEPHANIE: Yeah, I like that distinction because, you know, a few weeks ago, we were at RailsConf. We had kind of recapped it in a previous episode. And I think we had talked about like, oh, do we, like, to sit in talks or participate in workshops? And I think that's also another example of, like, passive versus active, right? Because I 100%, like, don't have the same type of learning by just, you know, listening to a talk that I do with maybe then going to look up, like, other things this person has put out in the world, finding them to talk to them about it, like, doing something with the content, right? Otherwise, it's just like, oh yeah, I heard this talk. Maybe one day I'll remember it when the need arises [laughs]. I, like, have a pointer to it in my brain. But until then, it probably just kind of, like, sits there, and nothing's really happened with it. JOËL: I think maybe another thing that's interesting in that passive versus active distinction is that synthesis is inherently an act of creation. You are now creating new ideas of your own rather than just capturing information that is being thrown at you, either by sitting in a talk or by shipping tickets. The act of synthesizing and particularly, I think, making connections between ideas, either because something that, let's say you're in a talk, a speaker said that sparks an idea for yourself, or because you can connect something that speaker said with another idea that you already have or an idea that you've seen elsewhere. So, you're like, oh, the thing this person is saying connects to this thing I read in a book or something another speaker said in an earlier session, or something like that. All of a sudden, now you're creating these new bits of knowledge, new perspectives, maybe even new mental models. We talked about mental models last week. And so, knowledge is not just the facts that you absorb or memorize. A lot of it is building the connections between those facts. And those are things that are not always given to you. You have to create them yourself. STEPHANIE: Yeah, I am nodding my head a lot because that's resonating with, like, an experience that I'm having kind of coaching and mentoring a client developer on my team who is earlier in her career. And one thing that I've been really, like, working on with her is asking like, "Oh, like, what do you think of this?" Or like, "Have you seen this before? What are your reactions to this code, or, like this comment?" or whatever. And I get the sense that, like, not a lot of people have prompted her to, like, come up with answers for those kinds of questions. And I'm really, really hopeful that, like, that kind of will help her achieve some of the goals that she's, like, hoping for in terms of her technical growth, especially where she's felt like she's stagnated a little bit. And I think that calls back really well to what you said at the beginning of, like, you can spend years, right? Just kind of plugging away. But that's not the same as that really active growth. And, again, like, that's fine if that's where you're at or want to be at for a little while. But I suspect if anyone is kind of, like, wondering, like, where did that time go [laughs]...even for me, too, like, once someone started asking me those questions, I was like, oh, there's still so much to figure out or explore. And I think you're actually really good at doing that, asking questions of yourself. And then, another thing that I've picked up from you is you ask questions about, like, what are questions other people would have? And that's a skill that I feel like I still have yet to figure out. I'm [chuckles] curious what you think about that. JOËL: That's interesting because that kind of goes to another level. I often think of the questions other people would have from a more, like, pedagogical sense. So, I write a lot of blog posts. I write a lot of talks that I give. So, oftentimes when I'm creating that kind of material, there's a bit of an inner critic who's trying to, you know, sitting in the audience listening to myself speak, and who's going to maybe roll their eyes at certain points, or just get lost, or maybe raise their hand with a question. And that's who I try to address those things so that then when I go through it the next time, that inner critic is actually feeling engaged and paying attention. STEPHANIE: Do you find that you're able to do that because you've seen that happen enough times where you're like, oh, I can kind of predict maybe what someone might feel confused about? I'm curious, like, how you got from being, like, well, I know what I would be confused about to what would someone else be unsure or, like, want more information about. JOËL: Part of the answer there is that I'm a very harsh critic myself. STEPHANIE: [laughs] Yes. JOËL: So, I'm sitting in somebody else's talk, and there are probably parts where I'm rolling my eyes or being like, wait a minute, how did you get from this idea to this other thing? That doesn't follow. And so, I try to turn that back towards myself and use that as fuel to make my own work better. STEPHANIE: Yeah, that's cool. I like that. Even if it's just framed as, like, a missed opportunity for people to have better or more comprehensive understanding. I know that's something that you're, like, very motivated to help kind of spread more of [laughs]. Understanding and learning is just important to you and to me. So, I think that's really cool that you're able to find ways to do that. JOËL: Well, you definitely want to, I think, to keep a sort of beginner's mindset for a lot of these things, and one of the best ways to do that is to work with beginners. So, I spent a lot of time, back in the day, for example, in the Elm language chat room, just helping people answer basic questions, looking up documentation, explaining sort of basic concepts. And that, I think, helped me get a sense of like, where were newcomers to the language getting stuck? And what were the explanations of those concepts that really connected? Which I could then translate into my work. And I think that that made me a better developer and helped me build this, like, really deep understanding of the underlying concepts in a way that I wouldn't have had just writing code on my own. STEPHANIE: Wow, forum question answering hero. I have never thought to do that or felt compelled to do that. But I remember my friend was telling me, she was like, "Yeah, sometimes I just want to feel good about myself. And I remember that I know things that other people, like, are wanting to find out," and she just will answer some easy questions on Stack Overflow, you know, about, like, basic Rails stuff or something. And she is like, "Yeah, and that's doing my good deed [laughs]." And yeah, I think that it also, you know, has the same benefits that you were just saying earlier about...because you want to be helpful, you figure out how to actually be helpful, right? JOËL: There's maybe a sense as well that helping others, once more, forces you into more of an active mindset for growth in the same way that interrogating yourself does, except now it's a beginner who's interrogating you. And so, it forces you to think a little bit more about those whys or those places where people get stuck. And you've just sort of assumed it's a certain way, but now you have to, like, explain it and really get into some of the concepts. STEPHANIE: So, on the show, we've talked a lot about the fun things you share in the dev channel in our Slack workspace. But I recently discovered that someone (Was it you?) created an Obsidian MD channel for our favorite note-taking software. And in it, you shared a really cool tool that is available in Obsidian called mind maps. JOËL: Yeah, so mind maps are a type of diagram. They're effectively a tree structure, but they don't really look like that when you draw them out. You start with a sort of topic in the center, and then you just keep drawing branches off of that, going every direction. And then, maybe branches off branches and keep going as you add more content. Turns out that Mermaid.js supports mind maps as a graph type, and Obsidian embeds Mermaid diagrams. So, you can use Mermaid's little language to express a mind map. And now, all of a sudden, you have mind mapping as a tool available for you within Obsidian. STEPHANIE: And how have you been using that to kind of process and experience or maybe, like, end up with some artifacts from, like, something that you're just doing in regular day-to-day work? JOËL: So, kind of like you, I think I have the aspiration of doing some kind of, like, daily note journaling thing and turning that into bigger ideas. In practice, I do not do that. Maybe that's the thing that I will eventually incorporate into my practice, but that's not something that I'm currently doing. Instead, a thing that I've done is a little bit more like you, but it's a little bit more thematically chunked. So, for example, recently, I did several weeks of work that involved doing a lot of documentation for module-level documentation. You know, I'd invested a lot of time learning about YARD, which is Ruby's documentation system, and trying to figure out, like, what exactly are docs that are going to be helpful for people? And I wanted that to not just be a thing I did once and then I kind of, like, move on and forget it. I wanted to figure out how can I sort of grow from that experience maximally? And so, the approach I took is to say, let's take some time after I've completed that experience and actually sort of almost interrogate it, ask myself a bunch of questions about that experience, which will then turn into more broad ideas. And so, what I ended up doing is taking a mind-mapping approach. So, I start that center circle is just a circle that says, "My experience writing docs," and then I kind of ring it with a series of questions. So, what are questions that might be interesting to ask someone who just recently had experience writing documentation? And so, I come up with 4,5,6 questions that could be interesting to ask of someone who had experience. And here I'm trying to step away from myself a little bit. And then, maybe I can start answering those questions, or maybe there are sub-questions that branch off of that. And maybe there are answers, or maybe there are answers that are interesting but that then trigger follow-up questions. And so I'm almost having a conversation with myself and using the mind map as a tool to facilitate that. But the first step is putting that experience in the center and then ringing it with questions, and then kind of seeing where those lead. STEPHANIE: Cool. Yeah, I am, like, surprised that you're still following that thread because the module docs experience was quite a little bit a while ago now. We even, you know, had an episode on it that I'll link in the show notes. How do you manage, like, learning new things all the time and knowing what to, like, invest energy and attention into and what to kind of maybe, like, consider just like, oh, like, I don't know, that was just an experience that I had, and I might not get around to doing anything with it? JOËL: I don't know that I have a great system. I think sometimes when I do, especially a more prolonged chunk of time doing a thing, I find it really worthwhile to say, hey, I don't want that to sort of just be a thing that was in my memory, and then it moves out. I'd like to pull out some more maybe practical or long-term ideas from it. Part of that is capture, but some of that is also synthesis. I just spent two weeks or I just spent a month using a particular technology or doing a new kind of task. What do I have to show for it? Are there any, like, bigger ideas that I have here? Does this connect with any other technologies I've done or any other ideas or theories? Did I come up with any opinions? Did I like this technology? Did I not? Are there elements that were inspirational? And then capturing some of that eventually with the idea of...so I do a sort of Zettelkasten-style permanent note collection, the idea to create at least a few of those based off of the experience that I can then connect to other things. And maybe it eventually turns into other content. Maybe it's something I hold onto for a while. In the case of the module docs, it turned into a Bike Shed episode. It also turned into a blog post that was published this past week. And so, it does have a way of coming back. STEPHANIE: Yeah. Yeah. One thing that sparked for me was that, you know, you and I spend a lot of time thinking about, like, the practice of writing software, you know, in the work we do as consultants, too. But I find that, like, you can also apply this to the actual just your work that you are getting paid for [laughs]. This was, I think, a nascent thought in the talk that I had given. But there's something to the idea of, like, you know, if you are working in some code, especially legacy code, for a long time, and you learn so much about it, and then what do you have to show for it [chuckles], you know? I have really struggled with feeling like all of that work and learning was useful if it just, like, remains in my memory and not necessarily shared with the team or, I don't know, just, like, knowing that if I leave, especially since I am a contractor, like, just recognizing that there's value in being like, oh, I spent an hour or, like, half a day sifting through this complex legacy code just to make, like, a small change. But that small change is not the full value of all of the work that I did. And I suspect that, like, just the mind mapping stuff would be really interesting to apply to more. It's not, like, just practical work, but, like, more mundane, I don't know, like, labor [laughs], if you will. JOËL: I can think of, like, sort of two types of knowledge that you can take out of something like that. Some of it is just understanding how this legacy system works, saying, oh, well, they have this user model that's connected to this old persona table, which is kind of unused, but we sometimes rely for in this legacy case. And you've got to have this permission flag turned on and, like, all those things that you had to just discover by reading the code and exploring. And that's going to be useful to you as long as you work in that legacy codebase, as long as you work through that path. But when you move on to another project, that knowledge probably doesn't serve you a whole lot. There are things that you did throughout that journey, though, that you can probably pull out that are going to be useful to you on other projects. And that might be maybe you came up with a new way of navigating the code or a new way of, like, finding how different pieces were connected. Maybe it was a diagramming tool; maybe it was some sort of gem. Maybe it was just a, oh, a heuristic, like, when I see a model, I like to follow the associations first. And I always go for the hasmanys over the belongstos because those generally lead me in the right direction. Like, that's really interesting insight, and that's something that might serve you on a following project. You can also pull out bigger things like, are there refactoring techniques that you experimented with or that you learned on this project that you would use again elsewhere? Are there ways of maybe quarantining scary code on a legacy project that are a thing that you would want to make more consistent part of your practice? Those are all great things to pull out of, just a like, oh yeah, I did some work on a, like, old legacy part of an app. And what do I have to show for it? I think you can actually have a lot to show for it. STEPHANIE: Yeah, that's really cool. That sounds like a sure way of multiplying the learning. And I think I didn't really consider that when I was first talking about it, too. But yeah, there are, like, both of those things kind of available to you to, like, learn from. Yeah, it's like, that time is never just kind of, like, purely wasted. Oh, I don't know, sometimes it really feels like that [laughs] when you are debugging something really silly. But yeah, like, I would be interested in kind of thinking about it from both of those lenses because I think there's value in what you learn about that particular system in that moment of time, even if it might not translate to just future works or future projects. And, like, that's something that I think we would do better at kind of capturing, and also, there's so much stuff, too, kind of to that higher level growth that you were speaking to. JOËL: I think some of the distinctions we're talking about here is something that was explored in an older episode on note-taking with Amanda Beiner, where we sort of explored the difference between exploratory notes, debugging notes, idea notes, and how note-taking is not a single thing. It can serve many purposes, and they can have different lifespans. And those are all just ways to aid your thinking. But being maybe aware of the kind of thinking that you're trying to do, the kind of notes you're trying to take can help you make better use of that time. STEPHANIE: I have one last question for you before we wrap up, which is, do you find, like, the stuff we're talking about to be particularly true about software development, or it just happens to be the thing that you and I both do, and we also love to learn, and so, therefore, we are able to talk about this for, like, 50 minutes [laughs]? Are you able to make any kind of distinction there, or is it just kind of part of pedagogy in general? JOËL: I would say that that sort of active versus passive thing is a thing that's probably true, just about anything that you do. For example, I do a lot of bouldering. Just going spending a lot of time on the wall, climbing a lot; that's going to help me get better. But a classic way that people try to improve is filming themselves or having a friend film themselves, and then you can look at it, and then you evaluate, oh, that's what I did. This is where I was struggling to get the next hold. What if I try to do something different? So, building in an amount of, like, self-reflection into the loop all of a sudden catalyzes that learning and helps you grow at a rate that's much more than if you're just kind of mindlessly putting time into it. So, I would go so far as to say that self-reflection, synthesis—those are all things that are probably going to catalyze growth in most areas of your life if you're being a little bit more self-aware. But I've found that it's been particularly useful for me when it comes to trying to get better at the job that I do every week. STEPHANIE: Yeah, I think, for me, it's like, yeah, getting better at being a developer rather than being, you know, a software developer at X company. Like, not necessarily just getting better at working at that company but getting better at the skill itself. JOËL: And those two things have a way of sort of, like, folding back into themselves, right? If you're a better software developer in general, you will probably be a better developer at that company. Yes, you want domain knowledge and, like, a deep understanding of how the system works is going to make you a better developer at that company. But also, if you're able to find more generic approaches to onboard onto new things, or to debug more effectively, or to better read or understand unknown code of high complexity, those are all going to make you much better at being a developer at that company as well. And they're transferable skills, so they're all really good things to have. STEPHANIE: On that note. Shall we wrap up? JOËL: Let's wrap up. STEPHANIE: Show notes for this episode can be found at bikeshed.fm. JOËL: This show has been produced and edited by Mandy Moore. STEPHANIE: If you enjoyed listening, one really easy way to support the show is to leave us a quick rating or even a review in iTunes. It really helps other folks find the show. JOËL: If you have any feedback for this or any of our other episodes, you can reach us @_bikeshed, or you can reach me @joelquen on Twitter. STEPHANIE: Or reach both of us at hosts@bikeshed.fm via email. JOËL: Thanks so much for listening to The Bike Shed, and we'll see you next week. ALL: Byeeeeeee!!!!!! AD: Did you know thoughtbot has a referral program? If you introduce us to someone looking for a design or development partner, we will compensate you if they decide to work with us. More info on our website at: tbot.io/referral. Or you can email us at: referrals@thoughtbot.com with any questions.

(NOTAS Y ENLACES DEL CAPÍTULO AQUÍ: https://www.jaimerodriguezdesantiago.com/kaizen/qa11-encuentros-inesperados-organizar-nuestra-informacion-diseno-humano-cambios-de-sector-estoicismo-objetivos-y-un-intringulis/)¡Último Preguntas y respuestas de la temporada! Y ha quedado bastante bastante variado.Se nos han cruzado fortuitos, Sistemas de organización de nuestra información, diseño humano, cambios de sector, estoicismo, formas de organizar nuestros objetivos y hasta una pregunta hipotética sobre cómo vivir miles de vidas. Por cierto, que me habéis avisado varias personas de que en algunos de los anteriores, las preguntas de la audiencia sólo sonaban por un canal y no en estéreo. Perdonad, fue un fallo técnico al exportarlas desde whatsapp, pero espero que haya quedado resuelto.Con este capítulo creo que me he puesto casi al día, me parece que queda algún audio suelto, pero esos ya serán para la próxima temporada.Patrocinador del capítulo: Morfeo.com (150€ de descuento con el código KAIZEN)  ¡Ya están abiertas las inscripciones para la 2ª edición del programa de desarrollo directivo y liderazgo que dirijo en Tramontana! ¿Te interesa? Toda la info aquí: https://www.tramontana.net/desarrollo-directivo-liderazgo¿Te gusta kaizen? Apoya el podcast uniéndote a la Comunidad y accede a contenidos y ventajas exclusivas: https://www.jaimerodriguezdesantiago.com/comunidad-kaizen/

This interview was recorded for GOTO Unscripted.https://gotoldn.com/2024-eda-aws-dayRead the full transcription of this interview hereDavid Boyne - Senior Developer Advocate at AWS Eric Johnson - Principal Developer Advocate for Serverless at AWSRESOURCESDavidhttps://twitter.com/boyney123https://linkedin.com/in/david-boynehttps://www.boyney.ioErichttps://twitter.com/edjgeekhttps://linkedin.com/in/singledigithttps://serverlessland.comLinkshttps://serverlessland.com/event-driven-architecture/visualshttps://zettelkasten.dehttps://en.wikipedia.org/wiki/Niklas_Luhmannhttps://youtu.be/39ujoTd2CJIhttps://youtu.be/9StQpMLC-5Qhttps://youtu.be/GBzr48Mj2JUDESCRIPTIONEric Johnson and Dave Boyne take a deep dive into Event-Driven Architecture (EDA) visuals, dissecting complex concepts with clarity and insight. Their discussion stresses the importance of thoughtful event design, the nuances of event delivery failures, and the intricacies of communicating between bounded contexts.With a wealth of experience and expertise, they shed light on the artistry behind EDA visuals, offering hands-on advice for architects and enthusiasts alike. [...]RECOMMENDED BOOKSAdam Bellemare • Building Event-Driven MicroservicesPeter Sbarski • Serverless Architectures on AWSMichael Stack • Event-Driven Architecture in GolangFord, Richards, Sadalage & Dehghani • Software Architecture: The Hard PartsGerardus Blokdyk • Event-Driven Architecture EDAJames Urquhart • Flow ArchitecturesTwitterInstagramLinkedInFacebookLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

Dans cet épisode palpitant de "Young, Wild & Freelance", Thomas plonge au cœur des préoccupations actuelles d'énormément de freelances et entrepreneurs : l'intelligence artificielle. Alors que la vague de l'IA (et notamment de ChatGPT) est arrivée de toute force en 2023, en quelques mois elle s'intègre de plus en plus dans notre vie professionnelle. Dans cette conversation, Shubham Sharma et Thomas Burbidge explorent l'impact de cette technologie sur notre avenir, nos métiers et la société. Doit-on craindre ou embrasser l'IA dans nos entreprises ? Et comment rester compétitif dans un environnement en constante évolution ? Shubham et Thomas abordent des sujets cruciaux tels que la régulation de l'IA, son potentiel pour accentuer les inégalités sociales et osent même une comparaison intriguante entre l'IA et la course à l'arme atomique. Êtes-vous prêt à tirer parti de l'intelligence artificielle sans sacrifier l'humain dans votre activité freelance ? Ce débat riche d'enseignements offre des insights précieux sur la manière de naviguer dans l'écosystème entrepreneurial actuel, marqué par les avancées technologiques. Rejoignez-nous pour une discussion profonde sur comment l'intelligence artificielle façonne notre vision du travail, le rôle crucial de l'éducation et les réflexions clés écologiques derrière ces technologies. Cet épisode vous aidera à comprendre les enjeux de l'IA pour les freelances et entrepreneurs tout en conservant une approche éthique et durable dans leur business.Abonne toi au podcast pour ne rien manquer des épisodes suivants

An audio blog of sorts, where I focus on one thing that’s not directly related to fiction but important for me. This episode I’m covering Zettelkasten. Here are some supporting links: Zettelkasten on Wikipedia Zettelkasten.de FYI I’m using Vim with Vimwiki and Vim-zettel. I’ve also tried Emacs with Org-Roam, but I didn’t care for it…Read more F/log_1: Zettelkasten

Do you feel your digital notes are not giving you what you want? And, is there a right and wrong way to manage all these notes? That's what we are looking at today.  You can subscribe to this podcast on: Podbean | Apple Podcasts | Stitcher | Spotify | TUNEIN Links: Email Me | Twitter | Facebook | Website | Linkedin The Working With… Weekly Newsletter The FREE Beginners Guide To Building Your Own COD System Carl Pullein Learning Centre Carl's YouTube Channel Carl Pullein Coaching Programmes The Working With… Podcast Previous episodes page Script | 317 Hello, and welcome to episode 317 of the Working With Podcast. A podcast to answer all your questions about productivity, time management, self-development and goal planning. My name is Carl Pullein, and I am your host of this show. Over the last few years, there's been a lot of discussion around how we manage our digital notes. There have been hundreds, if not thousands of new notes apps promising to do wonderful things for us and there have been numerous ways to organise all these notes from Tiago Forte's PARA and the Second Brain to the Zettelkasten system.  The question is do any of these apps and systems work?  I feel qualified to answer this question as I have been down every rabbit hole possible when it comes to digital notes. I've tried Michael Hyatt's Evernote tagging system, Tiago's PARA and I even developed my own system, GAPRA. But, ultimately do any of these work ?  And asking that question; do any of these systems give you what you need? Perhaps is the right place to start. What do you want from a notes app? What do you want to see and how?  Before we get to the answers here, let me hand you over to the Mystery Podcast Voice for this week's question.  This week's question comes from Susan. Susan asks, Hi Carl, I'm having difficulties trying to understand how best to use Evernote. I just do not know how to organise my notes. I have thousands of notes in there going back at least five years and it's a mess. Do you have any suggestions on how best to clean all these notes up?  Hi Susan, thank you for your question.  I don't think you are alone. The popularity of books like Building A Second Brain and the number of YouTube videos on this subject suggests many people are struggling to know how best to organise their digital notes. But, I wonder if what we are doing is over-complicating something that should be very simple.  I've recently been reading Walter Isaacson's brilliant biography of Leonardo Da Vinci and on the chapter about his notebooks Isaacson points out that Leonardo Da Vinci instilled the habit of carrying around a notebook into all is students and apprentices. It was something Leonardo did himself and everything he collected, wrote and sketched was random in order. We are very fortunate that many of these notebooks survive today and what we get to see is the complete randomness of what he collected. In these notebooks there are designs, sketches, thoughts and to-do lists all on the same page. It was this randomness that led to Leonardo discovering new ways to connect ideas to solve difficult problems and to paint in a way no one else had ever done.  And, I think, this is where we have gone wrong with our digital notes. It's the randomness of your notes that will lead you to discover new ways of doing things. It will help you to be more creative and help you develop your ideas. If you try and strictly organise your notes—something a digital notes app will do—you lose those random connections. Everything will be organised by topic, thought or idea.  That does not mean that you want complete randomness. There will be projects, goals and areas of interest that you will want to keep together. A large project works best when all related notes, emails and thoughts are kept together. After all, they are connected by a common desired outcome. This is where your digital notes will excel—everything together in one place.  This is why having a project notebook or folder is a good idea. You can keep all these materials together and it gives you a central place to review your ongoing projects.  Then, there are what I would describe as critical information materials—things like your clothing and shoe sizes for the various places you buy things from. You may collect your receipts in organised months, and if you trust your digital notes, you may want to keep information such as your ID numbers, driving licence details, and health insurance certificates.  Again, digital notes are great for storing this kind of information as they make it easily retrievable whenever you need it.  What about everything else? The random thoughts and ideas you have. Well, if you want these to be useful to you at some future date, you will want to keep them random. Why is that? Your brain works at a very high level of illogicality. This is the opposite of what a computer does. A computer operates on very strict logical lines. Even AI works logically. AI will look at data and information and give you answers that are already in existence. This often seems amazing because we had not thought of those ideas before, but someone did. That's how AI found the answers.  And of course, as we recently discovered with Google's AI models, there are the biases of the people programming the software—all based on existing thoughts and ideas.  It's these notes that if you want to develop new, creative ideas that link uniquely together, they want to be maintained in a random way.  Paper notebooks make this easy. Each new thought or idea is added to a page in your notebook chronologically, and over time, your ideas will fill that notebook in the order you have them. There may be blocks of similar thoughts and ideas you collected around the same time, but on the whole, they will be completely random. Perhaps on one page, you have some ideas about how you will redesign your back garden and on another page, you have drafted out some ideas about where you and your family will go on their next holiday.  This becomes a little more difficult with digital notes because your computer and the apps you use will want to organise them logically. However, you can create randomness here, too, if you use an archive folder. Many people think of their archive as being one step short of the trash. It's where things you are not sure what to do with go. But stop a moment. Where would historians be without your country's national archive? What are museums? Essentially, museums are archives of interesting things people may want to see. And there is the archive at the Vatican that holds so many treasures and documents.  An archive is not a glorified trash can. It's a treasure trove of history. And if you create an archive notebook or folder in your digital notes you will be creating your own digital archive.  Now, because places like the National Archives in the US or UK or the archives at the Vatican City are always adding new stuff, it would be impossible to organise all these documents by theme. They may be tagged by theme, but they are organised by the date they entered the archive. If I wanted to find documents related to the Titanic, I would begin my search around April 1912. If I wanted to get a snapshot of life in 1964, I would just go to the section that housed documents from 1964.  You can do the same with your own archives. Once you have created a notebook or folder called archive, you can create sub-folders or sub-notebooks by year. Then, as you archive notes, you just add them to the year they were created.  This approach will give you the all-important randomness, yet you still have some organisation.  You can tag these notes if you wish; I do. But, and this is an important but, don't try and be too clever here.  Imagine you were researching the Vietnam War and wanted to know how and why the war escalated in 1965. If you were at the US National Archives, you might begin your research in 1965, then Vietnam. So, the tag would be Vietnam. If you wanted to narrow down your research, you might look at the documents related to President Johnson's decision-making, so perhaps there would be a tag for presidential papers. Beyond that, you would be trying to fine-tune things too much. You would likely see from the results you get which documents relate to meetings.  In your archive, you may have taken a trip to Paris in 2018, and while there, you came across a fantastic restaurant. Perhaps you took at picture of the menu and saved that into your notes. Now, you have two ways of retrieving that information today. If you remember the year you were in Paris, you could go straight to your 2018 archive, and as your notes will be in date order, you could scroll down to the date you were in Paris.  The alternative is if you tagged the note “Paris”, you could do a search for “Paris”. And within seconds you will have retrieved the information you wanted.  That's how you want your notes to work. Keep them simple, so that if you want to retrieve information at a later date, you would be able to find things quickly.  What I've noticed is when we try and be too strict about how we organise our notes we are always fiddling and changing things. While this can be fun, at first, it becomes a drag on your productivity because the more time you spend organising, the less time you spend doing the work you need to do.  You could create separate notebooks for places and topics, but unless these are lifetime interests, keeping everything in their separate notebooks will not make retrieval any faster, and you lose that all-important randomness.  Another area where randomness really helps is with your ideas and thoughts. I'm sure you've had an idea about classes you may want to take or a business idea you want to investigate. You may have had ideas about starting a blog or podcast or writing a book. Many of these ideas will be passing ideas and you soon move on to the next idea. If you were intent on doing something about the idea you would begin. If you don't begin, it's likely a passing idea.  These passing ideas are the gold you do not want to delete. They could contain the seeds of something very special. However, on their own, they may seem redundant after a few weeks or months. It's these notes you want to keep in your archive.  In a year or two, you may feel compelled to skim through one of your archive years, and you begin to see connections between all these ideas. Leonardo Da Vinci, sketched the mouth he eventually gave the Mona Lisa twelve years before he began painting the Mona Lisa.  Individually, these notes may mean nothing. But together, they could be your next great idea.  So, Susan, look at what you want to collect and save. Keep your projects together, these you will be working on frequently. And all those random notes you collect, store them in archives by year. As these build, you will be creating a gold mine of ideas and thoughts you will never regret keeping.  I hope that has helped and thank you for your question. And thank you to you, too, for listening. It just remains for me now to wish you all a very, very productive week.   

Martin Adams is ecommerce entrepreneur and content creator trying to inspire the next generation of thinkers and doers. He makes content on Personal Knowledge Management as well as content on mindset and mastery. He's also creating Flowtelic, an app to help you study, learn, think, write, and publish with maximum efficiency and consistency. And he recently published his book Atomic Notetaking: The Ultimate Zettelkasten Guide.In this podcast you will learn:How to find joy in your Personal Knowledge ManagementHow to become a more critical thinkerHow to come to genius insights with your ZettelkastenMY FREE ONLINE COURSES:

“Los juegos de palabras amasan realidades” – Karla Paniagua (

A philosopher programmer who specializes in back-end development and stoicism. His biggest project right now is creating a MINDOS, a mental operating system which he's doing in public through his newsletter. He's recently published a book called Zettelkasten And The Art Of Personal Knowledge Management. In this podcast you will learn:- How to supercharge your learning with the Zettelkasten system- How to upgrade your journaling with the Zettelkasten- The future of AI and the ZettelkastenMY FREE ONLINE COURSES:

The world is changing fast. Technology can be used to empower us -- and also to hack our brains & our lives. What laws do we need to protect our freedoms? Rahul Matthan joins Amit Varma in episode 360 of The Seen and the Unseen to share his work on privacy -- and on a new, subtle approach towards data governance. (FOR FULL LINKED SHOW NOTES, GO TO SEENUNSEEN.IN.)   Also check out: 1. Rahul Matthan on Twitter, Instagram, LinkedIn, Trilegal, Substack and his own website. 2. Privacy 3.0: Unlocking Our Data-Driven Future -- Rahul Matthan. 3. The Third Way: India's Revolutionary Approach to Data Governance -- Rahul Matthan. 4. The Life and Times of KP Krishnan -- Episode 355 of The Seen and the Unseen. 5. Sudhir Sarnobat Works to Understand the World -- Episode 350 of The Seen and the Unseen. 6. Roam Research. 7. Zettelkasten on Wikipedia. 8. Tana, Obsidian and Notion. 9. Getting Things Done -- David Allen. 10. The Greatest Productivity Mantra: Kaator Re Bhaaji! -- Episode 11 of Everything is Everything. 11. Hallelujah (Spotify) (YouTube) -- Leonard Cohen. 12. Hallelujah (Spotify) (YouTube) -- Jeff Buckley. 13. The Holy or the Broken: Leonard Cohen, Jeff Buckley, and the Unlikely Ascent of "Hallelujah" -- Alan Light. 14. Hallelujah on Revisionist History by Malcolm Gladwell. 15. Bird by Bird: Some Instructions on Writing and Life -- Anne Lamott. 16. The New Basement Tapes. (Also Wikipedia.) 17. Kansas City -- Marcus Mumford. 18. The Premium Mediocre Life of Maya Millennial -- Venkatesh Rao. 19. Vitalik Buterin Fights the Dragon-Tyrant — Episode 342 of The Seen and the Unseen. 20. Paul Graham on Twitter and his own website. (His essays are extraordinary.) 21. Ribbonfarm by Venkatesh Rao. 22. The Network State --  Balaji Srinivasan. 23. Marc Andreessen on Twitter. 24. The Techno-Optimist Manifesto -- Marc Andreessen. 25. Siddhartha Mukherjee and Carlo Rovelli on Amazon. 26. For the Lord (Spotify) (YouTube) -- Rahul Matthan. 27. Predicting the Future -- Rahul Matthan (on Asimov's concept of Psychohistory etc). 28. Gurwinder Bhogal Examines Human Nature — Episode 331 of The Seen and the Unseen. 29. The Looking-Glass Self. 30. Panopticon. 31. Danish Husain and the Multiverse of Culture -- Episode 359 of The Seen and the Unseen. 32. A Scientist in the Kitchen — Episode 204 of The Seen and the Unseen (w Krish Ashok). 33. We Are All Amits From Africa — Episode 343 of The Seen and the Unseen (w Krish Ashok and Naren Shenoy). 34. Nothing is Indian! Everything is Indian! — Episode 12 of Everything is Everything. 35. The Right to Privacy -- Samuel D Warren and Louis D Brandeis. 36. John Locke on Britannica, Stanford Encyclopedia of Philosophy, Wikipedia and Econlib. 37. Build for Tomorrow -- Jason Feifer. 38. Ex Machina -- Alex Garland. 39. Arrival -- Denis Villeneuve. 40. The Great Manure Crisis of 1894 -- Rahul Matthan. 41. Climate Change and Our Power Sector — Episode 278 of The Seen and the Unseen (w Akshay Jaitley and Ajay Shah). 42. The Book of Why: The New Science of Cause and Effect -- Judea Pearl. 43. The New World Upon Us — Amit Varma on Alpha Zero. 44. Brave New World -- Vasant Dhar's podcast, produced by Amit Varma. 45. Human and Artificial Intelligence in Healthcare -- Episode 4 of Brave New World (w Eric Topol). 46. The Colonial Constitution -- Arghya Sengupta. 47. Beyond Consent: A New Paradigm for Data Protection -- Rahul Matthan. 48. The Puttaswamy case. 49. Judicial Reforms in India -- Episode 62 of The Seen and the Unseen (w Alok Prasanna Kumar.) 50. Accidental Feminism: Gender Parity and Selective Mobility among India's Professional Elite --  Swethaa S Ballakrishnen. 51. Magic Fruit: A Poetic Trip -- Vaishnav Vyas. 52. Hermanos Gutiérrez and Arc De Soleil on Spotify. 53. The Travelling Salesman Problem. 54. The Twenty-Six Words That Created the Internet -- Jeff Kosseff. 55. Code: And Other Laws of Cyberspace -- Lawrence Lessig. 56. Financial Inclusion and Digital Transformation in India -- Suyash Rai. 57. No Time for False Modesty -- Rahul Matthan. 58. In Service of the Republic: The Art and Science of Economic Policy -- Vijay Kelkar and Ajay Shah. 59. Once Upon a Prime -- Sarah Hart. 60. The Greatest Invention -- Silvia Ferrara. 61. Surveillance State -- Josh Chin and Liza Lin. 62. Surveillance Valley -- Yasha Levine. 63. Sex Robots and Vegan Meat -- Jenny Kleeman. 64. How to Take Smart Notes -- Sönke Ahrens. 65. The Creative Act -- Rick Rubin. 66. How to Write One Song -- Jeff Tweedy. 67. Adrian Tchaikovsky and NK Jemisin on Amazon. 68. Snarky Puppy. on Spotify and YouTube. 69. Empire Central -- Snarky Puppy. 70. Polyphia on Spotify and YouTube. 71. The Lazarus Project on Jio Cinema. This episode is sponsored by the Pune Public Policy Festival 2024, which takes place on January 19 & 20, 2024. The theme this year is Trade-offs! Amit Varma and Ajay Shah have launched a new video podcast. Check out Everything is Everything on YouTube. Check out Amit's online course, The Art of Clear Writing. And subscribe to The India Uncut Newsletter. It's free! Episode art: ‘Protocol' by Simahina.

The Zettelkasten Method is often over-complicated. Discover an easier, faster and more memory-friendly Zettelkasten system now.

Theo Stowell is a Uni Student and full-time content creator. He has created a custom PKM system mixing together Tiago's PARA framework with the Zettelkasten developed by Nikolas Luhman into PARAZETTEL. Now he's sharing his learnings about Personal Knowledge Management, and his journey in content creation and self-actualization online.In this podcast you will learn:- How to boost your creativity and get things done with Theo's custom-made PARAZETTEL system- How to balance content creation and schoolwork- How to create a PKM system that works for youTheo's Twitter: https://x.com/fundamentalised?s=20Theo's Parazettel Course: https://fundamentalised.ck.page/parazettelMY FREE ONLINE COURSES:

Easily listen to The Science of Self in your podcast app of choice at https://bit.ly/ScienceOfSelfPodcast00:02:58 In 1885, German psychologist Hermann Ebbinghaus published a groundbreaking study on memory and learning.00:07:51 Gather and Capture00:10:51 William James, author of The Principles of Psychology, discussed habits and their importance in achieving happiness and success.00:14:11 Organize What You've Captured 00:32:05 Chapter TakeawaysHear it Here - https://adbl.co/3KWyCB0• Personal knowledge management (PKM) is a set of processes that a person uses in their daily activities to collect, categorize, store, search for, retrieve, and share knowledge.• Creating a "capture habit" is the first step in personal knowledge management, which is important for lifelong learning and freedom. A capture habit involves quickly saving any helpful or inspiring information or ideas that are come across. This can be done by setting up Google Alerts, subscribing to RSS feeds, following social media accounts, etc.• Once information is gathered, it needs to be properly labeled and organized using a system that makes sense for the task at hand. This will make it easier to find later on when needed. The goal is to make your life easier by understanding and implementing the techniques learned from gathering this information.• The Zettelkasten method is a notetaking system developed by German sociologist Niklas Luhmann that helps you capture ideas and connect them with one another. It has three essential elements: slips of paper, a filing system, and a mind map. The slips of paper are used to record ideas, thoughts, and information, which are then sorted into different categories and filed accordingly. • The mind map is used to visualize the relationships between different ideas. In order to make connections between concepts, you can use special strategies like bridge notes or progressive summarization. Bridge notes can be used to connect ideas, index notes to organize ideas, and topic notes to group relevant information or notes together.#ABCMethod #ACCEPTS #ACT #ActionCommitmentTherapyACT #AnthonyDoerr #Aurelius #BreneBrown #PKM #RussellNewton #NewtonMG #PeterHollins #TheScienceofSelf

Welcome to Strange Rare Peculiar, a weekly podcast with Denise Straiges and Alastair Gray of the Academy of Homeopathy Education discussing everything you REALLY need to know about homeopathy. We'll look at philosophy, practice, research, and education–all with a little bit of history. If you want to know why we still can't get enough homeopathy after a combined 50+ years of study and practice, we invite you to join the conversation!  Please help us spread the word by sharing this with someone in your life who would like to learn more about homeopathy.  In this week's episode, we dive into… Staycations & Catch-Upcations Nerds make great homeopaths. The Zettelkasten method of notetaking. Educating polymaths How we minimize anxiety by previewing, doing and reviewing. Helping students learn to master information management.  The reason our students start chronic Clinic in their first weeks of school.  If you'd like to study homeopathy, visit: https://academyofhomeopathyeducation.com/ To support homeopathy research and help make homeopathy accessible to all, visit: https://hohmfoundation.org/ For accessible homeopathy care, visit:  https://homeopathyhelpnow.com/ About Denise Straiges: Denise Straiges MA, CCH, RSHom(NA), PCH is fiercely committed to raising the bar in academic and clinical training for all Homeopaths. She is the President and Clinical Director of The Academy of Homeopathy Education (AHE) and established HOHM Foundation, whose initiatives include the Homeopathy Help Network, a not-for-profit, research-based initiative focused on delivering high-quality, affordable Homeopathy care to all. Under her leadership, AHE was named the preferred educational provider for the American Institute of Homeopathy (AIH), the oldest medical society in the US Denise has taught for numerous homeopathy schools in the US and abroad and has been an invited speaker at conferences around the world in homeopathy, integrative wellness, and spirituality in medicine. She is currently pursuing graduate studies at Johns Hopkins University School of Medicine. Her work includes original, primary research focused on the origins of homeopathy, in particular, Hahnemann's influences in The Chronic Diseases and the evolution of potency. She is writing a practical, in-depth compendium on Case Analysis.     --- Send in a voice message: https://podcasters.spotify.com/pod/show/srp-podcast/message

King a content creator on with over five years of experience on YT who embarked on a transformative journey to revolutionize his content creation process. Balancing the demands of a full-time job, a growing family of two boys and a wife, and a desire to fulfil his creative potential, King sought out effective strategies to streamline his content production. After experimenting with various methods, he stumbled upon the zettelkasten system, delving deep into Niklas Luhmann's original paper and distilling its complex principles into practical strategies. After 300+ hours of applying Luhman's principles, he has built the Obsidian Zettelkasten Starter Guide to help creators go beyond regurgitating content.In this podcast you will learn:What a Zettelkasten isHow you can become more prolific and creative using itBiggest Zettelkasten beginner mistakesKing twitter: https://twitter.com/kinginmotionMY FREE ONLINE COURSES:

ノートと万年筆、ホドロフスキーのDUNE、流・式・発・国産について、パズルとボルダリング、帯状疱疹とurgent care、SF6観戦のすすめについて話しました。Shownotes amazonのミーティング Notion ピクシブでのNotionのつかいかた TAIYAKI NYC … なんというあられもない姿 66. Weaving a web of ideas (Researchat.fm) … “アイデアとノートの取り方、ノートの変遷、Zettelkasten (ノート作成方法)について話しました。” Moleskin ロイヒトトゥルム1917 …Moleskinもこれも値段上がりすぎじゃないか…??? Zettelkasten 新しいデジタルノート術で第二の脳を作ろう　… notionに限らずデジタルノートの扱い方について。zettelkastenについても言及があります。 LAMYのsafari 万年筆のインク　… 皆さんおすすめをおしえてください。 カヴェコ WATERMANの万年筆 … 高い…!!! Smith-Waterman algorithm … DNAをアラインメントするアルゴリズム スタンフォードの人気教授が教える 「使える」アイデアを「無限に」生み出す方法 … この激烈に惹かれないタイトル ホドロフスキーのDUNE 魂の戦士 ロットリング600 北辰一刀流 示現流 … 六三四の剣で日高に憧れたのは私だけではないはず モンテッソーリー … みんな大好きなやつ。 国産CRISPR 159. Gordian Knot (Researchat.fm) … パズル回 パズルの話半分 … パズルの話を堪能しまくれる最高のポッドキャスト ダイアゴナル … キョン、フラッギング、ヒールフック、などなどを覚えながら地味にやっている。行っているジムだとV1は大体できるようになって、V2に挑戦中。 Boston Bouldering Project … 最高 帯状疱疹 … みんな気をつけよう。 緊急 … ER, 緊急じゃなくて救急 SF6 … 過去最高傑作との呼び声も高い。 篠原涼子 with t.komuro / 恋しさと せつなさと 心強さと 2023 Researchat Dojo Reject Fight Night REJECT … ときど選手加入！ Crazy Raccoon Cup Street Fighter 6 … この大会は盛り上がりすぎてやばかったですね。最後のウメハラ選手の締め方も最高でした。 赤見かるび … 正直にいってハマっている。 ずんだもん … 関係ないが、ずんだもんにもはまっている… Redbull Kumite 2023 背水の逆転劇 … Let's GO! Justin! 千裂脚 -> 鳳翼扇 3. Here Comes A New Challenger!(Researchat.fm) … “eスポーツ、EVO JAPAN 2019、パキスタン勢とArslan Ash、eスポーツと渡航ビザ問題、格ゲー動画勢の楽しみ方、eスポーツの解説とサイエンスコミュニケーション、ウメハラの攻略法、サムライスピリッツの新作、おすすめのマンガ情報について話しました.” Arslan Ash Gamers8 … サウジアラビアで行われる大会 鉄拳はArslan Ash率いるパキスタンの優勝 evo2023 cpt SFL 東大式小パン ここから下はcoelaがそのうちに編集します。 モダン入力 クラシック入力 daigo umehara haitani sako fudo momochi dogura go1 nemo 小路KOG … CR cupの後に何かの沼に自ら頭の先まで浸かってしまい、自分の切り抜きを見るという新技まで開発し、もっとも勢いのある格ゲープレイヤーとなっている伝説の人(現在進行形)。twitchの小路さんの視聴者数が最初はバグかとおもうぐらい(失礼)跳ね上がっており、何が起こったのかと思った。 ときどさん えいたはプロゲーマーになれるか一緒に考えよう … プロゲーマーについて必要なことについてえいた選手にウメハラ選手が語った伝説の回。 種田山頭火 Editorial Notes (coela) すいません、メチャクチャすでに試合が行われてしまいました… SF6の盛り上がりやばい。(tadasu)

Okumanın kutsal öğretilerine, CIA'in bilmenizi istemediği sırlarına kaldığımız yerden devam. Bugün işin teknik taktik kısmına dalacağız, pratiklerine bakacağız.Konular:(00:00) Geyik: Ağustos böcekleri. (02:10) Okumak diyaloga girmektir. (02:50) Beklentileriniz yazın. (03:27) Kitabı mundar edin. (04:33) Özet çıkarın. (07:00) Hiyerarşik not tutmayın. (08:35) Not kartları kullanın. (11:00) Commonplace Book. (11:50) Zettelkasten. (15:22) A Syntopicon (Patreon). (16:33) Hızlı Okuma Teknikleri. (18:00) Subvocalization: İç Seslendirme. (19:00) Kurgu Nasıl Okunur. (22:54) Patreon teşekkürleri. .Kaynaklar:Patreon: A Syntopicon: Kimsenin Bilmediği En Önemli KitapVideo: Ryan Holiday's 3-Step System for Reading Like a Pro Yazı: A Beginner's Guide to the Zettelkasten MethodYazı: IMPLEMENTING ZETTELKASTEN IN ROAM: A PRACTICAL GUIDEKitap: Great Books of the Western World (1952)Kitap: A Syntopicon (1952)Yazı: How subvocalization makes you a better readerYazı: HOW TO START READING FICTION (WHEN YOU ONLY READ NONFICTION)Yazı: How To Read A Book (Of Fiction), According to Mortimer J. AdlerSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Oliver Burkeman discusses with Ivan six things which should be better known. Oliver Burkeman is the author of the New York Times and Sunday Times bestseller Four Thousand Weeks, about embracing limitation and finally getting round to what counts, along with The Antidote: Happiness for People Who Can't Stand Positive Thinking and Help! How to Become Slightly Happier and Get a Bit More Done. For many years he wrote a popular column for the Guardian, 'This Column Will Change Your Life'. In his email newsletter The Imperfectionist, he writes about productivity, mortality, the power of limits and building a meaningful life in an age of distraction. He lives in the North York Moors. The Zettelkasten https://zenkit.com/en/blog/a-beginners-guide-to-the-zettelkasten-method/ Death: The End of Self-Improvement by Joan Tollifson https://www.joantollifson.com/book-death-the-end-of-self-improvement.html The fact that everyone is just winging it https://www.theguardian.com/news/oliver-burkeman-s-blog/2014/may/21/everyone-is-totally-just-winging-it Rosedale Chimney Bank and Spaunton Moor https://www.walkingbritain.co.uk/walk-1921-description "Ought implies can" https://platofootnote.wordpress.com/2016/06/13/ought-implies-can-or-does-it/ This Jungian Life https://thisjungianlife.com/ This podcast is powered by ZenCast.fm

Josh Duffney is a software engineer, writer, and speaker as well as the author of How to Take Smart Notes in Obsidian and Become Ansible. He records YouTube videos about technology, productivity, and personal knowledge management.In this podcast, you will learn:Why the Zettelkasten notetaking system can fail...How to take dumb notes over smart notesHow AI will change notetakingMY FREE ONLINE COURSES:

Do you enjoy the shamelessly fringe? How about this podcast? We want to hear your voice in all it's weirdo glory! Go to ratethispodcast.com/openloopsYou may have noticed there's a gold rush of AI opportunities. Instant video creation, real-time art generation, copywriting without human touch. ChatGPT, MidJourney, OpenAI, Bard, and even Microsoft Bing (no one saw that one coming) are the future of work, art, and life. Why? Because they are the cutting edge of the Singularity.  That's right. We're talkin' AI.  In this very special extended episode of Open Loops, Master Hypnotist and Agent of Change James Tripp returns to discuss the evolution of humanity's consciousness as it gets outpaced by the never-ending revolution of artificial intelligence.  Bottom-line, there's a gold rush.  But remember, if gold suddenly shows up everywhere as a resource...what's it actually worth?James told Greg he had thoughts on this very topic TOO CONTROVERSIAL for his audience.  ....But not for this show!  And when he brings the Frankfurt School, universal income, and fall of SUCCESS for entrepreneurs, consultants, coaches and hypnotherapists...let's just say there's nothing held back in the mind-bending conversation about the AI overwhelm in abundance of 2023.They cover:  (0:00:13) - Artificial Intelligence and Creativity(0:14:57) - The Challenges of Authentic Coaching(0:22:41) - Hypnosis and Chat GPT Temptation(0:26:22) - Making Money With Shiny Object Side Hustles(0:39:58) - Finding Fulfillment Outside of Societal Expectations(0:55:00) - The Bleak Future With AI(1:07:54) - Creativity and Self-Development(1:13:49) - Myths of Decision-Making and Worthiness(1:26:50) - Psychotherapy and the Power of Belief(1:30:31) - Neurolinguistics and Language Intelligence(1:47:28) - Exploring the Limits of AI Modeling(2:01:30) - The Importance of Generative Communication(2:13:21) - Organizing Information With Zettelkasten and Your Second Brain(2:22:44) - Criticism, Creativity, and AI PlagiarismIt's a long episode, but we're pretty sure some bot already replaced you at your day job anyways, so you've got the time for this audio journey like none other....it's Open Loops.  James's Links: Find everything James Tripp on his Substack here at https://jamestripp.substack.com/ 

In this final episode of The Sketchnote Army Podcast season 13, we've gathered all the tips from 9 fantastic visual thinkers to inspire you!Sponsored by ConceptsThis episode of the Sketchnote Army Podcast is brought to you by Concepts, a perfect tool for sketchnoting, available on iOS, Windows, and Android.Concepts' vector-based drawing feature gives you the power to adjust your drawings — any time you like. You can nudge the curve of a line, swap out one brush for another, or change stroke thickness and color at any stage of your drawing — saving hours and hours of rework.Vectors provide clean, crisp, high-resolution output for your sketchnotes at any size you need — large or small. Never worry about fuzzy sketchnotes again.Concepts is a powerful, flexible tool that's ideal for sketchnoting.SEARCH “Concepts” in your favorite app store to give it a try.Running OrderIntroKatrin WietekFilippo "Sketchy" BuzziniEric BakeyMaria Coryell-MartinJulia KnyupaTy HatchMawusi AmoakuEdmund GröplNatalie TaylorOutroLinksKatrin's WietekFilippo "Sketchy" BuzziniEric BakeyMaria Coryell-MartinJulia's KnyupaTy HatchMawusi AmoakuEdmund GröplNatalie TaylorKatrin's TipsPick a project you are really excited about.Don't compare yourself to othersDon't overcomplicate things. Don't overcomplicate sketchnoting.Don't overvalue talent.Filippo's TipsBarter your services.Ask your colleagues, connect, share, and give.Prepare your title ahead.Use Post-it notes.Eric's TipsWhat problem are you trying to solve, who is it for, and what is the value of solving that problem?Where are you right now and where do you want to go?Be useful, resourceful, and know your five-mile famous world.Maria's TipsUse a timer and set yourself a very small amount of time to do something.Give yourself the opportunity to play with color, what you see, and don't worry about composition.Paying attention to the world and just letting yourself start with notes just to start that attention.Trust the process.Practice not perfection.Julia's TipsFake it till you make it.Work-life balance. Just continue learning every day, getting inspiration from everywhere, from your colleagues, traveling, and following people from different industries.Authenticity is the most important value nowadays so allow yourself to be yourself and be very kind o yourself.Ty's TipsEverybody is creative in their own way, and that's okay.Enjoy what you do. You can like a range of different things, and that's okay.Set boundaries for the things that are really important to you, in your life that are not work-related. Set those boundaries, talk about them, and live your life in a way that reflects your priorities.Mawusi's TipsContinue feeding your mind.Even if you go digital, keep drawing by hand.Don't overthink it. Just do it.Be open to trying something new.Listen to other sketchnoters.Share your work.Experience with other layouts, find out what works for you.Collaborate with your colleagues.Ask for feedback.Be intentional and tell someone your goal.Don't give up. Be patient.Edmund's TipsBenefit from self-organized learning groups.Attend a LernOS sketchnoting circle.Zettelkasten with Obsidian is your second brain for sketchnoting.Take useful notes!Natalie's TipsInvest and improve in what you love.Recognize what is your strength. Focus on your strength as you try and improve your weaknesses.Share your work.Write down your ideas.Get involved with the community.CreditsProducer: Alec PulianasTheme music: Jon SchiedermayerShownotes and transcripts: Esther OdoroSubscribe to the Sketchnote Army PodcastYou can subscribe to the podcast through iTunes, Google Podcasts, Spotify, Amazon Music, YouTube or your favorite podcast listening source.Support the PodcastTo support the creation, production and hosting of the Sketchnote Army Podcast, buy one of Mike Rohde's bestselling books. Use code ROHDE40 at Peachpit.com for 40% off!

Bob Doto, for the past 20 years, has worked with writers, spiritual aspirants, yogis, teachers, knowledge workers, teaching courses on Zettelkasten, PKM, social media, and spirituality. He is a past mentor on Building a Second Brain. Bob has been blogging since 2003 and publishing zines on and off since the early 90s. He's the author of four books and writes a newsletter called the High Pony which features weekly insights on the creative process, spiritual practice, personal knowledge management, and productivity.In this podcast you will learn:How spirituality connects with PKM and The Zettelkasten method of notetakingHow to overcome the two biggest problems of starting in PKMHow to use your PKM system for creative insightMY FREE ONLINE COURSES: 

In ihrem ersten Roman erzählt die 25-jährige Schweizer Autorin Mina Hava in Bruchstücken von einer jungen Frau, ihrer Familie, den bosnischen Wurzeln und dem Wunsch nach einem Platz in der Welt. In einer Achterbahn der Eindrücke und Gefühle sucht sie dabei im Grossen und Kleinen nach Zusammenhängen. Mina Hava studierte am Literarisches Schreiben am Deutschen Literaturinstitut Leipzig und danach Globalgeschichte und Wissenschaftsforschung an der ETH Zürich. Sie ist gleichermassen Künstlerin und Forscherin und legte ihren Roman als riesigen Zettelkasten an. Weltpolitik, Wirtschaftsgeschichte, längst vergessene oder überlagerte Konflikte mischen sich darin mit privaten Erzählungen und ergeben faszinierende Muster. Im Gespräch live von den Solothurner Literaturtagen erzählt Mina Hava von der Entstehung und den Hintergründen ihres ersten Romans. Buchhinweis: Mina Hava. Für Seka. 277 Seiten. Suhrkamp Verlag.

In this episode, Edmund Gröpl, a retired engineer, discovers how life is often circular. He shares his in-depth knowledge of Zettelkasten (card file in German) and how he links sketchnotes using Obsidian. Edmund shares how he is integrating Zettlekasten and sketchnotes in a new book.Sponsored by ConceptsThis episode of the Sketchnote Army Podcast is brought to you by Concepts, a perfect tool for sketchnoting, available on iOS, Windows, and Android.Concepts' vector-based drawing feature gives you the power to adjust your drawings — any time you like. You can nudge the curve of a line, swap out one brush for another, or change stroke thickness and color at any stage of your drawing — saving hours and hours of rework.Vectors provide clean, crisp, high-resolution output for your sketchnotes at any size you need — large or small. Never worry about fuzzy sketchnotes again.Concepts is a powerful, flexible tool that's ideal for sketchnoting.SEARCH “Concepts” in your favorite app store to give it a try.Running OrderIntroWelcomeWho is Edmund?Origin StoryEdmund's current workSponsor: ConceptsTipsToolsWhere to find EdmundOutroLinksAmazon affiliate links support the Sketchnote Army Podcast.Edmund on LinkedinEdmund on InstagramEdmund on TwitterEdmund's eBookLinktreeBook: Zettelkasten by Niklas LuhmannHow To Take Smart NotesThe Back of the Napkin by Dan RoanWriting Useful Books by Rob FitzpatrickThe Sketchnote Handbook by Mike RohdeThe Sketchnote Army PodcastToolsAmazon affiliate links support the Sketchnote Army Podcast.Neuland markersStaedtler markersiPad ProApple PencilConceptsMiroObsidianPowerBITipsBenefit from self-organized learning groups.Attend a LernOS sketchnoting circle.Zettelkasten with Obsidian is your second brain for sketchnoting.Take useful notes!CreditsProducer: Alec PulianasTheme music: Jon SchiedermayerShownotes and transcripts: Esther OdoroSubscribe to the Sketchnote Army PodcastYou can subscribe to the podcast through iTunes, Google Podcasts, Spotify, Amazon Music, YouTube or your favorite podcast listening source.Support the PodcastTo support the creation, production and hosting of the Sketchnote Army Podcast, buy one of Mike Rohde's bestselling books. Use code ROHDE40 at Peachpit.com for 40% off!Episode TranscriptMike Rohde: Hey everyone, it's Mike, and I'm here with my friend Edmund Gropl. Edmund, how are you?Edmund Gropl: Hello, Mike. Nice to see you. And I put one sentence on paper. Thank you so much for having me.MR: You're so welcome. I'm glad to have you. I'm excited because I know that you're really into this intersection between Zettelkasten and sketch notes. I'm really curious to hear in the section where we talk about current projects, where you're at with that. Because I think one of the things that I struggle with is I produce lots of sketch notes, but the challenge I find is organizing them in a logical way.I think your episode, your interview with us may be really helpful for me to think about how do I do that in a good way. I've got some fits and starts. I'm really personally looking forward to learning and getting some ideas from you. Before we get to that, let's start first with who you are and what you do.EG: Hello, my name is Edmund. I'm here from Germany, living in the Frankfurt area. To make it short, I'm a husband, I'm a father, and I'm a grandfather.MR: Congratulations.EG: Thank you. Thank you very much. Husband since 41 years, father then 33 years, and a grandfather since 10 months.MR: Wow.EG: Both three are really exciting.MR: Well, then congratulations to you for setting an example for us for consistency and reliability, and loyalty. It's always good to see those qualities in people because we need that. We need those models and examples to follow. Talk to us a little bit about, you mentioned to me that you were an engineer. I don't know much more about that. Why don't you talk a little bit about your time as an engineer and your specialty and what was interesting to you in the work that you did?EG: If you're in business, it's very important to talk about your profession, about being an engineer. Since two years, I'm retired, and therefore I have a lot of time and I have my head free thinking for my own, not for the company, not for the customers. It's exciting, what is changing. Is it the same as I did years ago as an engineer, or is there's some new stuff?What I didn't expect that it's a really new phase in life, redefining yourself, and you are not a retired engineer. You are your person as your own. If I look at my hobbies, I love swimming, climbing, drawing, going outside, and so, and these are my hobbies. and it's all the stuff I mostly liked when I was a child.MR: Interesting.EG: Yes. It was climbing on trees. it was playing outside, it was swimming in the gym with my parents, it was drawing, not mathematics, and all the other stuff which came important to me afterwards. That's back to the roots and life seems to be a little bit like a mirror to see what was at the beginning comes back at the end.MR: Rediscovering childhood in a way.EG: Yeah. I didn't read it in a book, and it was not a plan. I had no idea what I would do as a retired engineer, but that was it. In the last years, I was working for a big company as a data scientist. I came here from Darmstadt near Frankfurt, and here it was the time when I came as a young man studying software and systems engineering.Therefore, my head is all full with these engineering tools and concepts and methods and all this way of thinking. Sketchnoting was for me, very surprising to get in contact with all the other guys worldwide. Artists, illustrators' facilitators, and so on and so on. It was really an enrichment of my life to have contact with different people with different professions and so on.That's in short to say about my life. It was one year ago. Do you remember, Mike? It was in March last year. There was a session from you in the internet about sketchnoting, in March 3rd or so?MR: Interesting. It's not one that comes to mind.EG: Eventbrite was the platform where you announced it.MR: It must have been interesting. That must have been—oh, that's a good question. We'll have to look and see. On the top of my head, I don't remember. The reason is there's been so many events that I've been doing that it's not surprising that I don't remember what it was.EG: I was really happy that I could watch your presentation about sketchnoting, about drawing, and all this stuff. Real life, it was Mike, personally. It was not a book, it was you in person. There were a lot of visitors in your presentation. There was this chat by, near all these pictures, and there was one of the participants from New York City. Her name was—there was only a short form, Caroline New York City and she posted Zettelkasten and Sonke Ahrens.I thought, okay, it was a session for Mike Rohde, it's about sketchnoting, there's some new stuff about sketchnoting. I have a whole bunch of literature about sketchnoting. I think all the books of all sketchnoters worldwide in different languages are on my bookshelf. I said, okay, Zettelkasten, it must be amazing. I bought this book, let me show you. It's a Kindle book, "How to Take Smart Notes."MR: Interesting.EG: Yes. Sketchnotes, smart notes, smart sketch notes. I started reading, and I was disappointed.MR: It was all text.EG: Yes. It's only text. The whole book is full of text. No sketchnotes at all.MR: Interesting.EG: And it was about note-taking. Then this boring stuff at the beginning, because only text, I said, okay, if it's not said what is the best way for note-taking, and I translate it in what is the best way for sketchnote taking or taking sketchnotes. I read all this book about note-taking with a sketchnote metaphor in mind, and that was an amazing book.This book from Sonke Ahrens it's not written from an engineer or from a writer, it's a German sociologist as well as this Niklas Luhmann. Let me say in short, who invented this Zettlekasten method.Sonke Ahrens explained it in his own language, and it's an amazing stuff. It's worth reading twice or three times this book. It's about 250 pages. What I learned reading one book about sketchnoting is not okay. I read the book, I'm now a sketchnoter.It needs a lot of practice. With the note-taking, it's the same as taking sketchnotes, it needs a lot of practice, but you need to know a lot of principles behind, and I say hidden principles. In the first moment, you couldn't see these principles.Mike, I looked at your book first. It was amazing, the sketchnotes, the ideas, but it needs maybe one or two years, I came back to your book and say, okay, now I understand it. You have no chance to understand it from the beginning. With note-taking, it's nearly the same.That is my hobby since one year. Since your online session about sketchnoting. To mix it a little bit up to say, okay, that's Sonke Ahrens and that's the Mike Rohde, put it together and that's my hobby since nearly one year. 362 days is my Zettlekasten hobby.MR: I had no idea that a workshop that I was teaching had sparked you along this path. That's really exciting to hear. That's pretty cool.I know we're gonna talk more about what Zettelkasten is, how you've overlapped it or integrated it with sketchnoting, but I think I wanna go back. We've gone back one year to last March.Now, let's go back to when you were a kid, and as you grew up in school and as you went to university, and as you worked in business as an engineer. I'm really curious, what were the moments in time, because you talked about when you were a kid, you liked drawing and now here you are again at the end drawing again in retirement years.What was it that kept drawing alive? Or maybe it didn't stay alive and it had to be resurrected later. Talk about your path from a little boy to now. What were those key moments that brought you to where you are now?EG: It's not drawing as a child, as a senior citizen, or so. It's at school first. I loved drawing most. Then they said, "Drawing is for small children. You are growing up and the really intelligent and clever ones, they can write and they can calculate. Drawing is only for the small ones."But that was at the beginning of the school, but in mathematics, there are also some specialties where you can draw with a pencil, with a ruler, with a circle. It's not freehand drawing, but it's visual. I learned in mathematics also in physics, that all the visual stuff was for me, easy to understand.For example, I'm really good in mathematics and physics and chemistry, for example. There was a lot of stuff I had to learn by heart that was not my idea. The visualization of elements, it was a little bit boring. Mathematics and physics was much more exciting too. In physics, to draw the experiments from the teacher on the sheet of paper and to say, okay, that's the motor, that's the battery and have it with symbols and the wires you can draw.This physical stuff was the way I learned. That was also a reason for becoming an engineer. Engineering is also stuff with drawings there. There are concepts, there are diagrams, all this visual stuff, and that helps a lot. Coming in my professional life, after I was a systems engineer from university, I had to communicate with others, with the colleagues, with my boss, with the customers.Then my drawings were these engineer drawings. I would not like to explain it too much in words. I will draw this system. We want to sell you this system that solves your problem, and so on. Or this process diagrams, flow diagrams and all this stuff. That was all visual. Therefore, I'm sure there are different styles of thinking maybe we are all born with. If you're more visual thinker, it's easier to become an engineer or an architect, and it's easier than to become a lawyer or something like this.MR: I know the physicist that I've spoken with Rob Dimeo and others who talk about physics is really dependent on visuals, and so, they find it a real natural companion to sketchnoting, which is pretty interesting that you mentioned it as well.EG: That's the side when I came to sketchnoting—and let me show you one book, I think one of my first sketch noting book was from Dan Roam.MR: "The Back of the Napkin." Yep. Great book.EG: It was a lot about the concepts itself. And I understand the concepts with a mind of an engineer, but years later, after Dan Roam, that was your book, I had a sketchnoting workshop over five days learning sketchnoting from a guy from Berlin, if I remember, Dick Hanaman.MR: Dick Hanaman. Okay.EG: Dick Hanaman from Berlin, he's giving sketchnoting workshops.MR: Great.EG: That was one of the books he recommended. With this book and with this workshop, I learned the stuff behind it, what does it mean to draw a line in this or in this way, why are there thicker and thinner lines, how to focus the attention on a special part of the drawing, and that was not in this book. Then came the book of Mike Rohde. I was happy to understand after years what drawing really means. I was working for a big company with more than 200,000 employees.MR: Oh, wow.EG: There's an internal platform or an internal community of self-organized learning. If you have some interesting stuff in engineering, in whatever, in the internet, you can post that you will held a session via Zoom or a special tool to show others, oh, there's interesting stuff for you about databases, proclaiming, and so on. And I offered Sketchnoting sessions, and it was two weeks after my first sketchnoting workshop and I held this session with 400 colleagues.MR: No pressure. Edmund, no pressure.EG: It was a feeling like flying in the air.MR: Wow.EG: I was able to draw a sticky man and write my name on paper. It was not only one session, it was repeatable. Week after week. That was really a nice feeling to say, oh, that's the right direction, and therefore I banned all my PowerPoint from my presentations, used the flip chart with the Neuland markers. It is the only ones I can use because I can use them for drawing and for writing. If the paper is white, the pen is black. What we had in the company before was you can't use this stuff. I always had my own Neuland markers with me.MR: Me too.EG: And the corporate material or markers most times they were old, two or three years old.MR: Dry.EG: Dry. You have to throw them away. That was it all with Neuland. Also, as an engineer, drawing on a whiteboard, it was the same with the dry markers years before, but with the Neuland markers for the whiteboard, I was the king. If we had a meeting, blah, blah, blah, this and this. Then Edmund uses his Neuland marker, went to the whiteboard, and explained how it works.MR: What we just talk about, Edmund would visualize it for you.EG: Yeah. It was amazing. It was all I think a little bit by excellent. It was not planned in my career.MR: Organic, maybe a good way to describe it, which is always good because you follow it because it's interesting. You didn't follow it because somebody told you to, or you had to because of your job. You did it because you were interested and you came to love it, it seems like.EG: Most of the stuff by accident, and what was the term I got from the internet? Serendipity. To be open to see things you wouldn't expect. As I told you, it was the same with Zettelkasten. It was, you were sketchnoting session in the internet.MR: That's funny.EG: The girl from New York said, Zettlekasten and Sonke Ahrens. Really cool stuff.MR: You just never know what's going to send you in the new direction.EG: Yeah.MR: Which is great. That's a great thing about life, right, if you're open to it. Which I would argue that people that stay in the sketch note community are very open and interested and curious people, I think by nature. Probably something else you share in common when you go to an event with other sketch noters, everybody's curious and loves to learn and loves to share. Those combination of things seem consistent to me. That makes a great community because there's just endless things you can learn about and endless things to do, which is exciting.EG: It's really my experience learning and talking with sketch noters, it's just another family. It's not the engineering style. It's another mindset. And I love it. They are from different professions. That's a big difference to my typical work as an engineer or as a data scientist.MR: You also have the international component, so not only are they from different walks of life and different interests, but they're also from different countries. Even then you have another perspective change, right? Even in countries in Europe as well as the United States and around the world, everyone has a little bit different view on things so you can learn some new things from those people from other places. At least that's what I've experienced. My life is so much richer because of the community for sure.EG: In this community, I really love this sharing mindset and this lifelong learning. And being curious, there's new stuff. There's a new app for drawing, could you please tell me a little bit about it? For these digital tools, they freely give away a digital brush set.MR: Right. Yeah, it's a great community, and we're glad you're part of it. Thank you for your contributions for sure. Speaking of contributions, I'd like to hear a little bit more about Zettelkasten, how it integrates or overlaps with sketchnoting.Probably, the best place to be would be to give us some history. Where did the term Zettelkasten—it seems to me like a German word from what I've done. Maybe take it from there and give us a backstory. Obviously, we know how you came across it. How do you then apply the Zettelkasten idea with sketchnoting?EG: You are right. Zettlekasten is a German word, and I think if you translate it right, it's a slip box. Typically, a slip box is a wooden box, small ones with a lot of note cards. This German, this Niklas Luhmann, this professor from Germany, a sociologist from Germany from the last century. He had a wooden Zettleksten with about 90,000 notes he'd taken in his life.MR: Wow. He must have had more than one box for that.EG: Yeah. It's a small format, and there's only written down his idea he got while reading a book while reading an article. Not reading in the internet. That wasn't invented at that time. When he was ready with creating this note card, he put it in a Zettelkasten.MR: A slip box. Yep.EG: In the slip box, yes. But you would say, okay, what's the way coming back to this Zettel or to this note card some days, weeks, or months or years later? That was the system we all know if you're familiar with the internet, he put a number on top of his note card, an identificater, an ID. It was written the date and the time when he created this note. And whenever he put some ideas on paper, he linked this note with another ID of another note card.For example, if you would say ideas not art, and put it only here on this note card, then he should put a link to the note card of Mike Rohde, with a Mike Rohde Id and maybe a must be an ID from this book.MR: Got it.EG: Then he put it in his Zettelkasten. Later on, if he was working on an idea, he want to write an article, or was writing a book yet idea, okay, there are some note cards. They're important for this stuff. I got them from my Zettelkasten. With these two or three cards, there are a lot of connections to the other note cards in the Zettelkasten.MR: Then you pull those note cards, right?EG: He put this on his desk, rearrange it a little bit.MR: Card sorting. Yeah.EG: Card sorting and say, okay, all the ideas are on the table. It's an easy stuff for writing. He was never sitting with a blank sheet of paper. Always starts with his notes. Note cards he captured days, months, or years ago. Niklas Luhman, it is said he was very productive in his life. I'm not good in remembering numbers, about 400 articles and 90 books. It's unbelievable for a lifetime.MR: Wow. The thing that makes me wonder is there must have been some kind of index. When you do the ID on the card, you must have to also—I think about the bullet journal. When you put entries into your book, you're supposed to add that to the index so that you can find it later.Is there an index component to this as well? Or do you have to just rifle through your slips? How would you know by the ID whether it's the thing you need, you'd almost need some organizing structure where you would say things about this are these numbers and things about that, or something. Tell me about that.EG: You have different types of notes in your Zettelkasten. The main part of the Zettelkasten are so-called permanent notes. Let me say there's a phrase to call them atomic notes because on one Zettel, there's only one idea. There's not an article or a story. One idea. Okay. And there are other types of notes. For example, structure notes and structure notes says, okay, that's my topic. That's about—MR: Gardening. Let's say.EG: It's about gardening. On this structure notes, you say in gardening, you need tools plants and whatever, soil and you put a list of important stuff for gardening. What are the 10 most important tools for gardening? Put it on this paper. And link it with a note card you already have in your Zettelkasten.MR: Got it. There is some manual, identification and crosslinking and such that you would do. That makes sense.EG: In book writing, it's an index. This structure notes are indexes and there are table of content. You have some structures like the structures in a mind map. In outlining of an article, for example, you have some main ideas, some sub ideas, and so. These structures are on special cards, but on the structure notes, they are only structure information, no content. The ideas are on separate permanent notes, and you have the structure notes.MR: In the physical box of cards, box of slips, I would assume, maybe in the back is where all the content notes are or the idea notes. And maybe in the front is where the indexes and structure notes live. You would maybe first go to the front part of the box to look for topics and say, "Okay, I need card number, this, and card number that and this."And based on that, then you'd go in the back and pull those because they would be in some order, then you could pull 'em all out and then lay them out and do what you will, and then return it all back to the box, assuming you didn't add some notes. If you added notes, then those would go in. Indexes would be updated and the new slips would be put maybe in the back, I suppose.EG: Yeah. These are the main types of notes. How to create the note, if I'm reading a book and I'm note-taking, I use my Zettels, and if there's important information on page 56, I put my idea with this important idea from the book on the literature note card. Literature note card only means it's the content I read in the book with my own words. It has an unique identifier, and with a digital tool, it would be a title.You don't need these numbers anymore. From a hindsight, you have to order and to sort them ad you have no search function. Today, you only have the title, you have the content in your own words, and you have a link to the source. Literature note—MR: Easily do with these tools that exist now, right? Linking is easier.EG: Yes, the only must with the literature note is to have a backlink to the source itself.MR: The book itself and the page number itself.EG: The book also to the author. And the literature note is not a permanent note. Maybe on the same day or little bit later, you will take you a literature note, look at it and say, "Okay, are there any connections in my mind, which may be important?"Maybe it's a phrase from your book, Mike to focus attention in your sketch note. And you said, okay, there's a connection to attention, and there are a lot of note cards, they are connected to attention. You put this on your—if you are started to link your literature note with other already existing permanent notes, then you transform this literature note to a permanent note. And the literature note vanish.MR: Doesn't need to be kept yet.EG: Yeah. With a linking to other notes, you have two possibilities. One is the link, like a hyperlink in the internet and the other possibility to link to other concepts, ideas, or whatever is tagging as you do it in Instagram, in Twitter, and—.MR: The hashtag.EG: —whatever. It's all the stuff we already know, but did it on paper. We are really lucky to have the computers and you have modern tools for this idea of note-taking. My favorite tool is called Obsidian. It's one of the favorite tools from a lot of writers. Starting with a steep curve in, if you ask at Google trends about Obsidian, it's a very slow line and rising high in the last month or years.It's a really great community. It's a little bit this sharing style, like the sketch noters. If you are in an Obsidian community with other guys using this tool and using the Zettelkasten method, and you ask a question, you are sure there's an answer within a few minutes. They really help each other. What is behind as I said to you in the beginning using sketchnoting seems to be easy, but you need a lot of experience.MR: It's a learning curve. Yeah, for sure.EG: It's not so steep learning curve. The same is with notetaking. It seems to be easy, as I told you, only a few types of notes. Use it on paper or use it on the PC with Obsidian tool, but it's really learning, learning, learning. In my professional life, most part, I need a lot of time in my business for note taking, with sketch notes without sketch notes.What, for me, was fascinating. If you have a note card, you can draw on it. There's no need. Like Niklas Luhmann, I think he wasn't a visual thinker. I do not know him personally, but only writing text or note cards. He couldn't have read your book in this time.MR: Yeah. Yeah.EG: There was no drawing at all. Unbelievable. But today, I think use a note card, put your drawings on it, and you have a mixture of sketch noting and note-taking with a Zettelkasten method integrated in the Obsidian tool.MR: Tell us a little bit how you do that, because that's the part where—I've got a text editing tool. I use Ulysses for writing. It can do some linking, but it's not optimized like Obsidian is, which I've considered, but for now, it's been great for writing. I use folders and structures.It also does tagging, so I could do some of it, but I'm really curious to see like bringing in the visuals into Obsidian. I would guess that you could attach images. You could do a drawing, take a photo and attach it to one of these cards and then use your linking and tagging to make sense of how it fits in the greater whole. Talk to us a little bit about how you make that work.EG: It's a little bit like linking a drawing to a note card. It's like building a webpage, there's the written stuff, and then there's a link to a jpeg or PNG or whatever file. For me, that's the same for drawing. I typically us my iPad with the Concepts app. I can export it in this—MR: It's an image.EG: Yeah. It's an image at the special formats. Then they are linked in the Zettelkasten tool. I can reuse. Also, it's only a link to the image. There's one place, they are all images. It's big box with thousands of images. And there's one link to one note. If I use the same image in another note, there's only a link to this image.MR: One link. Got it.EG: One link and one—you say you have a tool using folders.MR: Right.EG: I was trained my whole life working with folders. I'm not sure if it's a German invention to put all stuff in folders. I had these folders before the PC was invented. In the living room, wherever you look, there were folders with different Zettels here. And it was a nice feeling putting all the stuff in the folders. It looks pretty. When I had the idea, coming back to an idea, which was the right folder, where did I put it in? and I lost a lot of time my life for searching.MR: Searching for things.EG: The most confusing thing was this folder structure with sub-folders and sub-sub-folders. It was this tree-like structure, and you never which branch and which leaf and couldn't find it. What was really hard for me, learning the Zettelkasten method there, I would say no folders. All these permanent notes are in one folder. That's a crazy feeling. If you do it at the beginning and you'll say, okay are there the right links? Do I have a link to the source? Do I have a link to the author?And then you put it in this box, in this permanent note box, and it vanishes, and it's gone. From your life, you have no experience, is there a chance to get it back? Although I knew it's easy to get it back. There's a perfect search function, full text searching in this tool. You can look at the links. You have a craft view. You have a crafted representation of this network. You can filter this craft view, and it's really easy with all these tools coming back to an idea. But using folders the whole life—MR: It's very comfortingEG: It's a brainwash to put something in this black hole.MR: Like putting it in the sea.EG: I will never get it back.MR: Interesting. Well, I suppose, if I were to think of the one thing that's close to folders in this method would be tagging. You could have multiple tags. In a way, you're marking it in a folder, but it can be in more than one folder. That's the beauty of tagging where with a folder, there's only one, and if you can't find that folder, it's lost.I guess now with tools like Ulysses as an example, I can do searches and find things. Ideally, and probably the way I would go about it is probably use tagging to start tagging. Then I guess the challenge around tagging that I've seen in my lifetime is being consistent with tagging. Because maybe one tag is icon and then you accidentally say icons and now you have two tags.So, forming a manageable set of tags is probably a challenge because if the tags get out of control, then you could potentially have more processing stuff. You probably have to be disciplined about tagging, I suppose. To have a pretty structured tagging organization otherwise could get outta control, just like folders could.EG: It's really important point you talked about, this tagging and what you need at most at the beginning of working with a Zettelkasten, to have some kind of architecture for your text. What is important, what needs to be tagged in which way and not to have an idea of all the text from A to Z, but you have this taking architecture.For example, I have texts about hashtag type. And in Obsidian you have not only one level of tagging, but two levels of tagging. You can say hashtag type slash note slash sketchnote.MR: So, modify in a way.EG: Slash book. It's not about the content of the note, but it's more a little bit like metadata. If you come back, for example, oh I'm not sure what it was, but it was from a book, and then I could use this hashtag-type book. And then I have a list of books, and then I say, okay, but only the last two weeks. Then the list is very short and say, "Okay, that it was."You can find things and have no—you wouldn't be able to have a prompt, a search phrase. In Google, for example, you need some phrases to find the stuff. With your tagging architecture, you can search for stuff where you have forgotten the phrase.MR: So, probably tags for someone who, like you and me, have been trained to use folders for our whole lives, and that's a comfort for us. Probably the bridging mechanism to Zettelkasten might be tagging and then linking as well. Because in a way, tagging becomes like your representation of what the folder means. It's a metadata. It's the thing that defines the category.EG: In my architecture, I have for example, this taking of types, and as a process engineer, one of my jobs in the past, there was input, computation, and output. Then I have the tech input, and I can say it's from the internet, it's from the book, it's from YouTube. Sometimes, I only have an idea where it comes from. And other texts are about output to say, okay, I put it to Twitter, to LinkedIn, to Instagram or whatever. That's not about the content of the note, but only where it comes from, where it goes to.In this architecture, there several metadata sets I can extend at the end. The list of output, it's infinity to extend it, but this main structure it's very important to have it at the beginning, but when you have hundreds or thousands of notes and you have to change all this text, it's not so much fun.In Obsidian, there's a plugin. There's a plugin, if you say icon or icons, you can say, please change all text icons to icon, and that's makes it easy.MR: Yeah. Interesting. Is there so you think the Sonke Ahren's book is a good place for someone to start who's maybe interested. Are there other resources you might recommend? Are there classes or YouTube videos or something that might be helpful to get people started on this? Secondarily, once they've established the base, is that a Zettelkasten structure then is there reference for how to integrate visuals into it?Because it sounds like a lot of what I've seen is more text oriented, like linking and writing and so forth, it's all text, and there's not so much emphasis on integrating images. I think for sketch and visual thinkers, having that additional information would be useful. In addition, like once you set up the structure, then how do we integrate images into it would be helpful.Some of the things you've hinted at like there's a big folder that has all the images in it, and then you just link to it. And I suppose that's part of the whole box, right? So, you have one folder that's got all the text and it's all linked together, and then one box with images or something, and then you link them together.EG: I have one folder. The folder is called visuals. They're all my images. I have a folder, as I said, a permanent notes. They're all this permanent notes stuff. Other stuff, for example, I collect a lot of PDF files. Maybe I have books in PDF format or table of content from a book I have on paper in PDF, and all this stuff of value in my assets folder and I can link them easily.MR: All between each other.EG: Some of the sketch notes I have in PDF formats from others.MR: I see.EG: Assets for example, are the sketch notes from others I collected as an example, as a source of inspiration. In the visuals, I have these drawings from myself. As Niklas Luhmann did writing it down with your own words, it's drawing with your own pencil.MR: Yeah, same thing. Just a visual interpretation.EG: There's no difference. Therefore, the only difficulty with this book of Sonke Ahren, believe me, there are no pictures.MR: Yeah. Exactly.EG: Most of the sketch noters can draw, and therefore, it should be possible.MR: Now, I know that you offer, as part of your show notes that you pre-sent to me, there's something about an e-book. Is the e-book address using Zettelkasten for visuals and sketch notes? Is that what the book is about?EG: Yes. My idea was using the Mike Rohde book and using the book from Sonke Ahrens, put it together, but not to repeat it. But to say, what does it mean if you put it together? I give a lot of hints and advices how to structure the folders, how to use the architecture for the tagging.MR: That sounds like exactly—EG: That's more important. If it's more, oh, sketchnoting, then there's a link maybe to your book or maybe a link to a YouTube video. All the details are links to the internet, to some Zettelkasten videos or to sketchnote videos, or other material. And it's one overview. It's a book, would say a structure note with a lot of sketch notes and with links to all this stuff you need to put together.MR: Got it.EG: It's a book full of references.MR: So basically, if someone is listening to this and getting excited about the idea of, say, picking up Obsidian, which by the way is free for personal use, sets up Zettelkasten so that they can manage their sketch notes. That this would be the next step would be to get the book that you've created in order to structure it and start working with it and integrating it. Would that be the right way to think about it?EG: And the idea of my book is not writing it and publishing it in two or three years. I'm fascinated from this idea learning in public and publishing all the stuff. If I'm sitting here at the weekend writing a chapter in this book, then it's published in a pre-published version. I published already 15 versions. Most, it's one more chapter, some more links, and so on. It's growing and growing. What is really nice, the sketch noters and the Zettelkasten community, they all help me writing this book.MR: Oh, great.EG: I don't understand this sketch note. What do you mean with a sentence? I got feedback and okay, it's not printed this book. It's a PDF. It's on GitHub. It's freely available and all this feedback, there's an update and I can improve it. I earned my money as an IT engineer with HR projects. And we put running software to a customer a few days after he agreed with us the contract, and we were improving and improving. Today, it's possible also with books.MR: It's a mindset. It's a living book in a lot of ways. It's almost like software documentation, right? As you build the tool, like pieces are removed and replaced or depreciated, or things or features are added. In software, you have to document this stuff so that it's tracked, and you can go back in time and look at the old version and see, oh, that's right. We had that feature, and because of this and that, we removed it. It's no longer in the documentation.I suppose, in this case, you're doing more adding, but I suspect at some point maybe something would disappear or whatever, and you might have to replace it or something. Like a link, say somebody website in five years goes away, you might have to find a new link to that or something.EG: With Zettelkasten, I started in March '22, with your even bright workshop.MR: That's funny.EG: And then I started writing the book because the idea is not to take notes and to put all these Zettels, as I said in this box. It's a black hole. What do you need? That's very important for all who want to start with the Zettelkasten. You need the goal. What do you want to do with all these ideas in this box?MR: Right. How's it gonna be applied?EG: That's not the final destination. That's an asset. As a proof of concept, I have to write a book. Otherwise, all these ideas would vanish in this Zettelkasten box. And they're beautifully linked, nicely teched, but it doesn't make any sense. What I found in the internet, I think nearly as great as the sketch noting book from Mike Rohde, as great as Sonke Ahrens Zettelkasten it's about "Writing Useful Books." It's from Rob Fitzpatrick. You see, it's full of highlighted text, every page full of nuggets.Yes, yes, yes, the idea that non-fiction books are problem-solving books. You need to know the problems of your potential readers and to show them on the first page, which problem are you looking at, and how you can help them. And if you read the table of contents, there are a lot of promises from the author, how he could help you to solve your problem. And then, this as very short in writing, as you see, it's a small book.MR: Yeah. It's quite thin.EG: Quite thin, but full of value. Other books 500, 600 pages. I stopped in the middle of the book. I had no time in life to read it to the end. And that's the third book in my project, using the contents here of these right useful books to get the Zettels out of the Zettelkasten to create project notes, to create consistent chapters and sub-chapters, and to deliver result from all this syncing behind.MR: I think the other challenge too, that it's important to have a purpose would be if you just did the Zettlekasten just to do it without a purpose in mind, it would just go into an ocean. I think eventually your motivation to maintain it because it takes work to do the linking and all this, even if you get into a rhythm, it takes work. Just like sketchnoting, it takes more work to do sketch notes 'cause you have to really think about it and you're analyzing. So, it takes effort.Unless you have a purpose for it, eventually you're gonna, "Uh, I don't want to put a link, I'm tired, I don't wanna write a link, or I don't wanna do a tag." Then the next thing you know, then you're not adding thing. You know what I mean? It's like, would degrade ‘cause you didn't have a purpose for it.By having a purpose, like in your case, writing a book, it meant that you had something that you were doing. And now everything that goes into your Zettelkasten is likely for future additions of the book, or maybe now some new project that the Zettelkasten serves a purpose for, I would guess.EG: As a process engineer, in my Zettelkasten, I measure the input, I measure the output, I can measure the productivity, the relation between output and input, and I can see is it working. Is the process working? Are there some bottlenecks in the Zettelkasten? What takes the most of my valuable time? Is there connection between the idea at the input to the book at the output? Is it a little bit complicated or is it directly connected? How long does it take to get one idea in and one idea out? If I take this book, it's from 2012. If I would use one concept to improve my output, that 10 years between your idea, your shared to my idea, I shared.MR: The application.EG: Yes. And my idea is to shorten it a little bit. Reading a book, reading another book, connected and having an output and an output of value to solve a problem of my readers. That's more than note taking.MR: It's another level up.EG: It's a philosophy that connects really the organizational part with the Zettelkasten, the visual part with the sketch notes and the value part from "Creating Useful Books" from Rob Fitzpatrick.MR: Overlap of three things.EG: Combining three things and say, okay. That's for me, it makes sense. It's not only a machine, I'm focused on the wheels, didn't have a look at the motor, but I want tto build this car, and it's really working. You can use it.MR: Well, this is great. Thank you, Edmund. And you know, if you've been listening to this discussion, you're getting ideas in the end of the show, of course, have contact information for Edmund so you can reach out directly, but we'll also have links to his book and the other books that he's mentioned so you can do your own work and download obsidian and those kind of things, and try it out. I think this has been very helpful. I'm hoping that it will inspire some people to maybe organize their sketch notes using this method. That would be great.EG: I hope it solves one or another problem from all these guys taking notes their whole life, being a student, being a professional. And so, take their notes, but having ideas to improve this process. Taking sketch notes, not only the written stuff. Remember the old stuff, finding back to old ideas, combining with news, and having the chance to give the ideas a chance. They can meet in a Zettelkasten although they came from very different sources.MR: Right. The opportunities are pretty great there. Well, this has been interesting. Let's shift a little bit now. We'll talk a little bit about tools now. Let's start with analog tools and then we'll talk about digital tools. You've hinted at some of these things already, but let's go more in detail. Starting with analogEG: I already mentioned it I only used this Neuland and the reasons I gave you.MR: They're all there.EG: The only Markers, they really work in a professional context. That are my fine liners on paper. Is it?MR: Yeah. The little guys. Yes. Staedtler,EG: It's Staedtler. I think it's from Germany, but it's a way. The Neuland markers they also sell the Staedtler stuff.MR: Yes.EG: It's the same is only a branded Neuland on it. But it's the same. Perfect quality for me. That was my life before I got an iPad.MR: Tell us about how the iPad changed you. You mentioned that you've made a shift from one application to another. I'd love to hear not only what those two tools were, but then the rationale for switching and what led you to the new tool that you're using now.EG: With my iPad, I looked at the internet and to all the sketch notes and they told me there's only one tool you can use, it's Procreate. I had a lot of experience with Photoshop in the past, and it was not so difficult to understand how to use the Procreate tool. But I struggled a little bit with my canvas. Is it designed for a letter format or for a large poster? It is pixel-based the Procreate and enlarging your drawing means there is all this—MR: The jackety edges.EG: Yeah. It's not so nice. The Procreate, if you say, okay, I'm not sure which format is the best, I plan for the highest resolution and can reduce it if I need. But then the fights were getting bigger and bigger. With a Concept app, it's a vector-based format. I can resize as I like it. At the beginning, at the end, and the canvas is infinite. If there's not enough place, there's place for an extra drawing and I put it together.What I learned is, it's very easy to handle an object library in the Concepts app. Most of my life, I was working with PowerPoint. PowerPoint means use it as a tool putting different visual objects together. This PowerPoint style of working I can use with a Concepts app. If I drawing a house or a special icon, some eggs are very easy, a square or triangle. I can put it on the surface as well.But if it's a little bit more complicated, a stopwatch or so with some details, it costs me a few minutes to do it well. Then I can go to the library, put it together, and it's all my shape. It looks like freshly drawn from Edmund. It's not a library I bought.MR: You made it yourself.EG: I can say from Microsoft. I would say, okay, there are a lot of visuals, but they are not from me. And it makes it very personal to use my own icons, my own drawings. What I have to learn is to write my name with nice letters. And that's not so easy, it takes me most of the time to learn this architect's handwriting.It's all in Concepts. It's now not so difficult to, produce nicely looking stuff. Not only for me but also for others. Also, I'm not an illustrator. I'm not a professional artist. And graceful enough, that was the phrase I got from Mauro Toselli.He said, "The sketch notes must be graceful enough, not more." There's no need for, but if they're really ugly, someone would say, okay, it's hard to read. I do not really understand. Is it a horse or a dog or so? It must be graceful enough. That's possible very easily with pre-drawn objects I use most times.MR: Interesting.EG: Therefore, if you say there's a better tool, okay, I will have a look at it, but at the moment, I'm pretty happy with my Concepts app.MR: That's good. That's good. We'd like to hear that. It's always about finding what fits the way you work. Some people, Procreate just works the way they like to, and they don't have these challenges of sizing in vectors, and it works fine for them, which is great. But if you have other needs, it's great that there are other software out there that can do what you need to do. It's important that we have variety, and we definitely. We are very lucky that the iPad has lots of options available to us.EG: It's the same iPad, it's the same pencil, and everyone can use the tool which fits to his own personal styles.MR: Yeah, I still use the app Paper, by WeTransfer, which hasn't really changed too much, but I've become pretty fluent with it, so I can work really quickly. If I do illustrations, I have to move to another tool like Procreate or Concepts. But for really super quick ideas, for me, it's just really efficient.I've learned that in my career when I'm faced with a heavy deadline, it's wise for me to choose a tool that I'm fluent in because I'm speedier in that tool than if I tried the perfect tool for it, but I don't have familiarity with it yet. That's a lesson I've learnedEG: As I learned in my profession, whatever tool you are using, you have to use it really professionally, and you have—it's not only starting with the tool and being very fluent or very efficient, you must know your tool very well.MR: Yes. Yep. Well, that's great to hear. Really simple tool set both on the analog and digital side. Let's shift a little bit more, and let's talk about your tips. The three tips that you might share. I always frame this, imagine someone's listening, they are visual thinker, whatever that means to them. And they're excited about the space, just like we talked about our excitement about the community, but maybe they've hit a plateau or they just feel they need a little bit of inspiration. What would be three things that Edmund would tell them to kind of encourage them and break them out of maybe being stuck?EG: Starting with sketch notes, that was always the question, how to find a personal motivation going on improving your skills. One of the motivation as I showed you are books. I love it to learn from books. But what is even better learning from other people? With my company where there's self-organized learning groups, we're growing up. I learned this self-organized learning groups are the best to improve yourself.One of your podcasts Mike, there's a team about LernOS. They had a 12-week journey, different stuff. There's also a learning journey for sketch notes, and you have self-organized meetings every week and having a Zoom meeting or so, sharing my report or whatever.It's little bit like there are some examples, some exercises you can do together, but you can do as a homework for the next meeting. That's the way I like to learn. It's better than sitting with a blank sheet of paper at home and reading the book and—MR: Struggling. Yeah.EG: Struggling.MR: That, by the way was for those listening is season eight was an episode with Karl Damke and Raffaelina Rossetti.EG: Rossetti. Raffaelina Rossetti is her name. Yeah.MR: You can learn about that movement there in the podcast.EG: There's a link to the internet also where the Sketchnoting Guide is, and so, and it's amazing stuff. Getting the right people for the sketchnoting Circle. That's my next advice. Typically, they are distributed around the world. That's not your neighbor, the sketch noter, or the other neighbor on the other side of the street. They're somewhere in this internet universe.Some years ago, I found this Sketchnote Army Slack platform you established, Mike. And there's one folder with announcement of LernOS sketchnoting groups, and that's sub organized to find others. They're interested to have on Friday afternoon five o'clock or so, the next 12-week we want to join this sketch noting journey. And they're from different countries, different professions, different skills in drawing that's not only the beginners or the specialists. It's like these schools and former times they are the small and the older, the grownup children, and they help each other.MR: The one-room schoolhouse, we would say in the United States. Back in the days.EG: This one-room schoolhouse you have in the Slack rooms. You find all these people and it's this mindset sharing things, learning together, and so, you would never find them in real life.MR: Yeah. That's two points. That's number two.EG: Two points. The last one, I want to repeat, Zettelkasten is my second brain. Zettelkasten it's also your second brain. You have a lot of experience in note-taking, different tools, but looking at this concept to get a step higher in efficiency, in effective note taking, and making things easier than they are.MR: Great. Well, those are three great tips. Thanks so much for sharing those. And definitely, encourage you to do all those things, both the LernOS and explore Zettelkasten. So Edmund, what's the best way for people to reach out if they have questions about Zettelkasten and sketchnoting or something else, what's the best place to go?EG: Mike, you said you are sharing some links about me.MR: Yes. We'll definitely share links.EG: It's very easy because I look at my posts nearly every day in LinkedIn. In Instagram, you'll see some of the sketch notes, the newer ones. Most of them are sketch notes before they are published in the ebook. On Twitter, there's a chance for communication very fast. Is it one year ago, Mike we had this discussion about sketch note manifesto?MR: Yes. That's been around. I think Mauro has been talking about this for years.EG: Yes. That was an idea from him and I mixed it a little bit up with atrial development. Then we had a discussion about it. That's the style of communicating and Twitter. And yeah. I also have this in your link list a Linktree. Yeah. All the other stuff are from Masterton or from the forums about Zettelkasten. There's a Zettelkasten forum and Obsidian forum. Also, there are new ideas I discussed with others, and they also get the feedback. I'm learning with all these guys.MR: I'll look on the Link tree. You have several links here, LinkedIn, Instagram, medium, Pinterest, Masterdom, and on Twitter, and eBook.EG: On all platforms, there are links to the GitHub platform. There's the PDF file of the actual version of this e-book, "How to Take Useful Notes."MR: Yeah, I see it here. We've got links for all these things, everyone. So we'll put 'em in the show notes so you can see and jump and look at all these things that Edmund has been talking about. Especially, if you really want to get into this Zettelkasten with Obsidian and using your sketch notes, making a way to organize 'em.I'm inspired, I'm gonna do some looking at this because I think there's an opportunity for me to level up, like all the work I've done and make some sense of it. It might be interesting to see, looking back over it what connections there are. Maybe it's a big job though, Edmund. I don't know. That could be a lifetime just organizing all this junk I've made.EG: I will tell you the story. Maybe I published the story about the new situation before Mike Rohde's podcast and afterwards. Or is it worth a sketch note to say, that was my life before and that was the life after?MR: Yeah. Well, as a process engineer, you're gonna wanna know what's the input, which is doing the podcast. And the output is, are you suddenly getting more downloads of your book? And questions about doing Zettelkasting with sketch notes. That would be ideal because you're a pioneer in this space. I think Chris Wilson is another person in the space that's explored, we talked about in his interview, he was starting to play with Obsidian.EG: I listened to this podcast from him. It was the first time I saw some sketch noter using the Zettelkasten.MR: You two need to get together and do a workshop for everybody, so you can sort of walk them through. That could be interestingEG: If you know a female sketch noter from Denmark, Ingrid LiLL.MR: Oh yeah, of course. Yeah.EG: He is also starting with the Zettelkasten.MR: Oh, there you go. Now you have three people to your merry band, so you can maybe do some kind of a teaching.EG: It's a very small community.MR: That's okay. Sketchnoting community is small, but getting bigger every day. So you have to start somewhere, Edmund, you have to start somewhere.EG: It's the 1% of the sketch noters using Zettelkasten.MR: Yeah, exactly. That's okay. If it works for you, then you can do itEG: All things I believe ever starting small.MR: Yes. The best things start small. Well, Edmund—go ahead.EG: No, no.MR: I was just gonna say thank you so much for your participation. I see you on LinkedIn and Instagram and Twitter. You're always so kind and you have such kind words, and I just love that. You could have easily retired and just gone to Majorca and like, just enjoyed your life and not done any of this work, but yet you choose curiosity and sharing and giving, and I really appreciate that and I admire that. So, thank you for giving back to the community and making it a better place. That's so much what we need.EG: Thank you for having me.MR: You're so welcome.EG: It was really fun. Also, the story in the beginning you told before the podcast, it was a wonderful evening.MR: Yeah. I told him my German experiences that made me fall in love with Germans and Germany. Maybe I'll tell that story sometime. Well, everyone, this has been another episode of "The Sketchnote Army Podcast." So until the next episode, we will talk to you soon.EG: Thank you. Have a nice evening. Bye-bye, Mikey.MR: See ya.

We try out the most secure messaging app in the world, and Wes' new note system that's so great you'll want to abandon your current one.

Making, recording, and evaluating predictions is a simple way to improve your thinking and decision-making. But the way to properly make and record predictions isn't obvious. In this article, I'll share some predictions I've made, what I've learned, and how you can improve your thinking by making predictions. Making predictions has grown my business Five years ago, I had been running my business for ten years, and it wasn't going great. Then, I started publishing monthly income reports, and along the way, making predictions. My income has nearly doubled, and I attribute much of that success to my habit of making predictions. I began by predicting how much money I'd make in a product launch, and grew to predicting how much traffic articles I had written would gain, and how many copies books I'd written would sell. I now routinely make predictions for things as seemingly mundane as whether I'll enjoy a conference, whether I'll still be publishing on TikTok a year from now, or whether an avocado is ripe. On the surface, making predictions seems like a pointless game. This is, indeed, true of making predictions the wrong way. But making predictions the right way helps you deal with uncertainty you otherwise have no hope of handling. Predictions help you bet your life, better Each of us has limited resources, such as time, money, and mental energy. We're constantly making decisions about how to use these resources, and when we make those decisions, we are expecting outcomes. If we go on this date, will we find the love of our life, or wish we'd stayed in? If we write this book, will we achieve fame and fortune, or feel as if we've wasted years of our life? If we spend an hour on social media, will we make valuable connections, or spiral into self-hatred over our lack of discipline? As Annie Duke, author of Thinking in Bets wrote: In most of our decisions, we are not betting against another person. Rather, we are betting against all the future versions of ourselves that we are not choosing. —Annie Duke, Thinking in Bets Each decision we make is a bet. We bet a resource, and expect something in return. Most of us don't recognize or express the expectations of our bets. But we should. Some bets are clearer than others If you bet a dollar on a coin flip and only win $1.50 for guessing correctly, you'd easily recognize that as an unfair bet: There's a 50% chance of guessing correctly, so you clearly should receive two dollars. But the more variable the odds, and the more vague your wager and winnings, the more difficult it becomes to think clearly. What's the value of finding the love of your life? What other benefits can you get writing a book besides fame and fortune? What are the chances that during this hour of social media you'll make a life-changing discovery? Making objective decisions taking into account all these variables becomes so complicated you might as well throw up your hands, surrender to randomness, and do what feels right in the moment. And that's what most of us do. Case in point: The multi-billion-dollar gambling industry, propped up by people doing what feels right in the moment – their decision-making shrouded by the smokescreen of ever more complex and variable bets. The key to making predictions in a way that helps you evaluate your decisions is to avoid what Annie Duke calls “resulting.” If you wager a dollar on a coin flip, with a chance to win $10, and lose, the result of your decision was bad, but your decision was good. The odds were clearly in your favor. Mathematically, you were sure you'd win that bet one of two times. If you had won, you were going to win ten times your money. Now how do you apply this thinking to more complex and vague situations, such as a product launch, your Saturday night plans, or whether or not your new hobby is a passing obsession? The key is to make a prediction, the right way. How to make predictions the right way There are two components to making predictions the right way. Turn it into a coin flip. Identify the odds. 1. Turn the outcome into a “coin flip” First, turn the prediction into a coin flip. I don't mean in terms of odds, but in terms of result. When you flip a coin, it comes up heads or tails. When you make a prediction about a result, that result must either happen or not. For a prediction to be useful, it has to be falsifiable. This is not easy to do, which is why few of us make predictions the right way, if at all. If you think it's going to rain, in what area will it rain, by what time? Does a single raindrop count? If you think you'll still be doing bird photography in six months, how many bird photos will you have taken, within the previous month? If you think you'll enjoy going to the party, how many good memories will you be able to recall a week later? You can define a successful result in whatever measurable way you want. The important thing is that to make a prediction, you need to turn the result into a coin flip. Not in terms of odds, but in terms of how you define the result. Some actual predictions I've turned into coin flips: My Black Friday promotion will earn $3,000–$6,000. My blog post on Zettelkasten will average worse than a ranking of 10 for the keyword “zettelkasten”, the first three months after publish, according to Google Console. I will sell 5,000–15,000 copies of Mind Management, Not Time Management within the first year. With each of these predictions, I was wagering resources. It took, time, money, and energy to run a promotion, write a blog post, and write a book. But what did I expect from those investments? I could have done any of these without making a prediction. Besides the long-term benefits of making these predictions – which I'll get to in a bit – turning these predictions into coin flips had immediate benefits. Turning predictions into coin flips helps answer these questions: Is this worth doing? By defining a successful result, you're forced to ask yourself if it's worth the investment, based upon your expectations. How will I achieve this? In the process of defining a successful result, you start thinking about why you expect to achieve that result. Do you have prior experiences or past data to draw upon? You'll never search as hard for these as when you're making a prediction. Can I do better? Defining a successful result has a symbiotic relationship with the effort you put forth trying to achieve the result. Making the prediction motivates you to try to make that prediction correct, which sometimes motivates you to predict and try to achieve an even better result. When you flip a coin, you of course aren't sure whether it will come up heads or tails, and when you make a prediction, you aren't sure whether you'll achieve that result. And that is how it should be. 2. Identify the odds The second way to make a prediction the right way is to identify the odds of achieving that result. You've turned the prediction into a coin flip, but it's not necessarily a coin flip with 50/50 odds. It may be more like a die roll, with 1:6 odds, or a roll of four or lower, with 2:3 odds. If you've turned your predicted result into a coin flip by adjusting a range, you can adjust that range according to your expected odds. In this way, if you want to literally turn your prediction into a coin flip, you can pick a range you feel you have 50/50 odds of achieving. For example, I believed I had 50/50 odds of making $3,000–$6,000 on my Black Friday promotion, and of selling 5,000–15,000 copies of my book in the first year. I specifically chose those ranges based upon what I expected to have 50/50 odds of achieving. If your prediction doesn't involve a range, such as whether or not you will regret going to a party, then you simply have to identify your expected odds of that result. For all odds, I think it's easiest to choose a percentage of confidence, such as 50% for 50/50 odds, or 66% for 2:3 odds. For example, I was 70% sure I wouldn't regret attending a conference in Vegas last year. Each of these predictions is for one event. But the result will either be achieved, or not. Therefore, what you felt 70% sure would happen will in retrospect look as if it had 0 or 100% odds of happening. So what is the point of choosing odds for your prediction? There are three benefits of choosing odds: It helps you gain clarity on each decision. It helps you distinguish risky from not-risky decisions. It helps you rate and improve your decision-making, over time. Choosing odds helps you gain clarity First, choosing odds of achieving a result helps you gain clarity on a decision. Let's say you buy your first guitar. Surely you're picturing yourself being a pretty good guitar player someday. But how do you define that, how sure are you you'll become a good guitar player, and how soon? A year later, when your guitar is collecting dust in your closet, you might feel pretty bad about yourself. But suppose that when you bought your guitar you had predicted that you were 50% sure, one year later, you would have practiced guitar at least fifteen minutes in the previous month? Based upon that prediction, it turns out you weren't so sure to begin with that you'd become a good guitar player. Choosing odds helps you distinguish sure bets from wildcards Which brings us to the second benefit of choosing odds, which is that it helps you distinguish risky decisions from not-risky decisions. You took a chance buying a guitar, and it didn't work out. That's easier to live with if you know you were taking a chance. Some of life and business's greatest benefits come from taking chances. But you only have so many resources to gamble with. Professional poker players know they need a certain “bank roll” to stay in the game and keep making bets. If they have a lot of bank roll, they might play a riskier bet than if they have little. They're able to do that because they know the odds. In business, especially creative business, your “sure bets” keep you in business, while “wildcards” can change your business. As you decide how to invest your resources, and evaluate whether you've achieved successful results, you'll make better decisions if you know ahead of time whether you're playing a sure bet or a wildcard. For example, I was 95% sure my Zettelkasten blog post wouldn't rank in the top ten for the search term, so I was clear going into it I was playing a wildcard. Additionally, while I was 50% sure I'd sell 5,000–15,000 copies of my book in the first year, I was 90% sure I'd sell fewer than 250,000 copies, which helped put a ceiling on my expectations. Choosing odds improves your decision-making Which is the third benefit of choosing odds: improving your decision-making over time. If you had been 90% sure you'd've practiced guitar ten hours in a month, you'd still feel bad when it turned out you didn't, but at least you'd have data to learn from. Without that data, you might say to yourself, “I never finish what I start. I'm a loser.” With that data, you can say, “I overestimated my enthusiasm to play guitar. I'll keep that mistake in mind in the future.” Notice you wouldn't tell yourself you were “wrong.” Because you weren't. Even if you were 90% sure you'd've practiced guitar ten hours in a month and didn't, you'd only end up 90% wrong. Which means you were 10% right. When you choose odds of your expected results, it's easier to learn from your mistakes because you're never totally wrong, and always a little right – which makes your mistakes sting a little less. But to get enough data to know how good your predictions are, you need to make a lot of predictions over time. If you don't know the odds of a coin flip, and your prediction turns out wrong, you don't learn a whole lot. But if you make a hundred predictions, you'll end up with a pretty good idea of the odds of that coin flip. Make many predictions with the same odds, for faster calibration The more predictions you make with the same odds, the more quickly you can tell how good your predictions are. I've presented to you examples of predictions I've made with various odds. But whenever possible, I try to choose “coin flips” I believe have a 70% chance of being correct. 70% is an arbitrary level of confidence. What's important is that by making many predictions of which I have 70% confidence, I learn how accurate my predictions tend to be at that confidence level. I've made 19 predictions at 70% confidence. Only 63% of those have turned out correct. By making and tracking many predictions, I've learned that when I'm 70% confident something will happen, it will generally happen only 63% of the time. I'm slightly overconfident at that range, and so should be more conservative with my future predictions. My prediction track-record I keep track of and publicly display many of my predictions on PredictionBook.com, which is one of those totally free websites with no ads that makes you nostalgic for 2007. Because I've made more than fifty predictions, I can see how good I am at predicting at various levels. For example, after fifteen predictions at 90% confidence, 80% have turned out correct. After five at 50% confidence, and five at 60% confidence, those have turned out correct 80% and 100% of the time, respectively. While I should to be more pessimistic about things I'm pretty sure will happen, it seems I should be more optimistic about things I'm not so sure will happen. It turned out the prediction that my Black Friday promotion would earn between $3,000 and $6,000 was correct. Since I was 50% confident, I was half-right, and half-wrong. I did sell between 5,000 and 15,000 copies of my book in the first year. Again, half-right, half-wrong. And the Zettelkasten blog post I was 95% sure wouldn't rank in the top ten, actually did! I was happy to be 95% wrong about that – it was a wildcard that turned out. Making predictions feels unnatural – which is why you do it The next time you're choosing whether something is worth doing, I highly recommend you make a prediction. If turning the outcome into a coin-flip and picking a percentage of confidence feels uncomfortable to you – it should. Thinking in this way doesn't come naturally – which is why it's a superpower. Image: Ghost of a Genius, by Paul Klee About Your Host, David Kadavy David Kadavy is author of Mind Management, Not Time Management, The Heart to Start and Design for Hackers. Through the Love Your Work podcast, his Love Mondays newsletter, and self-publishing coaching David helps you make it as a creative. Follow David on: Twitter Instagram Facebook YouTube Subscribe to Love Your Work Apple Podcasts Overcast Spotify Stitcher YouTube RSS Email Support the show on Patreon Put your money where your mind is. Patreon lets you support independent creators like me. Support now on Patreon »       Show notes: https://kadavy.net/blog/posts/make-predictions/

This is a continuation of the conversation I had with Maggie previously: "The Dark Forest and Generative AI." We discuss why we write, versus why to use AI and LLMs to produce writing, and what effects that loss is likely to have. Discussed in this episode: Why do humans write? Writing is around 5,000 years old We mention a note-taking system called a "Zettelkasten" which I wrote about here Writing to our future selves How do we read? Science and philosophy as conversations On getting up to speed in conversation How much to read before we should write Who wants to read GPT outputs? Roland Barthes' "The Death of the Author" (1967) The deep link between cognition, action, perception The 4Es: embodied, embedded, enacted, extended (see: enactivism) Moravec's paradox Gwern Clerestory by ⁠⁠⁠Bryan Kam⁠⁠⁠ • Infrequent updates at ⁠⁠⁠Substack⁠⁠⁠ • All my work plus exclusive content at ⁠⁠⁠Patreon⁠⁠ Show notes https://pod.fo/e/1720c4 --- Send in a voice message: https://podcasters.spotify.com/pod/show/bkam/message

How do you compile knowledge?  How do you capture ideas, inspirations, insights, and connections?  How do you keep it all organized?  What would it look like to do this for a team or mob?  Join Chris as he explores with Vince Carpino and Jason Storey the intriguing world of second brains. First, Vince defines a second brain and shares about his productivity journey with second brains. Second, they dive into the many different implementations of a second brain ranging from Zettelkasten to Bullet Journaling to Commonplace Books. Throughout they not only talk about benefits of having a second brain but they also share their own personal experiences with them. Lastly, they give some tips for a team or mob who may want to experiment with implementing a collective second brain.  FYI: Video and show notes to be posted here in the next day or so. 

Joël's been traveling. Stephanie's working on professional development. She's also keeping up a little bit more with Ruby news and community news in general and saw that Ruby 3.2 introduced a new class called data to its core library for the use case of creating simple value objects. This episode is brought to you by Airbrake (https://airbrake.io/?utm_campaign=Q3_2022%3A%20Bike%20Shed%20Podcast%20Ad&utm_source=Bike%20Shed&utm_medium=website). Visit Frictionless error monitoring and performance insight for your app stack. Maggie Appleton's Tools for Thought (https://maggieappleton.com/tools-for-thought) Episode on note-taking with Amanda Beiner (https://www.bikeshed.fm/357) Obsidian (https://obsidian.md/) Zettelkasten (https://zettelkasten.de/posts/overview/) Evergreen notes (https://notes.andymatuschak.org/Evergreen_notes) New Data class (https://ruby-doc.org/3.2.0/Data.html) Joël's article on value objects (https://thoughtbot.com/blog/value-object-semantics-in-ruby) Episode on specialized vocabulary (https://www.bikeshed.fm/356) Primitive Obsession (https://wiki.c2.com/?PrimitiveObsession) Transcript: AD: thoughtbot is thrilled to announce our own incubator launching this year. If you are a non-technical founding team with a business idea that involves a web or mobile app, we encourage you to apply for our eight-week program. We'll help you move forward with confidence in your team, your product vision, and a roadmap for getting you there. Learn more and apply at tbot.io/incubator. STEPHANIE: Hello and welcome to another episode of The Bike Shed, a weekly podcast from your friends at thoughtbot about developing great software. I'm Stephanie Minn. JOËL: And I'm Joël Quenneville. And together, we're here to share a little bit of what we've learned along the way. STEPHANIE: So, Joël, what's new in your world? JOËL: I've been traveling for the past few weeks in Europe. I just recently got back to the U.S. and have just gotten used to drinking American-style drip coffee again after having espresso every day for a few weeks. And it's been an adjustment. STEPHANIE: I bet. I think that it's such a downgrade compared to European espresso. I remember when I was in Italy, I also would really enjoy espresso every day at a local cafe and just be like sitting outside drinking it. And it was very delightful. JOËL: They're very different experiences. I have to say I do enjoy just holding a hot mug and sort of sipping on it for a long time. It's also a lot weaker. You wouldn't want to do a full hot mug of espresso. That would just be way too intense. But yeah, I think both experiences are enjoyable. They're just different. STEPHANIE: Yeah. So, that first day with your measly drip coffee and your jet lag, how are you doing on your first day back at work? JOËL: I did pretty good. I think part of the fun of coming back to the U.S. from Europe is that the jet lag makes me a very productive morning person for a week. Normally, I'm a little bit more of an evening person. So I get to get a bit of an alter ego for a week, and that helps me to transition back into work. STEPHANIE: Nice. JOËL: So you've also been on break and have started work again. How are you feeling productivity-wise, kicking off the New Year? STEPHANIE: I'm actually unbooked this week and the last week too. So I'm not working on client projects, but I am having a lot of time to work on just professional development. And usually, during this downtime, I also like to reassess just how I'm working, and lately, what that has meant for me is changing my note-taking process. And I'm really excited to share this with you because I know that you have talked about this on the show before, I think in a previous episode with a guest, Amanda Beiner. And I listened to that episode, and I was really inspired because I was feeling like I didn't have a note-taking system that worked super well for me. But you all talked about some tools you used and some, I guess, philosophies around note-taking that like I said, I was really inspired by. And so I hopped on board the Obsidian train. And I'm really excited to share with you my experience with it. So I really like it because I previously was taking notes in my editor under the impression that, oh, like, everything is in one place. It'll be like a seamless transition from code to note-taking. And I was already writing in Markdown. But I actually didn't like it that much because I found it kind of distracting to have code things kind of around. And if I was navigating files or something, something work or code-related might come up, and that ended up being a bit distracting for me. But I know that that works really well for some people; a coworker of ours, Aji, I know that he takes his notes in Vim and has a really fancy setup for that. And so I thought maybe that's what I wanted, but it turns out that what I wanted was actually more of a boundary between code and notes. And so, I was assessing different note-taking and knowledge management software. And I have been really enjoying Obsidian because it also has quite a bit of community support. So I've installed a few plugins for just quality-of-life features like snippets which I had in my editor, and now I get to have in Obsidian. I also installed things like Natural Language Dates. So for my running to-do list, I can just do a shortcut for today, and it'll autofill today's date, which, I don't know, because for me, [laughs] that is just a little bit less mental work that I have to do to remember the date. And yeah, I've been really liking it. I haven't even fully explored backlinking, and that connectivity aspect, which I know is a core feature, but it's been working well for me so far. JOËL: That's really exciting. I love notes and note-taking and the ways that we can use those to make our lives better as developers and as human beings. Do you have a particular system or way you've approached that? Because I know for me, I probably looked at Obsidian for six months before I kind of had the courage to download it because I didn't want to go into it and not have a way to organize things. I was like; I don't want to just throw random notes in here. I want to have a system. That might just be me. But did you just kind of jump into it and see, like, oh, a system will emerge? Did you have a particular philosophy going in? How are you approaching taking notes there? STEPHANIE: That's definitely a you thing because I've definitely had the opposite experience [laughs] where I'm just like, oh, I've downloaded this thing. I'm going to start typing notes and see what happens. I have never really had a good organizational system, which I think is fine for me. I was really leaning on pen and paper notes for a while, and I still have a certain use case for them. Because I find that when I'm in meetings or one-on-ones and taking notes, I don't actually like to have my hands on the keyboard because of distractions. Like I mentioned earlier, it's really easy for me to, like, oh, accidentally Command-Tab and open Slack and be like, oh, someone posted something new in Slack; let me go read this. And I'm not giving the meeting or the person I'm talking to my full attention, and I really didn't like that. So I still do pen and paper for things where I want to make sure that I'm not getting distracted. And then, I will transfer any gems from those notes to Obsidian if I find that they are worth putting in a place where I do have a little bit more discoverability and eventually maybe kind of adding on to my process of using those backlinks and connecting thoughts like that. So, so far, it's truly just a list of separate little pages of notes, and yeah, we'll see how it goes. I'm curious what your system for organizing is or if you have kind of figured out something that works well for you. JOËL: So my approach focuses very heavily on the backlinks. It's loosely inspired by two similar systems of organization called Zettelkasten and evergreen notes. The idea is that you create notes that are ideas. Typically, the title is like a thesis statement, and you keep them very short, focused on a single thing. And if you have a more complex idea, it probably breaks down into two or three, and then you link them to each other as makes sense. So you create a web of these atomic ideas that are highly interconnected with each other. And then later on, because I use this a lot for either creating content in the future or to help refine my thinking on various software topics, so later on, I can go through and maybe connect three or four things I didn't realize connected together. Or if I'm writing an article or a talk, maybe find three or four of these ideas that I generated at very different moments, but now they're connected. And I can make an article or a talk out of them. So that's sort of the purpose that I use them for and how I've organized things for myself. STEPHANIE: I think that's a really interesting topic because while I was assessing different software for note-taking and, like I said, knowledge management, I discovered this blog post by Maggie Appleton that was super interesting because she is talking about the term tools of thought which a lot of these different software kind of leveraged in their marketing copy as like, oh, this software will be like the key to evolving your thinking and help you expand making connections, like you mentioned, in ways that you weren't able to before. And was very obviously trying to upsell you on this product, and she -- JOËL: It's over the top. STEPHANIE: A little bit, a little bit. So in this article, I liked that she took a critical lens to that idea and rooted her article in history and gave examples of a bunch of different things in human history that also evolved the ways humans were able to express their thoughts and solve problems. And so some of the ones that she listed were like storytelling and oral tradition. Literally, the written language obviously [laughs] empowered humans to be able to communicate and think in ways that we never were before but also drawings, and maps, and spreadsheets. So I thought that was really cool because she was basically saying that tools of thought don't need to be digital, and people claiming that these software, you know, are the new way to think or whatever, it's like, the way we're thinking now, but we also have this long history of using and developing different things that helped us communicate with each other and think about stuff. JOËL: I think that's something that appealed to me when I was looking at some of these note-taking systems. Zettelkasten, in particular, predates digital technology. The original system was built on note cards, and the digital stuff just made it a little bit easier. But I think also when I was reading about these ideas of keeping ideas small and linking them together, I realized that's already kind of how I tend to organize information when I just hold it in my brain or even when I try to do something like a tweet thread on Twitter where I'll try to break it up. It might be a larger, more complex idea, but each tweet, I try to get it to kind of stand on its own to make it easier to retweet and all that. And so it becomes a chain of related ideas that maybe build up to something, but each idea stands on its own. And that's kind of how in these systems notes end up working. And they're in a way that you can kind of remix them with each other. So it's not just a linear chain like you would have on Twitter. STEPHANIE: Yeah, I remember you all in that episode about note-taking with Amanda talked about the value of having an atomic piece of information in every note that you write. And since then, I've been trying to do that more because, especially when I was doing pen and paper, I would just write very loose, messy thoughts down. And I would just think that maybe I would come back to them one day and try to figure out, like, oh, what did I say here, and can I apply it to something? But it's kind of like doing any kind of refactoring or whatever. It's like, in that moment, you have the most context about what you just wrote down or created. And so I've been a little more intentional about trying to take that thought to its logical end, and then hopefully, it will provide value later. What you were saying about the connectivity I also wanted to kind of touch on a little bit further because I've realized that for me, a lot of the connection-making happens during times where I'm not very actively trying to think, or reflect, or do a lot of deep work, if you will. Because lately, I've been having a lot of revelations in the shower, or while I'm trying to fall asleep, or just other kinds of meditative activity. And I'm just coming to terms with that's just how my brain works. And doing those kinds of activities has value for me because it's like something is clearly going on in my brain. And I definitely want to just honor that's how it works for me. JOËL: I had a great conversation recently with another colleague about the gift of boredom and how that can impact our work and what we think about, and our creativity. That was really great. Sometimes it's important to give ourselves a little bit more blank space in our lives. And counter-intuitively, it can make us more productive, even though we're not scheduling ourselves to be productive. STEPHANIE: Yes, I wholeheartedly agree with that. I think a lot about the feeling of boredom, and for me, that is like the middle of summer break when you're still in school and you just had no obligations whatsoever. And you could just do whatever you wanted and could just laze around and be bored. But letting your mind wander during those times is something I really miss. And sometimes, when I do experience that feeling, I get a little bit anxious. I'm like, oh, I could be doing something else. There's whatever endless list of chores or things that are, quote, unquote, "productive." But yeah, I really like how you mentioned that there is value in that experience, and it can feel really indulgent, but that can be good too. MID-ROLL AD: Debugging errors can be a developer's worst nightmare...but it doesn't have to be. Airbrake is an award-winning error monitoring, performance, and deployment tracking tool created by developers for developers that can actually help cut your debugging time in half. So why do developers love Airbrake? It has all of the information that web developers need to monitor their application - including error management, performance insights, and deploy tracking! Airbrake's debugging tool catches all of your project errors, intelligently groups them, and points you to the issue in the code so you can quickly fix the bug before customers are impacted. In addition to stellar error monitoring, Airbrake's lightweight APM helps developers to track the performance and availability of their application through metrics like HTTP requests, response times, error occurrences, and user satisfaction. Finally, Airbrake Deploy Tracking helps developers track trends, fix bad deploys, and improve code quality. Since 2008, Airbrake has been a staple in the Ruby community and has grown to cover all major programming languages. Airbrake seamlessly integrates with your favorite apps to include modern features like single sign-on and SDK-based installation. From testing to production, Airbrake notifiers have your back. Your time is valuable, so why waste it combing through logs, waiting for user reports, or retrofitting other tools to monitor your application? You literally have nothing to lose. Head on over to airbrake.io/try/bikeshed to create your FREE developer account today! JOËL: So you mentioned recently that you've had a lot of revelations or new ideas that have come upon you or that you've been able to dig into a little bit more. Is there one you'd like to share with the audience? STEPHANIE: Yeah. So during this downtime that I've had not working on client work, I have been able to keep up a little bit more with Ruby news or just community news in general. And in, I think, an edition of Ruby Weekly, I saw that Ruby 3.2 introduced this new class called data to its core library for the use case of creating simple value objects. And I was really excited about this new feature because I remembered that you had written a thoughtbot blog post about value objects back in the summer that I had reviewed. That was an opportunity that I could make a connection between something happening in recent news with some thoughts that I had about this topic a few months ago. But basically, this new class can be used over something like a struct to create objects that are immutable in their values, which is a big improvement if you are trying to follow value objects semantics. JOËL: So, I have not played around with the new data class. How is it different from the existing struct that we have in Ruby? STEPHANIE: So I think I might actually answer that first by saying how they're similar, which is that they are both vehicles for holding pieces of data. So we've, in the past, been able to use a struct to very cheaply and easily create a new class that has attributes. But one pitfall of using a struct when you're trying to implement something like a value object is that structs also came with writer methods for all of its members. And so you could change the value of a member, and that it kind of inherently goes against the semantics of a value object because, ideally, they're immutable. And so, with the data class, it doesn't offer writer methods essentially. And I think that it freezes the instance as well in the constructor. And so even if you tried to add writer methods, you would eventually get an error. JOËL: That's really convenient. I think that may be an area where I've been a little bit frustrated with structs in the past, which is that they can be modified. They basically get treated as if they're hashes with a slightly nicer syntax to interact with them. And I want slightly harder boundaries around the data. Particularly when I'm using them as value objects, I generally don't want people to modify them because that might lead to some weird bugs in the code where you've got a, I don't know, something represents a time value or a date value or something, and you're trying to do math on it. And instead of giving you a new time or date, value just modifies the first one. And so now your start date is in the past or something because you happen to subtract a time from it to do a calculation. And you can't assign it to a variable anywhere. STEPHANIE: Yeah, for sure. Another kind of pitfall I remember noticing about structs were that the struct class includes the enumerable module, which makes a struct kind of like a collection. Whereas if you are using it for a value object, that's maybe not what you want. So there was a bit of discourse about whether or not the data class should inherit from struct. And I think they landed on it not inheriting because then you can draw a line in the sand and have that stricter enforcement of saying like, this is what a data as value object should be, and this is what it should not be. So I found that pretty valuable too. JOËL: I think I've heard people talk about sort of two classes of problems that are typically solved with a struct; one is something like a value object where you probably don't want it to be writable. You probably don't want it to be enumerable. And it sounds like data now takes on that role very nicely. The other category of problem is that you have just a hash, and you're trying to incrementally migrate it over to some nicer objects in some kind of domain. And struct actually gives you this really nice intermediate phase where it still mostly behaves like a hash if you needed to, but it also behaves like an object. And it can help you incrementally transition away from just a giant hash into something that's a little bit more programmatic. STEPHANIE: Yeah, that's a really good point. I think struct will still be a very viable option for that second category that you described. But having this new data class could be a good middle ground before you extract something into its own class because it better encapsulates the idea of a value object. And one thing that I remember was really interesting about the article that you wrote was that sometimes people forget to implement certain methods when they're writing their own custom value objects. And these come a bit more out of the box with data and just provide a bit more like...what's the word I'm looking for? I'm looking for...you know when you're bowling, and you have those bumpers, I guess? [laughs] JOËL: Uh-huh. STEPHANIE: They provide just like safeguards, I guess, for following semantics around value objects that I thought was really important because it's creating an artifact for this concept that didn't exist. JOËL: And to recap for the audience here, the difference is in how objects are compared for equality. So value objects, if they have the same internal value, even if they're separate objects in memory, should be considered equal. That's how numbers work. That's how hashes work. Generally, primitives in Ruby behave this way. And structs behave that way, and the new data class, it sounds, also behaves that way. Whereas regular objects that you would make they compare based off of the identity of the object, not its value. So if you create two user instances, not ActiveRecord, but you could create a user class, you create two instances in memory. They both have the same attributes. They will be considered not equal to each other because they're not the same instance in memory, and that's fine for something more complex. But when you're dealing with value objects, it's important that two objects that represent the same thing, like a particular time for a unit of measure or something like that, if they have the same internal value, they must be the same. STEPHANIE: Right. So prior to the introduction of this class, that wasn't really enforced or codified anywhere. It was something that if you knew what a value object was, you could apply that concept to your code and make sure that the code you wrote was semantically aligned with this concept. And what was kind of exciting to me about the addition of this to the core class library in Ruby is that someone could discover this without having to know what a value object is like more formally. They might be able to see the use of a data class and be like, oh, let me look this up in the official Ruby docs. And then they could learn like, okay, here's what that means, and here's some rules for this concept in a way that, like I mentioned earlier, felt very implicit to me prior. So that, I don't know, was a really exciting new development in my eyes. JOËL: One of the first episodes that you and I recorded together was about the value of specific vocabulary. And I think part of what the Ruby team has done here is they've taken an implicit concept and given it a name. It's extracted, and it has a name now. And if you use it now, it's because you're doing this data thing, this value object thing. And now there's a documentation page. You can Google it. You can find it rather than just be wondering like, oh, why did someone use a struct in this way and not realize there are some implicit semantics that are different? Or wondering why did the override double equals on this custom class? STEPHANIE: Yeah, exactly. I think that the introduction of this class also provides a solution for something that you mentioned in that blog post, which was the idea of testing value objects. Because previously, when you did have to make sure that you implemented methods, those comparison methods to align with the concept of a value object, it was very easy to forget or just not know. And so you provided a potential solution of testing value objects via an RSpec shared example. And I remember thinking like, ooh, that was a really hot topic because we had also been debating about shared examples in general. But yeah, I was just thinking that now that it's part of the core library, I think, in some ways, that eliminates the need to test something that is using a data class anyway because we can rely a little bit more on that dependency. JOËL: Right? It's the built-in behavior now. Do you have any fun uses for value objects recently? STEPHANIE: I have not necessarily had to implement my own recently. But I do think that the next time I work with one or the next time I think that I might want to have something like a value object it will be a lot easier. And I'm just excited to play around with this and see how it will help solve any problem that might come up. So, Joël, do you have any ideas about when you might reach for a data object? JOËL: A lot of situations, I think, when you see the primitive obsession smell are a great use case for value objects, or maybe we should call them data objects now, now that this is part of Ruby's vocabulary. I think I often tend to; preemptively sounds bad, but a lot of times, I will try to be careful. Anytime I'm doing anything with raw numbers, magic strings, things like that, I'll try to encapsulate them into some sort of struct. Or even if it's like a pair of numbers, it always goes together, maybe a latitude and longitude. Now, those are a pair. Do I want to just be passing around a two-element array all the time or a hash that would probably make a very nice data object? If I have a unit of measure, some number that represents not just the abstract concept of three but specifically three miles or three minutes, then I might reach for something like a data class. STEPHANIE: Yeah, I think that's also true if you're doing any kind of arithmetic or, in general, trying to compare anything about two of the same things. That might be a good indicator as well that you could use something richer, like a value object, to make some of that code more readable, and you get some of those convenient methods for doing those comparisons. JOËL: Have you ever written code where you just have like some number in the code, and there's a comment afterwards that's like minutes or miles or something like that, just giving you the unit as a comment afterwards? STEPHANIE: Oh yeah. I've definitely seen some of that code. And yeah, I mean, now that you mentioned it, that's a great use case for what we're talking about, and it's definitely a code smell. JOËL: It can often be nice as you make these more domain concepts; maybe they start as a data object, but then they might grow with their own custom methods. And maybe you extend data the same way you could extend a struct, or maybe you create a custom class to the point where the user...whoever calls that object, doesn't really need to know or care about the particular unit, just like when you have duration value. If you have a duration object, you can do the math you want. You can do all the operations and don't have to know whether it is in milliseconds, or seconds, or minutes because it knows that internally and keeps all of the math straight as opposed to just holding on to what I've done before, which is you have some really big number somewhere. You have start is, or length is equal to some big number and then comment milliseconds. And then, hopefully, whoever does math on that number later remembers to do the division by 1,000 or whatever they need. STEPHANIE: I've certainly worked on code where we've tolerated those magic numbers for probably longer than we should have because maybe we did have the shared understanding that that value represents minutes or milliseconds or whatever, and that was just part of the domain knowledge. But you're right, like when you see them, and without a very clear label, all of that stuff is implied and is really not very friendly for someone coming along in the future. As well as, like you mentioned earlier, if you have to do math on it later to convert it to something else, that is also a red flag that you could use some kind of abstraction or something to represent this concept at a higher level but also be extensible to different forms, so a duration to represent different amounts of time or money to represent different values and different currencies, stuff like that. JOËL: Do you have a guideline that you follow as to when something starts being worth extracting into some kind of data object? STEPHANIE: I don't know if I have particularly clear guidelines, but I do remember feeling frustrated when I've had to test really complicated hashes or just primitives that are holding a lot of different pieces of information in a way that just is very unwieldy when you do have to write a test for it. And if those things were encapsulated in methods, that would have been a lot easier. And so I think that is a bit of a signal for me. Do you have any other guidelines or gut instincts around that? JOËL: We mentioned the comment that is the unit. That's probably a...I wasn't sure if I would have to call it a code smell, but I'm going to call it a code smell that tells you maybe you should...that value wants to be something a little bit more than just a number. I've gotten suspicious of just raw integers in general, not enough to say that I'm going to make all integers data objects now, but enough to make me pause and think a lot of times. What does this number represent? Should it be a data object? I think I also tend to default to try to do something like a data object when I'm dealing with API responses. You were talking about hashes and how they can be annoying to test. But also, when you're dealing with data coming back from a third-party API, a giant nested hash is not the most convenient thing to work with, both for the implementation but then also just for the readability of your code. I often try to have almost like a translation layer where very quickly I take the payload from a third-party service and turn it into some kind of object. STEPHANIE: Yeah, I think the data class docs itself has an example of using it for HTTP responses because I think the particular implementation doesn't even require it to have attributes. And so you can use it to just label something rather than requiring a value for it. JOËL: And that is one thing that is nice about something like a data object versus a hash is that a hash could have literally anything in it. And to a certain extent, a data object is self-documenting. So if I want to know I've gotten to a shopping cart object from a third-party API, what can I get out of the shopping cart? I can look at the data object. I can open the class and see here are the methods I can call. If it's just a hash, well, I guess I can try to either find the documentation for the API or try to make a real request and then inspect the hash at runtime. But there's not really any way to find out without actually executing the code. STEPHANIE: Yeah, that's totally fair. And what you said about self-documenting makes a lot of sense. And it's always preferable than that stray comment in the code. [laughs] JOËL: I'm really excited to use the data class in future Ruby 3.2 projects. So I'm really glad that you brought it up. I've not tried it myself, but I'm excited to use it in future projects. STEPHANIE: On that note, shall we wrap up? JOËL: Let's wrap up. STEPHANIE: Show notes for this episode can be found at bikeshed.fm. JOËL: This show has been produced and edited by Mandy Moore. STEPHANIE: If you enjoyed listening, one really easy way to support the show is to leave us a quick rating or even a review in iTunes. It really helps other folks find the show. JOËL: If you have any feedback for this or any of our other episodes, you can reach us @_bikeshed, or you can reach me @joelquen on Twitter. STEPHANIE: Or reach both of us at hosts@bikeshed.fm via email. JOËL: Thanks so much for listening to The Bike Shed, and we'll see you next week. ALL: Byeeeeeeeeeeeeee!!!!!!!!!!!! ANNOUNCER: This podcast is brought to you by thoughtbot, your expert strategy, design, development, and product management partner. We bring digital products from idea to success and teach you how because we care. Learn more at thoughtbot.com.

La newsletter è ottimale per fidelizzare e vendere. Ecco come trovare il tempo per portarla avanti. Per avere la tua consulenza gratuita sulla tua partita IVA con lo sponsor FiscoZen e risparmiare 50€ sulla soluzione tutto in uno, commercialista + tool per la contabilità, clicca qui: https://www.fiscozen.it/invitoINDIE50A Una newsletter funziona solo se è regolare. Devi trovare tempo ogni settimana? Ma chi ce l'ha tutto 'sto tempo? In questo video ti mostro come organizzarti per stare il minor tempo possibile e massimizzare il tuo business online. Ecco le risorse che ho citato: - Zettelkasten in Notion per costruire le tue idee giorno per giorno https://www.youtube.com/watch?v=0Z98hxWd2as - idee su cosa mandare ai tuoi iscritti email https://www.youtube.com/watch?v=wspWV-pcNBI&list=PLSJzKwiacm8ffCDPjzEeP7v86n_XUZUGP&index=7 - come vendere con la newsletter https://www.youtube.com/watch?v=bK4suYWqWzg&list=PLSJzKwiacm8ffCDPjzEeP7v86n_XUZUGP&index=13 - playlist sull'email marketing https://www.youtube.com/watch?v=6BP5XavfHEs&list=PLSJzKwiacm8ffCDPjzEeP7v86n_XUZUGP - Template e corso per creare più contenuti in meno tempo https://italianindie.com/creatanticontenutiutili RISORSE PER PRODUTTORI DI CONOSCENZA

As 2022 draws to a close, it's time to chill. Vikram Sathaye and Roshan Abbas join Amit Varma in episode 309 of The Seen and the Unseen to share wit, wisdom and life lessons that are priceless. There is cricket, there is singing, there are great bad jokes -- never has insight been so much fun! (For full linked show notes, go to SeenUnseen.in.) Also check out: 1. Roshan Abbas at Instagram, Twitter and his own website. 2. Vikram Sathaye at Instagram, Twitter and YouTube. 3. Roshan Abbas and the Creator Economy — Episode 239 of The Seen and the Unseen. 4. Kommune on YouTube, Facebook, Twitter and Instagram. 5. Speechless — Roshan Abbas and Siddharth Banerjee. 6. What the Duck With Vikram Sathaye -- Vikram Sathaye's talk show on YouTube. 7. How Sachin Destroyed My Life -- Vikram Sathaye. 8. Vikram Sathaye's breakout performance at the 2004 Ceat Cricket Awards. 9. Episodes of The Seen and the Unseen on the creator ecosystem with Roshan Abbas, Varun Duggirala, Neelesh Misra, Snehal Pradhan, Chuck Gopal, Nishant Jain, Deepak Shenoy and Abhijit Bhaduri. 10. The Loneliness of the Indian Man -- Episode 303 of The Seen and the Unseen (w Nikhil Taneja). 11. Pu La Deshpande. 12. Roam Research. 13. Zettelkasten on Wikipedia. 14. Dance Dance For the Halva Waala — Episode 294 of The Seen and the Unseen (w Jai Arjun Singh and Subrat Mohanty). 15. Parkinson's Law — C Northcote Parkinson. 16. Bhimsen Joshi on Spotify and YouTube. 17. Arnold: The Education of a Bodybuilder -- Arnold Schwarzenegger. 18. Papa Kehte Hain -- Mahesh Bhatt. 19. Ghar Se Nikalte Hi -- Song from Papa Kehte Hain. 20. Tarkash -- Javed Akhtar. 21. Vijay Tendulkar and Satyadev Dubey. 22. Wednesday, starring Jenna Ortega, directed by Tim Burton & others. 23. 1000 True Fans — Kevin Kelly. 24. 1000 True Fans? Try 100 — Li Jin. 25. The BarberShop with Shantanu. 26. The Refreshing Audacity of Vinay Singhal — Episode 291 of The Seen and the Unseen. 27. Stage.in. 28. Parasite — Bong Joon-ho. 29. Sunandan Lele on Instagram, Twitter, YouTube, LinkedIn and Facebook. 30. Atomic Habits — James Clear. 31. The Love Fools on Instagram, Zomato and Facebook. 32. Behave — Robert Sapolsky. 33. The Double ‘Thank-You' Moment — John Stossel. 34. Seinfeld -- Created by Larry David and Jerry Seinfeld. 35. 3 Deewarein (Nagesh Kukunoor), Satta (Madhur Bhandarkar) and Dil Vil Pyar Vyaar (Anant Mahadevan). 36. A Meditation on Form — Amit Varma. 37. Vijay Gokhale on Amazon. 38. The Evolution of Cricket — Episode 97 of The Seen and the Unseen (w Harsha Bhogle). 39. Profit = Philanthropy — Amit Varma. 40. Nudge -- Richard Thaler and Cass Sunstein. 41. Japan fans clean up the stadium after defeat to Croatia. 42. Euphoria on Hotstar/HBO. 43. Why I'm Hopeful About Twitter -- Amit Varma. 44. Lifespan: Why We Age – and Why We Don't Have To -- David Sinclair. 45. The Lifespan Podcast by David Sinclair. 46. Huberman Lab. 47. Muse: EEG-Powered Meditation & Sleep Headband. 48. Factfulness — Hans Rosling. 49. Genepath Diagnostics. 50. Abby Philips on Twitter, Instagram, YouTube and Google Scholar. 51. The Case Against Sugar — Gary Taubes. 52. The Big Fat Surprise: why butter, meat, and cheese belong in a healthy diet — Nina Teicholz. 53. The Obesity Code — Jason Fung. 54. Why We Sleep — Matthew Walker. 55.The Swimmers -- Sally El Hosaini. 56. Khakee: The Bihar Chapter -- Created by Neeraj Pandey. 57. Bihar Diaries -- Amit Lodha. 58. Angad Daryani of Praan on Twitter, Instagram and LinkedIn. 59. Robert Sapolsky's biology lectures on YouTube. 60. Jonathan Haidt on Amazon, Twitter, Google Scholar and his own website. 61. Anatomy of the Vertical Invader -- IMRB International. 62. Josh Talks and The Lallantop. 63. The full Cristiano Ronaldo Interview With Piers Morgan. 64. Anumita Nadesan on Spotify, YouTube and Instagram. 65. Kusha Kapila on Instagram and YouTube. 66. I Boiled My Buttocks for a Week -- Amit Varma. 67. Propah Lady -- Puma commercial directed by Reema Sengupta. 68. The Life and Times of Mrinal Pande — Episode 263 of The Seen and the Unseen. 69. Glimpses from the event with Zakir Hussain and Sachin Tendulkar. 70. Phineas Gage. 71. Don't think too much of yourself. You're an accident — Amit Varma's column on Chris Cornell's death. 72. Why We Choke — Amit Varma. 73. Garden -- The app for staying in touch. 74. A Creator of the Floating World — Episode 218 of The Seen and the Unseen (w Varun Duggirala). 75. The Artist's Way -- Julia Cameron. 76. Coverage of the Bawraas by YourStory, Times of India and Hindustan Times. 77. Varun Grover Is in the House — Episode 292 of The Seen and the Unseen. 78. Monsoon Wedding -- Mira Nair. 79. How to Be Successful -- Sam Altman. Check out Amit's online course, The Art of Clear Writing. And subscribe to The India Uncut Newsletter. It's free! Episode art: ‘Time For Adda' by Simahina.

The guys talk get into note-taking, Zettelkasten, Obsidian. Normal stuff too like Fusion 360, 3D Printing and CNC's.Watch on YoutubeDISCUSSED:✍️ Send Comments on this EpisodeDiscuss on Show SubredditPlease note: Show notes contains affiliate links.World CupFusion 360 Apocalyptic Prepping - Project ArchiverBenchmarking Fusion 360Journaling ExperienceZettelkasten.de / Obsidian.mdPrusa Layer Shifts are Back ☹️Just Make PartsFB Ad SuccessSUPPORT THE SHOWBecome a Patreon - Get the Secret ShowReview on Apple Podcast Share with a FriendShow InfoShow WebsiteContact Jem & JustinTiktok | YoutubeHOSTSJem FreemanCastlemaine, Victoria, AustraliaLike ButterMore LinksJustin BrouillettePortland, Oregon, USAPDX CNCNackMore Links

Society cannot be designed in a top-down way. Central planning was a historic blunder that harmed India -- even though it was conceived by great men with good intentions. Nikhil Menon joins Amit Varma in episode 306 of The Seen and the Unseen to talk about the flawed genius PC Mahalanobis, the planning commission, and his own life as a scholar. (For full linked show notes, go to SeenUnseen.in.) Also check out: 1. Nikhil Menon on Amazon and University of Notre Dame. 2. Planning Democracy: How A Professor, An Institute, And An Idea Shaped India -- Nikhil Menon. 3. The Evolution of Everything -- Episode 96 of The Seen and the Unseen (w Matt Ridley). 4.  The Use of Knowledge in Society — Friedrich Hayek. 5. Sherlock Holmes, Ramayana and Mahabharata. 6. The Rooted Cosmopolitanism of Sugata Srinivasaraju — Episode 277 of The Seen and the Unseen. 7. Religion and Ideology in Indian Society — Episode 124 of The Seen and the Unseen (w Suyash Rai). 8. Political Ideology in India — Episode 131 of The Seen and the Unseen (w Rahul Verma). 9. The Decline of the Congress -- Episode 248 of The Seen and the Unseen (w Rahul Verma). 10. The Intellectual Foundations of Hindutva — Episode 115 of The Seen and the Unseen (w Aakar Patel). 11. Aakar Patel Is Full of Hope — Episode 270 of The Seen and the Unseen (w Aakar Patel). 12. The Gita Press and Hindu Nationalism — Episode 139 of The Seen and the Unseen (w Akshaya Mukul). 13. The Discovery of India -- Jawaharlal Nehru. 14. The Collected Writings and Speeches of Dr Babasaheb Ambedkar. 15. Caste, Capitalism and Chandra Bhan Prasad -- Episode 296 of The Seen and the Unseen (w Chandra Bhan Prasad). 16. John Locke on Wikipedia, Britannica and Stanford Encyclopedia of Philosophy. 17. John Dewey on Wikipedia, Britannica and Stanford Encyclopedia of Philosophy. 18. The Ideas of Our Constitution — Episode 164 of The Seen and the Unseen (w Madhav Khosla). 19. Friedrich Hayek on Wikipedia, Britannica, Stanford Encyclopedia of Philosophy and Econlib. 20. The Fatal Conceit: The Errors of Socialism -- Friedrich Hayek..  21. ये लिबरल आख़िर है कौन? — Episode 37 of Puliyabaazi (w Amit Varma, on Hayek). 22. The Importance of the 1991 Reforms — Episode 237 of The Seen and the Unseen (w Shruti Rajagopalan and Ajay Shah). 23. India's Lost Decade — Episode 116 of The Seen and the Unseen (w Puja Mehra). 24. The Forgotten Greatness of PV Narasimha Rao — Episode 283 of The Seen and the Unseen (w Vinay Sitapati). 25. The Life and Times of Montek Singh Ahluwalia -- Episode 285 of The Seen and the Unseen. 26. The Gentle Wisdom of Pratap Bhanu Mehta -- Episode 300 of The Seen and the Unseen. 27. On Exactitude in Science (Wikipedia) — Jorge Luis Borges. 28. What is Libertarianism? — Episode 117 of The Seen and the Unseen (w David Boaz). 29. India's Greatest Civil Servant — Episode 167 of The Seen and the Unseen (w Narayani Basu, on VP Menon). 30. Angus Deaton, John von Neumann, Albert Einstein and Howard Aiken. 31. The Life and Times of Vir Sanghvi — Episode 236 of The Seen and the Unseen. 32. Les Misérables -- Victor Hugo. 33. Hardy Boys on Amazon. 34. One Hundred Years of Solitude -- Gabriel Garcia Marquez. 35. Love in the Time of Cholera -- Gabriel Garcia Marquez. 36. Midnight's Children -- Salman Rushdie. 37. Fixing Indian Education — Episode 185 of The Seen and the Unseen (w Karthik Muralidharan). 38. Shahid Amin and Sunil Kumar. 39. 300 Ramayanas -- AK Ramanujan. 40. Nehru's Debates — Episode 262 of The Seen and the Unseen (w Tripurdaman Singh and Adeel Hussain.) 41. Whatever happened To Ehsan Jafri on February 28, 2002? — Harsh Mander. 42. Who Broke Our Republic? — Episode 163 of The Seen and the Unseen (w Kapil Komireddi). 43. John McPhee on Amazon. 44. Mumbai Fables -- Gyan Prakash. 45. Emergency Chronicles — Gyan Prakash. 46. Gyan Prakash on the Emergency — Episode 103 of The Seen and the Unseen. 47. Delhi Reborn: Partition and Nation Building in India's Capital -- Rotem Geva. 48. A People's Constitution — Rohit De. 49. Jugalbandi: The BJP Before Modi — Vinay Sitapati. 50. The BJP Before Modi — Episode 202 of The Seen and the Unseen (w Vinay Sitapati). 51. India After Gandhi: The History of the World's Largest Democracy -- Ramachandra Guha. 52. Roam Research. 53. Zettelkasten on Wikipedia. 54. Linda Colley on Amazon and Princeton. 55. Gandhi as Mahatma -- Shahid Amin. 56. Tanika Sarkar, Neeladri Bhattacharya and Janaki Nair. 57. The Great Man Theory of History. 58. Pramit Bhattacharya Believes in Just One Ism — Episode 256 of The Seen and the Unseen. 59. Demystifying GDP — Episode 130 of The Seen and the Unseen (w Rajeswari Sengupta). 60. Milton Friedman on Amazon, Wikipedia, Britannica and Econlib. 61. The Man of System — Adam Smith (excerpted from The Theory of Moral Sentiments). 62. The Idea of India — Sunil Khilnani. 63. The Rocking-Horse Winner -- DH Lawrence. 64. Taylor Sherman and Niraja Gopal Jayal. 65. Kamyab Hum Karke Rahenge -- Lata Mangeshkar and Mohammed Rafi on central planning. 66. Naya Daur -- BR Chopra. 67. Chhodo Kal Ki Baatein -- Song from Hum Hindustani. 68. Char Dil Char Raahein -- KA Abbas. 69. Jhootha Sach (Hindi) (English) -- Yashpal. 70. Marxvaad Aur Ram Rajya — Karpatri Maharaj. 71. Narendra Modi takes a Great Leap Backwards — Amit Varma. 72. The Importance of Data Journalism — Episode 196 of The Seen and the Unseen (w Rukmini S). 73. Rukmini Sees India's Multitudes — Episode 261 of The Seen and the Unseen (w Rukmini S). 74. Circe -- Madeline Miller. 75. The Song of Achilles -- Madeline Miller. 76. The Thursday Murder Club -- Richard Osman. 77. Only Murders in the Building. Check out Amit's online course, The Art of Clear Writing. And subscribe to The India Uncut Newsletter. It's free! Episode art: ‘Central Planning' by Simahina.

This week's challenge: make a proper Zettelkasten.You can hear the after show and support Do By Friday on Patreon!------Edited by Alex Cox------Show LinksHow to Write a Morrissey Song ("Sing The Third") - YouTubeLin-Manuel Miranda Lip Bite | Know Your MemeTwitter: LexTwitter: GriffinBob Wachter on Twitter: "…moderate surge in SF…"How Cranbrook's Design Program Redefined How We Make and Talk About Graphic Design – Eye on DesignEmigre: MagazineCranbrook Style GuideHistory Of The FedEx Logo Design - Meaning & Evolution 2022Home | Paul Rand: Modernist Master 1914-1996Designculture • Massimo VignelliJan Tschichold : Design Is HistoryThe New Typography (Weimar and Now: German Cultural Criticism (Paperback)): Tschichold, Jan, McLean, Ruari, Kinross, Robin, Hendel, Richard: 9780520250123: Amazon.com: BooksJan Tschichold and the New TypographySwiss Style: The Principles, the Typefaces & the Designers – PRINT MagazineNo. 3236: The Humble Index CardGetting Started • Zettelkasten MethodThe Archive (macOS) • Zettelkasten MethodIntroduction to the Zettelkasten Method • Zettelkasten MethodFolgezettel • Zettelkasten Method(Recorded on Wednesday, November 30, 2022)

Joël is joined by Amanda Beiner, a Senior Software Engineer at GitHub, who is known for her legendary well-organized notes. They talk about various types of notes: debugging, todos, mental stack, Zetelkasten/evergreen notes, notetaking apps and systems, and visual note-taking and diagramming too! @amandabeiner (https://twitter.com/amandabeiner) Mermaid.live (https://mermaid.live) Monodraw (https://monodraw.helftone.com/) Zettlekasten (https://zettelkasten.de/introduction/) Evergreen Notes (https://notes.andymatuschak.org/Evergreen_notes) Notion (https://www.notion.so/) Obsidian (https://obsidian.md/) Transcript: JOËL: Hello and welcome to another episode of The Bike Shed, a weekly podcast from your friends at thoughtbot about developing great software. I'm Joël Quenneville. And today, I'm joined by Amanda Beiner, a Senior Software Engineer at GitHub. AMANDA: Hey, Joël. Great to see you. JOËL: And together, we're here to share a little bit of what we've learned along the way. So, Amanda, what is new in your world? AMANDA: Well, one thing I'm really excited about is that my team at GitHub is experimenting with how we're going to incorporate learning and sharing what we've learned with each other in new ways, and I'm really excited to see where people take that. So, one of the things that we're thinking of is that we all get really busy, and we all have exciting projects that we're working on in the day-to-day, and sometimes it can be really hard to pull yourself away from them to do some learning that would be something that will probably help you in the long run. But every time we do do projects like that, people are really excited about it, and people like to collaborate. So we're just trying to figure out how we can make that a more regular thing because it's great for our whole team. JOËL: I love that. Do you have a project or something that you've been getting into recently to learn? AMANDA: Yeah. One of the things that I have been working on is that this is the first backend-focused role that I've had in my entire career. So I feel like I just kind of keep pulling back layers on how different forms of magic work. And I'm just trying to get closer to the metal of what is powering our databases. And that's something that I've been really excited to learn some more about. JOËL: So it's digging into a lot of, like, Postgres and just general database theory. AMANDA: Yeah. So for me, I've spent a lot of time at the Active Record layer as I have been settling into my role and figuring out what our domain models are that we care about. And I'm trying to get a little bit more into the questions of why did these tables end up looking the way that they do? Why are they normalized or denormalized where they are? And trying to get a better idea of the theory behind those decisions. JOËL: And this is a new team that you've joined. AMANDA: This is an existing team that I've joined a year ago now. JOËL: So it sounds like you're dealing with a somewhat unfamiliar codebase. You're looking at a bunch of existing models and database tables. That can be a lot to process and understand when you first join a team. Do you have an approach that you like to use when you're looking at unknown code for the first time? AMANDA: Yeah. I usually like to dive right in as much as I can, even if it's with a very small bug fix or something like that, something that allows me to just get my hands dirty from the beginning and poke around what models I'm dealing with, and maybe some of the adjacent ones that I don't need to know about now but might want to come back to later. JOËL: One thing that I find is really helpful for me are diagramming and note-taking. So if it's something like a database table or ActiveRecord models that I'm not familiar with, if it's more than maybe two or three, which is probably the most I can keep in my head, I have to start drawing some kind of like an entity-relationship diagram or maybe even just a bulleted list somewhere where it's like here are the things and how they connect to each other. Otherwise, I'm like, I don't know, I don't have enough RAM in my brain for that. AMANDA: That sounds like a really helpful approach. How do you approach creating these diagrams? JOËL: Occasionally, I will just draw it out by hand with pen and paper. But more recently, I've been using tools like Mermaid.js and specifically the website mermaid.live that allows you to just put in some names and arrows, and it will build out a diagram for you. And that's been really helpful to explore and understand what is going on with different entities that relate to each other. AMANDA: I've used Mermaid.js recently, and I really enjoyed it as well. I found that writing something that lets me write words or something somewhat like words and takes care of the drawing for me is probably best for everyone involved. JOËL: Yeah, that's a good point. It's kind of like Markdown, the ability to just write a little bit of text and move on and not worry about the size of boxes or the shape of the arrows or whatever. It helps you to really stay in that flow and keep moving. AMANDA: I definitely agree. I feel like I can't have been the only person that somehow ended up very deep into the Figma documentation because I didn't quite know how to do what I was supposed to do, and I forgot what I was trying to draw in the first place. JOËL: Right. It's really easy to put your designer hat on and want to make something like a beautiful diagram when this is really more of a capturing your state of mind. It's a rough note, not something you're necessarily going to publish. So, in addition to visuals, do you find yourself taking a lot of notes when you're exploring code or debugging code? AMANDA: Yeah. I feel like I tend to jot a lot of things down, maybe class names, maybe some links to PRs or issues, or anywhere that might have context about what I'm looking at and how it got in that way. At this point in the process, it feels my notes usually feel like a bit of a bullet point list that doesn't quite make sense to me yet but maybe will get some shaping later. JOËL: What kind of things do you tend to record in those notes? AMANDA: I think one of the things that I'm usually trying to get out of those notes is just a snapshot of what I'm trying to accomplish at the time that I'm creating them. What's the bug that I'm trying to solve, and how did I get into this rabbit hole? So that if it ends up being the wrong one, I can follow my breadcrumbs back out and start a different way. JOËL: Oh, that is really powerful. I love the imagery you used there of following breadcrumbs. And I feel like that's sometimes something I wish I had when I'm either exploring a particular code path or trying to find a bug. And at some point, I've gone a pretty long path, and I need to back up. And I don't remember exactly where I was or how I got to this point, especially if I've gone down a path, backtracked a little bit, gone down a different path, backtracked, gone further down a third path. And so having breadcrumbs, I think, is a really valuable thing that I wish I did more when I was debugging. AMANDA: Yeah. And one of the most helpful breadcrumbs that I found is just a list of questions. What was the question that I was trying to answer when I opened this file or looked at this method, and did it help me solve that question or answer that question? And if the answer is no, then I can refer back to what the question was and try to think about what else might help me solve that question. JOËL: I also love that. It's really easy to get sidetracked by other questions or other ideas when exploring or debugging. And sometimes I find that half hour later, I haven't answered the original question I came here to answer, and I kind of haven't even tried. And so, maybe writing down my questions before I go down a path would help me stay more focused during a debugging session rather than just trying to keep it all in my head. AMANDA: I very much relate to getting nerd sniped by something that looks interesting but ultimately doesn't solve the original problem that you were trying to. JOËL: This even happens to me when I'm pair programming. And so we'll say out loud the question we're trying to answer is this; let's open this file. And then you go into it, and you're like, oh, now that is an unusual line of code right there. AMANDA: [laughs] JOËL: I wonder why they're doing that. Let me check the git blame on this line. Oh, it's from 2015? AMANDA: [laughs] JOËL: I wonder what was happening there. Was that part of a Rails upgrade? And then, at some point, the other person has to interject and be like, "That's all fascinating, but I think the question we're actually trying to answer is..." and we get back on track. AMANDA: I feel like that's a really good opportunity, maybe for a different kind of note of just interesting curiosities in a given codebase. I find that one of the skills that I'm trying to get better at is, rather than building a repository of information or answers to questions, just building a mental map of where the information I'm trying to find lives so that when someone asks me a question or when I have to solve something I don't necessarily know the answer, but I just know the resource to find that will point me in the direction of that answer. And I feel like those kinds of explorations are really helpful for building out that mental model, even if it may be at the time seems like an unrelated rabbit hole. JOËL: So this kind of note is a bit more permanent than a bread crumb style note would be. AMANDA: Yeah, maybe. And I guess maybe it's less of a note, and it feels kind of like an index. JOËL: Hmmm. AMANDA: Like something that's connecting other pieces of information. JOËL: That's really interesting. It's got me thinking about the fact that note-taking can be very different in different situations and for different purposes. So we've talked a little bit about debugging. I think we've mixed debugging and exploration. Maybe those two are not the same, and you treat notes differently. Actually, do you treat those two as different, or do you have different approaches to note-taking when you're exploring a new codebase versus debugging a particular problem? AMANDA: I think that those kinds of notes could probably be a little bit different because I think when I'm onboarding onto a new codebase, I'm trying to cast a pretty wide net and give some overall information about what these things do that by the time I'm very deep in debugging, it might be information that I already know very well. So I feel like maybe debugging notes are a little bit more procedural. They are a little bit more I did X, and I did Y, and I did Z, and these were the questions. And the introductory notes to a new codebase might be more along the lines of this is what this model does, and stuff that will eventually become second nature and might be useful to pass off to someone else who's onboarding but which I might myself not refer back to after a certain amount of time. JOËL: I see. That's an interesting point because not only might the type of notes you take be different in different scenarios, but even their lifespan could be different. The value of a debugging note, that sort of breadcrumbs, might really only be that useful for a few hours or a couple of days. I can imagine notes you're taking while you're exploring a codebase those might be helpful for a much longer period and, as you said, maybe in passing them on to someone else when they're joining a team. AMANDA: So that makes me think of whether the debugging notes should be as short-lived as I'm making them sound because I feel like there are times where you know you've debugged something previously, but you didn't keep the notes. Maybe they were just on a scrap of paper, and now they're gone. And I feel like I'd like to do a better job of digesting those notes a little bit better and eventually turning them into something that can be a little bit longer-lived. JOËL: That's fair. I find that, especially for debugging, I like to capture a lot of what was in my notes in the eventual commit message for the fix. Of course, my random breadcrumbs probably don't make sense in the commit message, but a lot of what I have learned along the way often is helpful. AMANDA: That's a really good point. I hadn't thought of commit messages as notes, but you're right; they totally are. JOËL: One thing I've done is I've sort of taken this idea to the extreme. I was debugging some weird database table ActiveRecord model interactions, and the modeling was just a little bit unusual. There were multiple sources of truth in the relationships. And there were enough models that I struggled to really understand what was going on. And so I drew an entity-relationship diagram. And I felt that that was important to understand for people reviewing the code but also anybody looking back at the commit later on. So I used a tool called Monodraw, which allows you to draw simple diagrams as ASCII art. And so, I have a little ASCII art ERD in my commit message. AMANDA: That's incredible. I feel like if I were a developer git logging and I saw that commit message, I would be both thrilled and terrified of what exactly I was diving into in the git blame. [laughs] JOËL: Definitely both, definitely both. But I have referred back maybe a few months later. Like you said, I had to refer back to that commit because a similar bug had cropped up somewhere else. And I knew that that commit had information that I had gathered that would make the debugging experience easier. AMANDA: I guess the commit message is a really good example of having a note that's very closely tied to its context. Like, it's in the context of like a commit, which is a set of changes at a point in time, and it's really well situated in there. What do you think about the trade-offs of having that as part of a commit message versus something like some other sort of documentation where something like that could live? JOËL: I guess it depends on how you think you're going to use it in the future. Again, for debugging things, it feels like you don't often need to refer back to them, so I don't think you would want to just dump that on a wiki somewhere. It probably makes sense to have that either in just a collection of debugging notes that you have or that you could then dig into if you needed or in a commit message, something like that. But maybe some of the things that you learned along the way could be pulled out and turned into something that lives somewhere else that's maybe less of a note at that point and more of a publication. AMANDA: That sounds like a fine line between note and publication. JOËL: Perhaps it's an artificial line that I'm making. AMANDA: [laughs] JOËL: But yeah, I guess the idea is that sometimes I will look at my own debugging notes and try to turn them into something like either a wiki page for a particular codebase or potentially even a blog post on the thoughtbot blog, something that I've been able to synthesize out of the notes there. But now you've kind of gone a few steps beyond the underlying raw notes. AMANDA: I'm interested in your thoughts on that synthesis of notes into how does something go from a commit message into a blog? What does that process look like for you? JOËL: I have a personal note-taking system that's loosely inspired by a system called Zettelkasten and also another similar system called evergreen notes. The idea is that when you learn things, you capture small atomic notes, so they are an idea in your note-taking application, and then you connect them. You create links between notes. And the idea is that there's a lot of value in making connections between notes that's almost as much part of the knowledge-creating experience as capturing single notes on their own. And as you capture a bunch of these little, tiny notes over time and they become very interconnected, then you can start seeing, oh, this note from this one experience, this note from this conference talk, and this note from this book all connect together. And they maybe even make connections I hadn't seen, or I hadn't thought of individually in those moments. But now I see that they all kind of come together with a theme. And I might then combine those together to make a blog post or to use as the foundation for a conference talk. AMANDA: That's really interesting. I like the concept of being able to capture bits of information at the time that they felt relevant without having to have an entire thesis in this note. Or that idea doesn't have to be fully fleshed out; it can become fleshed out later when you connect the dots. JOËL: That's a really powerful concept. One of the big ideas that I picked up through this was that there are always byproducts of knowledge creation. So if I'm writing a blog post, there are always some things that I cut that didn't make it into the blog post because I'm trying to keep it focused. But those are still things that I learned, things that are valuable, that could be used for something else. And so anytime I'm writing a blog post, preparing for a conference talk, learning some things in a debugging session by reading a book, there are always some things that I don't use necessarily immediately. But I can capture those little chunks, and eventually, I have enough of them that I can combine them together to make some kind of other work. AMANDA: I'm really curious about your process of creating those notes. If you're reading a blog post, say, to learn a new topic and you're taking notes on that, how do you go from this concept that you're learning in the blog post to these really focused notes that can be combined in other ways? JOËL: So the Zettelkasten approach suggests that you have two forms of notes, one it calls literature notes which are just sort of ideas you jot down as you are reading some work. You're reading a book or a blog post or watching a talk, and then, later on, you go and turn those into those atomic-separated, linked notes together, what Zettelkasten calls permanent notes. And so I'll often do that is just focus on the work itself and jot down some notes and then convert those later on into these smaller atomic chunks. AMANDA: That concept of taking a larger theme and then actually spending the energy to distill that into a different kind of artifact that might be helpful later on is really interesting. And I don't do Zettelkasten note-taking, but I've also found that to be useful in other contexts as well. JOËL: One thing that I sort of hold myself to is when I am writing those atomic notes is, I don't write them as bullet points. They're always written in prose and complete sentences. The title is usually a sort of thesis statement, a thing that I think is true or at least a thing that posits that could be true, and then a short paragraph expanding on that idea which I think helps cement a lot of information in my mind but also helps to give me little chunks of things that I can more or less copy-paste into an article and already have almost a rough draft of something I want to say. Do you find that when you synthesize ideas into notes that you do something similar, or do you stick mostly to bullet points? AMANDA: I think I might do a mixture of the two. I think procedurally, I use bullet points a lot, but I think those bullet points tend to be full sentences or several sentences together. I've definitely run up against some of the drawbacks of terseness, where they're less helpful when you refer back to it later. But I do like the visual cues that come with things like bullet points, or numbered lists, or even emoji and note-taking to be a visual cue of what I was thinking of or where I can find this later on. JOËL: I love emoji; emoji is great. AMANDA: I guess actually I've started using emoji as bullet points. That's something that I've found even to be helpful just with remembering or with grouping things thematically in my mind. And when I'm going back through my notes, I find it easier to find the information that I was looking for because it had a list, or an emoji, or an image, or something like that. JOËL: Yeah, that makes it really easy to scan and pick out the things that you're looking for. It's almost like adding metadata to your notes. AMANDA: Totally. JOËL: That's a great tip. I should do that. AMANDA: You can definitely run into the Figma problem of you then spend so much time finding the right emoji to be the bullet point that you forgot what you were doing, [laughs] but that's a problem for a different day. JOËL: So this sort of Zettelkasten evergreen notes approach is a system that I use specifically to help me capture long-term thoughts about software that could eventually turn into content. So this is very much not a debugging note. It's not an exploratory note. It has a very particular purpose, which is why I write it in this particular way. I'm curious; I know you have a lot of different systems that you use for your notes, Amanda. Is there one that you'd like to share with the audience? Maybe tell us a little bit about what the system is and why it's a good fit for the type of scenario that you'd like to use it in. AMANDA: Sure. One situation that I found myself in recently is I have started taking classes on things that I'm interested in, development-related and non-development-related. And that's a formal structure that requires some note-taking that I haven't really done since I was in school. And the tools were very different back then as to what we had available to us for note-taking. It was basically Microsoft Word or bust. So I have found myself having to develop a new note system for that kind of content delivery method, basically of watching a video and taking notes and having something that then makes sense outside of the context of sitting down and watching a video. So that has been a little bit of a process journey that I've been on the last couple of months. JOËL: And what does your note-taking system look like? AMANDA: So it's been a mix of things, actually. I started out just kind of brain-dumping as I went along with the instructor talking trying to type and keep up. And I found that very not scannable to look back on. I was looking for some more visual cues, and I didn't really have time to insert those visual cues as I was trying to keep up with a lecture essentially. I then transitioned back to old school pen and paper, like, got myself a notebook and started writing in it. And obviously, that has some benefits of the free-formness, like, I'm not constrained by the offerings of any specific tool. But the trade-off for that is always that you have different notebooks for everything. And it's like, where's my X class notebook? And so I've been trying to bring those two methods together into something that makes a little bit more sense for me and also bring in some of that synthesis process that you were talking about with your note-taking method of doing the full literature notes and then synthesizing them down into something a little bit more well-scoped for the particular piece of information. JOËL: So you have like a two-step process then. AMANDA: It did end up being a two-step process because one of the things that I found was the grouping of ideas that make sense when you're first learning a concept and the grouping of ideas that make sense when I'm revisiting that concept, later on, aren't necessarily the same. And so, keeping it in the original context doesn't necessarily help me recall the information when I'm referring back to my notes. JOËL: That's really interesting. When you're writing it, it's going to be different than when you're reading it. So we've been talking a lot about the purpose of different notes along the way, and you mentioned the word recall here. Do you use these notes mostly as a way to recall things that you would look back at them and try to remember, or are they more of a way to digest the material as you're going through it? AMANDA: I think at the time that I'm writing them, they definitely served the purpose of helping me digest the information. But at some point, I probably want to be able to look back at them and remember the things that I learned and see if maybe they have new salience now that I have sat on them for a little bit. JOËL: Hmmm, that's good. So it's valuable for both in different contexts. AMANDA: Yeah, definitely. And one of the more surprising things that I've learned through that process has been that when I'm learning something, I really like a chronological kind of step-by-step through that process and building blocks of complexity that basically go one on top of the other. But then, once I've kind of made it to the end when I look back on it, I look back on those notes, and they're usually pretty thorough. They probably have a lot of details that aren't going to be top-level priority at the end. But I didn't really have that concept of priority when I was first learning it. I was kind of grasping onto each bit of information, saying, "I'm going to scroll this away in case I need it later." And then when you get a better understanding of the full picture, you realize, okay, I'm glad that I know that, but it's not necessarily something that I'd want to look back on. So I really like having systems that then allow me to regroup that information once I have built out a fuller picture of what it is I'm trying to learn. JOËL: Interesting. So the sort of digesting step that happens afterwards or the synthesis step, a lot of the value that you're adding there is by putting structure on a lot of the information you captured. AMANDA: Yeah, I think putting structure and changing the structure, and not being afraid to change that structure to fit my new understanding in how I see this concept now instead of just how this concept was explained to me. JOËL: So you mentioned that you'd initially used notebooks and paper and that that felt a little bit constraining in terms of organization. Is there any kind of software or apps that you like to use to organize your notes, and how do they fit in with your approach to note-taking? AMANDA: I've been using Notion for the last few years. I found that that application works well with my visual preferences for note-taking. I think there's a lot of opportunity for visual cues that help me recall things, such as emoji and bullet points. And I like that I can do all of that by writing Markdown without then also having to read Markdown. JOËL: Yeah, I definitely agree that a little visual change there where you can actually see the rendered Markdown is a nice quality-of-life improvement. AMANDA: Absolutely. And I also think that the way that it turns Markdown into blocks that then you can rearrange has served me really well for that synthesis process of maybe this bullet point makes sense, and I want to keep it as is. But I want to rearrange it into these new themes that I'm seeing as I'm reviewing these things that I've learned. JOËL: That's fascinating. So it has some really good tools for evolving your notes and reorganizing them, it sounds like. AMANDA: I like that I can group my notes by concept, and notes can be subsets or sub-notes of other notes. And you can kind of move the individual notes in between those blocks pretty easily, which helps me rearrange things when I see different themes evolving. JOËL: I've heard really good things about Notion, but I've not tried it myself. My app of choice so far has been Obsidian, which I really appreciate its focus on linking between notes. It doesn't have this concept of blocks where you can embed parts of notes as notes into other notes and things like that. But that has been okay for me because I keep my notes very small and atomic. But the focus on hyperlinking between notes has been really useful for me because, in my approach, it's all about the connections. AMANDA: So, what does that process look like when you are referring back to all of these notes that are hyperlinked together? JOËL: That's actually really important because the recall aspect is a big part of how you would use a note-taking system. For me, it's sort of like walking the graph. So I'll use search, or maybe I know a note that's in the general theme of what I care about, and then I'll just follow the links to other related articles or notes that talk about things that are related to it. And I might walk that graph three, four steps out in a few different directions. It's kind of like surfing Wikipedia. You find some entry point, and then you just follow the links until you have the material that you're interested in. AMANDA: It sounds like creating a Wikipedia wormhole of your own. JOËL: It kind of is. I guess, in a way, it's kind of like a little mini personal wiki where the articles are very, very condensed because I have that limitation that everything must be atomic. Wow. So this has been a really fascinating conversation. I feel like one of the big takeaways that I have is that types of notes matter. Note-taking can take very different forms in different contexts. And the way you organize them would be vastly different; how long you care about them is also going to be different. So going into a particular situation, knowing what sort of situation is this that I'm using notes and what is their purpose is going to be really helpful to think in terms of how I want to do my note-keeping. Whereas I think previously, I probably was just like, yeah, notes. You open a document, and you put in some bullet points. AMANDA: I am definitely guilty of doing that as well. And I like the idea of having a purpose for your notes. You mentioned your purpose was ultimately to build a map that would produce content. And I really like how you have found a system that works really well for that purpose. And I'm going to keep thinking about how to be more intentional in what is the purpose of the notes that I'm taking in the future. JOËL: Well, thank you so much for joining the conversation today. Where can people find you on the web? AMANDA: Thanks so much for having me, Joël. You can find me @amandabeiner on Twitter. JOËL: And we'll link to that in the show notes. And with that, let's wrap up. The show notes for this episode can be found at bikeshed.fm. This show is produced and edited by Mandy Moore. If you enjoyed listening, one really easy way to support the show is to leave us a quick rating or even a review in iTunes. It really helps other folks find the show. If you have any feedback, you can reach us at @_bikeshed, or reach me at @joelquen on Twitter, or at hosts@bikeshed.fm via email. Thank you so much for listening to The Bike Shed, and we'll see you next week. Byeeeeeeee!!!!!!! ANNOUNCER: This podcast was brought to you by thoughtbot. thoughtbot is your expert design and development partner. Let's make your product and team a success.

Link to submit questions: bit.ly/3U3sTvoCAL REACTS: Brandon Sanderson't Underground Lair [2:49]- Was it a mistake to drop out of college? [21:49]- What tools should I use to manage my processes? [28:47]- CALL: Help with slow productivity [32:12]- What hobbies will improve my concentration? [37:34]CASE STUDY: Building a Deep Life on House Hacking (plus: thoughts on FIRE) [43:22]- Is Cal using Zettelkasten? [58:06]- How I schedule work with an unpredictable medical issue? [1:01:38]Books Cal Read in September, 2022 [1:15:07]Thanks to our Sponsors:eightsleep.com/Deeppolicygenius.comrhone.com/Calexpressvpn.com/DeepThanks to Jesse Miller for production, Jay Kerstens for the intro music, and Mark Miles for mastering.

We'll be talking about character spectrums. More specifically, we'll be covering Brandon Sanderson's sliding scales for writing a character: likability, proactivity, and competence. And our tool tip of the week is the Zettelkasten notetaking system. Stay tuned to hear about how a 20th century German sociologist inspired a modern-day open source note taking software. Picks of the Week: Dune Messiah by Frank Herbert Things that Matter by Joshua Becker How to Take Smart Notes by Sonke Ahrens Mentioned in the Episode: Brandon Sanderson BYU Lecture on Character Brandon Sanderson's Writing Excuses Podcast Obsidian Open-Source Software

“Crumb time” is the little pieces of time that get lost throughout the day. Instead of giving away your crumb time to unproductive distractions, build systems that complete big projects with small actions. Today, I'll tell you how. Crumb time is everywhere throughout our days. Whenever we do something substantial with our time, little chunks of time of various sizes and shapes fall to the floor. What is crumb time? Crumb time has a combination of the following qualities: Short amounts of time. Crumb time can be less than a minute, or several minutes. Unknown lengths of time. You often don't know when your crumb time will be over. It could end in a few seconds, or a few minutes. Distracting environments. It's hard enough to focus when you don't know when you'll be interrupted, but the environments in which crumb time take place are often noisy, with lots of activity. Some examples of crumb time: Standing in line at an airport: Lots is going on, you're waiting for your boarding call. Riding in a cab: The scenery is changing, but you might have a good idea how much time you have. Waiting for a friend to meet you for lunch: They could come in the door in two seconds, or twenty minutes. Why do we give away crumb time? Crumb time feels insignificant, and we think we need a controlled environment and a big block of time to do anything useful. You don't have the time or mental bandwidth, it seems, to make substantial progress reading a book, or writing an article. So, we doomscroll on Twitter, blow off steam with a game such as Wordle, or do something pseudo-productive such as check email once again. Productive uses of crumb time We just give away our crumb time, but we could turn it into something useful. Here are some things you could do with crumb time: Review highlights in your Zettelkasten: My favorite use of crumb time is reviewing my highlights from a book. I export them to Markdown, and whenever I have a moment, I scroll through the highlights in a plain-text app on my phone. I bold any of the highlights that are extra interesting. When my crumb time is over, I mark my place and lock my phone. Learn about something: A crumb-time list is a key component of a system of curiosity management, which I talked about on episode 284. Keep a list of subjects you'd like to learn about, and when you have crumb time, read a Wikipedia page. (I'm not a fan of read-later apps, because the easier it is to save articles, the harder it is to read all of them). Brainstorm social media updates: Twitter is a great place to share ideas, a terrible place to have them. Brainstorm potential tweets in a text file, to polish and schedule later. How about doing nothing at all? Another valid use of your crumb time is simply doing nothing. But when you choose to do something, you may as well do something useful. Anything other than giving away crumb time is better than building that bad habit. The more you give away crumb time, the easier that becomes the default use of your crumb time. Take a seven-day crumb-time challenge You don't need to change your crumb time habits all at once, forever. Instead, try a seven-day crumb-time challenge. Here's how: Delete social media apps. You can do most things on Twitter or Instagram from desktop. Get them off your phone, to force yourself to make good use of crumb time. Block social media websites. Use the parental controls on your phone to block websites to which you give away your crumb time. For me that's twitter.com and instagram.com. On the iPhone, use the “Limit Adult Websites” feature, and add whatever sites you want to the block list. (You can also add adult websites to the allowed sites if that's your thing.) Set up crumb-time actions. If you have a Zettelkasten, you know what to do. If you don't have one, for a quick-start you could export your highlights from your favorite book and have them available on your phone. Set up a list of things you'd like to look up when you have crumb time. Set up a scratch file for brainstorming social media updates, or set up anything else you could make progress on when you have a minute. Audio crumb time You're of course not always able to use your hands during crumb time, such as when you're driving. This is actually a great reason to have a podcast. Sharing your ideas with others is nice, but if you want to review your own ideas during crumb time, with a podcast you already have a convenient format in which to do so. But, you can also listen to articles or text you'd like to review using the text-to-speech feature on your phone, or an app, such as Otter. Crumb time becomes something bigger I like the term “crumb time” not only because it implies crumb time's perceived insignificance, but also because substantial things consist of crumbs. Bakers talk about the “crumb structure” of a cake, which is the mix of air and pastry that makes up the cake. In agriculture, soil has taken on a “crumb structure” when it has the right amount of moisture for the soil to bead into crumbs. Soil with a crumb structure has an ideal mix of air and moisture to be a good environment for plants to take root, and for microorganisms to assist in the plant's growth. Crumb time is powerful because it seems too insignificant to be worth anything. But if you use your crumb time well, those little pieces of time can build into something bigger. Here are some ways: Write a book: A book is little more than a collection of thoughts, and crumb time is enough to develop individual thoughts. I shared on episode 260 my newsletter system, which makes use of crumb time: My tweets grow into newsletters, which grow into podcast articles, which grow into books. Or, you can take a more direct approach. Walter Isaacson has said he writes on his phone while waiting in the airport, and Kirsten Oliphant wrote an entire book during two weeks' time on the treadmill. Build a database of knowledge: Instead of writing a book, you can aim to build a database of knowledge, such as the Zettelkasten I talked about on episode 250. Highlighting highlights is the easiest use of crumb time, but you can do other Zettelkasten tasks with your crumb time, such as clearing your inbox. Make real progress: Even if you don't aspire to write a book or build a Zettelkasten, you can use your crumb time to make real progress on any of your projects. Think of crumb time as a “context”, a la Getting Things Done. Just as you might mark a next action as “@home”, “@office”, or with my Seven Mental States of creativity, you can mark tasks as “@crumbtime”. Then you have a list of tasks you can do with little time and attention. Imagine what your crumb time could become Pay attention to how you use your crumb time, and you'll find significant uses of time and energy that could be put toward something productive. In the same time and mental effort it takes to play Wordle every day, you could build a database of knowledge, write articles, or even books. I encourage you to try a seven-day crumb-time challenge. Let me know how it goes! Image: Pexals Thank you for having me on your podcasts! Thank you for having me on your podcasts. Thank you to Ben Henley-Smith at Cord's Best Work podcast. As always, you can find all podcasts I've been on at kadavy.net/interviews. About Your Host, David Kadavy David Kadavy is author of Mind Management, Not Time Management, The Heart to Start and Design for Hackers. Through the Love Your Work podcast, his Love Mondays newsletter, and self-publishing coaching David helps you make it as a creative. Follow David on: Twitter Instagram Facebook YouTube Subscribe to Love Your Work Apple Podcasts Overcast Spotify Stitcher YouTube RSS Email Support the show on Patreon Put your money where your mind is. Patreon lets you support independent creators like me. Support now on Patreon »       Show notes: http://kadavy.net/blog/posts/crumb-time/

When Facebook was first expanding, they used a timeless military strategy to win their most-crucial first users. You can use this strategy to attack your toughest projects, by leveraging hidden complexity to lend devastating power to simple actions. Facebook faced tough competitors When Facebook was starting, in the mid-aughts, it was only available at colleges. It wasn't easy to win new users on campuses that had their own social networks. Who wants to join the network nobody is on? That's not where you find the big parties. That's not how you spy on your crush. There was no point in promoting to students who already had better alternatives. Facebook would waste their limited resources, driving themselves out of business. There were plenty of competitors they needed to outlast. An established network at a college was a barrier to winning over any user at that college – a “defense,” if you will. Facebook needed to break through those barriers. The surround strategy: Attack from the flanks So they used what they called a “surround strategy”. Instead of directly trying to get users on a given campus, they got them indirectly. The strategy that decimated the Roman army 1800 years ago Facebook's surround strategy was borrowed from the “pincer” military strategy. When you're up against an opponent with strong defenses, it's often not the best use of your resources to attack them head-on. It's better to focus on the flanks. Hannibal used a pincer strategy in one of the greatest military upsets in history, at the Battle of Cannae, in 216 B.C., sending the Roman empire into a panic. As the Romans attacked from a concentrated center, the center of Hannibal's forces fell back, creating a “crescent” shape that helped them attack the flanks. Eventually, Hannibal had the Romans surrounded. The Romans lost so many men that day, they had to lower the draft age to replenish their forces, and they reverted to using human sacrifices to try to please the gods. How Facebook won key users indirectly Facebook used this pincer strategy to indirectly win users at Baylor University, in Texas, which already had its own social network. Instead of promoting Facebook to users at Baylor, they focused on campuses near Baylor There weren't already competing social networks at UT Arlington, a one and a half-hour drive to the north; Southwestern University, a one-hour drive to the southwest; and Texas A&M, a one and a half-hour drive to the southeast. To get the dirt on their exes, they needed to be on Facebook While Facebook wasn't wasting resources trying to get Baylor students to switch social networks, those students started to hear about Facebook, anyway. The students in these surrounding colleges were former high-school classmates of the Baylor students. They were driving to one another's campuses to bong beers and eat jello shots. They were hearing rumors their high-school sweethearts were getting naked with half the campus. They were laughing maniacally upon hearing the former bully was found passed out, naked with an armadillo. To get the dirt, to creep on one another's profiles, or, sometimes to just stay in touch, they too needed Facebook accounts. So, without any promotion at Baylor, Facebook started winning users at Baylor. The birthday problem reveals the hidden complexity that make the surround strategy work This surround strategy works better than people expect it to. To understand why, think about the birthday problem, which I talked about on episode 237. How many people have to be in a room for a fifty-percent chance two of them have the same birthday? Most people guess 180 or 150, but the real answer: only twenty-three. The odds of shared birthdays climb rapidly as you add the first few dozen people to the room. Network effects between each person's potential birthdates quickly add potential matches. Adding one person to a room of twenty people doesn't add just one potential match, it adds twenty. Network effects...outside the network Facebook's surround strategy leveraged these network effects. The colleges they focused on didn't have social networks, so Facebook quickly became very appealing, as they added users. Meanwhile, Facebook also became more appealing to the students at Baylor. Who wants to use a social network that only has students from your college?! With each new user Facebook added in a neighboring campus, they added multiple contacts to potential new users at Baylor. After someone heard about Facebook enough times, they had to sign up. As Hannibal's men surrounded Rome's, there were more angles from which each soldier on Hannibal's front could attack soldiers on Rome's front, but not vice-versa. A complementary strategy to the pincer is also the “pocket,” or isolating small portions of a battalion to conquer them bit by bit. Surround & conquer your dreams Now, how can you use this surround strategy on some of your biggest and most-intimidating visions? When you want to accomplish something that's too big to attack head-on, use the surround strategy to break down the project's defenses. Here's how to surround, and conquer, your toughest projects: Make a list of all the things you'd need to know or have to accomplish your goal. Brainstorm ways you could learn those skills or gain those resources with smaller projects. Take on the smaller projects that are most interesting to you, or that use your existing resources. As you take on these smaller projects related to your target project, network effects take over. The skills and resources you gain will make the larger project seem easier than it would otherwise, and you get some successes to build your confidence along the way, and learn the skill of shipping, like I talked about on episode 265. Surround & conquer Shakespeare Here's a very simple example: Let's say you want to read a Shakespeare play, but you can't keep track of what everyone is saying in that language that doth make one scratch one's head. Do this: Watch the movie. Read the Wikipedia page. Listen to the podcast. Finally, read the play. By staking out the easier-to-conquer territory in your mind, it's easier to conquer the more-fortified territory, and run back for supplies – or a reminder of what the heck is going on, based upon the other ways you've heard the story. How creators surround & conquer Other creators use the surround strategy, whether they say so, or not. Before the Steves Jobs and Wozniak built their first Mac, they worked on “blue boxes” they used to tap into phone networks and make prank calls. It was just a fun and mischievous and illegal project, but it helped build their collaborative relationship on something smaller and less complex. Henry Ford got a job working on steam engines, while running experiments in his garage to perfect the internal combustion engine. He made a living gaining the background he needed, and making connections with potential investors, while on nights and weekends he tinkered on the finer details. Michelangelo didn't paint the Sistine Chapel ceiling from scratch. He had libraries of plaster-casted drapery and terra cotta body parts he mixed and matched to draw compelling figures in his scenes. How I use the surround strategy I, personally, use the surround strategy whenever I can. For example, I want to write fiction, though I'm not a huge fiction reader myself. But, I do like movies. So, I've been reading screenplays of my favorite movies and reading the novels those movies are based upon, while dabbling in short stories under a pen name, and working on my storytelling skills in my non-fiction writing whenever possible. I'm learning to love fiction, while working on my fiction-writing skills. In fact, all my work is a surround strategy for conquering new books. Each of my tweets, my weekly Love Mondays newsletters, my podcast episodes and articles and notes in my Zettelkasten, are experiments with progressively larger ideas, the best of which build into a book every few years or so. Go forth and conquer The next time you're dreaming about something that seems impossible, surround it with projects that are possible. Then, your bigger dreams will be easier to conquer. About Your Host, David Kadavy David Kadavy is author of Mind Management, Not Time Management, The Heart to Start and Design for Hackers. Through the Love Your Work podcast, his Love Mondays newsletter, and self-publishing coaching David helps you make it as a creative. Follow David on: Twitter Instagram Facebook YouTube Subscribe to Love Your Work Apple Podcasts Overcast Spotify Stitcher YouTube RSS Email Support the show on Patreon Put your money where your mind is. Patreon lets you support independent creators like me. Support now on Patreon »       Show notes: http://kadavy.net/blog/posts/surround-conquer/

He grew up breathing Kannada literature -- and he also embraced the globalised world. Sugata Srinivasaraju joins Amit Varma in episode 277 of The Seen and the Unseen to discuss this confluence of the old and the new, the near and the far, his society and the world.  Also check out: 1. Sugata Srinivasaraju in Outlook, ToI/Mumbai Mirror, New Indian Express, The Wire, Mint, Twitter and his own website. 2. Furrows in a Field -- Sugata Srinivasaraju. 3. Pickles from Home: The Worlds of a Bilingual -- Sugata Srinivasaraju. 4. Keeping Faith with the Mother Tongue -- Sugata Srinivasaraju. 5. Sugata Srinivasaraju on his father, Chi Srinivasaraju: 1, 2, 3. 6. Maharashtra Politics Unscrambled -- Episode 151 of The Seen and the Unseen (w Sujata Anandan). 7. Dodda Alada Mara (Big Banyan Tree). 8. GP Rajarathnam, AR Krishnashastry, P Lankesh and KS Nissar Ahmed on Wikipedia. 9. The Tell Me Why series of encyclopedias -- Arkady Leokum. 10. Stendhal, Honoré de Balzac, Victor Hugo and Charles Baudelaire on Amazon. 11. Rayaru Bandaru Mavana Manege -- The KS Narasimhaswamy poem Sugata translated. 12. Phoenix and Four Other Mime Plays -- Chi Srinivasaraju (translated by Sugata Srinivasaraju, who tweeted about it here.). 13. Ahobala Shankara, V Seetharamaiah, Roland Barthes, Michel Foucault, Jacques Derrida, KV Narayana, Noam Chomsky, DR Nagaraj, Jorge Luis Borges and Tejaswini Niranjana. 14. Lawrence Weschler on how Akumal Ramachander discovered Harold Shapinsky. 15. AK Ramanujan and Gopalakrishna Adiga. 16. The Penguin Book of Socialist Verse -- Edited by Alan Bold. 17. Gandhi as Mahatma: Gorakhpur District, Eastern UP, 1921-22 -- Shahid Amin. 18. Kraurya -- Girish Kasaravalli. 19. Deconstructing Derrida -- Sugata Srinivasaraju. 20. Yaava Mohana Murali -- Gopalakrishna Adiga's poem turned into a song. 21. Ram Guha Reflects on His Life -- Episode 266 of The Seen and the Unseen. 22. Understanding Gandhi. Part 1: Mohandas — Episode 104 of The Seen and the Unseen (w Ram Guha). 23. Understanding Gandhi. Part 2: Mahatma — Episode 105 of The Seen and the Unseen (w Ram Guha). 24. Modern South India: A History from the 17th Century to our Times -- Rajmohan Gandhi. 25. Ki Ram Nagaraja at Book Brahma. 26. A Map of Misreading -- Harold Bloom. 27. The Singer of Tales -- Albert Lord and David Elmer. 28. ಪಂಪ ಭಾರತ ದೀಪಿಕೆ: Pampa Bharatha Deepike -- DL Narasimhachar. 29. The Open Eyes: A Journey Through Karnakata -- Dom Moraes. 30. Dom Moraes on DR Bendre's love for numbers. 31. DR Bendre, Kuvempu, Shamba Joshi, MM Kalburgi, Shivaram Karanth, VK Gokak and Chandrashekhar Patil. 32. Da Baa Kulkarni, Sriranga, Nabaneeta Dev Sen, Bhisham Sahni, Kartar Singh Duggal and HY Sharada Prasad. 33. His Will Was His God -- Sugata Srinivasaraju on HY Sharada Prasad. 34. Jeremy Seabrook on Amazon. 35. Aakar Patel Is Full of Hope -- Episode 270 of The Seen and the Unseen. 36. The Rise and Fall of the Bilingual Intellectual — Ramachandra Guha. 37. The Life and Times of Mrinal Pande -- Episode 263 of The Seen and the Unseen. 38. Sara Rai Inhales Literature -- Episode 255 of The Seen and the Unseen. 39. The Art of Translation -- Episode 168 of The Seen and the Unseen (w Arunava Sinha). 40. Negotiating Two Worlds, Bilingualism As A Cultural Idea -- Sugata Srinivasaraju delivers the HY Sharada Prasad Memorial Lecture. 41. Karunaalu Baa Belake -- A Kannada version of 'Lead, Kindly Light'. 42. Liberal impulses of our regional languages -- Sugata Srinivasaraju. 43. Why Resisting Hindi is No Longer Enough -- Sugata Srinivasaraju. 44, The Indianness of Indian Food -- Episode 95 of The Seen and the Unseen (w Vikram Doctor). 45. Steven Van Zandt: Springsteen, the death of rock and Van Morrison on Covid — Richard Purden. 46. Roam Research and Zettelkasten. 47. Sixteen Stormy Days — Tripurdaman Singh. 48. The First Assault on Our Constitution — Episode 194 of The Seen and the Unseen (w Tripurdaman Singh). 49. Nehru's Debates -- Episode 262 of The Seen and the Unseen (w Tripurdaman Singh and Adeel Hussain). 50. Speaking of Siva -- Ak Ramanujan's translations of the Vacanas. 51. Not Waving but Drowning -- Stevie Smith. 52. Pictures on a Page -- Harold Evans. 53. Notes From Another India -- Jeremy Seabrook. 54. Good Times, Bad Times -- Harold Evans. 55. John Pilger on Amazon. 56. Sugata Srinivasaraju's pieces in Outlook in 2005 on the Infosys land scam: 1, 2. 57. ‘Bellary Is Mine' -- Sugata Srinivasaraju. 58. Deca Log: 1995-2005. A history in ten-and-a-half chapters, through the eyes of Outlook -- Sugata Srinivasaraju. 59. The Sanjay Story: From Anand Bhavan To Amethi -- Vinod Mehta. 60. Lucknow Boy: A Memoir -- Vinod Mehta. 61. Remembering Mr. Shawn's New Yorker -- Ved Mehta. 62. Off the Record: Untold Stories from a Reporter's Diary -- Ajith Pillai. 63. A Town Offers Its Shoulder -- Sugata Srinivasaraju. 64. Superforecasting: The Art and Science of Prediction -- Philip Tetlock and Dan Gardner. 65. Dhanya Rajendran Fights the Gaze -- Episode 267 of The Seen and the Unseen. 66. The Story of an Income Tax Search — Dhanya Rajendran on Instagram. 67. George Plimpton, 76; 'Paper Lion' author, longtime literary editor, amateur athlete -- David Mehegan. 68. Does The Paris Review Get a Second Act? -- Charles McGrath on literary magazines as "showcases of idealism." 69. My Father's Suitcase -- Orhan Pamuk's Nobel Prize lecture. 70. Gandhi's Assassin: The Making of Nathuram Godse and His Idea of India -- Dhirendra K Jha. 71. Harmony in the Boudoir -- Mark Strand. 72. Of Human Bondage -- W Somerset Maugham. 73. Man's Worldly Goods -- Leo Huberman. 74. Autobiography -- Bertrand Russell. 75. Graham Greene, Joseph Conrad, Gabriel Garcia Marquez, Jorge Luis Borges, Honoré de Balzac, Gustave Flaubert, Victor Hugo, Charles Dickens and George Orwell on Amazon. 76. Madame Bovary -- Gustave Flaubert. 77. Reflections on Gandhi -- George Orwell. 78. The Tyranny of Merit -- Michael Sandel. 79. Home in the World: A Memoir -- Amartya Sen. 80. Living to Tell the Tale -- Gabriel Garcia Marquez. 81. Ayodhya - The Dark Night and Ascetic Games by Dhirendra Jha. 82. Team of Rivals -- Doris Kearns Goodwin. 83. My Last Sigh -- Luis Bunuel. 84. Interview with History -- Oriana Fallaci. 85. Ryszard Kapuscinski on Amazon. 86. Journalism as Literature -- Salman Rushdie on Ryszard Kapuscinski. 87. Mallikarjun Mansur, Bhimsen Joshi and Kumar Gandharva on Spotify. 88. Vachanas sung by Mallikarjun Mansur and Basavaraja Rajguru. 89. Outlander, Knightfall and Money Heist on Netflix. 90. Sugata Srinivasaraju's Twitter thread on the songs of DR Bendre. This episode is sponsored by The Desi Crime Podcast. You'll find them on all podcast apps. Check out Amit's online course, The Art of Clear Writing. And subscribe to The India Uncut Newsletter. It's free! The illustration for this episode is by Nishant Jain aka Sneaky Artist. Check out his work on Twitter, Instagram and Substack.