Podcasts about redirects

Do you ever notice how one small trigger can send you into a full-blown spiral? Maybe your partner takes too long to text back, or a conflict makes you think the relationship is doomed and suddenly you're catastrophizing, overthinking, or blaming yourself. In this episode of Codependency Alchemy, I walk you through my 3-step “Stop the Spiral” framework (Root, Regulate, Redirect) to help you come back to your body when your nervous system gets hijacked. We'll explore common thought spirals like fear of abandonment, self-blame, and overthinking, and I'll share how to re-center with compassion instead of control.This episode is for you if:* You find yourself stuck in anxious or intrusive thought loops.* You panic when there's space or silence in your relationship.* You replay conversations, wondering if you said the “wrong thing.”* You want to feel calm and grounded instead of consumed by fear.I know now that spiraling is actually just my body asking for safety. When you pause to root into what's actually happening, regulate your nervous system, and redirect your energy back to yourself, you stop trying to fix the fear and start learning from it.

Welcome to the Celestial Insights Podcast, the show that brings the stars down to Earth! Each week, astrologer, coach, and intuitive Celeste Brooks of Astrology by Celeste will be your guide. Her website is astrologybyceleste.com.  

Today's Headlines: Donald Trump's Nobel campaign tour continues: he's meeting Zelensky at the White House today, fresh off a “productive” call with Putin and plans to see him soon in Budapest. Meanwhile, former national security adviser John Bolton was indicted on 18 counts for allegedly keeping and sharing over a thousand pages of classified info with relatives — which were later hacked by Iran-linked actors. The Wall Street Journal says Trump's next target is the IRS, with plans to redirect its muscle toward investigating left-leaning groups and major Democratic donors. Shutdown side effects keep piling up — the New York Times found $28 billion in federal project funding frozen in blue districts versus just $739 million in red ones.In other news, Harvard reported a $113 million operating loss, its first in years, after federal funding fell and costs rose (though donor gifts hit a record $629 million and its endowment swelled to $57 billion). Trump also wined and dined corporate giants like Palantir, Meta, and Google to raise $250 million for his new White House ballroom, while Illinois Governor JB Pritzker casually declared $1.4 million in blackjack winnings. And in Madagascar, Gen Z protesters ousted their president, who fled to Dubai, leaving a military colonel promising elections “within two years.” Resources/Articles mentioned in this episode: WSJ: Trump Says He Will Meet With Putin in Budapest to Discuss End to Ukraine War AP News: Donald Trump's former adviser John Bolton indicted WSJ: Trump Team Plans IRS Overhaul to Enable Pursuit of Left-Leaning Groups NYT: Trump Halts Billions in Grants for Democratic Districts During Shutdown Axios: Harvard posts biggest operating loss in 14 years as Trump cuts bite WSJ: Trump Hosts Corporate Ballroom Donors at Glitzy White House Dinner WSJ: Billionaire Gov. JB Pritzker Recounts $1.4 Million Las Vegas Blackjack Win Economist: Gen Z revolution or military coup in Madagascar? Morning Announcements is produced by Sami Sage and edited by Grace Hernandez-Johnson Learn more about your ad choices. Visit megaphone.fm/adchoices

Awareness is only the beginning—real leadership transformation happens when you take bold, intentional action. In this powerful podcast episode of Stepping Into The Arena, Karen Gombault lays out the exact steps you need to plug the four most common power leaks senior executives face.If you've recently stepped into a bigger role, and you're juggling visibility, credibility, and pressure, this is your tactical guide to reclaiming control, sharpening your presence, and protecting your energy.You don't need to do more—you need to do different.5 KEY TAKEAWAYS:Audit your altitude. Upgrade your calendar and your mindset. Shift from doing manager work to operating at strategic, high-level leadership altitude.Reframe your meetings. Stop the updates. Start making decisions. Ask the questions that move your team—and your influence—forward.Use the 3P Filter. Before saying yes, ask: Does this serve my Priorities, my People, or my Positioning?Don't let discomfort fester. Use a 48-hour rule to address tough conversations fast and with clarity. Avoiding conflict erodes your credibility.Stay in your lane. Focus only on what you can control. Redirect drama and noise into decisions and action that strengthen your presence.“Every time you reclaim your energy from things that are draining it, your presence, your authority and your credibility become much cleaner and sharper.” — Karen GombaultEvery time you close a power leak, you're not just being more efficient—you're strengthening your leadership identity. You're teaching people how to treat you. You're building trust, credibility, and authority.Choose one leak this week and stop it. You'll feel the shift instantly.RESOURCES & NEXT STEPS:

This episode of the Tactical Living Podcast, hosted by Coach Ashlie Walton and Sergeant Clint Walton, unpacks a surprising truth: praise, awards, and public recognition don't always feel good to first responders (Amazon Affiliate). While many people assume medals and compliments bring pride, for those in uniform they can sometimes trigger discomfort, guilt, or even resentment. We explore the psychology behind this paradox—and how to accept recognition in a healthy way without feeling like you're betraying your values. 1. Why Praise Can Feel Uncomfortable First responders often see their actions as “just doing the job,” not something special. Public praise can feel undeserved when you know how much was lost or how many others were involved. 2. The Guilt-Recognition Conflict Recognition sometimes resurfaces memories of traumatic calls or fallen colleagues. Officers may feel like accepting praise dishonors those who didn't survive. 3. The Culture of Humility and Stoicism First responder culture often discourages showing pride or seeking attention. Praise can clash with the deeply ingrained mindset of selfless service. 4. How This Affects Mental Health Dismissing or deflecting praise can reinforce feelings of isolation and low self-worth. Refusing to internalize recognition contributes to burnout and emotional exhaustion. 5. Healthier Ways to Receive Praise Acknowledge the emotion without minimizing it (“It was hard, and I did my best”). Redirect praise to the whole team without rejecting it entirely. Talk about the discomfort—normalize it among peers to reduce shame. Use praise as a reminder of impact, not perfection. Keep perspective: accepting recognition doesn't mean seeking it.

Today Eric shares a sales training session focused on improving discovery calls. He proposes a new approach, inspired by a clip from Charlie Kirk, that suggests starting sales conversations by asking the client to share their story regarding the project or problem, which he believes will lead to the customer's true motive faster. The speakers engage in role-playing scenarios—including one about fixing a pond liner leak and another about installing a waterfall—to test the efficacy of this "story" approach versus conventional questioning, with much of the discussion centering on active listening, cadence, and the importance of recaps and addressing the customer's emotions. The overall goal of the proposed technique is to increase efficiency and save time during the sales process. Key Takeaways: Initiate interactions by asking for the customer's story to quickly understand their motive and context. Focus on efficiency to save minutes during interactions, as these saved minutes accumulate into larger gains. Redirect overly lengthy conversations by stating you need to slow down to take notes and ensure you can properly address their needs. Perform consistent practice and role-playing to refine your skills and improve performance in real-world scenarios. Always recap discussions by including the client's emotional motive and story, not just the scope of work.

When executives lose influence, it rarely happens in one dramatic crash—it fades away slowly, almost invisibly. In this episode of Stepping Into The Arena, Karen Gombault reveals the four most common ways senior leaders leak power in the first six months of a new role. These aren't obvious failures; they're subtle habits that silently drain your credibility, clarity, and presence. Learn how to plug these leaks so you can lead with stronger influence, more confidence, and measurable impact from day one.Whether you're navigating a promotion, expanded scope, or a brand-new role, this episode is your wake-up call to take back your power—before it slips away.5 KEY TAKEAWAYS:Old habits don't serve new roles. Operating from your previous identity keeps you stuck in the weeds—and undermines your strategic presence.Saying yes to everything weakens your authority. Over-accommodating others' expectations may feel productive but signals a lack of boundaries.Avoiding discomfort erodes leadership. Postponing hard conversations or difficult decisions chips away at your credibility and decisiveness.Focusing on what you can't control drains energy. Redirect attention to what's in your lane to reclaim influence and protect your well-being.Power leaks aren't fixed with big moves. Small, conscious decisions restore authority—one shift at a time.“Every time you close a leak, you reclaim a piece of your authority. You're going to walk into the room taller, your words are going to carry more weight, and you'll start to feel completely aligned with your job.” — Karen GombaultPlugging power leaks isn't about being perfect. Tt's about becoming aware and choosing differently. Start by identifying one area where your influence is slipping and commit to a single action this week. Over time, those micro-adjustments compound into massive leadership credibility.RESOURCES & NEXT STEPS:

Hi Mamas, This week's Monday Mindset Reset is anchored in a quote from Tony Robbins that hits especially hard as we close out the year:

In this episode, Chad sits down with Yo Legroan from ReDirect Athletics in Reno, Nevada. Yo is a man whose mission goes way beyond sports. He isn't just training athletes; he's raising leaders. His passion is contagious, his mindset is relentless, and his belief is simple: everybody needs something, and everybody needs love. The conversation gets real. From boxing as a metaphor for life, getting knocked down, getting back up, and training harder, to race, resilience, and the role of strong men guiding the next generation. Chad and Yo don't shy away from the tough stuff. They dig into derogatory terms, cultural divides, and the mentors from different backgrounds who shaped them into who they are today. This one is seriously raw, honest, and it's the kind of talk that sticks with you. If you care about grit, accountability, and the future of our kids, this is one you can't miss. This episode is presented by Jack Daniels Tennessee Whiskey, and brought to you by Liberty Heritage Apparel, RIGID Industries, Bedslide, Mickey Thompson Tires, and PECOS Outdoors!

In this Q&A episode, I answer three questions from Emily. First, I share how I guide parents to respond when a child—or their sibling—asks why they're going to therapy. I offer simple, CCPT-aligned language that keeps the explanation safe, supportive, and child-appropriate. Next, I address a common situation in sessions with older children: when they want you to participate in games like “Would You Rather?” I explain how to stay true to the model while still maintaining connection and rapport. Lastly, I talk through how to handle personal questions from kids—especially pre-teens—who may be seeking relationship or connection. I offer mindset guidance and practical phrasing for staying centered and maintaining therapeutic boundaries while still honoring the child's need for connection. PlayTherapyNow.com is my HUB for everything I do! playtherapynow.com. Sign up for my email newsletter, stay ahead with the latest CCPT CEU courses, personalized coaching opportunities and other opportunities you need to thrive in your CCPT practice. If you click one link in these show notes, this is the one to click! Topical Playlists! All of the podcasts are now grouped into topical playlists on YouTube. Please go to https://www.youtube.com/@kidcounselorbrenna/playlists to view them. If you would like to ask me questions directly, check out www.ccptcollective.com, where I host two weekly Zoom calls filled with advanced CCPT case studies and session reviews, as well as member Q&A. You can take advantage of the two-week free trial to see if the CCPT Collective is right for you. Ask Me Questions: Call ‪(813) 812-5525‬, or email: brenna@thekidcounselor.com Brenna's CCPT Hub: https://www.playtherapynow.com CCPT Collective (online community exclusively for CCPTs): https://www.ccptcollective.com Podcast HQ: https://www.playtherapypodcast.com APT Approved Play Therapy CE courses: https://childcenteredtraining.com Facebook: https://facebook.com/playtherapypodcast Common References: Cochran, N., Nordling, W., & Cochran, J. (2010). Child-Centered Play Therapy (1st ed.). Wiley. VanFleet, R., Sywulak, A. E., & Sniscak, C. C. (2010). Child-centered play therapy. Guilford Press. Landreth, G.L. (2023). Play Therapy: The Art of the Relationship (4th ed.). Routledge. Landreth, G.L., & Bratton, S.C. (2019). Child-Parent Relationship Therapy (CPRT): An Evidence-Based 10-Session Filial Therapy Model (2nd ed.). Routledge. https://doi.org/10.4324/9781315537948 Benedict, Helen. Themes in Play Therapy. Used with permission to Heartland Play Therapy Institute.

In this episode of Overpowering Emotions, Dr. Caroline explores the often-overlooked role of pleasant emotions in self-regulation. From the high-energy buzz of excitement and joy to the quiet calm of contentment and gratitude, she unpacks what these feelings signal, the needs behind them, and how adults can guide children to channel them in healthy ways.Learn how excitement fuels motivation but can tip into dysregulation without support, why pride is a powerful pro-social emotion, and how gratitude and love deepen connection and resilience. Caroline shares practical strategies that help kids strengthen their emotional awareness and regulation skills.Learn actionable tools to nurture children's motivation, curiosity, and sense of belonging while reinforcing the “rest stops” of calm and contentment that every child needs.Homework IdeasHelp kids learn to:Channel excitement:Use countdown calendars, planning rituals, or physical play to help kids release energy safely.Redirect silliness into storytelling, drawing, or creative outlets.Savour Joy:Pause in the moment and ask: What feels good right now?Create joy rituals: end-of-day reflections, photo sharing, or a family “joy jar.”Reinforce Pride:Offer descriptive praise focused on effort, not outcomes.Help kids create a “brag book” or journal for proud moments.Cultivate Curiosity:Model open-ended questions (“I wonder…”).Provide exploration opportunities—STEM kits, nature walks, disassembling old gadgets.Anchor Calm & Contentment:Build quiet, screen-free downtime into daily routines.Use grounding practices (breathing, mindfulness, cozy snuggles, weighted blankets).Encourage Gratitude & Love:End the day with “3 things I'm grateful for.”Practice small acts of kindness—thank-you notes, hugs, or helping tasks.

Elizabeth Figura is a Wine developer at Code Weavers. We discuss how Wine and Proton make it possible to run Windows applications on other operating systems. Related links WineHQ Proton Crossover Direct3D MoltenVK XAudio2 Mesa 3D Graphics Library Transcript You can help correct transcripts on GitHub. Intro [00:00:00] Jeremy: Today I am talking to Elizabeth Figuera. She's a wine developer at Code Weavers. And today we're gonna talk about what that is and, uh, all the work that goes into it. [00:00:09] Elizabeth: Thank you Jeremy. I'm glad to be here. What's Wine [00:00:13] Jeremy: I think the first thing we should talk about is maybe saying what Wine is because I think a lot of people aren't familiar with the project. [00:00:20] Elizabeth: So wine is a translation layer. in fact, I would say wine is a Windows emulator. That is what the name originally stood for. it re implements the entire windows. Or you say win 32 API. so that programs that make calls into the API, will then transfer that code to wine and and we allow that Windows programs to run on, things that are not windows. So Linux, Mac, os, other operating systems such as Solaris and BSD. it works not by emulating the CPU, but by re-implementing every API, basically from scratch and translating them to their equivalent or writing new code in case there is no, you know, equivalent. System Calls [00:01:06] Jeremy: I believe what you're doing is you're emulating system calls. Could you explain what those are and, and how that relates to the project? [00:01:15] Elizabeth: Yeah. so system call in general can be used, referred to a call into the operating system, to execute some functionality that's built into the operating system. often it's used in the context of talking to the kernel windows applications actually tend to talk at a much higher level, because there's so much, so much high level functionality built into Windows. When you think about, as opposed to other operating systems that we basically, we end up end implementing much higher level behavior than you would on Linux. [00:01:49] Jeremy: And can you give some examples of what some of those system calls would be and, I suppose how they may be higher level than some of the Linux ones. [00:01:57] Elizabeth: Sure. So of course you have like low level calls like interacting with a file system, you know, created file and read and write and such. you also have, uh, high level APIs who interact with a sound driver. [00:02:12] Elizabeth: There's, uh, one I was working on earlier today, called XAudio where you, actually, you know, build this bank of of sounds. It's meant to be, played in a game and then you can position them in various 3D space. And the, and the operating system in a sense will, take care of all of the math that goes into making that work. [00:02:36] Elizabeth: That's all running on your computer and. And then it'll send that audio data to the sound card once it's transformed it. So it sounds like it's coming from a certain space. a lot of other things like, you know, parsing XML is another big one. That there's a lot of things. The, there, the, the, the space is honestly huge [00:02:59] Jeremy: And yeah, I can sort of see how those might be things you might not expect to be done by the operating system. Like you gave the example of 3D audio and XML parsing and I think XML parsing in, in particular, you would've thought that that would be something that would be handled by the, the standard library of whatever language the person was writing their application as. [00:03:22] Jeremy: So that's interesting that it's built into the os. [00:03:25] Elizabeth: Yeah. Well, and languages like, see it's not, it isn't even part of the standard library. It's higher level than that. It's, you have specific libraries that are widespread but not. Codified in a standard, but in Windows you, in Windows, they are part of the operating system. And in fact, there's several different, XML parsers in the operating system. Microsoft likes to deprecate old APIs and make new ones that do the same thing very often. [00:03:53] Jeremy: And something I've heard about Windows is that they're typically very reluctant to break backwards compatibility. So you say they're deprecated, but do they typically keep all of them still in there? [00:04:04] Elizabeth: It all still It all still works. [00:04:07] Jeremy: And that's all things that wine has to implement as well to make sure that the software works as well. [00:04:14] Jeremy: Yeah. [00:04:14] Elizabeth: Yeah. And, and we also, you know, need to make it work. we also need to implement those things to make old, programs work because there is, uh, a lot of demand, at least from, at least from people using wine for making, for getting some really old programs, working from the. Early nineties even. What people run with Wine (Productivity, build systems, servers) [00:04:36] Jeremy: And that's probably a good, thing to talk about in terms of what, what are the types of software that, that people are trying to run with wine, and what operating system are they typically using? [00:04:46] Elizabeth: Oh, in terms of software, literally all kinds, any software you can imagine that runs on Windows, people will try to run it on wine. So we're talking games, office software productivity, software accounting. people will run, build systems on wine, build their, just run, uh, build their programs using, on visual studio, running on wine. people will run wine on servers, for example, like software as a service kind of things where you don't even know that it's running on wine. really super domain specific stuff. Like I've run astronomy, software, and wine. Design, computer assisted design, even hardware drivers can sometimes work unwind. There's a bit of a gray area. How games are different [00:05:29] Jeremy: Yeah, it's um, I think from. Maybe the general public, or at least from what I've seen, I think a lot of people's exposure to it is for playing games. is there something different about games versus all those other types of, productivity software and office software that, that makes supporting those different. [00:05:53] Elizabeth: Um, there's some things about it that are different. Games of course have gotten a lot of publicity lately because there's been a huge push, largely from valve, but also some other companies to get. A lot of huge, wide range of games working well under wine. And that's really panned out in the, in a way, I think, I think we've largely succeeded. [00:06:13] Elizabeth: We've made huge strides in the past several years. 5, 5, 10 years, I think. so when you talk about what makes games different, I think, one thing games tend to do is they have a very limited set of things they're working with and they often want to make things run fast, and so they're working very close to the me They're not, they're not gonna use an XML parser, for example. [00:06:44] Elizabeth: They're just gonna talk directly as, directly to the graphics driver as they can. Right. And, and probably going to do all their own sound design. You know, I did talk about that XAudio library, but a lot of games will just talk directly as, directly to the sound driver as Windows Let some, so this is a often a blessing, honestly, because it means there's less we have to implement to make them work. when you look at a lot of productivity applications, and especially, the other thing that makes some productivity applications harder is, Microsoft makes 'em, and They like to, make a library, for use in this one program like Microsoft Office and then say, well, you know, other programs might use this as well. Let's. Put it in the operating system and expose it and write an API for it and everything. And maybe some other programs use it. mostly it's just office, but it means that office relies on a lot of things from the operating system that we all have to reimplement. [00:07:44] Jeremy: Yeah, that's somewhat counterintuitive because when you think of games, you think of these really high performance things that that seem really complicated. But it sounds like from what you're saying, because they use the lower level primitives, they're actually easier in some ways to support. [00:08:01] Elizabeth: Yeah, certainly in some ways, they, yeah, they'll do things like re-implement the heap allocator because the built-in heap allocator isn't fast enough for them. That's another good example. What makes some applications hard to support (Some are hard, can't debug other people's apps) [00:08:16] Jeremy: You mentioned Microsoft's more modern, uh, office suites. I, I've noticed there's certain applications that, that aren't supported. Like, for example, I think the modern Adobe Creative Suite. What's the difference with software like that and does that also apply to the modern office suite, or is, or is that actually supported? [00:08:39] Elizabeth: Well, in one case you have, things like Microsoft using their own APIs that I mentioned with Adobe. That applies less, I suppose, but I think to some degree, I think to some degree the answer is that some applications are just hard and there's, and, and there's no way around it. And, and we can only spend so much time on a hard application. I. Debugging things. Debugging things can get very hard with wine. Let's, let me like explain that for a minute because, Because normally when you think about debugging an application, you say, oh, I'm gonna open up my debugger, pop it in, uh, break at this point, see what like all the variables are, or they're not what I expect. Or maybe wait for it to crash and then get a back trace and see where it crashed. And why you can't do that with wine, because you don't have the application, you don't have the symbols, you don't have your debugging symbols. You don't know anything about the code you're running unless you take the time to disassemble and decompile and read through it. And that's difficult every time. It's not only difficult, every time I've, I've looked at a program and been like, I really need to just. I'm gonna just try and figure out what the program is doing. [00:10:00] Elizabeth: It takes so much time and it is never worth it. And sometimes you have to, sometimes you have no other choice, but usually you end up, you ask to rely on seeing what calls it makes into the operating system and trying to guess which one of those is going wrong. Now, sometimes you'll get lucky and it'll crash in wine code, or sometimes it'll make a call into, a function that we don't implement yet, and we know, oh, we need to implement that function. But sometimes it does something, more obscure and we have to figure out, well, like all of these millions of calls it made, which one of them is, which one of them are we implementing incorrectly? So it's returning the wrong result or not doing something that it should. And, then you add onto that the. You know, all these sort of harder to debug things like memory errors that we could make. And it's, it can be very difficult and so sometimes some applications just suffer from those hard bugs. and sometimes it's also just a matter of not enough demand for something for us to spend a lot of time on it. [00:11:11] Elizabeth: Right. [00:11:14] Jeremy: Yeah, I can see how that would be really challenging because you're, like you were saying, you don't have the symbols, so you don't have the source code, so you don't know what any of this software you're supporting, how it was actually written. And you were saying that I. A lot of times, you know, there may be some behavior that's wrong or a crash, but it's not because wine crashed or there was an error in wine. [00:11:42] Jeremy: so you just know the system calls it made, but you don't know which of the system calls didn't behave the way that the application expected. [00:11:50] Elizabeth: Exactly. Test suite (Half the code is tests) [00:11:52] Jeremy: I can see how that would be really challenging. and wine runs so many different applications. I'm, I'm kind of curious how do you even track what's working and what's not as you, you change wine because if you support thousands or tens thousands of applications, you know, how do you know when you've got a, a regression or not? [00:12:15] Elizabeth: So, it's a great question. Um, probably over half of wine by like source code volume. I actually actually check what it is, but I think it's, i, I, I think it's probably over half is what we call is tests. And these tests serve two purposes. The one purpose is a regression test. And the other purpose is they're conformance tests that test, that test how, uh, an API behaves on windows and validates that we are behaving the same way. So we write all these tests, we run them on windows and you know, write the tests to check what the windows returns, and then we run 'em on wine and make sure that that matches. and we have just such a huge body of tests to make sure that, you know, we're not breaking anything. And that every, every, all the code that we, that we get into wine that looks like, wow, it's doing that really well. Nope, that's what Windows does. The test says so. So pretty much any code that we, any new code that we get, it has to have tests to validate, to, to demonstrate that it's doing the right thing. [00:13:31] Jeremy: And so rather than testing against a specific application, seeing if it works, you're making a call to a Windows system call, seeing how it responds, and then making the same call within wine and just making sure they match. [00:13:48] Elizabeth: Yes, exactly. And that is obviously, or that is a lot more, automatable, right? Because otherwise you have to manually, you know, there's all, these are all graphical applications. [00:14:02] Elizabeth: You'd have to manually do the things and make sure they work. Um, but if you write automateable tests, you can just run them all and the machine will complain at you if it fails it continuous integration. How compatibility problems appear to users [00:14:13] Jeremy: And because there's all these potential compatibility issues where maybe a certain call doesn't behave the way an application expects. What, what are the types of what that shows when someone's using software? I mean, I, I think you mentioned crashes, but I imagine there could be all sorts of other types of behavior. [00:14:37] Elizabeth: Yes, very much so. basically anything, anything you can imagine again is, is what will happen. You can have, crashes are the easy ones because you know when and where it crashed and you can work backwards from there. but you can also get, it can, it could hang, it could not render, right? Like maybe render a black screen. for, you know, for games you could very frequently have, graphical glitches where maybe some objects won't render right? Or the entire screen will be read. Who knows? in a very bad case, you could even bring down your system and we usually say that's not wine's fault. That's the graphics library's fault. 'cause they're not supposed to do that, uh, no matter what we do. But, you know, sometimes we have to work around that anyway. but yeah, there's, there's been some very strange and idiosyncratic bugs out there too. [00:15:33] Jeremy: Yeah. And like you mentioned that uh, there's so many different things that could have gone wrong that imagine's very difficult to find. Yeah. And when software runs through wine, I think, Performance is comparable to native [00:15:49] Jeremy: A lot of our listeners will probably be familiar with running things in a virtual machine, and they know that there's a big performance impact from doing that. [00:15:57] Jeremy: How does the performance of applications compare to running natively on the original Windows OS versus virtual machines? [00:16:08] Elizabeth: So. In theory. and I, I haven't actually done this recently, so I can't speak too much to that, but in theory, the idea is it's a lot faster. so there, there, is a bit of a joke acronym to wine. wine is not an emulator, even though I started out by saying wine is an emulator, and it was originally called a Windows emulator. but what this basically means is wine is not a CPU emulator. It doesn't, when you think about emulators in a general sense, they're often, they're often emulators for specific CPUs, often older ones like, you know, the Commodore emulator or an Amiga emulator. but in this case, you have software that's written for an x86 CPU. And it's running on an x86 CPU by giving it the same instructions that it's giving on windows. It's just that when it says, now call this Windows function, it calls us instead. So that all should perform exactly the same. The only performance difference at that point is that all should perform exactly the same as opposed to a, virtual machine where you have to interpret the instructions and maybe translate them to a different instruction set. The only performance difference is going to be, in the functions that we are implementing themselves and we try to, we try to implement them to perform. As well, or almost as well as windows. There's always going to be a bit of a theoretical gap because we have to translate from say, one API to another, but we try to make that as little as possible. And in some cases, the operating system we're running on is, is just better than Windows and the libraries we're using are better than Windows. [00:18:01] Elizabeth: And so our games will run faster, for example. sometimes we can, sometimes we can, do a better job than Windows at implementing something that's, that's under our purview. there there are some games that do actually run a little bit faster in wine than they do on Windows. [00:18:22] Jeremy: Yeah, that, that reminds me of how there's these uh, gaming handhelds out now, and some of the same ones, they have a, they either let you install Linux or install windows, or they just come with a pre-installed, and I believe what I've read is that oftentimes running the same game on both operating systems, running the same game on Linux, the battery life is better and sometimes even the performance is better with these handhelds. [00:18:53] Jeremy: So it's, it's really interesting that that can even be the case. [00:18:57] Elizabeth: Yeah, it's really a testament to the huge amount of work that's gone into that, both on the wine side and on the, side of the graphics team and the colonel team. And, and of course, you know, the years of, the years of, work that's gone into Linux, even before these gaming handhelds were, were even under consideration. Proton and Valve Software's role [00:19:21] Jeremy: And something. So for people who are familiar with the handhelds, like the steam deck, they may have heard of proton. Uh, I wonder if you can explain what proton is and how it relates to wine. [00:19:37] Elizabeth: Yeah. So, proton is basically, how do I describe this? So, proton is a sort of a fork, uh, although we try to avoid the term fork. It's a, we say it's a downstream distribution because we contribute back up to wine. so it is a, it is, it is a alternate distribution fork of wine. And it's also some code that basically glues wine into, an embedding application originally intended for steam, and developed for valve. it has also been used in, others, but it has also been used in other software. it, so where proton differs from wine besides the glue part is it has some, it has some extra hacks in it for bugs that are hard to fix and easy to hack around as some quick hacks for, making games work now that are like in the process of going upstream to wine and getting their code quality improved and going through review. [00:20:54] Elizabeth: But we want the game to work now, when we distribute it. So that'll, that'll go into proton immediately. And then once we have, once the patch makes it upstream, we replace it with the version of the patch from upstream. there's other things to make it interact nicely with steam and so on. And yeah, I think, yeah, I think that's, I got it. [00:21:19] Jeremy: Yeah. And I think for people who aren't familiar, steam is like this, um, I, I don't even know what you call it, like a gaming store and a [00:21:29] Elizabeth: store game distribution service. it's got a huge variety of games on it, and you just publish. And, and it's a great way for publishers to interact with their, you know, with a wider gaming community, uh, after it, just after paying a cut to valve of their profits, they can reach a lot of people that way. And because all these games are on team and, valve wants them to work well on, on their handheld, they contracted us to basically take their entire catalog, which is huge, enormous. And trying and just step by step. Fix every game and make them all work. [00:22:10] Jeremy: So, um, and I guess for people who aren't familiar Valve, uh, softwares the company that runs steam, and so it sounds like they've asked, uh, your company to, to help improve the compatibility of their catalog. [00:22:24] Elizabeth: Yes. valve contracted us and, and again, when you're talking about wine using lower level libraries, they've also contracted a lot of other people outside of wine. Basically, the entire stack has had a tremendous, tremendous investment by valve software to make gaming on Linux work. Well. The entire stack receives changes to improve Wine compatibility [00:22:48] Jeremy: And when you refer to the entire stack, like what are some, some of those pieces, at least at a high level. [00:22:54] Elizabeth: I, I would, let's see, let me think. There is the wine project, the. Mesa Graphics Libraries. that's a, that's another, you know, uh, open source, software project that existed, has existed for a long time. But Valve has put a lot of, uh, funding and effort into it, the Linux kernel in various different ways. [00:23:17] Elizabeth: the, the desktop, uh, environment and Window Manager for, um, are also things they've invested in. [00:23:26] Jeremy: yeah. Everything that the game needs, on any level and, and that the, and that the operating system of the handheld device needs. Wine's history [00:23:37] Jeremy: And wine's been going on for quite a while. I think it's over a decade, right? [00:23:44] Elizabeth: I believe. Oh, more than, oh, far more than a decade. I believe it started in 1990, I wanna say about 1995, mid nineties. I'm, I probably have that date wrong. I believe Wine started about the mid nineties. [00:24:00] Jeremy: Mm. [00:24:00] Elizabeth: it's going on for three decades at this rate. [00:24:03] Jeremy: Wow. Okay. [00:24:06] Jeremy: And so all this time, how has the, the project sort of sustained itself? Like who's been involved and how has it been able to keep going this long? [00:24:18] Elizabeth: Uh, I think as is the case with a lot of free software, it just, it just keeps trudging along. There's been. There's been times where there's a lot of interest in wine. There's been times where there's less, and we are fortunate to be in a time where there's a lot of interest in it. we've had the same maintainer for almost this entire, almost this entire existence. Uh, Alexander Julliard, there was one person starting who started, maintained it before him and, uh, left it maintainer ship to him after a year or two. Uh, Bob Amstat. And there has been a few, there's been a few developers who have been around for a very long time. a lot of developers who have been around for a decent amount of time, but not for the entire duration. And then a very, very large number of people who come and submit a one-off fix for their individual application that they want to make work. [00:25:19] Jeremy: How does crossover relate to the wine project? Like, it sounds like you had mentioned Valve software hired you for subcontract work, but crossover itself has been around for quite a while. So how, how has that been connected to the wine project? [00:25:37] Elizabeth: So I work for, so the, so the company I work for is Code Weavers and, crossover is our flagship software. so Code Weavers is a couple different things. We have a sort of a porting service where companies will come to us and say, can we port my application usually to Mac? And then we also have a retail service where Where we basically have our own, similar to Proton, but you know, older, but the same idea where we will add some hacks into it for very difficult to solve bugs and we have a, a nice graphical interface. And then, the other thing that we're selling with crossover is support. So if you, you know, try to run a certain application and you buy crossover, you can submit a ticket saying this doesn't work and we now have a financial incentive to fix it. You know, we'll try to, we'll try to fix your, we'll spend company resources to fix your bug, right? So that's been so, so code we v has been around since 1996 and crossover, I don't know the date, but it's crossover has been around for probably about two decades, if I'm not mistaken. [00:27:01] Jeremy: And when you mention helping companies port their software to, for example, MacOS. [00:27:07] Jeremy: Is the approach that you would port it natively to MacOS APIs or is it that you would help them get it running using wine on MacOS? [00:27:21] Elizabeth: Right. That's, so that's basically what makes us so unique among porting companies is that instead of rewriting their software, we just, we just basically stick it inside of crossover and, uh, and, and make it run. [00:27:36] Elizabeth: And the idea has always been, you know, the more we implement, the more we get correct, the, the more applications will, you know, work. And sometimes it works out that way. Sometimes not really so much. And there's always work we have to do to get any given application to work, but. Yeah, so it's, it's very unusual because we don't ask companies for any of their code. We don't need it. We just fix the windows API [00:28:07] Jeremy: And, and so in that case, the ports would be let's say someone sells a MacOS version of their software. They would bundle crossover, uh, with their software. [00:28:18] Elizabeth: Right? And usually when you do this, it doesn't look like there's crossover there. Like it just looks like this software is native, but there is soft, there is crossover under the hood. Loading executables and linked libraries [00:28:32] Jeremy: And so earlier we were talking about how you're basically intercepting the system calls that these binaries are making, whether that's the executable or the, the DLLs from Windows. Um, but I think probably a lot of our listeners are not really sure how that's done. Like they, they may have built software, but they don't know, how do I basically hijack, the system calls that this application is making. [00:29:01] Jeremy: So maybe you could talk a little bit about how that works. [00:29:04] Elizabeth: So there, so there's a couple steps to go into it. when you think about a program that's say, that's a big, a big file that's got all the machine code in it, and then it's got stuff at the beginning saying, here's how the program works and here's where in the file the processor should start running. that's, that's your EXE file. And then in your DLL files are libraries that contain shared code and you have like a similar sort of file. It says, here's the entry point. That runs this function, this, you know, this pars XML function or whatever have you. [00:29:42] Elizabeth: And here's this entry point that has the generate XML function and so on and so forth. And, and, then the operating system will basically take the EXE file and see all the bits in it. Say I want to call the pars XML function. It'll load that DLL and hook it up. So it, so the processor ends up just seeing jump directly to this pars XML function and then run that and then return and so on. [00:30:14] Elizabeth: And so what wine does, is it part of wine? That's part of wine is a library, is that, you know, the implementing that parse XML and read XML function, but part of it is the loader, which is the part of the operating system that hooks everything together. And when we load, we. Redirect to our libraries. We don't have Windows libraries. [00:30:38] Elizabeth: We like, we redirect to ours and then we run our code. And then when you jump back to the program and yeah. [00:30:48] Jeremy: So it's the, the loader that's a part of wine. That's actually, I'm not sure if running the executable is the right term. [00:30:58] Elizabeth: no, I think that's, I think that's a good term. It's, it's, it's, it starts in a loader and then we say, okay, now run the, run the machine code and it's executable and then it runs and it jumps between our libraries and back and so on. [00:31:14] Jeremy: And like you were saying before, often times when it's trying to make a system call, it ends up being handled by a function that you've written in wine. And then that in turn will call the, the Linux system calls or the MacOS system calls to try and accomplish the, the same result. [00:31:36] Elizabeth: Right, exactly. [00:31:40] Jeremy: And something that I think maybe not everyone is familiar with is there's this concept of user space versus kernel space. you explain what the difference is? [00:31:51] Elizabeth: So the way I would explain, the way I would describe a kernel is it's the part of the operating system that can do anything, right? So any program, any code that runs on your computer is talking to the processor, and the processor has to be able to do anything the computer can do. [00:32:10] Elizabeth: It has to be able to talk to the hardware, it has to set up the memory space. That, so actually a very complicated task has to be able to switch to another task. and, and, and, and basically talk to another program and. You have to have something there that can do everything, but you don't want any program to be able to do everything. Um, not since the, not since the nineties. It's about when we realized that we can't do that. so the kernel is a part that can do everything. And when you need to do something that requires those, those permissions that you can't give everyone, you have to talk to the colonel and ask it, Hey, can you do this for me please? And in a very restricted way where it's only the safe things you can do. And a degree, it's also like a library, right? It's the kernel. The kernels have always existed, and since they've always just been the core standard library of the computer that does the, that does the things like read and write files, which are very, very complicated tasks under the hood, but look very simple because all you say is write this file. And talk to the hardware and abstract away all the difference between different drivers. So the kernel is doing all of these things. So because the kernel is a part that can do everything and because when you think about the kernel, it is basically one program that is always running on your computer, but it's only one program. So when a user calls the kernel, you are switching from one program to another and you're doing a lot of complicated things as part of this. You're switching to the higher privilege level where you can do anything and you're switching the state from one program to another. And so it's a it. So this is what we mean when we talk about user space, where you're running like a normal program and kernel space where you've suddenly switched into the kernel. [00:34:19] Elizabeth: Now you're executing with increased privileges in a different. idea of the process space and increased responsibility and so on. [00:34:30] Jeremy: And, and so do most applications. When you were talking about the system calls for handling 3D audio or parsing XML. Are those considered, are those system calls considered part of user space and then those things call the kernel space on your behalf, or how, how would you describe that? [00:34:50] Elizabeth: So most, so when you look at Windows, most of most of the Windows library, the vast, vast majority of it is all user space. most of these libraries that we implement never leave user space. They never need to call into the kernel. there's the, there only the core low level stuff. Things like, we need to read a file, that's a kernel call. when you need to sleep and wait for some seconds, that's a kernel. Need to talk to a different process. Things that interact with different processes in general. not just allocate memory, but allocate a page of memory, like a, from the memory manager and then that gets sub allocated by the heap allocator. so things like that. [00:35:31] Jeremy: Yeah, so if I was writing an application and I needed to open a file, for example, does, does that mean that I would have to communicate with the kernel to, to read that file? [00:35:43] Elizabeth: Right, exactly. [00:35:46] Jeremy: And so most applications, it sounds like it's gonna be a mixture. You're gonna have a lot of things that call user space calls. And then a few, you mentioned more low level ones that are gonna require you to communicate with the kernel. [00:36:00] Elizabeth: Yeah, basically. And it's worth noting that in, in all operating systems, you're, you're almost always gonna be calling a user space library. That might just be a thin wrapper over the kernel call. It might, it's gonna do like just a little bit of work in end call the kernel. [00:36:19] Jeremy: [00:36:19] Elizabeth: In fact, in Windows, that's the only way to do it. Uh, in many other operating systems, you can actually say, you can actually tell the processor to make the kernel call. There is a special instruction that does this and just, and it'll go directly to the kernel, and there's a defined interface for this. But in Windows, that interface is not defined. It's not stable. Or backwards compatible like the rest of Windows is. So even if you wanted to use it, you couldn't. and you basically have to call into the high level libraries or low level libraries, as it were, that, that tell you that create a file. And those don't do a lot. [00:37:00] Elizabeth: They just kind of tweak their parameters a little and then pass them right down to the kernel. [00:37:07] Jeremy: And so wine, it sounds like it needs to implement both the user space calls of windows, but then also the, the kernel, calls as well. But, but wine itself does that, is that only in Linux user space or MacOS user space? [00:37:27] Elizabeth: Yes. This is a very tricky thing. but all of wine, basically all of what is wine runs in, in user space and we use. Kernel calls that are already there to talk to the colonel, to talk to the host Colonel. You have to, and you, you get, you get, you get the sort of second nature of thinking about the Windows, user space and kernel. [00:37:50] Elizabeth: And then there's a host user space and Kernel and wine is running all in user, in the user, in the host user space, but it's emulating the Windows kernel. In fact, one of the weirdest, trickiest parts is I mentioned that you can run some drivers in wine. And those drivers actually, they actually are, they think they're running in the Windows kernel. which in a sense works the same way. It has libraries that it can load, and those drivers are basically libraries and they're making, kernel calls and they're, they're making calls into the kernel library that does some very, very low level tasks that. You're normally only supposed to be able to do in a kernel. And, you know, because the kernel requires some privileges, we kind of pretend we have them. And in many cases, you're even the drivers are using abstractions. We can just implement those abstractions kind of over the slightly higher level abstractions that exist in user space. [00:39:00] Jeremy: Yeah, I hadn't even considered the being able to use hardware devices, but I, I suppose if in, in the end, if you're reproducing the kernel, then whether you're running software or you're talking to a hardware device, as long as you implement the calls correctly, then I, I suppose it works. [00:39:18] Elizabeth: Cause you're, you're talking about device, like maybe it's some kind of USB device that has drivers for Windows, but it doesn't for, for Linux. [00:39:28] Elizabeth: no, that's exactly, that's a, that's kind of the, the example I've used. Uh, I think there is, I think I. My, one of my best success stories was, uh, drivers for a graphing calculator. [00:39:41] Jeremy: Oh, wow. [00:39:42] Elizabeth: That connected via USB and I basically just plugged the windows drivers into wine and, and ran it. And I had to implement a lot of things, but it worked. But for example, something like a graphics driver is not something you could implement in wine because you need the graphics driver on the host. We can't talk to the graphics driver while the host is already doing so. [00:40:05] Jeremy: I see. Yeah. And in that case it probably doesn't make sense to do so [00:40:11] Elizabeth: Right? [00:40:12] Elizabeth: Right. It doesn't because, the transition from user into kernel is complicated. You need the graphics driver to be in the kernel and the real kernel. Having it in wine would be a bad idea. Yeah. [00:40:25] Jeremy: I, I think there's, there's enough APIs you have to try and reproduce that. I, I think, uh, doing, doing something where, [00:40:32] Elizabeth: very difficult [00:40:33] Jeremy: right. Poor system call documentation and private APIs [00:40:35] Jeremy: There's so many different, calls both in user space and in kernel space. I imagine the, the user space ones Microsoft must document to some extent, but, oh. Is that, is that a [00:40:51] Elizabeth: well, sometimes, [00:40:54] Jeremy: Sometimes. Okay. [00:40:55] Elizabeth: I think it's actually better now than it used to be. But some, here's where things get fun, because sometimes there will be, you know, regular documented calls. Sometimes those calls are documented, but the documentation isn't very good. Sometimes programs will just sort of look inside Microsoft's DLLs and use calls that they aren't supposed to be using. Sometimes they use calls that they are supposed to be using, but the documentation has disappeared. just because it's that old of an API and Microsoft hasn't kept it around. sometimes some, sometimes Microsoft, Microsoft own software uses, APIs that were never documented because they never wanted anyone else using them, but they still ship them with the operating system. there was actually a kind of a lawsuit about this because it is an antitrust lawsuit, because by shipping things that only they could use, they were kind of creating a trust. and that got some things documented. At least in theory, they kind of haven't stopped doing it, though. [00:42:08] Jeremy: Oh, so even today they're, they're, I guess they would call those private, private APIs, I suppose. [00:42:14] Elizabeth: I suppose. Uh, yeah, you could say private APIs. but if we want to get, you know, newer versions of Microsoft Office running, we still have to figure out what they're doing and implement them. [00:42:25] Jeremy: And given that they're either, like you were saying, the documentation is kind of all over the place. If you don't know how it's supposed to behave, how do you even approach implementing them? [00:42:38] Elizabeth: and that's what the conformance tests are for. And I, yeah, I mentioned earlier we have this huge body of conformance tests that double is regression tests. if we see an API, we don't know what to do with or an API, we do know, we, we think we know what to do with because the documentation can just be wrong and often has been. Then we write tests to figure out what it's supposed to behave. We kind of guess until we, and, and we write tests and we pass some things in and see what comes out and see what. The see what the operating system does until we figure out, oh, so this is what it's supposed to do and these are the exact parameters in, and, and then we, and, and then we implement it according to those tests. [00:43:24] Jeremy: Is there any distinction in approach for when you're trying to implement something that's at the user level versus the kernel level? [00:43:33] Elizabeth: No, not really. And like I, and like I mentioned earlier, like, well, I mean, a kernel call is just like a library call. It's just done in a slightly different way, but it's still got, you know, parameters in, it's still got a set of parameters. They're just encoded differently. And, and again, like the, the way kernel calls are done is on a level just above the kernel where you have a library, that just passes things through. Almost verbatim to the kernel and we implement that library instead. [00:44:10] Jeremy: And, and you've been working on i, I think, wine for over, over six years now. [00:44:18] Elizabeth: That sounds about right. Debugging and having broad knowledge of Wine [00:44:20] Jeremy: What does, uh, your, your day to day look like? What parts of the project do you, do you work on? [00:44:27] Elizabeth: It really varies from day to day. and I, I, a lot of people, a lot of, some people will work on the same parts of wine for years. Uh, some people will switch around and work on all sorts of different things. [00:44:42] Elizabeth: And I'm, I definitely belong to that second group. Like if you name an area of wine, I have almost certainly contributed a patch or two to it. there's some areas I work on more than others, like, 3D graphics, multimedia, a, I had, I worked on a compiler that exists, uh, socket. So networking communication is another thing I work a lot on. day to day, I kind of just get, I, I I kind of just get a bug for some program or another. and I take it and I debug it and figure out why the program's broken and then I fix it. And there's so much variety in that. because a bug can take so many different forms like I described, and, and, and the, and then the fix can be simple or complicated or, and it can be in really anywhere to a degree. [00:45:40] Elizabeth: being able to work on any part of wine is sometimes almost a necessity because if a program is just broken, you don't know why. It could be anything. It could be any sort of API. And sometimes you can hand the API to somebody who's got a lot of experience in that, but sometimes you just do whatever. You just fix whatever's broken and you get an experience that way. [00:46:06] Jeremy: Yeah, I mean, I was gonna ask about the specialized skills to, to work on wine, but it sounds like maybe in your case it's all of them. [00:46:15] Elizabeth: It's, there's a bit of that. it's a wine. We, the skills to work on wine are very, it's a very unique set of skills because, and it largely comes down to debugging because you can't use the tools you normally use debug. [00:46:30] Elizabeth: You have to, you have to be creative and think about it different ways. Sometimes you have to be very creative. and programs will try their hardest to avoid being debugged because they don't want anyone breaking their copy protection, for example, or or hacking, or, you know, hacking in sheets. They want to be, they want, they don't want anyone hacking them like that. [00:46:54] Elizabeth: And we have to do it anyway for good and legitimate purposes. We would argue to make them work better on more operating systems. And so we have to fight that every step of the way. [00:47:07] Jeremy: Yeah, it seems like it's a combination of. F being able, like you, you were saying, being able to, to debug. and you're debugging not necessarily your own code, but you're debugging this like behavior of, [00:47:25] Jeremy: And then based on that behavior, you have to figure out, okay, where in all these different systems within wine could this part be not working? [00:47:35] Jeremy: And I, I suppose you probably build up some kind of, mental map in your head of when you get a, a type of bug or a type of crash, you oh, maybe it's this, maybe it's here, or something [00:47:47] Elizabeth: Yeah. That, yeah, there is a lot of that. there's, you notice some patterns, you know, after experience helps, but because any bug could be new, sometimes experience doesn't help and you just, you just kind of have to start from scratch. Finding a bug related to XAudio [00:48:08] Jeremy: At sort of a high level, can you give an example of where you got a specific bug report and then where you had to look to eventually find which parts of the the system were the issue? [00:48:21] Elizabeth: one, one I think good example, that I've done recently. so I mentioned this, this XAudio library that does 3D audio. And if you say you come across a bug, I'm gonna be a little bit generics here and say you come across a bug where some audio isn't playing right, maybe there's, silence where there should be the audio. So you kind of, you look in and see, well, where's that getting lost? So you can basically look in the input calls and say, here's the buffer it's submitting that's got all the audio data in it. And you look at the output, you look at where you think the output should be, like, that library will internally call a different library, which programs can interact with directly. [00:49:03] Elizabeth: And this our high level library interacts with that is the, give this sound to the audio driver, right? So you've got XAudio on top of, um. mdev, API, which is the other library that gives audio to the driver. And you see, well, the ba the buffer is that XAudio is passing into MM Dev, dev API. They're empty, there's nothing in them. So you have to kind of work through the XAudio library to see where is, where's that sound getting lost? Or maybe, or maybe that's not getting lost. Maybe it's coming through all garbled. And I've had to look at the buffer and see why is it garbled. I'll open up it up in Audacity and look at the weight shape of the wave and say, huh, that shape of the wave looks like it's, it looks like we're putting silence every 10 nanoseconds or something, or, or reversing something or interpreting it wrong. things like that. Um, there's a lot of, you'll do a lot of, putting in print fs basically all throughout wine to see where does the state change. Where was, where is it? Where is it? Right? And then where do things start going wrong? [00:50:14] Jeremy: Yeah. And in the audio example, because they're making a call to your XAudio implementation, you can see that Okay, the, the buffer, the audio that's coming in. That part is good. It, it's just that later on when it sends it to what's gonna actually have it be played by the, the hardware, that's when missing. So, [00:50:37] Elizabeth: We did something wrong in a library that destroyed the buffer. And I think on a very, high level a lot of debugging, wine is about finding where things are good and finding where things are bad, and then narrowing that down until we find the one spot where things go wrong. There's a lot of processes that go like that. [00:50:57] Jeremy: like you were saying, the more you see these problems, hopefully the, the easier it gets to, to narrow down where, [00:51:04] Elizabeth: Often. Yeah. Especially if you keep debugging things in the same area. How much code is OS specific?c [00:51:09] Jeremy: And wine supports more than one operating system. I, I saw there was Linux, MacOS I think free BSD. How much of the code is operating system specific versus how much can just be shared across all of them? [00:51:27] Elizabeth: Not that much is operating system specific actually. so when you think about the volume of wine, the, the, the, vast majority of it is the high level code that doesn't need to interact with the operating system on a low level. Right? Because Windows keeps putting, because Microsoft keeps putting lots and lots of different libraries in their operating system. And a lot of these are high level libraries. and even when we do interact with the operating system, we're, we're using cross-platform libraries or we're using, we're using ics. The, uh, so all these operating systems that we are implementing are con, basically conformed to the posix standard. which is basically like Unix, they're all Unix based. Psic is a Unix based standard. Microsoft is, you know, the big exception that never did implement that. And, and so we have to translate its APIs to Unix, APIs. now that said, there is a lot of very operating system, specific code. Apple makes things difficult by try, by diverging almost wherever they can. And so we have a lot of Apple specific code in there. [00:52:46] Jeremy: another example I can think of is, I believe MacOS doesn't support, Vulkan [00:52:53] Elizabeth: yes. Yeah.Yeah, That's a, yeah, that's a great example of Mac not wanting to use, uh, generic libraries that work on every other operating system. and in some cases we, we look at it and are like, alright, we'll implement a wrapper for that too, on top of Yuri, on top of your, uh, operating system. We've done it for Windows, we can do it for Vulkan. and that's, and then you get the Molten VK project. Uh, and to be clear, we didn't invent molten vk. It was around before us. We have contributed a lot to it. Direct3d, Vulkan, and MoltenVK [00:53:28] Jeremy: Yeah, I think maybe just at a high level might be good to explain the relationship between Direct 3D or Direct X and Vulcan and um, yeah. Yeah. Maybe if you could go into that. [00:53:42] Elizabeth: so Direct 3D is Microsoft's 3D API. the 3D APIs, you know, are, are basically a way to, they're way to firstly abstract out the differences between different graphics, graphics cards, which, you know, look very different on a hardware level. [00:54:03] Elizabeth: Especially. They, they used to look very different and they still do look very different. and secondly, a way to deal with them at a high level because actually talking to the graphics card on a low level is very, very complicated. Even talking to it on a high level is complicated, but it gets, it can get a lot worse if you've ever been a, if you've ever done any graphics, driver development. so you have a, a number of different APIs that achieve these two goals of, of, abstraction and, and of, of, of building a common abstraction and of building a, a high level abstraction. so OpenGL is the broadly the free, the free operating system world, the non Microsoft's world's choice, back in the day. [00:54:53] Elizabeth: And then direct 3D was Microsoft's API and they've and Direct 3D. And both of these have evolved over time and come up with new versions and such. And when any, API exists for too long. It gains a lot of croft and needs to be replaced. And eventually, eventually the people who developed OpenGL decided we need to start over, get rid of the Croft to make it cleaner and make it lower level. [00:55:28] Elizabeth: Because to get in a maximum performance games really want low level access. And so they made Vulcan, Microsoft kind of did the same thing, but they still call it Direct 3D. they just, it's, it's their, the newest version of Direct 3D is lower level. It's called Direct 3D 12. and, and, Mac looked at this and they decided we're gonna do the same thing too, but we're not gonna use Vulcan. [00:55:52] Elizabeth: We're gonna define our own. And they call it metal. And so when we want to translate D 3D 12 into something that another operating system understands. That's probably Vulcan. And, and on Mac, we need to translate it to metal somehow. And we decided instead of having a separate layer from D three 12 to metal, we're just gonna translate it to Vulcan and then translate the Vulcan to metal. And it also lets things written for Vulcan on Windows, which is also a thing that exists that lets them work on metal. [00:56:30] Jeremy: And having to do that translation, does that have a performance impact or is that not really felt? [00:56:38] Elizabeth: yes. It's kind of like, it's kind of like anything, when you talk about performance, like I mentioned this earlier, there's always gonna be overhead from translating from one API to another. But we try to, what we, we put in heroic efforts to. And try, try to make sure that doesn't matter, to, to make sure that stuff that needs to be fast is really as fast as it can possibly be. [00:57:06] Elizabeth: And some very clever things have been done along those lines. and, sometimes the, you know, the graphics drivers underneath are so good that it actually does run better, even despite the translation overhead. And then sometimes to make it run fast, we need to say, well, we're gonna implement a new API that behaves more like windows, so we can do less work translating it. And that's, and sometimes that goes into the graphics library and sometimes that goes into other places. Targeting Wine instead of porting applications [00:57:43] Jeremy: Yeah. Something I've found a little bit interesting about the last few years is [00:57:49] Jeremy: Developers in the past, they would generally target Windows and you might be lucky to get a Mac port or a Linux port. And I wonder, like, in your opinion now, now that a lot of developers are just targeting Windows and relying on wine or, or proton to, to run their software, is there any, I suppose, downside to doing that? [00:58:17] Jeremy: Or is it all just upside, like everyone should target Windows as this common platform? [00:58:23] Elizabeth: Yeah. It's an interesting question. I, there's some people who seem to think it's a bad thing that, that we're not getting native ports in the same sense, and then there's some people who. Who See, no, that's a perfectly valid way to do ports just right for this defacto common API it was never intended as a cross platform common API, but we've made it one. [00:58:47] Elizabeth: Right? And so why is that any worse than if it runs on a different API on on Linux or Mac and I? Yeah, I, I, I guess I tend to, I, that that argument tends to make sense to me. I don't, I don't really see, I don't personally see a lot of reason for, to, to, to say that one library is more pure than another. [00:59:12] Elizabeth: Right now, I do think Windows APIs are generally pretty bad. I, I'm, this might be, you know, just some sort of, this might just be an effect of having to work with them for a very long time and see all their flaws and have to deal with the nonsense that they do. But I think that a lot of the. Native Linux APIs are better. But if you like your Windows API better. And if you want to target Windows and that's the only way to do it, then sure why not? What's wrong with that? [00:59:51] Jeremy: Yeah, and I think the, doing it this way, targeting Windows, I mean if you look in the past, even though you had some software that would be ported to other operating systems without this compatibility layer, without people just targeting Windows, all this software that people can now run on these portable gaming handhelds or on Linux, Most of that software was never gonna be ported. So yeah, absolutely. And [01:00:21] Elizabeth: that's [01:00:22] Jeremy: having that as an option. Yeah. [01:00:24] Elizabeth: That's kind of why wine existed, because people wanted to run their software. You know, that was never gonna be ported. They just wanted, and then the community just spent a lot of effort in, you know, making all these individual programs run. Yeah. [01:00:39] Jeremy: I think it's pretty, pretty amazing too that, that now that's become this official way, I suppose, of distributing your software where you say like, Hey, I made a Windows version, but you're on your Linux machine. it's officially supported because, we have this much belief in this compatibility layer. [01:01:02] Elizabeth: it's kind of incredible to see wine having got this far. I mean, I started working on a, you know, six, seven years ago, and even then, I could never have imagined it would be like this. [01:01:16] Elizabeth: So as we, we wrap up, for the developers that are listening or, or people who are just users of wine, um, is there anything you think they should know about the project that we haven't talked about? [01:01:31] Elizabeth: I don't think there's anything I can think of. [01:01:34] Jeremy: And if people wanna learn, uh, more about the wine project or, or see what you're up to, where, where should they, where should they head? Getting support and contributing [01:01:45] Elizabeth: We don't really have any things like news, unfortunately. Um, read the release notes, uh, follow some, there's some, there's some people who, from Code Weavers who do blogs. So if you, so if you go to codeweavers.com/blog, there's some, there's, there's some codeweavers stuff, uh, some marketing stuff. But there's also some developers who will talk about bugs that they are solving and. And how it's easy and, and the experience of working on wine. [01:02:18] Jeremy: And I suppose if, if someone's. Interested in like, like let's say they have a piece of software, it's not working through wine. what's the best place for them to, to either get help or maybe even get involved with, with trying to fix it? [01:02:37] Elizabeth: yeah. Uh, so you can file a bug on, winehq.org,or, or, you know, find, there's a lot of developer resources there and you can get involved with contributing to the software. And, uh, there, there's links to our mailing list and IRC channels and, uh, and, and the GitLab, where all places you can find developers. [01:03:02] Elizabeth: We love to help you. Debug things. We love to help you fix things. We try our very best to be a welcoming community and we have got a long, we've got a lot of experience working with people who want to get their application working. So, we would love to, we'd love to have another. [01:03:24] Jeremy: Very cool. Yeah, I think wine is a really interesting project because I think for, I guess it would've been for decades, it seemed like very niche, like not many people [01:03:37] Jeremy: were aware of it. And now I think maybe in particular because of the, the Linux gaming handhelds, like the steam deck,wine is now something that a bunch of people who would've never heard about it before, and now they're aware of it. [01:03:53] Elizabeth: Absolutely. I've watched that transformation happen in real time and it's been surreal. [01:04:00] Jeremy: Very cool. Well, Elizabeth, thank you so much for, for joining me today. [01:04:05] Elizabeth: Thank you, Jeremy. I've been glad to be here.

This week, Brian & Alexandr dive into:

Your sweet preschooler just turned into a pint-sized whirlwind—kicking, screaming, and even hitting.Before you panic or punish, listen in. Dr Justin and Kylie Coulson unpack why three-year-olds lash out, why it’s actually developmentally normal, and the calm, practical steps that help them (and you) find peace. Key Points Why hitting at age three is common—and not a sign you’re raising a violent teen. The real drivers: big emotions, low impulse control, limited language. Three core responses: stay regulated, set clear limits, redirect with movement or creative outlets. After the storm: empathic conversations and rehearsal for “next time.” Prevention tips: check the HALTS (Hungry, Angry, Lonely, Tired, Stressed) and keep screen time low. Quote of the Episode “Regulating emotions is harder than learning to walk or tie shoelaces. Your job is to stay the adult while your child learns.” – Dr Justin Coulson Resources Mentioned Little People, Big Feelings [Webinar] – practical tools for parents of toddlers and preschoolers. Little People, Big Feelings [The Summit] Action Steps for Parents Stay calm—model the regulation you want your child to learn. State the boundary—“We have gentle hands. Hitting hurts.” Redirect energy—offer drawing, movement, or grounding games. Debrief later—when calm, problem-solve and rehearse next time. Check the basics—food, sleep, connection, and screen habits. See omnystudio.com/listener for privacy information.

Who will stand in the gap?Every one of us knows the pain of living with a gap—between brokenness and healing, despair and hope, sin and redemption. In this message, we dive into Ezekiel 22:30 and discover God's heart for people willing to pray, model, redirect, and invite others to experience the life-changing hope found in Jesus Christ.From personal stories to biblical truth, this teaching unpacks what it means to: • Pray with power through intercessory prayer • Model a life centered on Jesus • Redirect with love and truth in a culture of confusion • Invite others to encounter the Gospel

Apply to the Coaching for Leaders Academy by Friday, September 12th. In this episode, Dave shares five ways to help leaders thrive through inflection points, including: Redirect vs. respond Set team norms Ask a second question Picture tomorrow's commitment today Hold a funeral

Release to Refill and Redirect your energies. Rev Cindy Fuller, Inner Quest Church, Alpharetta, Ga www.innerquestchurch.org

This podcast is brought to you by Outcomes Rocket, your exclusive healthcare marketing agency. Learn how to accelerate your growth by going to⁠ outcomesrocket.com Peace of mind in healthcare is just as important as access to care itself. In this episode, Dr. David Berg, Founder and CEO of Redirect Health, contrasts his experiences with Canadian and U.S. healthcare, noting that while America offers world-class medical care, it often leaves patients without confidence or peace of mind. He explains that uncertainty about affordability and access creates anxiety long before patients enter the system. Redirect Health addresses this by offering a free entry point into care through technology, virtual access, and advocacy, while focusing on logistics, how, and where care is delivered, as the key to lowering costs. David stresses that the U.S. doesn't lack funding; it must redirect resources toward delivering real value and peace of mind. Tune in and learn how healthcare logistics and advocacy can transform both cost and access! Resources: Connect with and follow Dr. David Berg on LinkedIn. Follow Redirect Health on LinkedIn and visit their website! Listen to David's previous interview on our podcast here! Email David directly here.

Kim Korte, creator of the Sensory Sync Method, joins us to discuss how understanding the "ingredients" of our emotions can transform the way we live, heal, and connect. From personal betrayal to emotional empowerment, Kim's story is both relatable and transformative. She introduces listeners to the concept of interoception—our internal sense of emotion—and how to use it to reclaim emotional agency. “We construct our emotions, and understanding the ingredients can give us autonomy over our lives.”

Ever find yourself wide awake at 3 AM, replaying every what if your brain can dream up?

Topics covered in this episode: * rathole* * pre-commit: install with uv* A good example of what functools.Placeholder from Python 3.14 allows Converted 160 old blog posts with AI Extras Joke Watch on YouTube About the show Sponsored by DigitalOcean: pythonbytes.fm/digitalocean-gen-ai Use code DO4BYTES and get $200 in free credit Connect with the hosts Michael: @mkennedy@fosstodon.org / @mkennedy.codes (bsky) Brian: @brianokken@fosstodon.org / @brianokken.bsky.social Show: @pythonbytes@fosstodon.org / @pythonbytes.fm (bsky) Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Monday at 10am PT. Older video versions available there too. Finally, if you want an artisanal, hand-crafted digest of every week of the show notes in email form? Add your name and email to our friends of the show list, we'll never share it. Michael #1: rathole A lightweight and high-performance reverse proxy for NAT traversal, written in Rust. An alternative to frp and ngrok. Features High Performance Much higher throughput can be achieved than frp, and more stable when handling a large volume of connections. Low Resource Consumption Consumes much fewer memory than similar tools. See Benchmark. The binary can be as small as ~500KiB to fit the constraints of devices, like embedded devices as routers. On my server, it's currently using about 2.7MB in Docker (wow!) Security Tokens of services are mandatory and service-wise. The server and clients are responsible for their own configs. With the optional Noise Protocol, encryption can be configured at ease. No need to create a self-signed certificate! TLS is also supported. Hot Reload Services can be added or removed dynamically by hot-reloading the configuration file. HTTP API is WIP. Brian #2: pre-commit: install with uv Adam Johnson pre-commit doesn't natively support uv, but you can get around that with pre-commit-uv $ uv tool install pre-commit --with pre-commit-uv Installing pre-commit like this Installs it globally Installs with uv adds an extra plugin “pre-commit-uv” to pre-commit, so that any Python based tool installed via pre-commit also uses uv Very cool. Nice speedup Brian #3: A good example of what functools.Placeholder from Python 3.14 allows Rodrigo Girão Serrão Remove punctuation functionally Also How to use functools.Placeholder, a blog post about it. functools.partial is cool way to create a new function that partially binds some parameters to another function. It doesn't always work for functions that take positional arguments. functools.Placeholder fixes that with the ability to put in placeholders for spots where you want to be able to pass that in from the outer partial binding. And all of this sounds totally obscure without a good example, so thank you to Rodgrigo for coming up with the punctuation removal example (and writeup) Michael #4: Converted 160 old blog posts with AI They were held-hostage at wordpress.com to markdown and integrated them into my Hugo site at mkennedy.codes Here is the chat conversation with Claude Opus/Sonnet. Had to juggle this a bit because the RSS feed only held the last 50. So we had to go back in and web scrape. That resulted in oddies like comments on wordpress that had to be cleaned etc. Whole process took 3-4 hours from idea to “production”duction”. The chat transcript is just the first round getting the RSS → Hugo done. The fixes occurred in other chats. This article is timely and noteworthy: Blogging service TypePad is shutting down and taking all blog content with it This highlights why your domain name needs to be legit, not just tied to the host. I'm looking at you pyfound.blogspot.com. I just redirected blog.michaelckennedy.net to mkennedy.codes Carefully mapping old posts to a new archived area using NGINX config. This is just the HTTP portion, but note the /sitemap.xml and location ~ "^/([0-9]{4})/([0-9]{2})/([0-9]{2})/(.+?)/?$" { portions. The latter maps posts such as https://blog.michaelckennedy.net/2018/01/08/a-bunch-of-online-python-courses/ to https://mkennedy.codes/posts/r/a-bunch-of-online-python-courses/ server { listen 80; server_name blog.michaelckennedy.net; # Redirect sitemap.xml to new domain location = /sitemap.xml { return 301 ; } # Handle blog post redirects for HTTP -> HTTPS with URL transformation # Pattern: /YYYY/MM/DD/post-slug/ -> location ~ "^/([0-9]{4})/([0-9]{2})/([0-9]{2})/(.+?)/?$" { return 301 ; } # Redirect all other HTTP URLs to mkennedy.codes homepage location / { return 301 ; } } Extras Brian: SMS URLs and Draft SMS and iMessage from any computer keyboard from Seth Larson Test and Code Archive is now up, see announcement Michael: Python: The Documentary | An origin story is out! Joke: Do you know him? He is me.

Daily Boost Podcast Show Notes Motivation Myth: What Really Drives Success September 1, 2025 | Episode - 5171 Host: Scott Smith Episode Description It's Labor Day, and Scott's firing up about motivation – the real kind, not the unicorn-and-rainbows version. He's cutting through the fluff to give you three rock-solid ways to stay motivated when life throws you curveballs. From why your body holds the key to your mindset, to how your self-talk is either building you up or tearing you down, this episode delivers the straight truth about getting what you want. Ready to stop making excuses and start making moves? Featured Story Scott shares his honest take on motivation in 2025, especially for remote workers wondering if they're really working. He dives into the psychology behind what really drives us – spoiler alert: it's not what most people think. Through his signature blend of humor and hard truth, Scott reveals why inspiration almost always leads to automatic motivation and how most people stumble onto their purpose instead of finding it through some grand plan. It's the kick in the pants you didn't know you needed. Important Points Your physiology dictates your feelings more than your psychology – when you move your body, you wake up your emotions and make anything possible. If you're feeling unmotivated, you're not unfocused – you're focused on the wrong thing, and you need to swing that focus around to something that excites you. The words you say to yourself create the emotions you have, and negative self-talk will drag you down faster than anything else in your life. Memorable Quotes "The easiest way for you to break free from a slump or to get what you want is to take a step. Stand up, take a step and repeat." "If you are feeling unmotivated, you are unfocused. You're not unfocused – you're focused on something else." "You want to stay motivated, get excited, period. Boom. Get a big goal. Go after it." Scott's Three-Step Approach Move your body intentionally – lift weights, get out of breath, or at minimum start overwalking to let your default brain kick in with great ideas. Redirect your focus from what's not working to something that genuinely excites you, because focus fuels your motivational fire. Monitor your self-talk ruthlessly and eliminate negative words that talk you out of what you want to accomplish. Connect With Me Search for The Daily Boost on Apple Podcasts and Spotify. Email: support@motivationtomove.com Main Website: https://motivationtomove.com YouTube https://youtube.com/dailyboostpodcast Facebook Page: https://facebook.com/motivationtomove Facebook Group: https://dailyboostpodcast.com/facebook Learn more about your ad choices. Visit megaphone.fm/adchoices

AI is everywhere. From promises of guaranteed rankings in ChatGPT to a flood of so-called “AI experts,” in your LinkedIn feed. The noise can be overwhelming. This Episode of The Redirect Podcast helps marketers sift through the noise that comes with AI advancements to separate the hype from the reality. Special guest Nick LeRoy (SEO Jobs) joins us to discuss what marketers need to pay attention to, he red flags to watch out for, and how to use AI as a tool without falling for scams.

Melody talks with Clayton Inman of Triumphant Quartet about the brotherhood that's kept the group strong for 20+ years, blessing his son Scotty's move to solo ministry, and the “widowmaker” heart scare that nearly stole his voice. It's a candid look at holding plans loosely and trusting God to lead every season.

This is part 18 of "The After Party," our series at Fusion Christian Church on the book of Acts. Follow along as we explore what happened to the church after Jesus ascended to heaven. In this message, Pastor Zac teaches that God is worthy of all glory and warns about what happens when we don't offer it to him.The downward spiral of being a glory hog.Glory hogs start with pride, chase applause, are left empty, and end in death. When we pursue our own glory instead of God's it stems from a place of pride. It starts by thinking that we are greater than our creator. The result is that we continue in a neverending pursuit of something that will never satisfy us anyway. We were made to worship God, and worshipping ourselves does not fill that void. Ultimately, those who worship themselves and live as glory hogs will die apart from God.Glory hogs steal what belongs to God.Part of the reason worshipping yourself leads to death is that we are stealing from God what is rightfully his. It is crazy for us to steal from God and think that there will not be consequences. Of course, by trying to take glory from God, we also starve ourselves of joy bit by bit. So how can we avoid stealing the glory for ourselves?Redirect the praise.By redirecting our praise toward God, we place him back at the center. When we praise God above all else, we are choosing to focus on him. By deciding not to play our own fanfare and instead to prioritize God, we recognize that he is greater and eliminate our own pride.Don't just give God more glory, give him ALL glory.It's not enough for us to give God just a little bit of praise, because he deserves all the praise. We must choose daily to give God all glory, honor, and praise, because reserving any of it for ourselves creates a bastion of pride. We owe God everything simply because he created us and sustains our every breath, and much more because he sent Jesus to die for our sins. It is only right for us to pay what we owe.

Episode 243How 2 Redirect LifeSensers! One of the most common topics that comes up in the manosphere…what traits about a woman makes her a compliment to a man of purpose? This one can be talked about for days on end, but I wanted to share my own thoughts on what makes a woman a compliment to the life I'm working towards on a day to day basis. Granted it's not everything listed in this show, but I believe it would do both men and women a perspective to take into consideration as we all figure out how to master the balance between each other. Looking back at the past and the mistakes as well as accomplishments earned, would you want your kid(s) to follow that same path as you? I'd say some I would want them to follow and other parts I wish they would learn sooner than I did for their own mental health's sake. Learn from others' mistakes such as us as parents and do your best to make your own mark on this earth while you're still here. “Im done with this shit!” How many times have we felt or actually went through with quitting something we were involved in because it became overwhelming to us? I been battling this throughout the journey of life and I believe that talking it out makes it easier to digest in the mind. Some days you just want to say fuck everything and run away. I believe it's all part of the journey of overcoming your own mind. May God and His Universe remove any negative energy you may have stored from reading this. If you dig the episode, click, like, and share on your page. Help build the tribe of healing

This is part two of the framework; if you missed part one, head to episode 175 and start there so you're all caught up.  In this episode of Experiencing Data, I continue my deep dive into the MIRRR UX Framework for designing trustworthy agentic AI applications. Building on Part 1's “Monitor” and “Interrupt,” I unpack the three R's: Redirect, Rerun, and Rollback—and share practical strategies for data product managers and leaders tasked with creating AI systems people will actually trust and use. I explain human-centered approaches to thinking about automation and how to handle unexpected outcomes in agentic AI applications without losing user confidence. I am hoping this control framework will help you get more value out of your data while simultaneously creating value for the human stakeholders, users, and customers. Highlights / Skip to: Introducing the MIRRR UX Framework (1:08) Designing for trust and user adoption plus perspectives you should be including when designing systems. (2:31) Monitor and interrupt controls let humans pause anything from a single AI task to the entire agent (3:17) Explaining “redirection” in the example context of use cases for claims adjusters working on insurance claims—so adjusters (users) can focus on important decisions. (4:35)  Rerun controls: lets humans redo an angentic task after unexpected results, preventing errors and building trust in early AI rollouts (11:12) Rerun vs. Redirect: what the difference is in the context of AI, using additional use cases from the insurance claim processing domain  (12:07) Empathy and user experience in AI adoption, and how the most useful insights come from directly observing users—not from analytics (18:28) Thinking about agentic AI as glue for existing applications and workflows, or as a worker  (27:35) Quotes from Today's Episode The value of AI isn't just about technical capability, it's based in large part on whether the end-users will actually trust and adopt it. If we don't design for trust from the start, even the most advanced AI can fail to deliver value." "In agentic AI, knowing when to automate is just as important as knowing what to automate. Smart product and design decisions mean sometimes holding back on full automation until the people, processes, and culture are ready for it." "Sometimes the most valuable thing you can do is slow down, create checkpoints, and give people a chance to course-correct before the work goes too far in the wrong direction."   "Reruns and rollbacks shouldn't be seen as failures, they're essential safety mechanisms that protect both the integrity of the work and the trust of the humans in the loop. They give people the confidence to keep using the system, even when mistakes happen." "You can't measure trust in an AI system by counting logins or tracking clicks. True adoption comes from understanding the people using it, listening to them, observing their workflows, and learning what really builds or breaks their confidence."   "You'll never learn the real reasons behind a team's choices by only looking at analytics, you have to actually talk to them and watch them work."   "Labels matter, what you call a button or an action can shape how people interpret and trust what will happen when they click it." Quotes from Today's Episode Part 1: The MIRRR UX Framework for Designing Trustworthy Agentic AI Applications 

In this episode, Colleen pulls back the curtain on a personal “bitch slap from the universe” that arrived in the form of a sudden, unexplained expulsion from a coaching program she once considered family. What could have been a spiral into shame became something else entirely—a masterclass in emotional sovereignty. She walks you through the shock, the grief, and the moment she realized: this wasn't actually about her. Instead of chasing fairness or demanding explanations, she chose action over rumination, redirecting her energy toward opportunities that actually align with her values. With candor, humor, and zero self-pity, Colleen models what it looks like to process hurt without handing away your power—and to see a painful ending as a door swinging wide to something better. This is more than a story about rejection; it's a real-time demonstration of the freedom that comes from owning your emotional narrative and refusing to let someone else's decisions define you.    

Got a team member who always finds what's wrong but never what's right?In this episode of The Chris LoCurto Show, we walk through five key ways to lead someone out of constant complaining—and into real contribution.Separate the Person from the Behavior (00:02:52)We show how to approach chronic negativity with curiosity and care, not condemnation.Name the Impact, Not Just the Complaint (00:05:49)Learn how to help them see how their words are affecting morale and team dynamics.Shift Their Identity From Problem-Spotter to Problem-Solver (00:08:24)Redirect that critical energy toward meaningful, solution-focused action.Build a Culture That Rewards Contribution, Not Criticism (00:11:14)We explore how to recognize and reinforce the right behaviors—so others follow.Coach Progress, Not Perfection (00:17:20)Real change takes time. Here's how to keep coaching consistently and patiently.Action Items (00:22:37)Quick steps to help complainers take ownership and turn into culture-builders.Additional Resources (00:23:39)Check out our blog on Unhealthy Attitudes: How Your Leadership Mindset Impacts Your TeamConclusion (00:23:57)Complainers can change—with the right leadership. Let's lead with clarity and care.

Pastor Gabe wraps up our teaching series, A Summer in Judges.

Have you ever struggled to regain control of a talkative class? Do you have a bunch of squirrly kids? Try these simple redirects to quiet and recenter kids so teaching time can be effective. #classroomstruggles #teachingtime #bibleteacher #intentionalchildrensministry

Struggling with watching your husband grab a banana and head out for his 5-mile run while you're sitting with your full breakfast? Feeling guilty about eating meals when your friend skips lunch because she's "too busy"? This episode tackles the comparison trap that's keeping you stuck in eating disorder recovery. Lindsey gets raw and real about why other people's food and exercise choices have absolutely nothing to do with your healing journey. Key Takeaways Other people's food and exercise choices have nothing to do with your recovery You're not comparing apples to apples - you're comparing apples to pineapples Comparison is literally increasing your risk of ED relapse Your recovery is not up for a vote Stop giving mental energy to other people's plates and start celebrating your own healing

Ever wonder what happens after a lead fills out your inquiry form? Spoiler: if you're not sending them to a Redirect Workflow™ (my signature process), you're missing out on bookings!!In this episode, I'm breaking down my exact Redirect Workflow™ the exact one I use and teach my students to effortlessly guide potential clients from inquiry to booked. You'll learn:✨ Why your post-inquiry experience is just as important as your marketing✨ The 3 must-have elements of a high-converting redirect page✨ How to set it up so it nurtures, educates, and builds trust on autopilot✨ And why this small shift could be the biggest game-changer for your conversion ratesIf you've been feeling like inquiries ghost you or don't know what to do next, THIS is your episode. Pull up your notes app because you're about to turn your inquiry process into a conversion machine

It's clear people are looking for ways to protect their peace. And if the comments, DMs, and emails are any indication, they're also looking for permission to do so.That's exactly why this conversation with Katrina Jones on DEI After 5 hit such a nerve. It's one of our most-watched episodes, and it makes sense—this is the stuff so many of us have been trying to name. That quiet unraveling you feel when you're committed to the work, but the workplace doesn't care. That guilt for wanting to step back when the weight of everything is on your shoulders. That slow erosion of your well-being in places that claim to value you but rarely show it.Katrina and I talked candidly about the emotional toll of toxic work environments—especially for those of us doing work that is rooted in justice, inclusion, or lived experience. There's a unique pain that comes with trying to create change in systems that don't want to be changed.But here's what we explored that I think we all need to hear:

Engineering often builds systems to withstand extreme forces. Nature's ecosystems build interconnected systems that never experience them through geometric redirection.Woodpeckers don't have super-strong skulls that absorb 1,200 G-forces—they instead have interconnected geometric features that fragment and redirect energy, so the brain never experiences the full impact. Alain Bujold, a visionary R&D expert with 27 years of experience leading over 140 projects and holding 18 patents, reveals how ecosystemic thinking transforms protection. Unexpected Paradigm Shifts:→ Ecosystemic Energy Management: Nature doesn't isolate protection—bone, geometry, and material work as an interconnected ecosystem to redirect forces→ Energy Redirection Over Absorption: Natural ecosystems fragment and redirect kinetic energy through surface geometry—never experience the full force→ Systems Within Systems: Alain's "local and global" R&D methodology mirrors nature's approach—component details + ecosystem-wide performance→ Shape + Resonance = Protection: Surface geometry controls wave behavior across protective ecosystemsEconomic Reality: 2 million TBI cases annually in the US, 400,000 children hospitalized. Military load-carriage injuries cost billions.The Innovation: Woodpecker-inspired helmet geometry that fragments and redirects impact energy through controlled surface patterns—moving beyond material strength to force redirection through shape alone.Opportunity: Ecosystemic energy redirection could revolutionize aerospace (spacecraft hulls that redirect debris impacts), architecture (buildings that redirect earthquake forces), and automotive (crumple zones across vehicle ecosystems).Getting There: Stop asking "How do we build stronger materials?" Start by asking: "How can we design ecosystemic geometry where interconnected elements ensure our system never experiences the full destructive force?"#EcosystemicFutures #Biomimicry #EnergyRedirection #GeometricDesignGuest: Alain Bujold, R&D Innovation Strategist | 27 Years, 140+ Projects, 18 PatentsHost: Dyan Finkhousen, CEO, Shoshin WorksSeries Hosts: Vikram Shyam, Lead Futurist, NASA Glenn Research Center Dyan Finkhousen, Founder & CEO, Shoshin WorksEcosystemic Futures is provided by NASA Convergent Aeronautics Solutions Project in collaboration with Shoshin Works

Money Talks. What's Yours Saying?This powerful message from the Grown Folks Faith series dives into the words of Jesus from Matthew 6:19–21 to help us confront one of the most spiritual topics of our lives—our finances.God never intended for His people to live in chronic financial stress. Biblical prosperity isn't about excess—it's about having enough: to meet your needs, fulfill your calling, bless your family, and be generous to others.

Money Talks. What's Yours Saying?This powerful message from the Grown Folks Faith series dives into the words of Jesus from Matthew 6:19–21 to help us confront one of the most spiritual topics of our lives—our finances.God never intended for His people to live in chronic financial stress. Biblical prosperity isn't about excess—it's about having enough: to meet your needs, fulfill your calling, bless your family, and be generous to others.

I got this. You got this. We all go this. Create from the internal wellspring of love frequency. Redirect when the scarcity shows up. Firmly and with care. I love you,  Dr. Angela

He guides me along the right paths. . . . — Psalm 23:3 The shepherd's main goal for his sheep is soul care. Our souls suffer when we are running quickly and taking life at a pace that is unsustainable. When we try to chart our own course, we often misjudge the best way forward because we are either impatient for good things to happen or scared that they won't. The psalm writer trusts that the shepherd is guiding him along the right paths and that these paths will lead to flourishing. In some Bible versions these are called paths of righteousness, and that means these pathways honor the shepherd. The way of the shepherd is noble, pure, and ethical, reflecting the very character with which he leads the sheep. Following the right pathways is the best way for the sheep to go because that helps others find and walk in the way of the Lord as well. I can picture the psalm writer reflecting on God's law, summarized in the Ten Commandments, as the best way to live because it leads to flourishing, full life with God. Loving God and our neighbor is the best way to live, creating shalom (peace) with God and his creation, including all of his creatures. Obeying the Lord, honoring our parents and loved ones, and caring for others and their well-being—all these things lead to living God's way and bringing peace. Where are you being led today? Lord, help us to see that empty promises for a better life do not come from you. Redirect us to your path, which leads to life with you. Amen.

In this inspiring conversation, Dominiece Clifton and Kellie Rhymes explore the transformative journey of self-discovery and embracing change. Kellie shares her shift from real estate to supporting women with hair loss, highlighting the power of stillness, clarity, and intuition. They discuss aligning business with purpose, incorporating spirituality into entrepreneurship, and the importance of grounding, slowing down, and releasing control to co-create with the universe. Kellie also offers insights on empowering women through personalized support and advice for early-stage entrepreneurs.Key TakeawaysTransformation requires embracing change and new directions.Self-discovery often comes from moments of stillness.Women face unique challenges with hair loss and identity.Incorporating spirituality into business can alleviate burnout.Releasing control allows for co-creation with the universe.Mindset shifts are essential when facing hair loss challenges.Finding the right coach can significantly impact your journey.Women should feel empowered despite hair loss.About Kellie RhymesKellie Rhymes is a dynamic force in the realm of women's hair loss support and empowerment, serving as the CEO of Limitless Mindset Coaching. Hailing from St. Louis, Missouri, Kellie has made a name for herself as an Authenticity Coach and Rapid Rewire Transformational Practitioner, dedicated to helping women reclaim their confidence. A proud listee in Marquis Who's Who in America 2024, she channels her personal journey with Alopecia into her mission—transforming the lives of women facing hair loss. As a confident bald woman, Kellie not only shares her story but she is also an advocate for the Scarring Alopecia Foundation leading the CCCA support group and real estate investor, demonstrating that resilience and success can flourish, regardless of life's hurdles. Her mission is to inspire others to embrace their beauty regardless of hair loss and live life on their own terms.Connect with Kellie RhymesEmail: kellie@limitlessmindsetcoach.comConnect with Kellie on InstagramConnect with Kellie on LinkedInYouTubeWebsiteBougie Baldie Facebook groupSupport the showIMPORTANT LINKS AND RESOURCES: Discover Where You Are Getting Stuck In Your Business, By Taking My Free 3-minute quiz: https://confusionloop.com/ Women Entrepreneurs, schedule your free Clarity Call here Learn more about Move And Still's service offerings: https://movexstill.com/ CONNECT WITH DOM: Learn about Transformation YOUniversity, my 12-week biz coaching program for women entrepreneurs at https://domrclifton.com/coaching-for-women/ IG - @DominieceRClifton LI- Dominiece R. Clifton Email me: hello@movexstill.com A GIFT FOR YOU! Don't forget to subscribe, rate, and review the show on Apple Podcasts to be entered into a drawing to receive my new book FREE! I will be picking one winner monthly. Just send me the screenshot at hello@movestill.com to enter.

Michelle addresses strategies for women to effectively manage performance reviews, career progression conversations, salary negotiations, and navigating gender biases in the workplace.Key Points:1. Mindset Shift: - Performance reviews are business meetings, not tests. - Move from anxiety to proactive preparation.2. Effective Performance Review Preparation: - Gather evidence continuously; document accomplishments and contributions regularly. - Use the STAR(O) method: Situation, Task, Action, Result, and Outcome for structured evidence. - Prevent "accomplishment amnesia" by keeping ongoing records.3. Setting the Agenda: - Take charge by proactively proposing career goals and objectives. - Reframe missed targets into learning opportunities; emphasize your growth mindset.4. Salary Discussions: - Frame requests using Business Intelligence (BQ): strategic, financial acumen, and ambition. - Use data-backed reasoning, tie your achievements directly to organizational outcomes. - Conduct salary benchmarking to understand industry standards and position yourself effectively. - Clearly communicate compensation expectations using assertive, business-like language. - Timing is crucial; prepare your manager and avoid surprises.5. Career Progression Conversations: - Initiate conversations early; don't wait to be noticed. - Nail your current role to be considered for advancement. - Partner with your manager and strategic mentor in career planning.6. Navigating Personality vs. Performance Feedback: - Recognize gender bias; women frequently receive personality-based feedback. - Redirect vague feedback by asking for specific examples and connect feedback to measurable outcomes. - Counter biased feedback with documented, positive stakeholder evidence.7. Advocating with Confidence: - Confidence is built on competence and courage. - Emphasize BQ—link your contributions explicitly to organizational success. - Use clear, direct, and assertive language; eliminate diminishing phrases. - Practice and prepare for challenging discussions, rehearsing with trusted colleagues or mentors.Key Takeaways:- Prepare continuously: Document achievements regularly.- Advocate proactively: Speak clearly about your career ambitions and compensation.- Understand the system :Navigate gender dynamics and organizational politics effectively.Action Item:Book a proactive conversation with your manager within one month to discuss your performance, career goals, or compensation. Hosted on Acast. See acast.com/privacy for more information.

Send me a Text Message

Send me a Text Message

Michelle Chalfant is a therapist, holistic life coach, speaker, and author. Today on the show we discuss: why your pain is a portal and not the problem, how to reprogram negative self talk, why you need more than self awareness to change your life, how to become a "healthy adult," the real role of "triggers" in your life, how to reinvent yourself and heal and much more. ⚠ WELLNESS DISCLAIMER ⚠ Please be advised; the topics related to mental health in my content are for informational, discussion, and entertainment purposes only. The content is not intended to be a substitute for professional advice, diagnosis, or treatment. Always seek the advice of your mental health professional or other qualified health provider with any questions you may have regarding your current condition. Never disregard professional advice or delay in seeking it because of something you have heard from your favorite creator, on social media, or shared within content you've consumed. If you are in crisis or you think you may have an emergency, call your doctor or 911 immediately. If you do not have a health professional who is able to assist you, use these resources to find help: Emergency Medical Services—911 If the situation is potentially life-threatening, get immediate emergency assistance by calling 911, available 24 hours a day. National Suicide Prevention Lifeline, 1-800-273-TALK (8255) or https://suicidepreventionlifeline.org. SAMHSA addiction and mental health treatment Referral Helpline, 1-877-SAMHSA7 (1-877-726-4727) and https://www.samhsa.gov Learn more about your ad choices. Visit megaphone.fm/adchoices

Convinced that participants need to engage in order to learn, a leader is discouraged after the cheerless rollout of her online learning program. She turns to her coach for help facilitating virtual groups.Tools in this episode:Tone-setting at the opening:Get people engaged by using the chat to think together;Get people engaged by thinking about how they will show up (ground rules);Ask: “How engaged do you want to be?” Rank 1 – 7 in chat. (#3 came from Michael Bungay Stanier who wrote The Coaching Habit and hosts the Change Signal podcast. Much gratitude!)Three facilitation skills:Use learning questions;Redirect; don't be the hub;Activate your deadpan.All our infographics are available for free in our Tools Bin. Help yourself. Tom's most recent conversation with Dave Stachowiak on Coaching for Leaders explored How to Take Initiative. A lively, thought-provoking episode.Coaches! Join us at ICF Los Angeles's Executive Coaching Special Interest Group. Check us out on the ICF-LA website, then come join us!Categories in the archive to explore for more ideas about deepening relationships:Communication SkillsLeading TeamsEpisodes with more tools for engagement:141 - High-Stakes Meetings253 - How to Answer Questions Powerfully213 - How to Re-engage a Team34 - Keeping Repeated Material Fresh175 - Leading Offsites143 - Powerful Tools for Team: Plus / Delta148 - Taming MeetingsAre you coach curious? Talk with Tom. Send him an email here. Additional resources are in our monthly email. Sign up here.Until next time!From The Look & Sound of Leadership team 

When Mark Batterson was 22 years old, his church plant in Chicago failed. “It was embarrassing. It was discouraging. It was a little confusing, to be honest,” Mark said. However, God used that closed door to redirect Mark to start a church plant in Washington, D.C.—this time with a very different outcome. Today, he's pastored National Community Church for nearly 30 years and launched Kingdom-focused businesses to help people in his city.  “I want people to hear my heart here that prayer is not outlining our agenda to God. It's about God outlining his agenda to us.”Hear Mark share his story and more Biblical wisdom on this episode of GPS: God. People. Stories. Connect with us through email at gps@billygraham.org or on Facebook at Billy Graham Radio. If you'd like to know more about beginning a relationship with Jesus Christ, or deepening the faith you already have, visit FindPeacewithGod.net. If you'd like to pray with someone, call our Billy Graham 24/7 Prayer Line at 855-255-7729. 

Here's a simple 5-step method I created to help stay calm, present, and grounded when you're facing uncertainty and bracing for the unknown. In this episode, I'm diving into a mindset strategy that helped me through a really intense week filled with anxiety and uncertainty. When life feels overwhelming and fear creeps in, it's so important to have a simple plan to stay grounded. I'll walk you through the exact five steps I used to calm my mind, stay present, and truly enjoy the moments that mattered most. If you ever find yourself stuck in a cycle of worry, these steps will help you find your way back to peace. Action Plan: 1 - Acknowledge your awareness: Notice when your mind is jumping ahead to worst-case scenarios — awareness gives you back your power. 2 - Set a clear intention: Decide to stay grounded and present, even when challenges are looming. 3 - Focus on your breath: Take three deep, intentional breaths to signal to your body that it's safe. 4 - Tune into your senses: Name three things you can see, hear, or feel to anchor yourself to the present moment. 5 - Redirect your thoughts: Practice gratitude, flip a negative "what if" into a positive one, and envision something you're excited about. Get in touch with Megan below. Website | Instagram

The HOPE-PV guide offers us some tactics in safely + effectively pushing back against perpetrators of political violence. Combat the cover-up with the Reveal – Expose the injustice.Combat devaluation + Redeem – Validate the target.Combat reinterpretation + Reframe – Interpret the event as an injustice.Combat official channels + Redirect – Mobilize support and avoid official channels.Combat intimidation or rewards + Resist – Resist intimidation and bribes.RESOURCES:The Free HOPE-PV Guide to ending Political Violence: https://www.endpoliticalviolence.org/guideWhat can I do? Choose Democracy Resource: https://choosedemocracy.us/what-can-i-do/Daniel Hunter's Analysis on Staying Grounded: https://wagingnonviolence.org/2024/11/10-things-to-do-if-trump-wins/?utm_source=Climate+Advocacy+Lab+Members&utm_campaign=8cf646d623-EMAIL_CAMPAIGN_2025_01_22_04_22&utm_medium=email&utm_term=0_-8cf646d623-547145900Democracy is a verb: Interview series: https://wagingnonviolence.org/2024/07/democracy-is-a-verb/#interviewsWisdom from the Fight for Democracy in Serbia. https://wagingnonviolence.org/2024/05/overcoming-despair-apathy-win-democracy-otpor-serbia-ivan-marovic/Donate to Palestinian Children's Relief Fund::www.pcrf.netDonate to Mutual Aid Funds: https://www.folxhealth.com/library/mutual-aid-fundsGET AN OCCASIONAL PERSONAL EMAIL FROM ME: www.makeyourdamnbedpodcast.comTUNE IN ON INSTAGRAM FOR COOL CONTENT: www.instagram.com/mydbpodcastOR BE A REAL GEM + TUNE IN ON PATREON: www.patreon.com/MYDBpodcastOR WATCH ON YOUTUBE: www.youtube.com/juliemerica The opinions expressed by Julie Merica and Make Your Damn Bed Podcast are intended for entertainment purposes only. Make Your Damn Bed podcast is not intended or implied to be a substitute for professional medical advice, diagnosis or treatment. Get bonus content on PatreonSupport this show http://supporter.acast.com/make-your-damn-bed. Hosted on Acast. See acast.com/privacy for more information.

Another day, another phishing campaign abusing google.com open redirects Google s links from it s maps page to hotel listings do suffer from an open redirect vulnerability that is actively exploited to direct users to phishing pages. https://isc.sans.edu/diary/Another%20day%2C%20another%20phishing%20campaign%20abusing%20google.com%20open%20redirects/31950 Adobe Patches Adobe patched 12 different applications. Of particular interest is the update to ColdFusion, which fixes several arbitrary code execution and arbitrary file read problems. https://helpx.adobe.com/security/security-bulletin.html Samsung Patches magicInfo 9 Again Samsung released a new patch for the already exploited magicInfo 9 CMS vulnerability. While the description is identical to the patch released last August, a new CVE number is used. https://security.samsungtv.com/securityUpdates#SVP-MAY-2025 Ivanti Patches Critical Ivanti Neurons Flaw Ivanti released a patch for Ivanti Neurons for ITSM (on-prem only) fixing a critical authentication bypass vulnerability. Ivanti also points to its guidance to secure the underlying IIS server to make exploitation of flaws like this more difficult