Podcasts about Cluster

Lange Zeit ist Europa der Vorreiter der globalen Energiewende. Inzwischen läuft China Ländern wie Deutschland technologisch den Rang ab. Im Umfeld der Volksrepublik erwächst außerdem neue Konkurrenz. In Staaten wie Thailand oder Vietnam boomen Elektromobilität und erneuerbare Energien. Aus Eigennutz: Sie möchten kein Geld mehr für fossile Importe ausgeben, sondern welches verdienen. Deshalb bauen sie vollständige Wertschöpfungsketten um Zukunftsbranchen auf und knüpfen Beziehungen mit Gleichgesinnten. "Südostasien bildet für mehrere Technologien ein neues geopolitisches Cluster", sagt Maria Pastukhova von der Denkfabrik E3G. Die Leiterin des Forschungsprogramms "Globale Energiewende" legt Europa nahe, sich zu sputen, wenn es nicht abgehängt werden möchte: "Die Weltwirtschaft wartet nicht auf Länder, die zögern." Die entscheidende Frage ist: Wie gelingt die Energiewende, ohne erneut abhängig zu werden? "Europa hat drei nicht so gute Optionen", sagt Pastukhova. Ihre Empfehlung: kontrollierte Offenheit. Außerdem Thema im Podcast: +++ Der Aufstieg der Region ist China-getrieben: Machen sich die südostasiatischen Staaten abhängig? +++ Warum ist der Zugriff auf Verarbeitungskapazitäten wichtiger als auf seltene Erden selbst? +++ Warum fällt Europa auch bei den Emissionen hinter den Entwicklungsländern zurück? Gast: Maria Pastukhova, Leiterin des Forschungsprogramms "Globale Energiewende" der Denkfabrik E3G. Sie beschäftigt sich mit Fragen zu Energiediplomatie, Energiesicherheit und Geopolitik der Energiewende. Moderation: Clara Pfeffer und Christian Herrmann Wir freuen uns über Feedback und Zuschriften: klimalabor@ntv.de Ihr möchtet uns unterstützen? Dann bewertet das "Klima-Labor" bei Apple Podcasts oder Spotify Das Interview als Text? Einfach hier klicken. Dieser Podcast wird vermarktet von Julep Media: sales@julep.de Wir verarbeiten im Zusammenhang mit dem Angebot unserer Podcasts Daten. Wenn Sie der automatischen Übermittlung der Daten widersprechen wollen, melden Sie sich hier: datenschutz@julep.de

Carnage -/- Cluster presents Hits & Shits Radio EP.93 26-05-29 01. Carnage -/- Cluster - Revenge 02. Carnage & Cluster - Tone Control 03. Carnage -/- Cluster - Manufactured Silence 04. Cement Tea - Time To Eat Cake (Carnage & Cluster's Millenium Industrial Remake) 05. Carnage -/- Cluster - Senseless Self-Destruction 06. Carnage -/- Cluster - Trippin' 07. Carnage -/- Cluster - What's That Noisj 2K25 08. Carnage & Cluster - Squeezing Pigs 09. Carnage -/- Cluster - Charlie Foxtrot 10. Cause Of Death & Carnage -/- Cluster - Wrong Day 11. Carnage -/- Cluster - Satanic Panic 12. Carnage -/- Cluster - The Breaking Point (Ode To Misery) 13. Carnage -/- Cluster - Die Screaming, Motherfucker 14. Carnage -/- Cluster - Divinity 15. Species Kai - Collateral Damage (Carnage & Cluster Never Stop Banging Remix) 16. God Complex vs. Carnage & Cluster - The Creator 17. Carnage -/- Cluster - Zombie Noises 18. Carnage -/- Cluster - Complex God 19. Carnage -/- Cluster - No Competition 20. Carnage -/- Cluster - I Am God 21. Carnage -/- Cluster - Fuck With Us

Criminal Minds is back and still makes us happy! And also your Canadian hosts talk about the CRTC?

Are you winging it when it comes to picking consonant clusters? If you're spending more time hunting for the right targets than actually running therapy, this episode is your reset button. In today's episode, we're diving deep into selecting consonant clusters. We're breaking down how to select targets strategically, sequence them with intention, and finally see the carryover you've been waiting for. Whether you're a seasoned SLP or new to building your clinical confidence, you'll walk away with a clearer framework and a fresh perspective on why some clients plateau and exactly how to get them moving again. In this episode, we cover: 1) Why random target selection is quietly sabotaging your data 2) The developmental and phonological principles that should be driving your cluster choices 3) How to align targets with your client's unique error patterns for faster progress 4) What the research actually says about cluster intervention sequences Ready to stop searching and start treating? Join the SIS Membership and get done-for-you consonant cluster targets you can put to use today. No more building from scratch, no more second-guessing, just clinically sound, ready-to-use materials designed specifically for SLPs and SLPAs. Join now at kellyvess.com/sis Don't delay and have a summer of reorganizing the brain today.

A 15-minute podcast of Bible teaching, Monday - Friday, by the President and Editor of the Sword of the Lord Publishers, Dr. Shelton Smith.

This episode of the Research Like a Pro Genealogy podcast focuses on the latest updates from 23andMe: the new DNA Relatives Clustering feature and the return of the chromosome browser. Nicole introduces the topic by explaining that both features are now available for premium users, stating that this move, while potentially disappointing for some, is necessary to support the profitability of DNA testing companies. Diana discusses the brand new DNA Relatives Clustering feature, clarifying that it organizes DNA matches into groups who share with each other, suggesting they descend from the same common ancestors. Listeners learn that a key benefit of this clustering is being able to hover over an intersecting cell to see the shared centimorgans between two people in the cluster. Nicole adds that users can also download their cluster results to a CSV file, which shows how much individuals share with each other. Diana illustrates the process by giving an example of creating a cluster from a DNA match named Susan, which involves using the "Cluster relatives in common" button. The hosts then shift their focus to the Advanced DNA Comparison Tool, also known as the chromosome browser. Diana clarifies that the tool is still useful for triangulation, allowing users to compare one match to another match. She explains that the main difference is that matches must be a "connection" with the test-taker to be placed in the primary comparison spot. Nicole notes a benefit where users can see if DNA overlaps in the "Relatives in Common" list, and clicking on that overlap takes them directly to the chromosome browser. Listeners gain a detailed understanding of how to use these new tools to advance their genetic genealogy research at 23andMe. This summary was generated by Google Gemini. Links 23andMe New Clustering Feature and Returning Chromosome Browser - https://familylocket.com/23andme-new-clustering-feature-and-returning-chromosome-browser/ 23andMe Customer Care Articles and blog posts: How to Use DNA Relatives Clustering at 23andMe - https://customercare.23andme.com/hc/en-us/articles/38509301730839-How-to-Use-DNA-Relatives-Clustering-at-23andMe How to Start and Stop 23andMe Sharing https://customercare.23andme.com/hc/en-us/articles/212871747-How-to-Start-and-Stop-23andMe-Sharing Decoding Your Connections: Introducing Advanced DNA Comparison - https://blog.23andme.com/articles/reintroducing-advanced-dna-comparison Sponsor – Newspapers.com For listeners of this podcast, Newspapers.com is offering new subscribers 20% off a Publisher Extra subscription so you can start exploring today. Just use the code "FamilyLocket" at checkout.  Research Like a Pro Resources Airtable Universe - Nicole's Airtable Templates - https://www.airtable.com/universe/creator/usrsBSDhwHyLNnP4O/nicole-dyer Airtable Research Logs Quick Reference - by Nicole Dyer - https://familylocket.com/product-tag/airtable/ Research Like a Pro: A Genealogist's Guide book by Diana Elder with Nicole Dyer on Amazon.com - https://amzn.to/2x0ku3d Research Like a Pro with AI Workbook – Second Edition (eBook) - https://familylocket.com/product/research-like-a-pro-with-ai-workbook-second-edition-ebook/ 14-Day Research Like a Pro Challenge Workbook - digital - https://familylocket.com/product/14-day-research-like-a-pro-challenge-workbook-digital-only/ and spiral bound - https://familylocket.com/product/14-day-research-like-a-pro-challenge-workbook-spiral-bound/ Research Like a Pro Webinar Series - monthly case study webinars including documentary evidence and many with DNA evidence - https://familylocket.com/product-category/webinars/ Research Like a Pro eCourse - independent study course -  https://familylocket.com/product/research-like-a-pro-e-course/ RLP Study Group - upcoming group and email notification list - https://familylocket.com/services/research-like-a-pro-study-group/ Research Like a Pro Institute Courses - https://familylocket.com/product-category/institute-course/ Research Like a Pro with DNA Resources Research Like a Pro with DNA: A Genealogist's Guide to Finding and Confirming Ancestors with DNA Evidence book by Diana Elder, Nicole Dyer, and Robin Wirthlin - https://amzn.to/3gn0hKx Research Like a Pro with DNA eCourse - independent study course -  https://familylocket.com/product/research-like-a-pro-with-dna-ecourse/ RLP with DNA Study Group - upcoming group and email notification list - https://familylocket.com/services/research-like-a-pro-with-dna-study-group/ Thank you Thanks for listening! We hope that you will share your thoughts about our podcast and help us out by doing the following: Write a review on iTunes or Apple Podcasts. If you leave a review, we will read it on the podcast and answer any questions that you bring up in your review. Thank you! Leave a comment in the comment or question in the comment section below. Share the episode on Twitter, Facebook, or Pinterest. Subscribe on iTunes or your favorite podcast app. Sign up for our newsletter to receive notifications of new episodes - https://familylocket.com/sign-up/ Check out this list of genealogy podcasts from Feedspot: Best Genealogy Podcasts - https://blog.feedspot.com/genealogy_podcasts/

A 15-minute podcast of Bible teaching, Monday - Friday, by the President and Editor of the Sword of the Lord Publishers, Dr. Shelton Smith.

What does it really take to deliver lifesaving aid in the middle of war zones, natural disasters, and humanitarian crises? In this powerful episode of Logistics With Purpose®, Enrique Alvarez and Kristi Porter sit down with Noemi Pazienti and Kelly Bradley from the Logistics Cluster, the World Food Programme-led coordination platform supporting humanitarian operations across the globe.From Lebanon and Gaza to Burkina Faso and Ukraine, this conversation takes listeners behind the scenes of humanitarian logistics operations happening in some of the world's most complex and dangerous environments. Learn how the Logistics Cluster coordinates global partnerships, activates emergency supply chain networks, and works with NGOs, governments, and private sector leaders to ensure aid reaches the people who need it most.Noemi and Kelly share firsthand stories from the field, including coordinating humanitarian convoys during active conflict, setting up emergency warehouse capacity in Beirut, navigating collapsed infrastructure in Gaza, and balancing operational efficiency with humanity and compassion.You'll also hear valuable leadership lessons on adaptability, collaboration, communication, resilience, and why details matter in supply chain operations where every decision can impact lives.Whether you work in supply chain, logistics, humanitarian aid, or simply want a deeper understanding of how global relief efforts operate, this episode offers an inspiring and eye-opening look at logistics truly driven by purpose.Additional Links & Resources:Learn more about the Logistics Cluster: https://logcluster.org/enConnect with Kelly: www.linkedin.com/in/kelly-bradley-6646a744Connect with Noemi: https://www.linkedin.com/in/noemi-pazienti/Learn more about Logistics with Purpose®: https://supplychainnow.com/program/logistics-with-purposeLearn more about Vector Global Logistics: https://vectorgl.com/Subscribe to Logistics with Purpose: https://logistics-with-purpose.captivate.fm/listenThis episode was hosted by Enrique Alvarez and Kristi Porter. For additional information, please visit our dedicated episode page: https://supplychainnow.com/itlays-logistics-cluster-delivering-aid-crisis-zones-world-food-programme-lwp156

Star_Cluster_Tersus

Does your baby want to feed all day and all night? Do you feed your little one and put themdown only to look over at your baby with their mouth wide open like you haven't fed them at all, perhaps your little one is Cluster feedings.This week on Parents You've Got This The Expert Guide to Parenthood Podcast we welcome back our Lactation Expert and IBC Rowena Gray to discuss Cluster Feeding, what is, whyyour baby does it and how to get through it.We discuss:- What Cluster Feeding is.- What age babies typically Cluster Feed - How Cluster Feeding affects your milk supply- How you know if your baby is clusterfeeding or if they are comfort sucking- If you are constantly feeding your baby it can be exhausting. Rowena shares her Top Tips to help tired Mama- If Cluster Feeding causes nipple damage or sore breasts and Rowena's tips if this happens- What age babies typically stop Cluster Feeding- If growth spurts coincide with Cluster Feeding?- As a baby gets older the milk supply stabilizes, how long it takes for Cluster Feeding to increase a women's supply- Rowena shares her advice around when a baby stops cluster feeding and reduces their milk intake, how breasts and milk supply responds- Rowena's tips for MastitisNever forget Parents You've Got This Parents You've Got This - The Expert Guide To Parenthood Podcast is proudly supported by Mustela natural origin skincare, by parents' side since 1950.Follow us Social: Instagram: @parentsyouvegotthis_auThreads @parentsyouvegotthis_auTikTok:@partentsyouvegotthis_auFacebook:@parentsyouvegotthis__________________________________Parents You've Got This offers antenatal and postnatal parenting education and Masterclasses from the planning phase to early preschool.Learn more: parentsyouvegotthis.com.auCredits: Producer Dean Thomas, Camera person Tim Hehir, Content and Hosts Parents You've Got ThisThank you Think HQ for the beautiful podcast recording space

Many astronomical discoveries have come in stages – a series of “aha” moments where we learn more about the nature of an object. A good example is Messier 13, the Great Hercules Cluster. Under especially dark skies, it’s just visible to the unaided eye, so people have known about it forever. It looks like a faint, hazy star. But during the 1700s, the cluster was “discovered” several times. The first discovery was made by Edmond Halley. Using a small telescope, he came across it in 1714. He described it as “a little patch.” Charles Messier saw it a half-century later. He described it as “round, beautiful, and brilliant.” But, he wrote, “I am sure it doesn’t contain any star.” He made it the 13th object in his catalog. In 1779, though, William Herschel contradicted Messier. M13 “is a most beautiful cluster of stars,” he wrote. Many other discoveries have followed. They’ve told us that M13 contains hundreds of thousands of stars packed into a tight ball. And the cluster is ancient – 12 billion years old or older. Messier 13 is 25,000 light-years away. In early evening, look in the east-northeast for the Keystone of Hercules – a lopsided “square” of stars. M13 is between the two stars at the top of that pattern, a bit closer to the one on the left – a giant cluster that’s still producing amazing discoveries. Script by Damond Benningfield

Stacks on stacks of Domains of Dread! Homebrew Corner: Van Richten's Dungeons, Issue 2 - Zherisia DnD Lorecast Discord | DnD Lorecast t-shirts, stickers and more! Order Lore TA Shaun's Alien novel, PERFECT ORGANISMS, out now! Order Lore TA Shaun's Solomon Kane novel, SUFFER THE WITCH, out now! Links: Lore TA Shaun's second novel, The Dissonance, is out NOW Pantheon/PRH! Buy it ANYWHERE books are sold! And pick up Shaun's Conan the Barbarian ebook short story, also available now! The 616 Files - Shaun and Sergio's OTHER nerdy podcast! A deep dive into the 616 Marvel Universe, comic by comic, year by year Fandom University - And yet ANOTHER nerdy podcast! Multi-episodes arcs deep-diving into various nerdy topics *SEASON 1 NOW COMPLETE* Check out all the socials at dndlorecast.com And send us a note! Email us at dndlorecast@gmail.com  ROBOTSRADIO.net - Smart Shows for Interesting People. Explore all the awesome shows on the network. Robots Radio Network Discord: discord.gg/JXKfVhM "Crusade - Heavy Industry" Kevin MacLeod (incompetech.com)Licensed under Creative Commons: By Attribution 4.0 Licensehttp://creativecommons.org/licenses/by/4.0/ Learn more about your ad choices. Visit megaphone.fm/adchoices

Stacks on stacks of Domains of Dread! Homebrew Corner: Van Richten's Dungeons, Issue 2 - Zherisia DnD Lorecast Discord | DnD Lorecast t-shirts, stickers and more! Order Lore TA Shaun's Alien novel, PERFECT ORGANISMS, out now! Order Lore TA Shaun's Solomon Kane novel, SUFFER THE WITCH, out now! Links: Lore TA Shaun's second novel, The Dissonance, is out NOW Pantheon/PRH! Buy it ANYWHERE books are sold! And pick up Shaun's Conan the Barbarian ebook short story, also available now! The 616 Files - Shaun and Sergio's OTHER nerdy podcast! A deep dive into the 616 Marvel Universe, comic by comic, year by year Fandom University - And yet ANOTHER nerdy podcast! Multi-episodes arcs deep-diving into various nerdy topics *SEASON 1 NOW COMPLETE* Check out all the socials at dndlorecast.com And send us a note! Email us at dndlorecast@gmail.com  ROBOTSRADIO.net - Smart Shows for Interesting People. Explore all the awesome shows on the network. Robots Radio Network Discord: discord.gg/JXKfVhM "Crusade - Heavy Industry" Kevin MacLeod (incompetech.com)Licensed under Creative Commons: By Attribution 4.0 Licensehttp://creativecommons.org/licenses/by/4.0/ Learn more about your ad choices. Visit megaphone.fm/adchoices

Is this the END?? No...just life in California.

The Ethereum protocol cluster gets new leadership. The SBC releases a new CLARITY Act draft. And Aave amends an Arbitrum AIP following a court order. Read more: https://ethdaily.io/944 ETH Daily sponsorships are now open. Reach over 10,000 Ethereum-native subscribers every weekday. Learn more at ethdaily.io/sponsor Disclaimer: Content is for informational purposes only, not endorsement or investment advice. The accuracy of information is not guaranteed.

The YOSEMITE CLUSTER - Part 2Become a supporter of this podcast: https://www.spreaker.com/podcast/missing-persons-mysteries--5624803/support.

Why is your baby so unsettled at night? If evenings feel harder than the rest of the day, you are far from alone.Many babies become fussier in the late afternoon and evening. They may want to feed constantly, cry more easily, resist being put down, or only settle when held close. It can feel relentless when you are already tired.In this episode, I'm explaining why evening fussiness is so common in the newborn weeks, what may be driving it, and how to respond with more calm and confidence.Inside this episode:• Why babies often struggle more in the evening• Cluster feeding and constant evening feeding• Why milk flow can feel different later in the day• Overtiredness, overstimulation, and nervous system load• Why closeness helps so much• Gentle ways to settle your baby• When to look more closely or ask for supportVery often, evening fussiness is about biology, regulation, tiredness, and a strong need for connection.FREE RESOURCES + SUPPORTWeekly Resourceshttps://askthevirtualmidwife.com/weekly-resourcesPre-order my book: Baby Steps to Six Weeks – A Day-by-Day Guide for New Mothershttps://askthevirtualmidwife.com/baby-steps-preorderIf this episode helped you, please like, subscribe, and share it with someone in the newborn weeks who may need it.00:00 Why Evenings Feel Hard00:31 Overstimulation And Co Regulation01:22 Cluster Feeding Explained02:13 Calming Strategies That Help03:41 Take Breaks And Get Support04:35 Do You Need A Top Up05:19 Reassurance And Next Steps05:51 Resources And Recommendations

For decades, psychedelics like LSD, psilocybin, and MDMA were regarded as dangerous drugs of abuse — but that's started changing as research increasingly reveals their ability to help treat serious mental health issues. On this episode, we listen back to past conversations about the science behind these drugs' therapeutic potential, along with powerful stories of healing. When Marcus Capone retired from the Navy SEALS in 2013 after more than a decade of service, he found himself at loose ends, and battling a deep depression. He cycled through antidepressants and other prescription medications, but nothing worked — until his wife suggested a radical alternative: psychedelic-assisted therapy. Capone describes his experience with ibogaine, how it changed him, and why he thinks it worked when nothing else did. Capone is the co-founder and chairman of VETS: Veterans Exploring Treatment Solutions, and is featured in the documentary “In Waves and War” now on Netflix. Psychiatrist and researcher Rachel Yehuda explains the science behind psychedelic-assisted therapy, and what she's learned about its potential to treat PTSD in veterans. She leads the PTSD clinical research program at the James J. Peters VA Medical Center in New York City. MDMA — otherwise known as ecstasy or molly — is best known as a party drug, but in recent years, scientists have begun investigating it as a treatment for PTSD. We talk with science journalist Rachel Nuwer about the history of MDMA, the science behind its therapeutic potential, and how it helped change one woman's life. Nuwer's book is called “I Feel Love: MDMA and the Quest for Connection in a Fractured World.” Cluster headaches can be debilitating — but a little over a decade ago, a group of sufferers, who call themselves “Clusterbusters,” began investigating the potential of psilocybin, otherwise known as magic mushrooms, to treat their intractable pain. We talk with sociologist Joanna Kempner about her research into the group and their mission, documented in her book “Psychedelic Outlaws: The Movement Revolutionizing Modern Medicine.”

MISSING - The Yosemite ClusterBecome a supporter of this podcast: https://www.spreaker.com/podcast/missing-persons-mysteries--5624803/support.

I recently (and very quietly!) celebrated an important milestone on the Restorative Reading & Writing for Wellness podcast: I reached the 225 episode milestone!It truly seems like yesterday when I nervously hit record and uploaded a very real, raw episode into the world and it's been a wonderful journey of learning ever since. Recently, I've started posting some of these backlist episodes in my current show notes as they relate to the current theme in case you missed it or are new to the podcast and I've loved seeing new life brought to these old episodes. So, I've decided to periodically bring back a backlist episode that relates to my current one-word theme in hopes that it re-energizes your reading and writing life, too. Starting today!Spring is in the air and that means Spring cleaning, organizing and freshening. This kind of work pairs perfectly with my RELEASE theme and might help you let go of the old and make space for the new on your bookshelf….and your life. Today, I am talking about shelf-care or showing love to your bookshelf in mindful and intentional ways to rejuvenate your reading life and how it can lead to self-care in our actual lives, too. Here's a quick overview of the steps I shared in the episode:Know Your WhyFirst, before you even get started, articulate why you are choosing to cull your book collection. Clearly stating your ‘why' behind this work will give you the energy your bookish heart will need to tackle it. Say it out loud. Are you sorting through your books to gain:* a cleaner and refreshed look to your bookshelves?* additional space for new titles and genres?* a chance to sift through your reading life past and plan for the future?Whatever the reason, define your why and hold it close throughout the process.Remove & SortNext, pull all the books off of your shelf so you can literally see and touch each one. This contact is important. Quickly glancing at the titles on your self will not suffice. Pick up each book and sort them into two piles: read and not read yet.Review the Books You've ReadThen, head to the stack of books you've already read. Pick up each book, say the title and author out loud and fan the pages. Saying the title out loud will jog your memory of the book and fanning the pages will highlight any dog-earned passages, bookmarks or sticky notes, all signs you loved the book. If this process does NOT jog your memory of the book, then that's a sure sign you might let it go.Make a decision to keep or donate each book. Is it a book that you read, loved, remembered and want to keep? Yes? Well, why? If you have a compelling reason to keep the book on your shelf waiting patiently for another reader that might never come, then do so. If not, set it aside so you can pay it forward to share with a reader who will love and appreciate it. Continue the process until you have sorted all of the books into KEEP and SHARE piles.But don't put them back on the shelf. Not yet!Review the Books You Haven't Read YetNext, it's time to head to the stack of books you have not read yet. Just as with the books you've already read, pick up each book and say the title and author aloud. How do you feel? Does the book register in your memory? Does it tug at your reading heart? Or do you feel nothing at all? Use that gut feeling to decide whether to keep the book on your shelves or donate to others. These questions might help you decide:* Do you remember when and why you purchased the book?* Are those reasons still relevant in your life today?* Do you remember who recommended it to you and why they thought you might enjoy it?If you can answer these questions and are still interested in the book, keep it. If not and you do not feel any tug at your reading heart, then pay it forward to another reader.Now, there are two steps left: to reorganize your newly culled reading shelves and decide on your donation strategy.Reorganize & ReshelveFirst, let's reorganize. Organization of your bookshelves is a personal process that should be based on your preferences and wishes as a reader AND your desire for organization and accessibility. Here are a few methods you might try:* Shelve books by reading status: read and not yet read* Arrange books alphabetically by author last name* Categorize books by genre and/or format* Sort books by hardcover and paperback* Cluster books by your mood for reading* Visually display books by color, size and/or shape* Celebrate favorite books in a showcaseChoose a method that speaks to your bookish heart and experiment with combinations of strategies, too. You might have a TBR shelf arranged by genre. Or an alphabetically arranged shelf within a certain genre. The choice is yours.Donate Books ForwardLastly, it's time to get your excess books into the hands of its next reader. Here are a few possibilities:* Donate adult books to your local library.* Donate children's literature books to your local school.* Add a few books to a Free Little Library in your neighborhood (or start your own!)* Gift them to family and friends with handwritten recommendations* Declare yourself a book fairy and leave a book in a random place for the next reader to find.Once you see the possibilities for pressing books into the hands of its next reader and making space for the books that need to find you next, it doesn't seem quite so daunting, does it?! Culling your book collections is a necessary stage of the reading life: sharing books that no longer serves you to others and making space for those that need to find you in this season of life:Shelf-Care to Self-Care MagicMoving through this book-culling process and releasing the books that no longer serve you in this particular season of life can feel quite thrilling and leave you with a sense of accomplishment. It also leaves you with new space: space to connect with new books that are just what you need in this moment. So, your last step is to reflect on these three questions, even better if you jot them down in your notebook:* Who do you want to be in this current season?* How do you want to feel?* What do you want to do?Use your unfiltered, gut-reaction responses to connect with new books that can offer you the kind of care you need right now. Here are the books originally mentioned in the backlist episode that I made space for on my newly refreshed bookshelf:ABOVE GROUND by Clint Smith (Amazon / Bookshop)WHEN THE RAIN ENDS by Mary Ellen Taylor (Amazon / Bookshop)ADELAIDE by Genevieve Wheeler (Amazon / Bookshop)And here are the current books I've made space for inspired by the re-airing of this episode:THEO OF GOLDEN by Allen Levi (Amazon / Bookshop)A SPRINKLE OF SWEET SERENDIPITY by Rachel Linden (Amazon / Bookshop)LOVE, FINALLY: UNTANGLING THE KNOT BETWEEN MOTHERS, DAUGHTERS, AND FOOD by Geneen Roth (Amazon / Bookshop)I'd love to hear what you think of this episode! How has culling your book collection helped you move into a new season of your reading life AND your actual one, too? What books are on your newly-curated bookshelf? Share in the comments below!Let's Work Together!I love to connect with others around our shared love of reading and writing.Here are some ways we can work together to create a life you love where restorative reading and writing is at the center of it all:

Carnage -/- Cluster presents Hits & Shits Radio EP.92 26-04-24 01. Relapse & Machinist - Nightmares 02. Embrionyc - Biohazard 03. Nekra Damage - Corridors Of Pain 04. Tymon - Rioted 05. CRPTC - Innercity Resonance 06. Is:End - Anything 07. Frozen & Dr. Macabre - Dimension Of The Doomed 08. Embrionyc & Cubic Nomad - Sensation Of The Mind 09. Slavefriese - One Night Back In Time 10. Convulzion - Kick Some Ass 11. Ferox - 3oh3 12. Carnage & Tymon - Caged Fury (Part 3) 13. Matt Green - Chest Painz (Shallow Breath Mix) 14. Kader vs. Carnage & Cluster - Afraid (Industrial Edit) 15. Carnage & Cluster - Wall Of Sound

Debate TM Tower, el edificio residencial más alto de Europa con el Cluster de la Edificación. Pablo García - Responsable de Desarrollo, TM Grupo Inmobiliario Enrique Gutiérrez - Jefe de Proyectos, FR Ingeniería Fernando Cerveró - Director Lean Construction, Think Productivity

News and Updates: Stanford AI Trust Gap: The 2026 AI Index reveals a widening divide: while 56% of experts feel positive about AI, only 10% of the public agrees. Orbital Compute Launch: Canada's Kepler Communications successfully launched an orbital cluster of 10 satellites using Nvidia processors, proving software can operate effectively in space. Compute Power Shortage: Soaring demand for autonomous "agentic" AI is causing severe compute rationing, forcing companies like OpenAI to scrap products to prioritize enterprise tools. Wisconsin Data Center Referendum: Port Washington voters passed a landmark referendum requiring community approval for large-scale data projects receiving more than $10 million in tax benefits. Texas Tax Break Scrutiny: Texas data center tax breaks are ballooning toward $1.8 billion annually, prompting state lawmakers to consider repeal or stricter oversight for 2027.

Pack Nation, let me tell you somethin' — Jonathan Gannon just rolled into Green Bay with his full Arizona pattern-match press-bail playbook, and the Packers' corner room needs a complete rebuild to match it. In this two-part masterclass, we walk the entire draft board together and break down exactly which college corners have the length, eyes, physicality, and downhill tackling Gannon demands… and which ones are the wrong tool for the job. From the critical pick at 52 all the way down to the final dart throws at 255, this is your complete blueprint for how Green Bay can finally draft corners that actually fit the scheme instead of hoping the wrong bodies magically work. Key Discussion Points Pick 52 Breakdown: Why D'Angelo Ponds might not be the scheme fit despite his twitch and ball skills, the massive intel advantage on Treydan Stukes, and why trading back for Keionte Scott could be the smartest move to add extra picks while landing a perfect length-and-tackle prospect Round 3 Cluster (84): Davison Igbinosun, Malik Muhammad, and Devin Moore — the physical, long-armed options that flash exactly what Gannon wants Value in Round 4 and Beyond: Georgia's Daylen Everette, Texas A&M's Will Lee III, the ice-fishing "keeper" mentality, plus late steals like Ephesians Prysock's insane length and Alabama's Domani Jackson The Big Picture: Why the Packers must come out of this draft with at least two true Gannon-scheme corners to build depth and competition — or risk another mismatched secondary This episode is brought to you by PrizePicks! Use code PACKDADDY and visit https://prizepicks.onelink.me/LME0/PACKDADDY to get started with America's #1 fantasy sports app. If you want the Packers to finally nail the corner room the right way, hit that subscribe button, leave a five-star review on Apple Podcasts, and tell a friend in a Lambeau parka that Packernet is dropping five times a week. Drop your biggest take in the comments — would you trade back at 52 for Keionte Scott, or are you pounding the table for Stukes? I want to hear from you, Pack Nation! To advertise on this podcast please email: ad-sales@libsyn.com Or go to: https://advertising.libsyn.com/packernetpodcast

Pack Nation, let me tell you somethin' — Jonathan Gannon just rolled into Green Bay with his full Arizona pattern-match press-bail playbook, and the Packers' corner room needs a complete rebuild to match it. In this two-part masterclass, we walk the entire draft board together and break down exactly which college corners have the length, eyes, physicality, and downhill tackling Gannon demands… and which ones are the wrong tool for the job. From the critical pick at 52 all the way down to the final dart throws at 255, this is your complete blueprint for how Green Bay can finally draft corners that actually fit the scheme instead of hoping the wrong bodies magically work. Key Discussion Points Pick 52 Breakdown: Why D'Angelo Ponds might not be the scheme fit despite his twitch and ball skills, the massive intel advantage on Treydan Stukes, and why trading back for Keionte Scott could be the smartest move to add extra picks while landing a perfect length-and-tackle prospect Round 3 Cluster (84): Davison Igbinosun, Malik Muhammad, and Devin Moore — the physical, long-armed options that flash exactly what Gannon wants Value in Round 4 and Beyond: Georgia's Daylen Everette, Texas A&M's Will Lee III, the ice-fishing "keeper" mentality, plus late steals like Ephesians Prysock's insane length and Alabama's Domani Jackson The Big Picture: Why the Packers must come out of this draft with at least two true Gannon-scheme corners to build depth and competition — or risk another mismatched secondary This episode is brought to you by PrizePicks! Use code PACKDADDY and visit https://prizepicks.onelink.me/LME0/PACKDADDY to get started with America's #1 fantasy sports app. If you want the Packers to finally nail the corner room the right way, hit that subscribe button, leave a five-star review on Apple Podcasts, and tell a friend in a Lambeau parka that Packernet is dropping five times a week. Drop your biggest take in the comments — would you trade back at 52 for Keionte Scott, or are you pounding the table for Stukes? I want to hear from you, Pack Nation! To advertise on this podcast please email: ad-sales@libsyn.com Or go to: https://advertising.libsyn.com/packernetpodcast

In episode 2043, Jack and guest co-host Sofiya Alexandra are joined by co-host of Brief Recess, Michael Foote, to discuss… The Use of ICE to Suppress the Vote / Disappear People, Ticketmaster And Live Nation Lose Antitrust Case and more! Jury finds Live Nation, Ticketmaster had anti-competitive monopoly over big concert venues Live Nation Lost Its Monopoly Trial. What’s Next — and Could Ticketmaster Really Be Sold? LISTEN: KARMA by SHIMASee omnystudio.com/listener for privacy information.

Titans general manager Mike Borgonzi says there is a cluster of players at the top for the 2026 NFL Draft? Who is in that group and how many? Does this keep the Titans from trading down? Which players are on the second tier and how does that impact trading back? RSVP for the 2026 NFL Draft Party to benefit Our Kids by emailing here: InCrowd@SinkersBeverages.com Thursday Night: $40 all you can eat, all you can drink M.L. Rose in East Nashville with prizes and a first round competition. Saturday Night: $75 all you can eat Shotgun Willie's BBQ, a bourbon tasting, off-the-record Q&A with reporters and special guests, gift bag and more. James Foster and Braden Gall talk Tennessee Titans. Be sure to watch the show at ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠440 Sports YouTube channel.⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ In Nashville? Support great local taprooms and breweries: ⁠⁠⁠⁠⁠⁠⁠Yazoo Brewing Company⁠⁠⁠⁠⁠⁠⁠ on the river in Madison Elite food and beer from ⁠⁠⁠⁠⁠⁠⁠Tennessee Brew Works⁠⁠⁠⁠⁠⁠⁠ downtown ⁠⁠⁠⁠⁠⁠⁠East Nashville Brew Works⁠⁠⁠⁠⁠⁠⁠ in Wilson County and the Eastside

For all those who missed out on London, see you in Miami next week!Notion, the knowledge work decacorn, has been building AI tooling since before ChatGPT, with many hits from Q&A in 2023 and unified AI in 2024 and Meeting Notes in 2025. At the end of their last Make user conference, Ryan Nystrom teased Notion 3.0's Custom Agents - and they are finally embracing the Agent Lab playbook!Sarah Sachs and Simon Last of Notion join us for a deep dive into how Notion built Custom Agents, why it took years and multiple rebuilds to get right, and what it means to turn a productivity tool into an agent-native system of record for enterprise work.We go inside the product, engineering, evals, pricing, and org design decisions behind one of the most ambitious AI product efforts in software today — from early failed tool-calling experiments in 2022 to agent harnesses, progressive tool disclosure, meeting notes as data capture, and the long-term vision for software factories and agentic work.We discuss:* Sarah and Simon's path to launching Notion Custom Agents, and why the feature was rebuilt four or five times before it was ready for production* Why early agent attempts failed: no tool-calling standard, short context windows, unreliable models, and too much complexity exposed to the model* The “Agent Lab” thesis: not just wrapping a model, but understanding how people collaborate and building the right product system around frontier capabilities* How Notion thinks about roadmap timing: not swimming upstream against model limitations, but also building early enough that the product is ready when the models are* Why coding agents feel like the kernel of AGI, and how Notion is thinking about “software factories” made up of agents that spec, code, test, debug, review, and maintain codebases together* How Sarah runs AI engineering at Notion (“notes from Token Town”): objective-setting over idea ownership, low-ego teams comfortable deleting their own work, and a culture designed to swarm around fast-changing opportunities* The “Simon Vortex,” company hackathons, and why security gets pulled in early rather than late* How Notion organizes AI: core AI capabilities and infrastructure, product packaging teams, and a broader company mandate that every product surface must increasingly work for both humans and agents* Why prototypes have become much easier to build internally, and how “demos over memos” changes product development inside a tool the whole company already uses every day* Notion's eval philosophy: regression tests, launch-quality evals, and “frontier/headroom” evals that intentionally only pass ~30% of the time so the company can see where model capabilities are going* What a “Model Behavior Engineer” is, and why Notion treats eval writing, failure analysis, and model understanding as a distinct function rather than just software engineering* The changing role of software engineers in the age of coding agents, and why the new job looks less like typing code and more like supervising a rigorous outer system of agents, PRs, and verification loops* How the “software factory” should work: specs, self-verification, bug flows, subagents, and minimizing human intervention while preserving the invariants that matter* A live walkthrough of a Notion Custom Agent handling coworking space tenant applications by triaging email, enriching applicants with web search, and writing structured data into a Notion database* How agents compose inside Notion: shared databases as primitives, agents invoking other agents, “manager agents” supervising dozens of specialized agents, and memory implemented simply as pages and databases* Notion's take on MCP vs CLI: why Simon is bullish on CLI's self-debugging nature, where MCP still makes sense, and how Sarah thinks about capability, determinism, permissioning, and pricing alignment* The evolution of Notion's internal agent harness: from early JavaScript coding agents, to custom XML, to Markdown and SQL-like abstractions, to tool definitions, progressive disclosure, and a much shorter system prompt* Why Notion cares about teaching “the top of the class,” building for sophisticated operators rather than abstracting away too much capability for everyone* How agent setup works today: agents that can configure themselves, inspect their own failures, and edit their own instructions — with guardrails around permissions* How Notion prices Custom Agents: credits as an abstraction over tokens, model type, serving tier, web search, and future sandbox costs; why usage-based pricing was necessary; and how “auto” tries to match the right model to the right task* Why Notion is not eager to train a foundation model, where they do fine-tune and optimize today, and why retrieval/ranking is one of the most important investment areas as more searches come from agents rather than humans* Why Meeting Notes became one of Notion's strongest growth loops: not just as transcription, but as high-signal data capture that powers search, custom agents, follow-up workflows, and the broader system of record for company collaboration* Why Notion is more interested in being the place where collaboration data lives than in building hardware themselves — and how wearables or other capture devices may eventually feed into that systemSarah SachsLinkedIn: https://www.linkedin.com/in/sarahmsachsX: https://x.com/sarahmsachsSimon LastLinkedIn: https://www.linkedin.com/in/simon-last-41404140X: https://x.com/simonlastFull Video EpisodeTimestamps* 00:00:00 Introduction and launching Notion Custom Agents* 00:01:17 Why Notion rebuilt agents four or five times* 00:03:35 Building for where models are going, not just where they are* 00:05:32 The Agent Lab thesis, wrappers, and product intuition* 00:08:07 User journeys, leadership, and low-ego AI teams* 00:13:16 The Simon Vortex, hackathons, and bringing security in early* 00:16:39 Team structure, demos over memos, and building for agents* 00:20:25 Evals, Notion's Last Exam, and the Model Behavior Engineer role* 00:27:37 Evals as an agent harness and the changing role of software engineers* 00:30:42 The software factory: specs, verification, and agent workflows* 00:32:18 Live demo: a custom agent for coworking space applications* 00:35:08 Composing agents, manager agents, and memory as pages* 00:38:15 Notion Mail, Gmail, native integrations, and tools* 00:39:43 MCP vs CLI and the cost of capability* 00:44:13 When Notion uses MCP vs building its own integrations* 00:47:43 The history of Notion's agent harness rebuilds* 00:55:35 Power users, public tools, and the setup agent* 00:58:01 Self-fixing agents, permissions, and “flippy”* 01:01:13 Pricing, credits, and choosing the right model automatically* 01:09:01 Why Notion isn't training its own frontier model* 01:14:07 Retrieval, ranking, and search built for agents* 01:17:27 Meeting Notes as data capture and workflow automation* 01:21:18 Wearables, hardware, and Notion as the system of record* 01:23:45 OutroTranscript[00:00:00] Alessio: Hey everyone. Welcome to the Latent Space podcast. This is Alessio founder of Kernel Labs and I'm joined by swyx, editor of the Latent Space.[00:00:11] swyx: Hello. Hello. We're back in the beautiful studio that, uh, Alessio has set up for us with Simon and Sarah from Notion. Welcome.[00:00:18] Sarah Sachs: Thanks for having us.[00:00:19] Alessio: Thanks for having us. Yeah.[00:00:20] swyx: Congrats on the launch recently the custom agents, finally it's here. How's it feel?[00:00:26] Sarah Sachs: We ship things slowly. So it had been in Alpha for a little bit and at the point at which is it's an alpha, um, there's a group of people that are making sure it's ready for prod, and then there's a group of people working on the next thing.So sometimes some of these launches are a bit delayed satisfaction, so it's quite nice to remind yourself all the work you did because we do have a habit of like. Being two or three milestones ahead. Uh, just ‘cause you have to be, you know, you can't get complacent. Um, but it's been great that people understood how this is helpful.And I think that's just easier in general building AI tools today than it was two, three years ago. People kind of get it and so that user education, um, there's just, it was our most successful launch in terms of free trials and converting people and things like that. It was really successful, so yeah.But there's a lot to build.[00:01:12] swyx: Making it free for three months helps.[00:01:16] Sarah Sachs: Yep.[00:01:17] Simon Last: It was definitely super exciting for me because it's probably the fourth or fifth time that we rebuilt that.[00:01:22] swyx: Yes.[00:01:23] Simon Last: And I mean,[00:01:24] swyx: you've been building this since like 20, 22.[00:01:26] Simon Last: Yeah, I mean, like, it was even right when we got access to like GPT four in late 20 22, 1 of the first ideas we had is like, oh, okay, let's make an agent that I, we used the word assistant at the time, there wasn't really the word, the word agent yet, but, oh, we'll give an access to all the tools the notion can do, and then it, we run in the background like, like do work for us.And then we just tried that many times and it just. Was too early. Um,[00:01:48] swyx: I need to force you to like double click on that. What is too early? What didn't work?[00:01:52] Sarah Sachs: We were fine to, like, before function calling came out. We were trying to fine tune with the Frontier Labs and with fireworks, like a function calling model on notion functions.This is right when I joined. I joined because, um, we needed a manager as Simon was needed to be able to go on vacation. So, uh, that's, that's around when I joined, so you can speak much more to it.[00:02:11] Simon Last: Yeah, we did partnerships with both philanthropic and open AI at different times, uh, to try to, at the time the, I mean, when we first tried, there wasn't even a constant of like tools yet.We, we sort of designed our own like, like tool calling framework and then we tried to fine tune the models to, uh, to use it over multiple turns. Um, and because it, it didn't work well out the box, I think. Yeah. The models are just too dumb and the context thing was also way too short.[00:02:37] Alsesio: Yeah.[00:02:37] Simon Last: Um, and yeah, we just kind of banged our head against it for a long time.Uh, unfortunately it was always like, there was always like sort of. Glimmers that it was working, but um, it never felt quite robust enough to be like a useful, delightful thing. Um, until I would say, uh, the big unlock was probably like Sonic 3.6 or seven, uh, early last year. And that's when we started working on our agent, which we shipped last year.Um, and then, and then uh, uh, custom agents, kinda a similar capability and that, that one just took longer because we, we just wanted to get the reliability up a lot higher. ‘cause it's actually running in the background.[00:03:14] Sarah Sachs: And the product interface of like permissions and understanding, you know, this custom agent is shared in a Slack channel with X group of people and has access to documents that are surfaced to Y group of people.And the intersect experts, Y might not be whole. And so how do you build the product around making sure administrators understand that permissioning took multiple swings.[00:03:35] Alsesio: Everything is hard back at the end of the day. Yeah. I'm curious, like when the models are not working, how do you inform the product roadmap of like, okay, we should probably build, expecting the models to be better at some reasonable pace, but at the same time we need to, you know, you had a lot of customers in 2022.It's not like you were a new company or like no user base.[00:03:54] Simon Last: Yeah, I mean I think there's always the balance of, you know, like you want to be a GI pilled and thinking ahead and building for where things are going. Uh, but also you wanna be like shipping useful things. And so we always try to like, like keep a balance there.You know, we. We try to take clear, like a portfolio approach. You know, we're always working on multiple projects and, and we're always trying to work on, you know, maintaining things where that have already shipped, like, like shipping new things that are like eminently working well and make them really good.And, and then we wanna always have a few projects that are a little bit crazy. Um,[00:04:23] Alsesio: and what are the a GI peel projects that you have today? I'm curious about, uh, you don't have to share exactly what you're working on, but I'm curious what are things today that maybe in 18 months people will be like, oh, obviously this was gonna work[00:04:35] Sarah Sachs: 18 months.[00:04:37] Alsesio: Yeah, 18 months is, you know,[00:04:37] Sarah Sachs: it's a long time and Yeah. Yeah.[00:04:39] Simon Last: I mean, there's a number of things happening. I think one thing that's becoming more clear is I think like, like, uh, coding agents are the kernel of EGI, sort of, everything is a coding agent. Mm-hmm. I think that's, that's sort of one, one direction.Um, and then, yeah, the exciting thing about that is sort of your agent can sort of bootstrap its own software and capabilities and actually debug and maintain them. And so yeah, we're, we're, we're thinking a lot about that. And then, yeah, like, like another category of things that I'm, I'm really excited about is like, uh, we call the software factory also.People are using this, uh, this, this sort of word. Um, basically it just means can you create sort of like a, as automated as possible, a workflow for developing debugging. Mm-hmm. Merging, reviewing, and maintaining a code base and a service where there's a bunch of agents working together inside, and like, like how does that work?[00:05:28] Sarah Sachs: If you think back to your initial question, like, why did this take so long? I think something,[00:05:32] swyx: I didn't say that, but Yes. Okay. Go ahead.[00:05:34] Sarah Sachs: Why, what, what changed over the three and half years of trying[00:05:37] swyx: it? Exactly. Right. Because most people always say like, it didn't work yet. Then reasoning models came, then it worked.I was like, okay, let's go a little[00:05:43] Sarah Sachs: bit. That's, I mean, that's part of it, but I think the other part of it that I actually think is really what will set notion apart for every new capability is we have like. Two skills that are crucial when it comes to frontier capabilities. One is not letting yourself swim upstream.So like quickly realizing if you're just pressing against model capabilities versus not exposing the model to the right information, not having the right infrastructure set up. That and of itself is the skill of intuition. And the second is to see, okay, you're not swimming upstream. Which direction is the river flowing and what is like, how do we think ahead about the product and start building it even if it's not great yet, so that when it is there, we're ready for it.Right? And like those can sometimes feel like counterintuitive things. Like we can be trying to fine tune a tool calling model when they don't exist yet. And that the trick is to not do that for too long, but realize that there was something there. And we've had a lot of things which like, um, we're just like not swimming in the right direction with the streams.I think we had multiple versions of transcription before we got meeting notes, right? Oh, I gotta talk[00:06:39] swyx: about that. Yeah.[00:06:40] Sarah Sachs: Yeah. Um, and so. I, I, I think that like we, we really closely partner with the Frontier Labs on capabilities and we also have to have strong conviction on, as those capabilities move.Notion is about being the best place for you to collaborate and do your work. And how does that narrative change if the way that we work changes?Yeah.[00:06:58] swyx: Yeah. You told me you were a fan of the Agent Lab thesis, and this is, this is kind of it, right?[00:07:02] Sarah Sachs: Right. I show that thesis to so many candidates. Like I have it as like micro chrome autofill.Um, at this point, like it's one of my most visitations[00:07:10] swyx: because like, is this the, here's why you should work in notion and not open, open eye. I, it's like,[00:07:14] Sarah Sachs: here's, here's what's different about it.[00:07:16] swyx: Yeah.[00:07:16] Sarah Sachs: And here's why. It's not just a rapper. I actually think more and more people understand it's not just a wrapper.[00:07:21] swyx: Yeah.[00:07:22] Sarah Sachs: Um, and by the way, like in the beginning, parts of what we build are wrappers on functionality. That works well, of course, but that's not really the most, um. I would say that's not the product that, that drives revenue. And that's not necessarily always what users need.[00:07:35] swyx: I mean, you know, notion is the AWS wrapper, but like the, the wrapper is very beautiful and like very, very well polished.So[00:07:40] Sarah Sachs: like the analogy,[00:07:41] swyx: like[00:07:42] Sarah Sachs: the analogy that I've been coming back to his Datadog in AWS[00:07:45] swyx: Yeah.[00:07:46] Sarah Sachs: So, uh, Datadog could not exist with, without cloud storage. Right. That it's kind of fundamental that that works. Um, and AWS has like a CloudWatch product, but Datadog is an expert on understanding how people want observability on the products they launch.And we're experts in understanding how people wanna collaborate, and that's really where our expertise lies.[00:08:04] swyx: Totally.[00:08:04] Sarah Sachs: Um, regardless of the tools that we use,[00:08:07] Alsesio: I'm kind of curious how you think about implicit versus explicit expertise. I feel like Datadog is half and half implicit and explicit. It's like they understand across markets and industries what engineering teams usually look for.With notion, it's almost like more of the expertise is at the edge because you as a platform, you're like so horizontal that the end user is not really the same. Mm-hmm. Like with Datadog, the end user is always like, yeah, an engineering lead, a kinda like SRE related person with notion. It can be anything.So I'm curious how you put that expertise into a product versus, you know, obviously it, WS cannot build notion. It's, that doesn't quite work in this case, but[00:08:44] Simon Last: it's, it's a little bit differently shaped. I think, you know, a classic vertical SaaS, like the data is kind of like that. They understand their individual customer very deeply.It's kinda a narrow slice, um, notion has always been super horizontal. And our, our task has always been to sort of balance these two somewhat opposing forces of like, we're listening to our customers and what they want us to build. It's a broad slice. And then also we're thinking about like, okay, how do we decompose what they want into, uh, nice primitives that are, that are really nice to use and we'll, we'll get us like as much bang for the buck as possible.And then, you know. Maintain the whole system, make it all like, like super clean and nice to use.[00:09:22] Sarah Sachs: We still have user journeys. I mean, we still focus on like core. I actually think the failure of our team is when we focus too much on what are cools that are, what are tools that are[00:09:31] Simon Last: mm-hmm.[00:09:31] Sarah Sachs: Cool tools. I actually think that's when we make have the least velocity because you still need some sort of focus on a user journey.So like for instance, we'll all sit down every Friday and look at the P 99 of like the most token exhaustive custom agent transcript and just look at why it didn't do well and cut a bunch of tasks. Like we still focus on like, this has, like this should work. Email triaging should work. Mm-hmm. Right. And similarly, like when we're talking about before building, um, chatting, um, before we started filming about, okay, how can I do PDF export?Well that's functionality that then merits. Maybe we should build a tool that has access to a computer sandbox in a file system and the ability to write code. Right? Right. Um, but it's because we're thinking about the fact that our users to do their, to do their daily work, need to export PDFs, not because we're like, Hmm, I think a computer tool could be cool.Like, let's just see what happens. Mm-hmm. Like we, we have to focus on some user journeys, otherwise we just don't have like, enough strategy to, to prioritize.[00:10:29] swyx: I think there's a lot of like really strong opinions that you've had. Do you have like sort of like a towel of Sarah Sachs? Like, you know, like what, how do you run your team?Like I feel like you just have accumulated all these strong opinions. Obviously part, part of this is your, your token town thing.[00:10:43] Sarah Sachs: I think the TAs working with Service X is, um, you'd have to, it depends who you ask. Um, I think it depends if you're on my team or a partner Right. Or a vendor.[00:10:54] swyx: Yeah. There other people want to run their teams the way that you're Yeah.You're like bringing these things. And then also similarly, uh, Simon, when you did the custom agents demo, you had like, well, we've been using custom agents and here's the super long list of everything that we do. No humans ever read it. Right? That's what you said. I was like,[00:11:07] Sarah Sachs: yeah. So I think for, for me, um, something that I learned very quickly and became very comfortable with was that my job was not to be the ideas per person or the technical expert.My job was to make it so that everybody understood the objective, had a resource to help prioritize what they should work on, and had an avenue to prioritize what they thought was important. And I think that's true with all, all leadership, but I think especially on the AI team. Almost all of our best ideas come from prototypes, from people that have a cool idea because they saw a user problem, and it's a huge disservice if all of those ideas have to pass, like the sniff test of what me and a product partner or Simon and Ivan decided were the direction, right?Because a lot of what we're doing is leaning into capabilities, so. I think that's the first thing is like, I don't really view like the role of engineering leadership as like, uh, hierarchical, nor has it ever been, but especially now, like very willing to change direction based on, um, like proof is in the pudding.Yeah. And like, and I think we have rebuilt our harness three or four times. And when you do that, then the second rule of engineering leadership is like you need to build a team that's comfortable deleting their own code and is very low ego and is driven by what's best for the company. And, um, doesn't write design docs because they think it's their promotion packet.Right. And that's a culture that notion had long before I joined, but like our willingness to just swarm on different problems and um, redo things that we've built before because something has changed. Like, there's a lot of friction that can happen at companies when you do that. And it doesn't happen at Notion.And because it doesn't happen when new people join. Like they don't wanna be the ones that are saying, we shouldn't do this. I wrote that code. So then it's, you know, you, you create a culture that everyone thoughts and that culture comes directly, I think from Simon and Ivan though, um, because they're very open-minded.[00:12:50] swyx: Anything that you,[00:12:50] Simon Last: you'd add? I'm not a manager, like, like, like Sarah is. Um, a lot of my role is really to try to think a little bit ahead, make sure that we're, we're building on the right capabilities and then like the prototyping stuff. And yeah, it's really, really critical to always just be starting again.It's like, okay, this is new thing. What does this mean? What if we just rethought everything or wrote everything? And so I, I'm, I'm basically just doing that in a loop every six months.[00:13:16] swyx: Yeah. Do you believe in internal hackathons for this stuff?[00:13:19] Sarah Sachs: I think there's like two different versions. So one is like, we just have a, a, a solid bench of senior engineers that come and go on what we call the Simon Vortex and Productionizing what we built, right?Because when you're in the Simon Vortex, the velocity is super high. The direction changes daily, and it's meant to be like the equivalent of a SC Works lab. We don't need to do hackathons for that. We need to have senior engineers that we trust to come in and out of those projects. For instance, like management boundaries are really loose.Like you report to him, but you work for her right now. Yeah. That's something that when we hire managers, it's important they don't care about because we tend to form more structures. Yeah. Don't be too[00:13:54] swyx: territorial.[00:13:55] Sarah Sachs: We form more. It's after we ship things, not not before, just historically. Um, the second thing is we do have companywide hackathons.Actually we just had our demos day for the hackathon we had last week this morning. That's more for people that aren't directly working on the project, feeling like they have the time to pause and learn how to make themselves more productive or how they would use notion custom agents to build something.Or part of the hackathon was actually encouraging everyone across the company to build their own agentic tool loop, calling from scratch. Follow like an every blog post on how to do what I think because we want[00:14:26] swyx: just with the compound engineering one. Yeah.[00:14:28] Sarah Sachs: We want everyone to use cloud code in the company or whatever the coding agent they please and understand that fundamental.So we set aside a day and a half. We're all leadership, encourage everyone on their teams across the company to do it. So we have hackathons like that. I would say like kind of facetiously, like everything we build is a little bit like a hackathon until it graduates and puts on big boy pants and as a product ops rollout leader and has a assigned data scientists and stuff like that,[00:14:54] swyx: security review enterprise stuff,[00:14:56] Sarah Sachs: actually security reviews one of the things that we bring in first because it just slows us down way more and, um, causes a lot of tension and they build better product if they're involved early.So, um, that is probably the first person to get involved in something that's the[00:15:09] swyx: right PR approved answer.[00:15:10] Sarah Sachs: No, but it's not just PR approved. It like, um, um, it's[00:15:13] swyx: actually real. It's actually real. It's like, um, I'm just saying scar[00:15:15] Sarah Sachs: tissue.[00:15:15] swyx: Yeah,[00:15:16] Sarah Sachs: because like, you know, my background's also, I worked at Robinhood for a number of years.Yes. So like, uh, compliance and things like that, um, are a little bit more, you learn the hard way when it doesn't come naturally.[00:15:26] Simon Last: Yeah. I think the. The hackathon is really important for uplifting the general population, but like, if that's the only way you can build new things, you're kind of toast. I mean, it, it has to be like the daily processes, like, you know, building these new things.Um, and it has to be about, I think like, I think in the AI era a lot more leverage accumulates to the most curious and excited people. And so it's like we're all about just like activating that energy. You know, like if someone's protesting something on the weekend that they're excited about and it's important, that should be the main thing that we're doing.Yeah. Um, it's not a hackathon that we schedule once a quarter, it's just like, yeah. Daily process. Part of the culture.[00:16:02] Sarah Sachs: I mean, that's how we shift image generation and notion now. It was always this thing that would be kind of nice to have, but it wasn't really clear where that was necessarily aligned in product priorities.It'd be a lot of work. And we had someone on the database collections team, Jimmy, who was like. I really wanna do image generation for cover photos and inside notion. And we're like, if you wanna build it, like it's, do it please. Like we encourage you. We gave ‘em all the resources of working directly with Gemini and being able to like track the token usage and it working through endpoints.We gave them eval, support, everything, and then became a, a full project.[00:16:34] Alsesio: Yeah.[00:16:35] Sarah Sachs: That's why you can't have like ego as a, a leader. Like that's, that's how we work.[00:16:39] Alsesio: What's the size of the team today, both engineering and overall?[00:16:43] Sarah Sachs: I manage, uh, the team. That's what we'll call it. Core AI capabilities and infrastructure.That's about 50 people. But then we have per i partner teams that do packaging. So how it shows up in the corner chat versus custom agents versus meeting notes, that's another 30, 40 people. And, and then every team that has a product service at Notion that a user can interface with owns the tool that the agent interfaces with the editor team.The team that did CRDT for offline mode is the same team that handles how two agents, um, edit competing blocks. Mm-hmm. Right? It's the same problem. The team that built the underlying SQL engine is the same team that owns how the agent asks it to run a SQL query, and it does it performantly. And so from that regard, anyone working on product engineering is tasked with making them work for customers that are humans and agents because over time the majority of our traffic will be coming from agencies using in our interface, not humans.And so. Our objective is to make it so that the whole product org is building for agents.[00:17:40] Alsesio: Yeah. How has it changed internally? The activation bar is kind of lowered a lot. Like anybody can kind of create a prototype very, somewhat easily, especially if you're like an existing code base. Have you raised the bar on like what type of prototype people need to bring forward to gonna be taken?Not like seriously, but like, you know what I[00:17:58] Simon Last: mean? Yeah. I think the bar is lowered in many ways. Be like, one thing our, uh, our team built that is really cool is our, uh, our, our design team made a whole separate GitHub repo, uh, called the, the design Playground. And it's basically just to create a bunch of like, like helper components and you, uh, for, for quickly a throwing together UIs.And it's become like actually quite sophisticated. Like it has like an agent in there and like, uh, that's pretty fun. So like, we pretty much, like, they don't do mocks, they just make like, like full, full prototypes.[00:18:27] swyx: Here it is. It works.[00:18:28] Simon Last: They give you like a u rl. They're like, okay, all right. So we have to make the, like the real production version of that.Um, and then for engineers. A prototype looks like just making it a feature flag that actually works. Like that's sort of the bar.[00:18:39] Sarah Sachs: Something to understand that's really unique about notion. One of the reasons I joined we're super lucky is no one uses Notion in their job as much as people that work at Notion.[00:18:46] Simon Last: Of course.[00:18:47] Sarah Sachs: So I think there's very few companies, maybe if you worked on Chrome I guess, but like everything that we ship, we ship internally first and get a lot of really quick feedback. And also sometimes our dev instance is totally borked and you have to change a bunch of flags to get things done. And that's kind of like, but everyone, so people that do it ticketing, people that do supply chain procurement, recruiting, everyone is using the same instance of notion with like a lot of flags on for these prototypes people build.Um, and so we have this, Brian Levin, one of the designers on our team, I think evangelize this concept of demos over memos.[00:19:18] swyx: Ooh, too[00:19:20] Sarah Sachs: good. Um, which has been, uh, very good for building demos, and I think it's put a big pressure point on us to have really strong product conviction, because if anything can be demoed, you really need a strong filter of making sure that if you know, you're doing X amount of work, you're making the, you're, you're focusing on one tower, you're not just building a really flat hill.Right. That's actually where I think there has to be more conviction from our PMs, um, and our designers and, and well, the company really to have conviction of what journey we're going on.[00:19:52] Simon Last: But overall, I feel like it works pretty well. Like people, almost all the engineers have good enough taste to realize that like, this prototype doesn't actually make sense in the product, or, or it does.So it's not that common that I would see a prototype. It's like, oh, this makes no sense. Mm-hmm. It's like, you know, people are doing reasonable things and, and, and then it's just a matter of. Which things we build first and then often just, just figuring out how to turn it on and off. There's our, in the, in our like experimental chat ui, there's this, there's probably like, like a hundred check boxes in there.[00:20:22] Sarah Sachs: Kills me[00:20:23] Simon Last: the things you could turn on and off.[00:20:25] Sarah Sachs: Uh, but I think that, okay, so that is kind of true, Simon, but like being the person that manages the evals team, like there is a level of intensity that it adds to the platform team. So, you know, if we're gonna do image generation and notion, all of a sudden the way that we do attachments and the way that we, um, our LLM completion like cortex talks and expects tokens back and now it's getting images back.Like there's a lot of platform work that we do need to, like solidify a little bit. So sometimes it'll be in dev for a couple weeks before it makes it to prod just because we still have to like, make it robust, make it HIPAA compliant, ZDR compliant, figure out the right contracting with the vendor, whatever it is.And we need to eval it because we want the team. To still maintain what they build. That's the one thing is like if we have a bunch of prototypes, it can't just be like a small group of people that then maintain whatever end prototypes. So we have invested a lot of people in an eval and model behavior understanding teams that, we call it agent dev velocity.So your dev velocity building agents can be faster if we invest in that platform. And so we have a whole org dedicated to Asian, um, platform velocity so that you can build your own eval and then maintain it once you ship it. So if a new model release comes out and we, every[00:21:38] swyx: team maintains their own eval,[00:21:40] Sarah Sachs: we maintain the eval framework.Every team owns their own evals and a lot of them we've integrated to Optin, to ci, or we run them nightly and we have a team, uh, a custom agent that triggers to a team to look at the major failures. That's really critical because if we have like all these different surfaces now, a lot of it's on the same agent harness, so it's easier to maintain.It's just packaging of different agent harnesses, but new functionality of the agent. Let's say that like we wanna update like. Uh, you know, they deprecated, sonnet, um, four or whatever it is and we need to auto update. Are[00:22:11] swyx: they already? That's so, okay. Yeah. Actually wasn't that long ago.[00:22:14] Alsesio: Theywere[00:22:14] Alsesio: just 3.5.[00:22:15] Sarah Sachs: 3.537. Just got deprecated.[00:22:18] swyx: 3 7, 5 0.2 or, yeah. No,[00:22:20] Sarah Sachs: it's not. 5.2 is five point. Five point no. Yeah, five four is 40% more expensive than five two. So if they deprecated five two, you would hear they can, you would hear from me about that one. Um, but, uh, another conversation to have.[00:22:35] swyx: I have a cheeky evals question for you.Have you noticed any secret degradation from any of the major model providers?[00:22:40] Sarah Sachs: Secret degradation,[00:22:42] swyx: like. During the War Bay, when it's high traffic, it suddenly gets dumber.[00:22:47] Sarah Sachs: Yeah. I mean, not just between the, I mean, we definitely notice flakiness, we've definitely noticed, particularly for some providers, that things are slower during working hours and[00:22:57] swyx: there's a latency argument.Yes. Not a quality argument.[00:22:59] Sarah Sachs: No. I think the quality difference that's interesting is, um, even though companies that say they're selling the same, a, it's really into like quanti quantization, but like companies that say they're selling the same model through different vendors, whether it be through first party or Bedrock, Azure, et cetera.We do see different qualities sometimes, and that's not necessarily what's advertised.[00:23:21] swyx: Yeah. Kidney went to the point of like, if we, they shipped like this, like eval across all the providers and it was like very obvious we were secret equalizing and it was very,[00:23:28] Sarah Sachs: yeah. But[00:23:29] swyx: that's very embarrassing.[00:23:30] Sarah Sachs: You know, um, we hire Subprocess to figure that out for us.So we just wanna understand where it's regressing or where it's optimized. And sometimes we're okay with regressions that optimize latency if they're the appropriate regressions. Our job is to make sure we have the evals to understand the changes that are important to us. And even like when we're partnering with labs on pre-releasees of models, they'll send us multiple snapshots.And this is less about quantization, but more just regressions. Like they have shipped models that were not the snapshots that we wanted, and they have changed the snapshots that they shipped based on the feedback that we give. Because our feedback tends to be more enterprise work focused and not coding agent focused.And definitely those can be bummers, like, you know, uh, we know that this wasn't the version you wanted, but we'll help you make it work. I mean, we always make it work, but that definitely happens.[00:24:16] Alsesio: Yeah. Do you have, um, failing evals that you're just hoping, oh, that will have success eventually when a good model comes out?[00:24:23] Sarah Sachs: Uh, I mean, yeah. So I think. I mean, I could talk about this for 60 minutes, so I will limit myself. I think it's a real issue when people say evals and it's just like, that's quality, that's like unit, I mean, it's like saying testing. It's not just unit tests, right? So. We have the equivalent of unit test.Regression test. Those live in ci, those have to pass a certain percent, you know, within some stochastic error rate. Then we have, as you're building a product, evals of these aren't passing right now, and this is launch quality. So we have a report card and we need to, on these categories, you know, be it 80 or 90% of all of these user journeys to launch, and then what we have what we call frontier or headroom evals, where we actively wanna be at 30% pass rate.And that's actually been a effort that we took in partnership with philanthropic and OpenAI in the past maybe two or three months, because we actually hit a point where our evals were saturated and we weren't able to really give insightful feedback other than it wasn't worse. And not only is that not helpful for our partners, it's not helpful for us to understand where the stream is going.You know, going back to that analogy. And so we spent a lot of time thinking about. What notions last exam looks like, right? Mm-hmm. Not just humanities, last exam. Ooh, notions last exam. Mm-hmm. And, um, there's a lot of, you know, dreams about what that would look like. I know we've talked a lot about benchmarking, um, swix, but, uh, yeah.Notions last exam is a big thing inside the company and we have people, full-time staff to it exclusively. Mm. We have a data scientist, a model behavior engineer, and an full-time, um, evals engineer just dedicated to the evals that we pass 30% of the time.[00:25:56] swyx: What you're hiring for[00:25:57] Sarah Sachs: MBEs? I am hiring[00:25:58] swyx: What is an MBEA[00:25:59] Sarah Sachs: model?Behavior Engineer Model. Behavior engineers started with a title data specialist before I joined when they were working with Simon on like, uh, Google Sheets and like Simon just needed someone to look through Google Sheets and say, yes, no, this looks bad. This looks good. Right? And so we hired people with kind of diverse linguistics background.We had like a linguistics PhD dropout. Mm-hmm. And a Stanford ate new grad. And they're amazing. And they formed a new function basically. And over time we've built a whole team, um, with a manager who's now kind of reinventing what that role is with coding agents. So they used to be kind of manually inspecting code.Now they're primarily building agents that can write evals for themselves or LLM judges. There's a really funny day I can send you the picture where Simon, about a year and a half ago, was teaching them how to use GitHub. Um, and they're on the whiteboard and it was like, okay, I think it would be so much faster if our data specialists learned how to use GitHub and like learned how to commit these things in Dakota.And, and that was then and now I think, you know, coding has been a lot more accessible. Um, but moving forward it's this mix of like data scientist PM and prompt engineer because there's craft in understanding like even like what models can and can't do things. How do we define like that headroom? How do we define like what a good journey is?Um, is this model better or not? Why is this failing? There's some qualitative work, but then there's also like a lot of instinct and taste to it, and that's not necessarily software engineering. And so we have like very firm conviction and we have had for a number of years now that that is its own career path and we have always welcomed the misfits, so to speak.So we really firmly believe that you don't need an engineering background to be the best at this job. And that's what's quite unique about this particular role.[00:27:37] Simon Last: Yeah, this is something that I've been pretty excited about recently is we made an effort basically to treat the eval system as like an agent harness.So if you think about it, like, you know, you should be able to have an agent end-to-end, download a dataset, run an eval, iterate on a failure, debug, and, and then implement a fix. And ultimately you should be able to, you know, drive the full time process with a human sort of observing the, you know, the outer uh, system.So yeah, we went, went pretty hard on that. And that's, that's worked extremely well so far. It's like basically just to turn it into a coding agent, uh, uh, problem.[00:28:11] swyx: Your coding agent or just whatever[00:28:13] Simon Last: harness No coding agent. Yeah, code, cloud code. It should be totally general. Yeah. I think if it would be a mistake to like, like fix it on any, any particular coding agent.At the end of the day, it's just like CLI tools.[00:28:21] Sarah Sachs: It's like the same way that you would've a coding agent write the unit test. You should have a coding agent write the eval.[00:28:26] swyx: Yeah.[00:28:26] Sarah Sachs: But there's a lot of supervision in that still. We just don't believe that supervision has to come from software engineers because a lot of it is like, um, kind of you XREE and whatever, and these are the people that also triage failures and tell us where we should be investing next.[00:28:40] swyx: Yeah. I'm gonna go ahead and ask a spicy question. Is there a data, there are no software engineers at Notion.[00:28:46] Simon Last: Um,[00:28:46] Sarah Sachs: what does it mean to be a software engineer?[00:28:47] swyx: Exactly.[00:28:48] Simon Last: I mean, I think the way things are going is like we're on some continuum where. If, if you look back three years ago, humans were typing all the code and then we had auto complete, you're typing list of the code.Then we had sort of like filling agents, filling lines, and now we're getting into like agents doing longer range tasks where you can debug and implement a fix and then verify it works and you know, get your, get your PR even like, like Merion deployed. I think we're sort of just moving up the abstraction ladder and then the human role becomes more about observing and maintaining the outer system.There's a string of agents flowing through, like me prs what's going off the rails. Like what do I need to approve? Is there like a learning or memory mechanism that that works? So it's kind of a hard engineering problem. There's a, you know, there's, there's a lot to do there. I think we're just sort of moving up stack[00:29:34] Sarah Sachs: the same transition machine learning engineers have made, right?Like I haven't looked at a PR curve in a while.[00:29:39] swyx: Yeah. You used to do this stuff and now, um, auto research can do it,[00:29:42] Sarah Sachs: right? Like I think it depends on what you define as a software engineer.[00:29:46] swyx: Yes. It's, that's changing for sure.[00:29:49] Sarah Sachs: I think every software engineer in notion this summer went through like this, um, sheer, um, one of our engineering leads of the company called it, like every software engineer is going through the, the, uh, identity crisis that every manager goes through, where all of a sudden they realize their ability to write code is less important than their ability to delegate in context switch.And I think that is a transition out of being a software engineer. But[00:30:12] Simon Last: yeah. Yeah, there's a critical difference to being a manager, which is that like, it is actually very deeply technical. The problem, you know, humans are very like, like, like fuzzy and you can't like treat a team of humans like a, like a rigorous system where like, you know, prs like, like flow through and can be in like a block status and then what happens when they're blocked, right.With a set of agents, you actually can do that. And, and, and I think it's actually, there's a lot of interesting technical rigor that that goes into that it's like it's a technical design problem. Ultimately.[00:30:42] Alsesio: What is the design of the software factory that you're building?[00:30:46] Simon Last: Yeah, I mean, I think we're. Trying a lot of different things.I mean, ultimately you want to design a system that requires as little human intervention as possible, but like still maintaining the in variance that, that you care about. So yeah, we're exploring a lot different ideas there. I mean, I think I could talk about a few things I think are important there.Like, one thing I think is really important is, um, having some kind of like specification layer you can just commit marked on files. Mm-hmm. That works pretty well, but[00:31:15] swyx: it's nice to be notion man. I'm just saying like the spec, like Yeah. The natural home for specs is notion.[00:31:21] Simon Last: Yeah. Right. It can be a database of pages.Yeah. I mean, it needs to be something that is, you know, human readable and I viewable and I think that's pretty key. Another really key component is like the, the self verification loop. Yes. You need really, really good testing layers, basically. And that's a really deep, uh, uh, problem. But by getting that right, you know, and then, and then it's kinda like the workflow of like.What happens when there's a bug? How does it flow into the system? Like, is it like a subagent working on it? How does it make a PR and how does that get reviewed? And me, and then, you know, so there's like the, the flow or process.[00:31:56] swyx: Yeah. Cool. Uh, you know, one thing we did work out before you guys came in was this demo or this[00:32:01] Simon Last: agents[00:32:02] swyx: agent demo.Uh,[00:32:03] Simon Last: so every,[00:32:04] Alsesio: every time we do an episode, we try the product. Right. I don't think there's ever been an episode that I haven't tried. Yeah. Um,[00:32:11] swyx: and we, we try, try is a, a big word. Like since day one lane space has been on Notion, but this is the, this is the net new thing. Yes.[00:32:18] Alsesio: So this is for Nel Labs, which is the space we're in.So next week we're opening applications for tenants. So there's a web form, let me, we got this form done here. Uh, so, uh, before. Uh, the workflow would be I get an email, then I look at the person. It was like, should I spend time talking to this person? Then I respond, they respond back. So I build this. So the name it came up for on its own.Can you maybe h how do, how does it come up with its own name?[00:32:43] Simon Last: Yeah, that's a pretty app name. It's, it, it is just a random, it's a random, a name generator.[00:32:47] Alsesio: Oh, that's funny. It just came,[00:32:49] Simon Last: the fact that it picked that is, is kind of hilarious. I'm pretty sure it's just determined,[00:32:54] Sarah Sachs: resilient collector. I, I think I've never looked at the code for that.I've never second guessed it. I think it's kind of like a madlib situation.[00:33:00] Simon Last: Yeah, I think you're right. Yeah. It's, it's totally a, a deterministic. Oh, I thought it was great. Yes. Although, although when the, if you use the AI to set itself up, it can update its own name, so. Okay. Um,[00:33:11] Sarah Sachs: how did you create it? It, did you just do[00:33:12] Alsesio: classroom?I,[00:33:13] Sarah Sachs: okay.[00:33:13] Alsesio: I did, yeah. I'll say just check my inbox for applications for a coworking space. Keep a people, so it created the database for me. Which I have here. And I guess database is like an notion table because everything is notion. Um, and then whenever um, an email comes in, like here, it just creates a new role for the person.Mm-hmm. And then it uses web search to enrich the mm-hmm. The profile. So it kind of like searches the web and it's like, this is who this person is, this is when they say they wanna move in and kind of updates everything else. This is, I mean, it's not a GI, but to me, I don't wanna do this work. So it feels like, I mean, it took me maybe like 15 minutes to set up the whole thing.Um, and I really like that most of the information should live here. You know, it is not like some other tool asking me[00:34:01] Sarah Sachs: Yeah.[00:34:01] Alsesio: To like, bring my stuff there. It's like I would've probably already created an ocean thing.[00:34:06] Sarah Sachs: Mm-hmm.[00:34:06] Alsesio: So[00:34:07] Sarah Sachs: most of our biggest use cases and gains are from. That extra layer of human involvement in the process to make it so right.And so like one of our biggest use cases is bug triaging. So if someone posts something in Slack, can you just have a custom agent that lives there that has its own routing constitution of what team this belongs to, creates a task in your task database and then posts in that Slack channel, right? Like that's like one of the first things that we built internally, I think.And it's completely changed the way that notion functions as a company. Nothing falls through, well, most things don't fall through the crack. We don't know what we don't know. But it's not replacing people, it's replacing processes.[00:34:44] Alsesio: Yeah.[00:34:44] Sarah Sachs: Right.[00:34:45] Alsesio: And I'm curious how you think about composability of these things.So the other one I was working on is like a. These filler. So whenever somebody signs up as a tenant, kind of he'll sell the lease for them. There should probably some agent that is like office manager agent mm-hmm. That can handle the request, make the lease, and then, uh, give them a ADA access to the office and all of that.How do you think about that feature?[00:35:08] Simon Last: Yeah, so I mean, there's, there's two ways you can compose. One way is by using like the data primitives. So you can, you know, you, you could give, you have one agent, uh, be writing to the database and there's another agent that's walked in the database. So that's, that's one way that they, they can coordinate that's like a little bit more decoupled and mm-hmm.Works really well. Or you, you can couple them. So I, I think it's actually not released yet. Releasing it like next week is, uh, in the settings for an agent, you can give access to invoke any other agent.[00:35:34] swyx: Hmm.[00:35:34] Simon Last: So you can have them just. Just, uh, uh, talk directly. So[00:35:37] swyx: you, was there a limit on like, number of recursions or just,[00:35:40] Simon Last: um, probably,[00:35:42] swyx: you know what I mean?Like, you can just get an infinite loop that way there's[00:35:45] Simon Last: some kind of Yeah,[00:35:46] Sarah Sachs: I think it's, there is actually a number somewhere.[00:35:49] swyx: I believe I'm just, you know, like, you're, you're, someone's gonna screw up. You[00:35:51] Simon Last: should you try to see[00:35:53] swyx: Yeah. I mean, everything's gonna be paperclips.[00:35:55] Simon Last: Oh, yeah. Yeah. But, uh, but, but that's really useful.Yeah. So we, you know, like I just, I, I helped, uh, someone internally the other day, they had, they had built like over 30 custom agents for, uh, for our go to market team doing all kinds of different things. You know, for example, like researching, you know, like, like filling information about, about a customer or like, like triaging customer feedback or like, uh, something like that.Literally over 30 of them. And, and then he, and then he even made like a database of all the agents and then he is like, okay, and, and now I'm getting 70, over 70 notifications per day with just the agents are blocked on various things. Uh, and then I was like, oh, okay, cool. You know, the obvious thing to do there is to make a manager agent,[00:36:32] Sarah Sachs: right?[00:36:33] Simon Last: That's gonna sort of blocks be another abstraction layer in between your, your, uh, uh, 30 agents. Uh, so yeah, we, we send out with like a manager agent and then has access to invoke all the other agents and it's sort of like, like watching and observing them and then it sort of, it just creates a layer of abstraction.So instead of 70 notifications per day, it's like, like five. And then, and then the manager agent can help like, uh, debug and fix any problems with the,[00:36:54] swyx: does this is a concept of like an inbox or something like piece, you're basically saying that they can message each other?[00:37:00] Simon Last: Yeah.[00:37:01] Sarah Sachs: Well[00:37:01] swyx: they use the system of record, which, which is[00:37:02] Sarah Sachs: notion, so we[00:37:03] Simon Last: actually, yeah, we didn't make any special concepts at all.[00:37:06] swyx: They're interested to the motion notifications that I would've got,[00:37:09] Sarah Sachs: they can just like write a task to a database that the other agent's task to listening to, or they can actually call a web book to the agent, like they can just add the agent. Okay.[00:37:17] Simon Last: Yeah, I mean, this is something that, that we're still working on.I, I think we, you know, like, like generally, generally the way we do these things is, you know, you first make it possible, maybe like a sort of janky way. So I, I, I think the way I set ‘em up is like, you know, we created like a new database that was sort of like issues mm-hmm. That the custom agents were, were experiencing, and then gave them all access to file an issue and then the manager has access to, to read the issues.Um, and that works pretty well, essentially like, like give it its own like internal issue tracker just for the agents. And then, you know, if that becomes a, a concept that seems useful, generally maybe we will think of how to package it in. But I mean, generally we try to just keep it to composing the primitive if we can.You know, another example of this is we have no built-in memory concept. Memory is, is just pages and databases. And so if you wanna give a memory, just give it a page and give it. Edit access to that page and the[00:38:03] swyx: human can edit it. Agent can edit[00:38:04] Simon Last: it. Yeah. And so that works, that pattern works extremely well on it.And you know, depending this case, you can have it be just a page or it could be an entire database with, you know, or, you know, I can have sub pages is is pretty on what you can do with that.[00:38:15] Alsesio: So when I was setting this up, uh, I connected my inbox and it was like, do you wanna use Gmail or Notion Mail? And I'm like, I don't wanna use Eater, I just want you to do it.I'm curious how you think about, you know, notion, mail, notion, calendar, all of these kind of ui ux interfaces, full stack[00:38:29] Simon Last: notion.[00:38:30] Alsesio: Yeah. When like at the same time you have the agents abstracting them away from you in a way, you know, how do you spend like the product calories so to speak?[00:38:37] Simon Last: Yeah, I mean, I think it's pretty important that you don't have to use, not your mail to connect to the mail capability.So we can just connect to Gmail or, or whatever you want, uh, to use. And we're thinking of the mail service as being really great to the extent that it's really agent built, right? So maybe the mail app is just sort of a prepackaged agent that helps you automate your, your inbox.[00:39:00] Alsesio: Yeah, the auto labeling is great.Think[00:39:03] Sarah Sachs: the, when we, um, integrate with Gmail for instance, we have a series of tools available that are available via MCP or API to Gmail. When we integrate with Notion Mail, we have the Notion Mail engineering team to build us the, um, exact right tools that optimize latency, optimize performance and quality.They own that quality. Um, there's product leads there. They're directly thinking about the user problems that happen in mail. So it tends to be when we build integrations and connections, we build natively first. Um, and then think about, um, extending them generally just because it's also easier. Mm-hmm. Um, um, to build natively first.Um, so that tends to be how we phase things out.[00:39:43] swyx: Talking about integrations, you prompted me, so I gotta ask. M-C-P-C-L-I. What's going on? What's the[00:39:48] Simon Last: Yeah. Opinion. I think, I mean, I'm, I'm definitely bullish and excited about cli. I think there's a few really cool things about cli. So one really cool thing is like, um, is that it's in the terminal environment, so it gets a bunch of extra power.So it, you know, for example, it can like, like paginating and cursor through like long outputs. Um, and it has a progressive disclosure inherently. Uh, so, you know, you don't see all the tools at once. It's just, you see the CLI wrapper and you can like use the, the help commands and, and, and read files. And then I think the most important thing that's, that's super cool is that there, it's also inherently a, a bootstrapped.So if there's an issue, uh, the agent can debug and fix itself within the same environment that it uses the tool.[00:40:30] swyx: Mm.[00:40:30] Simon Last: Right. Like, you know, I think I saw a tweet this morning. Someone said, you know, my agent didn't have a browser, so I asked it to make all a browser tool and within a hundred lines of code, it gave itself a little browser, like, like wrapping the, the, the chromium API, um.That's pretty incredible. And then if there was a bug, it would just immediately try to fix it. Mm-hmm. Right. On the other hand, if you use an, you know, if you use like of, of the Chrome dev tools, MCP, I've had this issue where like, like sometimes the transport gets like messed up. If it gets messed up, the agent has no way to fix itself.It, it no longer has a browser, it's, it's not broken. Right. I think that's, that's pretty fundamental, but I would say like a lot of the, the bad things about it can be fixed. Uh, so I think like, as a progressive disclosure, that can be fixed with, with right harness. Like, it, it obviously doesn't make sense to show it all the tools all the time.That's not really inherent to the MCP protocol. It's just like how you wrap it and use it.[00:41:16] swyx: There's many poorly built MCPs because we didn't know.[00:41:19] Simon Last: Yeah, yeah. I mean it was just early, like, like the obvious thing is, uh, you know, to start with is, is to just show it all the tools and it's like, okay, now we have a hundred tools.Yeah. And like the tool calling actually works. So let's of[00:41:28] swyx: your success[00:41:29] Simon Last: give it a way to like, like filter to source the tools. So yeah, I would say like broadly speaking, I'm really bullish on cli. I'm still bullish on CPS and in a certain environment. I think in, in particular, CP is really great for when you want sort of like a narrow, lightweight agent.I think there's, there's definitely a lot of use cases where, where you don't want like a full coding agent with a compute run time. And also you want it to be like more tightly permissioned. MCP inherently has a really strong permission model, like all you can do is call the tools. A CLI is a little bit murkier.It's like, can I access the, if PI token are you, like, properly sort of like re-encrypt the token so it can't like exfiltrate it, it introduce a lot of like, like new issues, which are. Real and hard to solve. And MCP is just like the dumb simple thing that works and it that it's pretty good.[00:42:12] Sarah Sachs: I'll add two more perspectives, not from it working well for Notion, but how notion like commits to both platforms.Notion is dedicated to being the best system of record for where people do their enterprise work. So we will always support our MCP and so far as other people are using cps, right? So regardless of our perspective, we've put a lot of effort into our MCP and we have a fantastic team that we're building, um, to do more there.And the second thing I'll say, I think, um, we all think a lot, but lately I've been thinking a lot about making sure there's a value alignment and pricing, um, with capability.[00:42:43] swyx: Literally our next question[00:42:44] Sarah Sachs: and. Needing language to execute deterministic tasks feels wasteful and requiring on a language model to interface with third party providers seems wasteful for tasks that don't require it.And particularly because our custom agents are using usage-based pricing. We think of pricing as like the barrier of entry for use of our product, and we're quite committed to making sure that it's not wasteful. Um, not just because it's a bad deal for our customers, but it's also bad business. We wanna have as many buyers, like there's a, there's an elasticity of demand and so if we can have our agents properly execute code that calls on CLI deterministically, it's a one-time cost, right?Versus constantly having a language model integrate with an MCP over and over and over and paying those like repeated token fees and it's happening outside the cash window, then you're paying for it over and over and over and it's just kind of unnecessary and less deterministic when it doesn't have to be.[00:43:36] Alessio: Yeah, the open-endedness I think is like, the main thing is like, well, if I go write code to just call an API, I would never use an MCP. But then you need an NCP sometimes when you know what to call, but you don't want it to restart versus like, I think the it built a browser from scratch is like, it's great when you're doing it on your own, but like if your customers were having your AI write a browser from scratch every time and you had to pay the token cost of that, yeah.You'd be like, no, no. The Chrome dev tools CP is actually pretty great. Just use that. I'm curious, how do you make that decision? Like should it be. Just straight API call very narrow. Should it be an MCP? Should it be super open-ended?[00:44:10] Sarah Sachs: Do you mean for when we ship notion capabilities or when we add capabilities to[00:44:13] Alessio: notion[00:44:14] Sarah Sachs: AI or,[00:44:14] Alessio: I mean, you might have a capability that the only way to do is an open-ended agent, like an agent with a coding sandbox.[00:44:21] Sarah Sachs: Yeah. In Notion ai they're not explicit, not We also ship an MCP.[00:44:24] Alsesio: Yeah. Yeah. In B,[00:44:25] Sarah Sachs: yeah.[00:44:26] Alsesio: Internally. Okay. Like is there ever a discussion of like, we're not gonna ship it because we're not able to tie it down? Or are you happy to just like,[00:44:33] Sarah Sachs: um, no. I mean, there are a lot of things where we choose not to use MCP because we wanna add more high touch to quality.I think search an agent to find is like the largest instance of that, where we have. Um, slack and linear and Jira search and notion that is not using necessarily the search MCP functionality that is provided by those companies. And that's because it's quite critical we think, to how our agent trajectories work is for us to have a little bit more control on the functionality of the search journey.And so it usually comes from quality and there's a long tail of things and that's why we built an MCP client or an MCP server, excuse me, so that people can connect whatever they want. There's that long tail, right. But we, for search particularly, I would say that's like the primary entry point, but there are other connections as well that it's a little bit of secret sauce a

Born in 1984, Kai Neville came to surfing at age 11 on the Sunshine Coast, where his dad pushed him into his first waves. He loved it, aspired to be a pro, but soon realized he might be better off behind the camera rather than in front of it. He got a job at McDonald's, saved up for a High-8 Sony Handycam, and started creating short surf films, which led to a job making promo DVDs for Australia's Surfing Life magazine, and then a gig working with renowned filmmaker Taylor Steele. Under Steele, Neville got a crash course in surf filmmaking when he worked on 2008's Stranger Than Fiction, for which he was a videographer and editor.  Neville's first major surf film, 2010's Modern Collective, landed with a major splash. Not only did it announce a group of surfers that would define the decade to come—Jordy Smith, Dane Reynolds, Dion Agius, Yadin Nicol, Mitch Coleborn, Dusty Payne, and Craig Anderson—but it announced Neville's singular vision as the lenspiece of a new generation.  Then came Lost Atlas in 2011, Dear Suburbia in 2012, and Cluster in 2015—all of them oozing with innovative surfing. The Neville thumbprint is distinctive: He has a love of unbridled aerialists. His musical tastes are broad and experimental. His titles are also as eclectic as his eye. For instance, his shorts: "The Quieter You Are, The More You Can Hear." "Welcome Elsewhere." "No One Knows Me Like the Ocean." Along with his surf films, Kai is an accomplished commercial director and photographer, working with brands like Corona, Nike, IWC, Schaffhausen, and Shiseido. He also loves print media, and co-founded What Youth with Travis Ferre. Today, Neville lives with his wife and two boys in the Northern Rivers region of New South Wales, not far from Byron Bay. In this episode of Soundings, Neville talks with Jamie Brisick about chasing creativity, learning his trade under Taylor Steele, the magnetism of misfit surfers, the art of titling and soundtracking, his enduring love for print, and the grind behind some of his most iconic films.  Presented by Rainbow® Sandals. Produced by Jonathan Shifflett. Music by PazKa (Aska Matsumiya & Paz Lenchantin). Become a TSJ member at surfersjournal.com.

Astronomers love star clusters. All the stars in a cluster were born at the same time, from the same cloud of gas and dust. So any differences in the stars are the result of their evolution, which is a result of their mass. That makes it easier to learn what’s going on inside the stars. One problem, though, is identifying which stars belong to a cluster. It takes detailed measurements of motion and brightness to separate members of the cluster from stars that just happen to line up in the same direction. An example is the Coma star cluster, in Coma Berenices. The constellation is in the east at nightfall. Under dark skies, the cluster is a good target for binoculars. The cluster is about 280 light-years away. But it spans dozens of light-years, so its stars are spread out. That makes it harder to pick out its members. And it takes big telescopes to pick out its fainter stars. So despite decades of study, astronomers are still locking down the census of stars in the Coma cluster. A study about a decade ago confirmed eight small, faint members – the first of their kind known to belong to the cluster. And another study found that about a quarter of the stars in the cluster are binary or multi-star systems. These discoveries bring the total number of stars in the Coma cluster to several dozen, with a few dozen more possibilities – members of a wide-spread stellar family. More about Coma Berenices tomorrow. Script by Damond Benningfield

Last time we spoke about the beginning of the first battle of Changsha. From Chongqing, Chiang debated defensive strategies for Hunan, ultimately adopting Plan B after Xue Yue's pleas, focusing on successive resistance north of Changsha to thwart Japanese advances. Japanese forces, under Okamura Yasuji, launched assaults in Jiangxi and Hunan. In Jiangxi, the 106th and 101st Divisions attacked Huibu and Gao'an, where Chinese troops under Luo Zhuoying and Song Kentang fiercely resisted. Gao'an fell briefly but was recaptured by the 32nd Army and the elite 74th Army, with heavy casualties on both sides, as recounted by soldier Liu Qihuai. In Hunan, Japanese units crossed the Xin Qiang River and landed at Yingtian, facing brutal opposition. At Bijia Mountain, Qin Yizhi's 195th Division held for four days; Battalion Commander Shi Enhua's reinforced unit perished entirely, their fragmented remains mourned by locals. Along the Miluo River, Chen Pei's 37th Army fortified positions, repelling waves of Japanese attacks, including suicide squads disguised as civilians. Recruit Yang Peyao's unit endured bombardments, inflicting significant enemy losses before withdrawing at dusk.   #197 The First Battle of Changsha Welcome to the Fall and Rise of China Podcast, I am your dutiful host Craig Watson. But, before we start I want to also remind you this podcast is only made possible through the efforts of Kings and Generals over at Youtube. Perhaps you want to learn more about the history of Asia? Kings and Generals have an assortment of episodes on history of asia and much more  so go give them a look over on Youtube. So please subscribe to Kings and Generals over at Youtube and to continue helping us produce this content please check out www.patreon.com/kingsandgenerals. If you are still hungry for some more history related content, over on my channel, the Pacific War Channel where I cover the history of China and Japan from the 19th century until the end of the Pacific War. Major Luo Wenlang, battalion commander of the 3rd Battalion, 55th Regiment, 19th Division of the 28th Army, harbored a peculiar quirk: he couldn't sleep soundly without unwrapping his leg bindings, a small ritual that anchored him in the chaos of war. Since the war's eruption, such luxuries were rare, and unwrapping his bindings every night became an impossibility, leaving him to endure restless slumbers. Tonight, however, sleep eluded him entirely; he tossed and turned on his makeshift bed, his mind a whirlwind of unrest. Two days after the northern Hunan battle ignited like a powder keg, the 55th Regiment received urgent orders from Division Commander Tang Boyin to race to Wukou in Pingjiang County. Their path wound through Luo Wenlang's hometown of Fulinpu, a twist of fate that stirred conflicting emotions. Entering the village under the cover of night, the entire battalion encamped in the commander's modest family village, with battalion headquarters naturally established in his ancestral home.   Luo yearned to step across that familiar threshold but dreaded it, for his parents remained oblivious to a devastating truth. They slaughtered chickens and prepared meat, hosting the battalion staff with drinks and hospitality, after all, this was their son's unit gracing their home. Luo orchestrated door planks and straw for bedding, posted sentries, and deftly evaded his parents until they retired. Before dawn broke, he mustered the troops, ensured they were fed, and led them onward, slipping away like a shadow. By noon on the 22nd, they reached Wukou, only to receive fresh directives: rush to Yingtian to bolster the 95th Division against the enemy's audacious landings. The 3rd Battalion spearheaded the division's reinforcements, marching relentlessly through day and night, arriving at Dongtang, over 30 kilometers southeast of Yingtian—on the 23rd, hearts sinking upon learning Yingtian had already fallen into enemy clutches.   Luo Wenlang sought out the retreating 95th Division Commander Luo Qi to beg for a mission, his resolve unyielding. Luo Qi, anticipating his arrival, relayed Commander Guan Linzheng's ironclad instructions: The 19th Division's reinforcements would assume Dongtang's defenses. With the main force still en route, Luo Qi tasked Luo's battalion with relieving a segment held by a replacement regiment. He handed over a map, sketching a line with a pencil, a simple stroke that thrust Luo Wenlang and his men onto the front lines of fate. An operations staff was dispatched to guide them to the position and oversee the handover.   As the troops advanced, they encountered scattered soldiers fleeing like startled rabbits; seizing a platoon leader revealed they were indeed from the replacement regiment. Mere minutes from division HQ, the enemy was already closing in, a predator's breath hot on their necks. Luo Wenlang and Deputy Battalion Commander Wu Yacui split the battalion, launching a counterattack on Dongtang from dual routes. Fortune favored them; the Japanese held only an exhausted company, crumbling under a single, ferocious charge. They swiftly deployed two companies to the positions, reserving one as a bulwark. By dusk, the full 55th Regiment arrived, accompanied by the rest of the 19th Division's reinforcements, allowing the battered 95th Division, ravaged at Yingtian, to withdraw for desperate reorganization. The regimental commander positioned Luo's 3rd Battalion on the regiment's vulnerable left wing. In the blink of an eye, it was the 27th, aligning with the 15th of the eighth lunar month. Amid the relentless great battle, few noted the calendar, and the skies hung heavy with clouds. Luo Wenlang twisted on his straw bed, his thoughts a snarled knot of anxiety and memory.   At 11 p.m., gunfire shattered the night; a barrage of machine gun bullets riddled the battalion HQ house, raining thatch and dust upon Luo like fallout from a storm. Catastrophe had struck! Luo surged toward the positions with the bugler—his battalion signal chief—and the reserve force, ascending the hilltop in a frenzy. Halfway up, he spotted 8th Company's Lieutenant Platoon Leader Rong Fayu leading over 20 soldiers in retreat. Bellowing "Why unauthorized retreat?" while brandishing his pistol, he compelled Rong to rally and turn back. The Japanese had launched a nocturnal assault; 8th Company Commander Yi Zuitao lay slain by a fatal shot, over a dozen comrades felled in brutal close combat, the survivors scattered like leaves in the wind; the high ground now belonged to the enemy.   Upon learning of Dongtang's loss, the regimental commander personally led the regimental reserve, his face etched with urgency. Under flickering lantern light, poring over the map with Luo, Division Commander Tang Boyin telephoned, his voice a whipcrack of command: Recapture it before dawn, or both would face the merciless hand of military justice. After seizing the high ground, the enemy hesitated to press further; Luo surmised the darkness concealed paths, and their numbers were not overwhelming. Forgoing the regimental reserve, he led 7th Company's 4 squads and remnants of the routed 8th Company in a stealthy ascent. Near the position, a ravine concealed over 20 8th Company soldiers, rallied by Sergeant Squad Leader Tan Tianrong, who had lurked in wait for reinforcements, dreading exposure at dawn under the enemy's gaze.   Spotting the battalion commander personally spearheading the counterattack, Tan Tianrong's face lit with fierce joy; his men, armed with grenades, surged as the vanguard. Intimate with the terrain even in blindness, they hurled explosives into bunkers, trenches, and works. The commander orchestrated the charge; the Japanese force of 40-50 men crumbled, over half slain or maimed, the remnants fleeing northward to their village stronghold. It was past 4 a.m.; the moon pierced the clouds, bathing the earth in a silvery glow. With positions reclaimed, the night revealed its secret: tonight was Mid-Autumn. Moonlight unraveled the tangled threads of his past; Luo draped his clothes over his shoulders, sat beneath the luminous orb, and wept in solitary anguish.   Before the war, devastating news had arrived: his brother Luo Yinong had been killed in Jiangxi. Luo had three brothers; the eldest shouldered half the family's burdens, their bond unbreakable. The brother had enlisted first in the 50th Army, climbing to battalion commander through sheer valor. He and his younger brother had followed suit, inspired by that call to arms.   Wartime conscription demanded only one per family, but battling the devils was a duty for the nation and its people. His brother had risen to deputy regimental commander before his end. The 50th Army notified him first. Engulfed in battle, there had been no time to console his grieving parents or tend to the funeral; it weighed on his heart like an unyielding stone. His sister-in-law, diligent and unassuming, cared for a young boy and carried another child; the long, arduous days ahead loomed like an endless shadow. The night dew brought a biting chill, the moon an icy sentinel; Luo shivered uncontrollably, his tears mingling with the frost.   The sky hung heavy with overcast gloom, yet the moon lurked beyond the clouds, casting a faint, ethereal light that warded off utter darkness. Along the road, a unit's elongated black shadow snaked southward in hurried silence, a serpent of weary resolve pressing through the night. Qin Yizhi reined in his horse, pausing to gaze back: the queue stretched onward, silent and impeccably orderly, belying the exhaustion of a force scarred by days of ferocious combat, their spirits unbroken amid the shadows. After the Japanese seized the 195th Division's defiant outpost at Bijia Mountain, they surged across the Xin Qiang River in a merciless onslaught. The river, shallow enough to wade knee-deep, offered no true impediment; the real barrier was forged from the defenders' scorching blood, a crimson testament to their unyielding stand. The 195th Division clashed in a maelstrom of cruelty; positions were heaped with corpses time and again, the Xin Qiang's waters churning blood-red in relentless cycles of carnage. From the night of the 23rd to the dawn of the 25th, respite was a forgotten dream; Okamura Yasuji, in a gesture of grim respect, inscribed Qin's name in elegant calligraphy and hung it within his command tent, a haunting trophy of the foe's tenacity.   Following their triumphant landing at Yingtian, the Japanese entangled the Ninth War Zone's left-wing defenders in a protracted snare, their advances grinding slowly like a predator toying with prey, menacing the flanks of the frontal troops with insidious intent. On the evening of the 27th, Xue Yue issued the fateful order for the 15th Army Group to withdraw to the precarious ground between the Miluo River and Shangshan City, ushering this blood-soaked force into an all-night march toward the next defensive crucible. Late into the night, a brief halt was called. Soldiers slumped to the ground, adjusting leg wraps and gear with mechanical precision; logistics teams darted through the ranks, distributing rations like lifelines; cooks, having forged ahead, arrived with steaming pots of rice soup, infusing the air with a rare warmth. Though no clamor broke the hush, a quiet camaraderie enveloped the queue, a fleeting balm against the war's chill.   The division staff claimed a flat expanse beside a farmhouse yard for their respite. Qin settled onto a stone roller used for grinding grain, nibbling at his meager ration and sipping the hot soup that steamed in the cool air. Suddenly, moonlight pierced the clouds, cascading down in silvery streams; the familiar contours of the farmhouse stirred a flood of warmth in his heart, evoking memories of home.   Chongqing, Huangshan Villa. Every window was shrouded in double layers of thick curtains, sealing out any sliver of betraying light, as if the very walls conspired to guard secrets from the encroaching night. Tonight's ethereal protagonist rose languidly from the eastern valley, its orange-red moonlight casting an aura of drowsy reluctance, as though it had not fully shaken off the slumber of the day. The feeble glow dappled the building's roof, balcony, and the surrounding hillsides, intersections, and thickets, where armed shadows lurked, capturing every rustle in the oppressive silence. Only upon close inspection could one discern the faint specks of moonlight glinting off steel helmets. Yet, beyond those fortified walls, another realm pulsed with life, a vibrant contrast to the shadowed vigilance outside. The front hall, living room, and dining room blazed with brilliant light. Vibrant flowers, dominated by chrysanthemums in full, defiant bloom, infused the air with color and fragrance; a phonograph murmured a cheerful Guangdong melody, weaving an atmosphere thick with festive joy, a deliberate illusion amid the storm of war.   Chiang Kai-shek, clad in a flowing black silk gown, strode ahead with poised grace, escorting his guests into the dining room alongside the elegantly attired Soong May-ling, their conversation laced with laughter and warmth. At the table, Soong May-ling's smile was a beacon of diplomacy, as she artfully arranged the seating to suit hierarchies and alliances, while servers in crisp white uniforms moved with nimble precision. This was Chiang Kai-shek's intimate Mid-Autumn family banquet; beyond a handful of pivotal military and political figures, the gathering brimmed with relatives. Guests and kin alike noted Chiang's buoyant spirits tonight; his smiles were wide and genuine, his discourse light and expansive, delving into casual topics with uncharacteristic ease.   In September 1939, China's War of Resistance Against Japan had entered its grueling third year. After the initial cataclysm of turmoil and disarray, the government and military had clawed their way to stability, adapting to this unprecedented historical crucible, with operations finally aligning into a semblance of order. According to figures proclaimed by Minister of Military Affairs He Yingqin to Chinese and foreign reporters on the 13th of this month, Japanese invaders had seized 521 counties across 12 provinces, a vast swath of conquest. Yet, the Japanese imperialists had exacted this toll at a staggering cost. Just prior, on August 30, the Hirannuma Cabinet, installed a mere eight months earlier, had collapsed in mass resignation. Hirannuma Kiichiro's predecessor, Konoe Fumimaro, had similarly bowed out amid governmental failures, chiefly the unmet ambitions in the Sino-Japanese War that he had boldly promised to parliament, exacerbating domestic political and economic woes. Days ago, when Wang Pengsheng briefed Chiang on Japan's turbulent politics, he quipped: "Konoe said three months to destroy China; three months didn't work, nor three years, who knows about 30 or 300. Hirannuma had no solutions, down in eight months. Does Abe have good ideas? How long can he be prime minister?" Indeed, Abe Nobuyuki, Hirannuma's successor, would endure a mere four and a half months before resigning in ignominy. Tonight's feast showcased Chiang's favored cuisines: delicate Jiangsu-Zhejiang dishes mingled with robust Sichuan flavors. Chiang abstained from alcohol, raising his cup in mere symbolic toasts to his guests. During the meal, as if by unspoken accord, no one broached the raging domestic battles or the volatile international landscape; conversations meandered through trivialities, skirting anything heavy or discordant, a fragile bubble of normalcy.   On September 3, Britain and France had declared war on Germany, shattering the global order in a seismic shift. Foreign newspapers already bandied the term "Second World War," a phrase that evoked freshness, exhilaration, and sheer terror in equal measure. China's diplomacy surged with newfound vigor. In April, Ambassador to the US Wang Zhengting had negotiated a $20 million loan with American banks on China's behalf. In May, Stalin responded to Chiang's overtures, agreeing to exchange arms for Chinese tea, wool, raw hides, and more. A month later, the first consignment of light and heavy weapons—including artillery and heavy machine guns—arrived via clandestine routes through Xinjiang and Mongolia, bolstering the central army's frontlines. In August, Hu Shih, Wellington Koo, and Chien Tai represented the Nationalist Government at the 19th League of Nations Assembly, laying bare the Japanese imperialists' atrocities in China before the world and rallying global forces for peace to support China's defiant stand. Soon after, British and American civic groups ignited "China Week" campaigns, pressing their governments to aid the beleaguered nation. Waves of foreign volunteers streamed in from distant shores: doctors, journalists, ordnance engineers, even retired soldiers clamoring to join the fray on the frontlines.   "If we could pull America into this war..." Through Soong May-ling's subtle, persuasive influence, Chiang allowed himself to daydream of that prosperous, dynamic young powerhouse across the vast ocean. Thus, on this Mid-Autumn night, his talk turned to America, to his correspondence with President Roosevelt regarding the "tung oil loan." That saga had unfolded the previous October; T.V. Soong had jetted to America, securing a loan with China's tung oil, a commodity scarce in the US, as collateral. China had boldly requested $400 million; America countered with $25 million, a classic tale of "ask high, settle low." Yet, the funds were secured. One success paved the way for many. Soong May-ling had once confided to Chiang: "In mobilizing US aid for China's resistance, I'll make a difference." When Chiang responded with a smile, "Thank you, Madam," he could scarcely foresee how his beautiful wife's extraordinary prowess in fulfilling this solemn vow would astonish him, etching eternal glory for Chinese women worldwide and elevating Soong May-ling to the zenith of her life's achievements.   The most direct echo of the First Battle of Changsha's thunderous saga resides in the Ninth War Zone's meticulous report on the northern Hunan and southern Hubei operations, submitted to the Chongqing Military Committee and Chiang Kai-shek himself, a faded relic now entombed amid the vast ocean of Nationalist Government military and political archives in Nanjing's Second Historical Archives of China. This document, a painstaking compilation of combat dispatches from divisions, armies, and army groups, stands as a testament to valor and sacrifice. Tragically, time's relentless march and human folly have ravaged this priceless artifact, leaving only shards and whispers to conjure the heart-wrenching inferno of that bloody clash.   "October 24, Year 28. Urgent. To Chongqing. Chairman Chiang. Secret. Submitted by Commander Xue on orders." The rice paper has yellowed to a deep, somber hue, brittle and parched; a careless touch could reduce it to dust. Some pages lie fractured, their remnants affixed to white paper, forever unable to reclaim their original wholeness. Leafing through page by page unleashes a pungent miasma, a scorched, acrid, decayed blend that assaults the senses. Traces of fire and water mar the original rice paper sheets, with countless fragments glued haphazardly to white backings, their sequences lost to eternity.   "...The Xin Qiang River spanning from Lujiao to Leishi Mountain, defending a front of over 110 li..." "Enemy 13th and 33rd Divisions, parts of the Hata Detachment, naval units, and artillery, cavalry, engineers totaling..." "...Began attacking us first with artillery... fortifications completely destroyed, then infantry charged; relying on our officers and men all resolved to coexist with the homeland..." "...And launched balloons to direct artillery... our army braved the cannons... repelled them, corpses filling the river, turning the water red..." "Division casualties also reached over a thousand... failed to inflict greater strikes and annihilate... deep inner guilt, besides vigorously training troops awaiting orders to kill the enemy..." "...Attack casualties heavy, then concentrated large forces... artillery fire so dense like continuous firecrackers for hours... released poison gas, Wang Street garrison all heroically sacrificed, then breached... Zhao Gongwu kowtows, October 15"   Zhao Gongwu commanded the 2nd Division under Zhang Yaoming's 52nd Army. This unit first held the line along the Xin Qiang River, then fell back to northeast of Fengjiang Bridge to staunch the enemy tide once more; after October 6, it hammered southward-marching Japanese from the west in the Yanglin Street and Dajing Street regions. Through these crucibles, the division bled over half its strength. A fragment of an envelope clings to a sheet of white paper, its words faintly visible: "Changsha 126-3 Zhang Yaoming," "Hunan Jinjing Air Mail," "Combat Process by..." and the like. The stamp remains remarkably intact—a philatelic gem now. Measuring 1.5 cm square, it features Sun Yat-sen's portrait at its center, inscribed "Republic of China Post" below, with "5" in the upper right, "fen" to the left, and "5" in each lower corner. I sat at the long table in the spacious, brightly lit reading room, staring vacantly, my thoughts grinding to a halt. These remnants are all that endure for posterity, of that monumental battle, of the scorching blood and vanished lives of countless unnamed Chinese soldiers. With hands that once gripped a rifle, I gently caressed those pages from a bygone era; they were cold, devoid of any lingering breath.   As the full moon of the 15th of the eighth month dissolved into the golden-red blaze of sunrise, Qin Yizhi's 195th Division had already plunged into the rugged mountains and dense forests encircling Fulinpu. Per directives from 15th Army Group Commander Guan Linzheng, the 195th was to forge a new defensive bastion centered on Fulinpu, 40 to 70 kilometers from Changsha. Their mandate: stall the Japanese southward juggernaut, granting precious time for allied forces to muster and fortify around the city. Despite the grueling all-night march, morale soared undimmed. The advance chief of staff doled out positions to each regiment, and the troops dove into fortification labors with fervent zeal. The 195th Division's unyielding stand along the Xin Qiang River had already etched preliminary glory upon this unit in its baptism of fire. "Fame in one battle" echoed as a battle cry throughout the division, where collective honor intertwined with personal valor. Honor and triumph formed the bedrock for soldiers and armies alike. Yet, another fire fueled their resolve.   On September 23, amid the Japanese forcing the Xin Qiang River, Guan Linzheng's voice crackled over the phone to Qin Yizhi: "Facing you is the 6th Division." The 6th Division, a name that ignited fury in Chinese troops and civilians, forever linked to the demonic specter of Tani Hisao. Moments later, the whisper spread like wildfire through every trench: "The Japanese army that perpetrated the Nanjing Massacre is right in front." Agitation rippled through the ranks; some donned fresh uniforms and shoes from their packs, casting aside the worn; others flouted discipline to bid farewells to hometown comrades: "Today we fight to the death here; see you in the next life." "Tell my mother I died fighting the Nanjing Massacre enemies."   Some company commanders commanded their mess sergeants to expend all funds on hearty feasts. All Japanese were foes, but the 6th Division embodied a blood debt, an unforgivable vendetta; the Chinese nation does not lightly forget its tormentors. In the Xin Qiang River maelstrom, the 195th Division battled with heroic ferocity. Some soldiers, in their final breaths, murmured: "Die then; it's worth it." Others lamented slaying too few devils, gritting teeth, eyes refusing to close in eternal regret. Now under Inaba Shiro's command, the 6th Division splintered southward after breaching the Xin Qiang; roughly a thousand hounded the 195th to Fulinpu. On the morning of September 29, the Japanese blundered into the 195th's meticulously laid ambush. Qin Yizhi, pulse racing with excitement and tension, fumbled the binoculars from his guard's hand. His command sliced the air: "Begin." War history chronicles: "The 6th Division advanced south from the Miluo River along the Xinshi-Liqiao road and Xinshi-Fulinpu routes. The over a thousand reaching Fulinpu were ambushed by the Nationalist 195th Division, suffering heavy losses." As Japanese artillery and aircraft unleashed hell upon the 195th's positions, Qin orchestrated a swift southward withdrawal to the environs of Shangshan City. Again, without pause, they erected fortifications and set deadly traps.   On the morning of September 30, the pursuers from Fulinpu closed in on Shangshan, their numbers swollen to over 1,500. Qin Yizhi clenched his jaw, his demeanor icy calm, allowing the Japanese to creep into the kill zone before barking: "Hit them hard!" Combat raged from dawn to dusk, obliterating over 700 foes. Qin ascended a hill, surveying through binoculars, then erupted: "Bad! The enemy is retreating." Upon receiving Qin's telegram, Guan Linzheng scrutinized the map, momentarily stunned, then replied: "Enemy shows no retreat signs yet; proceed per original plan. Your unit to block at Shangshan City line until October 2." Xianning, Okamura Yasuji's 11th Army HQ.   Combat maps bristled with markings, staff officers darting amid ringing phones and clattering telegrams. The colossal red arrow in northern Hunan had fractured into tributaries, surging over 100 km southward from the outset; one tendril pierced to Yong'an City, a mere 30 km from Changsha. Vast swaths of northern Hunan lay conquered, yet Okamura sensed the tide turning, it was time to retreat. The Chinese employed their time-honored gradual resistance, battling while retreating with cunning grace. Some units fell back directly, others amassed on flanks—what portent did that hold? In Okamura's shrewd mind loomed an equally shrewd Xue Yue; he envisioned his adversary methodically weaving a snare.   Post-Yingtian landing, the 15th Army Group's timely evasion had unraveled his "Xiang-Gan Operation Plan" like fragile thread. If encircling and annihilating the Chinese main force proved unattainable, what purpose in pressing onward? Telegrams from 3rd Division's Fujita Susumu, 6th's Inaba Shiro, and 13th's Tanaka Seiichi piled on his desk, pleading to assault Changsha—for headlines and Imperial accolades, perhaps, but blind to their exposed supply lines vulnerable to enemy thrusts? Ground logistics teetered on collapse; the air force resorted to airdrops for isolated regiments. Venturing further south would stretch lines to breaking; a severed artery spelled doom for the vanguard. When would these commanders mature into true stewards of the Imperial Army? Okamura fretted and pitied them in equal measure.   At 4 p.m. on September 30, Okamura decreed a halt to advances at Shangshan and Yong'an. He commenced orchestrating the retreat. Changsha, Yuelu Mountain, Ninth War Zone Command Forward HQ. October 1. Xue Yue stood before the map, Guan's latest telegram clutched in hand. Qin's second missive insisted on Japanese withdrawal, corroborated by 15th Army Group scouts from Yingtian: This morning (October 1), Japanese transports unloaded artillery stowed the previous night, hauling it back to Yueyang; intercepted wires revealed a regiment aborting its southward push, standing idle. Guan assessed the mosaic and commanded counteroffensives: intercept if feasible, pursue relentlessly, deny the Japanese escape; he relayed retreat indicators to Xue. Xue paced the chamber, head bowed in contemplation. Chief of Staff Wu Yizhi, Staff Director Zhao Zili, and their cadre tracked his every step with expectant eyes, awaiting the verdict. Xue's thoughts whirled through military stratagems and beyond.   Pre-war, Xue had segmented the war zone's forces into tripartite blocs: Northern Hunan under Guan Linzheng's 15th, Yang Sen's 27th, and Shang Zhen's 20th Army Groups as "A Cluster"; Northern Jiangxi Nanchang with Yunnan Army Lu Han's 1st Army Group and the 74th Army as "B Cluster"; the Wuning, Xiushui, Hunan-Hubei-Jiangxi border guarded by Sichuan Army Wang Lingji's 30th Army Corps, Fan Songpu's Border Advance Army, and 8th Army; augmented by 3 armies' 7 divisions in general reserve. Before the storm broke, Xue pored over maps, tracing every mountain, river, road, and bridge, envisioning burial grounds for the invaders.   Now, beneath Changsha, 200,000 troops formed a tightening net. The "decisive battle in Changsha suburbs" blueprint had been wired to Chongqing. Chiang and the nation yearned for a resounding triumph as the resistance pivoted into a new epoch?! A masterful drama, honed over half a month's toil, neared its crescendo; yet that cunning fox appeared to sniff the trap's metallic tang, freezing in place. "Commander, phone from Minister Chen." "Brother Boling, good news." Chen Cheng's voice brimmed with levity, "Your formal appointment published. What? Ninth War Zone Commander! First to congratulate; document tomorrow." Shedding the "acting" prefix was inevitable; Chiang had intimated as much long ago. But for a man and general, true worth lay not in titles, but in forging indelible feats. Splendor was judged not by underlings, colleagues, or superiors, but by peers in the craft of war.   Unmoved by the promotion, Xue exhaled a profound sigh. Though the 15th's intelligence couldn't confirm a wholesale retreat, preparations for dual contingencies were imperative. Victories came hard; a splendid battle, harder still. He summoned Wu Yizhi and Zhao Zili to devise countermeasures for the enemy's potential flight. October 2, Sichuan Army Yang Sen's 27th Army Group, Yang Gancai's 134th Division special service company, under Company Commander Wan Mingyu, slogged through the profound mountains and forests on the northern Mufu Mountains' flanks. The 134th's covert mandate: infiltrate enemy rear via treacherous terrain, sabotage supply arteries in the Chongyang-Xianning sector, and deliver a dagger to the Japanese spine when opportunity struck, bolstering frontal defenses.   Past 3 p.m., a crystalline mountain stream materialized. Wan decreed a respite. Over 100 soldiers, drained from a half-day's ascent, collapsed like puppets with severed strings. Most propped their torsos with rifles in one hand, fanning hats to ward off the relentless forest mosquitoes with the other. Regaining breath, they devoured rations washed down with stream water. Some unfurled towels and ventured downstream, letting the cool flow rinse away layers of sweat. Then, a muted engine drone encroached from the heavens. Wan peered through the foliage: a low-flying plane vectored southward, its wings emblazoned with the Rising Sun.   A transport; Wan recognized the temporary Japanese airfield near Xianning. With lines overextended, airdrops sustained isolated units. Wan was prying open a can with his bayonet, the tip etching a cross on the lid before levering along the edge; paired with a rice ball, it promised a savory repast. His orderly proffered a cup of fresh stream water; 2nd Platoon Leader Hu Yaozong perched nearby on a rock, smirking, poised to pilfer from the opened tin. Wan warded off this Sichuan Pixian compatriot. The plane droned overhead then.   Both glanced skyward; the platoon quipped: "Open quick, damn, I'll repay two cans later." Commander: "Want cans? Sky has; shoot plane down, enough for two lifetimes, bloat your mother-in-law first." The can hailed from a prior supply raid. Platoon: "You want me to shoot the plane?" Commander: "Bastard! You shooting or not?" The platoon snatched the light machine gun from a tree fork, jamming the butt against his belly, one hand on the grip, aiming crudely: "Come down, you turtle son!" The other hand squeezed the trigger. Wan assumed jest, resuming his task. "Da-da-da..." Wan jolted; the half-opened can tumbled to his feet, spilling Japanese fish onto Chinese soil. Recoil floored the platoon; he hurled the gun like a branding iron, face ashen. Inspecting the trigger, he snarled: "Whose damn fault, why no safety?!" The gunner dashed over; tall and even-tempered: "Safety was on; how'd it fire without pulling?" Wan's initial panic: "Damn! Position exposed."   The company spearheaded the division's reinforced regiment to raze a recent Japanese depot, guarded by a mere company—but exposure doomed the regiment deep in hostile territory. The assault had been plotted for days; pre-departure, Yang Gancai had toasted them. Wan had sworn a blood oath: No return to Sichuan without success. Hu had jested then: "No Sichuan return means wanting Hunan girl as concubine." Banter was fine in peace, but in war's grip, this was no trifling errand. Wan unleashed a torrent of curses, rising to survey the environs. The main force lagged 15 km behind; advance or abort post-blunder? Enemy rear was a labyrinth; this isolated band teetered on a razor's edge. As if to compel a choice, the radio operator approached; Wan itched to lash out. In his fury and indecision, a miracle unfolded.   The transport's engines hacked like a consumptive invalid, then a witness spied the plane banking left, plummeting, its nose inexorably toward a colossal rock 3-4 km distant. It rebounded twice on the stone, nose and left wing crumpling; the fuselage, fragile as parchment, tumbled gently, skewing onto the slope amid splintered trees. Wan gaped, then bellowed: "Assemble!" The men snapped from reverie, charging downhill in a frenzied cascade. One hour later, 134th Deputy Commander and Reinforced Regiment Commander Liu decoded Wan's vanguard transmission via radio. Another hour passed before Liu received Yang Gancai's directive: Abort Mountain Leopard operation; return with documents expeditiously. One day hence, October 3, Okamura Yasuji's original retreat order from October 2 dawn, addressed to northern Hunan's 6th, 33rd Divisions, Nara and Uemura Detachments, plus its Chinese translation, landed on Xue Yue's desk.   Fifteen days later, at the Changsha Victory Celebration, unit accolades were proclaimed; for "shooting down enemy plane, obtaining vital enemy documents," meritorious honors went to 134th Commander Yang Gancai and Deputy Liu. Each received 1000 yuan and one 3rd Class Baoding Medal. Okamura's October 2 order original: Chinese forces retreated to Miluo and Xiushui Rivers banks assembling; to avoid disadvantage, this army should quickly withdraw to original positions, restore combat strength.   Withdrawal plan as follows: … Xue's October 3 order original:   "Northern Hunan frontal units with current posture immediately pursue facing enemy fiercely, must capture in Chongyang-Yueyang south area. ... Pursuit units may detach part to monitor and sweep enemy collection troops; main force execute overtaking pursuit... Already deep behind enemy advance units vigorously destroy enemy transport lines, cut escape routes."   From October 3, Chinese forces unleashed ferocious counteroffensives against the Japanese on three fronts: northern Hunan, southern Hubei, and the Hunan-Hubei-Jiangxi border; the invaders receded like a vanishing tide, never to reclaim their ground. The 25th and 195th Divisions hounded the 6th Division and Nara Detachment from Fulinpu back to the Miluo River, then to the Xin Qiang River. On October 8, the Japanese fled across the Xin Qiang; the 195th's 566th Brigade surged in pursuit, launching a nocturnal raid on Xitang-Jianshan. Gains were modest, but the enemy, entrenched in their den, resisted with feral tenacity. Qin commanded the brigade's withdrawal southward; northern Hunan operations concluded.   In southern Hubei, the 79th Army chased remnants of the 33rd Division from Sanyan Bridge to Pingjiang, across Nanjiang Bridge, hounding them back to their Tongcheng lair. On the Hunan-Hubei-Jiangxi border, 30th Army Group Commander Wang Lingji orchestrated a pincer against Japanese at Xiushui. The foes retreated to Sandu, mounting a stubborn defense. Chinese assaults faltered for three days; on the fourth night's blitz, victory crowned their efforts, expelling the invaders to their original Wuning stronghold. With both armies reclaiming pre-war lines, the First Battle of Changsha drew to its resounding close.   Over days, Xue Yue received a deluge of congratulatory telegrams and letters from the Nationalist Government, Military Committee, National Assembly, myriad civic groups, party officials, and social luminaries. As hoped, among them was Chiang Kai-shek's effusive missive, brimming with joy. For Xue Yue, this one sufficed. Chiang Kai-shek's telegram to Xue Yue:   "In this northern Hunan campaign, over half the enemy was annihilated. The triumphant news has invigorated the nation, all due to effective command and soldiers' valor; I commend without reservation. Thoroughly investigate and report meritorious personnel from this battle; also report the dead and wounded for awards and relief. With this initial victory foundation laid, our officers and men's responsibilities grow heavier; urge your subordinates to extra vigilance, redoubled effort, avoiding arrogance or complacency, to amass great achievements, my deepest hopes."   As if countering Chongqing's high-powered broadcasts, Japanese radios in Wuhan, Nanjing, Beiping, and Manchukuo blared at full volume: "In this Xiang-Gan operation, valiant Imperial forces penetrated over 100 km into northern Hunan, sweeping anti-peace elements, routing Chinese central main forces, inflicting over 40,000 enemy casualties, a pivotal triumph advancing the holy war. Having achieved objectives, Imperial troops have victoriously withdrawn..."   In the aftermath of the First Battle of Changsha, the Japanese high command spun a tale of calculated restraint, insisting their assault was merely a spoiling raid, a calculated jab never intended to seize and hold the city indefinitely. With brazen confidence, they downplayed their toll, claiming a mere 850 souls lost to death and 2,700 wounded in the fray, while boastfully asserting they had slain 44,000 Chinese defenders and taken 4,000 captive, painting a picture of overwhelming triumph amid the smoke and ruin. Yet, foreign military observers, peering through the fog of propaganda with detached scrutiny, painted a starkly different canvas. They gauged Chinese losses at a far more tempered 20,000 killed and wounded, a heavy but bearable scar on the nation's resolve, while estimating Japanese casualties soared to around 30,000, a grievous hemorrhage that belied the invaders' claims of minimal sacrifice. Military historian Michael Clodfelter, sifting through the annals of conflict, ventured an even grimmer tally: a staggering 50,000 Japanese casualties endured in the relentless clash, a testament to the ferocity of Chinese resistance and the high price of imperial ambition. In the battle's locale, neither side claimed clear victory, but globally for the resistance, it favored China. I would like to take this time to remind you all that this podcast is only made possible through the efforts of Kings and Generals over at Youtube. Please go subscribe to Kings and Generals over at Youtube and to continue helping us produce this content please check out www.patreon.com/kingsandgenerals. If you are still hungry after that, give my personal channel a look over at The Pacific War Channel at Youtube, it would mean a lot to me. The First Battle of Changsha unfolded in September 1939 during China's War of Resistance Against Japan. Japanese forces under Okamura Yasuji advanced into Hunan and Jiangxi, crossing rivers and capturing key positions like Yingtian amid fierce Chinese defenses led by Xue Yue. 

Daiba is just tryin' to Thrive-a in these chapters, as he battles Guts and Serpico with the might of even more ancient Eastern Magic: namely water tornados, makaras, and a giant ethereal Kundalini snake that's essentially a god. Schierke helps Guts to finally exist half in and half out of the Berserker Armor; but, as Daiba ask him: will he be able to use it to its fullest potential without the “power of madness” on his side? These chapters have some amazing action, with the team up between Guts, Schierke and Serpico at its peak. However, there IS a war raging on between the Kushan, Vritannis…and The Band of the Hawk, and by the end of our episode, a swarm of The Godhand's apostles and dread emperor Ganeshka are battling it out for evil supremacy over Midland. Follow No Guts, No Glory on Instagram: https://www.instagram.com/nogutsnoglorypc/ Check out Joey and Ryan's Renaissance Martial Arts organization: https://www.thearma.org/ Check out Steve and Joey's other podcast: https://podcasts.apple.com/us/podcast/probing-ancient-aliens/id1321801647 https://open.spotify.com/show/3aREEXpe4DE37LsNkUxntW Check out Steve and Joey's Patreon for that other podcast: https://www.patreon.com/probingancientaliens

akarta's Strange Fruit with the last track from their Drips EP is something super special. Pouvoi Moteur – French for “motoric power,” since you asked – is exactly what that sounds like: locked-groove krautrock discipline shot through with kosmische shimmer, the kind of track that makes the road ahead feel endless and the destination irrelevant. The ghost of Can's engine room is all over it, that locked hypnosis that somehow never quite repeats itself, while Cluster's smeared electronics hover at the periphery. Aryadiaz, who conceived it partly out of an obsession with factory machinery and, apparently, partly with German beer, describes the 4/4 pattern as feeling like “breaking through space and time.” We're inclined to agree. Out now via Gentle Tuesday Recordings, with a vinyl release to follow through Loide and TipTop Records. Stunning stuff. https://strangefruit.bandcamp.com/album/drips

durée : 00:04:13 - InterNational - par : Jose Manuel Lamarque - Un tour de France des littoraux présenté par la présidente du Cluster Maritime Français, Nathalie Mercier-Perrin. Vous aimez ce podcast ? Pour écouter tous les épisodes sans limite, rendez-vous sur Radio France

Please note that an (authentic!) alert sound is heard twice throughout the episode. Watch us on Youtube: https://youtu.be/UdhHLAquwgs Follow Unholy and learn more about the pod: https://unholy-podcast.lovable.app/ The fourth week of the war with Iran finds both sides insisting—loudly and contradictorily—that peace talks are either underway or nowhere in sight. In the meantime, Iranian missiles continue to hit civilian neighbourhoods across Israel, while rolling news blurs day into night, tracking both the war itself and the political manoeuvres that show little sign of slowing down. And in London, another antisemitic attack raises uncomfortable questions about double standards when it comes to hatred directed at Israel. This week, Yonit and Jonathan sit down with Jake Sullivan, who puts it bluntly: this war should not have started. Sullivan lays out three reasons why the decision was flawed, argues that Donald Trump's “appetite grew with the eating” from the 12-day war to the current escalation, and offers an alternative path—a renewed nuclear deal backed by long-term deterrence. He also raises a troubling possibility: could this conflict increase the likelihood of Chinese action against Taiwan?   Plus: a rare look behind the scenes of Israel's most-watched news broadcast, as Yonit reflects on what it means to sit in the anchor's chair for hours on end—and the personal toll it takes.   00:00 Day 27 — Cluster bomb near Yonit's house  03:00 Life under sirens: sheltering in Tel Aviv  19:48 The Rubio remark: did Israel drag America into war? 23:28 Yonit on anchoring Israel's news during a war she's living 31:23 Jonathan: global antisemitic attacks since the war began  42:06 Jake Sullivan: deal or escalation? 1:15:16 Chutzpah & Mensch Awards Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

00:00 – 10:26 – The Pacers find a way to end their losing streak behind Pascal Siakam's great performance and game-winning block, Notre Dame women's team advances, Kevin is showing off his hair this morning, Jeff is back, why isn't spring break the same for everyone. 10:26 – 22:41 – Morning Checkdown 22:41 – 47:13 – Celebrating the Pacers win for a moment, how does Purdue matchup with Texas, how good are the Longhorns actually, how has the bracket played out? How do we contextualize 7 Sweet 16's in 9 years, some of the massive matchups that are waiting for us this weekend, roasting fill-in producer Caleb's odd college fandom 47:13 – 1:14:47 - Some texters come in Caleb's defense for their college football and basketball fandom, recapping the Pacers nail-biting win over the Magic, comparing the Pacers risking their first round pick and the Colts trading their first round picks, could Darius Acuff go in the top 4 of the NBA Draft, morning checkdown 1:14:48 – 1:19:37 – Jeff has a crazy story he saw, Kevin's last two ball competition last night 1:19:38 – 1:30:01 – We get into a Colts discussion about what we might want to hear from the Colts brass next week at the owner's meetings, are they really "running it back", have they gotten better? 1:30:02 - 1:55:53 – We talk about if there is any Cinderella in the tournament this year before The Athletic's CJ Moore joins us to give his opinion on it and discuss his piece on Braden Smith breaking the NCAA all-time assist record which includes Moore going through some of his assists that tell a story, he also did a story on Darryn Peterson earlier in the year and he gives his take on how an NBA team should approach him in the draft process, CJ also still plays basketball and he explains why he loves it, morning checkdown 1:55:53–2:04:07 – Cluster truck is in the building, the Kevin Bowen burger is returning, previewing our conversation with Bruce Weber 2:04:08 - 2:15:56 – Big Ten Network's Bruce Weber joins to talk about where Cinderella stands, what he remembers about his recruitment of Matt Painter, his memories of working with Matt Painter, what he thinks of Braden Smith breaking the all-time assists record, what type of coach Butler needs INSTANT REPLAY: Bruce Weber or CJ MooreSupport the show: https://1075thefan.com/the-wake-up-call-1075-the-fan/See omnystudio.com/listener for privacy information.

Pool Pros text questions hereIn this timely and globally relevant episode of Mondays Down Under, hosts Lee (Australia) and Shane (New Zealand) are joined by special guest Nick—a seasoned pool industry veteran with over two decades of experience managing a high-volume retail and service operation.Against the backdrop of escalating geopolitical tensions involving the U.S., Israel, and Iran, the conversation pivots to a pressing issue hitting close to home for pool professionals: rising fuel costs and supply uncertainty. While geographically distant from the conflict, Australia and New Zealand are already feeling the ripple effects—especially at the pump.This episode delivers a grounded, practical discussion on how service-based pool businesses can adapt, protect margins, and remain operational in the face of rising costs and potential shortages.⛽ Key Topics & TakeawaysFuel Prices Are Climbing—Fast Fuel costs across Australia and New Zealand are rising sharply, with increases of 20–50 cents per liter already being reported. Some regions are even experiencing fuel shortages, creating urgency for service companies that rely on daily vehicle use.Service Businesses Are on the Front Line Unlike other industries, pool service companies can't reduce fuel consumption easily. Trucks must roll, routes must be completed, and المياه doesn't balance itself. This makes fuel one of the most immediate threats to profitability.

* This episode has been corrected to remove an erroneous reference to the meeting between U.S. President Donald Trump and Japanese Prime Minister Sanae Takaichi being on Wednesday. It is scheduled for Thursday, March 19. Iran hits Tel Aviv with cluster warheads. It's retaliation for the killing of Tehran's security chief and powerbroker, Ali Larijani, whose death leaves a vacuum that will make de-escalation efforts tricky. The head of the National Counterterrorism Center, Joe Kent, quits over the Iran war blaming Israel's influence. And Japan's Sanae Takaichi will have a tightrope to walk in her meeting with U.S. President Donald Trump. Listen to the Morning Bid podcast ⁠⁠here⁠⁠. Sign up for the Reuters Econ World newsletter ⁠⁠here⁠⁠. Listen to the Reuters Econ World podcast ⁠⁠here⁠⁠. Visit the Thomson Reuters Privacy Statement for information on our privacy and data protection practices. You may also visit megaphone.fm/adchoices to opt out of targeted advertising. Learn more about your ad choices. Visit megaphone.fm/adchoices

Donate (no account necessary) | Subscribe (account required) Join Bryan Dean Wright, former CIA Operations Officer, as he dives into today's top stories shaping America and the world. In this Friday Headline Brief of The Wright Report, Bryan covers a wave of Islamist terror attacks across the U.S., including a deadly shooting at Old Dominion University in Virginia and a car bombing attempt at a synagogue and daycare in Michigan. Bryan then turns to the war with Iran, where Tehran has escalated its attacks on oil infrastructure across the Middle East, striking tankers near Iraq, targeting an oil port in Oman, and hitting cargo ships in the Strait of Hormuz as energy markets brace for further disruption. He also reports on U.S. and Israeli strikes inside Iran that are targeting regime forces and infrastructure, new AI-assisted military operations speeding up targeting decisions, and the growing debate in Washington about how long the war will last and what victory might look like. Finally, Bryan closes the week with some encouraging medical research, including new findings on how exercise can boost memory and brain health, plus emerging science linking gut health to sharper thinking as we age.   "And you shall know the truth, and the truth shall make you free." - John 8:32     Keywords: Islamist terror attacks Virginia Michigan, Old Dominion University shooting, synagogue attack Michigan Dearborn, Iran war escalation Strait of Hormuz, Iranian drone attacks oil tankers Middle East, US Israel strikes Tehran IRGC, AI targeting warfare Iran conflict, Trump Iran war strategy, exercise brain health memory research, Bryan Dean Wright podcast, The Wright Report

March Madness starts Friday for Razorback basketball. The Diamond Hogs begin conference play with a three-game series against Mississippi State on Friday. Spring Football kicks off on Sunday. Join HawgSports.com publisher Trey Biddy as he welcomes in Connor Goodson and Kevin Bohannon to discuss the latest and what's next in the three major Arkansas sports on this episode of HawgSports LIVE, driven by the Crain Automotive Team! To learn more about listener data and our privacy practices visit: https://www.audacyinc.com/privacy-policy Learn more about your ad choices. Visit https://podcastchoices.com/adchoices

Stephan Livera and Pieter Wuille discuss Cluster Mempool for Bitcoin Core, its motivations, and its implications for Bitcoin users and miners. Where does the current mempool design have issues? Why is it important to maintain a transparent and reliable open mempool? Pieter Wuille also explains the complexities of transaction clustering and how the new framework improves efficiency and helps keep bitcoin mining open. Timestamps:(00:00) - Intro(01:05) - What is Cluster Mempool?(03:05) - What is its impact on everyday Bitcoin users?(06:21) - How does the mempool work today?(11:52) - Current mempool heuristics and issues(16:37) - Censorship resistance and economic demand(22:56) - Practical implications for exchanges & miners(26:12) - How does cluster mempool work?(29:29) - Transaction clusters & mempool dynamics(37:27) - Should mempools align across the node network?(43:47) - What about other implementations of Bitcoin?(48:17) - Other interesting areas for bitcoin development(52:11) - Closing thoughtsLinks: https://github.com/bitcoin/bitcoin/pull/33629 https://bitcoinmagazine.com/print/the-core-issue-cluster-mempool-problems-are-easier-in-chunks https://delvingbitcoin.org/t/an-overview-of-the-cluster-mempool-proposal/393 https://delvingbitcoin.org/t/mempool-incentive-compatibility/553 Stephan Livera links:Follow me on X: @stephanliveraSubscribe to the podcastSubscribe to Substack

The U.S. is now at war with Iran — and in this episode, we break down how we got here, why it happened now, and what could come next. We react in real time to the opening phase of the conflict, from the shock of direct U.S. involvement to the strategic questions already emerging: the Strait of Hormuz, oil disruption, Iran's missile and drone strategy, regime change talk, and the possibility of a much wider regional war. They also dig into the shifting justifications for the conflict, whether this was really about nuclear weapons, how Israel may have shaped the timing, and why the endgame still looks dangerously unclear. TIMESTAMPS 00:00 – The U.S. is at war with Iran 05:18 – Strategy, Millennium Challenge, and early war questions 08:30 – Strait of Hormuz, oil, and global economic risk 16:52 – What is the real casus belli? 25:00 – Trump, Israel, and the politics of escalation 32:02 – Why Iran may be choosing attrition over saturation 42:00 – Iranian public opinion, regime stability, and miscalculation 49:13 – MEK, Pahlavi, and the regime change fantasy 53:28 – Israel's long-term strategy and the diplomacy problem 56:02 – Does this push Iran toward getting the bomb? 01:04:00 – Cluster munitions, nukes, and moral double standards 01:13:00 – The anti-war myth and Trump's base 01:19:00 – Ground invasion, Kharg Island, and what comes next #Iran #USIranWar #IsraelIran #MiddleEast #Geopolitics #WorldNews #StraitOfHormuz #Trump #MilitaryAnalysis #BroHistory Links to our other stuff on the interwebs: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.youtube.com/@BroHistory⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://brohistory.substack.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ #345 Learn more about your ad choices. Visit megaphone.fm/adchoices

5. Guest: Malcolm Hoenlein Headline:Iran Launches Cluster Bombs Against IsraeliCivilians Summary: Malcolm Hoenleinreports on Iran's use of cluster-bomb warheads against Israeli cities like Haifa. Despite the attacks and financial burdens, 93% of Israelis support the effort to end regional threats permanently. (6)1930 TEHRAN CEMENT FACTORY

[SPECIAL] Larry Johnson : Cluster Warheads Rain Down - Iran's Retaliation UpdateSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

This Week’s Big Questions! You’ve been sending in your brilliantly curious questions, and this week… ✨ Orla asks: Why do we get spots?

Paul lists words of wisdom and words of knowledge in 1 Corinthians 12:8 alongside healings, miracles, prophecy, tongues, and interpretation. But he never defines them. That silence has sparked a real debate in the body of Christ, and in this episode Michael Rowntree works through it carefully.Are these giftings simply elevated Bible teaching, or are they something more? Are they specific, Spirit-initiated operations that reveal hidden things, provide supernatural guidance, and speak into real-life situations? Michael walks through the major interpretive positions, from cessationist scholars like Dr. Tom Schreiner to charismatic perspectives.He'll examine the biblical moments that make you stop: Jesus knowing the woman at the well's full story before she said a word (John 4:17–18). Peter confronting Ananias and Sapphira with information no one told him (Acts 5:1–11). Paul warning a ship's captain of coming disaster before a storm cloud appeared (Acts 27:9–10). Are those words of knowledge and words of wisdom in action?By the end you'll have working definitions of revelation, prophecy, word of knowledge, and word of wisdom. And you'll sit with Paul's deeper question: are we using these gifts to exalt Jesus and build up the body of Christ, or to build a platform for ourselves?0:00 – Introduction0:04 – Defining the question0:34 – Reading 1 Corinthians 121:52 – Cessationist teaching view3:17 – Contextual pushback5:22 – Word of knowledge defined6:15 – Word of wisdom defined7:19 – Cluster of extraordinary gifts8:24 – Knowledge under prophecy11:05 – Blending gift categories14:34 – Defining key terms16:00 – Using gifts rightly16:37 – Closing thoughts Support the showABOUT THE REMNANT RADIO:

HEADLINE: Challenging Gravity: MOND vs. Matter. GUEST: Govert Schilling. SUMMARY: Modified Newtonian Dynamics is discussed as a rival theory, though gravitational lensing and the Bullet Cluster strongly support dark matter's physical existence.

Submit your question and we'll answer it in a future episode!Join our Patreon Community!https://www.patreon.com/badassbreastfeedingpodcastToday on the Badass Breastfeeding podcast, Dianne and Abby are discussing whatis a normal baby problem and what is a breastfeeding problem. Listen in today tolearn more about your baby's behavior and why they are doing what they aredoing!If you are a new listener, we would love to hear from you.  Please consider leavingus a review on iTunes or sending us an email with your suggestions and commentsto badassbreastfeedingpodcast@gmail.com. You can also add your email to ourlist and have episodes sent right to your inbox!Things we talked about:Question about gas [4:50]Cluster feeding [11:05]Distraction [18:39]Shallow latch [24:48]Sleepy babies [28:27]Links to information we discussed or episodes you should check out!https://badassbreastfeedingpodcast.com/episode/sleepy-breastfeeding-babies/https://badassbreastfeedingpodcast.com/episode/latch-regression/Set up your consultation with Diannehttps://badassbreastfeedingpodcast.com/consultations/Check out Dianne's blog here:https://diannecassidyconsulting.com/milklytheblog/Follow our Podcast:https://badassbreastfeedingpodcast.comHere is how you can connect with Dianne and Abby:AbbyTheuring ,https://www.thebadassbreastfeeder.comDianne Cassidy @diannecassidyibclc, http://www.diannecassidyconsulting.comMusic we use:Music: Levels of Greatness from We Used to Paint Stars in the Sky (2012)courtesy of Scott Holmes at freemusicarchive.org/music/ScottHolmes