Podcasts about Kite

Fluent Fiction - Mandarin Chinese: Soaring Dreams: A Kite's Journey at the Great Wall Festival Find the full episode transcript, vocabulary words, and more:fluentfiction.com/zh/episode/2026-06-15-22-34-01-zh Story Transcript:Zh: 龙舟节这一天，长城上阳光明媚，风景如画。En: On the day of the Dragon Boat Festival, the Great Wall basked in bright sunshine, offering picturesque scenery.Zh: 人们聚集在一起，庆祝这个快乐的节日。En: People gathered together to celebrate this joyous holiday.Zh: 李伟站在城墙脚下，抬头看着这段古老的长城。En: Li Wei stood at the foot of the Great Wall, looking up at this ancient structure.Zh: 今天是他再次证明自己的日子。En: Today was his day to prove himself once again.Zh: 他要在这里放飞一只巨大的风筝。En: He planned to fly a gigantic kite here.Zh: 李伟是一位热爱风筝的年轻人。En: Li Wei was a young man who loved kites.Zh: 每年他都参加风筝节，今年，他带来了他最大的创作。En: Every year he participated in the kite festival, and this year, he had brought his largest creation.Zh: 然而，这个风筝实在是太大了。En: However, this kite was truly enormous.Zh: 张明看着这庞然大物，忍不住皱眉，“李伟，这怎么能带上去呢？”En: Zhang Ming looked at the gigantic object and couldn't help but frown, "How can this be taken up there, Li Wei?"Zh: 陈秀笑着拍拍李伟的背，“要不我们帮你吧，分成几部分，搬上去？”En: Chen Xiu smiled and patted Li Wei on the back, "How about we help you? We can divide it into parts and carry it up."Zh: 李伟一边擦汗，一边点头，“好主意，分开来我们一起搬。”En: Li Wei wiped his sweat and nodded, "Good idea, let's separate it and carry it up together."Zh: 于是在朋友的帮助下，他们小心翼翼地把风筝分解成几个部分开始往上搬。En: With the help of his friends, they carefully disassembled the kite into several parts and began to carry it upwards.Zh: 长城的台阶陡峭，太阳晒得他们汗流浃背。En: The steps of the Great Wall were steep, and the sun made them sweat profusely.Zh: 张明时不时停下来喘气，陈秀用手巾抹去额头上的汗水，而李伟则紧紧盯着越来越接近的顶端，“加油，我们快到了！”En: Zhang Ming paused occasionally to catch his breath, Chen Xiu wiped the sweat from her forehead with a handkerchief, while Li Wei kept his eyes fixed on the increasingly close top, "Come on, we're almost there!"Zh: 终于，他们站在长城的顶端，俯瞰着下方的群山与人群。En: Finally, they stood at the top of the Great Wall, overlooking the mountains and the crowd below.Zh: 李伟迫不及待地开始组装他的风筝。En: Li Wei couldn't wait to start assembling his kite.Zh: 张明和陈秀忙着把风筝的骨架架起来，忽然一阵大风吹来，风筝险些被吹跑。En: Zhang Ming and Chen Xiu busied themselves with setting up the frame of the kite, when suddenly a strong gust of wind nearly blew the kite away.Zh: “不好，快抓住它！”李伟大喊。En: "Oh no, grab it quickly!" Li Wei shouted.Zh: 陈秀和张明迅速反应，三个人合力才稳住了风筝。En: Chen Xiu and Zhang Ming reacted swiftly, and together the three of them managed to stabilize the kite.Zh: 经过一番紧张的忙碌，风筝终于组装完毕。En: After a bout of tense busyness, the kite was finally assembled.Zh: 李伟深吸一口气，将风筝放飞。En: Li Wei took a deep breath and released the kite.Zh: 巨大的风筝在空中展开，五彩斑斓，十分壮观。En: The gigantic kite unfolded in the air, beautifully colorful and spectacular.Zh: 周围的人群纷纷拍手叫好。En: The surrounding crowd erupted into applause and cheers.Zh: 李伟看着在风中翱翔的风筝，心中充满了自豪与感激。En: Li Wei watched the kite soar in the wind, his heart filled with pride and gratitude.Zh: 他转过头，看着身边的朋友们，“谢谢你们，没有你们，我不可能做到。”En: He turned his head to look at his friends by his side, "Thank you all, I couldn't have done it without you."Zh: 这一次，李伟不仅实现了他的梦想，还明白了朋友和合作的意义。En: This time, Li Wei not only achieved his dream but also understood the importance of friendship and cooperation.Zh: 风筝在长城的蓝天中飞得更高，象征着他的友谊和新的理解。En: The kite flew higher in the blue sky above the Great Wall, symbolizing his friendship and newfound understanding. Vocabulary Words:bask: 晒picturesque: 如画ancient: 古老的gigantic: 巨大的enormous: 庞然大物frown: 皱眉disassembled: 分解profusely: 汗流浃背handkerchief: 手巾gust: 一阵大风swiftly: 迅速stabilize: 稳住tense: 紧张的assembled: 组装unfolded: 展开spectacular: 壮观applause: 拍手叫好gratitude: 感激friendship: 友谊cooperation: 合作structure: 城墙overlooking: 俯瞰achieved: 实现soar: 翱翔symbolizing: 象征着prove: 证明foot: 脚下steep: 陡峭sweat: 汗水erupted: 纷纷

June 10, 1752. Benjamin Franklin flies a kite during a thunderstorm to demonstrate a connection between lightning and electricity. This episode originally aired in 2025. Support the show! Join Into History for ad-free listening and more. History Daily is a co-production of Airship and Noiser.Go to HistoryDaily.com for more history, daily.

Back on this day in 1752, Benjamin Franklin flies a kite in a thunderstorm. Franklin did the stunt to see if a key attatched to the string would draw an electrical current. Some historians, however, don't believe this ever happened.

Boys of Dungeon Lane, McCartney's collaboration with producer Andrew Watt, arrived when McCartney was 83 and and he came out swinging: the opening track greets listeners with a dissonant, unresolved guitar chord that sets the album's tone. Harmonic instability runs through the entire record: chromatic mediants, deceptive cadences, and persistent pedal tones prevent even the most nostalgic songs from settling into comfort. The album's lyrics focus on McCartney's pre-Beatles Liverpool youth, territory unfamiliar even to long-time fans. The songs pay deliberate sonic tribute to specific Beatles recordings: Mellotron strings echoing "Strawberry Fields Forever," a backwards laugh tape loop answering "Tomorrow Never Knows," a first-ever McCartney/Starr vocal duet so close in timbre the two voices are nearly indistinguishable. Songs discussed:Paul McCartney – "Mull of Kintyre"Paul McCartney – "As You Lie There"The Beatles – "Blackbird"The Beatles – "Helter Skelter"The Beatles – "You Never Give Me Your Money"Paul McCartney – "Uncle Albert / Admiral Halsey"Paul McCartney – "Band on the Run"Paul McCartney – "Live and Let Die"Paul McCartney – "Mountaintop"The Beatles – "Being for the Benefit of Mr. Kite!"The Beatles – "For No One"The Beatles – "Because"The Beatles – "Lucy in the Sky with Diamonds"The Beatles – "Octopus's Garden"Paul McCartney – "Down South"The Beatles – "Two of Us"Paul McCartney – "We Two"The Beatles – "Strawberry Fields Forever"Paul McCartney – "Never Know Those"The Beatles – "Tomorrow Never Knows"Paul McCartney – "Salesman Saint"John Lennon – "Working Class Hero"John Cougar Mellencamp – "Small Town"Paul McCartney – “Home to Us” (with Ringo Starr)Paul McCartney – "The Days We Left Behind"The Beatles – "When I'm Sixty Four" Learn more about your ad choices. Visit podcastchoices.com/adchoices

For episode 742 of the BlockHash Podcast, host Brandon Zemp is joined by Chi Zhang, co-founder and CEO of Kite, which is building the base layer for the agentic internet. Her extensive background encompasses AI, big data, and product management.

It was likely this week in 1752 that Benjamin Franklin famously flew a kite in a thunderstorm. The story of this experiment has been changed and twisted over time, so we'll sort out facts from myth, and figure out why and how Franklin was doing what he was doing. Plus: today in 1961, the birthday of Michael J. Fox, whose acting career took off like lightning despite the best efforts of one of his early bosses. Benjamin Franklin flies kite during thunderstorm (History.com)Michael J Fox nearly lost a TV series because of a producer's strange belief (Virgin Radio)Our Patreon backers are key to our success

Joining the WOO Pro Team is Jett Bradshaw, a big air kiter from South Africa known for crazy kite angles with fearless aggression.Before jumping in, we catch up on this weekend's storylines in the UK, where the all-time highest jump record has been broken twice in a week.

Oggi ascoltiamo la storia di SABINA MINUTO, docente e formatrice. Sabina è andata in pensione da qualche mese, ma continua con passione ad insegnare, un'attività che ha praticato a lungo a Savona e che l'ha portata prima nelle scuole primarie e poi in quelle secondarie di secondo grado. Si occupa da tempo di metodologie didattiche, in particolare del metodo Writing and Reading Workshop. Attraverso questa metodologia si è imbattuta negli albi illustrati e da allora li utilizza costantemente nel suo lavoro per avvicinare i ragazzi alla lettura.  Quest'episodio appartiene ad una vera e propria rubrica del podcast che possiamo intitolare “L'ALTRO ILLUSTRATO” ed è nata parlando con Valentina Mai di Kite Edizioni, che da tempo dedica spazio e attenzione a esplorare l'albo illustrato in contesti anche diversi da quelli dell'infanzia, a cui tipicamente appartiene. Si parlerà de “L'Altro illustrato” anche ad “Autori in città”, l'evento che KITE edizioni organizza ogni anno a Padova, e che quest'anno si terrà dal 10 al 13 Settembre. Un appuntamento immancabile per chi è interessato alla letteratura illustrata e ai suoi autori. Questo è un podcast indipendente. Clicca i link qui di seguito per: Diventare un PATREON de "Il Mondo Invisibile" e sostenere questo podcast con un piccolo contributo per coprire le spese di produzione ed aiutarmi a continuare questo progetto;Ricevere la NEWSLETTER de “Il Mondo Invisibile” su Substack;Ascoltare il podcast anche su YOUTUBE;Seguire l'account Instagram @ilmondoinvisibilepodcast e la pagina facebook, per vedere le opere degli artisti, e per mandarmi i tuoi commenti.Grazie milleA presto! Alessandro#sabrinaminuto #kiteedizioni. #laltroillustrato #arte #illustratori #illustratore #illustrazioni #illustrazione #alboillustrato #picturebook  #immagini #ilmondoinvisibile #ilmondoinvisibilepodcast #podcastitaliani  

Today's poem is The Burning Kite by Ouyang Jianghe, translated by Austin Woerner. The Slowdown is your daily poetry ritual. In this episode, Maggie writes… “Every once in a while, a poem comes along with imagery so startling, phrasing so original, I have to read it several times in a row to be sure I'm taking it all in. Today's poem is one of them.” This show is supported by gifts from listeners. Support The Slowdown with a donation and get access to the sponsor-free version of The Slowdown today. Slowdownshow.org/donate

Įsilaužėliams pavogus šimtus tūkstančių gyventojų registrų duomenų, krašto apsaugos ministras Robertas Kaunas kritikuoja Registrų centro darbą užkardant saugumo spragas. Seimo opozicija kelia dviejų ministrų ir premjerės atsakomybės klausimą, neatmeta ir interpeliacijų galimybės. Tuo metu gyventojams tikrinant, ar pavogti jų duomenys, ėmė strigti Registrų centro svetainė.Šia tema – duomenų apsaugos ekspertė, advokatė Asta Macijauskienė.

The annual Dark Nation Radio GOTHIC BEACH PARTY broadcast can now be streamed! Memorial Day weekend is considered the “unofficial start of summer” in the US and, to mark the occasion, I'm pleased to present my friskiest show of the year—I throw out all the rules for this one to bring you an eclectic mix of rockabilly, electronica, New Wave, punk, and, of course, satanic doo-wop. Anything goes as long as its devilishly fun—I mean, where else are you going to find a show that includes Evil Elvis, Red Elvises, Dead Elvi, and Dread Zeppelin? Also in the mix this year are My Life with the Thrill Kill Kult, Wanda Jackson, The Clash, Laibach (!), Twin Temple, Santigold, The Ramones, Genesis Owusu, and, of course, The Cramps—plus a lot more. The show pairs well with evil tiki drinks and cursed idols, so pass the moon-tan lotion and turn it! DJ cypher's Dark Nation Radio Playlist 24 May 2026 GOTHIC BEACH PARTY 2026 HorrorPops, “Horror Beach” The Cramps, “Aloha from Hell” My Life w/ the Thrill Kill Kult, “Hit & Run Holiday” Kat Robichaud, “Break My Heart” Klack, “Good Luck Babe (1982 Cassette version)” Diechotomy, “Blood Beach” Wanda Jackson, “Shakin' All Over” Tiger Army, “The Devil That You Don't Know” Karen O, “Love is Strange” Genesis Owusu, “Leaving the Light” The Clash, “London's Burning” Mister Monster, “Science Fiction Double Feature” The Interrupters, “Broken World” The B-52s, “Private Idaho” Flesh for Lulu, “Sleeping Dogs” Teddybears, “Punk Rocker” The Brick Bats, “Na Na Na Na (The Creature)” Dead Elvi, “The Creature Stole My Surfboard” Red Elvises, “I Wanna See You Bellydance” Evil Elvis, “I Wanna Wed (the Undead)” Dead Elvis + Thee Gravemen, “Munster Boogie Woogie” Dread Zeppelin, “Whole Lotta Love” Twin Temple, “Let's Have a Satanic Orgy” Imelda May, “It's Your Voodoo Working” Devil Doll, “Liquor Store” The Creepshow, “Cherry Hill” Voltaire, “Captains All” The Ramones, “Rockaway Beach” Emi Pop, “Amigos Vampiros” Meat Loaf / Rocky Horror, “Hot Patootie” Sweet, “Ballroom Blitz” The Young Werewolves, “Zombie Prom” The Tomb Tones, “Hex Girl” The Damned, “Black is the Night” Laibach, “Allgorythm” Chris Harms, “Lunamor” Volbeat, “Lola Montez” Tiffany Hadish, “Evil Queen” The Beastie Boys, “Shake Your Rump” THOT Squad, “Pound Cake” Tunde Adebimpe, “Magnetic” Book of Love, “Boy (Dave Audé remix)” Kite, “Ways to Dance” The Cars, “You Might Think” Emilie Autumn, “Girls Just Wanna Have Fun” Cyndi Lauper, “I Drove All Night” The Rosedales, “Stars are Falling” The Hillbilly Moon Explosion, “1979” Santigold, “The Keepers” Social Distortion, “The Way Things Were” DJ CYPHER'S DARK NATION RADIO—25 years strong! **Live Sundays @ 9 PM Eastern US on Spirit of Resistance Radio sorradio.org **Recorded @ http://www.mixcloud.com/cypheractive **Downloadable @ http://www.hearthis.at/cypheractive **Questions and material for airplay consideration to darknationradio[at] gmail[dot]com **Facebook @ http://www.facebook.com/groups/darknationradio

Gina Kent is back on the show to continue our discussion about the magnificent Swallow-Tailed Kite. Gina is a senior scientist with the Avian Research and Conservation Institute in Gainesville, Florida. She is going to tell us all about the Eyes On Kites program and its efforts to document the nesting locations of Swallow-Tailed Kites throughout Florida, Georgia, and Alabama. Find out more by going to: www.arcinst.org. For the ARCI Eyes On Kites program, go to: https://www.arcinst.org/eyes-on-kites. For more info on the Swallow-Tailed Kite go to https://www.allaboutbirds.org/guide/Swallow-tailed_Kite/id#. Join Catherine Greenleaf, a certified wildlife rehabilitator with 25 years of experience rescuing and rehabilitating injured wildlife, for twice-monthly discussions about restoring native habitat and helping the birds in your backyard. Send your questions about birds and native gardening to birdhuggerpodcast@gmail.com. (PG-13) St. Dymphna Press, LLC.

In this episode of The Troubadour Podcast, hosts Jared Pete Gile and Carly Evans sit down for a candid, long-form conversation with Texas Red Dirt standout William Clark Green about his deeply personal seventh studio album, Watterson Hall. Released in March 2026 on Bill Grease Records and produced by Logan Wall, the 14-track record marks a mature evolution in Green's songwriting, drawing from his life as a husband and father while exploring themes of family, love, loss, and resilience across standout cuts like the title track "Watterson Hall (Me & You)," "Whole Lotta Lubbock," "Where The Wild Things Are," and "Stubborn and Remains."   Green opens up about stepping outside his usual lane, including powerful co-writes with Travis Meadows (notably on "Stubborn and Remains" and "I Am the Kite"), as well as collaborations with Gary Stanton, Sean McConnell, and others, plus the real-life dancehall inspiration behind the project's heartfelt core. The conversation also shines a light on Green's passion for giving back through Cotton Fest—the annual three-day country music festival he founded in Lubbock, Texas (taking place June 25-27, 2026 at Cook's Garage with a stacked lineup including Flatland Cavalry, 49 Winchester, Josh Abbott Band, and more)—and the High Cotton Relief Fund, the 501(c)(3) he helped establish in 2018 to support West Texas cotton farmers and their families facing hardships like medical bills, funeral costs, and farm needs. Listen now for an intimate look at one of Texas Country's most authentic voices.  Cotton Fest: https://www.cottonfestlbk.com/ High Cotton Relief Fund: https://www.highcottonrelief.org/ (or donate via Venmo: @highcottonrelief) ou can listen to all of our 200+ previous episodes by getting a  BACKSTAGE PASS by visiting our PATREON PAGE LINK https://www.patreon.com/bePatron?u=9861160&redirect_uri=https%3A%2F%2Fwww.thetroubadourpodcast.com%2Fsupport%2F&utm_medium=widget  GET HEALTHY WITH PETE LINK https://plexusworldwide.com/products?culture=en-US&sponsor=petegile  SWEETWATER AFFILIATE LINK  - Buy your gear using our affiliate link! https://www.sweetwater.com/?irclickid=zqw17qUMKxyNTm0SiXUTAXRYUkAzsJUCS0eM0I0&irgwc=1&utm_source=Impact&utm_medium=The%20Troubadour%20Podcast&utm_campaign=Online%20Tracking%20Link  

Fluent Fiction - Hungarian: Kite Tales: Friendship Soars Above Gellért-hegy Find the full episode transcript, vocabulary words, and more:fluentfiction.com/hu/episode/2026-05-17-22-34-01-hu Story Transcript:Hu: A tavasz napsütése fényesítette meg a Gellért-hegyet, virágok pompájával és a Duna ragyogásával.En: The spring sunshine brightened Gellért-hegy, with the splendor of flowers and the glitter of the Duna.Hu: István, egy vidám és kicsit ügyetlen férfi a harmincas évei közepén, fent állt a hegy tetején egy színes papírsárkánnyal a kezében.En: István, a cheerful and slightly clumsy man in his mid-thirties, stood at the top of the hill with a colorful kite in his hand.Hu: Szeme csillogott, ahogy a szép kilátást nézte, de szívében a gyermekkor örömét kereste.En: His eyes sparkled as he looked at the beautiful view, but in his heart, he was searching for the joy of childhood.Hu: „Repülj, kis barátom!En: "Fly, my little friend!"Hu: ” - suttogta a sárkánynak, ahogy a zsinórt kibontotta.En: he whispered to the kite as he released the string.Hu: De a sárkány nem repült.En: But the kite did not fly.Hu: Ehelyett újra és újra belegabalyodott a turisták szelfibotjaiba.En: Instead, it repeatedly tangled in the tourists' selfie sticks.Hu: István zavarba jött, de nem adta fel.En: István was embarrassed but didn't give up.Hu: „Ej, pajtás, hol van a lendület?En: "Oh, buddy, where's the momentum?"Hu: ” - kérdezte mosollyal a száján.En: he asked with a smile on his face.Hu: Majd úgy döntött, megkeresi a megfelelő helyet a dombon.En: Then he decided to find the right spot on the hill.Hu: A hegy tele volt látogatók hadával, mindannyian elmerülve a saját kis világukban, telefonokkal a kezükben.En: The hill was swarming with visitors, each absorbed in their own little world, phones in hand.Hu: István mélyet sóhajtott, mielőtt elindult volna egy nyugodtabb sarok keresésére.En: István sighed deeply before setting off to find a quieter corner.Hu: A szellő néha kuncogott a fák között, de kevés volt ahhoz, hogy a sárkány szárnyra kapjon.En: The breeze occasionally giggled among the trees, but it was too weak to lift the kite.Hu: Ekkor két idegen, Lajos és Katalin, figyelme István próbálkozására terelődött.En: Then two strangers, Lajos and Katalin, noticed István's efforts.Hu: Először csak nevetgéltek, de végül közelebb léptek.En: At first, they just chuckled, but eventually, they stepped closer.Hu: „Segíthetünk?En: "Can we help?"Hu: ” - kérdezte Katalin barátságos mosollyal.En: Katalin asked with a friendly smile.Hu: „Nagy szükségem volna rá” - vallotta be István egy kis mosollyal.En: "I could really use it," admitted István with a slight smile.Hu: „Talán együtt sikerülhet.En: "Maybe together we can succeed."Hu: ”Lajos bólogatott és segített Istvánnak egy kisebb, üres területet megtisztítani.En: Lajos nodded and helped István clear a smaller, empty area.Hu: Katalin bájos készséggel vezette el a szelfibotos turistákat egy másik irányba.En: Katalin charmingly guided the selfie-stick tourists in another direction.Hu: „Készen állunk?En: "Are we ready?"Hu: ” - kérdezte Lajos, ahogy mindannyian körbeálltak.En: asked Lajos as they all stood around.Hu: „Most vagy soha!En: "Now or never!"Hu: ” - István felemelte magasra a sárkányt, és bíztatóan nézett a többiekre.En: István lifted the kite high and looked encouragingly at the others.Hu: És akkor történt a csoda.En: And then the miracle happened.Hu: A szél erőre kapott, és a sárkány végre felszállt, magasan a város fölé.En: The wind gained strength, and the kite finally took off, soaring high above the city.Hu: István, Lajos és Katalin hangos nevetéssel ünnepeltek, miközben a színes sárkány büszkén táncolt az ég kékjében.En: István, Lajos, and Katalin celebrated with loud laughter as the colorful kite proudly danced in the blue sky.Hu: Aznap, ahogy a naplemente aranyfényével borította be a várost, István tudta, hogy a közös munka és a barátság milyen erővel bír.En: That day, as the sunset bathed the city in golden light, István knew the power of teamwork and friendship.Hu: Látta a sárkányt, ahogy a távolban táncol, és a szívében már nem csak egyedül volt, hanem új barátokkal osztozott az élményben.En: He saw the kite dancing in the distance, and in his heart, he was no longer alone; he shared the experience with new friends.Hu: Kézfogások és nevetések követték egymást, és István boldogabb nem is lehetett volna.En: Handshakes and laughter followed one another, and István couldn't have been happier.Hu: A Gellért-hegy felett az öröm szárnyra kelt.En: Above Gellért-hegy, joy took flight. Vocabulary Words:splendor: pompaglitter: ragyogáscheerful: vidámclumsy: ügyetlensparkled: csillogotttangled: belegabalyodottmomentum: lendületswarming: hadávalabsorbed: elmerülvesighed: sóhajtottgiggle: kuncogottchuckled: nevetgéltekmiracle: csodasoaring: felszálltcelebrated: ünnepeltekdanced: táncoltteamwork: közös munkafriendship: barátságbathed: borította beproudly: büszkénencouragingly: bíztatóansearching: kerestewhispered: suttogtareleased: kibontottaembarrassed: zavarba jöttclear: megtisztítaniguided: vezettegained: erőre kapottlaughter: nevetésekhandshakes: kézfogások

It's the first Major Pain of Season 10 of Where's That Bar Cart. But Nick is being grumpy about the PGA Championship happening in May, so he has something up his sleeve. Listen/Watch to our discussion on Guyanese golfers, and Snipes & Kite.Thanks to Comedy Records and to each and every one of you who listens, watches, and supports our podcast. Please subscribe to our YouTube channel @ComedyRecords. Also, head to foretra.com and use the promo code NICKDURIE for discounts on amazing golf gear. Swing well out there.Follow us at:- @wheresthatbarcart- linkt.ree/wheresthatbarcart- @dpurcomic- @montymofoscott- @nickdurie- @comedyrecordsMusic by Devin BatesonThank you to Comedy Records

This week: James Heale on Farage's plan to win the left-wing vote, Geoffrey Cain on Trump's visit to China, Rachel Johnson has lost her luggage and Melissa Kite wonders why the French love Cork. Become a Spectator subscriber today to access this podcast without adverts. Go to spectator.co.uk/adfree to find out more.For more Spectator podcasts, go to spectator.co.uk/podcasts.Contact us: podcast@spectator.co.uk Hosted on Acast. See acast.com/privacy for more information.

Fluent Fiction - Korean: Soaring Joy: A Family's Kite-Flying Adventure Find the full episode transcript, vocabulary words, and more:fluentfiction.com/ko/episode/2026-05-16-22-34-01-ko Story Transcript:Ko: 한강 공원은 붓다의 생일을 맞이하여 가족들로 북적였다.En: The Hangang Park was bustling with families celebrating Buddha's birthday.Ko: 초록빛 잔디밭과 부드러운 청색 강물의 어울림 속에 천천히 흩날리는 벚꽃이 분위기를 더했다.En: Cherry blossoms gently scattered amid the harmony of the green grass and the soft blue river added to the atmosphere.Ko: 진수는 오늘 하루가 가족에게 특별한 추억이 되기를 바라며, 가족과 함께 큰 용연을 만들었다.En: Jinsu hoped today would become a special memory for his family and made a large dragon kite with them.Ko: 그의 목표는 이 거대한 연을 성공적으로 날리는 것이었다.En: His goal was to successfully fly this giant kite.Ko: 진수는 자신감 있게 연을 들었다.En: Jinsu confidently held the kite.Ko: 그러나 첫 시도는 순조롭지 않았다.En: But his first attempt didn't go smoothly.Ko: 바람은 예기치 않게 불어왔고, 연은 지면에 자꾸 떨어졌다.En: An unexpected gust of wind blew, and the kite kept falling to the ground.Ko: 진수의 얼굴에는 약간의 당혹감이 스쳤다.En: A hint of embarrassment crossed Jinsu's face.Ko: 그는 강한 바람 속에서 연을 붙잡고 있는 자신의 모습을 상상했다.En: He imagined himself holding onto the kite amidst the strong wind.Ko: "진수야, 도와줄까?" 친절한 민지가 말했다.En: "Jinsu, do you want some help?" Minji, kindly offered.Ko: 진수는 조금 망설였지만, 고개를 끄덕였다.En: Jinsu hesitated a bit but then nodded.Ko: 민지는 차분하고 실용적인 성격이었다.En: Minji had a calm and practical nature.Ko: 그녀와 함께라면 해결책을 찾을 수 있을 것 같았다.En: He felt that with her, they could find a solution.Ko: 그때, 상호가 다가왔다.En: At that moment, Sangho approached.Ko: "두 분, 나도 도울게. 기술적으로 좀 계산해볼까?" 그는 이론적 접근으로 상황을 분석하기 시작했다.En: "You two, I can help too. Shall I calculate it technically?" He began analyzing the situation with a theoretical approach.Ko: 세 사람은 함께 연의 구조를 조금 수정했다.En: The three of them made slight modifications to the kite's structure together.Ko: 상호는 바람의 방향을 체크했고, 민지는 적당한 각도로 연을 들어 올렸다.En: Sangho checked the wind direction, and Minji lifted the kite at the right angle.Ko: 마침내, 연은 하늘을 향해 날아오르기 시작했다.En: Finally, the kite started to soar toward the sky.Ko: 진수는 기대감과 긴장 속에서 줄을 계속 잡고 있었다.En: Jinsu held onto the string with anticipation and tension.Ko: 하지만 바로 그 순간, 힘찬 돌풍이 연을 불어 날렸다.En: But just then, a strong gust blew the kite away.Ko: 진수는 줄에 매달린 채 소리쳤고, 온 가족은 깔깔거리며 이 광경을 지켜봤다.En: Jinsu, clinging to the string, shouted, and the whole family watched the scene with laughter.Ko: 연은 하늘을 유영하듯 춤추고, 진수는 필사적으로 균형을 맞추며 버텼다.En: The kite danced smoothly in the sky, and Jinsu desperately tried to balance and endure it.Ko: 결국, 연은 안전하게 내려왔고 진수는 땅에 주저앉았다.En: Eventually, the kite came down safely, and Jinsu sank to the ground.Ko: 가족들은 큰 소리로 웃으며 즐거워했다.En: The family laughed heartily, enjoying the moment.Ko: "진수야, 정말 대단했어!" 민지가 진수를 칭찬했다.En: "Jinsu, you were really amazing!" Minji praised Jinsu.Ko: 진수도 마침내 웃음을 터뜨렸다. 그제서야 그는 깨달았다. 작은 실수가 오히려 가족을 더 행복하게 만들었다는 것을.En: He finally burst into laughter, realizing that the small mishap actually made his family happier.Ko: 진수는 그 날의 기억이 오래오래 남을 것임을 알았다.En: Jinsu knew that the memory of that day would last a long time.Ko: 계획대로 되지 않아도 괜찮았다.En: It was okay if things didn't go as planned.Ko: 그런 예측하지 못한 순간들이 진정한 추억이 되었다.En: Those unexpected moments became the real memories.Ko: 이날의 교훈은 분명히 진수의 가슴에 새겨졌다. 완벽함보다 더 중요한 것은 가족과 함께한 따뜻한 순간들이라는 것을.En: The lesson of the day was clearly etched in Jinsu's heart—that warm moments spent with family are more important than perfection. Vocabulary Words:bustling: 북적였다celebrating: 맞이하여scattered: 흩날리는harmony: 어울림anticipation: 기대감tension: 긴장smoothly: 순조롭지gust: 돌풍embarrassment: 당혹감hesitated: 망설였지만practical: 실용적인approach: 접근modifications: 수정soar: 날아오르기blowing: 불어왔다balance: 균형endure: 버텼다sank: 주저앉았다heartily: 즐거워했다bursted into laughter: 웃음을 터뜨렸다mishap: 실수가etched: 새겨졌다perfection: 완벽함unplanned: 예측하지 못한solution: 해결책calm: 차분하고technical: 기술적으로structure: 구조direction: 방향을lifted: 들어 올렸다

Cheers to Spring Wines! Let's go Fly a Kite in Grand Haven and A Unique Culinary Getaway! ALL on this episode of "Things to Do, Places to Go" with Kathleen Schiefler from the West Michigan Tourist Association! WMTA.org.See omnystudio.com/listener for privacy information.

Hot To Go featuring Tiffany Haddish, Late Night Strike Force Five reunites for Colbert's send off and we reveal what might be the most amazing reality show ever coming next year. We play Over/Under and when was the last time you flew a kite? See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

A gentle and meaningful bedtime story for young listeners about a little red kite who dreams of flying high above the clouds. When she finally gets her wish, she discovers that freedom is not always happiness, and that being loved matters more than reaching the sky. A touching children's story with a thoughtful ending and an important life lesson about gratitude, belonging, and choosing what truly matters.

Improve your foiling skills in paradise! Join us in Montanita Ecuador May 23-30, 2026 for a foil drive / tow / prone foil camp with Ecuador Foil, KT Foiling & Julia Castro. Learn MoreOn this episode, Luc Moore sits down with Floris Dielen from the Waterspeed App team to break down the results of the massive Defi 2026 pre-event challenges. Fresh off closing the leaderboard for Defi Kite, Wing, Windsurf, and Foil, they reveal the yellow jersey winners, standout performances, and some wild stats from thousands of logged kilometers.Floris shares the top finishers across disciplines — including dominant runs from Leopold, Martyn, PierrotRapido, Jean Le Gall, Charly Djen, and more — while highlighting incredible dedication like PierrotRapido's 11-hour, 354 km wing session and multi-event warriors logging 19 sessions each. The duo also discusses the exciting new Waterspeed live tracking feature debuting at Defi Wing and Windsurf: real-time session mapping so friends and family can follow competitors from home.From fastest overall times and location breakdowns to the pure stoke and preparation heading into the main event in France, this episode is packed with results, behind-the-scenes nuggets, and practical info for anyone heading to Defi or following along.Episode Highlights:Full Defi Challenge winners across Kite, Wing, Windsurf & FoilRecord-breaking sessions: 11 hours / 354 km, 19 sessions logged, and the fastest single run of the competitionNew Waterspeed live tracking — follow athletes in real time on the big screen and onlineEvent logistics, yellow jersey stories, and what to expect at Defi 2026Tips for participants and how to join the fun at the Waterspeed boothWhether you're competing at Defi, cheering from home, or just love data-driven foiling/windsurf/kite stories, this episode delivers the latest results and serious inspiration ahead of one of the biggest events on the calendar.

A forcible reminder to me: DO NOT DESPISE THE DAY OF SMALL BEGINNINGS.

Improve your foiling skills in paradise! Join us in Montanita Ecuador May 23-30, 2026 for a foil drive / tow / prone foil camp with Ecuador Foil, KT Foiling & Julia Castro. Learn MoreOn this episode, Luc Moore sits down with Baris Soyogul of the Kite4Life Foundation to discuss his powerful journey through testicular cancer, the mental health spiral that followed treatment, and how discovering kitesurfing became his unexpected lifeline. What started as a couple's beginner lesson on Bonaire turned into a complete mindset reset — clearing fear, depression, and overthinking through pure presence on the water. Baris shares how this experience inspired him to found Kite4Life, a foundation that pairs cancer survivors and their “plus ones” with beginner kitesurfing and wing foiling lessons along the Dutch coast.Episode Highlights:The raw reality of a cancer diagnosis at 38, surgery, radiotherapy, and the hidden mental toll that almost ended everything.How one kite lesson created a three-hour “mental reset” — the first time in nearly a year Baris didn't think about cancer.Why wind sports (especially kitesurfing and wing foiling) are uniquely powerful for rebuilding mental health and presence.The birth of Kite for Life Foundation: pairing survivors with their support person for shared beginner lessons, community, and stoke.How the foundation works — online prep sessions, kickoff beach days, partnerships with 11 schools, commitment fees, and fundraising to make it accessible.Real impact: 750+ people introduced to kitesurfing, powerful stories of renewed hope, relationships strengthened, and new chapters started.The importance of “plus ones” — supporting not just the patient but the partners and family who carry the load too.Practical details on season structure, what participants can expect, and why even one session can be life-changing.Packed with honest emotion, practical insights, and genuine inspiration, this conversation shows how wind and water can heal in ways medicine alone cannot. Whether you're a cancer survivor, supporter, or simply someone who knows the transformative power of kite and wing sports, Baris's story is a reminder that one session on the water can shift everything.Tune in for a deeply moving episode about resilience, community, and paying it forward through the stoke of wind sports.Visit: kiteforlifefoundation.orgFollow on Instagram for more stories and ways to support. This episode is brought to you by Waterspeed. Download the app — live tracking, deep analytics, and community vibes for every watersport adventure! Available on Andriod and IOS

Good morning from Pharma Daily: the podcast that brings you the most important developments in the pharmaceutical and biotech world. The industry continues to evolve rapidly with significant developments in drug approvals, regulatory changes, and innovative therapies. The latest updates highlight the tension between scientific advancement and regulatory scrutiny. A prime example is the FDA's proposal to rescind approval of Amgen's Tavneos due to alleged data manipulation and safety concerns. This action underscores the critical importance of rigorous data integrity and post-market surveillance in drug development. In a win for AstraZeneca, their Breztri Aerosphere has gained FDA approval for asthma treatment, strengthening its status as a blockbuster drug following its success in treating chronic obstructive pulmonary disease (COPD). This approval marks a significant milestone in AstraZeneca's ambition to achieve $80 billion in revenue by 2030. The inhaler's three-in-one formulation addresses a substantial unmet need in asthma management, offering enhanced convenience and efficacy for patients. Meanwhile, Novartis remains confident in its $5 billion peak sales projection for Pluvicto, even as it faces European regulatory setbacks and competitive pressures from bispecific antibodies. This scenario highlights the strategic resilience required by pharmaceutical companies to navigate regulatory landscapes and maintain market confidence amid challenges. Rocket Pharmaceuticals recently made headlines by selling a priority review voucher for $180 million following the approval of its gene therapy Kresladi. Such transactions are crucial for companies aiming to accelerate market entry for novel therapies, particularly in competitive fields like gene therapy. On the horizon for Kite Pharma, a subsidiary of Gilead Sciences, is the advancement of its next-generation CAR-T cell therapy for multiple myeloma. After refining its manufacturing processes, Kite is prepared to leverage its expertise in cell therapy to address the evolving landscape of hematologic malignancies. The potential approval of this therapy represents a significant step forward in personalized medicine and cancer treatment. GSK's ongoing legal dispute with AnaptysBio over Jemperli royalties emphasizes the complex interplay between strategic partnerships and intellectual property rights within the industry. As companies increasingly rely on collaborations for innovation, resolving such disputes amicably remains crucial for sustaining long-term alliances. Positive trial outcomes with Rezzayo from Mundipharma and CorMedix underscore an expanding focus on antifungal therapies, particularly for vulnerable populations like stem cell transplant recipients. This development could lead to broader prophylactic options against invasive fungal infections, improving patient outcomes in immunocompromised settings. Beyond therapeutic advancements, Medtronic's successful containment of a cyberattack highlights the growing importance of cybersecurity measures in safeguarding sensitive data and maintaining operational integrity. This incident reinforces the need for robust IT infrastructure within healthcare organizations to prevent disruptions and protect patient safety. Looking forward, Artificial Intelligence (AI) integration into pharma operations is reshaping traditional models from task execution to outcome ownership. AI-driven approaches are enabling life sciences organizations to scale impact, enhance decision-making processes, and accelerate value creation across drug discovery and development pipelines. Eli Lilly's collaboration with Profluent marks a significant move in the genetic medicine landscape. This $2.2 billion partnership focuses on developing AI-designed recombinases, a novel approach to gene editing that holds promise for addressing diseases with severe unmet needs. Recombinase-based Support the show

High Timeline Living Website:https://www.hightimelineliving.com/Readings with Kristin Lawhead:https://kristiraeastrology.wixsite.com/blogReadings with Alisa Dixon: https://www.astrologywithalisa.com/Fun Astrology YouTube Channel:https://www.youtube.com/@funastrologypodcastBuy Thomas a Coffee!https://www.buymeacoffee.com/funastrologyThank you!Join the Fun Astrology Lucky Stars Club Here!Old Soul / New Soul Podcast - Back Episodes:https://www.buzzsprout.com/2190199https://www.youtube.com/@OldSoulNewSoulAstrologyPodcastDisclaimer: The material in this episode is intended as informational and educational purposes only from an astrological perspective and reflects only the opinions of the presenter. In no way is this podcast considered professional psychological or medical counseling or advice. If you are experiencing a personal crisis, please contact 988 for immediate professional, licensed assistance. 

This content has been developed for healthcare professionals only. Patients who seek health information should consult with their physician or relevant patient advocacy groups.For the full presentation, downloadable Practice Aids, slides, and complete CME/NCPD/AAPA information, and to apply for credit, please visit us at PeerView.com/NBP865. CME/NCPD/AAPA credit will be available until April 18, 2027.Sorting the Sequence in Multiple Myeloma: Personalized Choices With BCMA and Non-BCMA Immunotherapies in Relapsed/Refractory Disease In support of improving patient care, PVI, PeerView Institute for Medical Education, is jointly accredited by the Accreditation Council for Continuing Medical Education (ACCME), the Accreditation Council for Pharmacy Education (ACPE), and the American Nurses Credentialing Center (ANCC), to provide continuing education for the healthcare team.SupportThis activity is supported by independent educational grants from Arcellx, Inc. and Kite, a Gilead Company; AstraZeneca; Johnson & Johnson; and Legend Biotech.Disclosure information is available at the beginning of the video presentation.

This content has been developed for healthcare professionals only. Patients who seek health information should consult with their physician or relevant patient advocacy groups.For the full presentation, downloadable Practice Aids, slides, and complete CME/NCPD/AAPA information, and to apply for credit, please visit us at PeerView.com/NBP865. CME/NCPD/AAPA credit will be available until April 18, 2027.Sorting the Sequence in Multiple Myeloma: Personalized Choices With BCMA and Non-BCMA Immunotherapies in Relapsed/Refractory Disease In support of improving patient care, PVI, PeerView Institute for Medical Education, is jointly accredited by the Accreditation Council for Continuing Medical Education (ACCME), the Accreditation Council for Pharmacy Education (ACPE), and the American Nurses Credentialing Center (ANCC), to provide continuing education for the healthcare team.SupportThis activity is supported by independent educational grants from Arcellx, Inc. and Kite, a Gilead Company; AstraZeneca; Johnson & Johnson; and Legend Biotech.Disclosure information is available at the beginning of the video presentation.

This content has been developed for healthcare professionals only. Patients who seek health information should consult with their physician or relevant patient advocacy groups.For the full presentation, downloadable Practice Aids, slides, and complete CME/NCPD/AAPA information, and to apply for credit, please visit us at PeerView.com/NBP865. CME/NCPD/AAPA credit will be available until April 18, 2027.Sorting the Sequence in Multiple Myeloma: Personalized Choices With BCMA and Non-BCMA Immunotherapies in Relapsed/Refractory Disease In support of improving patient care, PVI, PeerView Institute for Medical Education, is jointly accredited by the Accreditation Council for Continuing Medical Education (ACCME), the Accreditation Council for Pharmacy Education (ACPE), and the American Nurses Credentialing Center (ANCC), to provide continuing education for the healthcare team.SupportThis activity is supported by independent educational grants from Arcellx, Inc. and Kite, a Gilead Company; AstraZeneca; Johnson & Johnson; and Legend Biotech.Disclosure information is available at the beginning of the video presentation.

This content has been developed for healthcare professionals only. Patients who seek health information should consult with their physician or relevant patient advocacy groups.For the full presentation, downloadable Practice Aids, slides, and complete CME/NCPD/AAPA information, and to apply for credit, please visit us at PeerView.com/NBP865. CME/NCPD/AAPA credit will be available until April 18, 2027.Sorting the Sequence in Multiple Myeloma: Personalized Choices With BCMA and Non-BCMA Immunotherapies in Relapsed/Refractory Disease In support of improving patient care, PVI, PeerView Institute for Medical Education, is jointly accredited by the Accreditation Council for Continuing Medical Education (ACCME), the Accreditation Council for Pharmacy Education (ACPE), and the American Nurses Credentialing Center (ANCC), to provide continuing education for the healthcare team.SupportThis activity is supported by independent educational grants from Arcellx, Inc. and Kite, a Gilead Company; AstraZeneca; Johnson & Johnson; and Legend Biotech.Disclosure information is available at the beginning of the video presentation.

This content has been developed for healthcare professionals only. Patients who seek health information should consult with their physician or relevant patient advocacy groups.For the full presentation, downloadable Practice Aids, slides, and complete CME/NCPD/AAPA information, and to apply for credit, please visit us at PeerView.com/NBP865. CME/NCPD/AAPA credit will be available until April 18, 2027.Sorting the Sequence in Multiple Myeloma: Personalized Choices With BCMA and Non-BCMA Immunotherapies in Relapsed/Refractory Disease In support of improving patient care, PVI, PeerView Institute for Medical Education, is jointly accredited by the Accreditation Council for Continuing Medical Education (ACCME), the Accreditation Council for Pharmacy Education (ACPE), and the American Nurses Credentialing Center (ANCC), to provide continuing education for the healthcare team.SupportThis activity is supported by independent educational grants from Arcellx, Inc. and Kite, a Gilead Company; AstraZeneca; Johnson & Johnson; and Legend Biotech.Disclosure information is available at the beginning of the video presentation.

Isabel finds her aunt's old kite and takes it to the hill behind her house. It flies, but not as high as it should. The bows on its tail keep getting heavier, and Isabel knows exactly why.A story about what weighs us down when we hold on to anger, and what it costs to let it go.Turn this episode into a Spanish lesson — for your family or yourself:✓ Mi Cuento ($5/mo) — One story a week plus transcript, translation, and vocab guide.Join on Patreon: patreon.com/spanishstoriesforkidsHave a story idea? Email us at: hello@spanishstoriesforkids.com_____Isabel encuentra la cometa vieja de su tía y la lleva a la colina detrás de su casa. Vuela, pero no tan alto como debería. Los lazos de la cola se ponen cada vez más pesados, y Isabel sabe exactamente por qué.Una historia sobre lo que nos pesa cuando guardamos el enojo, y lo que cuesta soltarlo.Convierte este episodio en una lección de español — para tu familia o para ti:✓ Mi Cuento ($5/mes) — Un cuento nuevo cada semana, más transcripción, traducción y guía de vocabulario.Únete en Patreon: patreon.com/spanishstoriesforkids¿Tienes una idea para un cuento? Escríbenos a: hello@spanishstoriesforkids.com

GET ACTIVE WITH THE SOUND OF NOW! LIKE, SUBCRIBE AND SHARE LEAVE A COMMENT LET US KNOW HOW YOU FEEL! Check us out on Instagram too: I Do It For HipHop_Podcast or On Facebook I Do It For HipHop Podcast find us on INSTAGRAM @gr8_pharaoh @mrcanilive @macbailey_ BE SURE TO VISIT PHARAOHSOLCOLLECTIVE.COM FOR PREMIUM ART AS WELL AS APPEAREL FROM THE PHARAOH SOL BRAND!!!

Fluent Fiction - Hindi: The Kite Chase: A Tale of Friendship and Fun in the Fields Find the full episode transcript, vocabulary words, and more:fluentfiction.com/hi/episode/2026-04-22-07-38-20-hi Story Transcript:Hi: सुनहरी सरसों के खेतों के बीच नीला आकाश मुस्कुरा रहा था।En: Amidst the golden mustard fields, the blue sky was smiling.Hi: हल्की-हल्की हवा चल रही थी।En: A gentle breeze was blowing.Hi: इन खेतों के बीच में आरव अपनी पतंग लेकर खड़ा था।En: In these fields, Aarav stood with his kite.Hi: आरव की एक खास इच्छा थी - अपनी पतंग का ख़ास करतब दिखाना ताकि प्रिया उसे प्रभावित हो सके।En: Aarav had a special wish - to perform a unique trick with his kite so that Priya could be impressed.Hi: प्रिया, जो आरव की दोस्त थी, अक्सर उसे चिढ़ाया करती थी जब भी वह कुछ ज्यादा ही आत्म-विश्वास दिखाता था।En: Priya, who was Aarav's friend, often teased him whenever he showed too much self-confidence.Hi: विक्रम, आरव का शैतान चचेरा भाई, पास ही खड़ा था, उसकी योजनाओं पर नज़र रखे हुए, क्योंकि वह हमेशा आरव को परेशानी में डालना पसंद करता था।En: Vikram, Aarav's mischievous cousin, was standing nearby, keeping an eye on his plans, because he always enjoyed getting Aarav into trouble.Hi: आरव ने अपनी पतंग ऊँची उड़ाई।En: Aarav flew his kite high.Hi: जैसे ही वह अपनी पतंग का करतब दिखाने वाला था, पास में चर रही गाय ने अचानकर झपट्टा मारकर उसकी पतंग चबा ली।En: As he was about to perform his kite trick, a grazing cow suddenly lunged and nibbled at his kite.Hi: यह देखकर प्रिया खिलखिला उठी, "अब कैसे दिखाओगे अपनी कला आरव?En: Seeing this, Priya burst into laughter, "How will you show off your skills now, Aarav?"Hi: " आरव परेशान हो गया, परंतु उसकी आशाएँ अभी मरी नहीं थीं।En: Aarav was upset, but his hopes weren't dashed yet.Hi: उसने विक्रम की पतंग उधार लेने का फैसला किया।En: He decided to borrow Vikram's kite.Hi: विक्रम ने आँखें मारी और कहा, "चलो, आज देखता हूँ तुम्हारी क़ाबिलियत।En: Vikram winked and said, "Come on, let's see your capability today."Hi: "आरव ने गाय को खाने की दरार दिखाकर धीरे से अपनी ओर बुलाने की कोशिश की, ताकि अपनी पतंग वापस ले सके।En: Aarav tried to entice the cow by showing it a crack with food, hoping to get his kite back.Hi: लेकिन गाय तेज़ी से सरपट दौड़ने लगी।En: But the cow started running swiftly.Hi: अब आरव के पीछे-पीछे भागता गया, और प्रिया उसकी इस जद्दोजहद को देखकर हँसती रही।En: Now Aarav ran after it, and Priya kept laughing at his struggle.Hi: अंततः, आरव खाली हाथ लौट आया, लेकिन वह निराश नहीं था।En: Eventually, Aarav returned empty-handed, but he wasn't discouraged.Hi: प्रिया ने उसकी आँखों में देख कर कहा, "तुमने पूरी कोशिश की।En: Priya looked into his eyes and said, "You really tried hard.Hi: मुझे तुम्हारा प्रयास पसंद आया।En: I liked your effort.Hi: क्या तुम मुझे पतंग उड़ाना सिखाओगे?En: Will you teach me how to fly a kite?"Hi: "आरव ने मुस्कुरा कर हामी भर दी।En: Aarav smiled and nodded.Hi: उसे एहसास हुआ कि प्रिया को दिखावे से ज्यादा ईमानदारी और सच्चे प्रयास की परवाह है।En: He realized that Priya cared more about honesty and genuine effort than showmanship.Hi: सरसों के बीच की उस दिन की हवा आज आरव के लिए ख़ुशियों की ख़बर लेकर आई थी।En: The breeze in the mustard fields that day brought news of happiness for Aarav.Hi: खेत की सारी खुशबू आरव और प्रिया की दोस्ती में घुल गई।En: The whole fragrance of the field mingled into Aarav and Priya's friendship. Vocabulary Words:amidst: बीचgrazing: चर रहीnibbled: चबा लीdiscouraged: निराशcapability: क़ाबिलियतentice: लुभानाswifty: तेज़ी सेburst: खिलखिला उठीself-confidence: आत्म-विश्वासmischievous: शैतानunique: ख़ासimpressed: प्रभावितwinked: आँखें मारीstruggle: जद्दोजहदfragrance: खुशबूbreeze: हवाgenuine: सच्चेborrow: उधारshowmanship: दिखावाplans: योजनाओंeffort: प्रयासfriendship: दोस्तीnews: ख़बरcapability: क़ाबिलियतswiftly: सपट दौड़नेempty-handed: खाली हाथlunged: झपट्टाperform: दिखानाfields: खेतोंrealized: एहसास

On this week's Spectator Out Loud: as the King prepares to head to America, Robert Hardman looks ahead to what would have been Elizabeth II's centenary celebration; Melissa Kite reports from the fuel protests in Ireland (featuring one of the disgruntled truckers); Julian Glover mourns the demise of the railway restaurant car; and finally, do you love it or hate it – Sarah Carlson provides her notes on marmite. Produced and presented by Patrick Gibbons. Hosted on Acast. See acast.com/privacy for more information.

Fluent Fiction - Japanese: Blossoms and Blunders: A Chaotic Kite and Unexpected Connections Find the full episode transcript, vocabulary words, and more:fluentfiction.com/ja/episode/2026-04-17-22-34-01-ja Story Transcript:Ja: 京都の桜祭りの日は、晴れた空に色とりどりの凧が舞い上がる美しい朝でした。En: On the day of the Kyoto Cherry Blossom Festival, it was a beautiful morning with colorful kites soaring in the clear sky.Ja: ピンクの花びらが風に舞い、露店からは美味しそうな食べ物の香りが漂っていました。En: Pink petals danced in the wind, and from the stalls, the aroma of delicious food wafted through the air.Ja: ハルトはドキドキしていました。En: Haruto was feeling excited.Ja: 「今日は、アイコに自分をもっと知ってもらおう」と思っていたのです。En: "Today, I want Aiko to get to know me better," he thought.Ja: アイコは優しい笑顔で、美しい着物を着て歩いていました。En: Aiko, with her gentle smile, was walking around in a beautiful kimono.Ja: ハルトは彼女の姿を見て、どうしても印象を残したいと思いました。En: Seeing her, Haruto felt an overwhelming urge to leave a strong impression.Ja: そこで、ハルトは凧揚げを使ってアイコを驚かせる計画を立てました。En: So, he came up with a plan to surprise her with kite flying.Ja: ところが、凧を手に取った瞬間、彼はちょっぴり不安になりました。En: However, the moment he picked up the kite, a slight sense of nervousness crept in.Ja: 「大丈夫、ハルト。凧を上手に飛ばせば、アイコも喜ぶよ」と背中を押すのは、ハルトの親友リョウスケ。En: "Don't worry, Haruto. If you fly the kite well, Aiko will be delighted," encouraged Haruto's reliable friend Ryousuke, who was always there to support him.Ja: 常に彼を助けてくれる頼もしい存在です。しかし、少しまじめな顔をしたリョウスケの提案は、たまに問題を起こすこともありました。En: However, sometimes Ryousuke's serious suggestions could lead to unexpected problems.Ja: ハルトは勇気を出して凧を広げました。En: Haruto mustered up the courage to unfold the kite.Ja: 最初は順調に見えたものの、風が強くなり始め、ハルトの手から凧の糸が次々に絡んでしまいました。En: At first, everything seemed to be going smoothly, but the wind started to pick up, and soon the kite strings got all tangled in his hands.Ja: 「あ、ちょっと待って！」と叫ぶ声とともに、ハルトの凧は空中で他の凧と絡まり合い、見る間に大きな混乱を招きました。En: "Oh, wait a minute!" he shouted as his kite became intertwined with others in the sky, resulting in immediate chaos.Ja: 周囲の人々は「ああ！」と驚きの声を上げ、ハルトは慌てて凧糸を解こうとしました。En: The surrounding people let out cries of "Ah!" in surprise as Haruto frantically tried to untangle the kite strings.Ja: しかし、それは逆に糸の絡まりを悪化させるばかりでした。En: However, his attempts only made the tangling worse.Ja: 場面は一瞬静まり、次の瞬間大きな笑い声が響き渡りました。En: The scene fell silent for a moment and then erupted in laughter.Ja: その中にアイコの笑い声も混じっていたのです。En: Among those laughs was Aiko's.Ja: ハルトは恥ずかしさで顔を赤くしながらも、アイコが楽しそうに笑っているのを見て、ほっとしました。En: Feeling embarrassed, Haruto's face turned red, but seeing Aiko laughing happily brought him some relief.Ja: 「ごめん、ちょっと張り切りすぎたよ」と、ハルトは頭をかきながら言いました。En: "Sorry, I just got a little too enthusiastic," he said, scratching his head.Ja: 「そんなところもハルトらしくて、いいと思うわ」と、アイコは優しく答えました。En: "That's just like you, Haruto, and I think it's great," Aiko replied kindly.Ja: 彼女の言葉に励まされ、ハルトは自分らしさを出すことの大切さを知りました。En: Encouraged by her words, Haruto realized the importance of showing his true self.Ja: 彼は、「今度はもっと素直な自分を見せたいな」と心の中で決めました。En: He decided in his heart, "Next time, I want to show more of my genuine self."Ja: 風で舞う桜の下、彼らは新しい友情と理解を育んでいくのでした。En: Under the cherry blossoms swaying in the wind, they nurtured a new friendship and understanding.Ja: 春の日差しの中で、ハルトの心はますます温かく、穏やかに感じられたのでした。En: In the spring sunlight, Haruto's heart felt warmer and more at peace. Vocabulary Words:soaring: 舞い上がるpetals: 花びらaroma: 香りwafted: 漂っていたexcited: ドキドキしていたgentle: 優しいimpression: 印象urge: どうしても思ったsurprise: 驚かせるnervousness: 不安reliable: 頼もしいmustered: 勇気を出してsmoothly: 順調にtangled: 絡んでしまいましたshouted: 叫ぶresulting: 招きましたfrantically: 慌ててuntangle: 解こうintertwined: 絡まり合いchaos: 混乱relief: ほっとしたenthusiastic: 張り切りすぎたencouraged: 励まされgenuine: 素直swaying: 舞うnurtured: 育んでいくunderstanding: 理解spring: 春peace: 穏やかに

Alicia Kite is one of the UK's most pioneering figures in fashion. She opened her first luxury designer boutique at 19 — becoming one of the first UK retailers to stock Moschino and growing Alicia Kite into a five-store fashion destination, working with Prada and Dolce & Gabbana. She went on to launch Begin Again, a designer resale concept that was ahead of the sustainability curve by decades, before channelling her expertise into personal styling and the Alicia Kite Academy — now 20 years old, and responsible for training an entire generation of image consultants across the UK. Her latest venture is her own shapewear brand, designed from the ground up to be breathable, comfortable, and stylish enough to show off — not hide in. From teenage entrepreneur to academy founder to product designer, Alicia Kite has spent over three decades reshaping how women think about fashion, confidence, and what they wear.Alicia Kite is our guest in episode 578 of My Time Capsule and chats to Michael Fenton Stevens about the five things she'd like to put in a time capsule; four she'd like to preserve and one she'd like to bury and never have to think about again .For everything Alicia Kite including her shapewear and personal fashion consultancy, visit - https://www.aliciakite.co.uk .Follow Alicia Kite on Instagram: @aliciakiteshapewear .Follow My Time Capsule on Instagram: @mytimecapsulepodcast & Twitter/X & Facebook: @MyTCpod .Follow Michael Fenton Stevens on Twitter/X: @fentonstevens & Instagram @mikefentonstevens .Produced and edited by John Fenton-Stevens for Cast Off Productions .Music by Pass The Peas Music .Artwork by matthewboxall.com .This podcast is proud to be associated with the charity Viva! Providing theatrical opportunities for hundreds of young people .To support this podcast, get all episodes ad-free and a bonus episode every Wednesday of "My Time Capsule The Debrief', please sign up here - https://mytimecapsule.supercast.com. All money goes straight into the making of the podcast. Hosted on Acast. See acast.com/privacy for more information.

On this week's Spectator Out Loud: as the King prepares to head to America, Robert Hardman looks ahead to what would have been Elizabeth II's centenary celebration; Melissa Kite reports from the fuel protests in Ireland (featuring one of the disgruntled truckers); Julian Glover mourns the demise of the railway restaurant car; and finally, do you love it or hate it – Sarah Carlson provides her notes on marmite. Produced and presented by Patrick Gibbons.Become a Spectator subscriber today to access this podcast without adverts. Go to spectator.co.uk/adfree to find out more.For more Spectator podcasts, go to spectator.co.uk/podcasts.Contact us: podcast@spectator.co.uk Hosted on Acast. See acast.com/privacy for more information.

This content has been developed for healthcare professionals only. Patients who seek health information should consult with their physician or relevant patient advocacy groups.For the full presentation, downloadable Practice Aids, slides, and complete CME/NCPD/AAPA information, and to apply for credit, please visit us at PeerView.com/UKJ865. CME/NCPD/AAPA credit will be available until April 10, 2027.ChARTing New Ground in NHL: Practice-Changing Evidence, Real-World Experience, and Outpatient Delivery of Cellular Therapy In support of improving patient care, PVI, PeerView Institute for Medical Education, is jointly accredited by the Accreditation Council for Continuing Medical Education (ACCME), the Accreditation Council for Pharmacy Education (ACPE), and the American Nurses Credentialing Center (ANCC), to provide continuing education for the healthcare team.SupportThis activity is supported through educational grants from Bristol Myers Squibb, Caribou Biosciences, Inc., Kite, A Gilead Company, Miltenyi Biomedicine, and Novartis Pharmaceuticals Corporation.Disclosure information is available at the beginning of the video presentation.

This content has been developed for healthcare professionals only. Patients who seek health information should consult with their physician or relevant patient advocacy groups.For the full presentation, downloadable Practice Aids, slides, and complete CME/NCPD/AAPA information, and to apply for credit, please visit us at PeerView.com/UKJ865. CME/NCPD/AAPA credit will be available until April 10, 2027.ChARTing New Ground in NHL: Practice-Changing Evidence, Real-World Experience, and Outpatient Delivery of Cellular Therapy In support of improving patient care, PVI, PeerView Institute for Medical Education, is jointly accredited by the Accreditation Council for Continuing Medical Education (ACCME), the Accreditation Council for Pharmacy Education (ACPE), and the American Nurses Credentialing Center (ANCC), to provide continuing education for the healthcare team.SupportThis activity is supported through educational grants from Bristol Myers Squibb, Caribou Biosciences, Inc., Kite, A Gilead Company, Miltenyi Biomedicine, and Novartis Pharmaceuticals Corporation.Disclosure information is available at the beginning of the video presentation.

On May 24, 2004, co-workers of 53 year old Oakey Albert Kite Jr., who went by Al, drove to his house to check on him after he failed to show up to work - something he had never done before.Inside his Aurora, Colorado townhome, officers discovered a horrific scene. Al had been bound, tortured for hours, and killed in his own basement.The killer cleaned up, removed key evidence, and disappeared - leaving behind only a small amount of DNA and a trail that pointed to a man who wasn't who he claimed to be.More than 20 years later, Al's murder remains unsolved, and detectives are still working to identify the person responsible.Anyone with information in Al's case is asked to call the Metro Denver Crime Stoppers at 720-913-7867 or your local FBI office. There is a $2,000 reward for information. Editor: Shannon KeirceResearch/Writing: Haley GraySUBMIT A CASE HERE: Cases@DetectivePerspectivePod.com SOCIALInstagram: https://www.instagram.com/detperspective/Twitter: https://twitter.com/detperspectiveFIND DERRICK HERETwitter: https://twitter.com/DerrickLInstagram: https://www.instagram.com/DerrickLevasseurFacebook: https://www.facebook.com/DerrickVLevasseurCRIME WEEKLY AND COFFEECriminal Coffee Company: https://www.CriminalCoffeeCo.comCrime Weekly:  https://crimeweeklypodcast.com/shopADS:1. https://www.TryFUM.com - Use code DETECTIVE for a FREE gift with your Journey Pack!2. https://www.TakeLean.com - Use code DETECTIVE for 20% off and FREE rush shipping!3. https://www.Rula.com/Detective - Take the first step, get connected, and take control of your mental health today!

Improve your foiling skills in paradise! Join us in Montanita Ecuador May 23-30, 2026 for a foil drive / tow / prone foil camp with Ecuador Foil, KT Foiling & Julia Castro. Learn MoreOn this Foil Life Travel Show episode, Jelle Stoop — owner of Foil School Nederland — returns to catch up with Luc Moore about building and running a successful foil school in the Netherlands, the explosion of new foiling disciplines, and how to create a thriving watersports business with purpose.Jelle shares the story behind Foil School Nederland at the iconic Brouwersdam, the unique conditions that make it a favorite spot for wing foilers and kiters, and how the school has evolved with the rapid development of para-winging, foil assist, and e-foiling. He dives into teaching methodology, gear choices, why para-winging is taking off so quickly for experienced wing foilers, and how they're adapting lesson programs for the new season. The conversation also covers his popular foiling camps across Europe and the meaningful foundation work the school does with organizations like the BBL Mentel Foundation and Kite for Life.Episode Highlights:- Why “Foil School Nederland” remains a perfect, searchable name and how they split the local school from the international Foiling Camps brand.- Brouwersdam conditions: flat water options, chop, small waves, wind patterns, and the best months for visiting riders.- The rise of para-winging — how quickly experienced wing foilers progress, ideal conditions, gear recommendations, and why it feels so addictive.- Foil assist and e-foiling in the school program: what's working, what's growing, and how they fit into the bigger picture.- Building a purpose-driven school — working with Make-A-Wish, cancer survivors, and people with disabilities, and why giving back strengthens the business.- Camp destinations for 2026: Tenerife downwind camps, Denmark wave camps, Ireland, and more.- Advice for riders visiting the Netherlands and what the future holds for foiling in Europe.This is a practical, inspiring conversation for anyone interested in wing foiling, starting a school, traveling for foiling, or simply improving their sessions in variable conditions. Jelle's grounded approach and long-term vision make this a must-listen for the foiling community.Tune in to hear how one of Europe's busiest foil schools stays ahead of the curve while keeping the stoke and community at the center of everything they do.This episode is brought to you by Waterspeed. Download the app — live tracking, deep analytics, and community vibes for every watersport adventure.

Fluent Fiction - Mandarin Chinese: Soaring Smiles: A Kite Contest at the Great Wall Find the full episode transcript, vocabulary words, and more:fluentfiction.com/zh/episode/2026-04-08-07-38-20-zh Story Transcript:Zh: 清明节的上午，长城上充满了欢声笑语。En: On the morning of Qingming Festival, the Great Wall was filled with joyful laughter.Zh: 游客和当地人聚集在这里放风筝。En: Tourists and locals gathered here to fly kites.Zh: 天空中，各式各样的风筝迎风飞舞，形成了一幅美丽的画面。En: In the sky, all sorts of kites danced in the wind, creating a beautiful picture.Zh: 在这个热闹的场景中，李梅、陈伟和张涛正准备着他们的风筝比赛。En: In this lively scene, Li Mei, Chen Wei, and Zhang Tao were preparing for their kite competition.Zh: 李梅心里有些忐忑。En: Li Mei felt a bit anxious.Zh: 她一直想要证明自己能像张涛一样优秀。En: She always wanted to prove she could be as excellent as Zhang Tao.Zh: 张涛的风筝总是设计得又大又漂亮。En: Zhang Tao's kites were always designed to be big and beautiful.Zh: 陈伟却总是乐观。En: However, Chen Wei was always optimistic.Zh: 他相信，只要好玩，就一定能赢。En: He believed that as long as it was fun, he could definitely win.Zh: “李梅，别紧张！”陈伟笑着说，“让风筝带上你的笑脸就好。”En: "Li Mei, don't worry!" Chen Wei said with a smile, "Just let the kite carry your smile."Zh: 李梅听后微微一笑，心里觉得轻松了不少。En: After hearing this, Li Mei smiled slightly, feeling much more relaxed inside.Zh: 比赛开始，李梅的风筝总是跟其他风筝缠在一起，让她有点无奈。En: As the competition started, Li Mei's kite kept getting tangled with other kites, which left her a bit helpless.Zh: 而张涛的风筝依旧轻松飞在高空，引得大家阵阵喝彩。En: Zhang Tao's kite, on the other hand, soared easily in the high sky, drawing rounds of applause from everyone.Zh: 李梅努力地想控制住自己的风筝，却不断失败。En: Li Mei struggled to control her kite but kept failing.Zh: 她的风筝在空中像个调皮的小孩，乱飞乱撞。En: Her kite was like a mischievous child in the sky, flying and bumping around erratically.Zh: 就在这时，李梅想起了陈伟的话。En: Just then, Li Mei remembered Chen Wei's words.Zh: 她决定改变策略，不再仅仅追求技术。En: She decided to change her tactics and stopped solely pursuing technique.Zh: 她从包里拿出彩色的降落伞和画上滑稽表情的布料，迅速地装在风筝上。En: She took out colorful parachutes and fabric with funny faces from her bag and quickly attached them to her kite.Zh: 所有人都好奇地看着她。En: Everyone watched her curiously.Zh: 突然，李梅的风筝极速下坠。En: Suddenly, Li Mei's kite plummeted rapidly.Zh: 就在大家以为它要掉到地面时，那个滑稽的“脸”突然焕发笑容，降落伞展开，风筝在空中悠然飘荡，逗得观众哈哈大笑。En: Just when everyone thought it would crash to the ground, the funny "face" suddenly beamed with a smile, the parachute opened, and the kite drifted leisurely in the air, amusing the audience into hearty laughter.Zh: 比赛结束时，李梅没有赢得冠军，但她赢得了所有观众的欢笑和掌声。En: By the end of the competition, Li Mei didn't win the championship, but she won the laughter and applause of all the spectators.Zh: 而这时，她也终于明白了，快乐和创意比胜利更重要。En: At that moment, she finally understood that joy and creativity are more important than victory.Zh: 她对自己的风筝技艺更加自信，也感受到了风筝飞舞带来的乐趣。En: She felt more confident in her kite-flying skills and enjoyed the fun that kite flying brought.Zh: 在春日的微风中，李梅、陈伟和张涛相视而笑，长城在他们的身后，仿佛也在微笑着祝福。En: In the gentle spring breeze, Li Mei, Chen Wei, and Zhang Tao exchanged smiles, with the Great Wall behind them, as if it too was smiling and offering blessings.Zh: 今天的比赛虽然结束，但他们的友谊和欢笑，将永远在这片天空下继续。En: Although today's competition had ended, their friendship and laughter would continue forever under this sky. Vocabulary Words:festival: 节gathered: 聚集kite: 风筝joyful: 欢声笑语anxious: 忐忑prove: 证明excellent: 优秀optimistic: 乐观technique: 技术tangled: 缠soared: 飞applause: 喝彩mischievous: 调皮erratically: 乱tactics: 策略parachutes: 降落伞curiously: 好奇plummeted: 下坠leisurely: 悠然spectators: 观众championship: 冠军creativity: 创意confident: 自信enjoyed: 感受gentle: 微风blessings: 祝福competition: 比赛friendship: 友谊laughter: 欢笑continue: 继续

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'

TUESDAY HR 4 Detective Barb from CrimeLine Orlando. Protecting our retirees from phone scams. Dr. Celina Dozier for Orlando Kite Festival. Wine Diva Anne for International Beer Day

TUESDAY HR 4 Detective Barb from CrimeLine Orlando. Protecting our retirees from phone scams. Dr. Celina Dozier for Orlando Kite Festival. Wine Diva Anne for International Beer DaySee omnystudio.com/listener for privacy information.

High-performance coach and entrepreneur Jake Smolarek has spent over 20 years helping ambitious people scale fast, build smarter, and create businesses that serve their lives instead of consuming them. Today he reveals his battle-tested coaching frameworks that turn big dreams into reality without the burnout. The Journey: From arriving in the UK at 19 with just £150 in his pocket to building multiple businesses (and failing along the way), Jake learned the hard way that success demands persistence, delegation, and a refusal to quit. His frameworks were forged from two decades of coaching clients and studying icons like Arnold Schwarzenegger, Elon Musk, and Steve Jobs. The Value: If you're stuck drifting without direction or constantly starting over, Jake's three signature frameworks give you the exact structure to build unbreakable momentum, believe in your own success, and make daily progress that actually compounds. Perfect for entrepreneurs who are done with quick-fix hype and ready for real, sustainable growth. Links & Socials: Jake's website: https://jakesmolarek.com Find Jake on LinkedIn and Google “Jake Smolarek” Edit your podcasts like a pro:https://get.descript.com/mrzy10nwivuqJoin me as a guest or start your podcast journey:https://www.joinpodmatch.com/nickkuhne Timestamps: 00:00 – Jake Smolarek on never giving up and the crazy factor in success 01:00 – Kite surfing lessons: why you must learn to delegate early 03:00 – The origin of Jake's coaching frameworks 04:30 – Vision GPS explained (the four ingredients) 08:00 – Why most people stop dreaming and how to restart 10:30 – The power of “Just do it” and the importance of discipline over motivation 12:00 – Jake's personal vision and how it evolved 14:00 – Three Steps to Win Your Gold Medal 16:30 – No Zero Days + the 1% rule (Kaizen in action) 19:30 – How to get in touch with Jake Smolarek Connect with me on:All my linksBecome a guestSign up for RiversideGet Descript #DigitalMarketing #Branding #PersonalBranding #MarketingInsights #SocialMediaStrategy Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

The city got a new Zero Turn that I got to check out. And there was some kite flyin' goin' on at the park with the elementary school kiddos. Flyin' a kite ain't for the quitters. Maisley Grubbs ain't no quitter, but she almost wished she was. And me and Rusty Tidwell almost got really into remote control car rampin' until we got interrupted. Send in your answers for this week's question!Venmo: @Tavin-DillardEmail: tavindillard@gmail.com (mailto:tavindillard@gmail.com)Tavin's Instagram: http://www.instagram.com/tavin_dillard (http://www.instagram.com/tavin_dillard)All my shirts: https://www.rockcityoutfitters.com/collections/tavin-dillardLouisville Show Tickets: https://www.etix.com/ticket/p/65433481/tavin-dillard-in-louisvilleky-louisville-mr-gs-bar-and-grill?clickref=1100lC9iqtiFIndianapolis Show  Tickets: https://www.etix.com/ticket/p/68944629/tavin-dillard-in-indianapolisin-greenwood-greenwood-mad-hatter-shows-event-center-greenwoodin?clickref=1110l34XVBW7My website where you can find all show tickets: https://www.sweetteafilms.com/

This book has a very fabulous determined, genderfluid, and Bi character. Reading her released something in me.Today we meet Sarah Stone and we're talking about the queer book that saved their life: The Passion by Jeanette Winterson.Sarah Stone (she/they) is the author of Marriage to the Sea; Hungry Ghost Theater, a finalist for the 38th annual Northern California Book Awards; and The True Sources of the Nile, as well as co-author, with Ron Nyren, of Deepening Fiction: A Practical Guide for Intermediate and Advanced Writers.Sarah's work has appeared in many publications, including Ploughshares, StoryQuarterly, Scoundrel Time, Alta Journal online for the California Book Club, and A Kite in the Wind: Fiction Writers on Their Craft. She has taught for UC Berkeley, the Warren Wilson MFA Program for Writers, and Stanford Continuing Studies, AND has written for Korean public television, reported on human rights in Burundi, AND looked after orphan chimpanzees at the Jane Goodall Institute.The Passion was a 1987 novel described as "arresting, elegant." Set in Napoleon's Europe, The Passion tells the intertwined stories of Henri, a young Frenchmen who serves as a cook in Napoleon's army, and Villanelle who is a red-haired (and web-footed!) Venetian.Jeanette Winterson's (CBE) first novel was Oranges Are Not the Only Fruit. She has written thirteen novels, one memoir, and two collections of short stories. She has also written children's books, non-fiction and screenplays. She is Professor of New Writing at the University of Manchester.Connect with Sarahwebsite: sarahstoneauthor.cominstagram: @sarahstoneauthorOur BookshopVisit our Bookshop for new releases, current bestsellers, banned books, critically acclaimed LGBTQ books, or peruse the books featured on our podcasts: bookshop.org/shop/thisqueerbookBuy your copy of The Passion here: https://bookshop.org/a/82376/9780802135223Buy your copy of Marriage to the Sea: https://bookshop.org/a/82376/9781961897847Become an Associate Producer!Become an Associate Producer of our podcast through a $20/month sponsorship on Patreon! A professionally recognized credit, you can gain access to Associate Producer meetings to help guide our podcast into the future! Get started today: patreon.com/thisqueerbookCreditsHost/Founder: John ParkerExecutive Producer: Jim PoundsAssociate Producers: Archie Arnold, K Jason Bryan and David Rephan, Bob Bush, Natalie Cruz, Troy Ford, Jonathan Fried, Joe Perazzo, Bill Shay, Sean Smith, and Karsten VagnerPatreon Subscribers: Stephen D., Terry D., Stephen Flamm, Ida Göteburg, Thomas Michna, Sofia Nerman, and Gary Nygaard.Creative and Accounting support provided by: Gordy EricksonQuatrefoil LibraryQuatrefoil has created a curated lending library made up of the books featured on our podcast! If you can't buy these books, then borrow them! Link: https://libbyapp.com/library/quatrefoil/curated-1404336/page-1Support the show

"Humans are meant to excel. And when you start pushing that and seeing how capable we are, it's phenomenal what you can actually go and do."-Justin PackshawWhen Justin Packshaw was trekking in Antarctica several years ago, he noticed something disturbing: The ice shelf had visibly melted since his previous visit, just a few decades prior. "In the grand scheme of how old our world is, and its present state, that's a really quite frightening thing," he said. And with that, he had an idea. Not all scientists have the time, resources, or, frankly, the stamina to conduct invaluable in-person research in the heart of Antarctica, which holds the record as the world's coldest, windiest, and driest continent. But Justin did.He and his adventure partner, Jamie Facer-Childs, proposed a data-gathering mission to several universities: They would cross Antarctica's heart and gather critical scientific data about climate change. But other agencies were interested in the trip as well.As it turns out, pushing the human body to its limits - physically, psychologically, mentally - is one of the key areas of research for space agencies like NASA and the European Space Agency. Justin and Jamie's expedition would collect critical data on behavior, coping abilities, teamwork, endurance, even eyesight, that would be invaluable for future space missions in which astronauts will live for years in a space no larger than a studio apartment.This is a good, old-fashioned adventure romp - but it's more than that too. It's also a story about science, psychology, Mars, and climate change. It's about how we cope with the most extreme physical challenges imaginable and ultimately how that defines us as humans.FIND JUSTINLearn more about Justin and his adventures at his website, JustinPackshaw.com, or follow him on Instagram @JustinPackshaw. Find more details about the Antarctica expedition at ChasingTheLight2021.com.SOCIALShare the show with your friends! Subscribe to the podcast wherever you're listening, follow @armchairexplorerpodcast on Instagram and Facebook, check out Armchair Explorer's website, armchair-explorer.comCREDITSThis episode was produced by Armchair Productions. Find our other shows at armchair-productions.com. Jenny Allison wrote and produced this episode, along with host and producer Aaron Millar. Charles Tyrie did the audio editing and sound design. Theme music written by the artist Sweet Chap.Mentioned in this episode:Check out the Smart Travel PodcastThis week's show is supported by the new Smart Travel Podcast. Travel smarter — and spend less — with help from NerdWallet. Check out Smart Travel at the Link below:Smart Travel PodcastCheck out all of our other travel podcasts from around the worldThis podcast is part of the Voyascape Network, a collection of some of the world's best travel podcasts. Explore more at Voyascape.com. For advertising or sponsorship opportunities across the network, see the link below.Voyascape Podcast Network