Podcasts about callouts

Send us a textWelcome to another Listener Q&A with The Team at HR Stories! Today's episode goes into these questions:1. Can you require a doctors note for someone who continually calls in the day after a holiday weekend? Our PTO policy doesn't require it but it happens every time. 2. Is it an HR issue if someone brings particularly fragrant food into the break room?3. Can we lower someone's pay if they move to a cheaper remote work location?4. Can I take leave to take care of my sister who I am legally responsible for?5. If a person is off work for the day and they answer emails or do work without being asked to, do we have to pay them? Visit TeamAtHRStories.com to see all of our workshops and offerings to help you feel confident in your HR decisions. Support the showOur new book...The Ultimate Guide to HR: Checklists Edition is now AVAILABLE! Go to UltimateGuidetoHR.com to Get HR Right: and Avoid Costly Mistakes. Certified and approved for 3 SHRM Recertification Credits.Join the HR Team of One Community on Facebook or visit TeamAtHRstories.com and sign up for emails so you can be the first to know about new things we have coming up.You can also follow us on Instagram and TikTok at @HRstoriesPodcast Don't forget to rate our podcast, it really helps other people find it!Do you have a situation or topic you'd like the team to discuss? Are you interested in having Chuck or John talk to your team or Emcee your event? You can reach the Team at Email@TeamAtHRStories.com for suggestions and inquiries.The viewpoints expressed by the characters in the stories are not necessarily that of The Team at HR Stories. The stories are shared to present various, real-world scenarios and share how they were handled by policy and, at times, law. Chuck and John are not lawyers and always recommend working with an employment lawyer to address concerns.

In this episode, Damian takes us on a nostalgic, neon-lit journey through the "Dark Ages of Cocktails"—a period spanning from the 1970s to the early 2000s when bright colors, sweet mixers, and questionable balance ruled the bar.You'll hear:

The Police will continue with their plan to pull back from mental health callouts, but they're going about it more slowly. From Monday, 4 of the 12 police districts will move into the second phase, which involves 60-minute ED handovers. They will now be staggered across districts, instead of all at once. The Mental Health Foundation has been critical of the pull back. Police Association President Chris Cahill told Mike Hosking police need to draw a strong line in the sand to ensure people are taken care of by the right people. He says that shouldn't involve police sitting in emergency departments for six hours. LISTEN ABOVE See omnystudio.com/listener for privacy information.

The Government is assuring police will still respond to mental health callouts when needed. The Mental Health Foundation has launched a petition asking police to stop scaling back on attending mental health callouts. A four-phase reduction plan was announced in November. Mental Health Minister Matt Doocey says the programme addresses the handover - not the response. "People with mental health issues - they don't want to sit in emergency departments with police officers sitting there with tasers. They want a mental health response, and that's what we're working on." LISTEN ABOVESee omnystudio.com/listener for privacy information.

This episode is sponsored by BetterHelp — go to http://betterhelp.com/optic to get 10% off your first month. Go to http://drinktrade.com/OPTIC to get 40% off your first order. Go to http://rocketmoney.com/optic to cancel your unwanted subscriptions with Rocket Money. OpTic Gaming Merch: https://shop.opticgaming.com/ Check out the OpTic SCUF collection and use code “OpTic” for a discount: https://scuf.co/OpTic Check out the OpTic Podcast here: https://podcasts.apple.com/us/podcast/optic-podcast/id1542810047 https://open.spotify.com/show/25iPKftrl0akOZKqS0wHQG 00:00 Welcome Skyz 08:00 Kenny Stepping down 15:00 Skyz YouTube Description 18:30 Bracket Breakdown 22:45 OpTic Blacklisting 26:00 OpTic Major 30:30 Ads 35:15 Skyz Thoughts on Major 2 37:20 Where to go in Dallas 45:00 Callouts in BO6 49:00 France Wants the Eiffel Tower back

Very few beauty entrepreneurs have had more success than Carolyn Aronson. In 2006, the longtime hairstylist and salon owner launched professional hair-care brand It's a 10 with one hero product: Miracle Leave-In spray. The $21 formula was an immediate success for its ability to hydrate, smooth, condition, defrizz and protect hair with one formula. The brand had immediate success by seeding the product to professional hairstylists before entering Ulta Beauty, Target, Sally's Beauty, Cosmoprof, SalonCentric and Amazon, and selling DTC.  Using Miracle Leave-In as the anchor for expansion, the company added formulations through the years for various hair types and preferences. This includes new Miracle Leave-Ins for coily, blonde and men's hair; keratin- or color-treated hair; and lite, fragrance-free and dye-free variations. Each new collection includes shampoo, conditioner, masks and a variety of other offerings. The brand also sells body care.   In 2017, Aronson bought out her co-founder to become the sole owner of It's a 10. She's taken on no investors. The brand currently brings in around $500 million in gross annual sales and is distributed in more than 125 countries.  On a personal level, Aronson has also provided inspiration for women in the beauty industry. She entered the foster care system at age 2, began working in salons as a teenager and is currently one of the beauty industry's few self-made billionaires. She's also known for her philanthropy. For example, It's a 10 donated $250,000 worth of products to the Los Angeles Dream Center in January to help victims of the Los Angeles wildfires.  This year, Aronson is expanding her empire with Cloud Haircare, a new, Gen Z-focused line of shampoo, conditioner and styling products sold in two collections: nourishing and volumizing. Each SKU sells for $11.99 in CVS, Walmart and DTC.  The line features colorful, flat lay-friendly packaging and Gen Z-focused values: vegan, Leaping Bunny-approved formulas free of parabens and SLS, and sold in bottles made from post-consumer plastic resins.  Aronson's expansion into mass comes at a time when the sector has experienced a renaissance, of sorts. New, fresh brands are currently flooding the market, many of which are priced at $11.99 — like Odele, Saltair, Being Frenshe, Laura Polko and Function of Beauty —  while bargain formulas like Suave are back with new branding.  Beyond Cloud Haircare, Aronson entered the home hair-color space in 2023 with Rewind it 10, a line of men's home hair and beard dyes. She partnered with friend and rapper Fat Joe on the collection, as well as her husband Jeff Aronson. It sells for $15 per box DTC and through Sally's Beauty, CVS, Walmart, Amazon and more retailers.  To entice shoppers, each shade of hair dye is modeled by an influential figure like model Tyson Beckford, football star Trace Kelsie, DJ Khaled and celebrity face Brody Jenner, among many others.  On this week's episode of the Glossy Beauty Podcast, Aronson provides Glossy listeners an inside view of her move into mass hair care with Cloud and insights into navigating the men's marketplace with Rewind it 10. She also gives listeners a teaser on her entry into women's hair color and her hopes for Cloud Haircare.

Welcome to episode 145 of the Bodybuilding Down Under podcast! This week, your hosts dive into another packed episode, covering a range of exciting topics, including the impact of age on competition prep, whether the Olympia should introduce a cut round, and our dream first callouts across different eras of bodybuilding - both natural and enhanced. Plus, we discuss the latest in the bodybuilding scene, updates on our own journeys, and much, MUCH more! Thank you again for tuning in! If you enjoy the podcast, please subscribe and leave a five-star rating, it really helps us grow. Take a screenshot and share it on your IG story, and don't forget to tag us using the handles below! Stay tuned for more episodes every week!   Instagram Handles: Bodybuilding Down Under: https://www.instagram.com/bodybuildingdownunder/ Jack: https://www.instagram.com/jack.radfordsmith/ Daniel C: https://www.instagram.com/daniel.chapelle/ Lawrence: https://www.instagram.com/general.muscle/ Daniel Y: https://www.instagram.com/dy.fit/

Send us a textWhat happens when a podcast initially designed for soul care takes on a life of its own, transforming into a whirlwind of humor and unexpected conversations? Join us for an anniversary celebration like no other, as Jeremy, Jennifer, and our producer Drew Powell look back at the year and a half of delightful chaos on "The Gospel According to Jeremy." We're talking about everything from spontaneous tangents and candid reflections to a bizarre tale of a plane crash with no casualties. This episode offers more than just laughs; it captures the relatable chaos of raising a teenager, especially when Jeremy realizes how much his 17-year-old mirrors his experiences with Jennifer.The celebration doesn't stop there. We're also marking 30 years of marriage, exploring the complexities and joys of long-term relationships with quirky anecdotes like our unforgettable visit to O'Charley's in Franklin. As we share stories of marital milestones and the shifting dynamics brought by Jennifer's arrival and Drew's periodic resignations, listeners get an insight into our evolving podcast journey. Prepare yourself for a ride through three decades of life and love, packed with humor, insight, and a promise of many more spontaneous exchanges to come.

Unions say public health workers are confused about the police's phased withdrawal of support for mental health callouts. Reporter Lucy Xia has more.

All links, sponsors, networks, and notes for this episode can be accessed via the blog page below:https://yourfavoriteblockhead.com/2024/11/09/election-results-mixed-with-bold-callouts-in-mma/

A senior nurse said he's filled with dread at the prospect of police pulling back from their involvement with mental health patients. Starting today, Police are reducing the time they'll spend on mental health callouts - including limiting ED handovers to 15 minutes and they'll also spend less time on transporting patients and dealing with low risk cases. Frontline workers have warned there's an increased risk of violence with police turning more of their focus to crime fighting duties. Duly authorised officers or DAO's, are nurses with special powers to assess and detain mental health patients and RNZ understand about half a dozen of them have quit over safety concerns. Greg Davies is a DAO who is still on the job in Marlborough and spoke to Lisa Owen.

The Police have announced a new phased approach to attending lesser mental health-related callouts, that are not of high risk or are related to crime, with the next phase aimed at handing over these responsibilities to health staff. The first phase is beginning this month, with the fourth and final phase set to begin from July to September 2025. Police Commissioner, Andrew Coster, in a statement, sez Police received one mental health callout every seven minutes, taking up half a million hours of Police frontline time per year, of which of these callouts, only 11% are given a priority response. News and Editorial Director and Monday Wire Host, Joel, spoke to Associate Professor in the School of Health at the University of Waikato, Sarah Gordon, about what this phased approach will look like heading forward.

Phase One of the new Police approach to mental health callouts takes effect today. Police Association President Chris Cahill tells Mike Hosking that 11 percent of jobs that Police attend are related to mental health. Police will still attend to people who are at risk of harming themselves or others. Overseas, the removal of police from mental health callouts has lead to better outcomes for patients. LISTEN ABOVESee omnystudio.com/listener for privacy information.

The Police have announced a new phased approach to attending lesser mental health-related callouts, that are not of high risk or are related to crime, with the next phase aimed at handing over these responsibilities to health staff. The first phase is beginning this month, with the fourth and final phase set to begin from July to September 2025. Police Commissioner, Andrew Coster, in a statement, sez Police received one mental health callout every seven minutes, taking up half a million hours of Police frontline time per year, of which of these callouts, only 11% are given a priority response. News and Editorial Director and Monday Wire Host, Joel, spoke to Associate Professor in the School of Health at the University of Waikato, Sarah Gordon, about what this phased approach will look like heading forward.

From today, Police are dialling back the number of mental health callouts they will attend. Phase One of the reduced service will see Police complete faster handovers in the Emergency Department. Transport requests and attendance at mental health facilities will need to meet a higher threshold. Four phases are set to be implemented by September next year. Associate Professor in Mental Health Nursing at University of Waikato Anthony O'Brien tells Ryan Bridge police will now negotiate with health services whether they feel their presence is required on callouts where they are requested. LISTEN ABOVESee omnystudio.com/listener for privacy information.

Mental health nurses are worried the public, patients and health workers will be put at risk when Police stop attending some mental health callouts. From Monday, Police won't attend ‘low risk callouts' where there is no immediate risk to life and safety. Instead, Health NZ is expected to pick up the work. Leaked documents show only interim standard operating procedures have been developed by Health NZ. Mental Health Section Chair of the New Zealand Nurses Organisation Helen Garrick tells Heather du Plessis-Allan the plan is in its infancy but the industry does not have a sufficient workforce to manage the increase in workload. LISTEN ABOVESee omnystudio.com/listener for privacy information.

Send us a MessageIn this Solo Byte episode of Culture Change RX, Sue Tetzlaff discusses the importance of feedback in healthcare organizations, emphasizing its role as a superpower that enhances individual and organizational performance. She outlines the necessity of creating a feedback culture where giving and receiving feedback is normalized and seen as an act of caring. Sue shares practical tips for effective feedback, including being specific, asking for permission, and maintaining a positive ratio of compliments to call-outs. The episode encourages leaders to model feedback behaviors and highlights the benefits of fostering an environment where feedback is embraced in all directions.Feedback helps individuals feel appreciated and accountable.Leaders should model feedback behaviors for their teams.Omnidirectional feedback is essential to high performing and achieving organizations.Normalizing feedback as caring improves organizational culture.Specificity in feedback enhances its effectiveness.Asking for permission to give feedback can ease the feedback process.Ending feedback with questions fosters dialogue.Aiming for three times more compliments than call-outs is beneficial.Soliciting feedback helps individuals improve their reception of it.Learn more about creating a feedback culture in this blog, A Healthcare Organization's 3-Point Pathway to Normalizing Feedback as an Act of Caring, found at: https://www.radicalcandor.com/blog/feedback-in-healthcare/

The Mental Health Minister is confident about moving emergency responses to people in acute mental distress to health experts, rather than Police. Police say they'll be phasing rollout - of stepping back from mental-health callouts, over a year, starting in November. They'll lift the risk threshold for turning up - and start reducing how long officers stay with a patient they've transported to hospital. Matt Doocey told Heather du Plessis Allan mechanisms are being worked through for managing the transition. He says it's clear someone having a mental health crisis should get a health response, not a criminal one. LISTEN ABOVESee omnystudio.com/listener for privacy information.

On this episode of Good Guy / Bad Guy…From callout to title shot? First, Caio Borralho called out #5 ranked Middleweight Jared Cannonier when he wasn't even in the top 10. Then, he got the fight, beat him, and called out the Champ Dricus Du Plessis! Now, the leader of the Fighting Nerds could soon see himself at the top of the Middleweight Food Chain fighting for the title. DC & Chael are breaking down the importance of the callout and revealing the worst callouts of their careers! Plus, the UFC's only Coach-Analyst Din Thomas joins the show to pull back the curtain on everything…from the Do's and Don'ts during fight camps to what could make his former student the GOAT Amanda Nunes come out of retirement. You do NOT want to miss MMA's three favorite Uncles talk shop! Learn more about your ad choices. Visit megaphone.fm/adchoices

It's Know Your Rival season and we are kicking things off with a deep dive look at the Arizona Cardinals. Despite some potentially smart draft picks, the Cardinals' decision to stick with Kyler Murray and a difficult start to their 2024 schedule may doom their chances in the NFC West. But that wouldn't be anything new to the franchise. How does the Cardinals roster stack up? While they've made some major changes by jettisoning long-time veterans, could they still make a significant leap. In the second half of the show, we talk about potential ownership changes for the Seahawks and have some fun with hypothetical presidential tickets that includes a former member from the Legion of Boom era. Callouts to do better go out toward a nonsensically vindictive state politician and a current NBA player. Tune in to find out why Gardner Minshew and the Seahawks organization are "Better At Life." Support the show Get in the Flock! Visit GetInTheFlock.com Or visit our website for other ways to support the show Subscribe via: Apple Podcasts | Spotify | Google Podcasts | YouTube | TuneIn | RSS Follow us on: Facebook | Twitter Listen on our free app for Android, iOS, Kindle or Windows Phone/PC Call or text: 253-235-9041 Find Sea Hawkers clubs around the world at SeaHawkers.org Music from the show by The 12 Train, download each track at ReverbNation  

Just had a great win in the UFC or another MMA organization? The crowd's eating out of your hand? Well why not take the opportunity to setup your next big payday? In these cases though, pretty everyone though these callouts went waaaay outside the bounds of reality. It's unfortunate when the reaction is laughter instead of hype.

Callouts and RemindersSpeed tube high amp draw behavior, note the update on 2024.0.2RowFlow trouble shooting trees.Reminder on Sensing Y requirement for .1 software.Callout for replant instructions online.Special guest, Marcus Lee, joins Nate and Hans as he talks about some of the highlights of Smart Scout, now available, and some awesome learning tools within the application as well as the route for support within the app. SmartsScout available below:Precision News: smartscout (precisionplanting.com)

Mental Health Foundation chief executive Shaun Robinson speaks to Lisa Owen about his concerns around police pulling back from 80,000 mental health callouts a year

On this episode of Guff Guff Pass we first and foremost go through the entire fight card of NWC 4 which to say is stacked would be an understatement. Headlining the event is none other than our National pride - Rabindra Dhant, who will be facing the Australian striker Corey Sutclif. This all comes in the aftermath of the legendary UFC 300 that saw some jawdropping moments and adrenaline rushes like never before. Also, chime in to some interesting callouts during the ep as Rishabh sets his eyes on yet another potential fight that seems to be an even more well matched and dare we say, a higher possibility. Cheers! --- Send in a voice message: https://podcasters.spotify.com/pod/show/guffguffpass/message

The police pay dispute is now in the hands of a third party, who will decide whether or not they should be earning more. 

Rick returned from his extended weekend roadtrip to Cleveland, and had stories galore. Plus it's the official first day of Spring, which many treat as a time to clean out the crap. Others are hoarders for life and need to be called out! See omnystudio.com/listener for privacy information.

Building your own marketing business can be hard and lonely — but it doesn't have to be. When you become a StoryBrand Certified Guide, you'll join a like-minded community of marketers from all over the world. Apply before March 8 for our upcoming training at StoryBrand.com/ApplyNow.   --   Have you ever wondered what it takes to go viral? The answer might be less about luck and more about strategic, creative thinking. For many brands, coming up with new and exciting marketing ideas is a struggle. They often find themselves doing the same old things, which doesn't help them stand out or keep people interested. When everyone is fighting for attention, finding a unique way to connect with audiences is more important than ever. So how do you find the inspiration to try out fresh and inventive marketing ideas?   In today's episode, hosts Dr. J.J. Peterson and April Sunshine Hawkins explore the innovative marketing behind the band Jungle's latest album, Volcano. They're joined by guest Charlie Di Placido, the director and collaborator behind the viral music videos that propelled Jungle into the spotlight. Discover how Jungle used the power of viral moments, leveraged strategic collaborations (including a new international campaign with Gap), and made an entire movie for their album to get people interested. These unique strategies offer valuable lessons for marketers looking to elevate their game. Tune in and learn how creativity, collaboration, and the courage to dream big can change the way you do marketing!   Callouts from this episode:   Volcano - A Motion Picture by Jungle: https://www.youtube.com/watch?v=SU5tSF6k-m8   Jungle - Back on 74 (Live at the 2024 BRIT Awards): https://youtu.be/mPSt74adFnQ?si=sLEeAxi-91ggJ907   GAP x Jungle - Linen Moves Campaign (feat. Tyla): https://youtu.be/8unVMB-LoT8?si=tf8sWiTrarqPWaeE   Follow Jungle on Instagram: https://www.instagram.com/jungle4eva/   --   CLARIFY YOUR MARKETING AND CREATE YOUR FREE BRANDSCRIPT: Storybrand.com/sb7   TURN YOUR WEBSITE INTO A SALES MACHINE WITH THE ULTIMATE WEBSITE TEMPLATE: BusinessMadeSimple.com/Website   HIRE A STORYBRAND CERTIFIED GUIDE TO HELP CREATE THE MARKETING AND MESSAGING YOUR BUSINESS NEEDS TO GROW: MarketingMadeSimple.com   HELP US DELIVER EVEN MORE VALUE EACH WEEK BY COMPLETING OUR HERO MAKER SURVEY: StoryBrand.com/Survey   STORYBRAND INSTAGRAM: instagram.com/StoryBrand

Stephanie shares about her vacation at Disney World, particularly emphasizing the technological advancements in the park's mobile app that made her visit remarkably frictionless. Joël had a conversation about a topic he loves: units of measure, and he got to go deep into the idea of dimensional analysis with someone this week. Together, Joël and Stephanie talk about module documentation within software development. Joël shares his recent experience writing module docs for a Ruby project using the YARD documentation system. He highlights the time-consuming nature of crafting good documentation for each public method in a class, emphasizing that while it's a demanding task, it significantly benefits those who will use the code in the future. They explore the attributes of good documentation, including providing code examples, explaining expected usage, suggesting alternatives, discussing edge cases, linking to external resources, and detailing inputs, outputs, and potential side effects. Multidimensional numbers episode (https://bikeshed.thoughtbot.com/416) YARD docs (https://yardoc.org/) New factory_bot documentation (https://thoughtbot.com/blog/new-docs-for-factory_bot) Dash (https://kapeli.com/dash) Solargraph (https://solargraph.org/) Transcript:  JOËL: Hello and welcome to another episode of The Bike Shed, a weekly podcast from your friends at thoughtbot about developing great software. I'm Joël Quenneville. STEPHANIE: And I'm Stephanie Minn, and together, we're here to share a bit of what we've learned along the way. JOËL: So, Stephanie, what's new in your world? STEPHANIE: So, I recently was on vacation, and I'm excited [chuckles] to tell our listeners all about it. I went to Disney World [laughs]. And honestly, I was especially struck by the tech that they used there. As a person who works in tech, I always kind of have a little bit of a different experience knowing a bit more about software, I suppose, than just your regular person [laughs], citizen. And so, at Disney World, I was really impressed by how seamlessly the like, quote, unquote, "real life experience" integrated with their use of their branded app to pair with, like, your time at the theme park. JOËL: This is, like, an app that runs on your mobile device? STEPHANIE: Yeah, it's a mobile app. I haven't been to Disney in a really long time. I think the last time I went was just as a kid, like, this was, you know, pre-mobile phones. So, I recall when you get into the line at a ride, you can skip the line by getting what's called a fast pass. And so, you kind of take a ticket, and it tells you a designated time to come back so that you could get into the fast line, and you don't have to wait as long. And now all this stuff is on your mobile app, and I basically did not wait in [laughs] a single line for more than, like, five minutes to go on any of the rides I wanted. It just made a lot of sense that all these things that previously had more, like, physical touchstones, were made a bit more convenient. And I hesitate to use the word frictionless, but I would say that accurately describes the experience. JOËL: That's kind of amazing; the idea that you can use tech to make a place that's incredibly busy also feel seamless and where you don't have to wait in line. STEPHANIE: Yeah and, actually, I think the coolest part was it blended both your, like, physical experience really well with your digital one. I think that's kind of a gripe I have as a technologist [laughs] when I'm just kind of too immersed in my screen as opposed to the world around me. But I was really impressed by the way that they managed to make it, like, a really good supplement to your experience being there. JOËL: So, you're not hyped for a future world where you can visit Disney in VR? STEPHANIE: I mean, I just don't think it's the same. I rode a ride [laughs] where it was kind of like a mini roller coaster. It was called Expedition Everest. And there's a moment, this is, like, mostly indoors, but there's a moment where the roller coaster is going down outside, and you're getting that freefall, like, drop feeling in your stomach. And it also happened to be, like, drizzling that day that we were out there, and I could feel it, you know, like, pelting my head [laughs]. And until VR can replicate that experience [chuckles], I still think that going to Disney is pretty fun. JOËL: Amazing. STEPHANIE: So, Joël, what's new in your world? JOËL: I'm really excited because I had a conversation about a topic that I like to talk about: units of measure. And I got to go deep into the idea of dimensional analysis with someone this week. This is a technique where you can look at a calculation or a function and sort of spot-check whether it's correct by looking at whether the unit for the measure that would come out match what you would expect. So, you do math on the units and ignore the numbers coming into your formula. And, you know, let's say you're calculating the speed of something, and you get a distance and the amount of time it took you to take to go that distance. And let's say your method implements this as distance times time. Forget about doing the actual math with the numbers here; just look at the units and say, okay, we've got our meters, and we've got our seconds, and we're multiplying them together. The unit that comes out of this method is meters times seconds. You happen to know that speeds are not measured in meters times seconds. They're measured in meters divided by seconds or meters per second. So, immediately, you get a sense of, like, wait a minute, something's wrong here. I must have a bug in my function. STEPHANIE: Interesting. I'm curious how you're representing that data to, like, know if there's a bug or not. In my head, when you were talking about that, I'm like, oh yeah, I definitely recall doing, like, math problems for homework [laughs] where I had, you know, my meters per second. You have your little fractions written out, and then when you multiply or divide, you know how to, like, deal with the units on your piece of paper where you're showing your work. But I'm having a hard time imagining what that looks like as a programmer dealing with that problem. JOËL: You could do it just all in your head based off of maybe some comments that you might have or the name of the variable or something. So, you're like, okay, well, I have a distance in meters and a time in seconds, and I'm multiplying the two. Therefore, what should be coming out is a value that is in meters times seconds. If you want to get fancier, you can do things with value objects of different types. So, you say, okay, I have a distance, and I have a time. And so, now I have sort of a multiplication of a distance and a time, and sort of what is that coming out as? That can sometimes help you prevent from having some of these mistakes because you might have some kind of error that gets raised at runtime where it's like, hey, you're trying to multiply two units that shouldn't be multiplied, or whatever it is. You can also, in some languages, do this sort of thing automatically at the type level. So, instead of looking at it yourself and sort of inferring it all on your own based off of the written code, languages like F# have built-in unit-of-measure systems where once you sort of tag numbers as just being of a particular unit of measure, any time you do math with those numbers, it will then tag the result with whatever compound unit comes from that operation. So, you have meters, and you have seconds. You divide one by the other, and now the result gets tagged as meters per second. And then, if you have another calculation that takes the output of the first one and it comes in, you can tell the compiler via type signature, hey, the input for this method needs to be in meters per second. And if the other calculation sort of automatically builds something that's of a different unit, you'll get a compilation error. So, it's really cool what it can do. STEPHANIE: Yeah, that is really neat. I like all of those built-in guardrails, I suppose, to help you, you know, make sure that your answer is correct. Definitely could have used that [chuckles]. Turns out I just needed a calculator to take my math test with [laughs]. JOËL: I think what I find valuable more than sort of the very rigorous approach is the mindset. So, anytime you're dealing with numbers, thinking in your mind, what is the unit of this number? When I do math with it with a different number, is it the same unit? Is it a different unit? What is the unit of the thing that's coming out? Does this operation make sense in the domain of my application? Because it's easy to sometimes think you're doing a math operation that makes sense, and then when you look at the unit, you're like, wait a minute, this does not make sense. And I would go so far as to say that, you know, you might think, oh, I'm not doing a physics app. I don't care about units of measure. Most numbers in your app that are actually numbers are going to have some kind of unit of measure associated to them. Occasionally, you might have something where it's just, like, a straight-up, like, quantity or something like that. It's a dimensionless number. But most things will have some sort of unit. Maybe it's a number of dollars. Maybe it is an amount of time, a duration. It could be a distance. It could be all sorts of things. Typically, there is some sort of unit that should attach to it. STEPHANIE: Yeah. That makes sense that you would want to be careful about making sure that your mathematical operations that you're doing when you're doing objects make sense. And we did talk about this in the last episode about multidimensional numbers a little bit. And I suppose I appreciate you saying that because I think I have mostly benefited from other people having thought in that mindset before and encoding, like I mentioned, those guardrails. So, I can recall an app where I was working with, you know, some kind of currency or money object, and that error was raised when I would try to divide by zero because rather than kind of having to find out later with some, not a number or infinite [laughs] amount of money bug, it just didn't let me do that. And that wasn't something that I had really thought about, you know, I just hadn't considered that zero value edge case when I was working on whatever feature I was building. JOËL: Yeah, or even just generally the idea of dividing money. What does that even mean? Are you taking an amount of money and splitting it into two equivalent piles to split among multiple people? That kind of makes sense. Are you dividing money by another money value? That's now asking a very different kind of question. You're asking, like, what is the ratio between these two, I guess, piles of money if we want to make it, you know, in the physical world? Is that a thing that makes sense in your application? But also, realize that that ratio that you get back is not itself an amount of money. And so, there are some subtle bugs that can happen around that when you don't keep track of what your quantities are. So, this past week, I've been working on a project where I ended up having to write module docs for the code in question. This is a Ruby project, so I'm writing docs using the YARD documentation system, where you effectively just write code comments at the sort of high level covering the entire class and then, also, individual documentation comments on each of the methods. And that's been really interesting because I have done this in other languages, but I'd never done it in Ruby before. And this is a piece of code that was kind of gnarly and had been tricky for me to figure out. And I figured that a couple of these classes could really benefit from some more in-depth documentation. And I'm curious, in your experience, Stephanie, as someone who's writing code, using code from other people, and who I assume occasionally reads documentation, what are the things that you like to see in good sort of method-level docs? STEPHANIE: Personally, I'm really only reading method-level docs when, you know, at this point, I'm, like, reaching for a method. I want to figure out how to use it in my use case right now [laughs]. So, I'm going to search API documentation for it. And I really am just scanning for inputs, especially, I think, and maybe looking at, you know, some potential various, like, options or, like, variations of how to use the method. But I'm kind of just searching for that at a glance and then moving on [laughs] with my day. That is kind of my main interaction with module docs like that, and especially ones for Ruby and Rails methods. JOËL: And for clarity's sake, I think when we're talking about module docs here, I'm generally thinking of, like, any sort of documentation that sort of comments in code meant to document. It could be the whole modular class. It could be on a per-method level, things like RDoc or YARD docs on Ruby classes. You used the word API docs here. I think that's a pretty similar idea. STEPHANIE: I really haven't given the idea of writing this kind of documentation a lot of thought because I've never had to do too much of it before, but I know, recently, you have been diving deep into it because, you know, like you said, you found these classes that you were working with a bit ambiguous, I suppose, or just confusing. And I'm wondering what kind of came out of that journey. What are some of the most interesting aspects of doing this exercise? JOËL: And one of the big ones, and it's not a fun one, but it is time-consuming. Writing good docs per method for a couple of classes takes a lot of time, and I understand why people don't do it all the time. STEPHANIE: What kinds of things were you finding warranted that time? Like, you know, you had to, at some point, decide, like, whether or not you're going to document any particular method. And what were some of the things you were looking out for as good reasons to do it? JOËL: I was making the decisions to document or not document on a class level, and then every public method gets documentation. If there's a big public API, that means every single one of those methods is getting some documentation comments, explaining what they do, how they're meant to be used, things like that. I think my kind of conclusion, having worked with this, is that the sort of sweet spot for this sort of documentation is for anything that is library-like, so a lot of things that maybe would go into a Rails lib directory might make sense. Anything you're turning into a gem that probably makes sense. And sometimes you have things in your Rails codebase that are effectively kind of library-like, and that was the case for the code that I was dealing with. It was almost like a mini ORM style kind of ActiveRecord-inspired series of base classes that had a bunch of metaprogramming to allow you to write models that were backed by not a database but a headless CMS, a content management system. And so, these classes are not extracted to the lib directory or, like, made into a gem, but they feel very library-esque in that way. STEPHANIE: Library-like; I like that descriptor a lot because it immediately made me think of another example of a time when I've used or at least, like, consumed this type of documentation in a, like, SaaS repo. Rather, you know, I'm not really seeing that level of documentation around domain objects, but I noticed that they really did a lot of extending of the application record class because they just had some performance needs that they needed to write some, like, custom code to handle. And so, they ended up kind of writing a lot of their own ORM-like methods for just some, like, custom callbacks on persisting and some just, like, bulk insertion functionality. And those came with a lot of different ways to use them. And I really appreciated that they were heavily documented, kind of like you would expect those ActiveRecord methods to be as well. JOËL: So, I've been having some conversations with other members at thoughtbot about when they like to use the style of module doc. What are some of the alternatives? And one that kept coming up for different people that they would contrast with this is what they would call the big README approach, and this could be for a whole gem, or it could be maybe some directory with a few classes in your application that's got a README in the root of the directory. And instead of documenting each method, you just write a giant README trying to answer sort of all of the questions that you anticipate people will ask. Is that something that you've seen, and how do you feel about that as a tool when you're looking for help? STEPHANIE: Yes. I actually really like that style of documentation. I find that I just want examples to get me started, especially; I guess this is especially true for libraries that I'm not super familiar with but need to just get a working knowledge about kind of immediately. So, I like to see examples, the getting started, the just, like, here's what you need to know. And as I start to use them, that will get me rolling. But then, if I find I need more details, then I will try to seek out more specific information that might come in the form of class method documentation. But I'm actually thinking about how FactoryBot has one of the best big README-esque [laughs] style of documentation, and I think they did a really big refresh of the docs not too long ago. It has all that high-level stuff, and then it has more specific information on how to use, you know, the most common methods to construct your factories. But those are very detailed, and yet they do sit, like, separately from inline, like, code documentation in the style of module docs that we're talking about. So, it is kind of an interesting mix of both that I think is helpful for me personally when I want both the “what do I need to know now?” And the, “like, okay, I know where to look for if I need something a little more detailed.” JOËL: Yeah. The two don't need to be mutually exclusive. I thought it was interesting that you mentioned how much examples are valuable to you because...I don't know if this is controversial, but an opinion that I have about sort of per-method documentation is that you should always default to having a code example for every method. I don't care how simple it is or how obvious it is what it does. Show me a code example because, as a developer, examples are really, really helpful. And so, seeing that makes documentation a lot more valuable than just a couple of lines that explain something that was maybe already obvious from the title of the method. I want to see it in action. STEPHANIE: Interesting. Do you want to see it where the method definition is? JOËL: Yes. Because sometimes the method definition, like, the implementation, might be sort of complex. And so, just seeing a couple of examples, like, oh, you call with this input, you get that. Call with this other input; you get this other thing. And we see this in, you know, some of the core docs for things like the enumerable methods where having an example there to be like, oh, so that's how map works. It returns this thing under these circumstances. That sort of thing is really helpful. And then, I'll try to do it at a sort of a bigger level for that class itself. You have a whole paragraph about here's the purpose of the class. Here's how you should use it. And then, here's an example of how you might use it. Particularly, if this is some sort of, like, base class you're meant to inherit from, here's the circumstances you would want to subclass this, and then here's the methods you would likely want to override. And maybe here are the DSLs you might want to have and to kind of package that in, like, a little example of, in this case, if you wanted a model that read from the headless CMS, here's what an example of such a little model might look like. So, it's kind of that putting it all together, which I think is nice in the module docs. It could probably also live in the big README at some level. STEPHANIE: Yeah. As you are saying that, I also thought about how I usually go search for tests to find examples of usage, but I tend to get really overwhelmed when I see inline, like, that much inline documentation. I have to, like, either actively ignore it, choose to ignore it, or be like, okay, I'm reading this now [laughs]. Because it just takes up so much visual space, honestly. And I know you put a lot of work into it, a lot of time, but maybe it's because of the color of my editor theme where comments are just that, like, light gray [laughs]. I find them quite easy to just ignore. But I'm sure there will be some time where I'm like, okay, like, if I need them, I know they're there. JOËL: Yeah, that is, I think, a downside, right? It makes it harder to browse the code sometimes because maybe your entire screen is almost taken up by documentation, and then, you know, you have one method up, and you've got to, like, scroll through another page of documentation before you hit the next method, and that makes it harder to browse. And maybe that's something that plays into the idea of that separation between library-esque code versus application code. When you browse library-esque code, when you're actually browsing the source, you're probably doing it for different reasons than you would for code in your application because, at that point, you're effectively source diving, sometimes being like, oh, I know this class probably has a method that will do the thing I want. Where is it? Or you're like, there's an edge case I don't understand on this method. I wonder what it does. Let me look at the implementation. Or even some existing code in the app is using this library method. I don't know what it does, but they call this method, and I can't figure out why they're using it. Let me look at the source of the library and see what it does under the hood. STEPHANIE: Yeah. I like the distinction of it is kind of a different mindset that you're reading the code at, where, like, sometimes my brain is already ready to just read code and try to figure out inputs and outputs that way. And other times, I'm like, oh, like, I actually can't parse this right now [chuckles]. Like, I want to read just English, like, telling me what to expect or, like, what to look out for, especially when, like you said, I'm not really, like, trying to figure out some strange bug that would lead me to diving deep in the source code. It's I'm at the level where I'm just reaching for a method and wanting to use it. We're writing these YARD docs. I think I also heard you mention that you gave some, like, tips or maybe some gotchas about how to use certain methods. I'm curious why that couldn't have been captured in a more, like, self-documenting way. Or was there a way that you could have written the code for that not to have been needed as a comment or documented as that? And was there a way that method names could have been clear to signal, like, the intention that you were trying to convey through your documentation? JOËL: I'm a big fan of using method names as a form of documentation, but they're frequently not good enough. And I think comments, whether they're just regular inline comments or more official documentation, can be really good to help avoid sort of common pitfalls. And one that I was working with was, there were two methods, and one would find by a UID, so it would search up a document by UID. And another one would search by ID. And when I was attempting to use these before I even started documenting, I used the wrong one, and it took me a while to realize, oh wait, these things have both UIDs and IDs, and they're slightly different, and sometimes you want to use one or the other. The method names, you know, said like, "Find by ID" or "Find by UID." I didn't realize there were both at the time because I wasn't browsing the source. I was just seeing a place where someone had used it. And then, when I did find it in the source, I'm like, well, what is the difference? And so, something that I did when I wrote the docs was sort of call out on both of those methods; by the way, there is also find by UID. If you're searching by UID, consider using the other one. If you don't know what the difference is, here's a sentence summarizing the difference. And then, here's a link to external documentation if you want to dive into the nitty gritty of why there are two and what the differences are. And I think that's something you can't capture in just a method name. STEPHANIE: Yeah, that's true. I like that a lot. Another use case you can think of is when method names are aliased, and it's like, I don't know how I would have possibly known that until I, you know, go through the journey of realizing [laughs] that these two methods do the same thing or, like, stumbling upon where the aliasing happens. But if that were captured in, like, a little note when I'm in, like, a documentation viewer or something, it's just kind of, like, a little tidbit of knowledge [laughs] that I get to gain along the way that ends up, you know, being useful later because I will have just kind of...I will likely remember having seen something like that. And I can at least start my search with a little bit more context than when you don't know what you don't know. JOËL: I put a lot of those sorts of notes on different methods. A lot of them are probably based on a personal story where I made a mistaken assumption about this method, and then it burned me. But I'm like, okay, nobody else is going to make that mistake. By the way, if you think this is what the method does, it does something slightly different and, you know, here's why you need to know that. STEPHANIE: Yeah, you're just looking out for other devs. JOËL: And, you know, trying to, like, take my maybe negative experience and saying like, "How can I get value out of that?" Maybe it doesn't feel great that I lost an hour to something weird about a method. But now that I have spent that hour, can I get value out of it? Is the sort of perspective I try to have on that. So, you mentioned kind of offhand earlier the idea of a documentation viewer, which would be separate than just reading these, I guess, code comments directly in your code editor. What sort of documentation viewers do you like to use? STEPHANIE: I mostly search in my browser, you know, just the official documentation websites for Rails, at least. And then I know that there are also various options for Ruby as well. And I think I had mentioned it before but using DuckDuckGo as my search engine. I have nice bang commands that will just take me straight to the search for those websites, which is really nice. Though, I have paired with people before who used various, like, macOS applications to do something similar. I think Alfred might have some built-in workflows for that. And then, a former co-worker used to use one called Dash, that I have seen before, too. So, it's another one of those just handy just, like, search productivity extensions. JOËL: You mentioned the Rails documentation, and this is separate from the guides. But the actual Rails docs are generated from comments like this inline in code. So, all the different ActiveRecord methods, when you search on the Rails documentation you're like, oh yeah, how does find_by work? And they've got a whole, like, paragraph explaining how it works with a couple of examples. That's this kind of documentation. If you open up that particular file in the source code, you'll find the comments. And it makes sense for Rails because Rails is more of, you know, library-esque code. And you and I search these docs pretty frequently, although we don't tend to do it, like, by opening the Rails gem and, like, grepping through the source to find the code comment. We do it through either a documentation site that's been compiled from that source or that documentation that's been extracted into an offline tool, like you'd mentioned, Dash. STEPHANIE: Yeah, I realized how conflicting, I suppose, it is for me to say that I find inline documentation really overwhelming or visually distracting, whereas I recognize that the only reason I can have that nice, you know, viewing experience is because documentation viewers use the code comments in that format to be generated. JOËL: I wonder if there's like a sort of...I don't know what this pattern is called, but a bit of a, like, middle-quality trap where if you're going to source dive, like, you'd rather just look at the code and not have too much clutter from sort of mediocre comments. But if the documentation is really good and you have the tooling to read it, then you don't even need to source dive at all. You can just read the documentation, and that's sufficient. So, both extremes are good, but that sort of middle kind of one foot in each camp is sort of the worst of both worlds experience. Because I assume when you look for Rails documentation, you never open up the actual codebase to search. The documentation is good enough that you don't even need to look at the files with the comments and the code. STEPHANIE: Yeah, and I'm just recalling now there's, like, a UI feature to view the source from the documentation viewer page. JOËL: Yes. STEPHANIE: I use that actually quite a bit if the comments are a little bit sparse and I need just the code to supplement my understanding, and that is really nice. But you're right, like, I very rarely would be source diving, unless it's a last resort [laughs], let's be honest. JOËL: So, we've talked about documentation viewers and how that can make things nice, and you're able to read documentation for things. But a lot of other tooling can benefit from this sort of model documentation as well, and I'm thinking, in particular, Solargraph, which is Ruby's language server protocol. And it has plugins for VS Code, for Vim, for a few different editors, takes advantage of that to provide all sorts of things. So, you can get smart expansion of code and good suggestions. You can get documentation for what's under your cursor. Maybe you're reading somebody else's code that they've written, and you're like, why are they calling this parameterized method here? What does that even do? Like, in VS Code, you could just hover over it, and it will pop up and show you documentation, including the, like, inputs and return types, and things like that. That's pretty nifty. STEPHANIE: Yeah, that is cool. I use VS Code, but I've not seen that too much yet because I don't think I've worked in enough codebases with really comprehensive [laughs] YARD docs. I'm actually wondering, tooling-wise, did you use any helpful tools when you were writing them or were you hand-documenting each? JOËL: I was hand-documenting everything. STEPHANIE: Class. Okay. JOËL: The thing that I did use is the YARD gem, which you don't need to have the gem to write YARD-style documentation. But if you have the gem, you can run a local server and then preview a documentation site that is generated from your comments that has everything in there. And that was incredibly helpful for me as I was trying to sort of see an overview of, okay, what would someone who's looking at the docs generated from this see when they're trying to look for what the documentation of a particular method does? STEPHANIE: Yeah, and that's really nice. JOËL: Something that I am curious about that I've not really had a lot of experience with is whether or not having extra documentation like that can help AI tools give us better suggestions. STEPHANIE: Yeah, I don't know the answer to that either, but I would be really curious to know if that is already something that happens with something like Copilot. JOËL: Do better docs help machines, or are they for humans only? STEPHANIE: Whoa, that's a very [laughs] philosophical question, I think. It would make sense, though, that if we already have ways to parse and compile this kind of documentation, then I can see that incorporating them into the types of, like, generative problems that AI quote, unquote "solves" [chuckles] would be really interesting to find out. But anyone listening who kind of knows the answer to that or has experience working with AI tools and various types of code comment documentation would be really curious to know what your experience is like and if it improves your development workflow. So, for people who might be interested in getting better at documenting their code in the style of module docs, what would you say are some really great attributes of good documentation in this form? JOËL: I think, first of all, you have to write from the motivation of, like, if you were confused and wanting to better understand what a method does, what would you like to see? And I think coming from that perspective, and that was, in my case, I had been that person, and then I was like, okay, now that I've figured it out, I'm going to write it so that the next person is not confused. I have five or six things that I think were really valuable to add to the docs, a few of which we've already mentioned. But rapid fire, first of all, code example. I love code examples. I want a code example on every method. An explanation of expected usage. Here's what the method does. Here's how we expect you to use this method in any extra context about sort of intended use. Callouts for suggested alternatives. If there are methods that are similar, or there's maybe a sort of common mistake that you would reach for this method, put some sort of call out to say, "Hey, you probably came here trying to do X. If that's what you were actually trying to do, you should use method Y." Beyond that, a discussion of edge cases, so any sort of weird ways the method behaves. You know, when you pass nil to it, does it behave differently? If you call it in a different context, does it behave differently? I want to know that so that I'm not totally surprised. Links to external resources–really great if I want to, like, dig deeper. Is this method built on some sort of, like, algorithm that's documented elsewhere? Please link to that algorithm. Is this method integrating with some, like, third-party API? You know, they have some documentation that we could link to to go deeper into, like, what these search options do. Link to that. External links are great. I could probably find it by Googling myself, but you are going to make me very happy as a developer if you already give me the link. You'd mentioned capturing inputs and outputs. That's a great thing to scan for. Inputs and outputs, though, are more sometimes than just the arguments and return values. Although if we're talking about arguments, any sort of options hash, please document the keys that go in that because that's often not obvious from the code. And I've spent a lot of time source diving and jumping between methods trying to figure out like, what are the options I can pass to this hash? Beyond the explicit inputs and outputs, though, anything that is global state that you rely on. So, do you need to read something from an environment variable or even a global variable or something like that that might make this method behave differently in different situations? Please document that. Any situations where you might raise an error that I might not expect or that I might want to rescue from, let me know what are the potential errors that might get raised. And then, finally, any sorts of side effects. Does this method make a network call? Are you writing to the file system? I'd like to know that, and I'd have to, like, figure it out by trial and error. And sometimes, it will be obvious in just the description of the method, right? Oh, this method pulls data from a third-party API. That's pretty clear. But maybe it does some sort of, like, caching in the background or something to a file that's not really important. But maybe I'm trying to do a unit test that involves this, and now, all of a sudden, I have to do some weird stubbing. I'd like to know that upfront. So, those are kind of all the things I would love to have in my sort of ideal documentation comment that would make my life easier as a developer when trying to use some code. STEPHANIE: Wow. What a passionate plea [laughs]. I was very into listening to you list all of that. You got very animated. And it makes a lot of sense because I feel like these are kind of just the day-to-day developer issues we run into in our work and would be so awesome if, especially as the, you know, author where you have figured all of this stuff out, the author of a, you know, a method or a class, to just kind of tell us these things so we don't have to figure it out ourselves. I guess I also have to respond to that by saying, on one hand, I totally get, like, you want to be saved [chuckles] from those common pitfalls. But I think that part of our work is just going through that and playing around and exploring with the code in front of us, and we learn all of that along the way. And, ultimately, even if that is all provided to you, there is something about, like, going through it yourself that gives you a different perspective on it. And, I don't know, maybe it's just my bias against [laughs] all the inline text, but I've also seen a lot of that type of information captured at different levels of documentation. So, maybe it is a Confluence doc or in a wiki talking about, you know, common gotchas for this particular problem that they were trying to solve. And I think what's really cool is that, you know, everyone can kind of be served and that people have different needs that different styles of documentation can meet. So, for anyone diving deep in the source code, they can see all of those examples inline. But, for me, as a big Googler [laughs], I want to see just a nice, little web app to get me the information that I need to find. I'm happy having that a little bit more, like, extracted from my source code. JOËL: Right. You don't want to have to read the source code with all the comments in it. I think that's a fair criticism and, yeah, probably a downside of this. And I'm wondering, there might be some editor tooling that allows you to just collapse all comments and hide them if you wanted to focus on just the code. STEPHANIE: Yeah, someone, please build that for me. That's my passionate plea [laughs]. And on that note, shall we wrap up? JOËL: Let's wrap up. STEPHANIE: Show notes for this episode can be found at bikeshed.fm. JOËL: This show has been produced and edited by Mandy Moore. STEPHANIE: 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. It really helps other folks find the show. JOËL: If you have any feedback for this or any of our other episodes, you can reach us @_bikeshed, or you can reach me @joelquen on Twitter. STEPHANIE: Or reach both of us at hosts@bikeshed.fm via email. JOËL: Thanks so much for listening to The Bike Shed, and we'll see you next week. ALL: Bye. AD: Did you know thoughtbot has a referral program? If you introduce us to someone looking for a design or development partner, we will compensate you if they decide to work with us. More info on our website at: tbot.io/referral. Or you can email us at referrals@thoughtbot.com with any questions.

On the debut episode of Good Guy / Bad Guy, DC & Chael look ahead to the highly anticipated rematch between “Suga” Sean O'Malley & Marlon “Chito” Vera at UFC 299 in Miami. Chael knows a thing or two about being “Undefeated”, but does he agree with O'Malley's claim of being undefeated? Then, a Fight Night recap of the weekend's biggest Winners, Losers & Callouts at the APEX! Plus, DC & Chael look back on this very day in MMA history when Jon Jones became the UFC Heavyweight Champion. And find out which hot topics the guys think are Good, Bad, or Absolutely Suck! Learn more about your ad choices. Visit megaphone.fm/adchoices

The Police Commissioner says demand for police to respond to social harm is displacing their ability to attend other jobs.The briefing to the new minister included proposing going less to family harm callouts, which have risen 80 percent in the past 10 years. Commissioner Andrew Coster says officers would like to be doing more work only police can do. He says a managed withdrawal from harm callouts is the only way to free them up. "The ideal situation here would be that others step up to deal with this demand, because arguably- help should be available in some of these situations." LISTEN ABOVESee omnystudio.com/listener for privacy information.

Victim advocates say family violence could increase or go unreported if the police go ahead with plans to pull back from family harm callouts. In a briefing to incoming Police Minister, Mark Mitchell, Police bosses are proposing a so-called "managed withdrawal" from what they consider non-crime social problems. Krystal Gibbens reports.

Luis Scott of 8 Figure Consulting joins Dawn LIVE! Luis expands on the most absent day of the year - Super Bowl Monday! How can any business put guardrails in place to emphasize attendance on days like this one.  Luis then expands on the reality of the Trump Colorado case that was center stage yesterday in the news cycle. Luis responds to the prompt below: (Independent)Businesses across the United States are bracing for an outbreak of ‘Super flu' next Monday when over 16m Americans are expected to phone in sick after watching the San Francisco 49ers and Kansas City Chiefs play for the Lombardi Trophy.A survey from UKG, a provider of human resources, payroll, and workforce management solutions, estimated that 16.1m U.S. employees plan to miss work the day after the 11 February Super Bowlin Las Vegas. The survey also found that 22.5m U.S. employees, or 14 percent of the workforce, expect they will miss at least some work on Monday while 45m say they'll be less productive than usual. “The Monday after the Super Bowl has become the number one day in absenteeism or people taking a vacation day,” Derek Stevens, owner and CEO of several Las Vegas casinos including Circa, told Reuters. Read more. How should bosses handle this? Is it important to put a policy in place now about missing work the day after the Super Bowl? Business strategist and attorney Luis Scott can weigh in on this. He's overcome adversity to build two successful businesses. And now he advises others on how to do the same thing. Within a three-month period in 2017-2018, Luis went through a divorce and his law partners kicked him out of their practice. Less than six years later, a law firm he has since cofounded has five offices with nearly 30 attorneys. And his company 8 Figure Firm Consulting helps law firms achieve 8-figure yearly revenues. 8 Figure Firm clients employ almost 5,000 people nationwide.  Tune in 10 AM - 12 PM EST weekdays on Talk Radio 1210 WPHT; or on the Audacy app!

This week on The Last Round Podcast, the team Previews Jaime Munguia vs. John Ryder on DAZN, Canelo's options for May, Jermall Charlo, David Benavidez, Munguia, 168 Division, Ryan Garcia and his call-outs with opponents, Review Jonas' victory over Mayer, Joseph Parker vs. Zhang in March on AJ-Ngannou card, Preview Lewis Crocker vs. Jose Felix in Northern Ireland on DAZN, Joe Joyce vs. Kash Ali in March, and more.  https://linktr.ee/TheLastRound 

Yeah I do Christmas day Callouts - Wanna know how much????The most popular holiday in the whole wide world, someone is going to need an electrician. You could take that call, go to that job and make good money that day.....or Do what everyone else is doing and spend the whole day with your family and friends. Its not surprise that you can earn good money doing being a call out electrician, there are a few downfalls to doing that. In this podcast is a story of how I earned more then £400 an hour for a simple call out. To be honest its something anyone could have done, even DIY dave. This is the last podcast of 2023 and I would like to thank every single one of you listening and tuning in. Without your support I would have given up a long time ago. ⭐In 2024 its only going to get bigger and better!⭐Watch this space

Stray fireworks set a house on fire in Auckland overnight. Fire and Emergency says the fire began when fireworks hit the upper deck of the property in Mount Roskill. FENZ spokesperson Adrian Nacey spoke to Susie Ferguson.  

This season, we have been loosely exploring “cancelation” what it means for the canceled person if it works, and how we can integrate the canceled person back into society. This week's episode continues with that theme and is an extension of our last episode featuring canceled sexuality coach Charlie Glickman. This episode features Mischa Byruck, a sexual integrity coach who works to support people to live their sex lives in line with their values. He specializes in supporting subjects of public callouts and cancelations and assists over three dozen men to take accountability for sexual harm and return to their lives transformed. He also leads courses and workshops on sexual integrity, kink, and consent. Mischa is also part of Charlie's accountability team. Mischa and I explore how we can put preventative systems in place to avoid a power dynamic that prevents people in a passive position from approaching the more powerful person with feedback or notes on unintentional abuses of power. This all starts with an awareness that leaders in a power position (bosses, coaches, teachers) need to acknowledge the lack of power their audience has. Tools like these can help to avoid many harmful situations that result in leaders feeling scrutinized.  We also talk about why, as a society, we wait for harm to occur to establish accountability systems. What if this became the norm? Of course, this takes understanding and acknowledging the power differentials built into our roles, socioeconomic, gender, and race. We end with an exercise that briefly explains how to somatically navigate defensiveness as it arises and staying present when being called out.  

This episode begins with a heated Target-related callout, then progresses to a consideration of the various ways our fridges, closets, and other household items could improve our lives if they were only a little bit enchanted.

As we learned in Episode 79, “How We Broke DevRel as an Industry (https://www.communitypulse.io/79-how-we-broke-devrel-as-an-industry)”, sometimes the people in charge may not know how to set you up for success. The tasks you're expected to do can take you away from your core focus. In today's episode, we'll talk through how to define your role and defend your team against that very real possibility of being tasked with items that don't belong within your purview. Checkouts Evan Hamilton * Factfulness: Ten Reasons We're Wrong about the World by Hans Rosling (https://www.amazon.com/Factfulness-Reasons-World-Things-Better/dp/1250123828/ref=sr_1_1?hvadid=580750427006&hvdev=c&hvlocphy=9010222&hvnetw=g&hvqmt=e&hvrand=5641429314803382062&hvtargid=kwd-429505407993&hydadcr=22567_13493270&keywords=factfulness+by+hans+rosling&qid=1690810799&s=books&sr=1-1) * People I Mostly Admire speaks to Chicago's innovative sheriff (https://freakonomics.com/podcast/chicagos-renegade-sheriff-wants-to-fix-law-enforcement/) * Chris Detzel (https://chrisdetzel.com/) * Community Manager Breakfast (https://www.evanhamilton.com/community-manager-breakfast/) Angie Jones * ChatGPT (https://openai.com/) * Hackathons! Wesley Faulkner * Positioning with April Dunford (http://positioning.show) * Setting up For Success in Your Next Role: Where to start? (https://www.devrelx.com/post/setting-up-for-success-in-your-next-role-where-to-start) Jason Hand * DASH conference (https://www.dashcon.io/) * Beginners Guide to Sketchnoting: Focus Better, Learn Faster and Remember Longer by Drawing Your Notes (https://a.co/d/eSaombF) by Ashton Rodenhiser Mary Thengvall * American Dirt (https://www.goodreads.com/book/show/45721673-american-dirt) by Jeanine Cummins * Puppy Training: Sexier than a Squirrel (https://absolute-dogs.com/product/squirrel/) Enjoy the podcast? Please take a few moments to leave us a review on iTunes (https://itunes.apple.com/us/podcast/community-pulse/id1218368182?mt=2) and follow us on Spotify (https://open.spotify.com/show/3I7g5WfMSgpWu38zZMjet?si=565TMb81SaWwrJYbAIeOxQ), or leave a review on one of the other many podcasting sites that we're on! Your support means a lot to us and helps us continue to produce episodes every month. Like all things Community, this too takes a village. All headings are in bold. Callouts are using full host names. Artwork photo by Paul Skorupskas (https://unsplash.com/@pawelskor?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText) on Unsplash (https://unsplash.com/@pawelskor?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText) Special Guests: Angie Jones and Evan Hamilton.

Tony Jones Show #230 - With music from: Carissa Johnson, The Safes, The Quins, Umbrella Co., Flexie, For the Love of Sloane, Nymphidels, Jonee Earthquake Band, The Sleazies, The Showcase Showdown, Time Out Timmy, The Callouts, Gamma Rage, Brunt Of It, The Proletariat, The Schemers, Matchless, Senior Discount, Roz Raskin and the Rice Cakes

Police spend an estimated 20-40% of their time on mental health calls, according to the College of Policing. Is Humberside police's ‘Right Care, Right Person' a better way? Helen Pidd reports. Help support our independent journalism at theguardian.com/infocus

Tony Jones Show #228 - With music from: Steve Volkmann, Silverteeth, Atlantic Thrills, Deer Tick, The Callouts, Hayley and the Crushers, Smitt E. Smitty & The Fezztones, Sasquatch and the Sick-a-Billys, The Jabbers, We Own Land, The Benji's, GrandEvolution, Underdog, Traveling Empire, Ravi Shavi, Russ Carrick, The McGunks

Garza sits down with Melbourne, FL deathcore band Bodysnatcher. https://www.bodysnatcherofficial.com SPONSORS: Click this link to purchase from Sweetwater & help support the podcast: imp.i114863.net/rnrmVB TIME CODES: 00:00 - Sold Out Tour w/ Great Supporting Bands (Distant, Angelmaker, Paleface) 09:30 - How Bodysnatcher Started, Dealing w/ Pandemic 19:35 - “King of the Rats” Was Written in 45 Minutes 24:15 - Long Distance Writing Process 26:40 - Working w/ Neil Westfall from A Day to Remember 28:29 - Using MIDI as a Tool to Write Great Songs 35:14 - Farting During Serious Moments & Understanding Each Other 38:33 - Cooking & Eating 40:07 - Pooping Pants/Shaving Beard Bet 43:01 - Santana's Mexican Food 46:50 - Breakdown Callouts 49:40 - Playing to a Click Track 52:04 - Hatebreed Was the Gateway Band 58:50 - Keeping the Aggression in Deathcore

Richies, the “Vanderpump Rules” reunion is finally here! In part one of three, the cast sat down to spill the tea and break down "Scandoval." To say that last night's episode delivered the drama is an understatement, because Ariana Madix and James Kennedy were fired up. They called out a weeping Tom Sandoval for his “sad sack” act, and fired off a barrage of…shall we say…“inventive” insults along the way. There are still TWO more parts of this reunion left, and Richies, we can't wait to see how rest of this shit show plays out!See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Today I speak with IFBB Pro Arielle Ann Johnson, a momma of two amazing children and the first IFBB Bikini Pro from North Dakota. Growing up doing pageants and collegiate gymnastics and cheerleader, Arielle is no stranger to the stage. She first competed in 2019 and went on to compete in her first National show where she got second callouts. After taking time off, she came back in 2021 and experienced the loss of her boyfriend, Ty. After a short break, she then returned to the National circuit and eventually won her Pro Card at 2022 Nationals.    Arielle has faced a lot of challenges but bodybuilding has provided her a space to prioritize her mental health. She is so open and honest about her journey and struggles. You don't want to miss this episode!   TOPICS COVERED -advocating for mental health -routine helping through trauma -dealing with the loss of her boyfriend  -supporting other going through loss -never settle -being present and living in the moment -being kind to yourself -communicating with your coach -family relationships -motherhood and competing   CONNECT WITH CELESTE: Website: http://www.celestial.fit Instagram: https://www.instagram.com/celestial_fit/ All Links: http://www.celestial.fit/links.html CONNECT WITH ARIELLE ANN: Instagram: https://www.instagram.com/arielleann_ifbbpro/ TikTok: @arielleanns     TIME STAMPS 1:00 introduction 2:05 love and the loss of her boyfriend 6:40 finding strength through bodybuilding 10:18 changing plans after loss 14:40 grieving and motherhood 17:06 meeting her boyfriend on TikTok 21:40 new visions for the future 25:49 making the most of your relationships 28:15 what it means to settle 33:24 getting into competing 36:28 changing her approach to motherhood 37:54 letting go of the shreds 39:40 lessons learning in going Pro 43:50 setting a timeline 46:15 inspirations 49:38 a day in the life 52:01 family support and relationships 55:01 the desire to turn Pro 57:35 advice for competitors   CLICK HERE TO SIGN UP FOR THE FREE FOOD RELATIONSHIP COACHING SERIES   CLICK HERE TO SIGN UP FOR THE FREE POST SHOW BLUES COACHING SERIES   LEARN MORE AND APPLY FOR MY 5 WEEK FOOD RELATIONSHIP HEALING & DISCOVERY COACHING PROGRAM   FOR OTHER FREE RESOURCES, LIVE EVENTS, AND WAYS TO WORK WITH CELESTE CLICK HERE

The boys are here with a very special episode with our 1st ever Pro Athlete interview. Dre Miley joins us to tell his story of how he became a fighter and all the adversity he had to deal with from High School to now with Life & Fighting with one eye. We get to hear him discuss some behind the scenes of the fight life from regional scenes to now being signed to Bellator. Before he leaves he calls out a few names that he hopes to fight soon. As always Pour up, Spark up & Enjoy the show.   Pro Fighter: Dre Miley Twitter: 1EyedDragonDre

Tony Jones Show #224 - With music from: Dan Vapid & the Cheats, Nova One, The Silks, Mark Cutler, The Callouts, Speedfossil, We Own Land, The Skinny Millionaires, The Safes, Justine and the Unclean, For the Love of Sloane, November Party, Gein and the Grave Robbers, The Neighborhoods

Do what you can to get the fight you want I suppose.

Tony Jones Show #221 - With music from: Umbrella Co., Russ Carrick, The Benji's, Traveling Empire, Black 47 / Jonee Earthquake, The Callouts, 61 Ghosts, Look Back Luna, Shore City, Today is Tomorrow, We Own Land, Two Cow Garage, The Schemers, Roz and The Rice Cakes, Nymphidels, The Copacetics.

In this special episode, Paul Revelia is joined by his client Brittany Hamilton. Brittany competed at the Olympia for the first time this past year, under Paul's guidance and has big plans this upcoming year when it comes to her competing career. In this special episode, they talk about her road to the Olympia and the highs and lows leading up to the special day.

Chris Ehmke and Paul Wilson are joined by RJ Snider on this week's episode! RJ is a long-time listener and diesel enthusiast like us doing big things in his community with diesel. He discusses the dirt drag event The Cornfield Callouts and some 12 valve talk.  Are you in or near Ohio? Be sure to get out to this awesome event. Details of the event: The Cornfield Callouts November 5th 13603 Sand Rock Road Glenford, Ohio