Podcasts about say no

First off, this is NOT an episode about Miyavi. Spoiler Alert. No, this episode is about all the shows up on shows currently being watched. Hospital Playlist, NOT Squid Game, Go Go Squid, You Are My Spring, Bite Me, Don't Say No, and more but it's also about the decision of whether to go to the Denver Miyavi show. To read the complete show notes, please visit the official website.

Michael and Lori had to say "no" to recording an episode last week due to life's demands. In this episode they talk about the importance of saying no to our children, to others, and to tasks in order to keep proper order in our lives.

Nobody except the dolts on the Left wants the government telling them what to do and how to live their lives. Government mandates are a form of tyranny and antithetical to the American dream – except this one mandate that our government should ACTUALLY be enforcing. Stu Burguiere will tell you what it is. Then, Glenn Beck joins to preview his newest special and ask the question: Is America heading for a divorce? And, BlazeTV's Jeffy Fisher fills us in on exactly why he's going to be shaving his head. Learn more about your ad choices. Visit megaphone.fm/adchoices

It's okay to say No when something doesn't work for you. No is a complete sentence and a simple way to hold your boundaries..   .   .To help you remember, I created a “No” poster. Go get your printable in the 10 for Tweens Ep. 022 show notes on EmpowerfulGirls.com.

It's a Walker Rant: Why "no" is my 2nd favorite word in sales, plus why and how you should embrace it too! Where to find find Walker: LinkedIn Twitter Instagram www.walkermckay.com

There is so much to juggle while building a business and raising kids.  There is a lot on your plate, mama!  Do you have routines or boundaries in place that support you and your family?  Are you taking care of yourself?  No, I don't mean did you  make time for a bubble bath, but that does sound nice.  I mean, are you addressing what's overwhelming you at the root so you can improve your situation??  So much great info to cover in this amazing episode with guest speaker and business coach, Becca Ribbing.  Tune in for tips and tricks to gain clarity on all things business, family, and overwhelm!Becca is the author of, The Clarity Journal, and has been a coach for over a decade.  She is on a mission to help people break out of the cycles of uncertainty and struggle that hold them back.   All while raising 2 young boys and doing a mix of homeschooling, while navigating the unique challenges a pandemic brings to our lives.  This easy-going conversation touches on how your kids can start helping at home, of course if they are old enough, but also ideas as they grow!  Ideas to get to the root of stress and overwhelm so you truly can take care of yourself and others.  Alternatives to journaling and the traditional meditation.  So much you won't want to miss this one!Topics Covered in this Episode:How to Say No, Set Boundaries, and Communicate EffectivelyThe Self-Care Debacle and Getting To The Root of The ProblemAddressing Feelings of OverwhelmConnect with Becca RibbingWebsite: Becca RibbingAuthor : The Clarity JournalSocial: Becca Ribbing FacebookFind Out More About Your Host Herself Johanna Buss:• Facebook: https://www.facebook.com/johanna.m.buss/• Facebook Group: Next Level Boss Mamas • Website: https://www.johannabuss.comSUBSCRIBE & REVIEW ON APPLE PODCASTSDid you love this episode? Then I would love to have you subscribe! A new episode comes out every week and I have SO many amazing guests/topics on the schedule I would hate for you to miss any.   Click here to subscribe on Apple PodcastsDid something specific resonate with you? Then leave a review! I LOVE reading each and every one of them. They inspire me to keep going and remind me that I am making a difference. I can not tell you enough how much they mean to me! Plus it helps other amazing moms like yourself find this podcast so they can have the same wonderful "ah-ha" moments you did!Wondering how to leave a review? Click here to review, then select “Ratings and Reviews” and “Write a Review”.  So easy and again I can NOT thank you enough!! YOU ROCK!

Raise your hand if you feel exhausted, or that you never have enough time to get everything done. It doesn't have to be this way – finding true life balance is possible! Personal growth expert and national best selling author, Christy Wright is on the pod and ready to give us a crash course on her new book, Take Back Your Time: The Guilt-Free Guide to Life Balance. She reveals the main reasons why we feel out of balance and helps us ditch the distractions in life so we can focus on what really matters. Want more from our guests? Christy Wright Instagram https://www.instagram.com/christybwright/ (@ChristyBWright) https://www.ramseysolutions.com/christy-wright (Website ) How to Say NO https://www.ramseysolutions.com/personal-growth/how-to-say-no-and-stand-your-ground (here)  Check out her book https://www.amazon.com/ideas/amzn1.account.AFYVLW2XYGWWGP5C4AMRCXT26QKQ/234KHYSP8P0K5 (here)! Stay in touch with Sarah too! Follow along on https://www.instagram.com/Bigkidproblems/?hl=en (@bigkidproblems)! Personal Instagram: https://www.instagram.com/sarahmerrill_hall/ (@SarahMerrill_Hall) Find more at www.BigKidProblems.com  Big thank you to our episode sponsors! https://www.morelabs.com/pages/big-kid-problems (Morning Recovery) - ​​Drink smarter with Morning Recovery at MoreLabs.com/bigkid. Use code BIGKID for 20% off your order! http://www.prose.com/bigkid (Prose) - Get your FREE in-depth hair consultation and 15% off your new favorite hair care products at www.prose.com/bigkid Big Kid Problems is a production of http://crate.media (Crate Media)

“This is the season she will make beautiful things, notperfect things, but honest things that speak to who sheis and who she is called to be.” — Morgan Harper Nichols This quote was discovered on the wonderful website of this show's guest, Cynthia Hauk, a mindful art coach. Bet you didn't even know you could create mandalas that would bring you inner calm… but you can. And Cynthia shows us how! But first—I have something to say in this show about when and how to say ‘No' to your family members. Cause sometimes we all have to. Here are the key questions I closed this segment out with. Pull out a journal and have at it friend…. May they serve you well. Whom do you need to set limits with in your life? What would you like to request: When will you request it? Just what will you say? Moving on to my chat with Cynthia Hauk… I learned so much about WHY mindful art is such an enhancement to our slowing down, going with in and picking up the meditative vibe. And PS—this is especially for you if you believe  you can't draw/create. You can, friend. We all can! (Who knew?) Among other things, I learned: What is mindful art? How is mindful art supportive for self-care?  How do you manage an inner critic—and why is she ‘useful'? Why is art so therapeutic? What is soul collage? Analog v Digital technologies for creating What is the 5-Minute Mandala challenge? I hope you enjoy this show… and it gets you slowing down to the speed of life. Submitted with love, RESOURCES How to Say No to the People You Love The Extremely Busy Woman's Guide to Self-Care Cynthia's Mindful Creative Muse Site Cynthia's 5-Minute Mandala Challenge for Destressing Cynthia's Instagram Catherine Anderson's Collage Imagery Book Suzanne's recommended Scrapbook Adhesive Tape MORE ABOUT CYNTHIA Cynthia Hauk, founder of Mindful Creative Muse, is passionate about sharing simple Mindfulness and Art activities to help busy people de-stress and express themselves creatively. Cynthia believes in creating space for our self-care - even if it's only for 5 minutes. Cynthia's calming mandala art challenge can be seen on her YouTube Channel at Mindful Creative Muse, and her online classes and teacher training have supported creatives globally in more than 49 countries. 

If you seek physical healing, emotional healing, relationship coaching, nutrition/lifestyle advice, Dr. Jennifer Lamonica specializes in Chiropractic, Acupuncture, Nutrition, Face Reading and more. Dr. Lamonica is a graduate of New York Chiropractic College and has been a licensed chiropractor since 1984.  She is based out of Mineola, New York.This episode of SHLTMM, Jennifer shares her stories of her mother, Rose, who was widowed at a young age with 4 children. As the oldest of the family, Jennifer had to pick up the slack and help out at home, find a job and be there to support her mother.Jennifer is one of the most compassionate, honest and intelligent people I know. She loves to laugh and sing and is there to help her patients to no end.  

In Daniel 1, four teenagers show us how to be faithful when we are pressured to conform to the world around us.

My daughter Christiana said something very interesting. I was telling her about a house I was considering taking on, but totally willing to say no if I didn't get the price and the other parameters that I wanted. She said. "If I were ever to have my own cleaning business that would be really hard for me to do. I'm a people pleaser."  I thought about that and it's so true. There's something called the disc profile that helps put people into personality boxes. It's a useful analysis that helps us understand ourselves and others around us. We can learn things like traits, work styles, tendencies, best way to communicate with each other. D – Dominance – direct, firm, strong-willed, results orientedI – influence – high positive energy, outgoing, optimistic, enthusiasticS – Steadiness – accommodating, patient, humble, calmC – Conscientiousness – accurate, analytical, precise, privateGenerally speaking, the D's and I's are extraverts, while the C's and S's are introverts. D's run people over. I's love to be around people. S's are people pleasers. C's are people avoiders. I highly encourage you to take a free online assessment. However, I can guess which one you are. How would I know? You're a SOLO cleaner for a reason. You like to be by yourself working. You are a people pleaser in most cases. You are high detail. This makes you an introvert and probably on the S-C line somewhere. Some of you are I's and D's, but the majority are C's and S's. Let's continue.Since most of you are C's and S's, let's consider the weaknesses of each.  The C's are high-detail and hard to please. They tend to be perfectionists. As much as they want to get faster, they struggle with their own personality. It's an uphill battle. These C's will need to overcome perfectionism with excellence. I have two podcasts on this - Perfection Vs. Excellence & Accept the Uncertainty. Listen to them again and again!!!Read the rest of this article at the Smart Cleaning School website

Strategies from a survivor. 9% of the population will have an eating disorder in their lifetime. Faith Alicia helps THIS father and his careless comment understand how and why eating disorders work and hurt families. She also provides the support to get back on track.

D&S read from their mothers bible, The IRS, Say NO to drugs. Visit https://MyPillow.com Save up to 66%, use Code: DS21 Follow Diamond and Silk at https://ChatDit.com Follow Diamond and Silk on https://Gettr.com See omnystudio.com/listener for privacy information.

IN THIS EPISODE: Ugh! Once again I fall for the narcissist's trap. He texted and texted and texted, and then when I texted, I got my hand slapped. It made me furious and was upsetting. There's a reason why all the mental health experts insist on no contact when dealing with a narcissist. First came the love bombing, then came the gas lighting and devaluing, then the discarding, and now here I was doing the whole walking on eggshells dance. I was so over it. But nothing was going to take away my happiness because I had a fantastic meeting with the credit union and turned in all my paperwork for our mortgage. AND, I'd lost a couple more pounds and felt great!Support the show (http://paypal.me/mlindbloom989)

Kevin Fonseca returns and we get to talk about 1 year of Say No More and how the show evolved to what it is now! Kevin gets to talk about the Great Facebook/Instagram outage on Monday! And we get to talk about the recent David Dobrik/Durte Dom situation. --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app --- Send in a voice message: https://anchor.fm/say-no-more3/message

Dallas-based Southwest Airlines is the latest major company to announce a vaccine mandate for its employees. WBAP Correspondent Clayton Neville is here to give you the latest details. But a lot of companies are complying with Walter Biden's federal vaccine mandate. What if you get fired because you refuse to get the shot, but you can't get a job anywhere because you're not vaccinated? If you have a family, a mortgage, bills, kids in college...what are you going to do? The Rick Roberts Show is on NewsTalk 820 WBAP ... (Photo Courtesy of WFAA) See omnystudio.com/listener for privacy information.

Longtime listener and friend of the show, Gio Lodi, released a book y'all should check out and Chris and Steph ruminate on a listener question about tension around marketing in open-source. Say No To More Process, Say Yes To Trust by German Velasco (https://thoughtbot.com/blog/say-no-to-more-process-say-yes-to-trust) Test-Driven Development in Swift with SwiftUI and Combine by Gio Lodi (https://tddinswift.com/) Transcript: CHRIS: Our golden roads. STEPH: All right. I am also golden. CHRIS: [vocalization] STEPH: Oh, I haven't listened to that episode where I just broke out in song in the middle. Oh, you're about to add the [vocalization] [chuckles]. CHRIS: I don't know why, though. Oh, golden roads, Golden Arches. STEPH: Golden Arches, yeah. CHRIS: Man, I did not know that my brain was doing that, but my brain definitely connected those without telling me about it. STEPH: [laughs] CHRIS: It's weird. People talk often about the theory that phones are listening, and then you get targeted ads based on what you said. But I'm almost certain it's actually the algorithms have figured out how to do the same intuitive leaps that your brain does. And so you'll smell something and not make the nine steps in between, but your brain will start singing a song from your childhood. And you're like, what is going on? Oh, right, because when I was watching Jurassic Park that one time, we were eating this type of chicken, and therefore when I smell paprika, Jurassic Park theme song. I got it, of course. STEPH: [laughs] CHRIS: And I think that's actually what's happening with the phones. That's my guess is that you went to a site, and the phones are like, cool, I got it, adjacent to that is this other thing, totally. Because I don't think the phones are listening. Occasionally, I think the phones are listening, but mostly, I don't think the phones are listening. STEPH: I definitely think the phones are listening. CHRIS: Hello and welcome to another episode of The Bike Shed, a weekly podcast from your friends at thoughtbot about developing great software. I'm Chris Toomey. STEPH: And I'm Steph Viccari. CHRIS: And together, we're here to share a bit of what we've learned along the way. So, Steph, what's new in your world? STEPH: Hey. So we have a bit of exciting news where we received an email from Gio Lodi, who is a listener of The Bike Shed. And Gio sent an email sharing with us some really exciting news that they have published a book on Test-Driven Development in Swift. And they acknowledge us in the acknowledgments of the book. Specifically, the acknowledgment says, "I also want to thank Chris Toomey and Steph Viccari, who keep sharing ideas on testing week after week on The Bike Shed Podcast." And that's just incredible. I'm so blown away, and I feel officially very famous. CHRIS: This is how you know you're famous when you're in the acknowledgments of a book. But yeah, Gio is a longtime listener and friend of the show. He's written in many times and given us great tips, and pointers, and questions, and things. And I've so appreciated Gio's voice in the community. And it's so wonderful, frankly, to hear that he has gotten value out of the show and us talking about testing. Because I always feel like I'm just regurgitating things that I've heard other people saying about testing and maybe one or two hard-learned truths that I've found. But it's really wonderful. And thank you so much, Gio. And best of luck for anyone out there who is doing Swift development and cares about testing or test-driven development, which I really think everybody should. Go check out that book. STEPH: I must admit my Swift skills are incredibly rusty, really non-existent at this point. It's been so long since I've been in that world. But I went ahead and purchased a copy just because I think it's really cool. And I suspect there are a lot of testing conversations that, regardless of the specific code examples, still translate. At least, that's the goal that you and I have when we're having these testing conversations. Even if they're not specific to a language, we can still talk about testing paradigms and strategies. So I purchased a copy. I'm really looking forward to reading it. And just to change things up a bit, we're going to start off with a listener question today. So this listener question comes from someone very close to the show. It comes from Thom Obarski. Hi, Thom. And Thom wrote in, "So I heard on a recent podcast I was editing some tension around marketing and open source. Specifically, a little perturbed at ReactJS that not only were people still dependent on a handful of big companies for their frameworks, but they also seem to be implying that the cachet of Facebook and having developer mindshare was not allowing smaller but potentially better solutions to shine through. In your opinion, how much does marketing play in the success of an open-source project framework rather than actually being the best tool for the job?" So a really thoughtful question. Thanks, Thom. Chris, I'm going to kick it over to you. What are your thoughts about this question? CHRIS: Yeah, this is a super interesting one. And thank you so much, Thom, although I'm not sure that you're listening at this point. But we'll send you a note that we are replying to your question. And when I saw this one come through, it was interesting. I really love the kernel of the discussion here, but it is, again, very difficult to tease apart the bits. I think that the way the question was framed is like, oh, there's this bad thing that it's this big company that has this big name, and they're getting by on that. But really, there are these other great frameworks that exist, and they should get more of the mindshare. And honestly, I'm not sure. I think marketing is a critically important aspect of the work that we do both in open source and, frankly, everywhere. And I'm going to clarify what I mean by that because I think it can take different shapes. But in terms of open-source, Facebook has poured a ton of energy and effort and, frankly, work into React as a framework. And they're also battle testing it on facebook.com, a giant website that gets tons of traffic, that sees various use cases, that has all permissions in there. They're really putting it through the wringer in that way. And so there is a ton of value just in terms of this large organization working on and using this framework in the same way that GitHub and using Rails is a thing that is deeply valuable to us as a community. So I think having a large organization associated with something can actually be deeply valuable in terms of what it produces as an outcome for us as consumers of that open-source framework. I think the other idea of sort of the meritocracy of the better framework should win out is, I don't know, it's like a Field of Dreams. Like, if you build it, they will come. It turns out I don't believe that that's actually true. And I think selling is a critical part of everything. And so if I think back to DHH's original video from so many years ago of like, I'm going to make a blog in 15 minutes; look at how much I'm not doing. That was a fantastic sales pitch for this new framework. And he was able to gain a ton of attention by virtue of making this really great sales pitch that sold on the merits of it. But that was marketing. He did the work of marketing there. And I actually think about it in terms of a pull request. So I'm in a small organization. We're in a private repo. There's still marketing. There's still sales to be done there. I have to communicate to someone else the changes that I'm making, why it's valuable to the system, why they should support this change, this code coming into the codebase. And so I think that sort of communication is as critical to the whole conversation. And so the same thing happens at the level of open source. I would love for the best framework to always win, but we also need large communities with Stack Overflow answers and community-supported plugins and things like that. And so it's a really difficult thing to treat marketing as just other, this different, separate thing when, in fact, I think they're all intertwined. And marketing is critically important, and having a giant organization behind something can actually have negative aspects. But I think overall; it really is useful in a lot of cases. Those are some initial thoughts. What do you think, Steph? STEPH: Yeah, those are some great initial thoughts. I really agree with what you said. And I also like how you brought in the comparison of pull requests and how sales is still part of our job as developers, maybe not in the more traditional sense but in the way that we are marketing and communicating with the team. And circling back to what you were saying earlier about a bit how this is phrased, I think I typically agree that there's nothing nefarious that's afoot in regards to just because a larger company is sponsoring an open-source project or they are the ones responsible for it, I don't think there's anything necessarily bad about that. And I agree with the other points that you made where it is helpful that these teams have essentially cultivated a framework or a project that is working for their team, that is helping their company, and then they have decided to open source it. And then, they have the time and energy that they can continue to invest in that project. And it is battle-tested because they are using it for their own projects as well. So it seems pretty natural that a lot of us then would gravitate towards these larger, more heavily supported projects and frameworks. Because then that's going to make our job easier and also give us more trust that we can turn to them when we do need help or have issues. Or, like you mentioned, when we need to look up documentation, we know that that's going to be there versus some of the other smaller projects. They may also be wonderful projects. But if they are someone that's doing this in their spare time just on the weekends and yet I'm looking for something that I need to be incredibly reliable, then it probably makes sense for me to go with something that is supported by a team that's getting essentially paid to work on that project, at least that they're backed by a larger company. Versus if I'm going with a smaller project where someone is doing some wonderful work, but realistically, they're also doing it more on the weekends or in their spare time. So boiling it down, it's similar to what you just said where marketing plays a very big part in open source, and the projects and frameworks that we adopt, and the things that we use. And I don't think that's necessarily a bad thing. CHRIS: Yeah. I think, if anything, it's possibly a double-edged sword. Part of the question was around does React get to benefit just by the cachet of Facebook? But Facebook, as a larger organization sometimes that's a positive thing. Sometimes there's ire that is directed at Facebook as an organization. And as a similar example, my experience with Google and Microsoft as large organizations, particularly backing open-source efforts, has almost sort of swapped over time, where originally, Microsoft there was almost nothing of Microsoft's open-source efforts that I was using. And I saw them as this very different shape of a company that I probably wouldn't be that interested in. And then they have deeply invested in things like GitHub, and VS Code, and TypeScript, and tons of projects that suddenly I'm like, oh, actually, a lot of what I use in the world is coming from Microsoft. That's really interesting. And at the same time, Google has kind of gone in the opposite direction for me. And I've seen some of their movements switch from like, oh Google the underdog to now they're such a large company. And so the idea that the cachet, as the question phrase, of a company is just this uniformly positive thing and that it's perhaps an unfair benefit I don't see that as actually true. But actually, as a more pointed example of this, I recently chose Svelte over React, and that was a conscious choice. And I went back and forth on it a few times, if we're being honest, because Svelte is a much smaller community. It does not have the large organizational backing that React or other frameworks do. And there was a certain marketing effort that was necessary to raise it into my visibility and then for me to be convinced that there is enough there, that there is a team that will maintain it, and that there are reasons to choose that and continue with it. And I've been very happy with it as a choice. But I was very conscious in that choice that I'm choosing something that doesn't have that large organizational backing. Because there's a nicety there of like, I trust that Facebook will probably keep investing in React because it is the fundamental technology of the front end of their platform. So yeah, it's not going to go anywhere. But I made the choice of going with Svelte. So it's an example of where the large organization didn't win out in my particular case. So I think marketing is a part of the work, a part of the conversation. It's part of communication. And so I am less negative on it, I think, than the question perhaps was framed, but as always, it depends. STEPH: Yeah, I'm trying to think of a scenario where I would be concerned about the fact that I'm using open source that's backed by a specific large company or corporation. And the main scenario I can think of is what happens when you conflict or if you have values that conflict with a company that is sponsoring that project? So if you are using an open-source project, but then the main community or the company that then works on that project does something that you really disagree with, then what do you do? How do you feel about that situation? Do you continue to use that open-source project? Do you try to use a different open-source project? And I had that conversation frankly with myself recently, thinking through what to do in that situation and how to view it. And I realize this may not be how everybody views it, and it's not appropriate for all situations. But I do typically look at open-source projects as more than who they are backed by, but the community that's actively working on that project and who it benefits. So even if there is one particular group that is doing something that I don't agree with, that doesn't necessarily mean that wholesale I no longer want to be a part of this community. It just means that I still want to be a part, but I still want to share my concerns that I think a part of our community is going in a direction that I don't agree with or I don't think is a good direction. That's, I guess, how I reason with myself; even if an open-source project is backed by someone that I don't agree with, either one, you can walk away. That seems very complicated, depending on your dependencies. Or two, you find ways to then push back on those values if you feel that the community is headed in a direction that you don't agree with. And that all depends on how comfortable you are and how much power you feel like you have in that situation to express your opinion. So it's a complicated space. CHRIS: Yeah, that is a super subtle edge case of all of this. And I think I aligned with what you said of trying to view an open-source project as more generally the community that's behind it as opposed to even if there's a strong, singular organization behind it. But that said, that's definitely a part of it. And again, it's a double-edged sword. It's not just, oh, giant company; this is great. That giant company now has to consider this. And I think in the case of Facebook and React, that is a wonderful hiring channel for them. Now all the people that use React anywhere are like, "Oh man, I could go work at Facebook on React? That's exciting." That's a thing that's a marketing tool from a hiring perspective for them. But it cuts both ways because suddenly, if the mindshare moves in a different direction, or if Facebook as an organization does something complicated, then React as a community can start to shift away. Maybe you don't move the current project off of it, but perhaps you don't start the next one with it. And so, there are trade-offs and considerations in all directions. And again, it depends. STEPH: Yeah. I think overall, the thing that doesn't depend is marketing matters. It is a real part of the ecosystem, and it will influence our decisions. And so, just circling back to Thom's question, I think it does play a vital role in the choices that we make. CHRIS: Way to stick the landing. STEPH: Thanks. Mid-roll Ad And now a quick break to hear from today's sponsor, Scout APM. Scout APM is leading-edge application performance monitoring that's designed to help Rails developers quickly find and fix performance issues without having to deal with the headache or overhead of enterprise platform feature bloat. With a developer-centric UI and tracing logic that ties bottlenecks to source code, you can quickly pinpoint and resolve those performance abnormalities like N+1 queries, slow database queries, memory bloat, and much more. Scout's real-time alerting and weekly digest emails let you rest easy knowing Scout's on watch and resolving performance issues before your customers ever see them. Scout has also launched its new error monitoring feature add-on for Python applications. Now you can connect your error reporting and application monitoring data on one platform. See for yourself why developers call Scout their best friend and try our error monitoring and APM free for 14 days; no credit card needed. And as an added-on bonus for Bike Shed listeners, Scout will donate $5 to the open-source project of your choice when you deploy. Learn more at scoutapm.com/bikeshed. That's scoutapm.com/bikeshed. STEPH: Changing topics just a bit, what's new in your world? CHRIS: Well, we had what I would call a mini perfect storm this week. We broke the build but in a pretty solid way. And it was a little bit difficult to get it back under control. And it has pushed me ever so slightly forward in my desire to have a fully optimized CI and deploy pipeline. Mostly, I mean that in terms of ratcheting. I'm not actually going to do anything beyond a very small set of configurations. But to describe the context, we use pull requests because that's the way that we communicate. We do code reviews, all that fun stuff. And so there was a particular branch that had a good amount of changes, and then something got merged. And this other pull request was approved. And that person then clicked the rebase and merge button, which I have configured the repository, so that merge commits are not allowed because I'm not interested in that malarkey in our history. But merge commits or rebase and merge. I like that that makes sense. In this particular case, we ran into the very small, subtle edge case of if you click the rebase and merge button, GitHub is now producing a new commit that did not exist before, a new version of the code. So they're taking your changes, and they are rebasing them onto the current main branch. And then they're attempting to merge that in. And A, that was allowed. B, the CI configuration did not require that to be in a passing state. And so basically, in doing that rebase and merge, it produced an artifact in the build that made it fail. And then attempting to unwind that was very complicated. So basically, the rebase produced...there were duplicate changes within a given file. So Git didn't see it as a conflict because the change was made in two different parts of the file, but those were conflicting changes. So Git was like, this seems like it's fine. I can merge this, no problem. But it turns out from a functional perspective; it did not work. The build failed. And so now our main branch was failing and then trying to unwind that it just was surprisingly difficult to unwind that. And it really highlighted the importance of keeping the main branch green, keeping the build always passing. And so, I configured a few things in response to this. There is a branch protection rule that you can enable. And let me actually pull up the specific configuration that I set up. So I now have enabled require status checks to pass before merging, which, if we're being honest, I thought that was the default. It turns out it was not the default. So we are now requiring status checks to pass before merging. I'm fully aware of the awkward, painful like, oh no, the build is failing but also, we have a bug. We need to deploy this. We must get something merged in. So hopefully, if and when that situation presents itself, I will turn this off or somehow otherwise work around it. But for now, I would prefer to have this as a yeah; this is definitely a configuration we want. So require status checks to pass before merging and then require branches to be up to date before merging. So the button that does the rebase and merge, I don't want that to actually do a rebase on GitHub. I want the branch to already be up to date. Basically, I only ever want fast-forward merges on our main branch. So all code should be ahead of main, and we are simply updating what main points at. We are not creating new code. That code has run on CI, that version of the code specifically. We are fully rebased and up to date on top of main, and that's how we're going. STEPH: All of that is super interesting. I have a question about the workflow. I want to make sure I'm understanding it correctly. So let's say that I have issued a PR, and then someone else has merged into the main branch. So now my PR is behind me, and I don't have that latest commit. With the new configuration, can I still use the rebase and merge, or will I need to rebase locally and then push up my branch before I can merge into main but at least using the GitHub UI? CHRIS: I believe that you would be forced to rebase locally, force push, and then CI would rebuild, and that's what it is. So I think that's what require branches to be up to date before merging means. So that's my hope. That is the intention here. I do realize that's complicated. So this requirement, which I like, because again, I really want the idea that no, no, no, we, the developers, are in charge of that final state. That final state should always run as part of a build of CI on our pull request/branch before going into main. So no code should be new. There should be no new commits that have never been tested before going into main. That's my strong belief. I want that world. I realize that's...I don't know. Maybe I'm getting pedantic, or I'm a micromanager of the Git history or whatever. I'm fine with any of those insults that people want to lob at me. That's fine. But that's what I feel. That said, this is a nuisance. I'm fully aware of that. And so imagine the situation where we got a couple of different things that have been in flight. People have been working on different...say there are three pull requests that are all coming to completion at the same time. Then you start to go to merge something, and you realize, oh no, somebody else just merged. So you rebase, and then you wait for CI to build. And just as the CI is completing, somebody else merges something, and you're like, ah, come on. And so then you have to one more time rebase, push, wait for the build to be green. So I get that that is not an ideal situation. Right now, our team is three developers. So there are a few enough of us that I feel like this is okay. We can manage this via human intervention and just deal with the occasional weight. But in the back of my mind, of course, I want to find a better solution to this. So what I've been exploring…there's a handful of different utilities that I'm looking at, but they are basically merged queues as an idea. So there are three that I'm looking at, or maybe just two, but there's mergify.io, which is a hosted solution that does this sort of thing. And then Shopify has a merge queue implementation that they're running. So the idea with this is when you as a developer are ready to merge something, you add a label to it. And when you add that label, there's some GitHub Action or otherwise some workflow in the background that sees that this has happened and now adds it to a merge queue. So it knows all of the different things that might want to be merged. And this is especially important as the team grows so that you don't get that contention. You can just say, "Yes, I would like my changes to go out into production." And so, when you label it, it then goes into this merge queue. And the background system is now going to take care of any necessary rebases. It's going to sequence them, so it's not just constantly churning all of the branches. It's waiting because it knows the order that they're ideally going to go out in. If CI fails for any of them because rebasing suddenly, you're in an inconsistent state; if your build fails, then it will kick you out of the merge queue. It will let you know. So it will send you a notification in some manner and say, "Hey, hey, hey, you got to come look at this again. You've been kicked out of the merge queue. You're not going to production." But ideally, it adds that layer of automation to, frankly, this nuisance of having to keep things up to date and always wanting code to be run on CI and on a pull request before it gets into main. Then the ideal version is when it does actually merge your code, it pings you in Slack or something like that to say, "Hey, your changes just went out to production." Because the other thing I'm hoping for is a continuous deployment. STEPH: The idea of a merge queue sounds really interesting. I've never worked with a process like that. And one of the benefits I can see is if I know I'm ready for something to go like if I'm waiting on a green build and I'm like, hey, as soon as this is green, I'd really like for it to get merged. Then currently, I'm checking in on it, so I will restart the build. And then, every so often, I'm going back to say, "Okay, are you green? Are you green? Can I emerge?" But if I have a merge queue, I can say, "Hey, merge queue, when this is green, please go and merge it for me." If I'm understanding the behavior correctly, that sounds really nifty. CHRIS: I think that's a distinct but useful aspect of this is the idea that when you as a developer decide this PR is ready to go, you don't need to wait for either the current build or any subsequent builds. If there are rebases that need to happen, you basically say, "I think this code's good to go. We've gotten the necessary approvals. We've got the buy-in and the teams into this code." So cool, I now market as good. And you can walk away from it, and you will be notified either if it fails to get merged or if it successfully gets merged and deployed. So yes, that dream of like, you don't have to sit there watching the pot boil anymore. STEPH: Yeah, that sounds nice. I do have to ask you a question. And this is related to one of the blog posts that you and I love deeply and reference fairly frequently. And it's the one that's written by German Velasco about Say No to More Process, and Say Yes to Trust. And I'm wondering, based on the pain that you felt from this new commit, going into main and breaking the main build, how do you feel about that balance of we spent time investigating this issue, and it may or may not happen again, and we're also looking into these new processes to avoid this from happening? I'm curious what your thought process is there because it seems like it's a fair amount of work to invest in the new process, but maybe that's justified based on the pain that you felt from having to fix the build previously. CHRIS: Oh, I love the question. I love the subtle pushback here. I love this frame of mind. I really love that blog post. German writes incredible blog posts. And this is one that I just keep coming back to. In this particular case, when this situation occurred, we had a very brief...well, it wasn't even that brief because actually unwinding the situation was surprisingly painful, and we had some changes that we really wanted to get out, but now the build was broken. And so that churn and slowdown of our build pipeline and of our ability to actually get changes out to production was enough pain that we're like, okay, cool. And then the other thing is we actually all were in agreement that this is the way we want things to work anyway, that idea that things should be rebased and tested on CI as part of a pull request. And then we're essentially only doing fast-forward merges on the main branch, or we're fast forward merging main into this new change. That's the workflow that we wanted. So this configuration was really just adding a little bit of software control to the thing that we wanted. So it was an existing process in our minds. This is the thing we were trying to do. It's just kind of hard to keep up with, frankly. But it turns out GitHub can manage it for us and enforce the process that we wanted. So it wasn't a new process per se. It was new automation to help us hold ourselves to the process that we had chosen. And again, it's minimally painful for the team given the size that we're at now, but I am looking out to the future. And to be clear, this is one of the many things that fall on the list of; man, I would love to have some time to do this, but this is obviously not a priority right now. So I'm not allowed to do this. This is explicitly on the not allowed to touch list, but someday. I'm very excited about this because this does fundamentally introduce some additional work in the pipeline, and I don't want that. Like you said, is this process worth it for the very small set of times that it's going to have a bad outcome? But in my mind, the better version, that down the road version where we have a merge queue, is actually a better version overall, even with just a tiny team of three developers that are maybe never even conflicting in our merges, except for this one standout time that happens once every three months or whatever. This is still nicer. I want to just be able to label a pull request and walk away and have it do the thing that we have decided as a team that we want. So that's the dream. STEPH: Oh, I love that phrasing, to label a pull request and be able to walk away. Going back to our marketing, that really sells that merge queue to me. [laughs] Mid-roll Ad And now we're going to take a quick break to tell you about today's sponsor, Orbit. Orbit is mission control for community builders. Orbit offers data analytics, reporting, and insights across all the places your community exists in a single location. Orbit's origins are in the open-source and developer relations communities. And that continues today with an active open-source culture in an accessible and documented API. With thousands of communities currently relying on Orbit, they are rapidly growing their engineering team. The company is entirely remote-first with team members around the world. You can work from home, from an Orbit outpost in San Francisco or Paris, or find yourself a coworking spot in your city. The tech stack of the main orbit app is Ruby on Rails with JavaScript on the front end. If you're looking for your next role with an empathetic product-driven team that prides itself on work-life balance, professional development, and giving back to the larger community, then consider checking out the Orbit careers page for more information. Bonus points if working in a Ruby codebase with a Ruby-oriented team gives you a lot of joy. Find out more at orbit.love/weloveruby. CHRIS: To be clear, and this is to borrow on some of Charity Majors' comments around continuous deployment and whatnot, is a developer should stay very close to the code if they are merging it. Because if we're doing continuous deployment, that's going to go out to production. If anything's going to happen, I want that individual to be aware. So ideally, there's another set of optimizations that I need to make on top of this. So we've got the merge queue, and that'll be great. Really excited about that. But if we're going to lean into this, I want to optimize our CI pipeline and our deployment pipeline as much as possible such that even in the worst case where there's three different builds that are fighting for contention and trying to get out, the longest any developer might go between labeling a pull request and saying, "This is good to go," and it getting out to production, again, even if they're contending with other PRs, is say 10, 15 minutes, something like that. I want Slack to notify them and them to then re-engage and keep an eye on things, see if any errors pop up, anything like that that they might need to respond to. Because they're the one that's got the context on the code at that point, and that context is decaying. The minute you've just merged a pull request and you're walking away from that code, the next day, you're like, what did I work on? I don't remember that at all. That code doesn't exist anymore in my brain. And so,,, staying close to that context is incredibly important. So there's a handful of optimizations that I've looked at in terms of the CircleCI build. I've talked about my not rebuilding when it actually gets fast-forward merged because we've already done that build on the pull request. I'm being somewhat pointed in saying this has to build on a pull request. So if it did just build on a pull request, let's not rebuild it on main because it's identically the same commit. CircleCI, I'm looking at you. Give me a config button for that, please. I would really love that config button. But there are a couple of other things that I've looked at. There's RSpec::Retry from NoRedInk, which will allow for some retry semantics. Because it will be really frustrating if your build breaks and you fall out of the merge queue. So let's try a little bit of retry logic on there, particularly around feature specs, because that's where this might happen. There's Knapsack Pro which is a really interesting thing that I've looked at, which does parallelization of your RSpec test suite. But it does it in a different way than say Circle does. It actually runs a build queue, and each test gets sent over, and they have build agents on their side. And it's an interesting approach. I'm intrigued. I think it could use some nice speed-ups. There's esbuild on the Heroku side so that our assets build so much more quickly. There are lots of things. I want to make it very fast. But again, this is on the not allowed to do it list. [laughs] STEPH: I love how most of the world has a to-do list, and you have this not-allowed to-do list that you're adding items to. And I'm really curious what all is on the not allowed to touch lists or not allowed to-do list. [laughs] CHRIS: I think this might be inherent to being a developer is like when I see a problem, I want to fix it. I want to optimize it. I want to tweak it. I want to make it so that that never happens again. But plenty of things...coming back to German's post of Say No to More Process, some things shouldn't be fixed, or the cost of fixing is so much higher than the cost of just letting it happen again and dealing with it manually at that moment. And so I think my inherent nature as a developer there's a voice in my head that is like, fix everything that's broken. And I'm like, sorry. Sorry, brain, I do not have that kind of time. And so I have to be really choosy about where the time goes. And this extends to the team as well. We need to be intentional around what we're building. Actually, there's a feeling that I've been feeling more acutely than ever, but it's the idea of this trade-off or optimization between speed and getting features out into the world and laying the right fundamentals. We're still very early on in this project, and I want to make sure we're thinking about things intentionally. I've been on so many projects where it's many years after it started and when I ask someone, "Hey, why do your background jobs work that way? That's a little weird." And they're like, "Yeah, that was just a thing that happened, and then it never changed. And then, we copied it and duplicated, and that pattern just got reinforced deeply within the app. And at this point, it would cost too much to change." I've seen that thing play out so many times at so many different organizations that I'm overwhelmed with that knowledge in the back of my head. And I'm like, okay, I got to get it just right. But I can't take the time that is necessary to get it, quote, unquote, "Just right." I do not have that kind of time. I got to ship some features. And this tension is sort of the name of the game. It's the thing I've been doing for my entire career. But now, given the role that I have with a very early-stage startup, I've never felt it more acutely. I've never had to be equally as concerned with both sides of that. Both matter all the more now than they ever have before, and so I'm kind of existing in that space. STEPH: I really like that phrasing of that space because that deeply resonates with me as well. And that not allowed to-do list I have a similar list. For me, it's just called a wishlist. And so it's a wishlist that I will revisit every so often, but honestly, most things on there don't get done. And then I'll clear it out every so often when I feel it's not likely that I'm going to get to it. And then I'll just start fresh. So I also have a similar this is what I would like to do if I had the time. And I agree that there's this inclination to automate as well. As soon as we have to do something that felt painful once, then we feel like, oh, we should automate it. And that's a conversation that I often have with myself is at what point is the cost of automation worthwhile versus should we just do this manually until we get to that point? So I love those nuanced conversations around when is the right time to invest further in this, and what is the impact? And what is the cost of it? And what are the trade-offs? And making that decision isn't always clear. And so I think that's why I really enjoy these conversations because it's not a clear rubric as to like, this is when you invest, and this is when you don't. But I do feel like being a consultant has helped me hone those skills because I am jumping around to different teams, and I'm recognizing they didn't do this thing. Maybe they didn't address this or invest in it, and it's working for them. There are some oddities. Like you said, maybe I'll ask, "Why is this? It seems a little funky. What's the history?" And they'll be like, "Yeah, it was built in a hurry, but it works. And so there hasn't been any churn. We don't have any issues with it, so we have just left it." And that has helped reinforce the idea that just because something could be improved doesn't mean it's worthwhile to improve it. Circling back to your original quest where you are looking to improve the process for merging and ensuring that CI stays green, I do like that you highlighted the fact that we do need to just be able to override settings. So that's something that has happened recently this week for me and my client work where we have had PRs that didn't have a green build because we have some flaky tests that we are actively working on. But we recognize that they're flaky, and we don't want that to block us. I'm still shipping work. So I really appreciate the consideration where we want to optimize so that everyone has an easy merging experience. We know things are green. It's trustworthy. But then we also have the ability to still say, "No, I am confident that I know what I'm doing here, and I want to merge it anyways, but thank you for the warning." CHRIS: And the constant pendulum swing of over-correcting in various directions I've experienced that. And as you said, in the back of my mind, I'm like, oh, I know that this setting I'm going to need a way to turn this setting off. So I want to make sure that, most importantly, I'm not the only one on the team who can turn that off because the day that I am away on vacation and the build is broken, and we have a critical bug that we need to fix, somebody else needs to be able to do that. So that's sort of the story in my head. At the same time, though, I've worked on so many teams where they're like, oh yeah, the build has been broken for seven weeks. We have a ticket in the backlog to fix that. And it's like, no, the build has to not be broken for that long. And so I agree with what you were saying of consulting has so usefully helped me hone where I fall on these various spectrums. But I do worry that I'm just constantly over-correcting in one direction or the other. I'm never actually at an optimum. I am just constantly whatever the most recent thing was, which is really impacting my thinking on this. And I try to not do that, but it's hard. STEPH: Oh yeah. I'm totally biased towards my most recent experiences, and whatever has caused me the most pain or success recently. I'm definitely skewed in that direction. CHRIS: Yeah, I definitely have the recency bias, and I try to have a holistic view of all of the things I've seen. There's actually a particular one that I don't want to pat myself on the back for because it's not a good thing. But currently, our test suite, when it runs, there's just a bunch of noise. There's a bunch of other stuff that gets printed out, like a bunch of it. And I'm reminded of a tweet from Kevin Newton, a friend of the show, and I just pulled it up here. "Oh, the lengths I will go to avoid warnings in my terminal, especially in the middle of my green dots. Don't touch my dots." It's a beautiful beauty. He actually has a handful about the green dots. And I feel this feel. When I run my test suite, I just want a sea of green dots. That's all I want to see. But right now, our test suite is just noise. It's so much noise. And I am very proud of...I feel like this is a growth moment for me where I've been like, you know what? That is not the thing to fix today. We can deal with some noise amongst the green dots for now. Someday, I'm just going to lose it, and I'm going to fix it, and it's going to come back to green dots. [chuckles] STEPH: That sounds like such a wonderful children's book or Dr. Seuss. Oh, the importance of green dots or, oh, the places green dots will take you. CHRIS: Don't touch my dots. [laughter] STEPH: Okay. Maybe a slightly aggressive Dr. Seuss, but I still really like it. CHRIS: A little more, yeah. STEPH: On that note of our love of green dots, shall we wrap up? CHRIS: Let's wrap up. The show notes for this episode can be found at bikeshed.fm. STEPH: This show is produced and edited by Mandy Moore. CHRIS: If you enjoyed listening, one really easy way to support the show is to leave us a quick rating or even a review in iTunes, as it really helps other folks find the show. STEPH: If you have any feedback for this or any of our other episodes, you can reach us at @_bikeshed or reach me on Twitter @SViccari. CHRIS: And I'm @christoomey STEPH: Or you can reach us at hosts@bikeshed.fm via email. CHRIS: Thanks so much for listening to The Bike Shed, and we'll see you next week. All: Byeeeeeee!!! Announcer: This podcast was brought to you by thoughtbot. thoughtbot is your expert design and development partner. Let's make your product and team a success.

Arrange a one-on-one call with John Sbrocco and Crystal Hoarau. Learn the Virtue Health Consortium process, and start prospecting with NO IMQs and NO CLAIMS DATA >> CLICK HERE TO CHOOSE DATE / TIME-

Dr. Orient focuses especially on knee replacements, a medical procedure that she says is being used far too often for middle-aged patients who should, in many cases, simply lose weight to lessen the stress on load-bearing joints and other body parts. The dangerous implications of the over-prescription of mood-altering drugs and the unfounded push for universal vaccination against COVID-19...

How often do you take on too much? On today's episode, Albert speaks on the importance of saying no! --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app --- Send in a voice message: https://anchor.fm/uncommonlegend/message

We are finishing our series, Just Say No, with today's message on Bad Attitudes. Pastor John Vereeken will be sharing with us what it looks like to put aside our bad attitudes and change the way we think.

What are boundaries and why do we need them? Why is it hard when someone sets a boundary with us? MK and Sara discuss boundaries they've set with friends, family, their spouses, and ways they struggle with respecting someone else's boundaries. They also go down a Twilight rabbit hole because why wouldn't they?Codependent Book Club RecommendationBoundaries: When to Say Yes, How to Say No to Take Control of Your Life by Henry Cloud and John TownsendCloser to Fine closertofinepodcast@gmail.comwww.instagram.com/closertofinepodMary Katherine Backstrom www.facebook.com/mkbackstromwww.instagram.com/marykatherinebackstromSara Farrell Baker www.facebook.com/sarafarrellbakerwriterwww.instagram.com/sarafarrellbaker/

On this episode we're talking about Halloween being right around the corner and giving you a bunch of potential costume ideas! And it's all for free, you're welcome. We're more importantly discussing what it means to say no- whether it be for plans, commitments, or new activities. We talk about the importance of making time for people in your life and not just checking them off a list. If you have trouble saying no to people, or are looking for Halloween costume ideas, this one's for you!

Episode Summary: In this episode, we talk to author Kelly Balarie about how to train your mind to conquer challenges, defeat doubt, and live victoriously in a world where we have a very real enemy and we must always be battle ready. Quotables from the episode: “A simple girl who loves Jesus and who is just fighting on her own to figure out all of this with God and to learn these battle lessons.' “We know God is the one who validates us.” “Our thoughts are everything. Our thoughts really are our life. If our thoughts go off kilter, our life goes off kilter which is what I was experiencing.” "We are all in a fight to receive God's best for ourselves.” “It's easy to make an idol out of an outcome.” “I don't need an outcome to define who I am. I'm fully loved, I'm adored, I'm chosen, God is with me, God is using me.” “You have to go into the discovery with God. He wants to unveil to you who you really are. And so that's the joy, that's really what our joy is.” “I've got to find out the strategies, and the weapons and the tools and the insights and the wisdom and the new thoughts so that rather than letting myself be hit by the enemy all the time, and just sucker punched behind my house, I'm going to learn how to respond on offense rather defense, proactively rather than reactively and with my every emotion.” “It's not impossible to live victoriously, we can do it. It's a fight but God equips us with peace to do it.” “I need to adjust my game a little and so this book helps us all to get into the right game so that we can really live victoriously.” “I am at peace; I am not anxious; I am strong; I am believing what I never have before, and this is real.” “We get our mind in line with Jesus; we become Battle Ready. “ “The truth is all the power belongs to God and all the grace is His so He loves us when we do and He loves us when we don't. right. And humility is not what we do for God or how much we give to others, yea, like that might be a by-product of humility but true humility is saying, I love you so much Jesus, I love you so much God, I want to be with you and receive from you.” “Let's focus on what matters. Let's get after the real depths of what brings contentment to our hearts.” “It's time now, ladies, for us to rise up like we never have before. You know what, it's time, it's time for us to believe for who God says we are; it's time for us to love like we never have; it's time for us to know how much God loves us.” Scripture References: 2 Corinthians 10:5 “We demolish arguments and every pretension that sets itself up against the knowledge of God, and we take captive every thought to make it obedient to Christ.” Isaiah 41:10 “So do not fear, for I am with you; do not be dismayed, for I am your God. I will strengthen you and help you; I will uphold you with my righteous right hand.”  Recommended Resources: Battle Ready: Train Your Mind to Conquer Challenges, Defeat Doubt, and Live Victoriously by Kelly Balarie Fear Fighting: Awakening Courage to Overcome Your Fears by Kelly Balarie Rest Now: 7 Ways to Say No, Set Boundaries, and Seize Joy by Kelly Balarie Free Download: How To Fight Fearful/Anxious Thoughts and Win Breaking Anxiety's Grip: How to Reclaim the Peace God Promises by Dr. Michelle Bengtson Breaking Anxiety's Grip Free Study Guide Free 7-Day YouVersion Bible Reading Plan for Breaking Anxiety's Grip Hope Prevails: Insights from a Doctor's Personal Journey Through Depression by Dr. Michelle Bengtson, winner of the Christian Literary Award Reader's Choice Award Hope Prevails Bible Study by Dr. Michelle Bengtson, winner of the Christian Literary Award Reader's Choice Award How To Fight Fearful Thoughts and Win 5 Battle Tools to Help in Hard Moments How to Effectively Fight Fearful Thoughts Ask Dr. B: How To Combat Fearful Thoughts How to Control Worry, Fear, and Anxiety to Keep Your Peace Fear or Faith: You Choose Your Rx: 40 Scriptures that Combat Worry, Fear, Anxiety and Panic 5 Truths to Defeat Fear Social Media Links for Host and Guest: To connect with Kelly Balarie: Website / Facebook / Twitter For more hope, stay connected with Dr. Bengtson at: Order Book Breaking Anxiety's Grip / Order Book Hope Prevails  /  Website  /  Blog  /  Facebook / Twitter (@DrMBengtson)  /  LinkedIn  /  Instagram / Pinterest / YouTube Guest: Kelly Balarie is a speaker, blogger, and author of the books Fear Fighting, Battle Ready, and Rest Now. She comes alongside women to help them live wholeheartedly, rather than in uncertainty, fear, and doubt. When Kelly is not writing, she is chilling at the beach with her husband, a latte, and two young children who rightfully demand she build them awesome sandcastles. Hosted By: Dr. Michelle Bengtson Audio Technical Support: Bryce Bengtson

Do your relationships bring you joy or frustrate the heck out of you? How about your job—are you feeling burned out and unfulfilled? This week we're joined by Amina AlTai, a business coach who specializes in helping women overcome imposter syndrome, get clear on their purpose and passions, and create amazing work. We're starting with a super important convo on setting boundaries and releasing codependent tendencies and then diving deep into identifying and stepping into your purpose. Let's get juicy! Complete show notes are HERE New Organic Olivia Instagram HERE Amina's Instagram HERE Shop my herbal formulas HERE

In this episode, Dra. Yvette discusses the topic of saying no—when should you say no, how can you say no, and strategies to help you make a decision and remain firm with it. Tune in to learn more! --- Send in a voice message: https://anchor.fm/yvette14/message

We discuss strategies for escaping “zombie mode,” share a hack to make it easy for people to say “no,” and talk to Crystal Ellefsen about the know-yourself-better question of “What do you want to be known for?”  Get in touch: @gretchenrubin; @elizabethcraft; podcast@gretchenrubin.com Get in touch on Instagram: @GretchenRubin & @LizCraft Get the podcast show notes by email every week here: http://gretchenrubin.com/#newsletter Get the resources and all links related to this episode here: http://happiercast.com/345 Order a copy of Gretchen's new book OUTER ORDER, INNER CALM here: http://outerorderinnercalmbook.com Leave a voicemail message on: 774-277-9336 For information about advertisers and promo codes, go to happiercast.com/sponsors Use promo code HAPPIER to get 50% Build Your Author Platform. Follow Crystal on Instagram: @crystalellefsen Happier with Gretchen Rubin is part of ‘The Onward Project,' a family of podcasts brought together by Gretchen Rubin—all about how to make your life better. Check out the other Onward Project podcasts—Do The Thing, Side Hustle School, Happier in Hollywood and Everything Happens with Kate Bowler. If you liked this episode, please subscribe, leave a review, and tell your friends! Learn more about your ad choices. Visit podcastchoices.com/adchoices

On this episode, Dance Behind the Screen podcast co-host YeaJean Choi interviews artistic director Yoshiko Chuma. They discuss how to “Say No to the Box” and break the confines of categorization. Yoshiko also talks about her experience during Covid-19 and making connections with others. Enjoy this episode! Episode Show kNOwtes Podcast Home

Learn how to manage needy friends and coworkers in your life. In this lesson I teach you communication strategies to help you be assertive, say no, and protect your time. This will allow you to have healthier social interactions, improve relationships, and be a better friend. Get the writeup of the full lesson and podcast of this lesson on our blog: https://explearning.co/blog/lhm7w08g/how-to-manage-needy-friends-and-coworkers---be-assertive,-say-no,-protect-your-time ENROLL IN EXPLEARNING WEB COURSES (FREE trial included):

Welcome to this Monday mindset today. We're going to talk about how to say no and get more results by doing this. It's not easy to say no. We feel if we're saying no, we're going to miss out on something. We don't want to disappoint someone. Maybe we feel like we want to be that person that always says yes. I can do that. What ends up happening is we add more things to our plate, and we get overwhelmed. We don't do anything because we feel like we want to run away. Believe me. I've been there. I've done that. What I want to talk about here today is in this world of business. I'm going to go through three different things here. These are what I want you to consider that will help you say no with confidence.

Today we are getting ready to Just say No to Greed. The bible tells us that we cannot have two masters, God or Money. If we are faithful with our money to God, he will pour out so many blessings upon us we wont know what to do with them. But if we choose to serve money, we will forever be unsatisfied, looking for something to fill us up in all the wrong places. 

1 Samuel 26: Just Say No (Kingdom Building) taught by Pastor Dave Rolph on 09-26-20.

Learning how to say no can be an important part to growing your business. As Screen Printers there have been many customers that you wish you never worked with that in the long run cause more strain and stress on your business. 

Leave me a voicemail with your tips for saying "no": https://www.speakpipe.com/runliftmom Original episodes with Chris about her 100+ pound transformation to Ironman Triathlete:  https://runliftmompod.com/epi9/  https://runliftmompod.com/epi10/ Connect with me: suzy@runliftmompod.com https://instagram.com/runliftmom https://runliftmompod.com/blog https://www.pinterest.com/runliftmom https://www.youTube.com/runliftmom --- Send in a voice message: https://anchor.fm/runliftmom/message

Talking about examples of using food as a bribe (it might not be what you think) and why it is best to avoid this practice!   website: betterbitesrdn.com insta: @betterbites_rdn

Today's guest is Anna Hetzel, from Columbus, Ohio. Anna is the owner and founder of Strange Birds, a business they started five years ago in which they convert copywriting and strategy for websites and community design and strategy.   Anna works with service providers and entrepreneurs who are trying to expand their reach and figure out how to talk to their ideal clients and build more scalable offers through paid online communities.   Hear the fun story about how Anna named their business Strange Birds.   A lot of freelance advice is about how to grow your network. But Anna approached it differently. From day one, they approached it based on relationships: “I didn't give two hoots about how many people I was connected to. What mattered to me was did I have good relationships I was connected to.”   The value of that relationship building showed up when the pandemic hit. Instead of having just a lot of names of people Anna had met, they had real relationships.   Melanie talks about how she hates the traditional cocktail hour networking event where she doesn't know anyone. Anna offers a tip: Anna's goal at those events is to make one friend—not one contact, but one friend. That helped them filter out the noise and overwhelm.   At networking events, we may feel pressured to meet 12 new people and begin to develop opportunities. But opportunities take time. Focus on making one new friend instead.   There's a difference between a network and a community: “It's the difference between a list of contacts versus a group of people that are mutually invested in each other's success.”   Your social media following or your email list is a network. They are not a community; they are your audience.   It can be hard to make friends as an adult! Find what you're good at—like writing or photography—and read related social media posts and comment thoughtfully. Give your energy in that space.   As for virtual events, it's OK to decline those and set boundaries. Do what makes you feel comfortable. That includes not turning on your video during Zoom calls.   Anna uses the five love languages to build relationships in their business too. The love languages are words of affirmation, quality time, acts of service, gift giving and physical touch. Anna modifies the “physical touch” love language for the business world to think of it as “human to human.” Add a human touch, such as by sending gifs of people or a video of you reacting to an email.   Biz Bite: Before tomorrow, write out what an amazing day means to you (both in work and life) and build your business ferociously around those guidelines.   Resources: Sign up for Anna's email list at StrangeBirds.land and receive a quick guide to match your unique skills and simple-to-implement scalable ways to move away from transactional contacts and into real relationships.   Anna on Instagram   Episode #112 of Deliberate Freelancer: How and When to Say No   “Hoatzin: the Strangest Bird in the Amazon?”   Loom (send quick video messages)   What Are the Five Love Languages?  

You don't need to accept the first offer you're given. Saying no can show your conviction and help you hyper-target the best fit firm.

Manny Machado and Fernando Tatis hold a join press conference and say there is no beef between the. Canelo and Caleb Plant fight at their presser. JT The Brick joins us to talk Raiders. Conor McGregor's US tour keeps rolling. Support the show: http://Kaplanandcrew.com See omnystudio.com/listener for privacy information.

Manny Machado and Fernando Tatis hold a join press conference and say there is no beef between the. Canelo and Caleb Plant fight at their presser. JT The Brick joins us to talk Raiders. Conor McGregor's US tour keeps rolling. Support the show: http://Kaplanandcrew.com See omnystudio.com/listener for privacy information.

Permission-Based eating is a way of relating to food, but one that comes with a lot of questions, like is saying no ALWAYS a form a restriction? On today's solo episode of the podcast, Deanna coaches guest Hayley through some of the most common questions and misconceptions of Permission-Based so that you can know when it's best to say yes and when it's best to say no to the foods you love. If you enjoyed today's episode please leave us a 5 star rating and review. To join Built Daily Elite, go to builtdailyelite.com To work with Deanna in the Mentorship program or 1:1, go to builtdaily.com  

Do you feel like you're always saying yes? Maybe it's time to learn how to say no. In this episode of the STRESS-FREE YOU podcast, we share our top tips for learning how to say no and have a less stressful life! STRESS FREE YOU book on Amazon: https://tinyurl.com/mfrdfjmc STRESS FREE WORK book on Amazon: https://tinyurl.com/hjnpsc2b Website: https://www.stressfreeyou.net/

When you are having a day or a moment when you just need POSITIVITY- Lindsay has a FULL ON PLAN for you!   Maybe you're just in a funky headspace and being negative or stuck on something that happened that you want to let go but are having a hard time with it, or you are in an argument with someone close to you, or you're stuck in a complaining loop, or you just got yourself into a mood where you hate everyyyoneeee… we've all had moments or days like allll of these and it can be H-A-R-D to get your way out of it!   Today, Lindsay is sharing 3 hacks for getting the hell out of the negative hole you are sitting in and get into a positive state of mind. And not in a fake, cheesy way.  Like genuinely happy and feeling like you are on track and enjoying your days and being the person that you want to be. Lindsay says… "If I know ANYTHING- I know for sure that the thoughts you think and the words you say create the world that you live in. So it's worth fighting like HELL to get in a happy headspace and stay there." Lindsay is sharing a few hacks and I know at least one will work for you!  Even if you don't have a positive support system or that one go-to positive person that can help lift you out.  That's ok!  You can do this on your own! It's so important to be positive because its how you SEE and REACT to the world!  It's how you label things and interpret things! A few topics Lindsay discusses: --Music as your mantra --Find your most positive person in your crew --OR get it virtually! Find people that inspire you- and listen to them like they are your friends! **especially important to interrupt your thinking when you are off! -And STOP the things that make you feel like hell! -Don't let yourself go down a spiral! -Sometimes - we need a down day!!  Remove yourself from the world and get re-centered. -TUNE OUT the negativity if it is someone else!!  Tell them or don't! -SUBMERGE YOURSELF in all the positives -Get in as many 10s as you can -SAY NO to anything that sounds awful - remove it all - we are rebooting here - we aren't saying YES to be nice. -We have to be nice to ourselves first.  We can't pour from an empty cup!!! CHEERS to living in your happiest headspace!

In today's Monday Message, Emily talks about something we all struggle with: Fear. We can spend a lot of time in a state of fear. It can be scary to give your heart to somebody or to go after the goals you have for yourself or to pursue new job, etc. We can really overanalyze and fixate on the what ifs or how something could go wrong. The truth is, you only get one chance at this life. This is your only shot, so take it! If you are still on this earth it is your responsibility to run full force towards what is pulling on your heart.  SUPPORT THE SHOW HERE Coaching & Mentorship: https://linktr.ee/evolvex  All my links: https://linktr.ee/emilyhayden Instagram | YouTube  My favorite supplements www.1stphorm.com/EmilyHaydenFitness Bay Breeze music courtesy of the artist, FortyThr33  

Real Housewives of Beverly Hills celebrates Dorit's new wedding dress line and Erika spins another tall tale. Please don't flip your car while listening to this episode. Find all of our premium bonus episodes at https://patreon.com/watchwhatcrappens

Why can it be such a struggle to say 'no'? Anney and Samantha discuss all the complications with saying 'no', and how powerful it can be. Learn more about your ad-choices at https://www.iheartpodcastnetwork.com

Express How You Are Authentically Feeling Do you find it challenging to reply to an invitation or request in the moment? Do you often say "yes" when you really mean "no"? Join Dr. Aziz in this enlightening episode as he guides you through the process of learning how to confidently and clearly commit to what you want.

Governors of 27 states (thus far) have announced that they would oppose President Biden's announced dictate that any company with 100 or more employees must force vaccines or weekly testing. Biden has announced that he would "roll over" governors who get in the way...but are the storm clouds of rebellion gathering? Also today: Fauci stumped on CNN over "natural immunity." And - UK shocker: Vax passport dropped amid widespread rebellion in parliament.

An old wine cellar becomes a fighting pit against a host of inhuman nightmare creatures. Check out more from the crew by visiting us at www.glasscannonnetwork.com. For exclusive content and more, subscribe to our Patreon at www.patreon.com/glasscannon. And watch us live every week at www.twitch.tv/theglasscannon.