Podcasts about nvc

Send us Fan MailJoin Chris and Richie as they round-up all the news, announcements and reveals from this year's busiest week in gaming! 00:00:42 - Welcome/Housekeeping00:09:36 - PlayStation State of Play00:56:55 - Summer Game Fest01:25:54 - Xbox Games ShowcaseWant more gaming content?

Send us Fan MailJoin Chris and Tom as they round-up all the week's gaming news including a PlayStation State of Play announcement, Lord of the Rings RPG from Warhorse and all the LEGO Batman reviews.00:00:38 - Housekeeping00:01:43 - Whatcha playin? 00:14:08 - The News! 00:14:35 - PlayStation State of Play00:40:01 - Embracer & Lord of the Rings RPG00:58:30 - LEGO Batman Reviews01:05:33 - Yoshi and the Mysterious Book Reviews01:09:11 - Other NewsWant more gaming content?

Send us Fan MailJoin Chris and Richie as they round up all the week's gaming news including stellar reviews for Forza Horizon 6, a new Elite Controller and more...Want more gaming content?

In this episode, Leslie speaks with parent coach, writer, and speaker Margot Magowan about how Nonviolent Communication (NVC) transformed her relationship with her children—and especially helped her family through a painful mental health crisis involving her oldest daughter. After years of therapies, hospitalizations, medications, and conflict, Margot says the breakthrough came when she and her husband learned how to truly listen with presence, curiosity, and compassion. She explains how NVC helped her shift away from trying to control or “fix” behavior and instead understand the feelings and needs beneath it. The conversation explores practical parenting challenges that many families face—from school struggles and emotional outbursts to rules, conflict, and communication—and how changing the way we respond to children can create more trust, safety, and emotional connection. Margot also discusses the difference between “power-over” and “power-with” parenting, why so many parents feel overwhelmed today, and how emotional regulation begins with the adults in the room. It's an honest and compassionate conversation about parenting, connection, and learning how to listen in a whole new way. Margot's website is Listen2ConnectCoach.com and her handles on Instagram are @Listen2ConnectCoach and @reelgirlreviews.

In this episode, Leslie speaks with parent coach, writer, and speaker Margot Magowan about how Nonviolent Communication (NVC) transformed her relationship with her children—and especially helped her family through a painful mental health crisis involving her oldest daughter. After years of therapies, hospitalizations, medications, and conflict, Margot says the breakthrough came when she and her husband learned how to truly listen with presence, curiosity, and compassion. She explains how NVC helped her shift away from trying to control or “fix” behavior and instead understand the feelings and needs beneath it. The conversation explores practical parenting challenges that many families face—from school struggles and emotional outbursts to rules, conflict, and communication—and how changing the way we respond to children can create more trust, safety, and emotional connection. Margot also discusses the difference between “power-over” and “power-with” parenting, why so many parents feel overwhelmed today, and how emotional regulation begins with the adults in the room. It's an honest and compassionate conversation about parenting, connection, and learning how to listen in a whole new way. Margot's website is Listen2ConnectCoach.com and her handles on Instagram are @Listen2ConnectCoach and @reelgirlreviews.

If you listen to this podcast or have worked with me in any of my programs, you are already practicing Nonviolent Communication (whether you realize it or not). Today's guest, Margot Magowan, is an expert on Nonviolent Communication, and she's here to show you how to use those principles for better connection with your kids. You'll Learn:The basic principles of Nonviolent Communication and how to use them in parentingExamples of using NVC in real-life situationsWays that your own needs show up in your parenting (and healthier ways to meet them)How to focus on how your child is feeling, even if their story isn't totally factual-----------------------------------------------------Margot Magowan, a mom of 3, says that learning about Nonviolent Communication helped to transform everything for her family. When her oldest daughter was 15 years old, she started having behavioral health challenges, like refusing to go to school, abusing drugs, and stealing. Over the course of 3 years, she went to various wilderness and residential programs, receiving access to all kinds of support and resources. Now, at age 22, Margot's daughter is thriving. She says, “I really credit it to me and my husband learning how to listen to her.” In her coaching practice, Margot supports other parents in learning how to truly listen to their children with presence and curiosity.The Basics of Nonviolent CommunicationNonviolent Communication (NVC) was created by Marshall Rosenburg, who believes that all human behavior is motivated by an attempt to meet certain universal needs. Margot explains that NVC is made up of 4 parts: observations, feelings, needs, and requests. Take the example of you and your partner getting ready to go to a party, and you're worried you're going to be late. Instead of saying, “We're gonna be late. Hurry up!”, using NVC might look like this:Observation - The invitation says 7:30, and it's 6:30 nowFeeling - I'm feeling anxiousNeed - My need for security isn't being metRequest - Would you be willing to leave in 15 minutes?Margot says that when she first learned this, it felt a little robotic (and her kids hated it when she talked to them that way). She says that what really helped it to feel more authentic was when she focused on her energy rather than her language.Basically, it's not about the script. It's about focusing on connection. This is called NVC Consciousness, which Margot explains as “being open and curious and present and compassionate to whatever is happening.” You're not trying to fix anything (sound familiar?).It goes hand in hand with the Connection Tool that I teach. You're going into the situation as a neutral witness and viewing your child's behavior as an expression of needs or feelings that they don't know how to handle. Ultimately, Nonviolent Communication is:Focusing on your feelingsIdentifying the universal needs underneath those feelingsExpressing that truth honestly, while staying connected to a person's humanityIt's important to keep in mind that the goal of NVC is not to get to the other emotion. Or to get compliance out of our kids. Although these things do sometimes often happen when we show up in a compassionate way. The Universal NeedsThere are quite a few universal needs within NVC (if you want to see them all, Margot has a free list for you here). She helped us out by breaking it down into a few key categories:Connection MeaningAutonomyHonestyPhysical Well-BeingPeacePlayFor example, if you walk into your child's room and find them lying in bed when they're supposed to be cleaning their room, your first thought might be, “Ugh, my kid is lazy. They're not doing what they're supposed to do.”After that initial thought passes, ask yourself, “What need are they trying to meet?” Maybe it's comfort or ease, and this is their best strategy to do that. Then, you can look at the behavior through a more neutral lens.And as a parent, if you're feeling angry, resentful, or frustrated, you probably have some sort of need that's not being met. Be really gentle with yourself in wondering why the situation is upsetting you so much.Margot says that NVC has made her more aware of her own needs and how to get them met. She says, “I was using all 3 of my kids to meet my own needs…I didn't need to shift my kids' behavior to meet my needs.” She figured out new strategies to take care of herself. Now, she sees that a lot of moms hold to strict rules for their kids because they are trying to meet their own need for safety. If you find yourself being rigid somewhere, ask yourself, “What am I scared of? What am I making this mean?” This is how you get to CALM. By managing your own needs and taking care of yourself, you can then show up in a connected, compassionate way for your child. The Giraffe and the JackalIn Nonviolent Communication, Marshall Rosenberg uses two animal metaphors: a Giraffe and a Jackal.The Giraffe is compassionate, open, and curious. The Jackal is more judgemental and angry. One of the things that Margot coaches parents on is spending time with the Jackal when it shows up. And how to get your needs met from someplace other than your kid (having a safe container, like a coach, to bring these feelings and needs to is super helpful). You can ask for this clearly if you're talking to your partner or a friend. Say something like, “I just want empathy. I just want you to listen to me and not try to make it better or fix it or take it away.” You can also do this for yourself in a journal if you need to. Here's the magic. When you show up as the Giraffe and listen to your kid and they feel safe and their nervous system regulates, they reach that state of compassion and curiosity in themselves. Margot says, “I feel like we're doing such a service of actually modeling how to show up for them so they can show up for themselves and be healthy adults.”Challenging ChangeThere is a real obstacle that happens when we change our parenting. Our children want what is reliable and predictable. So even if you've been yelling, this is what they know and expect. When you change your behavior, your kid might not feel like it's trustworthy or safe right away. It's unfamiliar, like you're an imposter. It freaks them out. Margot explains that her kids thought the yelling parents were the authentic ones. They didn't totally trust them when they stopped yelling and started trying this new approach. Your child might even try to pull you back into your own pattern. Their behavior will escalate and they'll almost want you to yell, because that's what they're used to. You have to restrain yourself and stay within your new value system long enough to get all the way through that emotion.Eventually, they will catch up to the new version. And they'll really like this calmer, more connected parent that you're becoming. It just takes some time. Doing something different isn't always easy in the short term, but the long term gains are so worth it.Previous Episodes:Episode 2.16 - The Connection Tool [New & Improved]Connect with Margot:Get the “Feelings & Needs List” that Margot talked about in this episode: https://listen2connectcoach.com/resourcesFollow Margot on Instagram @listen2connectcoach Learn more about her coaching, workshops, and more at https://listen2connectcoach.com/ Free Resources:Get your copy of the Stop Yelling Cheat Sheet!In this free guide you'll discover:✨ A simple tool to stop yelling once you've started (This one thing will get you calm.)✨ 40 things to do instead of yelling. (You only need to pick one!)✨ Exactly why you yell. (And how to stop yourself from starting.)✨A script to say to your kids when you yell. (So they don't follow you around!)Download the Stop Yelling Cheat Sheet hereConnect With Darlynn:Book a complimentary session with DarlynnLearn about the different parenting programs at www.calmmamacoaching.comFollow me on Instagram @darlynnchildress for daily tipsRate and review the podcast on Itunes

Send us Fan MailJoin Chris and Tom as they breakdown all the week's Xbox rebrand, Saros Reviews and the return of Assassins Creed Black Flag! 00:00:41 - Welcome/Housekeeping00:12:30 - The News! 00:13:43 - Somehow Xbox Returned! 00:50:00 - Xbox ID Showcase01:01:08 - Saros Reviews01:11:43 - Assassins Creed Black Flag Resynced01:22:06 - Ubisoft Cancelled Game 'Alterra'Want more gaming content?

Send us Fan MailJoin Chris and Richie as they breakdown all the week's gaming news and reviews for the biggest games of April. 00:00:38 - Welcome/Housekeeping00:10:38 - The News! 00:11:56 - BAFTA Game Awards 202600:18:04 - Pragmata Reviews00:33:27 - Replaced Reviews00:38:10 - Mouse P.I. For Hire Reviews00:44:45 - Assassin's Creed Black Flag Resynced00:54:27 - Metro 2039 Revealed00:59:45 - First Light Bond Theme Revealed01:04:44 - Other NewsWant more gaming content?

In this episode of Engineering Peace, Thom Bond reflects on 15 years of developing and teaching The Compassion Course (http://compassioncourse.org)—a structured approach to teaching Nonviolent Communication and real-world conflict resolution skills.Thom explores how the course has evolved over time, what makes it effective, and why compassion must be practiced as a skill—not just understood as an idea. Drawing on insights from thousands of participants, he shares what it takes to create lasting personal peace and navigate difficult conversations with clarity and care.If you're interested in emotional intelligence, Nonviolent Communication (NVC), or practical tools for resolving conflict, this episode offers a deep and thoughtful perspective.Support the show

Happy Easter from the NVC crew! After a two-week break, host Tosin is back with Shaun Harris and Holly Nessling to dissect a mountain of new releases. From "food porn" gastro-dramas to chaotic ballet slashers, we're helping you decide where to spend your post-holiday cash. On the Big Screen The cinema picks this week range from star-studded dramas to "marmite" sci-fi: Spiltsville undertone The Drama: Zendaya and Robert Pattinson star in this buzzing A24 flick. The crew dives into the "star power" dynamic and debates whether the central conflict is a high-stakes dilemma or just "rich people problems." The Mario Galaxy Movie: Tosin takes the kids to a free screening and... let's just say he's not a fan. We discuss why this billion-dollar hit might be "worse than the first." On the Stream Last One Laughing Season 2 (Amazon Prime): Shaun breaks down the latest battle of the comedians. We talk about Bob Mortimer's masterful return and why Diane Morgan is the queen of the "deadpan." Inside Man (BBC/Streaming): Holly reviews the Stanley Tucci and David Tennant thriller. Is it a masterclass in tension or just too much "madness"? Pretty Lethal: A "madcap" ballet-dancer-meets-Hungarian-gangster movie. Think John Wick with point shoes and razor blades. The Verdict In a decisive win for the home viewers, Streaming takes the week with an average score of 3.6 compared to the 3.1 of the big screen. Enjoying the show? Join the conversation on TikTok, Instagram, and YouTube @NetflixVsCinema! Is Netflix killing cinemas? Each week we weigh up what we've seen in cinemas with what we've watched online at home and figure out which provided the best time. At least, we did before COVID jumped in and declared Netflix, Amazon Prime, Disney + and friends the winner. Listen and subscribe on Apple Podcasts https://podcasts.apple.com/gb/podcast/netflix-vs-cinema/id1448277363 Listen and subscribe on Youtube Music https://www.youtube.com/playlist?list=PL8xPMfsDQIDjM70v1Tah6BiKV4E3UQbaK Listen on Spotify https://open.spotify.com/show/6beXVeSImcgHLsPB22BgE3?si=wdoNI6E0SNqNfoqg4qnw4Q Support Netflix vs Cinema by contributing to their tip jar: https://tips.pinecast.com/jar/netflixvscinema Find out more at https://netflixvscinema.com This podcast is powered by Pinecast.

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'

Send us Fan MailJoin Chris as he breaks down all the weeks gaming news including the Xbox Summer Showcase reveal, The Last of Us Online being cancelled and more...  Want more gaming content?

NVC is based on the idea that "all conflict is a tragic expression of an unmet need." We know something is a need if it's something that everyone in the world wants. Universal human needs are many and include things like love, safety, connection, trust, fun, and more. However, the idea that all conflict is based upon needs is usually a new concept for folks and learning this can be revolutionary in how individuals move through their world - with a lot more ease and clarity. Episode 286 is all about this. We hope you enjoy.

Send us Fan MailJoin Chris and Richie on The GamerGuild Podcast as they round up all the weekly video game news and discussion every Monday on YouTube and Podcast services.Want more gaming content?

Sometimes it's hard to say what you mean. Oren Jay Sofer says, "Communication is a learnable skill and it's one of the most powerful levers for making change in your life and the world." Non-violent communication is about taking responsibility for what we are experiencing using empathy, deep listening, know how to make requests.// This episode is a replay from the Sonya Looney Show. It originally aired October 22, 2020. //Author and renowned meditation instructor Oren Jay Sofer regularly teaches a mindful approach to non-violent communication. spent two and a half years of living as an Anagarika (renunciate) at branch monasteries in the Ajahn Chah Thai Forest lineage. Today, his teaching combines classical Buddhist training with the accessible language of secular mindfulness.  Since the early 2000s, Oren has had a deep interest in the relationship between contemplative practice and communication. A graduate of the BayNVC North American Leadership Training, he has taught classes and workshops in Marshall Rosenberg's Nonviolent Communication (NVC) nationally since 2006. His innovative retreats and online programs in Mindful Communication offer one of the only opportunities in the U.S today to explore the intersection between formal meditation practice, Right Speech and NVC.  Oren  is the founder and Guiding Teacher of Next Step Dharma, an innovative online course focused on bringing the tools of meditation to daily life, and co-founder of Mindful Healthcare.  Oren has created mindfulness programs for organizations, companies, and apps including Apple, Kaiser Permanente, Lumosity, Calm, 10% Happier, Simple Habit and others.I loved his book, Say What You Mean: A Mindful Approach to Nonviolent Communication.  In the book, a main theme is that every thought or feeling is there to try to meet a need.  If you can try to figure out what need your thoughts are tied to, it's easier to articulate what you need to those around you.  It's also useful when listening to someone in a disucssion or conflict to tease out what need they are trying to have met.  I also enjoyed learning about conflict and viewing it as a way to deepen relationships. I also learned that non-violent communication and conflict resolution isn't necessarily to try to get someone to do things your way, it's about deepening understanding of one another because sometimes we simply can't agree to have the same viewpoint.   Non-violent communication has a framework of observation, the feeling, the needs and values to be met, and the request.Three questions you can ask yourself are what happened, how do I feel about it, and why?I also loved learning about how to use mindfulness in listening and communication as well as how to ground yourself in your own body when tensions rise.Topics Discussed in the Podcast from childhood actor to meditation instructor4 types of conflict avoidanceself-empathytools for internal pressureNo mud, no lotusaddressing the voiceless and gender constructshow to make requests of othersResourcesOren Jay Sofer's websiteGet Oren's book: Say What You Mean: A Mindful Approach to Nonviolent Communication--------------The Grow the Good Podcast is produced by Palm Tree Pod Co. 

Send a textJoin Chris for The GamerGuild Podcast as he rounds up all the weeks video game news.Want more gaming content?

Dear Listener, does communicating with your partner sometimes feel like an uphill battle? Do you find yourself saying things you don't mean—or struggling to say what you do mean without it landing as an attack? What if there were a way to communicate that actually brought you closer, even during conflict?In this episode, we're joined by Relationship Center therapist and couples counselor Nicole Penrod to explore Nonviolent Communication (NVC)—a powerful framework for transforming how you and your partner talk to each other.Nicole breaks down the basics of NVC (also called compassionate communication), originally developed by Marshall Rosenberg. At its core, NVC helps us move from reactive, judgmental communication to empathetic, connecting conversation. Think less jackal (defensive, fear-driven) and more giraffe (big-hearted, slow, and steady).We walk through the four steps of NVC—Observation, Feeling, Need, Request (OFNR)—with real examples, including Jessica getting pretend-mad at Josh about socks on the floor. You'll learn why "I feel abandoned" isn't actually a feeling, how to set your partner up for success (and vice versa!), and why asking for what you want can help heal attachment wounds.If you're tired of the same old fights and ready to communicate with more compassion—for your partner and yourself—this episode is for you.Key Takeaways0:00 Intro06:07 What is NVC?10:45 What are the NVC basics?18:28 Name the Need21:04 Requests Without Demands32:01 How do I actually use NVC with my partner?Resources and linksDecolonizing NVCBook: Decolonizing Non-Violent CommunicationPodcast episode with the author: https://www.skepticspath.org/podcast/decolonizing-nonviolent-communication-with-meenadchi/Feelings and Needs Lists: https://www.sociocracyforall.org/nvc-feelings-and-needs-list/Nicole's favorite video introduction of the basics: https://roxannemanning.com/an-introduction-to-nvc/On the 4 listening modes: https://seedofpeace.org/nvc-introductory-articles/four-ways-of-listening/Have a question or comment? Email us at podcast@relationshipcenter.com. We love hearing from you!If you'd like to work with one of the talented clinicians on our team, go to relationshipcenter.com/apply-now to apply for a free 30-minute consultation.To get a monthly email with our best content, go to relationshipcenter.com/newsletter.If something in this episode touched you, will you share it with a friend? That helps us reach more sweet humans like you.Lastly, we'd love it if you would leave us a rating and review wherever you listen to podcasts. And be sure to hit subscribe while you're there so you never miss an episode!

Send a textJoin Chris and Richie as they breakdown all the week's gaming news including the full shake-up of Xbox leadership, Pokémon confirming Gen 10, Wolverine landing a launch date and all the Resident Evil Requiem reviews rounded up! 00:03:23 - What We're Playing00:12:22 - The News! 00:13:10 - Pokémon Direct Breakdown00:31:45 - Resident Evil Requiem Reviews00:47:11 - Xbox Leadership Changes01:29:29 - Wolverine Release DateWant more gaming content?

Send a textWelcome to The GamerGuild Podcast! Your weekly show where three best friends round up and discuss all the week's gaming stories and news.00:00:40 - Welcome/Housekeeping00:03:50 - What We've Been Playing00:12:25 - The NEWS!00:13:05 - BluePoint Shut Down!00:52:55 - Pokemon Presents Direct + Fire Red Leaf Green01:02:00 - More Far Cry and Assassins Creed in Development01:06:05 - Rayman 30th Anniversary Controversy01:13:15 - Christopher Judge Hints at next God of War?01:17:30 - Sex in Video Games - Should GoW Remakes Keep Minigames01:26:05 - High on Life 2 Reviews01:28:55 - Metal Gear Solid 4 and Peace Walker DelistedEnjoy more GamerGuild content!

【マインドフルネスは、働く人の武器になる】 「心が弱いから整えるのではありません。力を発揮するために、整えるんです。」 マインドフルネス伝道師・ガネーシャ尾上さんは、マインドフルネスを“特別な人のもの”ではなく、働く人が日常で使える実践的な技術として伝えています。 瞑想、NVC（共感的コミュニケーション）、アーユルヴェーダ。 この3つを柱に、心と体を同時に整えていく。 一度きりではなく、3か月かけて毎日少しずつ習慣化することで、自己肯定感が高まり、人間関係が変わり、仕事の生産性や収入まで変化していく人が増えています。 尾上さん自身も、かつては自己肯定感が低く、38歳のときに心身の不調を経験しました。 その中で出会ったマインドフルネスが、薬に頼らず心を回復させ、人生を大きく変えたといいます。 志はただ一つ。 「全ての働く人が心を整えて、自分の真価を発揮できる社会をつくる」 忙しい経営者、リーダー、頑張り続けているあなたにこそ、静かに、しかし確実に響くエピソードです。 【今回のゲスト】 マインドフルネス伝道師 ガネーシャ尾上さん Podcast番組：いまここマインドフルトーク https://stand.fm/channels/68935a15b09e6a462a72cde4

I am Dr. Shinoah Taylor, wholistic U.S. Board Certified Doctor of Chiropractic of 55 years, 22 of them serving Dominica full time as sole proprietor of Quantum Leap; 18 years serving Antigua part-time; and the rest as a sole proprietor of 3 other  practices in Kentucky and Tennessee in the U.S.  I also was the CEO of Rainforest Shangri-La Resort, an eco- tourism and sustainable living facility on Dominica which I helped to build. For 18 years I wrote à health column “Health Wealth” for a local Dominican newspaper. In 2016 I published my first book DOG WITH THE CROOKED EAR, a Spiritual Journey of Darkness into Light. I am now retired, but not from bein the mother of 2 amazing adult children, born at home and home schooled.I carry a wealth of knowledge, experience and wisdom in wholistic health and am a living example of the self-responsibility model. I am well versed  in diet, nutrition, exercise, fitness,  stress management, Applied Kinesiology, herbology, Reiki, massage therapy, Touch for Health, sound bath ( crystal bowls), meditation, motivational speaking, child adjusting, homebirth, homeschooling, yoga, full moon ceremonies, non violent communication (NVC),  poet, and creator of THE DIVINE FEMININE QUANTUM  LEAP an 8 hour indoor/outdoor adventure to raise female vibrations._______________________________________________________________________________________Join The Buff Muff Method https://get.buffmuff.com/methodRejuve is a line of pelvic health and whole body health supporting supplements that are helping women have a daily poogasm, eliminate leaks and prolapse symptoms, and keep their vulvovaginal tissues supple and resilient. Get your Rejeuve Supplements https://rejeuve.com/ and use code Podcast to save 10% off your first order.Thank you so much for listening! I use fitness and movement to help women prevent and overcome pelvic floor challenges like incontinence and organ prolapse. There is help for women in all life stages! Every Woman Needs A Vagina Coach! Please make sure to LEAVE A REVIEW and SUBSCRIBE to the show for the best fitness and wellness advice south of your belly button. *******************I recommend checking out my comprehensive pelvic health education and fitness programs on my Buff Muff AppYou can also join my next 28 Day Buff Muff Challenge https://www.vaginacoach.com/buffmuffIf you are feeling social you can connect with me… On Facebook https://www.facebook.com/VagCoachOn Instagram https://www.instagram.com/vaginacoach/On Twitter https://twitter.com/VaginaCoachOn The Web www.vaginacoach.comGet your Feel Amazing Vaginal Moisturizer Here

In this episode you listen in as Thom interviews his own AI clone to find out if this technology can be genuinely life-serving. Find out for yourself, as Thom talks with a clone that has "memorized" his entire book and listened to a year's worth of Thom's trainings and conferences.Support the show

Send us a textIn Episode 238, Andrea Atherton explores the transformative power of Nonviolent Communication (NVC), a practice that teaches us how to speak from the heart while staying deeply connected to ourselves and others. Many of us were never taught how to express our feelings and needs without blame, shame, or defensiveness—and as a result, our most important relationships can feel fractured, distant, or painful. In this episode, Andrea guides listeners through what NVC really is, why it matters, and how it can create safety and understanding even in the most challenging conversations.Andrea breaks down the four core components of NVC—observations, feelings, needs, and requests—demonstrating how this framework allows us to speak our truth with clarity, compassion, and courage. She shares insights from her work as a psychotherapist and love expert, helping listeners recognize common patterns that trigger disconnection and showing how small shifts in communication can profoundly transform relationships.This episode is a practical and gentle guide for anyone seeking to deepen connection, repair ruptures, and foster empathy in their personal and professional relationships. Whether you are navigating romantic partnerships, family dynamics, friendships, or your inner dialogue, Andrea offers a step-by-step approach to speaking and listening in ways that honor both yourself and others. Listeners will leave with tools to communicate more honestly, create understanding, and cultivate relationships that thrive on presence and compassion.30-minute Consultation with Andrea https://www.andreaatherton.com/booking-calendarAndrea Atherton Websitehttps://www.andreaatherton.com/Love Anarchy Websitehttps://www.andreaatherton.com/podcasthttps://loveanarchypodcast.buzzsprout.comLove Anarchy Facebookhttps://www.facebook.com/loveanarchypodcast/Andrea Atherton Facebookhttps://www.facebook.com/andreaatherton-17/

Molly Graham has worked for some of tech's most effective leaders, including Mark Zuckerberg, Sheryl Sandberg, Chamath Palihapitiya, and Bret Taylor. Today she leads Glue Club, a community for leaders navigating rapid scale, growth, and change. She's best known for her “Give away your Legos” framework and her collection of practical mental models for leading through hypergrowth.We discuss:1. “Give away your Legos”: a framework for scaling yourself as a leader2. “J-curves vs. stairs”: the two paths of career growth, and why you should pick the scarier path3. “The waterline model” for diagnosing team problems (and why you should “snorkel before you scuba”)4. Six rules for creating effective goals (and aligning everyone around them)5. Rules of thumb for leading through rapid scale and change6. Her biggest leadership lessons from Mark Zuckerberg, Sergey Brin, Larry Page, Sheryl Sandberg, and Bret Taylor—Brought to you by:DX—The developer intelligence platform designed by leading researchersBrex—The banking solution for startupsGoFundMe Giving Funds—Make helping a habit—Transcript: https://www.lennysnewsletter.com/p/the-high-growth-handbook-molly-graham—My biggest takeaways (for paid newsletter subscribers): https://www.lennysnewsletter.com/i/182877855/my-biggest-takeaways-from-this-conversation—Where to find Molly Graham:• X: https://x.com/molly_g• LinkedIn: https://www.linkedin.com/in/mograham• Substack: https://mollyg.substack.com• Website: https://glueclub.com—Where to find Lenny:• Newsletter: https://www.lennysnewsletter.com• X: https://twitter.com/lennysan• LinkedIn: https://www.linkedin.com/in/lennyrachitsky/—In this episode, we cover:(00:00) Introduction to Molly Graham(04:28) Molly's background at Google, Facebook, Quip, and CZI(11:29) The “Give away your Legos” framework(16:44) Managing your inner monster(19:49) When not to give away your Legos(21:28) Embracing a long career(23:25) The J-curve vs. stairs approach to career growth(32:00) The gift of knowing yourself(34:28) Learning to be a professional idiot(38:30) The waterline model: snorkel before you scuba(47:16) Six rules for creating strong alignment around goals(57:15) Rules of thumb for leading through rapid scale(01:07:49) Investing in high performers vs. low performers(01:10:54) Lessons from Zuckerberg, Sandberg, and Bret Taylor(1:21:15) Pivoting from ambition to purpose(1:26:32) Finding stability in instability(01:29:44) Final thoughts—Referenced:• Making an impact through authenticity and curiosity | Ami Vora (CPO at Faire, ex-WhatsApp, FB, IG): https://www.lennysnewsletter.com/p/authenticity-and-curiosity-ami-vora• Sheryl Sandberg on LinkedIn: https://www.linkedin.com/in/sheryl-sandberg-5126652• Elliot Schrage on LinkedIn: https://www.linkedin.com/in/elliotschrage• Quip: https://quip.com• He saved OpenAI, invented the “Like” button, and built Google Maps: Bret Taylor on the future of careers, coding, agents, and more: https://www.lennysnewsletter.com/p/he-saved-openai-bret-taylor• Chan Zuckerberg Initiative: https://chanzuckerberg.com• 10 contrarian leadership truths every leader needs to hear | Matt MacInnis (Rippling): https://www.lennysnewsletter.com/p/10-contrarian-leadership-truths• ‘Give Away Your Legos' and Other Commandments for Scaling Startups: https://review.firstround.com/give-away-your-legos-and-other-commandments-for-scaling-startups• The Muppets: https://muppets.disney.com• Sara Caldwell on LinkedIn: https://www.linkedin.com/in/saramcaldwell• J-Curves vs. Stairs: Two Approaches to Career Growth: https://mollyg.substack.com/p/j-curve• Forget the corporate ladder—winners take risks: https://www.ted.com/talks/molly_graham_forget_the_corporate_ladder_winners_take_risks• Chamath Palihapitiya on LinkedIn: https://www.linkedin.com/in/chamath• Lori Goler on LinkedIn: https://www.linkedin.com/in/lori-goler-6b96921• Joseph Campbell's quote: https://www.goodreads.com/quotes/192665-the-cave-you-fear-to-enter-holds-the-treasure-you• Zevi Arnovitz on LinkedIn: https://www.linkedin.com/in/zev-arnovitz• Peopling 101: The Waterline Model: https://christinehaskell.com/blog/peopling-101-the-waterline-model• Introduction to NVC: https://www.cnvc.org/learn/what-is-nvc• I hate OKRs... and other thoughts about goal setting: https://mollyg.substack.com/p/i-hate-okrs-and-other-thoughts-about• Lessons from scaling Stripe | Claire Hughes Johnson (former COO of Stripe): https://www.lennysnewsletter.com/p/lessons-from-scaling-stripe-tactics• James Clear's quote: https://www.goodreads.com/quotes/9614600-problem-1-winners-and-losers-have-the-same-goals• Founder mode: https://paulgraham.com/foundermode.html• Stripe: https://stripe.com• Patrick Collison on X: https://www.linkedin.com/in/patrickcollison• John Collison on X: https://x.com/collision• Seth Godin's best tactics for building remarkable products, strategies, brands and more: https://www.lennysnewsletter.com/p/seth-godins-tactics-for-building-remarkable-products• Eric Antonow on LinkedIn: https://www.linkedin.com/in/antonow—Recommended books:• The Artist's Way: https://www.amazon.com/Artists-Way-25th-Anniversary/dp/0143129252• Scaling People: Tactics for Management and Company Building: https://www.amazon.com/Scaling-People-Tactics-Management-Building/dp/1953953212• Atomic Habits: An Easy & Proven Way to Build Good Habits & Break Bad Ones: https://www.amazon.com/Atomic-Habits-Proven-Build-Break/dp/0735211299—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com.—Lenny may be an investor in the companies discussed. To hear more, visit www.lennysnewsletter.com

728. Nonviolent communication, or NVC, is a communication strategy—and also a lens through which you can look at life—that can be used to connect with others and resolve conflict in a respectful and compassionate way.Find a transcript here.Have a parenting question? Email Dr. Coor at parenthood@quickanddirtytips.com or leave a voicemail at 646-926-3243.Find Project Parenthood on Facebook and Twitter, or subscribe to the Quick and Dirty Tips newsletter for more tips and advice.Project Parenthood is a part of Quick and Dirty Tips.Links: https://www.quickanddirtytips.com/https://www.quickanddirtytips.com/subscribehttps://www.facebook.com/QDTProjectParenthoodhttps://twitter.com/qdtparenthoodhttps://brooklynparenttherapy.com/ Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Welcome to another insightful episode of The Brand Called You! In this conversation, host Ashutosh Garg sits down with Paulina Orbitowska-Fernandez, a certified trainer of Nonviolent Communication (NVC), scrum coach, mediator, and resonant language practitioner from Warsaw, Poland.Paulina shares her powerful journey from her early years in communist Poland to becoming a global advocate for empathy, NVC, and authentic leadership. Discover what truly inspired her to pursue communication and empathy, the challenges leaders and organizations face today, and the transformative potential of NVC beyond just “being nice.” You'll learn about the neuroscience of empathy, how listening shapes culture, and practical ways organizations can foster trust and psychological safety.Paulina also talks about the internationally recognized “Time for Empathy” initiative—a week-long, global series of free empathy workshops. Tune in to learn practical tools and gain wisdom to make your organizations and relationships more compassionate and effective.

In this week's conversation, Vanessa brings forward the pain of a friendship that feels increasingly one-sided. Together, we explore the difference between situational limits and structural limits in relationships, how to trust the “data” we receive when others shut down, and the grief that comes with realizing we may be doing too much emotional labor.We explore how to discern when to keep engaging, when to step back, and how to communicate desires for mutuality without blame. We also look at why some people can talk the talk of empathy yet still struggle to walk it in relationships. And, how to honor our own boundaries when reciprocity is missing.Listener Takeaways•Learn how to interpret someone's emotional shutdowns as information about capacity rather than a reflection on your delivery.•Recognize the signs of over-functioning in friendships and how to stop carrying all the emotional labor.•Practice asking direct but compassionate questions that clarify whether mutuality is truly present.•Understand the developmental stages of NVC practice and why some people can use the tools for their own needs but not yet offer reciprocity.•Embrace grief as a necessary step when relationships aren't mutual, while keeping your heart open to future possibilities. For ongoing practice and deeper learning, join my monthly membership program. You will find a safe space for live discussions and a supportive community of like-minded, open-hearted humans. Stay updated on new episodes and resources by subscribing wherever you listen to podcasts or visiting yvetteerasmus.com. Here are more ways to connect with me: Join the School of Human Connection Hop on one of our live calls Check out my YouTube page

Are you and your partner stuck in the same arguments over and over? In this episode, which is the third in my new series called "Common Communication Patterns That Keep Couples Stuck — And How to Get Unstuck," I'll break down how rushing to get through a conflict might feel like progress, but is ultimately unproductive and keeps you stuck and frustrated.  I'll introduce my Heart-Centered Conflict Navigation Roadmap, an NVC-based approach that guides couples through conflict in a connecting, productive, and efficient way. You'll learn why slowing down, empathic understanding, and heart-centered communication are the keys to resolving conflict in a way that's collaborative, creative, and lasting. Plus, I'll share simple + practical tips you can start using today to move from "me vs. you" to "we're in this together," and why a few focused minutes of connection can save you hours of fruitless fighting. If you've ever thought, "We don't have time for this," or "We know each other's needs, but we're still stuck," this episode is for you.   Want to learn NVC with Ali? Training + Coaching Explore my 9-week private coaching program for couples: Stop Fighting! (without stuffing your feelings or sacrificing your needs): https://www.alimillercoaching.com/stopfighting Free Resources Feelings & Needs Cheatsheets: https://www.alimillercoaching.com/feelingsandneeds Free Mini-Course: The 4 Steps to Stop Any Fight Without Giving In https://www.alimillercoaching.com/freeminicourse Connect with Ali Instagram: @alimillercoaching Free Private Facebook Group: NVC for Couples https://www.facebook.com/groups/nvcforcouples Email: ali@alimillercoaching.com Website: https://www.alimillercoaching.com

In this powerful episode of The Circle of Hope, I'm thrilled to welcome Linda Balola, a lecturer and peacebuilder whose journey from the Democratic Republic of Congo to Rwanda has been marked by transformation, learning, and the courage to shift entire communities toward healing. Our story together began serendipitously in Nairobi, Kenya, when Linda recognized me from my TEDx talk—a beautiful reminder of how messages ripple globally, touching lives we may never even imagine reaching.Linda opens up about her personal evolution, moving from deep-seated judgments and cultural stereotypes to embracing the transformative principles of Nonviolent Communication (NVC). We dig into how she not only teaches these practices at the Protestant University of Rwanda but lives them—helping young people from conflict-impacted backgrounds explore empathy, process trauma, and rewrite how they relate to themselves and others. Our candid conversation explores the role of needs, feelings, and strategies for authentic connection and dives into our own real-life struggles and triumphs using NVC (including my very human experience navigating emotions at Costco!). If you're curious about building peace in divided communities, shifting personal relationships, or simply want to understand yourself and others more deeply, this heartfelt exchange is for you.Watch This If:You're curious about how Nonviolent Communication (NVC) works in real lifeYou want practical strategies for transforming conflict—personally or within your communityYou're interested in peacebuilding, empathy, and authentic relationshipsYou've ever struggled with communicating your needs, expressing emotions, or breaking through stereotypesYou're looking for inspiration from someone living and teaching hope amid challenging circumstancesQuotes to Remember:“Everything we do, we do to meet the needs... Even if you commit something that is not good, know that you still have something good inside.” – Linda Balola“Sometimes our needs are not meant to be met by other people. The need that we have are needs that we need to fulfill—we then select strategies that would address that need for us.” – Valerie Hope“Nonviolent Communication is not a therapy session, but it can heal.” – Linda Balola“Beyond right or wrong, we can still connect.” – Linda BalolaWhat You'll Learn:The fundamental components of Nonviolent Communication and their practical applicationHow to shift from habitual judgment (“jackal”) to empathic (“giraffe”) listening and expressionThe importance of identifying and owning your own needs in moments of conflictHow transparency and self-connection foster resilience and understanding, even in trauma-impacted settingsWays to compassionately hold space for strong emotions—both your own and others'Why cultural and personal stereotypes can be overcome through intentional connectionHow even compliments and praise can be forms of judgment, and the value of specificity in affirmationContact Information:Guest: Linda BalolaInstagram: https://www.instagram.com/lindaducc?igsh=am44NDBpOTFxNDNlLinkedIn: http://linkedin.com/in/linda-balola-sylvine-2a2b36183Facebook: https://www.facebook.com/share/1HwgWCZrm1/?mibextid=wwXIfrHost: Valerie HopeWebsite:https://www.valeriehope.comInstagram:https://www.instagram.com/valeriehope/LinkedIn:https://www.linkedin.com/in/valeriehope/Facebook:https://www.facebook.com/ValerieVHopeYoutube:https://www.youtube.com/@ConnecttoJoyProduction Support: Lucy Hope - Podcast Editing, Copy, and Publishing.#CircleOfHope #NonviolentCommunication #PeaceBuilding #Empathy #TransformConflict

Transforming your health is more fun with friends! Join Chef AJ's Exclusive Plant-Based Community. Become part of the inner circle and start simplifying plant-based living - with easy recipes and expert health guidance. Find out more by visiting: https://community.chefaj.com/ For a list "The Top 10 Things Having Cancer Has Taught Me" please email help@ChefAJ.com Disclaimer: This podcast does not provide medical advice. The content of this podcast is provided for informational or educational purposes only. It is not intended to be a substitute for informed medical advice or care. You should not use this information to diagnose or treat any health issue without consulting your doctor. Always seek medical advice before making any lifestyle changes. To book a consultation with Matt: https://form.jotform.com/241997228318164 Matthew Lederman, MD, is a board-certified Internal Medicine Physician and leading innovator in holistic health. Known for integrating plant-based nutrition, Nonviolent Communication (NVC), trauma-informed care, and lifestyle medicine, he emphasizes the deep connection between physical, emotional, and relational well-being. A certified NVC Trainer through the Center for Nonviolent Communication (CNVC), Dr. Lederman blends Polyvagal Theory, Somatic Awareness, and Pain Reprocessing to help people address root causes of chronic health issues, build emotional resilience, and strengthen meaningful connections. He co-hosts the webe Parents podcast and is the author of Wellness to Wonderful, which unites medical science, psychology, spirituality, and life wisdom to guide individuals toward lasting health and joy. He also co-founded Kinectin, an AI-driven platform for cultivating deeper, more fulfilling relationships. Dr. Lederman has co-authored six books—including the New York Times bestseller Forks Over Knives Plan—and appeared in the acclaimed documentary Forks Over Knives. He has served as Vice President of Medical Affairs at Whole Foods Market, lectured for eCornell, taught in medical schools, and co-created the webe kälm device for emotional regulation. As co-founder of Connection Docs, he integrates NVC and emotional health with practical, science-backed tools that foster resilience, balance, and meaningful relationships for individuals and families. Email (questions & requests): Support@ConnectionDocs.com Website: https://www.connectiondocs.com/ Free Resources (includes Feelings & Needs Sheet for children AND Role-Play Video “Talking to Your Child About ‘Too Much' Device Time”) : https://www.connectiondocs.com/resources Substack (Weekly Articles on Connection): https://substack.com/@connectiondocs Breath & Body Regulation Training Tool: https://webekalm.com/ webe Pärents Podcast https://webekalm.com/pages/webeparents AI Connection Coach:https://app.kinectin.com/signup Main Book WELLNESS TO WONDERFUL: 9 Pillars for Living Healthier, Longer, and with Greater Joy: https://www.amazon.com/dp/B0C2S1JGZK?ref=cm_sw_r_ffobk_cso_sms_apin_dp_K6HM5P02NNK5WAMRGE87&ref_=cm_sw_r_ffobk_cso_sms_apin_dp_K6HM5P02NNK5WAMRGE87&social_share=cm_sw_r_ffobk_cso_sms_apin_dp_K6HM5P02NNK5WAMRGE87&starsLeft=1&skipTwisterOG=1&bestFormat=true Children's E-Books (Supporting Children Bringing More Connection Into Their Lives): Healing Shame and Connecting to Self-Worth and Intrinsic Value: https://webekalm.com/products/lily-and-her-beautiful-flower Being Honest with Care https://webekalm.com/products/ella-and-the-two-gifts-ebook Supporting Children During Emergencies (fires, earthquakes, etc):'https://webekalm.com/products/brave-hearts-facing-the-fire-ebook Social Media: Instagram: https://www.instagram.com/TheConnectionDocs Substack Newsletter: https://connectionDocs.substack.com Facebook: https://www.facebook.com/connectionDocs X: https://x.com/connectionDocs

You asked your partner to do something, they said they'd do it… and they didn't. And now you're frustrated, wondering if your partner really cares or if you're asking for too much. If this dynamic feels familiar, you're not alone — and it's not because your partner is a jerk. In most relationships, missed follow-through has far more to do with unmet needs, unclear communication, or shifting capacity than a lack of love. This episode is Part 2 of my series, Common Communication Patterns That Keep Couples Stuck — and How to Get Unstuck. Today, we explore 5 compassionate reasons your partner might say "yes" and then not follow through — and how you can respond in ways that create closeness rather than conflict. You'll learn how to make requests that actually land, invite honest yes's and no's, and build (and rebuild!) agreements that support both people's needs. By the end, you'll walk away with practical tools, deeper understanding, and a new way of seeing your dynamic — so you can move out of frustration and into true partnership. And if this episode resonates, share it with your partner — it's a beautiful way to start the conversation together. Want to learn NVC with Ali? Explore my 9-week private coaching program for couples: Stop Fighting! (without stuffing your feelings or sacrificing your needs). Includes my signature training: Hearing Each Other's Hearts: NVC Essentials for Couples Learn more: www.alimillercoaching.com/stopfighting Free Resources Feelings & Needs Cheatsheets: www.alimillercoaching.com/feelingsandneeds Free Mini-Course: The 4 Steps to Stop Any Fight Without Giving In www.alimillercoaching.com/freeminicourse Connect with Ali Instagram: @alimillercoaching Free Private Facebook Group: NVC for Couples www.facebook.com/groups/nvcforcouples Email: ali@alimillercoaching.com Website: www.alimillercoaching.com

Sara Di Gregorio: Rebuilding Agile Team Connection in the Remote Work Era Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "The book helped me to shift from reacting to connecting, which completely changed the quality of conversation." - Sara Di Gregorio   When COVID forced Sara's team into full remote work, she noticed something troubling—the team was losing real connection. Replicating in-office meetings online simply didn't work. People attended meetings but weren't truly present. The spontaneous coffee machine conversations that built relationships and surfaced important information had vanished.  So Sara started experimenting. She introduced 5-minute chit-chat sessions at the start of every meeting: "Guys, how are you today? What happened yesterday?" She created "coffee all together" moments—10-minute virtual breaks where the team could drink coffee or have aperitivos together, sometimes three times per week. She established weekly feedback sessions every Friday morning—30 minutes to recap the week and understand what could improve.  These weren't just social niceties; they were deliberate efforts to recreate the human connections that remote work had stripped away. Sara recognized that mechanized interactions—"here are the things I need you to do, let's talk next steps"—kill team dynamics. Teams need moments where they relate to each other as people, not just as functions.  The experiments worked because they created space for genuine connection, allowing the team to maintain the trust and collaboration that makes effective teamwork possible, even when working remotely.   In this episode, we refer to Non-Violent Communication concepts and practices.   Self-reflection Question: How are you creating moments for your remote or hybrid team to connect as people, not just as colleagues executing tasks? Featured Book of the Week: Nonviolent Communication by Marshall Rosenberg Sara credits Nonviolent Communication by Marshall Rosenberg (translated in Italian as "Words are Windows, or They are Walls") as having a deep impact on her career. The book explores how to listen without judging, how to ask the right questions, and how to observe people to understand their real needs. But above all, it teaches how to communicate in a way that builds connection rather than creating barriers.  For Sara, the book was remarkably practical—she didn't just read it, she experimented with the techniques afterward. She explains: "I think that without this mindset, it's easy to fall into reactive communication, trying to defend, justify, or give quick answers. But that often blocks real understanding." The book helped her shift from reacting to connecting, which completely changed the quality of her conversations.  As a Scrum Master working with people every day—facilitating meetings, mediating conflicts, supporting teams—the way we communicate determines whether we open dialogue or close it. Sara found that taking time to reflect instead of giving quick answers transformed her ability to help teams discover dependencies, improve dialogue, and address communication issues. For anyone in the Scrum Master role, this book provides essential skills for building the kind of connection that makes true collaboration possible. In this segment, we also refer to the NVC episodes we have on the podcast. Check those out to learn more about Nonviolent Communication   [The Scrum Master Toolbox Podcast Recommends]

“Language can either divide us or bring us home to each other.”In this soulful conversation, Marina and Jawdat explore how Nonviolent Communication (NVC) becomes a bridge — between people, between cultures, and within ourselves. Jawdat, a lawyer and facilitator with Army of Healers, shares his work using dialogue, storytelling, and NVC to support trauma healing and collective reconciliation. Together, we explore how to communicate from compassion instead of defense, transform tension into deeper connection, bring awareness and healing into justice work, and use the body as a compass for honest, grounded expression.This episode invites us to see communication not just as words, but as an embodied act of love, repair, and truth.Connect with Jawdat:https://www.instagram.com/jdkassabhttps://jawdatkasab.wixsite.com/appraiser❥Softening into self- 3 month 1:1 with Whats App Support:https://marina-yt.mykajabi.com/offers/PAWQhZHu❥❥1:1 Coaching with me: https://docs.google.com/forms/d/e/1FAIpQLSfWcZM5s9c2OjOLwoGMI5jE6rh_JAzjN2d_vCtuVe7e3pVGxw/viewform❥❥❥Stay or Go Course: ⁠https://marinayt.com/stay-or-go⁠ ❥❥❥❥ FREE RESOURCE: a step-by-step process of working with your triggersTRIGGERED TO ROOTED: A ROADMAP TO CREATE TREASURES FROM YOUR TRIGGERSThis powerful step by step process will walk you through how to somatically move through a trigger, ground yourself, allow the emotions to come up and experience massive growth in your lifeDownload here:⁠ ⁠https://marinayt.com/trigger-2-rooted⁠⁠Follow me on Instagram:⁠ ⁠www.instagram.com/marina.y.t⁠⁠ Subscribe to YouTube: http://www.youtube.com/@marinatriner Top Episode Quotes:“Language is not neutral — it can be a weapon or a bridge.”“Compassion doesn't mean agreeing. It means staying present with humanity.”“We can't heal collectively without learning how to listen.”nonviolent communication, trauma healing, conflict transformation, empathy, peacebuilding, nervous system regulation, heartspace podcast, marina yanay triner, jawdat kasab, trauma informed communication, collective healing, nervous system awareness, self compassion, embodiment, emotional regulation, healing podcast, inner healing, community healing

In this episode of Love Each Other Better, I'm kicking off a new series on the communication patterns that keep couples stuck — and how to get unstuck. We're starting with one of the most common: when one partner talks more and more to feel heard, while the other gets overwhelmed and pulls away to find relief. It's a loop that leaves both people feeling disconnected, even though both are trying. I'll introduce a powerful concept from Nonviolent Communication: interrupting for the sake of connection. It's a way to pause, reflect, and stay present without shutting each other down. We'll also talk about reflective listening, and how it can radically shift the energy of a conversation in an instant. If you've ever felt like you're talking past each other instead of with each other, this one's for you.  Want to learn NVC with Ali? Explore my 9-week private coaching program for couples: Stop Fighting! (without stuffing your feelings or sacrificing your needs). Includes my signature training: Hearing Each Other's Hearts: NVC Essentials for Couples Learn more: www.alimillercoaching.com/stopfighting Free Resources Feelings & Needs Cheatsheets: www.alimillercoaching.com/feelingsandneeds Free Mini-Course: The 4 Steps to Stop Any Fight Without Giving In www.alimillercoaching.com/freeminicourse Connect with Ali Instagram: @alimillercoaching Free Private Facebook Group: NVC for Couples www.facebook.com/groups/nvcforcouples Email: ali@alimillercoaching.com Website: www.alimillercoaching.com

Send us a textRelationship expert warrior for love, Jonathon Aslay, shares insights, secrets and tips for zoning in on the perfect partner, and the ability to be radically authentic as a sexy, soul mate attracter. We have a blast discussing not only dating but exploring how to fortify relationships of all kind through compassionate communication. This one's a game-changer. Curiosity + Intentionality are the doorways to secure connection.Attachment spotting: ask about past relationships; listen for ownership.NVC in 3 steps: what happened → how I feel/need → are you willing…?Appreciation daily: aim for ~80% positive acknowledgments—tiny, specific, frequent.Micro-rituals: 20–120 second hugs, “I see you when…,” bedtime check-ins, weekly “state of us.”Friendship first: prioritize liking each other—rabbit-hole chats, shared curiosity, play.Requests from love: trade criticism for clear, kind asks.Grief alchemized: asking “What would love do?” creates meaning and gentleness.Try this tonight“When you did ___, I felt ___ because I need ___. Are you willing to ___?”Give three appreciations (specific!) before bed.30-second hug, slow breathing, no words.Schedule a weekly connection date (phones away): one curiosity question each.GuestJonathon Aslay — Relationship coach; host of What Would Love Do?; author of What the Heck Is Self-Love, Anyway?Support the showLink to Support this Channel: https://www.buzzsprout.com/2153284/supporters/newJulie's Book: https://amzn.to/3K2ZS05Julie's Website for more information, comments or requests: https://lifeofloveandjoy.comI receive a small commission when you purchase from these links.

In this special episode of Love Each Other Better, I sat down with Brian G. Murphy — author of Love Beyond Monogamy, certified relationship coach, and co-founder of the Queer Theology podcast. In this illuminating interview, Brian shares insights on navigating non-monogamy and open relationships, including: How to navigate differing desires between partners and approach the conversation about opening a relationship Handling jealousy and fostering intentional, authentic communication Why even couples who choose to stay monogamous can benefit from exploring these questions consciously Aligning relationships with personal values while considering the impact on your partner Whether you're exploring the possibility of an open relationship, looking for support in your already-established open relationship, or simply looking to build more authenticity and intentionality into your monogamous partnership, don't miss this opportunity to get high-integrity guidance and insights from Brian G. Murphy. About Ali's Guest Brian G. Murphy is an author and certified relationship coach helping people build thriving relationships on their own terms without shame or "shoulds" through his coaching practice Relationshift. He's also the co-founder of QueerTheology.com, a resource hub, online community, and the longest-running queer spirituality podcast which helps LGBTQ+ and polyamorous people heal from religious harm and live into their values. He is the author of Love Beyond Monogamy and co-author of Reading The Bible Through Queer Eyes, which will be published by HarperOne in fall 2026. Connect with Brian G. Murphy Social Media: @thisisbgm on all the places, but especially Instagram, Threads, and YouTube Website: https://www.thisisbgm.com Free Commitment Clarity Checklist - http://thisisbgm.com/commitment Want to learn NVC with Ali? Explore my 9-week private coaching program for couples: Stop Fighting! (without stuffing your feelings or sacrificing your needs). Includes my signature training: Hearing Each Other's Hearts: NVC Essentials for Couples Learn more: www.alimillercoaching.com/stopfighting Free Resources Feelings & Needs Cheatsheets: www.alimillercoaching.com/feelingsandneeds Free Mini-Course: The 4 Steps to Stop Any Fight Without Giving In www.alimillercoaching.com/freeminicourse Connect with Ali Instagram: @alimillercoaching Free Private Facebook Group: NVC for Couples www.facebook.com/groups/nvcforcouples Email: ali@alimillercoaching.com Website: www.alimillercoaching.com

Renee Troughton: The Hidden Cost of Constant Restructuring in Agile Organizations Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. "Trust and safety are the most fundamental foundations of a team to perform. And so you are just breaking the core of teams when you're doing this." Renee challenges us to look beyond team dysfunction and examine the "dirty little secrets" in organizations—leadership-driven anti-patterns that destroy team performance. She reveals a cyclical pattern of constant restructuring that occurs every six months in many organizations, driven by leaders who avoid difficult performance management conversations and instead force people through redundancy rounds. This creates a cascade of fear, panic, and victim mindset throughout the organization. Beyond restructuring, Renee identifies other destructive patterns including the C-suite shuffle (where new CEOs bring in their own teams, cascading change throughout the organization) and the insourcing/outsourcing swings that create chaos over 5-8 year cycles. These high-level decisions drain productivity for months as teams storm and reform, losing critical knowledge and breaking the trust and safety that are fundamental for high performance. Renee emphasizes that as Agile coaches and Scrum Masters, we often don't feel empowered to challenge these decisions, yet they represent the biggest drain on organizational productivity. Self-reflection Question: Have you identified the cyclical organizational anti-patterns in your workplace, and do you have the courage to raise these systemic issues with senior leadership? Featured Book of the Week: Loving What Is by Byron Katie "It teaches you around how to reframe your thoughts in the day-to-day life, to assess them in a different light than you would normally perceive them to be." Renee recommends "Loving What Is" by Byron Katie as an essential tool for Scrum Master introspection. This book teaches practical techniques for reframing thoughts and recognizing that problems we perceive "out there" are often internal framing issues. Katie's method, called "The Work," provides a worksheet-based approach to introspection that helps identify when our perceptions create unnecessary suffering. Renee also highlights Marshall Rosenberg's "Nonviolent Communication" as a companion book, which uses language to tap into underlying emotions and needs. Both books offer practical, actionable techniques for self-knowledge—a critical skill for anyone in the Scrum Master role. The journey these books provide leads to inner peace through understanding that many challenges stem from how we internally frame situations rather than external reality. We have many episodes on NVC, Nonviolent Communication, which you can dive into and learn from experienced practitioners.  [The Scrum Master Toolbox Podcast Recommends]

What if generosity isn't something we have to teach or force — but something we're born with? In this special episode honoring the birthday of Marshall Rosenberg, the founder of Nonviolent Communication (NVC), I share a personal story about my 5-year-old daughter — and how her spontaneous, joyful act of giving reminded me of one of Marshall's most powerful teachings: “What I want in my life is compassion — a flow between myself and others based on a mutual giving from the heart.” We'll explore: Why generous giving flows naturally when we feel connected and free How this principle applies not just to parenting, but to romantic relationships What gets in the way of that generosity in couples — and how NVC can help restore it A simple question to reflect on in your own relationship today Plus, I'll share how you and your partner can go deeper with NVC through my 9-Week Private Coaching Program for Couples: Stop Fighting (without stuffing your feelings or sacrificing your needs) If you're longing for more joy and spontaneous generosity in your relationship — this one's for you. Want to learn NVC with Ali? Explore my 9-week private coaching program for couples: Stop Fighting! (without stuffing your feelings or sacrificing your needs). Includes my signature training: Hearing Each Other's Hearts: NVC Essentials for Couples Learn more: www.alimillercoaching.com/stopfighting Free Resources Feelings & Needs Cheatsheets: www.alimillercoaching.com/feelingsandneeds Free Mini-Course: The 4 Steps to Stop Any Fight Without Giving In www.alimillercoaching.com/freeminicourse Connect with Ali Instagram: @alimillercoaching Free Private Facebook Group: NVC for Couples www.facebook.com/groups/nvcforcouples Email: ali@alimillercoaching.com Website: www.alimillercoaching.com Important note: The tools I share in this episode and all of the episodes on this podcast are suited for people who are in a safe relationship. If you do not feel safe in your relationship, please prioritize your safety. For support with priortizing your safety, in the U.S. you can chat with someone live at The National Domestic Violence Hotline at www.thehotline.org, or call them at 1-800-799-SAFE (7233) or text START to 88788. 

Ever feel like you're “in trouble” with your partner—even though you're a grown adult? That tight feeling in your chest, the urge to defend yourself, shut down, or appease… it's more common than you think. And it's not your fault. In this episode, we explore how growing up in a punitive culture wires us to associate conflict with danger—and how that fear shows up in our adult relationships. Using the lenses of Nonviolent Communication (NVC), Terry Real's Adaptive Child vs. Wise Adult, and self-compassion, we look at how to shift from self-protection to connection, even when emotions run high. You'll learn: Why the “I'm in trouble” feeling gets triggered in conflict How to recognize when your Adaptive Child is in the driver's seat Ways to offer yourself empathy so you can show up in your relationship from your Wise Adult self Practical NVC tools to respond with connection instead of self-protection Whether you're in a partnership or want to prepare for one, this episode is an invitation to soften, slow down, and connect—with yourself and your loved ones. Want to learn NVC with Ali? Explore my 9-week private coaching program for couples: Stop Fighting! (without stuffing your feelings or sacrificing your needs). Includes my signature training: Hearing Each Other's Hearts: NVC Essentials for Couples Learn more: www.alimillercoaching.com/stopfighting Free Resources Feelings & Needs Cheatsheets: www.alimillercoaching.com/feelingsandneeds Free Mini-Course: The 4 Steps to Stop Any Fight Without Giving In www.alimillercoaching.com/freeminicourse Connect with Ali Instagram: @alimillercoaching Free Private Facebook Group: NVC for Couples www.facebook.com/groups/nvcforcouples Email: ali@alimillercoaching.com Website: www.alimillercoaching.com Important note: The tools I share in this episode and all of the episodes on this podcast are suited for people who are in a safe relationship. If you do not feel safe in your relationship, please prioritize your safety. For support with priortizing your safety, in the U.S. you can chat with someone live at The National Domestic Violence Hotline at www.thehotline.org, or call them at 1-800-799-SAFE (7233) or text START to 88788. 

While I'm still in India, I wanted to revisit one of the most meaningful conversations I've had on the podcast, with Judith Hanson Lasater on non-violent communication for yoga teachers. I chose to share this episode again after receiving a surprising email that made me reflect deeply on how we speak to our teachers, students, and each other in the yoga space. This conversation is a beautiful reminder of how Ahimsa and respect show up not just in our practice, but in our communication, especially in the hard moments. I hope it offers insight, grounding, and a fresh perspective.Episode Highlights:What is non-violent communication? Is NVC more significant for yoga teachers? NVC is not for others but for usHow to engage with empathy? Who is NVC for? Where does violence start in communication? Cancel culture in the yoga world Should we respond to cancel culture in the yoga world?NVC exercise live on the podcast about cancel culture What are we giving our presence to? Why it matters? How to ground ourselves & act from empathyDifference between feeling & judgments Clarity of intension Updates about Judith's latest book Join our mailing listFind all the resources mentioned in this episodeConnect with us on Instagram