Podcasts about Yeager

Four tracks deep on a Saturday session, and Brick's spinning everything from hygiene anthems to hard film truths. The Chip Song settles the hand-washing debate once and for all — soap, twenty seconds, then you can say Go Pack Go. Non-Factor drops the cold line: the film doesn't argue back. Yeager brings the Jagger energy for the big man out of Kentucky who can play guard or center — answer's yes. And Stateline Rust closes the hour with a eulogy for a franchise that traded a century of frozen glory for a tax break in Indiana. The tapes are still spinning. Stay locked to Tundra FM.

Four tracks deep on a Saturday session, and Brick's spinning everything from hygiene anthems to hard film truths. The Chip Song settles the hand-washing debate once and for all — soap, twenty seconds, then you can say Go Pack Go. Non-Factor drops the cold line: the film doesn't argue back. Yeager brings the Jagger energy for the big man out of Kentucky who can play guard or center — answer's yes. And Stateline Rust closes the hour with a eulogy for a franchise that traded a century of frozen glory for a tax break in Indiana. The tapes are still spinning. Stay locked to Tundra FM.

Founder of Upshift, Shawn Yeager, joined me on Ditching Hourly to talk about how AI is killing the billable hour and what professional services firms can do about it. Jonathan and Shawn dig into judgment versus execution, what firms should commercialize after AI, why cost-cutting is only the first move, and how agent workflows change what small and midsize firms can do.00:00 - Introduction01:54 - AI and the billable hour03:56 - The judgment sandwich05:19 - Strategy, execution, and hidden value09:06 - Client conversations about AI pressure13:26 - Validating AI output15:29 - Judgment, marketing, and cost of being wrong17:07 - AI transformation and commercialization20:08 - The hard parts big firms still need humans for22:20 - Cost recovery versus new offerings25:35 - Agents as extra employees26:40 - Interns versus chiefs of staff28:44 - Scaffolding agent workflows30:12 - From chatbots to delegated workflows37:00 - AI adoption inside firms42:01 - Closing remarksShawn Yeager runs Upshift, a firm focused on helping professional services firms understand what they sell after AI. His career has focused on emerging technology and getting it to market, including work on Microsoft's first browser team, the SaaS/cloud wave, mobile, Bitcoin, and AI. His background is in computer science, and his work has included sales, marketing, partnerships, consulting, Accenture, early-stage startups, and his own ventures. Learn more at upshiftco.com. (00:00) - Introduction (01:54) - AI and the billable hour (03:56) - The judgment sandwich (05:19) - Strategy, execution, and hidden value (09:06) - Client conversations about AI pressure (13:26) - Validating AI output (15:29) - Judgment, marketing, and cost of being wrong (17:07) - AI transformation and commercialization (20:08) - The hard parts big firms still need humans for (22:20) - Cost recovery versus new offerings (25:35) - Agents as extra employees (26:40) - Interns versus chiefs of staff (28:44) - Scaffolding agent workflows (30:12) - From chatbots to delegated workflows (37:00) - AI adoption inside firms (42:01) - Closing remarks ----Do you have questions about how to improve your business? Things like:Value pricing your work instead of billing for your time?Positioning yourself as the go-to person in your space?Productizing your services so you never have to have another awkward sales call or spend hours writing another custom proposal?Book a one-on-one coaching call with me and get answers to these questions and others in the time it takes to get ready for work in the morning.Best of all, you're covered by my 100% satisfaction guarantee. If at the end of the call, you don't feel like it was worth it, just say the word, and I'll refund your purchase in full.To book your one-on-one coaching call, go to: https://jonathanstark.com/callI hope to see you there!

In this message, Ps Katy dives into what keeps you anchored in the age and times that we find ourselves in. Practically and biblically we can equip ourselves to withstand and flourish no matter what season you find yourself in.

In this episode, the crew makes like a remora and dives into… a new topic! Cloacal diving has been making its way around the internet and these manta rays and remoras don't even know how famous they are. Join us as we discuss the dynamics of a host and its symbionts with Emily Yeager, who published this enrapturing paper on fish swimming up into manta rays and much much more!Links to the papers referenced in this episode can be found on our Substack. The cloacal diving study we discussed in this episode was a collaborative effort between the University of Miami Shark Research and Conservation Program, the Marine Megafauna Foundation, and the Manta Trust. Be sure to check out these organizations and programs if you want to support them or learn more!This podcast is brought to you by the yellow perch, a freshwater fish native to North America. Known for its characteristic yellow and black vertical bars, the freshwater perch inhabits lakes, ponds and streams. Unlike birds, yellow perch are incapable of perching anywhere. During the breeding season, females lay their eggs and males follow them to fertilize them as a group, in what can only be considered a sperm race. Sounds freaky as hell! Cheers to you, yellow perch!Thanks for listening to Gettin' Fishy With It! You can find our website at www.gettinfishywithit.com/. You can find us on BlueSky at @gettinfishypod.bsky.social, and on Instagram ⁠⁠@gettingfishypod⁠⁠. You can also find us on ⁠⁠Facebook⁠⁠ and ⁠⁠LinkedIn⁠⁠. If you want to drop us an email, you can send your complaints (or questions!) to gettingfishypod@gmail.com.Our theme music is “Best Time” by ⁠⁠FASSOUNDS⁠⁠. Our audio in this episode is edited and produced by Christine Archer. Check her out on all the socials @nerdrvt!We very much appreciate you taking the time to listen to our seventy-eighth episode! Please help out the podcast by subscribing on your podcast platform of choice. If you could leave us a review, that would be super helpful!If you would like to support the show, you can sign up as a paid member on our⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Substack⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠, or you can ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠buy us a coffee⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠!Thanks and we'll “sea” you again in two weeks!Additional audio credits this episode:"Adventures in Adventureland" Kevin MacLeod (incompetech.com)Licensed under Creative Commons: By Attribution 4.0 Licensehttp://creativecommons.org/licenses/by/4.0/

The Apostle Paul said that the Kingdom is not of talk but of POWER. In this message, Ps Mike explores the earliest days of the church and the miracles that were common place.

Every developer knows funding gaps exist, but most don't realize they can start at the prototype stage, shaping how you approach development, publishing, and the path to shipping your game. So today, we examine how prototype funding works, what it takes to make early stage projects fundable, and how getting this stage right can jumpstart momentum for both your game and your studio. Episode Shownotes Link: https://rengenmarketing.com/454

Whitney Yeager shares the tragic story of her son's marijuana-induced psychosis and the impact it had on his life. She emphasizes the dangers of high-potency marijuana and the need for education and awareness. Whitney also discusses the importance of recognizing the signs of marijuana use and seeking help.TakeawaysHigh-potency marijuana poses significant risks to the developing brain, leading to addiction and psychosis.Parents and educators should educate themselves on the signs of marijuana use and engage in open, non-judgmental conversations with young people about the risks of marijuana.Chapters00:00 Recognizing Signs and Seeking Help18:10 Resources and Support for Parents and Educators23:27 The Sammy Project: De-stigmatizing Mental HealthWatch the 30-minute documentary about Sam's full story here: CANNABIS INDUCED PSYCHOSIS - Sam's Story - ep. 1 - https://www.youtube.com/watch?si=QxnQsSovUXYI1a04&v=_cCSy2eYIWQ&feature=youtu.beHigh Risk THC -https://highriskthc.org/Marijuana-Anonymous.org Marijuana Anonymous - https://marijuana-anonymous.org/Mar-Anon.com (similar to Al-Anon) - https://mar-anon.com/Understanding Motivational Interviewing -https://motivationalinterviewing.org/understanding-motivational-interviewing

Please join me for a fun, brief, and insightful conversation with new SMS Band Director Maddie Yeager.

Montana State commitment Dax Yeager joins Colter Nuanez on 102.9 FM ESPN radio to talk about his pledge to MSU football.

What if the most dangerous place in your life isn't where you've said no to God, but where you've quietly revised what He said? Pastor Mike walks through the story of a king who mostly obeyed, exposing the subtle compromises that keep us from walking in the fullness of what God has called us to. There is a way that seems right to a man, and then there is The Way.

On the second hour of Nuanez Now, Colter Nuanez has some fun with the crew behind the glass as they each throw questions his way, leading to a wide-ranging and entertaining segment filled with his takes, insights, and off-the-cuff reactions.Next, continuing the conversation around in-state rivalry, Colter sits down with Choteau native Dax Yeager to discuss his commitment to Montana State and what it means to join the Bobcats program.

Let's talk about fertility, hormones, and what every woman deserves to know! We're joined by Hailey Jager, founder of The Truth & Fertility Project, to chat about how to recognize what your body is telling you, why the pill isn't the answer, how to start charting your cycle, and so much more. If you've been feeling dismissed by your doctor or just ready to finally understand your body, this episode is for you.Learn more about Truth & Fertility ProjectListen to the Truth & Fertility PodcastFollow Haley on IGResources Mentioned:NaPro TechnologyFEMM / FEMM AppNeo Fertility / Chart Neo App------Join our Kingdom Club on Patreon! Members get exclusive perks such as:

This week, Abe Yeager taught from the book of Philemon on the importance of reconciliation. Through Paul's example, we see the heart of the gospel on display: taking on the cost, extending grace, and restoring relationships.

In this culture building message, Ps Katy shares on how biblically and practically we can become a unified kingdom-building church that disciples people towards health, joy, and purpose.

In Episode 173 of Trap Talk, Zach and Ricky sit down with Dr. Zeke Yeager of Corinth, Mississippi to talk about his trapshooting journey, his love for doubles, and what it took to become the 2020 Grand American Doubles Champion. From getting started as a kid with a hard-kicking single shot to becoming one of the top doubles shooters in the game, Zeke shares the story behind the scores, the mindset, and the work that shaped his success. The conversation gets into doubles strategy, point of impact, hold points, target setting around the country, mental approach, balancing a demanding professional career with competitive shooting, and why keeping the game simple still matters at the highest level.In this episode, the guys talk about: Zeke's background in trapshooting and chiropractic practice  Growing up in a trapshooting family  His progression from beginner to top doubles shooter  Winning the 2020 Grand American Doubles Championship  Doubles hold points, gun setup, and target reading  Mental game and keeping shooting fun  Competing at a high level while balancing real life and work  Why simple usually beats complicated in trapshooting If you enjoy the show, make sure to subscribe, like the video, and support the channel. That support helps us keep bringing you more Trap Talk episodes, interviews, shoot recaps, and content for the trapshooting world.Follow & Subscribe to Trap Talk!  It really helps the show!  YouTube - https://www.youtube.com/@traptalk27Instagram - https://www.instagram.com/traptalkfromthebackfence/Facebook - https://www.facebook.com/traptalk27TikTok - https://www.tiktok.com/@trap.talk.podcast*** Email us your listener questions to askus@traptalkpodcast.com *** *** Visit TrapTalkPodcast.com for all our links! ***

There is a name Jesus spoke over two ordinary fishermen that has echoed through two thousand years of church history: Sons of Thunder. In this message, Pastor Mike traces the remarkable story of James and John from a fishing boat to the ends of the earth and calls us out of passivity and into the identity Jesus spoke over us before we ever earned it.

In Acts 4, ordinary men with no credentials and no pedigree became completely unstoppable, not because of who they were, but because of who they'd been with. This is the story of the Church. In this message, Ps Mike unpacks the moment a group of overlooked fishermen stood before the most powerful men in the world and refused to back down.

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'

Dr. Adam Cayot from Peterson Smith discusses pre-purchase exams World-renowned equestrians Linda Parelli and Luis Lucio are with us for 2 segments to discuss the changes seen from true connection and relationship with your horse, plus some sneak peeks into the Horseman Symposium this coming weekend!! Becky Jenkins from Grateful Gallops offers treatments for K9s, too, and shares the success she is having with dogs, including Louisa's dog Lucy. Tune in to see the results and learn more at www.Gratefulgallops.com There are so many equine events in March, and there are still SO many more! Tonight, we discuss events that have already happened AND the exciting ones coming up

There's a reason the spirit of religion works so hard to keep you quiet on a Sunday morning. This powerful message from Ps. Mike is about what your praise actually accomplishes and why hell fights so hard to silence it.

For the 111th episode of the CIO podcast hosted by Healthcare IT Today, we are joined by Rusty Yeager, Senior VP and CIO at Encompass Health to talk about navigating the changing world of healthcare as a CIO! We kick this episode off by discussing what we think the greatest leadership challenge healthcare CIOs are facing right now. Then we debate how we think CIOs should be navigating the ever-evolving world of AI. Next, Yeager tells us more about the Palantir solution. We then get into the value that can come from the tight integration between ERP and EHR to find out whether Yeager has seen it. We then shift over to Yeager’s time as a CIO as he shares some of his keys to effectively leading a health IT organization in this current environment. Next, Yeager shares a major lesson he learned in his time as CIO. Then, we talk about a favorite story of a project, situation, or effort during Yeager’s career. We then discuss how to properly balance strategy and team development with all of the operational challenges healthcare organizations face.  Next, we take a look at a topic that Yeager thinks deserves more attention because it isn’t being talked about enough right now. Lastly, we conclude this episode with Yeager passing along advice to aspiring CIOs as Yeager prepares to retire soon. Here’s a look at the questions and topics we discuss in this episode: What’s the greatest leadership challenge that a healthcare CIO faces right now? How should a CIO be navigating the world of ever-evolving AI? Tell us more about the Palantir solution. Have you seen the value of the tight integration between ERP and EHR? What are some of your keys to leading a health IT organization effectively in this current environment? What was a major lesson you learned in your time as CIO? Share a favorite story of a project, situation, or effort during your career. How do you balance strategy and team development with all the operational challenges a healthcare organization faces? What’s a topic that isn’t being talked about enough right now that you think deserves more attention? What advice would you give an aspiring CIO? Now, without further ado, we’re excited to share with you the next episode of the CIO Podcast by Healthcare IT Today. We release a new CIO Podcast every ~2 weeks. You can also subscribe to the Healthcare IT Today podcast on any of the following platforms: NOTE: We’ll be updating the links below as the various podcasting platforms approve the new podcast.  Check back soon to be able to subscribe on your favorite podcast application. Apple Podcasts Google Podcasts Stitcher Podcast Radio TuneIn Spotify iHeartRadio Amazon Music Thanks for listening to the CIO Podcast on Healthcare IT Today and if you enjoy the content we’re sharing, please rate the podcast on your favorite podcasting platform. Along with the popular podcasting platforms above, you can Subscribe to Healthcare IT Today on YouTube.  Plus, all of the audio and video versions will be made available to stream on HealthcareITToday.com. We’d love to hear what you think of the podcast and if there are other healthcare CIO you’d like to see us have on the program. Feel free to share your thoughts and perspectives in the comments of this post with @techguy on Twitter, or privately on our Contact Us page. We appreciate you listening! Listen to the Latest Episodes

In this episode of The Hospitality Hangout, we welcome Aris Yeager, better known as the European Kid, to discuss his viral food comedy journey and insights into the hospitality industry. Aris shares how a college joke transformed into a viral persona captivating millions across social media, blending humor with commentary on American dining etiquette and culture. Dive into the hospitality business side of creator culture as Aris explains launching Storytime, a platform forging partnerships between restaurants and creators. This episode offers insider insights on restaurant growth strategies, tipping culture, influencer marketing, and emerging hospitality trends. We also explore differences between European and American food culture, viral restaurant skits, and the evolving role of creators in hospitality leadership and brand collaboration. Whether you're a restaurant operator or hospitality executive, this conversation is packed with valuable perspectives on the intersection of social media and the restaurant industry. Join us for a wide-ranging discussion that combines humor with savvy hospitality insider insights, perfect for anyone interested in the restaurant industry podcast and hospitality media landscape. Episode Credits:Sponsored by: DirecTVProduced by: Branded Hospitality MediaHosted by: Michael Schatzberg, JImmy FrischlingProducer: Julie ZuckerCreative Director: Adam LevineShow Runner: Drewe RaimiPost Production: GrodMediawww.thehospitalityhangout.com Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Haley Yeager shares her passion for knowledge and health as she joins Steve and Becky to talk about the Truth and Fertility Project.

In this powerful exclusive interview, Bogdan Zaslavsky, father of Brayden Zaslavsky, breaks his silence after his son was viciously beaten by a violent anti-ICE mob at Olathe Northwest High School simply for holding a Trump flag.What started as student-led walk-outs quickly turned into chaos and violence — and instead of protecting students, Olathe Schools Superintendent Dr. Brent Yeager sent a letter to parents claiming these walk-outs are “protected free speech.”He is dead wrong.On this episode of The Right Side, Bogdan shares the horrifying details of the attack on Brayden, how school officials responded (or failed to respond), and why this must never happen again.We also break down the Tinker v. Des Moines Supreme Court ruling that proves disruptive walk-outs that lead to violence are NOT protected speech — and why Dr. Yeager and Principal Mr. Chris Zuck have a duty to ban them immediately.This is raw, emotional, and unfiltered truth from a father fighting for his son and for every child in the Olathe school district.✅ Timestamps:0:00 – Bogdan Zaslavsky shares what really happened to Brayden4:15 – The moment his son was attacked for holding the Trump flag8:40 – Dr. Brent Yeager's “free speech” letter exposed12:20 – Principal Chris Zuck's response (or lack of it)16:30 – What parents must do now – Call to ActionIf you live in Olathe, call Superintendent Dr. Yeager and the school board TODAY and demand real leadership and safety for our kids.Share this interview with every parent and teacher you know.The Right Side with Doug Billings — Unapologetic. Uncensored. America First.SUBSCRIBE and turn on notifications so you never miss an episode.Follow me:X: @DougBillingsRumble: The Right Side with Doug Billings#OlatheSchools #OlatheWalkOut #BraydenZaslavsky #BogdanZaslavsky #TrumpFlag #OlatheNorthwest #AntiICERiot #SchoolViolence #DrBrentYeager #ChrisZuck #FreeSpeechLie #ProtectOurKids #OlatheKS #AmericaFirst #Trump #America #KansasSupport the show

In this hard-hitting 11-minute episode of The Right Side, Doug Billings reads Olathe (O-lay-thu) Kansas Public Schools Superintendent Dr. Brent Yeager's own parent letter back to him — word for word — and finishes the Supreme Court ruling from Tinker v. Des Moines that Dr. Yeager conveniently left out.Free speech does NOT protect mass student walkouts during class time, truancy, fights, or turning taxpayer-funded schools into political battlegrounds.Last Friday's walkout at Olathe Northwest High School ended with a juvenile arrest and injured students.Parents and taxpayers of Olathe and Johnson County: this is your moment.Demand the Olathe School Board immediately ban all mass walkouts during instructional hours.Education, NOT indoctrination.Timestamps:0:00 – Intro & The Crisis in Olathe1:45 – Reading Dr. Yeager's Letter4:20 – The FULL Tinker v. Des Moines Ruling7:10 – What the Law Actually Allows9:40 – Your Action Plan TonightCommentary & Opinion – February 24, 2026Full video version available on YouTube: @TheRightSideDougBillingsShare this episode with every parent you know.Tag Dr. Brent Yeager and the Olathe School Board.We're in this together, folks. Believe it. For the Republic!#OlatheSchools #BrentYeager #TinkerRuling #StudentWalkouts #Education #Indoctrination #Olathe #Taxpayers #KansasFirst #SchoolBoard #ParentsRights #Kansas #Students #Teachers #America #USASupport the show

Dr. Delaney sits down with acclaimed developmental psychologist David Yeager, Ph.D., to discuss his groundbreaking book, 10 to 25: The Science of Motivating Young People. Together, they delve into the transformative power of adopting a mentor mindset to simplify parenting — especially when tackling tech time challenges. Learn why combining high standards with high support is a game-changer, and uncover the key elements of "wise feedback" that make it so impactful, as shown across various studies. This episode offers science-backed communication techniques on topics like respectful versus disrespectful language, validation, cooperative problem-solving, and more. Parents will walk away with practical strategies to approach screen time struggles with confidence and clarity.   Featured Expert David Yeager, PhD   Books The Science of Motivating Young People, by David Yeager Belonging: The Science of Creating Connection and Bridging Divides, by Geoffrey L. Cohen   Research References Yeager, D. et al. Breaking the cycle of mistrust: Wise interventions to provide critical feedback across the racial divide. Journal of Experimental Psychology: General, 143(2), 804–824, 2014.  Dobson, K. et al. A Transparency Statement Improves Community-Police Interactions. Research Square (Research Square), 2022. Yeager, D. et al. A Transparency Statement Transforms Community-Police Interactions. Research Square (Research Square), 2022. Telzer, E. et al. Ventral striatum activation to prosocial rewards predicts longitudinal declines in adolescent risk taking. Developmental Cognitive Neuroscience, 3, 45–52, 2013.   Time Code 00:00 Introduction to the Screenagers Podcast 00:23 Meet David Yeager: Growth Mindset and Mentor Mindset 02:34 The Mentor's Dilemma: Balancing Criticism and Support 04:23 Wise Feedback: The Key to Motivating Youth 10:17 Transparency and Benevolent Intentions 12:45 Understanding Adolescent Motivation: Status and Respect 17:42 The Role of Testosterone in Adolescent Development 20:47 Respectful Communication: The Vegemite Experiment 24:15 Testosterone and Behavior 25:50 Parenting Challenges and Mentor Mindset 27:04 The Science of Nagging 29:25 Effective Communication with Teens 32:45 Collaborative Troubleshooting 34:41 Balancing Screen Time and Life Goals 36:53 The Enforcer vs. Mentor Mindset 41:30 Concluding Thoughts and Resources  

On Episode 123 of the MBN Podcast and the second in '26, Co-Directors of Broadcast and Media Relations Daniel Stein and Ryan Martin recap the Terps' season-opening series win at UNC Wilmington, talk with Maryland RHP Jake Yeager, and preview the Terps' upcoming trip to the Louisiana Ragin' Cajuns!

Join our Kingdom Club on Patreon! Members get exclusive perks such as:

God didn't just bring Israel out of Egypt, He was committed to getting Egypt out of them. In this powerful message from Exodus 15, Ps. Mike explores how our words reveal our hearts, why God takes complaining so seriously, and how true freedom requires inner transformation, not just outward deliverance.

‘Euphonic Gumbo' is not exactly a “Nawlin's” menu item but instead a tasty musical delight that's the title of of a new album on Club 44 Records from vocalist and Broadway star Julie Benko, featuring a dazzling seven-piece band directed by her pianist-arranger husband, Jason Yeager.   This recording is the result of the collaborating couple's numerous trips to New Orleans where they developed a love for the Crescent City and its rich musical and cultural histories. The album's title comes from Benko's original play ‘Down the Line' that is set in Storyville, New Orlean's former red-light district, and features the legendary pianist Tony Jackson, a mentor to Jelly Roll Morton, as the central character. Eventually, Benko and Yeager were invited by Birdland mainstay Jim Caruso to bring their musical ensemble to the club where their Big Easy-inspired celebrations have become a beloved winter tradition.   All of this led to the development of the recording ‘Euphonic Gumbo', and the story unfolds in my conversation with Julie Benko and Jason Yeager.

On this episode of Coffee, Country & Cody, we welcome Bucky Heard and Roger Yeager   0:00 - Welcome / What’s Coming Up 1:12 - Entertainment with Kelly Sutton  5:35 - Interview with Bucky Heard  20:51 - Entertainment with Kelly Sutton 25:24 - Interview with Roger Yeager   Connect with WSM Radio: Visit the WSM Radio WEBSITE: http://bit.ly/650AMWSM Follow WSM Radio on TikTok:  https://www.tiktok.com/@wsmradio Like WSM Radio on FACEBOOK: http://bit.ly/WSMRadioFB Check out WSM Radio on INSTAGRAM: http://bit.ly/WSMRadioInsta Follow WSM Radio on X: http://bit.ly/WSMRadioTweets Listen to WSM Radio LIVE: http://bit.ly/WSMListenLive Listen to WSM on iHeartRadio: https://www.iheart.com/live/wsm-radio...  

Welcome to the daily304 – your window into Wonderful, Almost Heaven, West Virginia. Today is Wednesday, January 7, 2026 #1 – From WV EXPLORER - From pickleball to mountain biking--discover 5 sports that are growing in WV West Virginia's sports landscape continues to grow, with expanding programs and participation helping strengthen communities across the Mountain State. From local leagues to broader opportunities for athletes, sports are building healthy habits, teamwork, and hometown pride. The story highlights how athletics are becoming a bigger part of community identity and quality of life — especially as programs evolve and reach more West Virginians. Read more: https://wvexplorer.com/2025/12/27/sports-west-virginia-growing/   #2 – From THE REAL WV - Meet Yeager Airport's wildlife patrol team At West Virginia International Yeager Airport in Charleston, two border collies — Hercules and Ned — have become part of the team keeping runways safer by chasing birds and wildlife away from flight paths. Airport staff say the runway dog program has helped reduce bird strike incidents significantly since it began. Learn how the dogs are trained for this work, how the airport coordinates wildlife patrol, and why Yeager is among a small group of airports using runway dogs as part of airfield safety. Read more: https://therealwv.com/2025/12/18/highway-to-the-danger-zone-the-true-tail-of-hercules-and-ned/   #3 – From WV DHHR - WV Department of Health seeks to implement a $199M rural healthcare transformation The West Virginia Department of Health is seeking a leadership team to implement a $199 million Rural Healthcare Transformation Initiative focused on strengthening healthcare access and systems in rural communities. The initiative aims to improve quality, sustainability, and outcomes — representing a major investment in long-term rural health capacity across the state. Read more: https://dhhr.wv.gov/News/Pages/West-Virginia-Department-of-Health-Seeking-Leadership-Team-to-Implement-$199-Million-Rural-Healthcare-Transformation.aspx   Find these stories and more at wv.gov/daily304. The daily304 curated news and information is brought to you by the West Virginia Department of Commerce: Sharing the wealth, beauty, and opportunity in West Virginia with the world. Follow the daily304 on Facebook, Twitter, and Instagram @daily304. Or find us online at wv.gov and just click the daily304 logo. That's all for now. Take care. Be safe. Get outside and enjoy all the opportunity West Virginia has to offer.  

On Vision Sunday, Ps. Mike Yeager challenges us to lift our eyes beyond our present circumstances and trust the promises God has spoken over our lives. Through the story of Israel standing on the edge of the Promised Land, this message invites us to step forward in faith and SEE clearly future God has already prepared for us that we must have FAITH to step into.

In this episode, we sit down with college hitting coaches to break down what really goes into developing consistent, confident hitters at the next level. From building swing plans and teaching approach to using analytics, technology, and in-game adjustments, the coaches share how they balance modern data with old-school feel. We dive into recruiting traits they look for in hitters, common misconceptions players have about college offense, and how they individualize development within a team setting. Whether you're a coach, player, or baseball junkie, this conversation offers practical insight into how college hitting coaches prepare athletes to succeed in today's game.

In this shredder sunday message, ps katy ministers around the story of the Israelites crossing over into the promised land: what it took to cross over, what it took to possess the land and fully live out the promises of God. Fast forward to today: God wants us to partner with Him to release, remember, and respond in order to have Gods best for our 2026!

Send us a text*What can we learn about causal inference from the “war” between Bayesians and frequentists?*What can we learn about causal inference from the “war” between Bayesians and frequentists?In the episode, we cover:- What can we learn from the “war” between Bayesians and frequentists?- Why do Bayesian Additive Regression Trees (BART) “just work”?- Do heterogeneous treatment effects exist?- Is RCT generalization a heterogeneity problem?In the episode, we accidentally coined a new term: “feature-level selection bias.”------------------------------------------------------------------------------------------------------Video version available on the Youtube: https://youtu.be/-hRS8eU3TowRecorded in Arizona, US.------------------------------------------------------------------------------------------------------*About The Guest*Professor Richard Hahn, PhD, is a professor of statistics at Arizona State University (ASU). He develops novel statistical methods for analyzing data arising from the social sciences, including psychology, economics, education, and business. His current focus revolves around causal inference using regression tree models, as well as foundational issues in Bayesian statistics.Connect with Richard:- Richard on LinkedIn: https://www.linkedin.com/in/richard-hahn-a1096050/- Richard's web page: https://methodologymatters.substack.com/about*About The Host*Aleksander (Alex) Molak is an independent machine learning researcher, educator, entrepreneur and a best-selling author in the area of causality (https://amzn.to/3QhsRz4 ).Connect with Alex:- Alex on the Internet: https://bit.ly/aleksander-molak*Links*Repo- https://stochtree.aiPapers- Hahn et al (2020) - "Bayesian Regression Tree Models for Causal Inference" (https://projecteuclid.org/journals/bayesian-analysis/volume-15/issue-3/Bayesian-Regression-Tree-Models-for-Causal-Inference--Regularization-Confounding/10.1214/19-BA1195.full)- Yeager, ..., Dweck et al (2019) - "A national experiment reveals where a growth mindset improves achievement" (https://www.nature.com/articles/s41586-019-1466-y)- Herren, Hahn, et al (20Support the showCausal Bandits PodcastCausal AI || Causal Machine Learning || Causal Inference & DiscoveryWeb: https://causalbanditspodcast.comConnect on LinkedIn: https://www.linkedin.com/in/aleksandermolak/Join Causal Python Weekly: https://causalpython.io The Causal Book: https://amzn.to/3QhsRz4

Bestselling authors William Bernhardt (The Superman Wars) and Lara Bernhardt discuss the latest news from the book world, offer writing tips, and interview Janet Yeager, author of the high-tech thriller, Two Birds, One Stone. 0:00 Opening ThoughtsHow Writers Prep for the Holidays4:51 News1) Amazon Offers Free AI Foreign-Language Translations2) Grammerly Becomes Superhuman with AI Assistant15:26 Craft CornerOur panel of experts discuss the use of Amazon and AI by Writers19:57 Interview with Janet Yeager40:18 Parting WordsThe WriterCon Cruise worked for Janet Yeager. Could it do the same for you? We're leaving from Ft Lauderdale for an eight-day cruise through the Eastern Caribbean, beautiful tropical vistas combines with over twenty hours of writing instruction, plus an onboard agent who will happily talk to every participant. Don't miss out. Plan now to be with us March 7-15. Visit the WriterCon website for more info.Until next time, keep writing, and remember: You cannot fail, if you refuse to quit.William Bernhardt www.williambernhardt.comwww.writercon.com

In this Legacy Sunday message, Ps Mike unpacks how God invites His people to build a dwelling place for His presence. Discover how generosity, unity, and faith unlock a legacy of transformation for generations to come.

Russ Yeager, owner and CEO of Russ Yeager Coaching, joins The Steve Gruber Show to talk about what it really takes to get into shape, physically and mentally. From setting the right mindset to staying disciplined during the busiest time of the year, Russ shares personal stories that inspire and motivate. The conversation dives into practical strategies for building healthy habits, the role of discipline in achieving long-term goals, and why prioritizing our health isn't just about appearance, it's about living a better, more productive life. Whether you're looking to start a fitness journey or strengthen your resolve, Russ offers actionable advice and real-world insights to help you succeed. Visit RussYeager.com/BOOK for your free book!

Meet Wyatt Uhrig. General Manager and 4th-generation member of one of Bellingham's oldest and most infamous family-run retail locations in town; Yeager's Sporting Goods. In this episode, Wyatt talks about the impact of having a team that's excited about the product they're selling, how they maintain such a wide spectrum of inventory, and how they're adapting their marketing to connect more people with their shop. Plus, we get into a little bit of the family history of the people in the Yeager Family who made the business what it was over the last 100+ years, and how Yeager's navigates a revolving door of evolution across all fronts of running an in-person retail space in 2025.   Enjoy the episode!   Learn more about Yeager's:

Brief Summary: The program focused on a discussion with Roger Launius, a retired NASA historian, about his book covering NASA's history from its origins as NACA to the present day. The conversation explored NASA's relationship with commercial space industry, historical organizational changes, and the challenges of accessing NASA's historical records and archives. The discussion also covered various technical and political aspects of space exploration, including decision-making processes, military roles in space, and the evolution of NASA's approach to partnerships and innovation. Roger shared his thoughts on the future of space exploration, expressing uncertainty about the timeline for lunar missions and human presence on Mars. Space Show team participants included myself, John Jossy, Bill Gowan, Marshall Martin, John Hunt, Dr. Ajay Kothari, and Phil Swan.Detailed Summary: As host I welcomed Dr. Roger Launius back to the Space Show to discuss his new book, “From NACA to NASA to Now.” Launius explained that the book, published in 2025, provides a concise history of NASA from its origins as the National Advisory Committee for Aeronautics (NACA) in 1915 to its transformation into NASA in 1958. He highlighted the ongoing role of NASA's legacy research centers in aeronautical research today. Launius also discussed the evolution of the aerospace industry, emphasizing that the distinction between “old space” and “new space” is complex and not clearly defined. He noted that private sector activities in space have a long history, dating back to the 1950s, and that NASA's approach to commercial partnerships has evolved over time, particularly with the creation of separate entities to handle launch services in the 1990s.Bill Gowan and Roger discussed the evolution of NASA's relationship with commercial space, noting that while NASA has always relied on commercial industry for spacecraft design and construction, there has been a shift towards non-cost-plus contracts. Roger highlighted that while NASA innovations have contributed to commercial space advancements, the designs are not entirely independent of NASA's influence. They also explored the partisan nature of NASA's early years, with Roger explaining that the Apollo program faced political challenges from both the left and right, and was subject to budget cuts after its initial success.The discussion focused on the impact of the government shutdown on NASA's historical resources and archives. Roger explained that while NASA facilities are currently closed, their websites and online historical resources remain accessible, though not updated. He detailed the complex federal records system, noting that most NASA records are stored at the National Archives in Washington, D.C., and other federal record centers across the country, with access often delayed by years, especially for recent or classified materials. Marshall inquired about accessing Elon Musk's communications with NASA and the President, to which Roger clarified that such recent records would not be available in the National Archives yet and suggested using interviews and publicly released documents for journalistic research on recent events.Roger explained that separating historical facts from salesmanship in space exploration is a challenging task due to the varied motivations behind statements. He emphasized the importance of understanding these motivations and balancing contradictory perspectives. David inquired about the feasibility of modernizing old Apollo lunar lander plans, to which Roger confirmed that NASA possesses extensive technical drawings and records of past hardware in federal records centers and has historically allowed access for analysis. Roger also described the difficult transition from NACA to NASA in 1958, highlighting resistance from the military, particularly over the transfer of the von Braun team and the Army Ballistic Missile Agency's resources, which was a prolonged and contentious process.Our discussion addressed historical NASA consolidations and organizational changes, with Roger explaining that efforts to close or merge NASA facilities have been ongoing since the 1960s, though political opposition from congressional delegations has typically prevented closures. The conversation also covered the history of the National Space Council, which was established in 1958 but became less active after the 1960s, particularly under Nixon, before being revived by the Trump administration. John Hunt raised questions about military roles in space, noting how the Army developed its own ballistic missile programs while the Air Force maintained separate capabilities, highlighting ongoing challenges in service roles and missions.Roger explained that Space Council issues are now handled through the Office of Science and Technology Policy in the White House. He discussed the difficulty in finding detailed information about NASA's decision-making process for certain projects, such as the Mars Sample Return mission. Roger mentioned that some individuals, like George Lowe and Bob Siemens, kept detailed records of meetings and decisions, which are now available at Rensselaer and MIT respectively. David asked if there would be a “post-NASA era,” to which Roger responded that there is no known impetus for such a transition. The conversation also touched on the public and intellectual resistance to using Nazi engineers, like Wernher von Braun, in the early American space program, and the debate within the federal government about this issue.Roger discussed the history of supersonic flight, clarifying that Chuck Yeager did not demand a million dollars to fly the X1 and that Slick Chalmers flew multiple supersonic flights. He also addressed a controversy about whether the F-86 pilot beat Yeager's speed record, noting that the evidence was unreliable. Roger emphasized the importance of data-driven decision-making in engineering, using examples from the Challenger disaster and flight readiness reviews. Marshall inquired about decision-making processes, and Roger highlighted the need for comprehensive data and proper training in engineering education.The group discussed historical space program decisions, focusing on the Challenger launch and the X-30 National Aerospace Plane program. Roger explained that while data existed showing risks of cold-weather launches, the decision-making process was complex and the data wasn't presented clearly, leading to the catastrophic failure. The discussion also covered the X-30 program, which was announced by Reagan in the 1980s but ended in the early 90s due to technological challenges and cost concerns, though some research continued.Roger discussed the NACA's contributions to aeronautics, highlighting its approach to research and development. He explained how the NACA hired young engineers and provided them with advanced research tools, such as the variable density wind tunnel, which led to significant advancements in airframe and wing design. Roger also mentioned the NACA's involvement in rocket research during World War II, which eventually led to the establishment of NASA and the transition of key personnel to the new space agency.Roger discussed his friendship with Dr. John Anderson and shared details about a 2009 incident involving Mike Griffin and Laurie Garver at a launch party for John Logsdon's book. He explained that Mike Griffin expressed concerns about Laurie Garver's involvement in the Constellation program, emphasizing her need to step back from technical details. Roger also highlighted Laurie Garver's significant role in transitioning NASA to the commercial crew program, advocating for private sector involvement in space exploration. The conversation touched on the challenges NASA faced in the 1990s, including the cancellation of the X-33 program and the search for alternatives to the Space Shuttle.Concluding Summary: The meeting featured an interview with Roger, a retired NASA historian, who discussed his book on the history of NASA and its predecessor organizations. Roger shared his plans for future conferences and mentioned his current residence in Auburn, Alabama. The discussion also covered the availability of Roger's book for free download from NASA. The conversation ended with thanks to the show's sponsors and participants, and a reminder about an upcoming open lines session.Special thanks to our sponsors:Northrup Grumman, American Institute of Aeronautics and Astronautics, Helix Space in Luxembourg, Celestis Memorial Spaceflights, Astrox Corporation, Dr. Haym Benaroya of Rutgers University, The Space Settlement Progress Blog by John Jossy, The Atlantis Project, and Artless EntertainmentOur Toll Free Line for Live Broadcasts: 1-866-687-7223 (Not in service at this time)For real time program participation, email Dr. Space at: drspace@thespaceshow.com for instructions and access.The Space Show is a non-profit 501C3 through its parent, One Giant Leap Foundation, Inc. To donate via Pay Pal, use:To donate with Zelle, use the email address: david@onegiantleapfoundation.org.If you prefer donating with a check, please make the check payable to One Giant Leap Foundation and mail to:One Giant Leap Foundation, 11035 Lavender Hill Drive Ste. 160-306 Las Vegas, NV 89135Upcoming Programs:Tuesday, 11-11-25; 7 PM PDT, 10 PM EDT:Bob Zimmerman returns with space news and updates plus a look at space 2025. Get full access to The Space Show-One Giant Leap Foundation at doctorspace.substack.com/subscribe

In this conversation, Steve and Carl delve into the themes and intricacies of B. Yeager's book, Negative Space. They explore the unique prose style, character voices, and the nonlinear storytelling that creates a sense of despair and madness. The discussion touches on the eldritch forces at play, gnostic influences, and the existential themes that permeate the narrative. They also reflect on character arcs, the role of technology, and the symbolism within the book, drawing comparisons to other works and ultimately sharing their final thoughts on the impact of the story.Chapters00:00Introduction to Negative Space and Its Themes02:47Character Voices and Narrative Structure05:46Exploring the Protagonist and Antagonist Dynamics08:38The Role of Magic and Eldritch Forces11:21Gnosticism and Its Influence on the Story14:18The Impact of Technology and Alienation17:17Character Tragedies and Relationships20:04The Symbolism of Objects and Themes of Despair22:51Conclusion and Final Thoughts on the Book37:24Exploring the Ambiguity of Reality38:33The Role of Children in Apocalyptic Events39:26The Bleakness of Insignificance40:15The Whimpering Ending: A Mixed Resolution42:18Timey-Wimey: The Complexity of Time in the Narrative43:49The Cosmic Horror and Its Symbolism45:46The Small Town Metaphor: Inescapable Despair46:43Character Development and Existential Themes48:46The Power of Language and Prose53:14Existential Quotes and Their Impact56:05The Nature of Existence and Its Implications57:27The Contrast of Prose Styles59:04The Unresolved Nature of Cosmic Horror01:05:03Final Thoughts and RecommendationsSend us a message (I'm not able to reply)Support the showPage Chewing Blog Page Chewing Forum Film Chewing PodcastSpeculative Speculations Podcast Support the podcast via PayPal Support the show by using our Amazon Affiliate linkJoin Riverside.fm Co-Hosts: Jarrod Varsha Chris Jose Carl D. Albert (author) Thomas J. Devens (author) Intro and Outro Music by Michael R. Fletcher (2024-Current)

To get live links to the music we play and resources we offer, visit www.WOSPodcast.comThis show includes the following songs:Annie Riggs - Inconvenient FOLLOW ON SPOTIFYwomen who work - Hot Secrets FOLLOW ON SPOTIFYKatie Yeager - Revolution, Baby! FOLLOW ON SPOTIFYChloe Tsangaris - Who You Are FOLLOW ON SPOTIFYGeena Fontanella - Best Friend's Brother FOLLOW ON SPOTIFYBrett lemon - Be a Girl (feat. Lizzy Pattinson) FOLLOW ON SPOTIFYAllen & Kelly - Lovely To Love You FOLLOW ON SPOTIFYEMMA SEE - Like That FOLLOW ON SPOTIFYOne of the Broken - WaterColor FOLLOW ON SPOTIFYRACHELRACHEL - Coffee Cup FOLLOW ON SPOTIFYCaitty - The Pieces That You Left FOLLOW ON SPOTIFYDenise Dimin & Lyia Meta - This One's For You FOLLOW ON BROADJAMHattenandOrliss - Time Moves On FOLLOW ON YOUTUBEFiona Carter - Wishing Well FOLLOW ON SPOTIFYClodagh Rose - Tears To Shed FOLLOW ON SPOTIFYFor Music Biz Resources Visit www.FEMusician.com and www.ProfitableMusician.comVisit our Sponsor Profitable Musician Newsletter at profitablemusician.com/joinVisit our Sponsor Melissa D Moorhouse at melissadmusic.comVisit our Sponsor Kolie Dee at koliedee.comVisit www.wosradio.com for more details and to submit music to our review board for consideration.Visit our resources for Indie Artists: https://www.wosradio.com/resourcesBecome more Profitable in just 3 minutes per day. http://profitablemusician.com/join

In this inspiring message, Ps. Katy shares biblically how to think and act in alignment with God's kingdom, which is always family and legacy centered. Let this message practically help you live a life with eternal impact!

In this City Impact Sunday message, Ps. Mike unpacks how God uses what looks like scattering to sow His people into cities that need His light. When truth, power, and love collide, joy fills the streets — and we discover what it means to be torchbearers for our city.

When David tried to bring God's presence back to Jerusalem, he learned that the presence of God can't be pushed on a cart — it has to be carried on shoulders. In this message, Ps. Mike unpacks what it means to revere, carry, and steward God's presence with the weight it deserves, and the peace, prosperity, and promotion that are unlocked when we do.

A conversation with Shawn Yeager and Derek Ross at the Imagine If conference in Nashville, TN. We discuss the current state of digital communications and identity with a specific focus on nostr.Date: September 20, 2025Shawn on Nostr: https://primal.net/shawnDerek on Nostr: https://primal.net/derekrossBitcoin Park on Nostr: https://primal.net/park Imagine If: https://bitcoinpark.com/imagineif(00:40) Future of digital comms, identity, social(01:41) Diagnosing the problems: incentives, KYC, and broken trust(03:05) Censorship, shadow bans, and owning your social graph(05:00) AI, deepfakes, and can we trust what we see?(07:24) Algorithmic control vs user choice(10:10) Introducing Nostr: open protocol, healthier engagement(11:54) Digital health, doomscrolling, and parenting challenges(15:21) Youth safety on open protocols: responsibilities and tools(18:22) Give parents the tools: OS-level controls and UX(19:35) Getting started with Nostr: keys, Primal, and UX spectrum(21:17) Vibe-coding apps: Soapbox/Shakespeare on Nostr + Bitcoin(22:39) Permissionless payments and AI-built sitesVideo: https://primal.net/e/nevent1qqs0v7rgjh55wygwuc8pmqvk0qz6qts30uaut2c8lp4dgh9usw2cdpgnznwd9 more info on the show: https://citadeldispatch.comlearn more about me: https://odell.xyz

From the archive: This episode was originally recorded and published in 2022. Our interviews on Entrepreneurs On Fire are meant to be evergreen, and we do our best to confirm that all offers and URL's in these archive episodes are still relevant. From chubby kid to top body transformation specialist, Russ Yeager and his team have helped thousands of people transform their bodies and health without giving up the foods they love. Top 3 Value Bombs 1. Use the slightest mental, physical and emotional energy to get the same result, and use the other energy to accomplish more things. 2. You are one workout away from getting more confidence and better results for your business. 3. Be consistent, shape your body with strength training, look great, and lose your body fat through nutrition. Take care of your joints and muscles by stretching. Sponsor ThriveTime Show - Attend the world's highest rated business growth workshop taught personally by Clay Clark and now featuring Football Star, Tim Tebow, and President Trump's son, Eric Trump, at ThrivetimeShow.com/eofire.