Species of plant, important culinary herb
POPULARITY
Categories
Trinity Anglican Seminary is built on the same daily prayer rhythms you practice every time you hit play. Morning Prayer. Evening Prayer. Weekly Eucharist. It's a place where chapel and classroom aren't two separate worlds, they're one. Whether you're pursuing a degree or exploring a certificate in Anglican studies, come experience being formed in community around study and prayer at Trinity. Registration is now open for their fall classes at tas.edu/dailyoffice.Evening Prayer for Sunday, June 14, 2026 (Proper 5; Basil the Great, Bishop of Caesarea and Teacher of the Faith, 379).Psalm and Scripture readings (60-day Psalter):Psalm 107:23-43Ezekiel 33:1-23, 30-33Acts 15:1-21Click here to support The Daily Office Podcast with a one-time gift or a recurring donation.Click here to access the text for the Daily Office at DailyOffice2019.com.
Trinity Anglican Seminary is built on the same daily prayer rhythms you practice every time you hit play. Morning Prayer. Evening Prayer. Weekly Eucharist. It's a place where chapel and classroom aren't two separate worlds, they're one. Whether you're pursuing a degree or exploring a certificate in Anglican studies, come experience being formed in community around study and prayer at Trinity. Registration is now open for their fall classes at tas.edu/dailyoffice.Morning Prayer for Sunday, June 14, 2026 (Proper 5; Basil the Great, Bishop of Caesarea and Teacher of the Faith, 379).Psalm and Scripture readings (60-day Psalter):Psalm 107:1-22Joshua 14:5-15Luke 23:50-24:12Click here to support The Daily Office Podcast with a one-time gift or a recurring donation.Click here to access the text for the Daily Office at DailyOffice2019.com.
Send us Fan MailIn this insightful episode of "Leave Your Mark," Vince Cortez interviews Michael Basil, who shares his expertise on effective leadership skills. We dive into practical advice for those looking to improve their career trajectory and truly understand how to be a leader. Michael offers valuable new manager tips to foster inspiration within any team. RESOURCES MENTIONED:► Visit our website: https://www.leaveyourmarkvc.com InVINCEble Coaching course:► https://leave-your-mark-podcast-vc.ck... Discover the keys to monetizing your podcast and gain practical tips on transforming your passion into a thriving venture. ► Visit our website: https://www.leaveyourmarkvc.com ► Donations Here send your gift to our host Vince: https://www.buymeacoffee.com/leaveyou...Subscribe to LYM on YouTube! / @leaveyoumarkvincecortese2020 Vince Cortese, Author: My Story about Courage and FaithBad Days are Really Good Days in Disguisehttps://amzn.to/3TB6VBP_______________Reach out to us on our website!https://www.leaveyourmarkvc.com/contactSupport the show
Important Links:Dad Tired Annual RetreatHost A Dad Tired Conference at your churchJoin the FREE Family Leadership ProgramShop the Dad Tired store for best-selling gearWhen your soul feels anxious, restless, angry, or worn down, what do you do?In this episode of Dad Tired, Pastor Kaleb points men back to one of the most overlooked gifts God has given us for caring for our souls: the Psalms. The Psalms give language to the deepest parts of us — our fear, sorrow, repentance, betrayal, joy, gratitude, and hope.If you've ever thought, “I don't even know what's going on inside of me,” this episode will help you see the Psalms as God's invitation to pray when you don't know how to pray.Kaleb walks through how Jesus, the apostles, and the early church leaned on the Psalms in moments of suffering, anxiety, worship, and spiritual battle. You'll be encouraged to stop treating the Psalms as ancient poetry only, and start using them as daily prayers for your soul.In this episode, you'll learn:How the Psalms help diagnose and shepherd your soulWhy Jesus prayed the Psalms in His sufferingHow the early church used the Psalms in moments of fear and persecutionWhy the Psalms give language to anxiety, repentance, grief, and worshipA simple practice for praying through the Psalms each weekWhether you're anxious, tired, tempted, grateful, or grieving, the Psalms give you words to bring your whole heart before God.Mentioned in this episode:Psalm 22, Psalm 23, Psalm 42, Psalm 51, Psalm 63, Psalm 88, Psalm 91, Psalm 103, Psalm 116, Matthew 26, Acts 4, John Calvin, Athanasius, Basil of Caesarea. Important Links:Dad Tired Annual RetreatHost A Dad Tired Conference at your churchJoin the FREE Family Leadership ProgramShop the Dad Tired store for best-selling gear
The Council of Constantinople as part of Sam and Hank's church Fathers series.00:00:00 - Introduction00:01:45 - Fourth Century Review00:16:00 - The Council begins00:20:20 - The Macedonians00:23:00 - Meletius of Antioch00:28:30 - Gregory of Nazianzus00:38:40 - Nectarius of Constantinople00:44:40 - The Canons of Constantinople00:49:20 - Aftermath00:55:30 - The Creed, or lack thereofRoman EmperorsConstantine the Great (Emperor who convened the Council of Nicaea)Constans (Son of Constantine, ruler of the West)Constantius II (Son of Constantine, ruler of the East)Julian the Apostate (Nephew of Constantine who rejected Christianity)Jovian (Imperial bodyguard commander who briefly succeeded Julian)Valentinian I (Western Emperor who appointed his brother Valens)Valens (Pro-Arian Eastern Emperor killed at Adrianople)Theodosius the Great (Spanish general made Emperor who convened the Council of 381)The Cappadocian Fathers & Allied TheologiansGregory of Nazianzus (Theologian, short-lived chairman of the Council, and Bishop of Constantinople)Basil the Great (Bishop of Caesarea who orchestrated the pro-Nicene strategy)Gregory of Nyssa (Brother of Basil, theologian who delivered Meletius's funeral oration)Meletius of Antioch (Initial chairman of the Council of Constantinople whose sudden death caused turmoil)Other Historical Church FiguresAmbrose of Milan (Influential Western bishop and advisor to emperors)Nectarius of Constantinople (The unbaptized Senator suddenly elected as Bishop and Council chairman)Paulinus of Antioch (Rival pro-Nicene bishop of Antioch backed by Rome and Alexandria)Euzoius of Antioch (Arian bishop appointed to replace Meletius)Maximus the Cynic (Rival candidate whose claim to the see of Constantinople was invalidated by Canon 4)Augustine of Hippo (Prolific Western Church Father referenced in the aftermath)Jerome (Translator of the Vulgate, referenced in the 4th-century timeline)Theological Figures (Eponymous Heresiarchs Mentioned)Arius (Originator of the Arian controversy regarding the Son's divinity)Macedonius I of Constantinople (Pneumatomachian leader whose followers denied the divinity of the Spirit)Eunomius of Cyzicus (Leader of the radical "Anomoean" or hardcore Arian faction)Photinus of Sirmium (4th-century bishop who taught a form of Biblical Unitarianism/Dynamic Monarchianism)Paul of Samosata (3rd-century adoptionist Bishop of Antioch)Apollinaris of Laodicea (Taught that Jesus had a human body but a divine mind instead of a human soul)Sabellius (3rd-century theologian who taught Modalism/Sabellianism)Marcellus of Ancyra (Strict Monarchian theologian condemned for his views on the lifespan of Christ's kingdom)Eudoxius of Constantinople (Prominent Arian bishop referenced in Canon 1)
And we're back! ETRSOP is jumping back onto your feeds with a monthly series on the University Masters in the Kingkiller Chronicle. First up is Master Artificer, Kilvin! Interesting facts in this episode: Some favorite Kilvin sayings, sygaldry and artificery, ever-burning lamps, and mysteries. I bring up Manet, Basil, and Jaxim here because they're also Artificing students!I'm working on some new editing tools and just got a new microphone to try and clean up production :) Thank you for hanging with me!You can find more updates at https://ko-fi.com/etrsop or give me a holler at etrsop@gmail.com. Happy listening!
The Sunday of All Saints reveals the fruit of Pentecost: the Holy Spirit does not produce one type of saint but sanctifies every kind of person according to God's purpose. The saints differ in vocation, personality, and circumstance, yet all are united by the same Spirit who transformed ordinary human lives into icons of Christ. The question is not whether we are the "right kind" of person to become holy, but whether we will allow the Holy Spirit to sanctify the life God has given us. --- Last Sunday we celebrated Pentecost. We celebrated the descent of the Holy Spirit upon the Apostles. And today, on the Sunday of All Saints, we celebrate the result. Pentecost is the gift. All Saints is the fruit. The Holy Spirit descended upon the Church, and what did He produce? Saints. Not one saint. Not one type of saint. Saints. A multitude which no man can number. When we look at the saints, one thing becomes immediately obvious: they are not all the same. Some were bishops. Some were monks. Some were mothers. Some were kings. Some were soldiers. Some were fools for Christ. Some were scholars. Some were illiterate. Some spent their lives in deserts. Others spent their lives in crowded cities. Some died as martyrs. Others lived long and quiet lives. There is no single personality type that guarantees holiness. There is no single profession. No single temperament. No single life story. St. Peter and St. John were different. St. Basil and St. Mary of Egypt were different. St. Nicholas and St. Anthony the Great were different. And yet all became saints. Why? Because holiness does not begin with personality. It begins with the Holy Spirit. The same Spirit who descended at Pentecost formed each of them according to God's purpose. We often think of saints as extraordinary people. But the Church sees them differently. The saints are what ordinary human beings look like when they are filled with the Holy Spirit. The Spirit does not erase personality. He transfigures it. The Spirit does not destroy human gifts. He sanctifies them. The Spirit does not make everyone identical. He makes each person fully what God created him or her to be. This is important because every generation is tempted to imagine that holiness belongs only to certain kinds of people. Some people think: "I could never be a saint because I'm not a monk." Others think: "I'm not educated enough," or "I'm too ordinary," or "I'm raising children, " or: "I'm busy with work." But the saints prove otherwise. God sanctifies fishermen and emperors. Widows and soldiers. Teachers and laborers. Children and elders. The question is not what role we occupy. The question is whether we allow the Holy Spirit to sanctify that role. The Church needs holy priests. But it also needs holy mothers. It needs holy fathers. Holy teachers. Holy business owners. Holy doctors. Holy craftsmen. Holy students. Holy retirees. The world does not need more successful people. It needs more saints. And that means people who do ordinary things in an extraordinary spirit. A teacher who teaches with love. A physician who heals with compassion. A parent who sacrifices with patience. A worker who labors with integrity. A neighbor who forgives. A pauper who prays. The difference is not merely what they do. The difference is the Spirit in which they do it. That is why this Sunday comes immediately after Pentecost. The Church wants us to see the connection. Pentecost is not merely a historical event. It is the beginning of a process that continues today. The Holy Spirit is still descending. Still healing. Still sanctifying. Still making saints. And He is doing so here. Among us. In this parish. In our homes. In our daily lives. The saints are not merely heroes from the past. They are proof of what God intends for humanity. They show us what happens when human beings cooperate with divine grace. They are the fruit of Pentecost. And they remind us that the same Spirit who dwelt in them has been given to us. To Him be glory, together with the Father and the Son, now and ever and unto ages of ages. Amen.
See omnystudio.com/listener for privacy information.
When people suffer serious injury, abuse, or trauma – either through criminal acts or negligence – it can prove challenging to rebuild their lives. We sit down with Basil Joy, an attorney with Goldberg, Goldberg & Maloney, to discuss his work representing victims of crime and personal injury. Basil explains how attorneys help clients pursue justice, accountability, and restitution. Basil reflects on his legal career and how that shapes his work advocating for and protecting the rights of victims. Chatting about a number of nonprofits, we also discuss the value of supporting local communities through board involvement.OUR PARTNERSouthern Chester County Chamber of CommerceLINKSGoldberg, Goldberg & MaloneyWebsiteLinkedInFacebookYouTubeBasil Joy on LinkedInBasil's commencement speech (2013) on YouTubeLocal NonprofitsCrime Victims' Center of Chester CountyGateway HorseworksFox Chase FarmSafe Harbor of Chester CountyChester County Fund for Women and GirlsChester County Bar AssociationAdditional LinksPink | Marked FoundationUnite for HERFox RothschildUnruh Turner Burke & FreesSuitsupplyConcordville CleanersVillanova University Charles Widger School of LawRelated EpisodesAdvocating for Local Communities: Law and Volunteerism with Rob JeffersonSetting the Example and Leading from the Front with Greg NardiSupporting Victims of Sexual Violence and Other Crimes with Christine ZaccarelliTranscriptThe full episode transcript will be posted on our website as soon as it is available.
Ferran adelantó a España tras una gran jugada de Borja Iglesias. El hoy capitán, definió con un buen zurdazo cruzado para superar la estirada abajo de Basil.
ABOUT THE EPISODEAccording to Eastern Orthodoxy, at death the soul ascends to various levels where Angels and Demons engage in a courtroom battle. What determines whether the soul goes up to heaven or down to hell? (Spoiler: it's not Jesus)SponsorThis month's sponsor is Grimke Seminary. Pastors are called to care for the church of God that God called them to. So why do seminaries require men to leave their church to pursue theological studies? At Grimké Seminary, you can get Christ-centered, theological training in the Reformed, Protestant tradition, without leaving your local church. They offer a range of pastoral studies for students of all backgrounds to serve your growth in ministry, from a Bachelor's to a Doctor of Ministry.To apply, go to grimkeseminary.org and use the code “christoverall” to have your application fee waived.Resources to Click“Aerial Toll Houses, or The Saving Weight of Works: The Soul's Trial by Demons After Death According to Eastern Orthodoxy” – Joshua Schooping“Octoechos” – Encyclopedia.com“The Origins of Pascha and Great Week – Part II” – Rev. Alkiviadis C. Calivas“The Icon FAQ” – Orthodox Christian Information Center“Icons as Teachers” – Archpriest John Matusiak“Exhortation to Baptism” – St. Basil the Great“Aerial Toll Houses, Provisional Judgment, and the Orthodox Faith” – Stephen ShoemakerTheme of the Month: Go West, Young Men: Evaluating the Drift toward Eastern OrthodoxyGive to Support the Work Books to ReadAfter Death – Vassilios BakoyiannisThe Doctrine of Deification in the Greek Patristic Tradition – Norman RussellEternal Mysteries Beyond the Grave – Archimandrite PanteleimonThe Departure of the Soul According to the Teaching of the Orthodox Church – St. Anthony's Greek Orthodox MonasteryLife After Death According to the Orthodox Church – Jean-Claude LarchetThe Soul, the Body and Death – Lazar PuhaloMount Athos: Microcosm of the Christian East – Graham Speake an Kallistos WareA Night in the Desert of the Holy Mountain: Discussion with a Hermit on the Jesus Prayer – Metropolitan Hierotheos of NafpaktosThe Future Life According to Orthodox Teaching – Constantine CarvanosThe Soul After Death – Fr. Seraphim RoseThinking Orthodox: Understanding an Acquiring the Orthodox Christian Mind – Eugenia Scarvelis ConstantinouBible, Church, Tradition: An Eastern Orthodox View – Georges FlorovskyEarly Christian Hagiography and Roman History – Timothy D. BarnesPythagorean Knowledge from the Ancient to Modern World – Almut Barbara Renger and Alessandro StavruDemons in Early Judaism and Christianity: Characters and Characteristics – Hector M. Patmore and Josef LösslThe Life of the Virgin: Maximus the Confessor – Stephen J. ShoemakerMary in Early Christian Faith and Devotion – Stephen J. ShoemakerAncient Traditions of the Virgin Mary's Dormition and Assumption – Stephen J. Shoemaker
Thank you for joining us for our 2nd Cabral HouseCall of the weekend! I'm looking forward to sharing with you some of our community's questions that have come in over the past few weeks… Bernice: Hi Doc, First, thank you so much for your podcast. I absolutely love it! My favorite day is Friday. I always enjoy hearing about the research and new products. I learned about psyllium husk on your podcast and I have been taking it every day. I wanted to ask you about Zen Basil. Is this something that we should also consider taking as well as a fiber source? It looks like there are 15 grams per serving! Thanks so much!! Bernice Genel: Hi Dr. Cabral, thank you for your work. About 5 years ago I had tuberculosis and long-term treatment. Since then I've had ongoing issues: persistent joint pain and unstable weight. I struggle to gain weight and often lose it without clear reason. Recent labs showed elevated rheumatoid factor (147.6 IU/mL), high ESR (38), and slightly low hemoglobin, suggesting inflammation or rheumatoid arthritis. I currently take DNS, Omega-3, and D3. What additional supplements could help lower inflammation and support recovery? I live outside the US and can order supplements, but EquiLife support said lab results cannot be processed from my country. I don't want to make the detox cause I don't want to lose the little weight I have. What protocol can I follow? Thank you again for your guidance. Katherine: Hi Doc. Thank you for all you do in helping all of us. I was looking into get a vibration plate and was wondering which one you would recommend. To date, I didn't find one on your resource page or previous podcast. Would you consider recommending one in the future? Thank you! Eli: Hi, Dr. Cabral, I feel like I can't get ahold of my appetite, both behaviorally and physiologically. I also deal with a huge amount of food noise. I notice when I eat a large breakfast, say from a restaurant, I can go basically the entire day without eating. Is it OK to flip meals - dinner for breakfast, regular lunch, and breakfast for dinner? Are there any studies or positive impacts of doing so? Why don't more health professionals talk about this type of practice? It seems as if it would be good for people. I'm desperate to try anything for my appetite and food noise problem. Thank you so much for answering my question! Sheena: Hi Dr. C! hope you and your team are well. I'm a 46 year old female experiencing peri-menopause symptoms. My endocrinologist prescribed me birth control pills to help alleviate some of the symptoms which helped for about 8 mths only but now I'm considering HRT. I purchased the Big 5 and want to know if I need to come off BCP for accurate results? If so, how long should I be off before testing? If not, will I need to notify labs in advance? If I'm on HRT, will my results be accurate for Stress Mood test? And my last question, when doing the Detox, am I allowed to take herbal tinctures? (I take tintures daily to support my adrenals and liver). Will that cancel out the effectiveness of the FM and AYU pills? Thx in advance! You are the BEST! Thank you for tuning into this weekend's Cabral HouseCalls and be sure to check back tomorrow for our Mindset & Motivation Monday show to get your week started off right! - - - Show Notes and Resources: StephenCabral.com/3768 - - - Get a FREE Copy of Dr. Cabral's Book: The Rain Barrel Effect - - - Join the Community & Get Your Questions Answered: CabralSupportGroup.com - - - Dr. Cabral's Most Popular At-Home Lab Tests: > Complete Minerals & Metals Test (Test for mineral imbalances & heavy metal toxicity) - - - > Complete Candida, Metabolic & Vitamins Test (Test for 75 biomarkers including yeast & bacterial gut overgrowth, as well as vitamin levels) - - - > Complete Stress, Mood & Metabolism Test (Discover your complete thyroid, adrenal, hormone, vitamin D & insulin levels) - - - > Complete Food Sensitivity Test (Find out your hidden food sensitivities) - - - > Complete Omega-3 & Inflammation Test (Discover your levels of inflammation related to your omega-6 to omega-3 levels) - - - Get Your Question Answered On An Upcoming HouseCall: StephenCabral.com/askcabral - - - Would You Take 30 Seconds To Rate & Review The Cabral Concept? The best way to help me spread our mission of true natural health is to pass on the good word, and I read and appreciate every review!
"The grandmother of St Basil the Great, she was outstanding for her intellect and piety. She was a disciple of St Gregory the Wonder-worker of Neocaesarea. In the reign of Diocletian, she abandoned her home and hid in the forests and desert places with her husband, Basil. Although their home was confiscated, they felt no pangs of regret. Stripped of everything except their love for God, they settled in an ancient forest and spent seven years there. By God's providence, goats would come down from the mountains and provide them with food. They both died peacefully in the fourth century, after great sufferings for the Christian faith." (Prologue)
This episode of The Currently Reading Podcast is a great place to jump in if you love honest book recommendations and spoiler-free bookish conversation. Meredith and Kaytee help two listeners take control of their overflowing TBR piles with personalized picks. They also get into everything they have been reading lately, from literary fiction like Martyr! by Kaveh Akbar to the cozy fantasy of T. Kingfisher, and they talk honestly about how to keep your reading life calm instead of overwhelming. On this episode of Currently Reading, Meredith and Kaytee are discussing: Bookish Moments: needing some reading sanity and two Kindles? Current Reads: all the great, interesting, and/or terrible stuff we've been reading lately Deep Dive: Kaytee and Meredith boss some listeners' TBRs Before We Go: our new segment featuring a bookish friend post and Meredith brings a book she may DNF Show notes are time-stamped below for your convenience. Read the transcript of the episode (this link only works on the main site). . . . 1:23 - Bookish Moments of the Week 3:16 - The Reimagining of Thornwood House by Jaleigh Johnson (pre-order, releases June 9, 2026) 5:56 - Martyr! by Kaveh Akbar 10:53 - Current Reads 11:14 - The Bookseller by Tim Sullivan (Meredith) 17:03 - The Better Mother by Jennifer van der Kleut (Kaytee) 21:30 - Strangers by Belle Berden (Meredith) 24:06 - Awake by Jen Hatmaker 28:49 - Nine Goblins by T. Kingfisher (Kaytee) 29:36 - A Sorceress Comes To Call by T. Kingfisher 32:40 - What Moves the Dead by T. Kingfisher 32:41 - Nettle & Bone by T. Kingfisher 32:42 - Swordheart by T. Kingfisher 34:56 - The Red Winter by Cameron Sullivan (Meredith) 36:42 - An Unlikely Story 38:25 - Jonathan Strange and Mr. Norrell by Susanne Clarke 39:26 - The Bright Sword by Lev Grossman 40:13 - Isola by Allegra Goodman (Kaytee) 45:35 - Deep Dive: Boss My TBR From Carrie: 47:19 - Lady Tremine by Rachel Hochhauser 47:20 - How to Kill A Guy In Ten Dates by Shailee Thompson 47:24 - Five by Ilona Bannister 47:27 - Isabella Nagg and the Pot of Basil by Oliver Darkshire 47:57 - romance.io 48:02 - This Summer will be Different by Carley Fortune 50:38 - Every Summer After by Carley Fortune From Gianna: 52:26 - The Boomerang by Robert Bailey 52:28 - Down with the Shipmans by Meg Mitchell Moore 52:31 - For Whom the Belle Tolls by Jaysea Lynn 52:34 - Good People by Patmeena Sabit 52:37 - Lady Tremine by Rachel Hochhauser 57:23 - Before We Go Kaytee highlights a bookish friend post Meredith brings a book she might DNF and why 59:43 - Bat Eater and Other Names for Cora Zang by Kylie Lee Baker Support Us: Become a Bookish Friend | Grab Some Merch Shop Bookshop dot org | Shop Amazon Bookish Friends Receive: The Indie Press List with a curated list of five books hand sold by the indie of the month. May's IPL is brought to us from a new to us bookstore, Book & Books in Coral Gables, Florida Love and Chili Peppers with Kaytee and Rebekah - romance lovers get their due with this special episode focused entirely on the best selling genre fiction in the business All Things Murderful with Meredith and Elizabeth - special content for the scary-lovers, brought to you with the behind-the-scenes insights of an independent bookseller From the Editor's Desk with Kaytee and Bunmi Ishola - a quarterly peek behind the curtain at the publishing industry The Bookish Friends Facebook Group - where you can build community with bookish friends from around the globe as well as our hosts Connect With Us: The Show: Instagram | Website | Email | Threads | Substack | Youtube The Hosts and Regulars: Meredith | Kaytee | Mary | Roxanna Production and Editing: Megan Phouthavong Evans Affiliate Disclosure: All affiliate links go to Bookshop unless otherwise noted. Shopping here helps keep the lights on and benefits indie bookstores. Thanks for your support!
Factory workers race to meet impossible wartime production demands while hidden enemies move through the endless machinery of a spinning city in space. One man notices a detail no one else catches, and suddenly millions of lives depend on whether he acts before the shift ends. Factory In The Sky by Basil Wells. That's next on The Lost Sci-Fi Podcast.What can you get for 16 cents a day? Almost nothing anymore.But for less than the price of a cup of coffee once a month, you can unlock all 556 episodes of The Lost Sci-Fi Podcast completely commercial-free — plus bonus episodes you won't hear anywhere else.Lost Sci-Fi Premium is the best way to support the podcast and enjoy uninterrupted listening.Go to LostSciFi.com/premium or just click the link in the description.Basil Wells takes us back to the Golden Age of science fiction with a strange journey high above the Earth, where industry has escaped the ground entirely and danger waits in the clouds. From page 68 in the September 1941 issue of Astonishing Stories, here's Factory In The Sky by Basil Wells…Next on The Lost Sci-Fi Podcast, A silent invader hangs over New York while entire buildings and war machines vanish without a sound. As governments prepare for surrender, one desperate idea forces a handful of men to walk straight toward a weapon no one has survived. The World In The Balance by J.P. Marshall.
Among the luminaries of the early Church were two brothers: Basil the Great and Gregory of Nyssa. Both were bishops, wrote theological treatises and made important contributions to the Church. And yet their style of biblical interpretation was very different. How and why? Music attribution: "Galway" Kevin MacLeod (incompetech.com) Licensed under Creative Commons: By Attribution 4.0 License http://creativecommons.org/licenses/b...
Psalm 68Reading 1: 1 John 4Reading 2: From the treatise On the Holy Spirit by St. Basil the Great, bishopSt. Helena Ministries is a registered 501(c)3 non-profit. Your donations may be tax-deductibleSupport us at: sthelenaministries.com/supportPresentation of the Liturgy of the Hours (Divine Office) from The Liturgy of the Hours (Four Volumes) © 1975, International Commission on English in the Liturgy Corporation. The texts of Biblical readings are reproduced from the New American Bible © 1975
You spent the money on herbs. You watched them grow. Now what? There's a whole season of flavor sitting in your garden, and most of it never makes it to your kitchen. This episode walks you through how to actually use what you grow — fresh, dried, frozen, and blended — from the first oregano harvest in spring all the way through cilantro in winter. Free Download: Herbs Quick Reference Chart A handy cheat sheet for growing and using your favorite kitchen herbs. http://journeywithjill.net/herbchart
The Thinklings Podcast — Episode 296Just a Dash of BasilWelcome to Episode 296 of The Thinklings Podcast!In this episode, the Thinklings spend time discussing Basil the Great, reflecting on memorable quotes, theological insights, and practical wisdom from one of the early church fathers.Thanks for tuning in to this week's conversation!Books & BusinessA History of the Catechumenate — Thinkling CarterSex, Dating, and Relationships — Thinkling LittleThe Autobiography of George Mueller — Thinkling Boyd“I Prepare Sermons 4 Weeks in Advance” (Article) — Thinkling StearnsMain ContentA discussion of Basil the Great, including quotes, reflections, and thoughts on his life and theology.Final MeditationA closing meditation from Joshua 24.Listen & SubscribeFollow The Thinklings Podcast for weekly conversations on books, theology, and the Christian life! This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit thethinklingspodcast.substack.com
The Thinklings Podcast — Episode 296 Just a Dash of Basil Welcome to Episode 296 of The Thinklings Podcast! In this episode, the Thinklings spend time discussing Basil the Great, reflecting on memorable quotes, theological insights, and practical wisdom from one of the early church fathers. Together, they consider how Basil's life and teaching continue to encourage Christians toward faithfulness, clarity, and devotion. Thanks for tuning in to this week's conversation!
Fantasy author Chris A. Jackson returns to Epic Realms to discuss his newest Pathfinder novel, Operation Hellmouth, the revival of the Pathfinder Tales series, and his long history writing fantasy, nautical adventures, and tie-in fiction. Chris and Nick dive into the creative process behind the new novel, including writing Valeros, revisiting beloved pirate characters, crafting infernal battles, and balancing action, humor, and emotional storytelling. Chris also shares behind-the-scenes insight into working with Paizo, writing for shared worlds like Shadowrun and Arkham Horror, and collaborating within long-running projects like Tales of Basil & Mobius. The episode also explores Chris' real-life sailing adventures across the Caribbean, memorable experiences in Belize, gaming, publishing, fantasy worldbuilding, and several upcoming projects currently in development. Filled with laughs, storytelling insight, and plenty of behind-the-scenes discussion, this is a fantastic episode for fantasy readers, tabletop RPG fans, Pathfinder enthusiasts, and aspiring writers alike. Check out Jaxbooks.com His Books on Amazon - https://amzn.to/4wp1kjo
Have you ever wondered what it would be like if they made a film about Sherlock Holmes but every character was a mouse? Of course you have, you're cultured and intelligent.Well, you're in luck, as this week, we're talking about The Great Mouse Detective (aka Basil the Great Mouse Detective).Josh chose this one as he thinks it deserves to be seen by more people. But is he right?Give it a listen to find out!Links to the pod and our social media can be found here. Just select your link of choice!https://linktr.ee/justfilmsandthatpodIf you'd like to get in touch for anything or even suggest a film for us to look at, the email is filmsandthatpod@gmail.comWe're on all the usual social media platforms if just search for Just Films and that and you should find us. Alternatively, all out social media is also linked above!Give us a follow on Letterboxd!https://letterboxd.com/justfilms_that/If you want to support us then you can do so via our Kofi page which is linked below:https://ko-fi.com/justfilmsthatAnything you donate to us will be massively appreciated and will go straight back into the cost of running and growing the podcast!Thank you to Dan and Tom who did our artwork and music! Click the links below to check out more of their fantastic work!Tom (Music)https://www.thomasgeorgemusic.com/Dan (Artwork)https://www.instagram.com/dan_vanguardcomic/Josh on Social Media:Twitter: @JoshieMcsquashyJamie on Social Media:Twitter: @JayAllerton Instagram: @allertonjamie Jamie's other Podcast: Twitter: @bestmovie2pod Instagram @bestmovie2pod Available wherever you get your podcasts. Give it a listen!Cheers!The Just Films & That team Hosted on Acast. See acast.com/privacy for more information.
The Cuban Missile Crisis brought the world close to nuclear war. But who saved the world? Was it US President Kennedy? Or was it a young Russian submarine office named Basil (in Russian, Basil = Vasily)? Check out maps and photos on https://www.dadandmelovehistory.com/ After the end theme music, you'll find these questions: Who were the two superpower countries on opposite sides to each other during the Cold War (1945-91)? What did the US government not like about Cuba? What did American U2 spy planes see in Cuba that threatened the USA? Why do you think President Kennedy did not invade Cuba nor fire nuclear weapons at it? How did Vasily Arkipov save the world from World War III? After the Russians removed their nuclear missiles from Cuba, where did the USA remove their missiles from? Here's our website, where you'll find photos, info about each episode and links to our social media: dadandmelovehistory.com - here, you can also listen to episodes. We also recommend the family-friendly History Detective podcast. Check out historydetectivepodcast.com! For mature history lovers: read industry reviews of Dad's World War II novels, A Chance Kill and The Slightest Chance, at paulletters.com. Available as e-books, as well as in paperback. Dad's first wartime novel, A Chance Kill, is a love-story/thriller based on real events in Poland, Paris, London and Prague. The Slightest Chance follows the remarkable true story of the only escape from Japanese imprisonment by a Western woman during World War II. Please rate and review us wherever you get podcasts. And share our podcast on social media and recommend it to friends – that's how we'll keep going. We will bring you more episodes, so stay subscribed on your podcast app! Podcast cover art by Molly Austin All instrumental music is from https://filmmusic.io and composed by Kevin MacLeod (https://incompetech.com) License: CC BY (http://creativecommons.org/licenses/by/4.0/) Sound effects are used under RemArc Licence. Copyright 2026 © BBC
Welcome to Day 2856 of Wisdom-Trek, and thank you for joining me. This is Guthrie Chamberlain, Your Guide to Wisdom – When Death Becomes Policy: How Christians Must Respond to a Dehumanizing System. Wisdom-Trek Podcast Script - Day 2856 Welcome to Wisdom-Trek with Gramps! I am Guthrie Chamberlain, and we are on Day 2856 of our Trek. The Purpose of Wisdom-Trek is to create a legacy of wisdom, to seek out discernment and insights, and to boldly grow where few have chosen to grow before. Our current series of Theology Thursday lessons is written by theologian and teacher John Daniels. I have found that his lessons are short, easy to understand, doctrinally sound, and applicable to all who desire to learn more of God's Word. John's lessons can be found on his website theologyinfive.com. Today's lesson is titled: When Death Becomes Policy: How Christians Must Respond to a Dehumanizing System. The biblical view of human life begins with the most foundational truth in Scripture: “God created man in His own image” (Genesis 1 verse twenty-seven). Unlike the surrounding cultures of the ancient Near East, where only kings reflected divinity, Israel declared that every human being bore the image of Yahweh. This principle shaped the covenant people's moral and legal systems. The Law commanded care for the widow, the orphan, and the foreigner. It forbade the sacrifice of children. Justice was not a privilege for the strong. It was a duty toward the weak. The prophets reinforced this ethic repeatedly. Isaiah, Amos, Jeremiah, and Micah rebuked rulers not merely for idol worship, but for oppressing the poor, neglecting the sick, and perverting justice. Human life was sacred not because of economic output, but because it belonged to the Creator. The first segment is: Jesus and the Early Church Jesus expanded and embodied this ethic perfectly. He healed the sick, welcomed the outcast, and affirmed the dignity of the forgotten. He did not divide people by status or function. He saw them as lost sheep, image-bearers in need of restoration. This was not sentiment. It was theology in action. The early Church followed His example with startling results. In a Roman culture where the disabled were abandoned, the elderly discarded, and infants exposed to die, Christians responded with radical mercy. They rescued infants from trash heaps. They nursed the sick during plagues, often at the cost of their own lives. And most notably, they created something the world had never seen before: the hospital. The first true hospital was founded in the late fourth century by St. Basil the Great in Caesarea, Cappadocia. The Basilias was a large complex that included housing for the poor, medical treatment for the sick, and care for lepers. It was not a tool of state power or military strategy, but a direct expression of Christian love for those society rejected. Basil believed that if Christ healed the broken, then His followers must do the same. Other Christians followed his lead. St. Fabiola in Rome founded one of the first hospitals in the West. Monasteries across Europe established infirmaries, not only for monks, but for pilgrims, travelers, beggars, and the dying. The very word hospital comes from hospitalis, Latin for “guest,” reflecting the belief that in caring for the sick, Christians were receiving Christ Himself. This was revolutionary. The Greco-Roman world had temples for the healthy and private physicians for the elite, but no institutions devoted to caring for the poor and dying until Christians built them. Their actions were not driven by utility. They were driven by conviction: life matters because it is made by God, seen by Christ, and destined for eternity. That is the root. That is the legacy. And when modern systems again begin to measure lives by what they cost instead of what they are, Christians must not be silent. They must remember who they are. The second segment is: Hospice Is Not the Enemy It is important to be clear: this is not an argument against hospice or genuine palliative care. Hospice reflects the biblical ethic of compassion. It affirms that life has value even in suffering, and that dignity is preserved not by hastening death, but by honoring a person's final days with comfort and presence. The danger arises when that sacred view of life is replaced by a cold calculation. Instead of seeing the end of life as a transition, society begins to treat it as a solution to systemic and financial problems. When the vulnerable are seen as obstacles, death becomes a policy tool, and compassion is used to justify elimination. The third segment is: A Troubling Shift in Canada Nowhere is this more visible than in Canada. What began as Medical Assistance in Dying (MAiD) for those suffering from unbearable physical pain has quickly expanded into something far broader. In 2016, just over 1,000 Canadians ended their lives through MAiD. By 2022, that number had surged to over 13,000. It is now reportedly the sixth leading cause of death in the country. Even more troubling is who is now eligible. Increasingly, MAiD is offered not to those with terminal illness, but to those who are poor, mentally ill, or socially isolated. Some have requested euthanasia because they cannot afford housing or support services. Others have been told that medical treatment is not available, but MAiD is. Doctors have reported being pressured to bring up euthanasia as an option, even in cases where it would never have been considered before. And some policy experts have openly acknowledged that the healthcare system is overloaded and needs a centralized solution. Quietly, and without ever officially declaring it, death is being presented as that solution. The fourth segment is: Death as an Economic Decision One of the most disturbing elements of Canada's MAiD system is how these deaths are recorded. In several provinces, including British Columbia and Ontario, official guidance instructs physicians to list the person's underlying illness or condition as the cause of death, even when the immediate act involved a medically administered lethal substance. This is not a clerical oversight. In British Columbia, the College of Physicians and Surgeons directs providers to list MAiD in Part I(a) of the Medical Certificate of Death, but the manner of death is still to be recorded as “natural.” The underlying illness remains the official cause. In Ontario, physicians providing MAiD are required to notify the Office of the Chief Coroner, and the death certificate process generally follows similar lines, emphasizing the condition rather than the procedure. At the federal level, Health Canada's monitoring and reporting system collects MAiD data separately, but the death certificates provided to families and registered in provincial statistics are shaped by these regional protocols. In public datasets and vital statistics, a MAiD death may appear indistinguishable from a natural death. The effect is not only statistical. It reframes euthanasia as a quiet extension of medical care, rather than a deliberate, policy-driven act of ending life. This framing can soften moral and public resistance, making it easier to expand eligibility without backlash. The fifth segment is: When Consent Looks Like Coercion While MAiD is legally defined as voluntary, the real-world conditions under which many of these decisions are made raise serious ethical concerns. Patients have increasingly reported seeking MAiD due to poverty, homelessness, mental illness, or chronic but non-terminal suffering. When essential care is delayed or denied, and when death is positioned as the one guaranteed option, consent begins to look less like a choice and more like surrender. In 2022, a Canadian Forces veteran suffering from PTSD and a traumatic brain injury approached Veterans Affairs for help. Instead of receiving mental health support, he was offered MAiD. A woman named Denise, suffering from multiple chemical sensitivities, chose MAiD because she could not find safe housing. She was not terminally ill, but her pleas for accommodation went unanswered. A man with a degenerative brain condition applied for MAiD after struggling to get the in-home care he needed. His doctor admitted that with proper support, he would not have sought death. A 51-year-old woman with long COVID applied due to unrelenting pain and fatigue. She said she would have preferred to live, but her condition had become intolerable without treatment options. Roger Foley, a man with a neurological condition, recorded hospital staff suggesting assisted death would cost less than long-term care. A woman with scoliosis and fibromyalgia applied after she could no longer afford her medications. Poverty, not disease, drove her request. A homeless man in Ontario with schizophrenia requested MAiD, saying he could not bear another...
We just watched the original Sisu from 2022 and our minds are completely blown by this absolute rollercoaster of a film! Basil and Keo are here for a new Flix and Giggles review to break down this masterpiece that essentially drops a ruthless protagonist right into the middle of World War II. We talk about the insane cinematography, the incredible performance by Jorma Tommila as the unstoppable gold miner Aatami Korpi, and the sheer creativity of the incredibly brutal fight scenes. The man simply refuses to die, and the practical effects alongside his pure determination had us cheering at the screen the entire time. This film perfectly sets up a gritty, unforgiving world, and it is easily one of the most wild and satisfying movies we have covered on the channel, leaving us absolutely hyped and counting down the days until we can watch the sequel.
The Trend is a Buffalo-based band formed in 1966, known for covering '60s rock 'n roll and rhythm and blues at High school parties and CYO dances. They often performed at local venues including Point Gratiot in Dunkirk NY. Fifty-plus years later, the lineup has evolved, but the core of that 1966 spirit is still there. Joining me in the lounge today are three of the guys who have been keeping The Trend moving from the garage days to right now. The Trend members - Dave Chiarmonte, Dave Roach and Bill Basil reminisced In the Flamingo Lounge on April 20, 2026 about their days as a garage band up to the present.
Matt Topping of Norfolk, VA's COVA Brewing has a knack for winning medals with his fruit beer, but they aren't what you think—from the full fruit refermentation to the light herbal spicing, he's found an equation that's equally successful on draft in the taproom and on the final table at World Beer Cup. From slightly higher pH to low mash temps for fermentable wort to frozen purée to Ebbegarden kveik for the primary fermentation, he's built a systemic approach to both the base gose and to the fruits and spices he layers on top. In this episode, Topping discusses: using Lactobacillus Plantarum from Goodbelly for souring wort low mash temperatures for greater fermentability using frozen rather than aseptic purée to maintain the fresh edge of fruit flavor strategically adding salt and hibiscus in the brite to dial in perfect amounts cleverly pairing fruit and spice flavors like rosemary lemon, passionfruit hibiscus, and more proper temperature for herb steeping brewing with difficult ingredients like watermelon and strawberry controlling finished pH for greater function And more. G&D Chillers A quick word for the brewers out there staring down a broken chiller. You know the pain—warm fermentors, stressed yeast, and that sinking feeling when the repair quote lands in your inbox. With refrigerant regulations changing and the cost of obsolete refrigerants skyrocketing, sometimes the fix costs more than the unit is worth. G&D Chillers is there to help, whether you're a small brew pub or large full-scale production brewery. Don't throw good money at bad equipment. Invest in a solution that grows with your brewery—and keeps your tanks cold when it counts. Big thanks to G&D Chillers for supporting this podcast since 2019. Reach out to them at gdhillers.com/podcast to learn how they can support your next six years of growth. Berkeley Yeast Berkeley Yeast just launched Dry Tropics London! Our best-selling liquid yeast strain, now with all the ease-of-use benefits of dry yeast. Dry Tropics London delivers the soft, pillowy mouthfeel and juicy character you'd expect from a top-tier London Ale strain, but with a serious upgrade: a burst of thiols that unleash vibrant, layered notes of grapefruit and passion fruit. A lot of brewers love the clean passion fruit you get from Tropics, but they don't want every IPA to be a tropical-fruit bomb. At the dry yeast price point, you can pitch and ditch without breaking the bank. Or, you can co-pitch with your house strain to adjust the intensity of the notes. And with nationwide free shipping, there's never been a better time to try Dry Tropics. Order now at berkeleyyeast.com and experience the ease and impact of Dry Tropics London Yeast. PakTech This episode is sponsored by PakTech—delivering craft-beer multipacking you can trust. Our handles are made from 100 percent recycled plastic and are fully recyclable, helping breweries close the loop and advance the circular economy. With a minimalist design, durable functionality you can rely on, and custom color matching, our carriers help brands stand out while staying sustainable. Trusted by craft brewers nationwide, we offer a smarter, sustainable way to carry your beer. To learn more, visit paktech-opi.com. Indie Hops Oregon hop country is heaven to world-class lager varieties, and Indie Hops is proud to have introduced Oregon's newest lager hop, Lórien, in 2022. Lórien is in a growing list of beers that have found their way to the podium and—more importantly—into the hearts of lager lovers across the country. Discover Indie Hops Lórien. (Side effects may include rampant festivity, sales bumps, and exceeded expectations.) Indie Hops—Life is Short. Let's Make It Flavorful. Midea 50/50 Flex If you're like many podcast listeners, you've got a lot of beers at home, and your regular fridge is at capacity. Enter the Midea 50/50 Flex—the industry's first dual-compartment three-way convertible freezer. Here's what all that means for you: options! The 50/50 has the power to be all freezer, all fridge, or a little bit of both. But you'll probably want to use those 20 cubic feet as a massive, garage-ready beer fridge. You can also change which side the door is on or how you want the shelves to be arranged—the 50/50 totally flexes to fit your life. Plus, it's designed to maintain a stable temperature even in non-climate-controlled conditions—so you can crack a cold one even on the warmest days in the man cave. Take your garage to the next level! Check out Midea.com/us/ to get more info about this game changer today. Old Orchard If your brewery is using fruit-juice concentrates, purees, and blends, then why not source everything from a one-stop shop? We might be best-known for flavored blends, but if you need 100 percent purees or concentrates, then we can likely help—even with options not listed on our website. Let us know what you need at oldorchard.com/brewer. ADM Are you ready to shake up the beverage world? ADM is passionate about helping you craft your next breakthrough. From cutting edge natural ingredients like hops to advanced technologies, ADM brings together science and creativity to elevate taste, quality, and recipe design. Whether you're developing a beer innovation or a bold new flavor experience, ADM is your trusted partner in innovation. Let's create something extraordinary—because the future of beer and brewing starts with inspired ideas and exceptional expertise. ADM is where nature meets precision! Learn more at adm.com/alcohol Arryved Running a brewery means juggling a lot—managing production, serving guests, selling online, and keeping everything moving behind the scenes. That's where Arryved comes in. What started as a point-of-sale system has grown into the technology your brewery runs on—built specifically for the teams behind great beer. Unlike generic systems, Arryved brings together taproom service, online sales, brewery management, payments, reporting, and growth tools into one complete platform. So instead of bouncing between systems, you can brew, serve, and sell—all in one place. See it in action at CBC 2026, Booth 1626, or visit arryved.com to learn more. Ss Brewtech Pumps are critical to any advanced homebrewing setup. From mash recirculation to wort transfer, and even for cleaning, a quality pump is a key part of every brew day. The Ss Brew Pump from Ss Brewtech is engineered to tackle even the messiest brew days. Featuring an IP55 water resistance rating, an easy-to-use DIN head with 360-degree rotation, and a flow rate of up to 11 gallons per minute, it has the power to keep your brew day moving. Visit www.SsBrewtech.com/Pump to learn more about how the Ss Brew Pump can upgrade your homebrewery.
The Clayface movie is coming and we've got you covered with everything you need to know.This week we're digging into the vault. Zach and Mike break down the full history of Clayface, all the versions, all the clay. Then dive straight into Clayface: One Bad Day, the 2023 DC one-shot that might just be the blueprint for what the movie does with this character.First: how do you go from Basil Karlo, a horror movie actor driven to murder by a remake of his greatest film, to Matt Hagan, to Preston Payne, to the shapeshifting monster we know today? Zach walks Mike through the whole muddy lineage. Mike's prior Clayface knowledge: a talking blob from a kids' show called Gigglesnort Hotel. We start there.Then: Clayface One Bad Day. A struggling Hollywood actor named Clay Pots lands his dream role and loses himself completely in the process. What follows is one of the darkest, most quietly tragic Clayface stories ever told. He suffocates a man, steals his face, walks onto a movie set, and spends the entire issue auditioning for a role he's already taken. The ending, with ten figures watching him deliver his monologue one final time, hits harder than it has any right to.Also in this episode:- The full Clayface family tree — Basil, Matt, Preston, Sondra, Cassius, and more- The Killing Joke connection hidden in the One Bad Day one-shot- Whether the Batman: Killing Joke animated movie deserved the extra 45 minutes (it did not)- Zach getting accused of being a porch pirate while retrieving his own DoorDash orderCheck out Feat of Clay. Our episode on the Batman: The Animated Series two-parter that inspired the film. Back to back Clayface. You're welcome.Read it yourself: Clayface One Bad Day is available now on DC Universe Infinite and wherever comics are sold.Follow us:YouTube Shorts & TikTok: @brofoeheroInstagram: @brofoeheroSpotify, Apple Podcasts, iHeart & more: search Bros Foes and Heroes#clayface #batman #dccomics #dcu #dc #brosfoesandheroes Thank you to our sponsors! Click on them below:puzzle.io : https://puzzleio.pxf.io/3J0Y4yMagikFlame: https://magikflame.pxf.io/K0dgQvHello Cake: https://cake.sjv.io/kOoEjvSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.
“Shout with joy to God, all the earth. Sing you a psalm in his name. Give glory to His praise.”These words of today's Introit are inviting us to rejoice in God and not only to praise Him but to give glory to His praise. How are we to do this? By singing.As human beings, singing is one of the best means we have to express the joy that is in our hearts and also give solemnity to our rejoicing.God has given us the great gift of our human voice and practically everyone around the world uses it at times to sing.The human voice is considered to be superior to all musical instruments for a number of reasonsBecause it is an instrument that is part of our body, we are able to produce many more sounds with it, and especially we are able to form words.Humans respond emotionally more to the sound of the human voice than to any instrument.The human voice alone functions as both a wind and a string instrument at the same time.It is for this reason that humans have always made music using their voices, using it to accompany their work, their gatherings, and especially their religious ceremonies.And just as the Catholic Church provides us with the greatest act of worship of God, the Holy Mass, so too she provides us with the greatest music to accompany the worship of God.The need to compose proper music for the Mass has been so great that the Mass has often been referred to as the foundational pillar of Western music. It was because of the Mass that musical notation was standardized, that polyphonic music was developed, and that musicians had employment over the centuries.For a long time, in the history of the Church, all Masses were sung Masses; the Low Mass only came into being in the Middle Ages. St. Paul already speaks about singing in his epistle to the Ephesians, when he invites them to “be filled with the holy Spirit, speaking to yourselves in psalms, and hymns, and spiritual canticles, singing and making melody in your hearts to the Lord” (Eph. 5:18-19). This is the epistle for the 20th Sunday after Pentecost.The Fathers of the Church spoke of the importance of singing at Mass:St. Augustine explained that we sing at Mass to show our love for God.St. Basil the Great says that our liturgical songs are like a spiritual incense that raises up to God.St. John Chrysostom said these beautiful words: “Every believer is a musical instrument made by God, and at the same time a musician. If the musician (the soul) keeps the instrument (the body) pure and uses it properly, the two together raise to the Creator a hymn of praise that is pleasing to God.”The bottom line is that one of the main reasons for which God created the human voice is for singing, and the best possible use of the human voice is singing to God at Mass.
Basil Halperin is an assistant professor of economics at the University of Virginia. In Basil's first appearance on the show he discusses the famous but flawed Citrini essay, why Silicon Valley's growth expectations aren't showing up yet in interest rates, the impact of Less Than Zero by George Selgin, what the true frictions in the economy are, the differences between Calvo and menu-cost pricing, the impact of transformational AI on emerging economies and the housing market, and much more. Watch the full length video on our new YouTube Channel! Check out the transcript for this week's episode, now with links. Recorded on March 27th, 2026 Subscribe to David's Substack: Macroeconomic Policy Nexus Follow David Beckworth on X: @DavidBeckworth Follow Basil Halperin on X: @BasilHalperin Follow the show on X: @Macro_Musings Check out our Macro Musings merch! Timestamps 00:00:00 - Intro 00:02:20 - Global Intelligence Crisis 00:07:04 - Transformative AI and Interest Rates 00:21:05 - Optimal Monetary Policy Under Menu Costs 00:48:13 - Transformative AI and its Macro Implications 00:55:41 - Outro
We just finished Humint on Netflix, and while we've talked about the length before, we have to give credit where it's due: this story is awesome. In this Flix and Giggles breakdown, Basil and Keo explore the "really dark" heart of this espionage thriller.We're discussing how the film prioritizes psychological stakes over physical ones, and why the narrative was strong enough to keep us hooked for the full two hours, even if we still think a 90-minute cut would have been lethal. From the interesting world-building to the bleakness of the final act, we're explaining why Humint is a must watch for fans of gritty storytelling.
Licinius was co-emperor with Constantine the Great. At his accession, he had agreed to tolerate Christianity in his territories, but soon turned to persecuting the Christians, and to a variety of carnal sins. He conceived a passion for Glaphyra, a Christian virgin handmaid of the Empress Constantia. When Glaphyra told Constantia of this, the Empress sent her away to Amasia in the East for her protection. There she was received and protected by Bishop Basil of that city. Licinius learned where Glaphyra was hiding and ordered that both she and the bishop be brought to him as prisoners. The soldiers who came for her found that she had already died, so they returned with only Bishop Basil, who was subjected to cruel tortures, then beheaded. His body was cast into the sea, but, with the help of an angel of God, his people found his body, retrieved it from the sea, and returned it to Amasia. The Prologue adds, "The Emperor Constantine raised an army against Licinius, overcame him, arrested him and sent him into exile in Gaul, where he ended his God-hating days."
Fresh herbs like basil come in a multitude of flavor profiles, like cinnamon, lemon and lime. Use basil to enhance your food and cocktails.
Dr. Sunberg highlighted the overarching biblical (prescriptive and descriptive) texts supporting women's shared leadership such as: Genesis 1:26–30, and Galatians 3:28, and Romans 16:1–16. These texts are the “rings that rule overall rings” to use a JRR Tolkien image. Even more, throughout Scripture we see, the power of the Holy Spirit empowering, guiding, encouraging women leaders. Paul's Gospel vision clearly includes women as part of the Great Commission, to share Jesus with the entire world. Phoebe's leadership cited in Romans 16:1–2 implemented Paul's vision. Paul's vision of church planting takes shape and flourishes beside his female workers, like Junia, Phoebe, and Priscilla. While many Christians tend to gloss over these details, they are crucial in planting, serving, and leading churches today. Carla addressed “the sociology of Scripture” which includes both biblical manhood and biblical womanhood as partners in the Gospel, not adversaries. Supremely, Proverbs 31 celebrates God's ideal or vision for woman—one of gift-based ministry and service not limited by gender. Referencing Dr. Ben Witherington, biblical patriarchy, is an exegete without clothes. Citing an extensive history noting the steady growth of women leaders/pastors in the Wesleyan Holiness church that began initially with only 2% women, to now 20% of clergy are women in the Church of the Nazarenewhich Carla is a member. Carla and discussed meeting this year, in person for the first time, during the recent Wesleyan Holiness Women Clergy Conference held in Minneapolis. This event aimed at supporting women clergy and CBE was invited to join in to support their inter-racial, international women's leadership which parallels that of CBE's ministry. We ended by discussing the needs women clergy have for flexibility given all they manage in their lives. women need support for the many responsibilities of being a Christian mother, wife, pastor, scholar, etc. Often these women are a minority serving beside men who have centuries of traditions supporting male-leaders. We ended in prayer. This was indeed an information, wisdom, holiness packed podcast!! Books Carla has contributed to: Viewing the whole sweep of scripture, Carla edited the book: Faithful to the Call, Women in Ministry. She wrote, The Christian Life: A Nazarene Perspective and Why Holiness?: The Transformational Message That Unites Us and Teach us to Pray: What We can Learn from Scripture. Carla coauthored, Reclaiming Eve: The Identity and Calling of Women in the Kingdom of God; Color: God's Intention for Diversity; The Cappadocian Mothers: Deification Exemplified in the Writings of Basil, Gregory and Gregory; Uncommon Virtues: Seven Saints Who shaped our Faith; Reflecting the Image: Our Call to Mirror Christ to the World, and Pulling Back the Curtain on the Former Soviet Union.
This week, Felder is joined by Abram to talk about the different fragrant flowers and herbs throughout Mississippi and recommends that growing oregano, thyme, basil, and rosemary - the pizza plants! Let's Get Dirty!Email Felder anytime at FelderRushing.Blog and listen Friday and Saturday mornings at 9 to The Gestalt Gardener on MPB Think Radio. In the meantime, in Felder's words, "get out and get dirty."If you enjoyed listening to this podcast, please consider contributing to MPB: https://donate.mpbfoundation.org/mspb/podcast Hosted on Acast. See acast.com/privacy for more information.
After some comments on a variety of topics at the top of the program, we dove deep into the following citation from Basil the Great, "because the honor paid to the image passes on to the prototype." We looked at the original context and meaning, and then how it was plucked out of that context and used by John of Damascus, and how that then became central to the arguments of the iconophiles at Nicea II, and hence became the basis of "infallible dogma" for both Roman Catholicism and Eastern Orthodoxy. Not an entertaining program, to be sure, but hopefully a helpful one. Tomorrow we will be doing a Zoom call "open phones" program, so join us then!
We just finished Crime 101 on Amazon Prime, and we're walking away with a not bad verdict, which, in 2026, is a high compliment for a streaming thriller! In this Flix and Giggles breakdown, Basil and Keo discuss the incredible ensemble cast, including a restrained Chris Hemsworth as jewel thief Mike Davis and a brilliantly messy Mark Ruffalo as Detective Lou Lubesnick. From Barry Keoghan's pure chaos energy to Halle Berry's magnetic role as the insurance broker caught in the middle, we're explaining why this is the perfect Friday night movie that prioritizes character over digital explosions.
00:00 Introduction02:20 The structure of the vesperal portion09:21 Why The Bible should have more than 66 books11:22 The structure of the Divine Liturgy of St Basil for Holy Saturday17:31 This service describes salvation in detailed images31:55 Closing~~~Vesperal Divine Liturgy of St. Basil the Great - What is Salvation? ~~~Reference materials for this episode: Reference materials for this episode: The rubrics of the services, in English translation, of The Vesperal Divine Liturgy of St. Basil the GreatScripture citations for this episode:The fifteen Old Testament readings - Genesis 1:1-13 - Isaiah 60:1-16 - Exodus 12:1-12 - The Book of Jonah - Jesus of Navi (Joshua) 5:10 - 15 - Exodus 13:20 - 15:19 - Sophronios (Zephaniah) 3:8 - 15 - 3rd Kingdoms (1st Kings) 17:8 - 24 - Isaiah 61:10 - 62:5 - Genesis 22:1 - 18 - Isaiah 61:1 - 10 - 4th Kingdoms (2nd Kings) 4:8 - 37 - Isaiah 63:11 - 64:5 - Jeremiah 38:31 - 34 (31:31 - 34) - Daniel 3 (including the song of the 3 youths from the Greek manuscript tradition)Epistle reading - Romans 6:3 - 11Gospel reading - Matthew 28:1 - 20~~~In our series of reflections on the Lenten Triodion we have reached the service of Holy Unction, which, strictly speaking, is after Lent is over, but we're going to carry all the way through Holy Week here.The morning of Holy Saturday finds us at the very brink of the celebration of Pascha, Passover, The Resurrection of Jesus The Messiah. All vespers services mark the beginning of the new day (there was evening, there was morning, the first day) & so in this service we transition from Sabbath to The Lord's Day. However, we're still in this accelerated timeline of Holy Week & so we cannot yet fully proclaim Christ is Risen. Yet, in the middle of this service we do transition from the darkness of Holy Week into the white of purity & resurrection & we proclaim who The Messiah is & what it is He saves us from & what it is He saves us for.The Christian Saints Podcast is a joint production of Generative sounds & Paradosis Pavilion. Our hosts are Father Symeon Kees of Iowa City & James John Marks of Chicago.Paradosis Pavilion - https://youtube.com/@paradosispavilion9555https://www.instagram.com/christiansaintspodcasthttps://x.com/podcast_saintshttps://www.facebook.com/christiansaintspodcasthttps://www.threads.net/@christiansaintspodcasthttps://bsky.app/profile/xtiansaintspodcast.bsky.socialIconographic images used by kind permission of Nicholas Papas, who controls distribution rights of these imagesPrints of all of Nick's work can be found at Saint Demetrius Press - http://www.saintdemetriuspress.comAll music in these episodes is a production of Generative Soundshttps://generativesoundsjjm.bandcamp.comDistribution rights of this episode & all music contained in it are controlled by Generative SoundsCopyright 2021 - 2026
Hello Adventurers! It's the most hype-able time of the year! In just a matter of weeks, the NA FanFest will be here and we'll have the first details of Final Fantasy XIV's next expansion! And the immediate Tuesday afterwards Patch 7.5 “Trail to the Heavens” drops! That's a lot. So we're here to break it all down and guess as to what our future holds. We start off with a look back at the previous Live Letter talking about the patch, then head straight into our hopes and predictions that are going to happen at FanFest! It's a wild ride. Spoiler Levels: Pineapple Orange Jelly! “Made from Turali pineapples and navel oranges, the refreshing flavor of this jelly will remind you of Tural no matter where you are.” Before we get into all the new stuff that could be happening, we wanted to make sure to remember where we've been. Spoilers abound in this episode. OSMnotes Lots of things are happening! Why as we post this on a Thursday, tomorrow morning is the next Live Letter! And then next weekend? FanFest! But until then, have some Time Cues: 00:00:00 – We Start The Carbuncle Chronicling 00:00:45 – Intro and General Gabbing 00:01:14 – Pour one out for Blue Mage 00:01:43 – Dissidia Duellum Final Fantasy 00:05:40 – Moogle Treasure Trove – The Hunt for Aphorism 00:08:59 –Live Letter 91! (Thanks to Nova Crystallis for the text recap) 00:09:16 – Where on the calendar the patches are arriving 00:10:30 – New Expert Dungeon: The Clyteum 00:11:07 – New Trial: The Unmaking 00:13:25 – New Ultimate: ??? 00:15:21 – New Alliance Raid Dungeon: Echoes of Vana'diel – Windurst: The Third Walk 00:18:50 – The Occult Crescent: North Horn 00:21:57 – Limited Job Updates 00:23:08 – New Limited Job: Beastmaster 00:25:01 – The part where Basil mentions Dragon Quest IV, but he actually meant Dragon Quest V 00:40:26 – Housing Updates 00:41:10 – Next Week is the North America Final Fantasy XIV Fan Festival! 00:41:19 – Basil's Addendums (MTAC, Anna's Corn Servant got into the Art Contest!, Goody Bag updates, FanFest App mentioned, FanFest Schedule updates) 00:44:354 – The Hype BEGINS! 00:48:49 – Our guesses as to what the new expansion will be called 00:52:34 – Where will we be going this time? 00:58:12 – Job? Jobs? What could they be?? 01:08:57 – The possibility of a Battle Challenge and the importance of having pictures of hotbars on your phone 01:16:28 – On being excited to see people, because seeing FFXIV sickos IRL is when the community is at its best 01:19:29 – What are we looking forward to the most? 01:31:54 – Final Thoughts Music is this episode features tracks such as “Coffee Break” by Masayoshi Soken, arranged by Daiki Ishikawa, “Taco Delight” by Masayoshi Soken, “Pa-Paya” by Masayoshi Soken, and “Fun and Games” by Takafumi Imamura. We also have YouTube Channels! Both for OSMcast proper and The Carbuncle Chronicle! Please subscribe, hit the bell, and share amongst your friends. And as always, feel free to leave us a review on Apple Podcasts! Oh, and if you still use Spotify, go ahead and get on that mobile device and throw us some five stars there too. Tell your friends! As well, just like we mentioned when we do the OSMplugs, you can also join the Discord and support us on Patreon! PS If you have ever wanted some OSMmerch, feel free to check out our TeePublic page! PPS We appreciate you.
Find this episode on YouTube: Let's take a look at what's happening in Iran, Israel, Ukraine. How are we 'waging' war? Well, the answer is more nuanced than you think. And St. Basil has a couple of words for us near the end.-----------------------Conrad's Deli - The best jerky you'll ever have: https://conradsdeli.com/ use promo code "FIRST THINGS" for 10% off.-----------------------✒ Substack: https://johnheersftf.substack.com/ⓧ https://x.com/johnfromftf
Description Recorded at the 2026 Great Hearts National Symposium on February 25, 2026, this edited episode features Christopher Perrin's keynote speech exploring the history, meaning, and renewal of classical education, asking a foundational question: what exactly are we trying to recover? Drawing from sources as diverse as Augustine, Herodotus, Tocqueville, and C.S. Lewis, he traces the transmission of the liberal arts from ancient Greece and Rome through Christendom and into early America. Along the way, Perrin reflects on the gradual fragmentation of this tradition in the modern era, illustrated through the story of the Adams family and the rise of progressive education. Perrin challenges educators to embrace the humility at the heart of true learning—that the more we know, the more we recognize our ignorance—and to see themselves as perpetual students. The episode also highlights the remarkable resurgence of classical education today, describing it as a reawakening of seeds long buried but now beginning to flourish. Perrin emphasizes that education is not merely a science or technique, but the transmission of a living tradition aimed at forming wisdom, virtue, and love. Listeners will come away with a renewed sense of purpose, encouraged to tend the “fire” of learning and to participate faithfully in handing down a rich inheritance to the next generation.Special thanks to the Great Hearts Institute. Episode OutlineWhy the question “What is classical education?” is harder than it sounds (and why it matters for renewal)The paradox of learning: the more you know, the more you know you don't know “Begin with the end”: death, wisdom, and the purpose of education Tradition as “handing down”: language, culture, and education as inheritance Athens and Rome: Greek paideia, Roman educatio, and the liberal arts as a transmitted curriculumThe Church and Christendom: incorporating Greco-Roman learning, theology as “queen,” and widening accessEngland to early America: grammar schools, Boston Latin, Harvard, and the rise of popular literacy The Adams family as an educational case study: formation, thinning, and the modern fracture Progressive education: what changed, what was gained, and why education can't be reduced to a quantitative scienceThe modern renewal: early schools (1979–1981), today's ecosystem, and the need for teacher formation at scaleFinal exhortation: preserve humility, avoid pride, resist false dichotomies, and tend the “fire” of wonder in schoolsKey Topics & TakeawaysClassical education is a tradition before it is a “renewal.” A renewal only makes sense if we can name what is being renewed.Teachers must be perpetual students. The classical teacher models humility—seeking wisdom while resisting the pretense of having arrived.Education is measured by ultimate aims. Human life is fleeting; education gains its meaning from what it prepares us for—virtue, wisdom, piety, and a life rightly ordered.Tradition is unavoidable. Even rejecting tradition requires using language and capacities that were first handed down as a tradition.The liberal arts are an inheritance with a genealogy. From Greek and Roman culture through Christian adaptation, the arts endure because they correspond to human nature.Modern fragmentation reshaped education's purpose. When technology and “force” become central categories, education shifts from transmitting culture to preparing for flux.Progressive vs. classical is not a simple binary. Many educational “heresies” are partial truths held out of balance (false dichotomies distort practice).The renewal must be sustained by love, not mere critique. A movement fueled only by opposition cannot endure—formation requires positive vision and shared goods.Classical education belongs to humanity. It is deeply shaped by Christianity, but not owned exclusively by Christians; it welcomes seekers and strangers.Questions & DiscussionWhy do you think “classical education” is so difficult to define clearly?Name what you most often hear from parents or colleagues when they ask what “classical” means. Try writing a two-sentence definition that includes both aim (why) and means (how), then compare with others.How does the “perpetual student” posture change the way you teach?Where are you tempted to project certainty or expertise instead of wonder and humility? Identify one practice that would help your faculty model learning (shared reading, teacher seminar, public “I don't know yet”).What is education for when you “begin with the end” (mortality in view)?How does remembering death sharpen what matters in curriculum and school culture? If you had to prioritize one outcome—wisdom, virtue, piety, civic responsibility—what would you choose and why?What can we learn from the Adams family arc—formation to fracture?In your own experience, where do you see education becoming “garments that no longer fit”? Does your school respond by adapting the form—or by recovering the measure of the human person?What kind of “renewal energy” actually sustains a school long-term?Where does your community rely on critique of modern schooling rather than a positive vision? Identify one “beauty practice” (music, poetry, liturgy, feast, shared reading) that could rekindle joy and friendship.Suggested Reading & ResourcesThe Liberal Arts Tradition by Kevin Clark, DLS, and Ravi Scott JainAn Introduction to Classical Education: A Guide for Parents by Christopher A. Perrin, MDiv, PhDHumanitasAn Essay Toward Education by W. H. H. KaneFrom Dawn to Decadence by Jacques Barzun Democracy in America by Alexis de Tocqueville The Education of Henry Adams by Henry AdamsThe Value of the Classics by Andrew West (ed.)Address to Young Men on Reading Greek Literature by Basil of CaesareaGreat Hearts Institute Classical Academic PressClassicalUClassicalU Course: The Liberal Arts TraditionClassicalU Course: Classical Education History and IntroductionClassicalU Course:
We're proud to release this ahead of Ryan's keynote at AIE Europe. Hit the bell, get notified when it is live! Attendees: come prepped for Ryan's AMA with Vibhu after.Move over, context engineering. Now it's time for Harness engineering and the age of the token billionaires.Ryan Lopopolo of OpenAI is leading that charge, recently publishing a lengthy essay on Harness Eng that has become the talk of the town:In it, Ryan peeled back the curtains on how the recently announced OpenAI Frontier team have become OpenAI's top Codex users, running a >1m LOC codebase with 0 human written code and, crucially for the Dark Factory fans, no human REVIEWED code before merge. Ryan is admirably evangelical about this, calling it borderline “negligent” if you aren't using >1B tokens a day (roughly $2-3k/day in token spend based on market rates and caching assumptions):Over the past five months, they ran an extreme experiment: building and shipping an internal beta product with zero manually written code. Through the experiment, they adopted a different model of engineering work: when the agent failed, instead of prompting it better or to “try harder,” the team would look at “what capability, context, or structure is missing?”The result was Symphony, “a ghost library” and reference Elixir implementation (by Alex Kotliarskyi) that sets up a massive system of Codex agents all extensively prompted with the specificity of a proper PRD spec, but without full implementation:The future starts taking shape as one where coding agents stop being copilots and start becoming real teammates anyone can use and Codex is doubling down on that mission with their Superbowl messaging of “you can just build things”.Across Codex, internal observability stacks, and the multi-agent orchestration system his team calls Symphony, Ryan has been pushing what happens when you optimize an entire codebase, workflow, and organization around agent legibility instead of human habit.We sat down with Ryan to dig into how OpenAI's internal teams actually use Codex, why the real bottleneck in AI-native software development is now human attention rather than tokens, how fast build loops, observability, specs, and skills let agents operate autonomously, why software increasingly needs to be written for the model as much as for the engineer, and how Frontier points toward a future where agents can safely do economically valuable work across the enterprise.We discuss:* Ryan's background from Snowflake, Brex, Stripe, and Citadel to OpenAI Frontier Product Exploration, where he works on new product development for deploying agents safely at enterprise scale* The origin of “harness engineering” and the constraint that kicked off the whole experiment: Ryan deliberately refused to write code himself so the agent had to do the job end to end* Building an internal product over five months with zero lines of human-written code, more than a million lines in the repo, and thousands of PRs across multiple Codex model generations* Why early Codex was painfully slow at first, and how the team learned to decompose tasks, build better primitives, and gradually turn the agent into a much faster engineer than any individual human* The obsession with fast build times: why one minute became the upper bound for the inner loop, and how the team repeatedly retooled the build system to keep agents productive* Why humans became the bottleneck, and how Ryan's team shifted from reviewing code directly to building systems, observability, and context that let agents review, fix, and merge work autonomously* Skills, docs, tests, markdown trackers, and quality scores as ways of encoding engineering taste and non-functional requirements directly into context the agent can use* The shift from predefined scaffolds to reasoning-model-led workflows, where the harness becomes the box and the model chooses how to proceed* Symphony, OpenAI's internal Elixir-based orchestration layer for spinning up, supervising, reworking, and coordinating large numbers of coding agents across tickets and repos* Why code is increasingly disposable, why worktrees and merge conflicts matter less when agents can resolve them, and what it really means to fully delegate the PR lifecycle* “Ghost libraries”, spec-driven software, and the idea that a coding agent can reproduce complex systems from a high-fidelity specification rather than shared source code* The broader future of Frontier: safely deploying observable, governable agents into enterprises, and building the collaboration, security, and control layers needed for real-world agentic workRyan Lopopolo* X: https://x.com/_lopopolo* Linkedin: https://www.linkedin.com/in/ryanlopopolo/* Website: https://hyperbo.la/contact/Timestamps00:00:00 Introduction: Harness Engineering and OpenAI Frontier00:02:20 Ryan's background and the “no human-written code” experiment00:08:48 Humans as the bottleneck: systems thinking, observability, and agent workflows00:12:24 Skills, scaffolds, and encoding engineering taste into context00:17:17 What humans still do, what agents already own, and why software must be agent-legible00:24:27 Delegating the PR lifecycle: worktrees, merge conflicts, and non-functional requirements00:31:57 Spec-driven software, “ghost libraries,” and the path to Symphony00:35:20 Symphony: orchestrating large numbers of coding agents00:43:42 Skill distillation, self-improving workflows, and team-wide learning00:50:04 CLI design, policy layers, and building token-efficient tools for agents00:59:43 What current models still struggle with: zero-to-one products and gnarly refactors01:02:05 Frontier's vision for enterprise AI deployment01:08:15 Culture, humor, and teaching agents how the company works01:12:29 Harness vs. training, Codex model progress, and “you can just do things”01:15:09 Bellevue, hiring, and OpenAI's expansion beyond San FranciscoTranscriptRyan Lopopolo: I do think that there is an interesting space to explore here with Codex, the harness, as part of building AI products, right? There's a ton of momentum around getting the models to be good at coding. We've seen big leaps in like the task complexity with each incremental model release where if you can figure out how to collapse a product that you're trying to.Build a user journey that you're trying to solve into code. It's pretty natural to use the Codex Harness to solve that problem for you. It's done all the wiring and lets you just communicate in prompts. To let the model cook, you have to step back, right? Like you need to take a systems thinking mindset to things and constantly be asking, where is the Asian making mistakes?Where am I spending my time? How can I not spend that time going forward? And then build confidence in the automation that I'm putting in place. So I have solved this part of the SDLC.swyx: [00:01:00] All right.[00:01:03] Meet Ryan swyx: We're in the studio with Ryan from OpenAI. Welcome.Ryan Lopopolo: Hi,swyx: Thanks for visiting San Francisco and thanks for spending some time with us.Ryan Lopopolo: Yeah, thank you. I'm super excited to be here.swyx: You wrote a blockbuster article on harness engineering. It's probably going to be the defining piece of this emerging discipline, huh?Ryan Lopopolo: Thank you. It is it's been fun to feel like we've defined the discourse in some sense.swyx: Let's contextualize a little bit, this first podcast you've ever done. Yes. And thank you for spending with us. What is, where is this coming from? What team are you in all that jazz?Ryan Lopopolo: Sure, sure.Ryan Lopopolo: I work on Frontier Product Exploration, new product development in the space of OpenAI Frontier, which is our enterprise platform for deploying agents safely at scale, with good governance in any business. And. The role of VMI team has been to figure out novel ways to deploy our models into package and products that we can sell as solutions to enterprises.swyx: And you have a background, I'll just squeeze it in there. Snowflake, brick, [00:02:00] stripe, citadel.Ryan Lopopolo: Yes. Yes. Same. Any kind of customerswyx: entire life. Yes. The exact kind of customer that you want to,Vibhu: so I'll say, I was actually, I didn't expect the background when I looked at your Twitter, I'm seeing the opposite.Stuff like this. So you've got the mindset of like full send AI, coding stuff about slop, like buckling in your laptop on your Waymo's. Yes. And then I look at your profile, I'm like, oh, you're just like, you're in the other end too. Oh, perfect. Makes perfect.Ryan Lopopolo: I it's quite fun to be AI maximalist if you're gonna live that persona.Open eye is the place to do it. And it'sswyx: token is what you say.Ryan Lopopolo: Yeah. Certainly helps that we have no rate limits internally. And I can go, like you said, full send at this stay.swyx: Yeah. Yeah. So the Frontier, and you're a special team within O Frontier.Ryan Lopopolo: We had been given some space to cook, which has been super, super exciting.[00:02:47] Zero Code ExperimentRyan Lopopolo: And this is why I started with kind of a out there constraint to not write any of the code myself. I was figuring if we're trying to make agents that can be deployed into end to enterprises, they should be [00:03:00] able to do all the things that I do. And having worked with these coding models, these coding harnesses over 6, 7, 8 months, I do feel like the models are there enough, the harnesses are there enough where they're isomorphic to me in capability and the ability to do the job.So starting with this constraint of I can't write the code meant that the only way I could do my job was to get the agent to do my job.Vibhu: And like a, just a bit of background before that. This is basically the article. So what you guys did is five months of working on an internal tool, zero lines of code over a mi, a million lines of code in the total code base.You say it was cenex, more like it was cenex faster than you would've. If you had done it by end. SoRyan Lopopolo: yeah, thatVibhu: was the mindset going into this, right?Ryan Lopopolo: That's right.[00:03:46] Model Upgrades LessonsRyan Lopopolo: Started with some of the very first versions of Codex CLI, with the Codex Mini model, which was obviously much less capable than the ones we have today.Which was also a very good constraint, right? Quite a visceral feeling to ask the [00:04:00] model to build you a product feature. And it just not being able to assemble the pieces together.Which kind of defined one of the mindsets we had for going into this, which is whenever the model just cannot, you always pop open at the task, double click into it, and build smaller building blocks that then you can reassemble into the broader objective.And it was quite painful to do this. Honestly, the first month and a half was. 10 times slower than I would be. But because we paid that cost, we ended up getting to something much more productive than any one engineer could be because we built the tools, the assembly station for the agent to do the whole thing.[00:04:43] Model Generations, Build Systems & Background ShellsRyan Lopopolo: But yeah, so onward to G BT 5, 5, 1, 5, 2, 5, 3, 5 4. To go through all these model generations and see their kind of corks and different working styles also meant we had to adapt the code base to change things up when the model was revved. [00:05:00] One interesting thing here is five two, the Codex harness at the time did not have background shells in it, which means we were able to rely on blocking scripts to perform long horizon work.But with five, three and background shells, it became less patient, less willing to block. So we had to retool the entire build system to complete in under a minute and. This is not a thing I would expect to be able to do in a code base where people have opinions. But because the only goal was to make the Asian productive over the course of a week, we went from a bespoke make file build to Basil, to turbo to nx and just left it there because builds were fast at that point.swyx: Interesting. Talk more about Turbo TenX. That's interesting ‘cause that's the other direction that other people have been doing.Ryan Lopopolo: Ultimately I have. Not a lot of experience with actual frontend repo architecture.swyx: You're talking that Jessica built the sky. So I'm like, I know the NX team. I know Turbo from Jared [00:06:00] Palmer.And I'm like, yeah, that's an interesting comparison.[00:06:02] One Minute Build LoopRyan Lopopolo: The hill we were climbing right, was make it fast.swyx: Is there a micro front end involved? Is it how how complex reactRyan Lopopolo: electron base single app sort of thingswyx: And must be under a minute. That's an interesting limitation. I'm actually not super familiar with the background shelf stuff.Probably was talked about in the fight three release.Ryan Lopopolo: BA basically means that codex is able to spawn commands in the background and then go continue to work while it waits for them to finish. So it can spawn an expensive build and then continue reviewing the code, for example.swyx: Yeah.Ryan Lopopolo: And this helps it be more time efficient for the user invoking the harness.swyx: And I guess and just to really nail this, like what does one minute matter? Like why not five, okay, good. We want no. WeRyan Lopopolo: want the inner loop to be as fast as possible. Okay. One minute was just a nice round number and we were able to hit it.swyx: And if it doesn't complete, it kills it or some something,Ryan Lopopolo: No.We just take that as a signal that we need to stop what we're doing, double click, decompose a build graph a bit to get us to high back under so that we [00:07:00] can able the agent continue to operate.swyx: It's almost like you're, it's like a ratchet. It's like you're forcing build time discipline, because if you don't, it'll just grow and grow.That's right. And you mentioned that my current, like the software I work on currently is at 12 minutes. It sucks.Ryan Lopopolo: This has been my experience with platform teams in the past, where you have an envelope of acceptable build times and you let it go up to breach and then you spend two, three weeks to bring it back down to the lower end of the average low bed stop.But because tokens are so cheap Yeah. And we're so insanely parallel with the model, we can just constantly be gardening this thing to make sure that we maintain these in variants, which means. There's way less dispersion in the code and the SDLC, which means we can simplify in a way and rely on a lot more in variance as we write the software.[00:07:45] Observability, Traces & Local Dev StackVibhu: Lovely.[00:07:46] Humans Are BottleneckVibhu: You mentioned in your article, like humans became the bottleneck, right? You kicked off as a team of three people. You're putting out a million line of code, like 1500 prs, basically. What's the mindset there? So as much as code is disposable, you're doing a lot of review. A lot [00:08:00] of the article talks about how you wanna rephrase everything is prompting everything, is what the agent can't see.It's kind of garbage, right? You shouldn't have it in there. So what's like the high level of how you went about building it, and then how you address okay, humans are just PR review. Like how is human in the loop for this?Ryan Lopopolo: We've moved beyond even the humans reviewing the code as well.[00:08:19] Human Review, PR Automation & Agent Code ReviewRyan Lopopolo: Most of the human review is post merge at this point.But post, post merge, that's not even reviewed. That's justswyx: Oh, let's just make ourselves happy by YouRyan Lopopolo: haven't used fundamentally. The model is trivially paralyzable, right? As many GPUs and tokens as I am willing to spend, I can have capacity to work with my hood base.The only fundamentally scarce thing is the synchronous human attention of my team. There's only so many hours in the day we have to eat lunch. I would like to sleep, although it's quite difficult to, stop poking the machine because it makes me want to feed it. You have to step back, right?Like you need to take a systems thinking mindset to things and [00:09:00] constantly be asking where is the agent making mistakes? Where am I spending my time? How can I not spend that time going forward? And then build confidence in the automation that I'm putting in place. So I have solved this part of the SDLC, and usually what that has looked like is like we started needing to pay very close attention to the code because the agent did not have the right building blocks to produce.Modular software that decomposed appropriately that was reliable and observable and actually accrued a working front end in these things, right?[00:09:35] Observability First SetupRyan Lopopolo: So in order to not spend all of our time sitting in front of a terminal at most, doing one or two things at a time, invested in giving the model that observability, which is that that graph in the post here.swyx: Yeah. Let's walk through this traces and which existed firstRyan Lopopolo: we started with just the app and the whole rest of it. From vector through to all these login metrics, APIs was, I dunno, half an [00:10:00] afternoon of my time. We have intentionally chosen very high level fast developer tools. There's a ton of great stuff out there now.We use me a bunch, which makes it trivial to pull down all these go written Victoria Stack binaries in our local development. Tiny little bit of python glue to spin all these up. And off you go. One neat thing here is we have tried to invert things as much as possible, which is instead of setting up an environment to spawn the coding agent into, instead we spawn the coding agent, like that's the entry point.It's just Codex. And then we give Codex via skills and scripts the ability to boot the stack if it chooses to, and then tell it how to set some end variables. So the app and local Devrel points at this stack that it has chosen to spin up. And this I think is like the fundamental difference between reasoning models and the four ones and four ohs of the past, where these models could not think so you had to put them in [00:11:00] boxes with a predefined set of state transitions.Whereas here we have the model, the harness be the whole box. And give it a bunch of options for how to proceed with enough context for it to make intelligent choices. SoVibhu: sales, so like a lot of that is around scaffolding, right? Yes. Previous agents, you would define a scaffold. It would operate in that.Lube, try again. That's pivoted off from when we've had reasoning models. They're seeming to perform better when you don't have a scaffold, right? That's right.[00:11:28] Docs Skills GuardrailsVibhu: And you go into like niches here too, like your SPEC MD and like having a very short agent MG Agent md.swyx: Yes. Yes.Vibhu: Yeah. So you even lay out what it is here, but I likeswyx: the table contents.Vibhu: Yeah.swyx: Like stuff like this, it really helps guide people because everyone's trying to do this.Ryan Lopopolo: This structure also makes it super cheap to put new content into the repository to steer both the humans and the agents.swyx: You, you reinvented skills, right?Vibhu: One big agents andswyx: skills from first princip holdsRyan Lopopolo: all skills did not exist when we started doing this.Vibhu: You have a short [00:12:00] one 100 line overall table of contents and then you have little skills, right? Core beliefs, MD tech tracker. Yeah. Yeah. The scale is overRyan Lopopolo: The tech jet tracker and the quality score are pretty interesting because this is basically a tiny little scaffold, like a markdown table, which is a hook for Codex to review all the business logic that we have defined in the app, assess how it matches all these documented guardrails and propose follow up work for itself.Before beads and all these ticketing systems, we were just tracking follow up work as notes in a markdown file, which, we could spa an agent on Aron to burn down. There's this really neat thing that like the models fundamentally crave text. So a lot of what we have done here is figure out ways to inject textswyx: intoRyan Lopopolo: the system right when we get a page, because we're missing a timeout, for example.I can just add Codex in Slack on that page and say, I'm gonna fix this by adding a timeout. Please update our reliability documentation. To require that all network calls have [00:13:00] timeouts. So I have not only made a point in time fix, but also like durably encoded this process knowledge around what good looks like.swyx: Yeah.Ryan Lopopolo: And we give that to the root coding agent as it goes and does the thing. But you can also use that to distill tests out of, or a code review agent, which is pointed at the same things to narrow the acceptable universe of the code that's produced.swyx: I think one of the concerns I have with that kind of stuff is you think you're making the right call by making, it's persisted for all time across everything.Yes. But then you didn't think about the exceptions that you need to make, right? And that you have to roll it back.Vibhu: Part of it isswyx: also sometimes it can follow your s instructions too.Vibhu: It's somewhat a skill, right? So it determines when it uses the tools, right? Like it's not like it'll run outta every call.It'll determine when it wants to check quality score, right?Ryan Lopopolo: Yeah. And we do in the prompts we give these agents, allow them to push back,[00:13:51] Agent Code Review RulesRyan Lopopolo: When we first started adding code review agents to the pr, it would be Codex, CLI. Locally writes the change, pushes up a PR on [00:14:00] those PR synchronizations of review agent fires.It posts a comment. We instruct Codex that it has to at least acknowledge and respond to that feedback. And initially the Codex driving the code author was willing to be bullied by the PR reviewer, which meant you could end up in a situation where things were not converging. So yeah, we had to,swyx: he's just a thrash.Ryan Lopopolo: We had to add more optionality to the prompts on both of these things, right? The reviewer agents were instructed to bias toward merging the thing to not surface anything greater than a P two in priority. We didn't really define P two, but we gave it, youswyx: did define P two.Ryan Lopopolo: We gave it a framework within which to score its outputswyx: and then greater than P zero is worse, right?Yes. P two is very good.Ryan Lopopolo: P zero is you will mute the code place ifswyx: you merch thisRyan Lopopolo: thing, right?swyx: Yeah.Ryan Lopopolo: But also on the code authoring agent side, we also gave it the flexibility to either defer or push back against review feedback, right? This happens all the time, right? Like I happen to notice something and leave a code review, [00:15:00] which.Could blow up the scope by a factor of two. I usually don't mean for that to be addressed Exactly. In the moment. It's more of an FYI file it to the backlog, pick it up in the next fix it week sort of thing. And without the context that this is permissible, the coding agents are gonna bias toward what they do, which is following instructions.swyx: Yeah.[00:15:19] Autonomous Merging Flowswyx: I do wanted to check in on a couple things, right? Sure. All the coding review agent, it can merge autonomously. I think that's something that a lot of people aren't comfortable with. And you have a list here of how much agents do they do Product code and tests, CI configuration and release tooling, internal Devrel tools, documentation eval, harness review, comments, scripts that manage the repository itself, production dashboard definition files, like everything.Yes. And so they're just all churning at the same time, is there like a record that, that any human on the team pulls to stop everythingRyan Lopopolo: Because we are building a native application here. We're not doing continuous deploy. So there's still a human in the loop for cutting the release branch.I see. We require a blessed [00:16:00] human approved smoke test of the app before we promote it to distribution, these sort of things.swyx: So you're working on the app, you're not building like infrastructure where you have like nines of reliability, that kinda stuff?Ryan Lopopolo: That's correct. That's correct. Okay. And also like full recognition here that all of this activity took in a completely greenfield repository.There's. Should be no script that this applies generally toswyx: this is a production thing, you're gonna shipRyan Lopopolo: toswyx: customers. Of course. Yeah, of course. So this is realVibhu: And like one of the things there is, you mentioned you started this as a repo from scratch. The onboarding first month or so was pretty, it was like working backwards, right?Yeah. And then you had to work with the system and now you're at that point where you know, you're very autonomous. I'm curious like, okay, so what, how human in the loop is it? So what are the bottlenecks that you wish you could still automate? And part of that is also like, where do you see the model trajectory improving and offloading more human in the loop?We just got 5.4. It's a really good,Ryan Lopopolo: fantastic model, by the way.Vibhu: Yeah. Yeah. It's the first one that's merged. Top tier coding. So it's codex level coding and reasoning. So general reasoning both in one model. SoRyan Lopopolo: andVibhu: computer [00:17:00] use vision.Ryan Lopopolo: Now we now with five four, I can just have Codex write the blog post, whereas for this one I had to balance between chat.swyx: Oh, I need to, I might be out of a job. Oh my God.Ryan Lopopolo: Oh,swyx: I know. You just gave me an idea for a completely AI newsletter that five four could do. Yeah, I get it Now.Ryan Lopopolo: This sort of thing is just one example of closing the loop, right? Like the dashboard thing you mentioned. We have Codex authoring the Js ON, for the Grafana dashboards and publishing them and also responding to the pages, which means when it gets the page, it knows exactly which dashboards are defined and what alerts.What alert was triggered by which exact log in the code base. ‘cause all of this stuff is collated together.swyx: It has to own everything.Yes. Yeah. Yeah.Ryan Lopopolo: And it means that if we have an outage that did not result in a page. It has the existing set of dashboards available to it. It has the existing set of metrics and logs and can figure out where the gaps in the dashboard are or [00:18:00] in the underlying metrics and fix them in one go.In the same way, you would have a full stack engineer be able to drive a feature from the backend all the way to the front end.Vibhu: So it, it seems like a lot of the work you guys had to do was you as a small team are fully working for a way that the model wants the software to be written. It's like less human legible for better. Code legibility, agent legibility. How do you think that affects broader teams? So one at OpenAI, do liaison, like this is how software should be written. Like I can imagine, say you join a new team with this methodology, this mindset there's ways that, teams do code review, teams write code, like teams are structured and a lot of it is for human legibility.So should we all swap? Like how does this play back one broader into OpenAI and then like broader into the software engineering, right? Is it like teams that pick this up will it's pretty drastic, right? You have to make a pretty big switch. Should they just full send Yeah.Ryan Lopopolo: The mindset is very much that I'm removed from the process, right? I can't really have deep code level opinions about [00:19:00] things. It's as if I'm. Group tech leading a 500 person organization.Vibhu: Yeah.Ryan Lopopolo: Like it's not appropriate for me to be in the weeds on every pr. This is why that post merge code review thing is like a good analog here, right?Like I have some representative sample of the code as it is written, and I have to use that to infer what the teams are struggling with, where they could use help, where they're already moving quickly and I can pivot my focus elsewhere.Vibhu: Yeah.Ryan Lopopolo: So I don't really have too many opinions around the code as it is written.I do, however, have a command based class, which is used to have repeatable chunks of business logic that comes with tracing and metrics and observability for free. And the thing to focus on is not how that business logic is structured, but that it uses this primitive ‘cause I know that's gonna give leverage by default.Vibhu: Yeah.Ryan Lopopolo: Yeah, back to that sort of systems stinking,Vibhu: and you have part of that in your blog post, enforcing architecture and ta taste how you set boundaries for what's used. There's also a section on redefining [00:20:00] engineering and stuff, but yeah, it's just, it's interesting to hear,Ryan Lopopolo: and as the models have gotten better, they have gotten better at proposing these abstractions to unblock themselves, which again, lets me move higher and higher up the stack to look deeper into the future on what ultimately blocked the team from shipping.swyx: Yeah. You mentioned so you, this is primarily a, it is like a 1 million line of code base electron app. But it manages its own services as well, so it's like a backend for front end type thing.Ryan Lopopolo: We do have a backend in there, but that's hosted in the cloud.Yeah. This sort of structure is actually within the separate main and render processesWithin theswyx: electric.That's just how electronic works.Ryan Lopopolo: Yeah, of course. So have also treated like. MVC style decomposition with the same level of rigor, which has been very fun.swyx: I have a fun pun. This is a tangent, NVC is model view controller. Any sort of full stack web Devrel knows that.But my AI native version of this is Model view Claw, the clause the harness.Ryan Lopopolo: That's right. That's right. I do think that there is an interesting space to [00:21:00] explore here with Codex, the harness as part of building AI products, right? There's a ton of momentum around getting the models to be good at coding.We've seen big leaps in like the task complexity with each incremental model release where if you can figure out how to collapse a product that you're trying to build, a user journey that you're trying to solve into code, it's pretty natural to use the Codex Harness to solve that problem for you. It's done all the wiring and lets you just communicate and prompts to let the model cook.Yeah. It's been very fun. And there's also a very engineering legible way of increasing capabil. It's fantastic, right? Yeah. Just give you, just give the model scripts, the same scripts you would already build for yourself.swyx: Yeah.Yeah. So for listeners, this is Ryan saying that software engineering or coding against will eat knowledge work like the non-coding parts that you would normally think.Oh, you have to build a separate agent for it. No, start a coding agent and go out from there. Which open Claw has like it's pie Underhood.Ryan Lopopolo: [00:22:00] Yes.Vibhu: Basically define your task in code. Everything is a codingswyx: agent by the way. Since I brought it up, it's probably the only place we bring it up. Is any open claw usage from you?Any?Ryan Lopopolo: No. No. Not for me. I don't have any spare Mac Minis rattling around my house.swyx: You can afford it? No. I just, I'm curious if it's changed anything in opening eye yet, but it's probably early days. And then the other, the other thing I, I wanna pull on here is like you mentioned ticketing systems and you mentioned prs and I'm wondering if both those things have to go away or be reinvented for this kind of coding.So the git itself and is like very hostile to multi-agent.Ryan Lopopolo: Yeah. We make very heavy use of work trees.swyx: But like even then, like I just did a, dropped a podcast yesterday with Cursors saying, and they said they're getting rid of work trees ‘cause it still has too many merge conflicts.It's still un too un unintuitive. But go ahead.Ryan Lopopolo: The models are really great at resolving merge conflicts. Yeah. And to get to a state where I'm not synchronously in the loop in my terminal, I almost don't care that there are mergeswyx: with disposable.[00:23:00] Yeah.Ryan Lopopolo: We invoke a dollar land skill and that coaches codex to push the PR Wait for human and agent reviewers Wait for CI to be green.Fix the flakes if there are any merged upstream. If the PR comes into conflict, wait for everything to pass. Put it in the merge queue. Deal with flakes until it's in Maine. End. This is what it means to delegate fully, right? This is in a, very large model re probably a significant tax on humans to get PRS merged, but the agent is more than capable of doing this and I really don't have to think about it other than keep my laptop open.swyx: Yeah. I used to be much more of a control freak, but now I'm like, yeah, actually you could do a better job of this than me. Yeah. With the right context. Yes.[00:23:47] Encoding Requirementsswyx: Anything else in harness in general? Just this piece, I just wanna make sure we,Ryan Lopopolo: I think one thing that I maybe didn't make super clear in the article that I heard on Twitter as an interesting, that's respond [00:24:00]swyx: to them.What's the chatter and then what's your response?Ryan Lopopolo: Ultimately, all the things that we have encoded in docs and tests and review agents and all these things are ways to put all the non-functional requirements of building high scale, high quality, reliable software into a space that prompt injects the agent.We either write it down as docs, we add links where the error messages tell how to do the right thing. So the whole meta of the thing is to basically tease out of the heads of all the engineers on my team, what they think good looks like, what they would do by default, or what they would coach a new hire on the team to do to get things to merch.And that's why we pay attention to all the mistakes, mistakes that the agent makes, right? This is code being written that is misaligned with some as yet not written down, non-functional requirement.swyx: Sorry, what? Did the online people misunderstand orRyan Lopopolo: No,swyx: whatyouRyan Lopopolo: responded to? Somebody just literally said that.I was like, oh yeah,swyx: okay,Ryan Lopopolo: This is the [00:25:00] thing. This is what I've been doing. Oh, youswyx: agree? Yeah. I see. Interesting.Ryan Lopopolo: One other neat thing, which I did totally did not expect is folks were just. Taking the link to the article and giving it to pi or Codex and say, make my repo this,Vibhu: you achi a whole recursion.Ryan Lopopolo: And it was wildly effective. Really? It was wildly effective. NoVibhu: way. It just actually is something I tried with five, four yesterday. I didn't have time. Last time I was like out speaking of something, and this is one of my things, I was like, okay, I have this article. Can we just scaffold out what it would be like to run this?And I, I did it first as that and then I was like, okay, let me take another little side repo and say okay, if I was to fully automate this like this because I haven't written a line of code, it'sRyan Lopopolo: like over full, setVibhu: it right. The side thing I'm doing of voice. TTS I'm just like, slobbing out, whatever.It's nothing production. I'm like, how would I make this like this? And it's actually like a really good way. It's like a good way to learn what could be changed, what could be like, it's just a good analyzing, right? You give it all the codes, you give it all the context, you give it the article and it walks you through it very well.That's right. That's right.[00:25:57] Inlining Dependencies[00:25:57] Dependencies Going Away & Brett Taylor's Responseswyx: I guess one more thing before we go to Symphony is I wanted to cover [00:26:00] Brett Taylor's response. We had him on the show. He is your chairman, which is wild. Yeah. That he's reading your articles as well and like getting engaged in it. He says software dependencies are going away.Basically they can just be like vendored. Yes. Response.Ryan Lopopolo: Aswyx: hundred percent. A hundred percent agree. You still pro qr, you still pay Datadog. You still pay Temporal. Thank you.Ryan Lopopolo: Yep. The level of complexity of the dependencies that we can internalize is, I would say low, medium right now. Just based on model capability.What does the,swyx: what is medium?Ryan Lopopolo: I would say like a. A couple thousand line dependency is a thing that we could in-house No problem. Call in an afternoon of time. One neat thing about it is like probably most of that code you don't even need. Like by in-house and abstraction, you can strip away all the generic parts of it and only focus on what you need to enable the specific thing.Yes. You're building,swyx: I've been calling this the end of b******t plugins.Ryan Lopopolo: Yeah.swyx: Because there's so much when I published an open source thing, I want to accept everything, be liberal. I want to accept, this is post's law, but that means there's so much bloat. Yes. There's so much overhead.Ryan Lopopolo: One other neat thing about [00:27:00] this too is when we deploy Codex Security on the repo, it is able to deeply review and change. The internalized dependencies in a much lower friction way than it would be to like, push patches upstream, wait for them to be released, pull them down, make sure that's compatible with all the transitive I have in my repo and things like that.So it's also much lower friction to internalize some of these things if code is free. ‘cause the tokens are cheap sort of thing.swyx: Yeah. Yeah. I think like the only argument I have against this is basically scale testing, which obviously the larger pieces of software like Linux, MySQL, he calls up even the Datadog and Temporals and then maybe security testing where Yes.Classically, I think, is it linis tos, it said security open source is the best disinfectant.Ryan Lopopolo: Many eyes.swyx: Many eyes. And if inline your dependencies and code them up, you're gonna have to relearn mistakes from other people that Yep.Ryan Lopopolo: Yep. And to internalize that dependency, you're back to zero and you have to start.Reassembling all those bits and pieces to Yeah. Have [00:28:00] high confidence in the code as it is written. Yeah.Vibhu: Even part of the first intro of this, you basically mentioned like everything was written by codex, including internal tooling, right? So internal tooling, like when you're visualizing what's going on it's writing it for itself.swyx: Yeah. I'm built internal tools way I now, and like I just show them off and they're like, how long did you spend? And I didn't spend any time. I just prompted it,Ryan Lopopolo: very funny story here.swyx: Yeah, go ahead.Ryan Lopopolo: We had deployed our app to the first dozen users internally had some performance issues, so we asked them to export a trace for us get a tar ball, gave it to our on-call engineer, and he did a fantastic job of working with Codex to build this beautiful local Devrel tool, next JS app, the drag and drop the tar ball in, and it visualizes the entire trace.It's fantastic. Took an afternoon, but none of this was necessary. Because you could just spin up codex and give it the tar ball and ask the same thing and get the response immediately. So in a way, optimizing for human [00:29:00] legibility of that debugging process was wrong. It kept him in the loop unnecessarily when instead he could have just like Codex cooked for five minutes and gotten this same.swyx: Yeah, you verify your instincts here of this is how we used to do it. Or this is how I would have used to solve it.Ryan Lopopolo: Yeah. In this local observability stack. Like sure, you can de deploy Yeager to visualize the traces, but I wouldn't expect to be looking at the traces in the first place because I'm not gonna write the code to fix them.swyx: Yeah. So basically there needs to be like this kind of house stack and owning the whole loop. I think that is very well established. And it sounds like you might be like sharing more about that in the future, right?Ryan Lopopolo: Yeah. I think we're excited to do[00:29:36] Ghost Libraries Specs[00:29:36] Ghost Libraries & Distributing Software as SpecsRyan Lopopolo: We're gonna talk about Symphony in a little bit, but like the way we distribute it as a spec, which I think folks are calling Ghost Libraries on Twitter.This is like a such a cool name. It does mean it becomes much cheaper to share software with the world, right? You define a spec, how you could build your own specifying as much as is required for a coding agent to reassemble it [00:30:00] locally. The flow here is very cool. Like we have taken. All the scaffolding that has existed in our proprietary repo spun up a new one.Ask Codex with our repo as a reference. Write the spec. We tell it. Spin up a team ox spawn a disconnected codex to implement the spec. Wait for it to be done. Spawn another codex and another team ox to review the spec com or review the implementation compared to upstream and update the spec so it diverges less.And then you just loop over and over Ralph style until you get a spec that is with high fidelity able to reproduce the system as it is. It's fantastic.Vibhu: And you're basically, you're not really adding any of your human bias in there, right? That's correct. A lot of times people write a spec and be like, okay, I think it should be done this way, and you'll riff on something.And it's no, the agent could have just handled it like you're still scaffolding in a sense, right? I want it done this way. It can determine its spec better.swyx: That's right. That's right. Part of me it, I'm, I've been working a lot on evals recently, and part of me is wondering if [00:31:00] an agent can produce a spec that it cannot solve.Is it always capable of things that he can imagine or can you imagine things that it is impossible to do?Ryan Lopopolo: I think with Symphony, we, there's like this there's this axis where you have things that are easier, hard, or established or new, right? And I think things that are hard and new is still something that the models need humans.Yeah. Drive.swyx: Yeah. Yeah.Ryan Lopopolo: But I think those other quadrants are largely salt. Given the right scaffold and the right thing that's gonna drive the agent to completion,swyx: it's crazy that it solved,Ryan Lopopolo: but it means that the humans, the ones with limited time and attention get to work on the hardest stuff, like the problems where it's pure white space out in front. Or like the deepest refactorings where you don't know what the proper shape of the interfaces are. And this is where I wanna spend my time. ‘cause it lets me set up for the next level of scale.swyx: Yeah. Yeah. Amazing. Let's introduce Symphony.I think we've been mentioning it every now and then. Elixir. Interesting option.Ryan Lopopolo: Yeah.swyx: Yeah. I'm not,Ryan Lopopolo: again, like the [00:32:00] elixir manifestation here is just a derivative. Is it a modelswyx: chosen? Yeah.Ryan Lopopolo: Yeah. Yeah. And it chose that because the process supervision and the gen servers are super amenable to the type of process orchestration that we're doing here.You are essentially spinning up little Damons for every task that is in execution and driving it to completion, which. Means the mall gets a ton of stuff for free by using Elixir and the Beam.swyx: I had to go do a crash course in Beam and Elixir, and I think most people are not operating at that scale of concurrency where you need that.But it is a good mental model for Resum ability and all those things. And these are things I care about. But tell me the story, the origin story of Symphony. What do you use it for? Is this, how did it form maybe any abandoned paths that you didn't take?[00:32:46] Terminal Free Orchestration[00:32:46] Symphony: Removing Humans from the LoopRyan Lopopolo: At the end of December we were at about three and a half PRS per engineer per day.This was before five two came out in the beginning of January. Everyone gets back from holiday with five two and no other work [00:33:00] on the repository. We were up in the five to 10 PRS per day per engineer. And I don't know about y'all, but like it's very taxing to constantly be switching like that. Like I was pretty tapped out at the end of the day, again, where are the humans spending their time? They're spending their time context switching between all these active tmox pains to drive the agent forward.swyx: Yeah. No way. Yeah.Ryan Lopopolo: So let's again, build something to remove ourselves from the loop. And this is what frantic sprinted adapt here to find a way to remove the need for the human to sit in front of their terminal.So a lot of experimentation with Devrel boxes and, automatically spinning up agents, like it seems like a fantastic end state here, where my life is beach. I open live twice a day and say yes no to these things. Yeah. And this is again, a super, super interesting framing for how the work is done.Because I become more latency and sensitive. I have [00:34:00] way less attachment to the code as it is written. Like I've had close to zero investment in the actual authorship experience. So if it's garbage. I can just throw it away and not care too much about it. In Symphony, there's this like rework state where once the PR is proposed and it's escalated to the human for review, it should be a cheap review.It is either mergeable or it is not. And if it's not, you move it to rework. The elixir service will completely trash the entire work tree NPR and start it again from scratch. Okay. And this is that opportunity again to say, why was it trash right? What did the agent do that wasswyx: bad. Yeah.Ryan Lopopolo: Fix that before moving the ticket toswyx: endRyan Lopopolo: of progress again.swyx: Yeah. Why is this not in codex app? I guess this, you guys are ahead of Codex app,Ryan Lopopolo: yeah, so the way the team has been working is basically to be as AI pilled as possible and spread ahead. And a lot of the things we have worked on have fallen out [00:35:00] into a lot of the products that we have.Like we were in deep consultation with the Codex team to. Have the Codex app be a thing that exists, right? To have skills be a thing that Codex is able to use. So we didn't have to roll our own to put automations into the product. So all of our automatic refactoring agents didn't have to be these hand rolled control loops.It has been really fantastic to be, in a way, un anchored to the product development of Frontier and Codex and just very quickly try to figure out what works and then later find the scalable thing that can be deployed widely. It's been a very fun way to operate. It's certainly chaotic. I have lost track very often of what the actual state of the code looks like.‘cause I'm not in the loop. There was. One point where we had wired playwright directly up to the Electron app. With MCPM CCPs, I'm pretty bearish on because the harness forcibly injects all those tokens in the [00:36:00] context, and I don't really get a say over it. They mess with auto compaction. The agent can forget how to use the tool.There's probably only what three calls in playwright that I actually ever want to use. So I pay the cost for a ton of things. Somebody vibed a local Damon that boots playwright and exposes a tiny little shim CLI to drive it. And I had zero idea that this had occurred because to me, I run Codex and it's able to, it's oh, it's better.Yeah. Like no knowledge of this at all. Uhhuh.[00:36:30] Multi Human ChaosRyan Lopopolo: So we have had like in human space to spend a lot of time doing synchronous knowledge sharing. We have a daily standup that's 45 minutes long because we almost have to. Fan out the understanding of the current state.swyx: Yeah, I was gonna say this is good for a single human multi-agent, but multi human, multi-agent is a whole like po like explosion of stuff.Ryan Lopopolo: Yeah. And that this is fundamentally why we have such a rigid, like 10,000 [00:37:00] engineer level architecture in the app because we have to find ways to carve up the space so people are not trampling on each other.swyx: Sorry, I don't get the 10,000 thing. Did I miss that?Ryan Lopopolo: The structure of the repository is like 500 NPM packages.It's like architecture to the excess for what you would consider, I think normal for a seven person team. But if every person is actually like 10 to 50. Then the like numbers on being super, super deep into decomposition and sharding and like proper interface boundaries make a lot more sense.swyx: Yeah. To me, that's why I talked about Microfund ends and I, an anex is from that world, but Cool. It is just coming back to, to, to this I dunno if you have other, thoughts on. Orchestrating so much work coin going through this. Is this enough? Is this like any aha moments?Vibhu: It'll be interesting to see like where, okay, so right now you pick linear as your issue tracker, right?swyx: Or it's like a is it actually linear? This is actually linear.[00:37:55] Linear vs Slack WorkflowVibhu: Oh, that's linear. It's linear.swyx: Oh I never looked atVibhu: video. The demo video I had to download to [00:38:00] run.swyx: So I, because I'm a Slack maxie, but Yeah, linear. Linear is also really good. Yes,Ryan Lopopolo: we do make a good use of Slack. We we fire off codex to do all these lotion, elasticity, fix ups, the things that like sync that knowledge into the repository.It's super cheap. Yeah.swyx: Yeah.Ryan Lopopolo: Just do it in Codex.swyx: My biggest plug is OpenAI needs to build Slack. You need to own Slack. Build yours. Turn this into Slack.Ryan Lopopolo: I did read about it. Youswyx: did?Ryan Lopopolo: Yeah.[00:38:25] Collaboration Tools for AgentsRyan Lopopolo: I would say that if we think that we want these agents to do economically valuable work, which is like this is the mission, right?We want AI to be deployed widely, to do economically valuable work, then we need to find ways for them to naturally collaborate with humans, which means collaboration tooling, I think, is an interesting space to explore.swyx: Yeah, totally. Yeah. GitHub, slack, linear.Vibhu: Yeah, that was my thing. Okay, where do we see right now Codex has started Codex Model, then CLI, now there's an app, app can let me shoot off multiple Codex is in parallel, but there's no great team collaboration for Codex.And it [00:39:00] seems like your team had some say into what comes out, right? So you talked to ‘em, codex kind of was a thing. From there, if you guys are on the bound, what stuff that like, you might not focus on, but what do you expect other people to be building, right? So people that are like five x 50 Xing.Should you build stuff that's like very niche for your workflow, for your team? Should it be more general so other people can adopt? Is there a niche there? ‘Cause part of it is just okay, is everything just internal tooling? Do we have everything our own way? Like the way our team operates has our own ways that we like to communicate or is there a broader way to do it?Is it something like a issue tracker? Just thoughts if you wanna riff on that.[00:39:35] Standardizing Skills and CodeRyan Lopopolo: I think TBD we have not figured this out in a general way. I do think that there is leverage to be had in making the code and the processes as much the same as possible. If you think that code is context, code is prompts, it's better from the agent behavior perspective to be able to look in a package in directory X, Y, Z, and it not to have to page so [00:40:00] deeply into directory if you C, because they have the same structure, use the same language, they have the same patterns internally.And that same like leverage comes from aligning on a single set of skills that you're pouring every engineer's taste into to make sure that the agent is effective. So like in our code base, we have, I think, six skills. That's it. And if some part of the software development loop is not being covered, our first attempt is to encode it in one of the existing setup skills, which means that we can change the agent behavior.Yeah. More cheaply than changing the human driver behavior.swyx: Yeah.[00:40:39] Self Improvement via Logsswyx: Have you ever, have you experimented with agents changing their own behavior?Ryan Lopopolo: We do.swyx: Yeah. Or parent agent changing a subagents, behavior or something like that.Ryan Lopopolo: We have some bits for skill distillation. So for example, there's one neat thing you can do with Codex, which is just point it at its own session logs to ask it to tell you how you can use [00:41:00] the tool pedal better.swyx: It's like introspectionRyan Lopopolo: or ask it to do things. I useVibhu: this session better. What skills should Iswyx: high? I like the modification of, you can do, just do things to you can just ask agent to do things.Ryan Lopopolo: Yeah. You can just codex things. This is like a, this is like a silly emoji that we have, right? You can just codex things, you can just prompt things.It's really glorious future we live in, but okay, you can do that one-on-one. But we're actually slurping these up for the entire team into blob storage and. Running agent loops over them every day to figure out where as a team can we do better and how do we reflect that back into the repositories?Yes, though everybody benefits from everybody else's behavior for free. Same for like PR comments, right? These are all feedback. That means the code as written, deviated from what was good, a PR comment, a failed build. These are all signals that mean at some point the agent was missing context. We gotta figure out how toswyx: Yeah.Ryan Lopopolo: Slurp it up and put it back in the reboot.swyx: By the way, I do this exactly right. I used to, when I use cloud code for [00:42:00] knowledge work, cloud cowork is like a nice product, right? Yes. In I think you would agree. I always have it tell me what do I do better next time? And that's the meta programming reflection thing.So I almost think like you have six reflection extraction levels in symphony and almost like the zero of layer. So the six levels are PO policy, configuration, coordination, execution, integration, observability. We've talked about a couple of these, but the zero layer is like the, okay, are we working well?Can we improve how we work? Yes. Can I modify my own workflow without MD or something? I don't know.Ryan Lopopolo: Yeah, of course. Yeah, of course you can. Like this thing is also able to cut its own tickets ‘cause we give it full access.Yeah. Make it a ticket to have it cut. Tickets you can.Put in the ticket that you expect it to file as on follow up work,swyx: like Yeah. Self-modifying. Yeah.Ryan Lopopolo: Yeah.[00:42:44] Tool Access and CLI FirstRyan Lopopolo: Put, don't put the agent in a box. Give the agent full accessibility over it. Domain.swyx: I had a mental reaction when you said don't put the agent in a box. So I think you should put it in a box. Like it's just that you're giving the box everything it needs.Ryan Lopopolo: Yeah. Context and tools.swyx: But we're like, as developers, we're used to calling [00:43:00] out to different systems, but here you use the open source things like the Prometheus, whatever, and you run it locally so that you can have the full loop. I assume.Ryan Lopopolo: Yep.Vibhu: I think likeRyan Lopopolo: another, you wanna minimize cloud, cloud dependencies.Vibhu: You also want to make sure that you think about what the agent has access to. What does it see? Does it go back into the loop, like from the most basic sense of you let it see its own like calls, traces it can determine where it went wrong. But are you feeding that back in? So you know, just the most basic level of you wanna see exactly what's input output, like does the agent have access to.What is being outputted, right? It can self-improve a lot of these things. It's allRyan Lopopolo: text, right? My job is to figure out ways to funnel text from one agent to the other.swyx: It's so strange like way back at the start of this whole AI wave Andre was like, English is the hottest day programming language.It's here, it's just Yeah. The feature as well.Vibhu: A lot of, okay. Like a lot of software, a lot of stuff. There's a gui, it's made for the human. We're seeing the evolution of CLI for everything, right? All tools have CLIs. Your agents can use [00:44:00] them well, do we get good vision? Do we get good little sandboxes?Like right now? It's a really effective way, right? Models love to use tools. They love the best. They love to read through text. So slap a CLI let it go loose. That works for everything.Ryan Lopopolo: It does. Yeah. Yeah.[00:44:14] UI Perception and RasterizingRyan Lopopolo: We've also been adapting nont, textual things to that shape in order to improve model behavior in some ways, right?We want the agent to be able to see the UI agents do not perceive visually in the same way that we do. They don't see a red box, they see red box button, right? They see these things in latent space. So if we want, Hey, yeah, I do. We haveswyx: a ding if that goes off every time. Alien spaceRyan Lopopolo: ding.Anyway if we wanna actually make it see the layout, it's almost easier to rasterize that image to ask EOR and feed it in to the agent. Ha. And there's no reason you can't do both, right? To like further refine how the model perceives the object it's [00:45:00] manipulating.swyx: Cool. Could we, you wanna talk about a couple more of these layers that might bear more introspection or that you have personal passion for?[00:45:07] Coordination Layer with ElixirRyan Lopopolo: I will say that the coordination layer here was a really tricky piece to get right.swyx: Let's do it. Yep. I'm all about that. And this is Temporal core.Ryan Lopopolo: This is where when we turn the spec into Elixir, where like the model takes a shortcut, right? Like it's oh, I have all these primitives that I can make use of in this lovely runtime that has native process supervision.Which is I think, a neat way to have taken the spec and made it more choices achievable by making choices that naturally mapswyx: Yeah.Ryan Lopopolo: To the domain, right? In the same way that like you would prefer to have a TypeScript model repo if you are doing full stack web development, right? Because the ability to share types across the front end and backend reduces a lot of complexity.And becauseswyx: that's what graph kill used to be.Ryan Lopopolo: That's right. Andswyx: I don't know if it's still alive, butRyan Lopopolo: [00:46:00] no humans in the loop here. So like my own personal ability to write or not write elixir. Doesn't really have to bias us away from using the right tool for the job. It is just wild.swyx: Love it. I love it.Yeah. I wonder if any languages struggle more than others because of this? I feel like everyone has their own abstractions. That would make sense. But maybe it might be slower, it might be more faulty where like you'd have to just kick the server every now and then. I, I don't know. I think observability layer is really well understood.Integration layer, CP is dead. I think all these just like a really interesting hierarchy to travel up and down. It's common language for people working on the system to understandRyan Lopopolo: The policy stuff is really cool, right? Yeah. You don't really have to build a bunch of code to make sure the system wait for the, to passswyx: it's institutional knowledge.Ryan Lopopolo: Yeah. You just give it the G-H-C-L-I with some text that say CI has to pass. It makes the maintenance of these systems a lot easier.[00:46:57] Agent Friendly CLI Outputswyx: Do you think that CLI maintainers need to be [00:47:00] do anything special for agents or just as is? It's good because like I don't think when people made the G GitHub, CLI, they anticipated this happening.Ryan Lopopolo: That's correct. The GH CLI is fantastic. It's great super industry.swyx: Everyone go try GH repo create GH pull and then pull request number, right? GH HPR, like 1 53, whatever. And then it like pullsRyan Lopopolo: basically my only interaction with the GitHub web UI at this point is GH PR view dash web.Exactly. Glanceswyx: at the diffRyan Lopopolo: and be like Sure thing. Send it. Yeah. But the CLI are nice ‘cause they're super token efficient and they can be made more token efficient really easily. Like I'm sure you all have seen like I go to build Kite or Jenkins and I could just get this massive wall of build output.And in order to unblock the humans, your developer productivity team is almost certainly gonna write some code that parses the actual exception out of the build logs and sticks it in a sticky note at the top of the page. And you basically [00:48:00] want CLI to be structured in a similar way, right? You're gonna want to patch dash silent to prettier because the agent doesn't care that every file was already formatted.Just wants to know it's either formatted or not. So it can then go run a right command. Similarly, like in our PNPM distributed script runner, when we had one, when you do dash recursive, like it produces a absolute mountain of text. But all of that is for passing. Test suites. So we ended up wrapping all of this in another scriptswyx: to suppress the,Ryan Lopopolo: which you can vibe the channel only output the failing parts of the tests.swyx: You make a pipe errors versus the standard, standard out. I don't know. Okay. Whatever. Too much thinking have to do that. The CII used to maintain SCLI for my company and yeah, this is like core, very core to my heart. But you're vibing my job.Ryan Lopopolo: That's right.swyx: Cool. Any other things?This is a long spec. [00:49:00] I appreciate that. It's got a lot of strong opinions in here. Any other things that we should highlight? I think obviously you can spend the whole day going through some of these, but I do think that some of these have a lot of care or some of this you might wanna tell people, Hey, take this, but, make it your own.[00:49:15] Blueprint Spec and GuardrailsRyan Lopopolo: Fundamentally, software is made more flexible when it's able to adapt to the environment in which it is deployed, which means that things like linear or GitHub even are specified within the spec, but not required pieces of it. There's like a more platonic ideal of the thing that you could swap in like Jira or Bitbucket, for example.But being able to tightly specify things like the ID formats or how the Ralph Loop works for the individual agents. Basically means you can get up and running with a fully specified system quickly that you then evolve later on. I think we never intended for this to be a static spec that you can [00:50:00] never change.It's more like a blueprint to get something worth a starting point up and running.swyx: Yeah.Ryan Lopopolo: For you then to vibe later to your heart's content,swyx: you have like code and scripts in here where it's oh, I think this is a really good prompt. It's just a very long prompt.Ryan Lopopolo: Fundamentally, the agents are good at following instructions, so give them instructions.And it will, improve the reliability of the result. We, much like the way we use Symphony, we don't want folks to have to monitor the agent as it is vibing the system into existence. So being very opinionatedVery strict around what these success criteria are means that our deployment success rate goes up. Yeah. It means we don't have to get tickets on this thing.Vibhu: Think it all goes back to that like code to disposable, right? Like early on when you had CLI or you'd kick off a Codex run, it would take two hours. You would wanna monitor okay, I'm in the workflow of just using one.I don't want it to go down the wrong path. I'll cut it off and, just shoot off four, like that was my favorite thing of the Codex app, right? Yeah. Just Forex it like, [00:51:00] it's okay. One of them will probably be right, one of them might be better. Stop overthinking it. Like my first example was probably like deep research.When you put out deep research and I'd ask it something like, I asked it something about LLM, it thought it was legal something and spent an hour, came back with a report completely off the rails. And I was like, okay, I gotta monitor this thing a bit. No don't monitor it. Just you want to build it so it's that it, it goes the right way.And you don't wanna, you don't wanna sit there and babysit, right? You don't want to babysit your agentsRyan Lopopolo: with that deep research query that you made. Looking at the bad result, you probably figured out you needed to tweak your prompt Yeah. A bit, right? That's that guardrail that you fed back into the code base for the task, your prompt to further align the agent's execution.Same sort of concept supply there too.swyx: When you talk, how are the customers feelingRyan Lopopolo: for Symphony? I think we have none, right? This is a thing we have put out into theswyx: world. Symphony's internal, right? As long as you are happy, you are the customer. That'
Journey with St. Basil this Lent through the Stations of the Cross as we contemplate through imaginative prayer the Stations of the Cross. As we walk alongside those that were in and around Jesus during His final walk to Calvary, we will learn to pray with them in a new way, and bring that prayer into our lives. Come, follow us: Parish Website | Facebook | Instagram | YouTube | Spotify Music
Cari and Randi pray with the fourteenth station, Jesus is laid in the tomb. Journey with St. Basil this Lent through the Stations of the Cross as we contemplate through imaginative prayer the Stations of the Cross. As we walk alongside those that were in and around Jesus during His final walk to Calvary, we will learn to pray with them in a new way, and bring that prayer into our lives. Episodes will release Wednesdays and Fridays during Lent. You can find them wherever you listen to podcasts, or on our YouTube Channel / @stbasilthegr8 Come, follow us: Parish Website | Facebook | Instagram | YouTube | Spotify Music
On April 16, 1990, brothers Basil (8) and Jamal (7) Abdul'Faruq were dropped off at their mother's apartment in Richmond, Virginia. Around 2:30 p.m. they went outside to play while their mother slept after a night shift. When she woke and couldn't find them, she looked for 45 minutes before calling the police. A search of the apartment complex and nearby woods found nothing. Three days later, on April 19, a worker at the Shoosmith landfill in Chesterfield County found a body. One child is deceased, the other is still missing. No suspects have been publicly named, and no arrests have been made. The case is active and unsolved in both Richmond and Chesterfield County. Investigators have not determined who took the boys, how they were transported, or why one boy was killed and the other kidnapped but they believe it's possible the other brother is still alive… Click here to join our Patreon. Click here to get your own Inhuman merch. Connect with us on Instagram and join our Facebook group. To submit listener stories or case suggestions, and to see all sources for this episode: https://www.inhumanpodcast.com/ Learn more about your ad choices. Visit megaphone.fm/adchoices