With the hotly anticipated playoff series between the Flames and Oilers beginning, Tim welcomes former Oilers player and head coach Craig MacTavish (1:14:08) and Sportsnet's Kelly Hrudey (1:01:51) to discuss the series. Blue Jays TV voice Dan Shulman (35:01) hops on to discuss what it would take for the Jays to land Juan Soto in a trade. Ken Reid (46:29) makes his contractually obligated appearance.The views and opinions expressed in this podcast are those of the hosts and guests and do not necessarily reflect the position of Rogers Media Inc. or any affiliate.
Welcoming Dr Georgia, Dr Sharon and Sacred Magic, the healing hour of transformation. Dr Sharon and Dr Georgia take time to unpack the energetics behind this hour of activation, transmutation and transformation. Enter the hub of magical possibilities and tap into your sacred nature. Call in to start the powerful shift you desire! Watch live on Facebook. facebook.com/transformationtalkradio Call in at 800-930-2819 for your personal energy reading and shift.
In this episode of the Duct Tape Marketing Podcast, I interview Edward Sullivan. Edward has been coaching and advising start-up founders, Fortune 10 executives, and heads of state for over 15 years. His clients include executives from Google, Salesforce, Slack, and dozens of other fast-growth companies. He holds an MBA from Wharton and an MPA from the Harvard Kennedy School. Edward is CEO & President of the renowned executive coaching consultancy Velocity. He also has a new book launching on June 21, 2022, called — Leading With Heart: 5 Conversations That Unlock Creativity, Purpose, and Results. Links to resources: Leadingwithheartbook.com Take the Marketing Assessment: Marketingassessment.co
This week, Linux Out Loud chats about what it is like for us to be content creators on the Tux Digital Network. Welcome to episode 14 of Linux Out Loud. We fired up our mics, connected those headphones as we searched the community for themes to expound upon. We kept the banter friendly, the conversation somewhat on topic, and had fun doing it. 00:00 Introduction 01:19 OnX Maps 05:05 Power Monitoring 08:10 Creepy Tale 2 13:05 Kid Check 16:21 Back Stage Pass 37:29 Game of the Week 42:37 Solar Panel Setup 45:38 3D Printer Update 59:34 Close Join in the chat on the Discourse forum here: https://discourse.destinationlinux.network/t/back-stage-pass-linux-out-loud-14/5180 Matt - OnX Maps - https://www.onxmaps.com/ - Game of the Week - https://store.steampowered.com/app/502500/ACECOMBAT7SKIESUNKNOWN/ Nate - Power Monitoring Solutions - https://circuitsetup.us/ Wendy - Finished a Game - https://store.steampowered.com/app/1550510/CreepyTale2/ - Open Source VR Drivers Installed - openVR - osvr-core - osvr-libfunctionality - osvr-openhmd - osvr-rendermanager - 3D Prints - https://www.thingiverse.com/thing:5024925 - https://www.thingiverse.com/thing:5274675 - https://www.thingiverse.com/thing:2412007 - https://www.thingiverse.com/thing:2707219 - https://www.thingiverse.com/thing:2390180 Upcoming Events - Game Shpere 24 hour Charity Livestream - Monday, June 20, 2022 through Tuesday, June 21, 2022 - Starts 9:00 AM EDT / 1:00 PM UTC - Charity - CURE Citizens United for Research in Epilepsy - https://www.cureepilepsy.org/ Contact info Matt (Twitter @MattGameSphere) Wendy (Mastodon @WendyDLN) Nate (Website CubicleNate.com)
Adam and Mark connect to discuss the latest in the Johnny Depp Amber Heard circus as well as covering the opening of Michael Sussmann's case, the first brought in the three years since John Durham was appointed by then Attorney General William Barr. Watch Beyond A Reasonable Doubt on YouTube at YouTube.com/ReasonableDoubtPodcast and subscribe while you're there.
Laurence Holmes was joined by Danny Parkins and Matt Spiegel for the daily transition segment. They discussed the successful start to the season for the Audacy softball team and more.
Michael K. Sahota, CEC, controversial thought leader and keynote speaker revealing the truth about organizational realities and what it takes to create high performance. What is a shift of consciousness at the individual level as a leader and within an organization ? What are the tools and concrete examples to create that shift? How does this translate at the organizational level? How do you define consciousness? Michael Sahota Michael K. Sahota, CEC, controversial thought leader and keynote speaker revealing the truth of organizational realities and what it takes to create high performance. Michael is the founder and CEO of SHIFT314 Inc - a leadership training and consulting organization, specializing in new ways of working, Agile, Digital, Lean and Evolutionary Leadership. He is the co-creator of the SHIFT314 Evolutionary Leadership Framework (SELF) , an integrated system for organizational transformation that has the ability to deliver extraordinary results for Business Agility. Michael has trained thousands of leaders worldwide through his highly accoladed Certified Agile Leadership Training. Michael gained notoriety in 2012 with his groundbreaking book “An Agile Adoption and Transformation Guide” on the forefront of leadership and culture. Co-Author of Emotional Science (2018) and the latest book “Leading Beyond Change '' a practical guide on “How To” lead evolutionary change and unlock the success of your organization. Excellent Executive Coaching Podcast If you have enjoyed this episode, subscribe to iTunes. We would love a review on iTunes or other platform. The EEC podcasts are sponsored by MKB Excellent Executive Coaching that helps you get from where you are to where you want to be with customized leadership and coaching development programs. MKB Excellent Executive Coaching offers leadership development programs to generate action, learning, and change that is aligned with your authentic self and values. Transform your dreams into reality and invest in yourself by scheduling a discovery session with Dr. Katrina Burrus, MCC to reach your goals. Your host is Dr. Katrina Burrus, MCC, founder and general manager of www.mkbconseil.ch a company specialized in leadership development and executive coaching.
LET's GOOOOOO! On the latest #CareFreeBlackGirl 2.0 episode we tackle Friendship breakups, Hot or Not and F*ck, Marry & Heal! 2.0 Question of the Episode (Starts at 6:16): Have you ever dealt with a friendship breakup? How has it affected your relationships with new friends since then? Hot or NOT? (Starts at 26:43) Kendrick Lamar, 'The Heart Part 5' Ella Mai's, 'Heart on my Sleeve' Lakeyah, 'I Look Good' Sir, 'Satisfaction' Glorilla, 'F.N.F. (Let's Go) F*ck, Marry, Heal (Starts at 53:16) Doechii, Azalea Banks & Baby Tate Jesse Williams, Tyler LaPlay & Keith Powers Kofi Siriboe, DaVinci & Pardison Fontaine Brandee Evans, Shannon Thorpe & Miracle Watts CareFree Keys (Starts at 1:07:43) Music curated by DJ Candy Raine. Tune in each month and hashtag #CareFreeBlackGirl to stay engaged with the conversation. Follow the hosts on Twitter; DJ Candy Raine - @mycandyraine Rebellious Kiana - @RebelliousKiana Nika - @dopeitsnika Mimi Navah - @MimiNavah Follow the Podcast on Twitter @CFBGPod Produced by Quanna Engineered by DJ Candy Raine Executively Produced by Wize Grazette Find out more at https://carefreeblackgirl.pinecast.co Check out our podcast host, Pinecast. Start your own podcast for free with no credit card required. If you decide to upgrade, use coupon code r-1aea92 for 40% off for 4 months, and support #CareFreeBlackGirl.
An e-car leasing trial is gearing up to provide low income families with hybrid vehicles. The government yesterday announced $20 million for a low-emissions vehicle leasing scheme for low-income families. But charitable foundation Akina is pulling ahead with its own pilot. Chief executive Nicola Nation says it'll be launched next week.
While at the Roland Wolf Event I was able to meet Eduardo. His story is one that will blow you away. Eduardo is a Caracas, Venezuela native and resided there for 28 years. Safety concerns brought him and his family to the United States. Prior to their move, Eduardo had a desire to enter the stock market and knew that becoming a trader was his calling. While in Venezuela he received a degree in Electrical Engineering and later entered an MBA program concentrating in Finance. Throughout his MBA he did not feel that the content truly matched his passions, he was introduced to a trading investment course by a professor. required a shift in his trading which led to his discovery of profits. Upon his arrival to the United States Eduardo was determined to maintain his passion for trading. He worked different positions to support his family while still maintaining his career in trading. Eduardo was strategic in removing the pressure of making a profit. Eduardo's story is one you will not want to miss. Cobra Trading Broker DISCOUNT! - https://get.cobratrading.com/bthestory/ Follow Eduardo on Twitter: https://twitter.com/edu_trades Book a 1 on 1 Call with me - https://calendly.com/bthetrader/1-on-1-talk Favorite Trading Books & Setup - https://kit.co/BTheTrader Click here to sign up for our Newsletter BTheTrader Merch - https://my-store-11542608.creator-spring.com Catch me trading live on Twitch - https://www.twitch.tv/bthetrader
Spoiler-lite Starts: 10:36 Plot Synopsis: Dr Stephen Strange casts a forbidden spell that opens a portal to the multiverse. However, a threat emerges that may be too big for his team to handle. Follow Kate Sanchez: https://twitter.com/OhMyMithrandir Follow Matt Donahue: https://twitter.com/dattm18 Follow Collier "CJ" Jennings: https://twitter.com/CJWritesThings
Are you looking for ways to improve your book marketing efforts? Would you like a resource that handles all your graphic design needs for promoting your books? Then, look no further than Book Brush! Whether you want to create your own book cover, make A+ content for your Amazon product page, or produce a book trailer, Book Brush has what you need. Level-Up Your Self-Publishing Business TODAY: Book Brush - https://DaleLinks.com/BookBrush The Amazon Self Publisher – https://DaleLinks.com/SelfPubBook Subscribe to Self-Publishing with Dale on YouTube at https://DaleLinks.com/YT and https://DaleLinks.com/YouTubePodcast. Join other like-minded and motivated self-publishers in the Self-Publishing Books Group. Learn, grow, and network with authors, freelancers, and industry experts at https://DaleLinks.com/SPB. Remember to answer the 3 questions to gain entry. Get access to my go-to resource, Publisher Rocket. Confidently research profitable keywords & categories. Easily select effective keywords for Amazon Advertising campaigns. For more details, visit https://dalelinks.com/PR. FULL DISCLOSURE: Most outbound links financially compensate the podcast through affiliate programs or sponsorship deals. We only recommend products and services we've used and confidently stand behind. Using the links do not adversely affect your purchase price and greatly helps support the channel. Thank you for your understanding.
Good News: A new precedent is being set in the Philippines, to hold corporations responsible for their roles in the climate change crisis, Link HERE. The Good Word: An absolutely delightful quote from C.S. Lewis. Good To Know: A little bit of fascinating information about how we measure time. Good News: The Smithsonian Institution is […]
In this episode, the THRU-r community welcomes back Wilderness Skills Instructor and Mountain Education founder Ned Tibbits to discuss the pros and cons of starting the Pacific Crest Trail for a Southbound (SOBO) hike. This is the audio from our community Zoom meetup incase you missed the live event! During this discussion, Ned goes over the pros and cons regarding weather, logistics, and strategy when starting from Washington in (typically) the summer months. Ned has founded a non-profit organization which promotes wilderness safety called Mountain Education. If you feel like this information added value to your hiking preparation, consider donating to thank him for his time and knowledge. You can donate here. If you loved this episode make sure to like, subscribe, rate & review, and share this podcast! Relevant Links: River Crossing Intensive Podcast Episode S1 E3 Steep Snow Travel Podcast Episode S1 E5 Over Snow Navigation Podcast Episode S1 E9 Connect With Us / Join The THRU-r Community: THRU-r Website THRU-r Instagram THRU-r Facebook THRU-r Youtube THRU-r TikTok Cheer's YouTube Cheer's Instagram Episode Music: "Communicator" by Reed Mathis --- Send in a voice message: https://anchor.fm/thru-r/message Support this podcast: https://anchor.fm/thru-r/support
It's an ancient and unbelievably dangerous vocation, beckoning workers to the undiscovered depths of our world. But in their digging, do they ever unearth things they can't explain? Today, we're sharing stories about miners and the darkness below.
Episode 110 ... week in review of May 14, 2022 ...Cold Open Question:- What is the optimal number of parks to hop to during a single day?Starts @2:06 ...New Discord Members and DCI Update- Welcome Ryan W to Discord!- Matt covers a "State of the DCI" on the latest episode of the Happily EVERYthing Disney podcast: iTunesStarts @8:50 ...Topic: Top 5 Attractions During Fireworks at the Magic Kingdom- If you aren't going to watch the fireworks, what rides are the best use of that time? Which ones can you see the fireworks from? Which will let you save time waiting on line at other times of the day?Starts @10:22 ...DBC Discord Engagement: Next Disney Dining- Great engagement on this topic - we share what dining we are looking forward to on our next trip along with a few mentioned on Discord- Next week's topic: What WDW resort would you like to stay at that you haven't? What one have you stayed at that you don't feel a need to repeat?Starts @21:02 ...Attractionality: Tomorrowland Speedway- Drivers, start your engines! A ride many people would like to see go, but what did the voters say?- What is the argument for keeping it?Starts @33:16 ...What is Everybody Talking About?- Cosmic Rewind - largely very positive reviews, but a few muted one (e.g., this one from Alicia Stella)- Rumor: Changes coming to Genie+ - Rumor: Disney to start charging for housekeeping. Source: WDWNTStarts @41:13 ...DBC Recommends: Honey, I Shrunk Nathan Hartman's WDW Music Collection- Twitter user who has kindly put tons of WDW park and resort music on a google drive. Amazing stuff here - current and past. Check it out!Source: TwitterStarts @57:51 ...* Reminder to like, subscribe, rate, and review the DBC Pod wherever you get your podcast *Send us an e-mail! .... firstname.lastname@example.orgFollow us on social media:- Instagram: https://www.instagram.com/TheDBCPod/- Twitter: https://twitter.com/TheDBCPod- Facebook: https://www.facebook.com/TheDBCPod- YouTube Channel: https://www.youtube.com/thedbcpod- Discord Server: https://discord.com/invite/cJ8Vxf4BmQNote: This podcast is not affiliated with any message boards, blogs, news sites, or other podcasts
After trading away Russell Wilson to Denver, the Seahawks have yet to announce his replacement. Seattle currently has Drew Lock, Geno Smith, Jacob Eason, and Levi Wallace in their QB room. The main two guys in the mix for the starting Quarterback job are Drew Lock and Geno Smith, which one will be the starting QB for the Seattle Seahawks this upcoming NFL season? The Pittsburgh Steelers signed Mitchell Trubisky on day 1 of NFL Free Agency and a few months later drafted rookie QB Kenny Pickett in the first round of the 2022 NFL Draft. Trubisky brings veteran experience to the Steelers Quarterback room while Pickett stays in the local Pittsburgh area after playing his college ball at Pitt which shares the same facilities as the Steelers. JT Sports gives his thoughts on who he believes will be the starting QB for the Steelers this season. The Houston Texans hired Lovie Smith to become their next Head Coach in a surprising move after parting ways with David Culley after a 4-13 season. Lovie Smith has decades' worth of NFL Head Coaching experience and was Houstons DC last year, however, he hasn't had success in his last few head coaching stops following his tenure with the Bears. JT Sports gives his first-year expectations for Lovie Smith and the Houston Texans. Matt Eberflus was hired as the new Head Coach for the Chicago Bears after four seasons as DC for the Colts. Eberflus has been regarded as one of the best defensive minds in the NFL but will have his work cut out for him taking over a Bears team that is one of the worse teams going into the upcoming NFL season. JT Sports gives his first-year expectations for Matt Eberflus and the Chicago Bears. --- Support this podcast: https://anchor.fm/jtsports/support
Things are always darkest before the dawn... Even when it comes to neckbeard stories. How is a neckbeard created? Well, the process might surprise you in some scenarios. Firebeard will tell us all of the grim, tragic details.YouTube: https://www.youtube.com/reddxyDiscord: https://discord.gg/Sju7YckUWuPayPal: https://www.paypal.me/daytondoesPatreon: http://patreon.com/daytondoesTwitter: http://www.twitter.com/daytondoesFacebook: https://www.facebook.com/ReddXD/Teespring: https://teespring.com/stores/reddx
We sat down at the picnic table with John Hart Asher, host of Central Texas Gardener and Cofounder/Senior Environmental Designer at Blackland Collaborative to talk about pocket prairies. What's a pocket prairie? It's a very small prairie. What's a prairie? It's a community of native grasses and forbs wildflowers that have evolved along with microbes, plants, and animals over millennia. This "disturbance-driven ecology" historically relied on periodic fire and low-frequency, high-intensity grazing to function. John Hart sees the "millions-year-old technology" of the American prairie as a replicable system that we can borrow in our own yards to sequester carbon, manage stormwater runoff, and support the essential interconnections between life forms that make up the food-soil web. As Douglas Tallamy writes in his book Nature's Best Hope, "If each American landowner made it a goal to convert half of his or her lawn to native plant communities...[we] could collectively restore some semblance of ecosystem function to more than twenty million acres of what is now ecological wasteland." We discuss the role of wildfires and buffalo grazing in Texas before European settlement, the Lady Bird Johnson Wildflower Center's research on prescribed burning, and how to prepare, install, and maintain a pocket prairie. John Hart insists that we must rethink our approach to landscape design, gardening, land ownership, and even our concept of "nature" if we are to sustain life on earth. He describes prairie restoration as "a trajectory, not an intervention" -- a process, rather than a product -- which can help us reconnect with the web of life, reduce climate anxiety, and make our homes more beautiful to boot. Mentioned in this episode: Nature's Best Hope: A New Approach to Conservation that Starts in Your Yard by Douglas Tallamy; the USDA Web Soil Survey; Black Owl Biochar; KR Bluestem. Please join our Patreon for bonus episodes, early access, and more!
Catalan Townspeople Declare Independence from Spain :: Anonymous FBI Agent Speaks Out on Project Veritas Raids :: Mark's Special Economic Zone Failing Before it Starts? :: Copyright to be Shortened? :: Parody and Copyright :: Show: 2022-05-13 Ian, Nobody, Chris W.
Alisha Johnson is a Care in Aging Post-Doctoral Fellow at the Sinclair School of Nursing here in Columbia. She spoke about aging in place, and what that means for older adults and long-term care facilities.
Three of our favorite segments from the week, in case you missed them. Eric Holder and Sam Koppelman on Voting Rights (First) | Parents Grapple with the Baby Formula Shortage (Starts at 38:00) | Unchecked Emissions and the Threat of Mass Marine Extinction (Starts at 55:10) If you don't subscribe to the Brian Lehrer Show on iTunes, you can do that here.
Future of Work Sherpa Dan Smolen explores mastering time for future work with guest Kris Ward. Kris is the host of the Win the Hour, Win the Day Podcast. She counsels entrepreneurs on how to manage their time resources so that they become successful in work, but also in life. Main podcast segment starts at 3:02 Time mastery is critical for success in the future of work. And to that end, Kris and Dan cover a lot of ground around time mastery including: The unique value proposition for Win the Hour, Win the Day. Starts at 4:13 How the notion of working a lot of hours is believed to be good. Starts at 6:43 A deep dive into her "Super Tool Kit" and what makes it effective. Starts at 11:07 Why entrepreneurs and career professionals get jammed up with "time sucks." Starts at 12:01 Infrastruture in the future of work frame. Starts at 14:00 The ways quality of work and life improves with time mastery. Starts at 16:50 The powerful outcome of giving up tasks. Starts at 18:32 In a future of work frame, getting away from the notion that the amount of time expensed in work is everything. Starts at 24:15 Mastering time for future work allows entrepreneurs and career professionals to thrive in work and life. Main podcast segment starts at 3:02 About our guest: Kris Ward is a leading authority on scaling business and maximizing the resource of time. She received a Bachelor of Arts degree from Ryerson University. Kris lives and works in the province of Ontario, Canada. EPISODE DATE: May 13, 2022 Social media: – LinkedIn – Twitter – Instagram – Podcast – Website Please Subscribe to The Dan Smolen Podcast on: – Apple Podcast – Android – Google Podcasts – Pandora – Spotify – Stitcher – TuneIn …or wherever you get your podcasts. You may also click HERE to receive our podcast episodes by email. Image credits: Clock, Valerii Evalakhov for iStock Photo; Portrait, Kris Ward; podcast button, J. Brandt Studio for The Dan Smolen Experience.
Five Ways to Keep Building Your Competitor Mindset After Today's Episode Join the new Competitor Nation at Community.CompeteEveryDay.com Text PODCAST to 972-945-9113 to join our Morning Motivation Club Hire Jake to speak at your company or event. Click here to learn more. Read the book, “Compete Every Day,” here. Save 15% on empowering gear at CompeteEveryDay.com
Its episode 176 and the boys catch up talking about Scotts favourite cup, Malls having none of it, Kept partners, Mouldy bread, Mall cant get a word in, Hashtag Live Recording is almost sold out, Sexy underwear made from bread, Welcome to Scotland, Cheap Bread, Scotts moving house (again), if you join our Patreon you will also hear about how The 90's were the best period for anything, Is Mall a Tory?, Politicians, Rangers fan's in a Hot-air Ballon, Bournemouth and cant get home and loads more ... Grab the last of the tickets for #100Heros Live Episode Recording. Half price if you are a Hero ! https://www.seetickets.com/event/hashtag-show-live-recording/the-classic-grand/2324816 The Classic Grand, Sunday 19 Jun 2022, Tickets only £10 or half price if you are a Hero ! Doors Open: 13:00 Starts: 14:00 Become Patreon #Hero https://www.patreon.com/thehashtagshow
Laura and the NFL Live Crew discuss the biggest concerns on the Packers' roster, which team has a better offense; the Bears or the Lions, how Yannick Ngakoue's addition affects the Colt's defense, how to defend QBs in the AFC North, and revenge games they're looking forward to. Learn more about your ad choices. Visit megaphone.fm/adchoices
On this week's episode of the podcast, Jeannie Sowers of University of New Hampshire joins Marc Lynch to discuss POMEPS's newest publication, POMEPS Studies 46:Environmental Politics in the Middle East and North Africa. (Starts at 0:36). Mariam Salehi of Freie University Berlin discusses her new book, Transitional justice in process: Plans and politics in Tunisia. The book discusses the development and design of the transitional justice mandate, and looks at the performance of transitional justice institutions in practice. It examines the role of international justice professionals in different stages of the process, as well as the alliances and frictions between different actor groups that cut across the often-assumed local-international divide. (Starts at 32:24). Music for this season's podcast was created by Bashir Saade (playing Ney) and Farah Kaddour (on Buzuq). You can find more of Bashir's work on his YouTube Channel.
In this week's episode of Porch Talk Ezra, Eric, and Diana are joined by world traveler and entrepreneur Alea Simone. Alea travels the world and runs a business giving travel tips, guides, group trips, and so much more! In this interview we hear her story about how she quit her job and started traveling the world, safety tips she has, general travel tips, the best places to go, the most overrated places, good food, and so much more! See below for time stamps for some of the highlights and important topics for this interview! interview Starts: (1:31) Safety tips/traveling as a women and black women: (9:05) General travel tips: (21:55) Where is it worth spending on your vacations: (28:48) Some places you should avoid traveling because they're overrated: (31:44) Biggest waste of money while traveling: (37:20) Best food while traveling and where to find the best food: (40:27) Last Important travel tip: (48:28) Music & TV Recommendations: (50:20) All the links you could ever need!: https://linktr.ee/porchtlk Merch Link: https://teespring.com/stores/porchtalk
032 - Maternity Leave Starts NOW!Hey Shayla Podcast | Ep: 032Guest: ME! @heyshaylaThank you for listening to the Hey Shayla podcast! Here, we love to learn new things and decide what works for us and our family.. We're the moms that support instead of judge and know there are many ways to do something right. I'd love to connect on Instagram @heyshaylaI recorded this episode a week before my due date letting you know I'll be taking maternity leave! Likely baby is already here, if you want to know, I imagine I'll be on Instagram (@heyshayla) because honestly that's the easiest place to show up. If you need a sign to slow down and enjoy your babies. THIS IS IT. As entrepreneurs it's hard to give ourselves this time but I'm so glad I decided to! I hope that you all have a great start to the summer and I'll be back soon!Xo ShayFood prep Cook Unity (use this ink to get a discount): https://www.cookunity.com/landing-referral?referral_code=shaylchri3If you want to know when we're back and running, get on the email list!: www.heyshayla.com/podcastemailThe book I read to sloooow down: https://amzn.to/3vIOcXN'Affiliates I work with:*California Beach Co: Travel Playpen use HEYSHAYLA for an additional 15% off whatever sale they're running!*LoveBug Probiotics: Pre and postnatal probiotics use code HEYSHAYLA for 15% off*My Little Eaters: Guide to Baby Led Weaning use code HEYSHAYLA for 15% off*Kindred Bravely: Maternity Sports Bra use code HEYSHAYLA for 20% off*TushBaby: Great “Up-Down” Baby carrier use code HEYSHAYLA for 15% offLet's Connect!Instagram (@heyshayla)YouTube (Hey Shayla)Website (www.heyshayla.com)Amazon (https://www.amazon.com/shop/heyshayla)**Disclaimer: Please note that some of the links here are affiliate links. Which means at no cost to you, I will earn a commission if you decide to make a purchase after clicking through the link. I only work with companies that I love, and that I think you will love.
Medical education is in the midst of a revolution. Students and educators want their education ingrained in antiracism and hope that by acknowledging and teaching about bias and systemic discrimination in the medical field, the next generation of doctors will be better equipped to dismantle racism within health care. STAT's “Color Code” takes a look at the groundswell of antiracism work in medicine and medical education, and explores the backlash these endeavors have received, which span from institutional repercussions to protests from hate groupsGuests:Jerrel Catlett: An MD/PhD student at the Icahn School of Medicine at Mount Sinai. Rebecca Zhou: A peer in medical school at Mt. Sinai.Jennifer Dias: An MD candidate at the Icahn School of Medicine at Mount Sinai.Michelle Morse: Chief Medical Officer of the NYC Dept. of Health and Mental Hygiene.Aysha Khoury: Assistant Professor at the Morehouse School of Medicine.Read a full transcript on our website.Want more Tradeoffs? Sign up for our free weekly newsletter featuring the latest health policy research and news.Support this type of journalism today, with a gift.Follow us on Twitter. See acast.com/privacy for privacy and opt-out information.
Welcome to TechTime Radio with Nathan Mumm, the show that makes you go "Hummmm" Technology news of the week for May 8th – May 14th, 2022.Today on the show marks our 100th Celebration Episode, "A Look Back at the Last Two Years of the Show" I am sure we will have a few items that will make you go humm today. Today's Show is not a standard episode as this particular episode has been dedicated to the review of TechTime with Nathan Mumm, the making of a show. Segments like "Top Stories" will not be done as we have guests, behind-the-scenes information, and hidden gems about our radio show. Long-time producer Gwen Way will be on and talk about what it takes to prepare for a show and give you a look behind the curtain into our production show meetings. We will then talk about a new Gadgets and Gear and explain why Gwen took this segment over. "Mike's Mesmerizing Moment" will be a question on everyone's mind – How and Why did Mike decide to do a radio show with Nathan. And, of course, our "Pick of the Day" whiskey tasting. We look back at what we did before our standard thumbs up and thumbs down review. So sit back, raise a glass, and Welcome to TechTime with Nathan Mumm episode 100, "A Look Back at the Last Two Years of TechTime" Episode 100: Starts at 1:14 --- [Now on Today's Show]: Starts at 3:53--- [The Beginnings of TechTime Radio]: Starts at 10:10We talk about Studio 6, TTR unplugged, and how the story started--- [Pick of the Day - Whiskey Tasting Review]: Starts at 27:55Colonel E.H Taylor Small Batch | 100 Proof | $45.00--- [Gwen Way Behind the Scenes & Gadgets and Gear]: Starts at 34:30Gwen Way joins us for a look at the Production Meetings and Behind the Scenes -100th Celebration Episode, "A Look Back at the Last Two Years of the Show" --- [This Week in Technology]: Starts at 47:36May 14, 1973The United States launched Skylab One, its first human-crewed space station. It was the last launch of the Saturn five rocket and the largest payload ever launched into space at the time. Skylab will fall back into the Earth's atmosphere in July of 1979.Skylab was the first United States space station launched by NASA and occupied for about 24 weeks between May 1973 and February 1974. It was operated by three-astronaut crews, each with three members: Skylab 2, Skylab 3, and Skylab 4. The operations included an orbital workshop, a solar observatory, Earth observation, and hundreds of experiments. --- [Why a Co-Host and Crazy Locations Onsite]: Starts at 50:04Mike and Nathan talk about some of the memorable shows -100th Celebration Episode, "A Look Back at the Last Two Years of the Show" --- [Mike's Mesmerizing Moment brought to us by StoriCoffee®]: Starts at 52:11 --- [Pick of the Day]: Starts at 53:27Colonel E.H Taylor Small Batch | 100 Proof | $45.00 Mike: Thumbs Up Nathan: Thumbs Up
Lately, I have struggled with this topic as I build my Soul Healers community. Let's discuss how Belief Systems stem from your inherent lack of worth. Where did it start? How do we catch them (ego) and learn to rebuild them with a solid foundation of gold! Share with me, is this an issue for you, and for how long? How does it show up for you? HIT the LIKE button and SUBSCRIBE! Never miss an episode. Hello, empowered empaths! Welcome to Heart-Led & Soul Fed, Season 3 Episode 195, this is a live unscripted show and podcast hosted by Soul Purpose Mentor, Healer, and Medium Christine. All about our soulful intuitive journey to healing at the 360-degree level. Depression and Anxiety are a side effects of not living intuitively, not trusting your gut, the lost connections with your higher self and others! I know that if more people hear your story, my story, our story, that's how transformation happens and love endures. Christine guides Empaths to unleash their gifts as lightworkers that are masked as depression & anxiety. Through that work, you will discover that you have always been intuitive, that you have gifts (psychic, medium, empath, healer) Support us here (Exclusive Community Benefits) we are building community, global healing centers, new equipment, helping fund Animal / Children & the Elderly https://www.patreon.com/user?u=53199576 Buy me a coffee https://www.buymeacoffee.com/Christin... *** SIGN up for FREE on StreamYard, here's my referral link https://streamyard.com?pal=5146271637... Wednesday's LIVE FACEBOOK / YOUTUBE Podcast https://anchor.fm/24k-healing ++LOOKING for community? Connection? Join us for free on meetup, FREE events, and workshops https://www.meetup.com/meetup-group-w... Book a 1 on 1 session here https://24khealing.godaddysites.com/ ++ MY new book is out "Intuition Saved My Life" https://www.amazon.com/gp/product/B09... NEW online courses are here https://www.learndesk.us/users/profil... Sign up for the monthly SOULletter & Receive a FREE Chakra eBook HERE - https://mailchi.mp/23472c4ff38b/24khe... * Unleash Your Magic, Unleash Your Purpose Mentorship and Soul Healers Club is here (unleash your intuition, mediumship development, intuitive coaching, energy awareness/healing, and more) SIGN UP here https://www.24khealing.com/unleash-yo... Starts year round! --- Send in a voice message: https://anchor.fm/24k-healing/message Support this podcast: https://anchor.fm/24k-healing/support
In This Episode, guest JoAnna Mitchell, (@themaladjustedmermaid on TikTok) joins the crew, as we react to the very real possibility of Roe V Wade being overturned in light of the draft opinion leaked to the public. Intro: Ana Kasparian "I don't care about your religion." Outro: George Carlin on abortion Music: "Testify" By Nas & "La femme fetal" By Digable Planets "Belief It Or Not" YouTube video mentioned in pod: https://youtu.be/k-KpiuRkzLs
This week, Linux Out Loud chats about what makes a good beginner-friendly Linux Distro. Welcome to episode 13 of Linux Out Loud. We fired up our mics, connected those headphones as we searched the community for themes to expound upon. We kept the banter friendly, the conversation somewhat on topic, and had fun doing it. 00:00 Introduction 00:52 Contact Update 03:21 Homebank 06:27 Skrooge 12:05 One Size Fits All 37:56 Wendy's 3D Printer Update 49:40 Game of the Week 52:26 Solar Update 55:50 Close Join in the chat on the Discourse forum here: https://discourse.destinationlinux.network/t/distro-of-the-fledgling-linux-out-loud-13/5157 Matt - Homebank - http://homebank.free.fr/en - Game of the Week - https://store.steampowered.com/app/560130/PillarsofEternityIIDeadfire/ Nate - Skrooge - https://skrooge.org/ Upcoming Events - Game Shpere 24 hour Charity Livestream - Monday, June 20, 2022 through Tuesday, June 21, 2022 - Starts 9:00 AM EDT / 1:00 PM UTC - Charity - CURE Citizens United for Research in Epilepsy - https://www.cureepilepsy.org/ Contact info Matt (Twitter @MattGameSphere) Wendy (Mastodon @WendyDLN) Nate (Website CubicleNate.com)
About AmyAmy Tobey has worked in tech for more than 20 years at companies of every size, working with everything from kernel code to user interfaces. These days she spends her time building an innovative Site Reliability Engineering program at Equinix, where she is a principal engineer. When she's not working, she can be found with her nose in a book, watching anime with her son, making noise with electronics, or doing yoga poses in the sun.Links Referenced: Equinix Metal: https://metal.equinix.com Personal Twitter: https://twitter.com/MissAmyTobey Personal Blog: https://tobert.github.io/ TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is sponsored in part by our friends at Vultr. Optimized cloud compute plans have landed at Vultr to deliver lightning-fast processing power, courtesy of third-gen AMD EPYC processors without the IO or hardware limitations of a traditional multi-tenant cloud server. Starting at just 28 bucks a month, users can deploy general-purpose, CPU, memory, or storage optimized cloud instances in more than 20 locations across five continents. Without looking, I know that once again, Antarctica has gotten the short end of the stick. Launch your Vultr optimized compute instance in 60 seconds or less on your choice of included operating systems, or bring your own. It's time to ditch convoluted and unpredictable giant tech company billing practices and say goodbye to noisy neighbors and egregious egress forever. Vultr delivers the power of the cloud with none of the bloat. “Screaming in the Cloud” listeners can try Vultr for free today with a $150 in credit when they visit getvultr.com/screaming. That's G-E-T-V-U-L-T-R dot com slash screaming. My thanks to them for sponsoring this ridiculous podcast.Corey: Finding skilled DevOps engineers is a pain in the neck! And if you need to deploy a secure and compliant application to AWS, forgettaboutit! But that's where DuploCloud can help. Their comprehensive no-code/low-code software platform guarantees a secure and compliant infrastructure in as little as two weeks, while automating the full DevSecOps lifestyle. Get started with DevOps-as-a-Service from DuploCloud so that your cloud configurations are done right the first time. Tell them I sent you and your first two months are free. To learn more visit: snark.cloud/duplo. Thats's snark.cloud/D-U-P-L-O-C-L-O-U-D.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. Every once in a while I catch up with someone that it feels like I've known for ages, and I realize somehow I have never been able to line up getting them on this show as a guest. Today is just one of those days. And my guest is Amy Tobey who has been someone I've been talking to for ages, even in the before-times, if you can remember such a thing. Today, she's a Senior Principal Engineer at Equinix. Amy, thank you for finally giving in to my endless wheedling.Amy: Thanks for having me. You mentioned the before-times. Like, I remember it was, like, right before the pandemic we had beers in San Francisco wasn't it? There was Ian there—Corey: Yeah, I—Amy: —and a couple other people. It was a really great time. And then—Corey: I vaguely remember beer. Yeah. And then—Amy: And then the world ended.Corey: Oh, my God. Yes. It's still March of 2020, right?Amy: As far as I know. Like, I haven't checked in a couple years.Corey: So, you do an awful lot. And it's always a difficult question to ask someone, so can you encapsulate your entire existence in a paragraph? It's—Amy: [sigh].Corey: —awful, so I'd like to give a bit more structure to it. Let's start with the introduction: You are a Senior Principal Engineer. We know it's high level because of all the adjectives that get put in there, and none of those adjectives are ‘associate' or ‘beginner' or ‘junior,' or all the other diminutives that companies like to play games with to justify paying people less. And you're at Equinix, which is a company that is a bit unlike most of the, shall we say, traditional cloud providers. What do you do over there and both as a company, as a person?Amy: So, as a company Equinix, what most people know about is that we have a whole bunch of data centers all over the world. I think we have the most of any company. And what we do is we lease out space in that data center, and then we have a number of other products that people don't know as well, which one is Equinix Metal, which is what I specifically work on, where we rent you bare-metal servers. None of that fancy stuff that you get any other clouds on top of it, there's things you can get that are… partner things that you can add-on, like, you know, storage and other things like that, but we just deliver you bare-metal servers with really great networking. So, what I work on is the reliability of that whole system. All of the things that go into provisioning the servers, making them come up, making sure that they get delivered to the server, make sure the API works right, all of that stuff.Corey: So, you're on the Equinix cloud side of the world more so than you are on the building data centers by the sweat of your brow, as they say?Amy: Correct. Yeah, yeah. Software side.Corey: Excellent. I spent some time in data centers in the early part of my career before cloud ate that. That was sort of cotemporaneous with the discovery that I'm the hardware destruction bunny, and I should go to great pains to keep my aura from anything expensive and important, like, you know, the SAN. So—Amy: Right, yeah.Corey: Companies moving out of data centers, and me getting out was a great thing.Amy: But the thing about SANs though, is, like, it might not be you. They're just kind of cursed from the start, right? They just always were kind of fussy and easy to break.Corey: Oh, yeah. I used to think—and I kid you not—that I had a limited upside to my career in tech because I sometimes got sloppy and I was fairly slow at crimping ethernet cables.Amy: [laugh].Corey: That is very similar to growing up in third grade when it became apparent that I was going to have problems in my career because my handwriting was sloppy. Yeah, it turns out the future doesn't look like we predicted it would.Amy: Oh, gosh. Are we going to talk about, like, neurological development now or… [laugh] okay, that's a thing I struggle with, too right, is I started typing as soon as they would let—in fact, before they would let me. I remember in high school, I had teachers who would grade me down for typing a paper out. They want me to handwrite it and I would go, “Cool. Go ahead and take a grade off because if I handwrite it, you're going to take two grades off my handwriting, so I'm cool with this deal.”Corey: Yeah, it was pretty easy early on. I don't know when the actual shift was, but it became more and more apparent that more and more things are moving towards a world where you could type. And I was almost five when I started working on that stuff, and that really wound up changing a lot of aspects of how I started seeing things. One thing I think you're probably fairly well known for is incidents. I want to be clear when I say that you are not the root cause as—“So, why are things broken?” “It's Amy again. What's she gotten into this time?” Great.Amy: [laugh]. But it does happen, but not all the time.Corey: Exa—it's a learning experience.Amy: Right.Corey: You've also been deeply involved with SREcon and a number of—a lot of aspects of what I will term—and please don't yell at me for this—SRE culture—Amy: Yeah.Corey: Which is sometimes a challenging thing to wind up describing or putting a definition around. The one that I've always been somewhat partial to is, “SRE is DevOps, except you worked at Google for a while.” I don't know how necessarily accurate that is, but it does rile people up.Amy: Yeah, it does. Dave Stanke actually did a really great talk at SREcon San Francisco just a couple weeks ago, about the DORA report. And the new DORA report, they split SRE out into its own function and kind of is pushing against that old model, which actually comes from Liz Fong-Jones—I think it's from her, or older—about, like, class SRE implements DevOps, which is kind of this idea that, like, SREs make DevOps happen. Things have evolved, right, since then. Things have evolved since Google released those books, and we're all just figured out what works and what doesn't a little bit.And so, it's not that we're implementing DevOps so much. In fact, it's that ops stuff that kind of holds us back from the really high impact work that SREs, I think, should be doing, that aren't just, like, fixing the problems, the symptoms down at the bottom layer, right? Like what we did as sysadmins 20 years ago. You know, we'd go and a lot of people are SREs that came out of the sysadmin world and still think in that mode, where it's like, “Well, I set up the systems, and when things break, I go and I fix them.” And, “Why did the developers keep writing crappy code? Why do I have to always getting up in the middle of the night because this thing crashed?”And it turns out that the work we need to do to make things more reliable, there's a ceiling to how far away the platform can take us, right? Like, we can have the best platform in the world with redundancy, and, you know, nine-way replicated data storage and all this crazy stuff, and still if we put crappy software on top, it's going to be unreliable. So, how do we make less crappy software? And for most of my career, people would be, like, “Well, you should test it.” And so, we started doing that, and we still have crappy software, so what's going on here? We still have incidents.So, we write more tests, and we still have incidents. We had a QA group, we still have incidents. We send the developers to training, and we still have incidents. So like, what is the thing we need to do to make things more reliable? And it turns out, most of it is culture work.Corey: My perspective on this stems from being a grumpy old sysadmin. And at some point, I started calling myself a systems engineer or DevOps or production engineer, or SRE. It was all from my point of view, the same job, but you know, if you call yourself a sysadmin, you're just asking for a 40% pay cut off the top.Amy: [laugh].Corey: But I still tended to view the world through that lens. I tended to be very good at Linux systems internals, for example, understanding system calls and the rest, but increasingly, as the DevOps wave or SRE wave, or Google-isation of the internet wound up being more and more of a thing, I found myself increasingly in job interviews, where, “Great, now, can you go wind up implementing a sorting algorithm on the whiteboard?” “What on earth? No.” Like, my lingua franca is shitty Bash, and no one tends to write that without a bunch of tab completions and quick checking with manpages—die.net or whatnot—on the fly as you go down that path.And it was awful, and I felt… like my skill set was increasingly eroding. And it wasn't honestly until I started this place where I really got into writing a fair bit of code to do different things because it felt like an orthogonal skill set, but the fullness of time, it seems like it's not. And it's a reskilling. And it made me wonder, does this mean that the areas of technology that I focused on early in my career, was that all a waste? And the answer is not really. Sometimes, sure, in that I don't spend nearly as much time worrying about inodes—for example—as I once did. But every once in a while, I'll run into something and I looked like a wizard from the future, but instead, I'm a wizard from the past.Amy: Yeah, I find that a lot in my work, now. Sometimes things I did 20 years ago, come back, and it's like, oh, yeah, I remember I did all that threading work in 2002 in Perl, and I learned everything the very, very, very hard way. And then, you know, this January, did some threading work to fix some stability issues, and all of it came flooding back, right? Just that the experiences really, more than the code or the learning or the text and stuff; more just the, like, this feels like threads [BLEEP]-ery. Is a diagnostic thing that sometimes we have to say.And then people are like, “Can you prove it?” And I'm like, “Not really,” because it's literally thread [BLEEP]-ery. Like, the definition of it is that there's weird stuff happening that we can't figure out why it's happening. There's something acting in the system that isn't synchronized, that isn't connected to other things, that's happening out of order from what we expect, and if we had a clear signal, we would just fix it, but we don't. We just have, like, weird stuff happening over here and then over there and over there and over there.And, like, that tells me there's just something happening at that layer and then have to go and dig into that right, and like, just basically charge through. My colleagues are like, “Well, maybe you should look at this, and go look at the database,” the things that they're used to looking at and that their experiences inform, whereas then I bring that ancient toiling through the threading mines experiences back and go, “Oh, yeah. So, let's go find where this is happening, where people are doing dangerous things with threads, and see if we can spot something.” But that came from that experience.Corey: And there's so much that just repeats itself. And history rhymes. The challenge is that, do you have 20 years of experience, or do you have one year of experience repeated 20 times? And as the tide rises, doing the same task by hand, it really is just a matter of time before your full-time job winds up being something a piece of software does. An easy example is, “Oh, what's your job?” “I manually place containers onto specific hosts.” “Well, I've got news for you, and you're not going to like it at all.”Amy: Yeah, yeah. I think that we share a little bit. I'm allergic to repeated work. I don't know if allergic is the right word, but you know, if I sit and I do something once, fine. Like, I'll just crank it out, you know, it's this form, or it's a datafile I got to write and I'll—fine I'll type it in and do the manual labor.The second time, the difficulty goes up by ten, right? Like, just mentally, just to do it, be like, I've already done this once. Doing it again is anathema to everything that I am. And then sometimes I'll get through it, but after that, like, writing a program is so much easier because it's like exponential, almost, growth in difficulty. You know, the third time I have to do the same thing that's like just typing the same stuff—like, look over here, read this thing and type it over here—I'm out; I can't do it. You know, I got to find a way to automate. And I don't know, maybe normal people aren't driven to live this way, but it's kept me from getting stuck in those spots, too.Corey: It was weird because I spent a lot of time as a consultant going from place to place and it led to some weird changes. For example, “Oh, thank God, I don't have to think about that whole messaging queue thing.” Sure enough, next engagement, it's message queue time. Fantastic. I found that repeating myself drove me nuts, but you also have to be very sensitive not to wind up, you know, stealing IP from the people that you're working with.Amy: Right.Corey: But what I loved about the sysadmin side of the world is that the vast majority of stuff that I've taken with me, lives in my shell config. And what I mean by that is I'm not—there's nothing in there is proprietary, but when you have a weird problem with trying to figure out the best way to figure out which Ruby process is stealing all the CPU, great, turns out that you can chain seven or eight different shell commands together through a bunch of pipes. I don't want to remember that forever. So, that's the sort of thing I would wind up committing as I learned it. I don't remember what company I picked that up at, but it was one of those things that was super helpful.I have a sarcastic—it's a one-liner, except no sane editor setting is going to show it in any less than three—of a whole bunch of Perl, piped into du, piped into the rest, that tells you one of the largest consumers of files in a given part of the system. And it rates them with stars and it winds up doing some neat stuff. I would never sit down and reinvent something like that today, but the fact that it's there means that I can do all kinds of neat tricks when I need to. It's making sure that as you move through your career, on some level, you're picking up skills that are repeatable and applicable beyond one company.Amy: Skills and tooling—Corey: Yeah.Amy: —right? Like, you just described the tool. Another SREcon talk was John Allspaw and Dr. Richard Cook talking about above the line; below the line. And they started with these metaphors about tools, right, showing all the different kinds of hammers.And if you're a blacksmith, a lot of times you craft specialized hammers for very specific jobs. And that's one of the properties of a tool that they were trying to get people to think about, right, is that tools get crafted to the job. And what you just described as a bespoke tool that you had created on the fly, that kind of floated under the radar of intellectual property. [laugh].So, let's not tell the security or IP people right? Like, because there's probably billions and billions of dollars of technically, like, made-up IP value—I'm doing air quotes with my fingers—you know, that's just basically people's shell profiles. And my God, the Emacs automation that people have done. If you've ever really seen somebody who's amazing at Emacs and is 10, 20, 30, maybe 40 years of experience encoded in their emacs settings, it's a wonder to behold. Like, I look at it and I go, “Man, I wish I could do that.”It's like listening to a really great guitar player and be like, “Wow, I wish I could play like them.” You see them just flying through stuff. But all that IP in there is both that person's collection of wisdom and experience and working with that code, but also encodes that stuff like you described, right? It's just all these little systems tricks and little fiddly commands and things we don't want to remember and so we encode them into our toolset.Corey: Oh, yeah. Anything I wound up taking, I always would share it with people internally, too. I'd mention, “Yeah, I'm keeping this in my shell files.” Because I disclosed it, which solves a lot of the problem. And also, none of it was even close to proprietary or anything like that. I'm sorry, but the way that you wind up figuring out how much of a disk is being eaten up and where in a more pleasing way, is not a competitive advantage. It just isn't.Amy: It isn't to you or me, but, you know, back in the beginning of our careers, people thought it was worth money and should be proprietary. You know, like, oh, that disk-checking script as a competitive advantage for our company because there are only a few of us doing this work. Like, it was actually being able to, like, manage your—[laugh] actually manage your servers was a competitive advantage. Now, it's kind of commodity.Corey: Let's also be clear that the world has moved on. I wound up buying a DaisyDisk a while back for Mac, which I love. It is a fantastic, pretty effective, “Where's all the stuff on your disk going?” And it does a scan and you can drive and collect things and delete them when trying to clean things out. I was using it the other day, so it's top of mind at the moment.But it's way more polished than that crappy Perl three-liner. And I see both sides, truly I do. The trick also, for those wondering [unintelligible 00:15:45], like, “Where is the line?” It's super easy. Disclose it, what you're doing, in those scenarios in the event someone is no because they believe that finding the right man page section for something is somehow proprietary.Great. When you go home that evening in a completely separate environment, build it yourself from scratch to solve the problem, reimplement it and save that. And you're done. There are lots of ways to do this. Don't steal from your employer, but your employer employs you; they don't own you and the way that you think about these problems.Every person I've met who has had a career that's longer than 20 minutes has a giant doc somewhere on some system of all of the scripts that they wound up putting together, all of the one-liners, the notes on, “Next time you see this, this is the thing to check.”Amy: Yeah, the cheat sheet or the notebook with all the little commands, or again the Emacs config, sometimes for some people, or shell profiles. Yeah.Corey: Here's the awk one-liner that I put that automatically spits out from an Apache log file what—the httpd log file that just tells me what are the most frequent talkers, and what are the—Amy: You should probably let go of that one. You know, like, I think that one's lifetime is kind of past, Corey. Maybe you—Corey: I just have to get it working with Nginx, and we're good to go.Amy: Oh, yeah, there you go. [laugh].Corey: Or S3 access logs. Perish the thought. But yeah, like, what are the five most high-volume talkers, and what are those relative to each other? Huh, that one thing seems super crappy and it's coming from Russia. But that's—hmm, one starts to wonder; maybe it's time to dig back in.So, one of the things that I have found is that a lot of the people talking about SRE seem to have descended from an ivory tower somewhere. And they're talking about how some of the best-in-class companies out there, renowned for their technical cultures—at least externally—are doing these things. But there's a lot more folks who are not there. And honestly, I consider myself one of those people who is not there. I was a competent engineer, but never a terrific one.And looking at the way this was described, I often came away thinking, “Okay, it was the purpose of this conference talk just to reinforce how smart people are, and how I'm not,” and/or, “There are the 18 cultural changes you need to make to your company, and then you can do something kind of like we were just talking about on stage.” It feels like there's a combination of problems here. One is making this stuff more accessible to folks who are not themselves in those environments, and two, how to drive cultural change as an individual contributor if that's even possible. And I'm going to go out on a limb and guess you have thoughts on both aspects of that, and probably some more hit me, please.Amy: So, the ivory tower, right. Let's just be straight up, like, the ivory tower is Google. I mean, that's where it started. And we get it from the other large companies that, you know, want to do conference talks about what this stuff means and what it does. What I've kind of come around to in the last couple of years is that those talks don't really reach the vast majority of engineers, they don't really apply to a large swath of the enterprise especially, which is, like, where a lot of the—the bulk of our industry sits, right? We spend a lot of time talking about the darlings out here on the West Coast in high tech culture and startups and so on.But, like, we were talking about before we started the show, right, like, the interior of even just America, is filled with all these, like, insurance and banks and all of these companies that are cranking out tons of code and servers and stuff, and they're trying to figure out the same problems. But they're structured in companies where their tech arm is still, in most cases, considered a cost center, often is bundled under finance, for—that's a whole show of itself about that historical blunder. And so, the tech culture is tend to be very, very different from what we experience in—what do we call it anymore? Like, I don't even want to say West Coast anymore because we've gone remote, but, like, high tech culture we'll say. And so, like, thinking about how to make SRE and all this stuff more accessible comes down to, like, thinking about who those engineers are that are sitting at the computers, writing all the code that runs our banks, all the code that makes sure that—I'm trying to think of examples that are more enterprise-y right?Or shoot buying clothes online. You go to Macy's for example. They have a whole bunch of servers that run their online store and stuff. They have internal IT-ish people who keep all this stuff running and write that code and probably integrating open-source stuff much like we all do. But when you go to try to put in a reliability program that's based on the current SRE models, like SLOs; you put in SLOs and you start doing, like, this incident management program that's, like, you know, you have a form you fill out after every incident, and then you [unintelligible 00:20:25] retros.And it turns out that those things are very high-level skills, skills and capabilities in an organization. And so, when you have this kind of IT mindset or the enterprise mindset, bringing the culture together to make those things work often doesn't happen. Because, you know, they'll go with the prescriptive model and say, like, okay, we're going to implement SLOs, we're going to start measuring SLIs on all of the services, and we're going to hold you accountable for meeting those targets. If you just do that, right, you're just doing more gatekeeping and policing of your tech environment. My bet is, reliability almost never improves in those cases.And that's been my experience, too, and why I get charged up about this is, if you just go slam in these practices, people end up miserable, the practices then become tarnished because people experienced the worst version of them. And then—Corey: And with the remote explosion as well, it turns out that changing jobs basically means their company sends you a different Mac, and the next Monday, you wind up signing into a different Slack team.Amy: Yeah, so the culture really matters, right? You can't cover it over with foosball tables and great lunch. You actually have to deliver tools that developers want to use and you have to deliver a software engineering culture that brings out the best in developers instead of demanding the best from developers. I think that's a fundamental business shift that's kind of happening. If I'm putting on my wizard hat and looking into the future and dreaming about what might change in the world, right, is that there's kind of a change in how we do leadership and how we do business that's shifting more towards that model where we look at what people are capable of and we trust in our people, and we get more out of them, the knowledge work model.If we want more knowledge work, we need people to be happy and to feel engaged in their community. And suddenly we start to see these kind of generational, bigger-pie kind of things start to happen. But how do we get there? It's not SLOs. It maybe it's a little bit starting with incidents. That's where I've had the most success, and you asked me about that. So, getting practical, incident management is probably—Corey: Right. Well, as I see it, the problem with SLOs across the board is it feels like it's a very insular community so far, and communicating it to engineers seems to be the focus of where the community has been, but from my understanding of it, you absolutely need buy-in at significantly high executive levels, to at the very least by you air cover while you're doing these things and making these changes, but also to help drive that cultural shift. None of this is something I have the slightest clue how to do, let's be very clear. If I knew how to change a company's culture, I'd have a different job.Amy: Yeah. [laugh]. The biggest omission in the Google SRE books was [Ers 00:22:58]. There was a guy at Google named Ers who owns availability for Google, and when anything is, like, in dispute and bubbles up the management team, it goes to Ers, and he says, “Thou shalt…” right? Makes the call. And that's why it works, right?Like, it's not just that one person, but that system of management where the whole leadership team—there's a large, very well-funded team with a lot of power in the organization that can drive availability, and they can say, this is how you're going to do metrics for your service, and this is the system that you're in. And it's kind of, yeah, sure it works for them because they have all the organizational support in place. What I was saying to my team just the other day—because we're in the middle of our SLO rollout—is that really, I think an SLO program isn't [clear throat] about the engineers at all until late in the game. At the beginning of the game, it's really about getting the leadership team on board to say, “Hey, we want to put in SLIs and SLOs to start to understand the functioning of our software system.” But if they don't have that curiosity in the first place, that desire to understand how well their teams are doing, how healthy their teams are, don't do it. It's not going to work. It's just going to make everyone miserable.Corey: It feels like it's one of those difficult to sell problems as well, in that it requires some tooling changes, absolutely. It requires cultural change and buy-in and whatnot, but in order for that to happen, there has to be a painful problem that a company recognizes and is willing to pay to make go away. The problem with stuff like this is that once you pay, there's a lot of extra work that goes on top of it as well, that does not have a perception—rightly or wrongly—of contributing to feature velocity, of hitting the next milestone. It's, “Really? So, we're going to be spending how much money to make engineers happier? They should get paid an awful lot and they're still complaining and never seem happy. Why do I care if they're happy other than the pure mercenary perspective of otherwise they'll quit?” I'm not saying that it's not worth pursuing; it's not a worthy goal. I am saying that it becomes a very difficult thing to wind up selling as a product.Amy: Well, as a product for sure, right? Because—[sigh] gosh, I have friends in the space who work on these tools. And I want to be careful.Corey: Of course. Nothing but love for all of those people, let's be very clear.Amy: But a lot of them, you know, they're pulling metrics from existing monitoring systems, they are doing some interesting math on them, but what you get at the end is a nice service catalog and dashboard, which are things we've been trying to land as products in this industry for as long as I can remember, and—Corey: “We've got it this time, though. This time we'll crack the nut.” Yeah. Get off the island, Gilligan.Amy: And then the other, like, risky thing, right, is the other part that makes me uncomfortable about SLOs, and why I will often tell folks that I talk to out in the industry that are asking me about this, like, one-on-one, “Should I do it here?” And it's like, you can bring the tool in, and if you have a management team that's just looking to have metrics to drive productivity, instead of you know, trying to drive better knowledge work, what you get is just a fancier version of more Taylorism, right, which is basically scientific management, this idea that we can, like, drive workers to maximum efficiency by measuring random things about them and driving those numbers. It turns out, that doesn't really work very well, even in industrial scale, it just happened to work because, you know, we have a bloody enough society that we pushed people into it. But the reality is, if you implement SLOs badly, you get more really bad Taylorism that's bad for you developers. And my suspicion is that you will get worse availability out of it than you would if you just didn't do it at all.Corey: This episode is sponsored by our friends at Revelo. Revelo is the Spanish word of the day, and its spelled R-E-V-E-L-O. It means “I reveal.” Now, have you tried to hire an engineer lately? I assure you it is significantly harder than it sounds. One of the things that Revelo has recognized is something I've been talking about for a while, specifically that while talent is evenly distributed, opportunity is absolutely not. They're exposing a new talent pool to, basically, those of us without a presence in Latin America via their platform. It's the largest tech talent marketplace in Latin America with over a million engineers in their network, which includes—but isn't limited to—talent in Mexico, Costa Rica, Brazil, and Argentina. Now, not only do they wind up spreading all of their talent on English ability, as well as you know, their engineering skills, but they go significantly beyond that. Some of the folks on their platform are hands down the most talented engineers that I've ever spoken to. Let's also not forget that Latin America has high time zone overlap with what we have here in the United States, so you can hire full-time remote engineers who share most of the workday as your team. It's an end-to-end talent service, so you can find and hire engineers in Central and South America without having to worry about, frankly, the colossal pain of cross-border payroll and benefits and compliance because Revelo handles all of it. If you're hiring engineers, check out revelo.io/screaming to get 20% off your first three months. That's R-E-V-E-L-O dot I-O slash screaming.Corey: That is part of the problem is, in some cases, to drive some of these improvements, you have to go backwards to move forwards. And it's one of those, “Great, so we spent all this effort and money in the rest of now things are worse?” No, not necessarily, but suddenly are aware of things that were slipping through the cracks previously.Amy: Yeah. Yeah.Corey: Like, the most realistic thing about first The Phoenix Project and then The Unicorn Project, both by Gene Kim, has been the fact that companies have these problems and actively cared enough to change it. In my experience, that feels a little on the rare side.Amy: Yeah, and I think that's actually the key, right? It's for the culture change, and for, like, if you really looking to be, like, do I want to work at this company? Am I investing my myself in here? Is look at the leadership team and be, like, do these people actually give a crap? Are they looking just to punt another number down the road?That's the real question, right? Like, the technology and stuff, at the point where I'm at in my career, I just don't care that much anymore. [laugh]. Just… fine, use Kubernetes, use Postgres, [unintelligible 00:27:30], I don't care. I just don't. Like, Oracle, I might have to ask, you know, go to finance and be like, “Hey, can we spend 20 million for a database?” But like, nobody really asks for that anymore, so. [laugh].Corey: As one does. I will say that I mostly agree with you, but a technology that I found myself getting excited about, given the time of the recording on this is… fun, I spent a bit of time yesterday—from when we're recording this—teaching myself just enough Go to wind up being together a binary that I needed to do something actively ridiculous for my camera here. And I found myself coming away deeply impressed by a lot of things about it, how prescriptive it was for one, how self-contained for another. And after spending far too many years of my life writing shitty Perl, and shitty Bash, and worse Python, et cetera, et cetera, the prescriptiveness was great. The fact that it wound up giving me something I could just run, I could cross-compile for anything I need to run it on, and it just worked. It's been a while since I found a technology that got me this interested in exploring further.Amy: Go is great for that. You mentioned one of my two favorite features of Go. One is usually when a program compiles—at least the way I code in Go—it usually works. I've been working with Go since about 0.9, like, just a little bit before it was released as 1.0, and that's what I've noticed over the years of working with it is that most of the time, if you have a pretty good data structure design and you get the code to compile, usually it's going to work, unless you're doing weird stuff.The other thing I really love about Go and that maybe you'll discover over time is the malleability of it. And the reason why I think about that more than probably most folks is that I work on other people's code most of the time. And maybe this is something that you probably run into with your business, too, right, where you're working on other people's infrastructure. And the way that we encode business rules and things in the languages, in our programming language or our config syntax and stuff has a huge impact on folks like us and how quickly we can come into a situation, assess, figure out what's going on, figure out where things are laid out, and start making changes with confidence.Corey: Forget other people for a minute they're looking at what I built out three or four years ago here, myself, like, I look at past me, it's like, “What was that rat bastard thinking? This is awful.” And it's—forget other people's code; hell is your own code, on some level, too, once it's slipped out of the mental stack and you have to re-explore it and, “Oh, well thank God I defensively wound up not including any comments whatsoever explaining what the living hell this thing was.” It's terrible. But you're right, the other people's shell scripts are finicky and odd.I started poking around for help when I got stuck on something, by looking at GitHub, and a few bit of searching here and there. Even these large, complex, well-used projects started making sense to me in a way that I very rarely find. It's, “What the hell is that thing?” is my most common refrain when I'm looking at other people's code, and Go for whatever reason avoids that, I think because it is so prescriptive about formatting, about how things should be done, about the vision that it has. Maybe I'm romanticizing it and I'll hate it and a week from now, and I want to go back and remove this recording, but.Amy: The size of the language helps a lot.Corey: Yeah.Amy: But probably my favorite. It's more of a convention, which actually funny the way I'm going to talk about this because the two languages I work on the most right now are Ruby and Go. And I don't feel like two languages could really be more different.Syntax-wise, they share some things, but really, like, the mental models are so very, very different. Ruby is all the way in on object-oriented programming, and, like, the actual real kind of object-oriented with messaging and stuff, and, like, the whole language kind of springs from that. And it kind of requires you to understand all of these concepts very deeply to be effective in large programs. So, what I find is, when I approach Ruby codebase, I have to load all this crap into my head and remember, “Okay, so yeah, there's this convention, when you do this kind of thing in Ruby”—or especially Ruby on Rails is even worse because they go deep into convention over configuration. But what that's code for is, this code is accessible to people who have a lot of free cognitive capacity to load all this convention into their heads and keep it in their heads so that the code looks pretty, right?And so, that's the trade-off as you said, okay, my developers have to be these people with all these spare brain cycles to understand, like, why I would put the code here in this place versus this place? And all these, like, things that are in the code, like, very compact, dense concepts. And then you go to something like Go, which is, like, “Nah, we're not going to do Lambdas. Nah”—[laugh]—“We're not doing all this fancy stuff.” So, everything is there on the page.This drives some people crazy, right, is that there's all this boilerplate, boilerplate, boilerplate. But the reality is, I can read most Go files from top to the bottom and understand what the hell it's doing, whereas I can go sometimes look at, like, a Ruby thing, or sometimes Python and e—Perl is just [unintelligible 00:32:19] all the time, right, it's there's so much indirection. And it just be, like, “What the [BLEEP] is going on? This is so dense. I'm going to have to sit down and write it out in longhand so I can understand what the developer was even doing here.” And—Corey: Well, that's why I got the Mac Studio; for when I'm not doing A/V stuff with it, that means that I'll have one core that I can use for, you know, front-end processing and the rest, and the other 19 cores can be put to work failing to build Nokogiri in Ruby yet again.Amy: [laugh].Corey: I remember the travails of working with Ruby, and the problem—I have similar problems with Python, specifically in that—I don't know if I'm special like this—it feels like it's a SRE DevOps style of working, but I am grabbing random crap off a GitHub constantly and running it, like, small scripts other people have built. And let's be clear, I run them on my test AWS account that has nothing important because I'm not a fool that I read most of it before I run it, but I also—it wants a different version of Python every single time. It wants a whole bunch of other things, too. And okay, so I use ASDF as my version manager for these things, which for whatever reason, does not work for the way that I think about this ergonomically. Okay, great.And I wind up with detritus scattered throughout my system. It's, “Hey, can you make this reproducible on my machine?” “Almost certainly not, but thank you for asking.” It's like ‘Step 17: Master the Wolf' level of instructions.Amy: And I think Docker generally… papers over the worst of it, right, is when we built all this stuff in the aughts, you know, [CPAN 00:33:45]—Corey: Dev containers and VS Code are very nice.Amy: Yeah, yeah. You know, like, we had CPAN back in the day, I was doing chroots, I think in, like, '04 or '05, you know, to solve this problem, right, which is basically I just—screw it; I will compile an entire distro into a directory with a Perl and all of its dependencies so that I can isolate it from the other things I want to run on this machine and not screw up and not have these interactions. And I think that's kind of what you're talking about is, like, the old model, when we deployed servers, there was one of us sitting there and then we'd log into the server and be like, I'm going to install the Perl. You know, I'll compile it into, like, [/app/perl 558 00:34:21] whatever, and then I'll CPAN all this stuff in, and I'll give it over to the developer, tell them to set their shebang to that and everything just works. And now we're in a mode where it's like, okay, you got to set up a thousand of those. “Okay, well, I'll make a tarball.” [laugh]. But it's still like we had to just—Corey: DevOps, but [unintelligible 00:34:37] dev closer to ops. You're interrelating all the time. Yeah, then Docker comes along, and add dev is, like, “Well, here's the container. Good luck, asshole.” And it feels like it's been cast into your yard to worry about.Amy: Yeah, well, I mean, that's just kind of business, or just—Corey: Yeah. Yeah.Amy: I'm not sure if it's business or capitalism or something like that, but just the idea that, you know, if I can hand off the shitty work to some other poor schlub, why wouldn't I? I mean, that's most folks, right? Like, just be like, “Well”—Corey: Which is fair.Amy: —“I got it working. Like, my part is done, I did what I was supposed to do.” And now there's a lot of folks out there, that's how they work, right? “I hit done. I'm done. I shipped it. Sure. It's an old [unintelligible 00:35:16] Ubuntu. Sure, there's a bunch of shell scripts that rip through things. Sure”—you know, like, I've worked on repos where there's hundreds of things that need to be addressed.Corey: And passing to someone else is fine. I'm thrilled to do it. Where I run into problems with it is where people assume that well, my part was the hard part and anything you schlubs do is easy. I don't—Amy: Well, that's the underclass. Yeah. That's—Corey: Forget engineering for a second; I throw things to the people over in the finance group here at The Duckbill Group because those people are wizards at solving for this thing. And it's—Amy: Well, that's how we want to do things.Corey: Yeah, specialization works.Amy: But we have this—it's probably more cultural. I don't want to pick, like, capitalism to beat on because this is really, like, human cultural thing, and it's not even really particularly Western. Is the idea that, like, “If I have an underclass, why would I give a shit what their experience is?” And this is why I say, like, ops teams, like, get out of here because most ops teams, the extant ops teams are still called ops, and a lot of them have been renamed SRE—but they still do the same job—are an underclass. And I don't mean that those people are below us. People are treated as an underclass, and they shouldn't be. Absolutely not.Corey: Yes.Amy: Because the idea is that, like, well, I'm a fancy person who writes code at my ivory tower, and then it all flows down, and those people, just faceless people, do the deployment stuff that's beneath me. That attitude is the most toxic thing, I think, in tech orgs to address. Like, if you're trying to be like, “Well, our liability is bad, we have security problems, people won't fix their code.” And go look around and you will find people that are treated as an underclass that are given codes thrown over the wall at them and then they just have to toil through and make it work. I've worked on that a number of times in my career.And I think just like saying, underclass, right, or caste system, is what I found is the most effective way to get people actually thinking about what the hell is going on here. Because most people are just, like, “Well, that's just the way things are. It's just how we've always done it. The developers write to code, then give it to the sysadmins. The sysadmins deploy the code. Isn't that how it always works?”Corey: You'd really like to hope, wouldn't you?Amy: [laugh]. Not me. [laugh].Corey: Again, the way I see it is, in theory—in theory—sysadmins, ops, or that should not exist. People should theoretically be able to write code as developers that just works, the end. And write it correct the first time and never have to change it again. Yeah. There's a reason that I always like to call staging environments in places I work ‘theory' because it works in theory, but not in production, and that is fundamentally the—like, that entire job role is the difference between theory and practice.Amy: Yeah, yeah. Well, I think that's the problem with it. We're already so disconnected from the physical world, right? Like, you and I right now are talking over multiple strands of glass and digital transcodings and things right now, right? Like, we are detached from the physical reality.You mentioned earlier working in data centers, right? The thing I miss about it is, like, the physicality of it. Like, actually, like, I held a server in my arms and put it in the rack and slid it into the rails. I plugged into power myself; I pushed the power button myself. There's a server there. I physically touched it.Developers who don't work in production, we talked about empathy and stuff, but really, I think the big problem is when they work out in their idea space and just writing code, they write the unit tests, if we're very lucky, they'll write a functional test, and then they hand that wad off to some poor ops group. They're detached from the reality of operations. It's not even about accountability; it's about experience. The ability to see all of the weird crap we deal with, right? You know, like, “Well, we pushed the code to that server, but there were three bit flips, so we had to do it again. And then the other server, the disk failed. And on the other server…” You know? [laugh].It's just, there's all this weird crap that happens, these systems are so complex that they're always doing something weird. And if you're a developer that just spends all day in your IDE, you don't get to see that. And I can't really be mad at those folks, as individuals, for not understanding our world. I figure out how to help them, and the best thing we've come up with so far is, like, well, we start giving this—some responsibility in a production environment so that they can learn that. People do that, again, is another one that can be done wrong, where it turns into kind of a forced empathy.I actually really hate that mode, where it's like, “We're forcing all the developers online whether they like it or not. On-call whether they like it or not because they have to learn this.” And it's like, you know, maybe slow your roll a little buddy because the stuff is actually hard to learn. Again, minimizing how hard ops work is. “Oh, we'll just put the developers on it. They'll figure it out, right? They're software engineers. They're probably smarter than you sysadmins.” Is the unstated thing when we do that, right? When we throw them in the pit and be like, “Yeah, they'll get it.” [laugh].Corey: And that was my problem [unintelligible 00:39:49] the interview stuff. It was in the write code on a whiteboard. It's, “Look, I understood how the system fundamentally worked under the hood.” Being able to power my way through to get to an outcome even in language I don't know, was sort of part and parcel of the job. But this idea of doing it in artificially constrained environment, in a language I'm not super familiar with, off the top of my head, it took me years to get to a point of being able to do it with a Bash script because who ever starts with an empty editor and starts getting to work in a lot of these scenarios? Especially in an ops role where we're not building something from scratch.Amy: That's the interesting thing, right? In the majority of tech work today—maybe 20 years ago, we did it more because we were literally building the internet we have today. But today, most of the engineers out there working—most of us working stiffs—are working on stuff that already exists. We're making small incremental changes, which is great that's what we're doing. And we're dealing with old code.Corey: We're gluing APIs together, and that's fine. Ugh. I really want to thank you for taking so much time to talk to me about how you see all these things. If people want to learn more about what you're up to, where's the best place to find you?Amy: I'm on Twitter every once in a while as @MissAmyTobey, M-I-S-S-A-M-Y-T-O-B-E-Y. I have a blog I don't write on enough. And there's a couple things on the Equinix Metal blog that I've written, so if you're looking for that. Otherwise, mainly Twitter.Corey: And those links will of course be in the [show notes 00:41:08]. Thank you so much for your time. I appreciate it.Amy: I had fun. Thank you.Corey: As did I. Amy Tobey, Senior Principal Engineer at Equinix. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, or on the YouTubes, smash the like and subscribe buttons, as the kids say. Whereas if you've hated this episode, same thing, five-star review all the platforms, smash the buttons, but also include an angry comment telling me that you're about to wind up subpoenaing a copy of my shell script because you're convinced that your intellectual property and secrets are buried within.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.
Peter and Aram discuss the reports that the Reds may be listening on Luis Castillo and Tyler Mahle, the Cardinals' somewhat surprising move to demote Paul DeJong, the hottest/coldest starts to the MiLB season, and the impact of Carlos Correa and Chris Paddack's injury. Sports Cards Available 24/7 on Loupe Join our Baseball Group Chat on Chalkboard Get Your Just Baseball Merch! Check out our website: https://www.justbaseball.com/ Personal Twitters: @peterappel23, @jack_mcmullen11, @aramleighton8 Learn more about your ad choices. Visit megaphone.fm/adchoices
A family prepared to say goodbye as doctors went to remove life support from their sick baby boy. But miracle baby Karson Jax Hough defied everyone's expectations as he started breathing on his own!ANDA missing infant found safe in a field in Louisiana was the cause of a lot of celebration.To see videos and photos referenced in this episode, visit GodUpdates!https://www.godupdates.com/remove-life-support-miracle-baby-karson-jax/https://www.godupdates.com/missing-infant-found-niguel-jackson/
Steve and Kristen chat about Gavin Newsom's Gubernatorial launch which sounds more like a Presidential launch and how he may have stepped in it. Then Steve welcomes Lance Christensen, Candidate for Superintendent of Public Instruction.
(00:00-22:50) – Monday's show opens with Dan talking about how fans usually react positively when a new player initially comes into town, just like the Colts have at QB the last few years and the Washington Commanders are right now with Carson Wentz. Plus, Dan talks about the intrigue of Matt Ryan under center this fall and looks at the leadership present in the Colts' locker room. (22:51-36:00) – We're back from break with some phone calls on what motivates athletes and why relationships shouldn't matter. Also, more on the Carson Wentz failed experiment in Indy. (36:01-44:35) – The first hour ends with Dan sharing with us what he did yesterday with some time to kill in Chicago. (44:36-1:09:09) – Our pal Sean Salisbury joins the show to weigh in on the Colts continued shots at Carson Wentz after the fact. Plus, Sean gives us his thoughts on fan bases being so desperate to love the new quarterback that gets acquired during the offseason. Also, Dan asks Sean about the future of Baker Mayfield in the NFL. (1:09:10-1:21:46) –This segment we look back at the 2022 Kentucky Derby and the incredible upset from Rich Strike. (1:21:47-1:30:03) – Hour number two closes with Dan lamenting the death of former Michigan State star Adreian Payne who died today at the age of 31. Plus, more on the Colts and the Frank Reich-Chris Ballard regime. (1:30:04-1:58:00) – The great Mike Tirico of NBC Sports joins the program to recap one of the most shocking Kentucky Derby in the 148 installments of the race, when 80-1 longshot Rich Strike stunned the world. (1:58:01-2:06:53) – We're back from break with Dan interacting with the YouTube Chat and sharing who he likes between the Celtics and the Bucks. (2:06:54-2:13:43)– Monday's show ends with Dan sharing the results from the Horseshoe Indianapolis Race of the Day. Also, Dan asks show producer Jimmy Cook for today's edition of The JCook Plays of the Day. Plus, Dan hands out some bets he likes this evening. See omnystudio.com/listener for privacy information.
This week on the Mimosas with Moms Podcast, Abbey welcomes Nicole Schwarz, LMFT and Parenting Coach. Nicole joins to talk abut her new book , “It Starts With You.” Nicole talks about focusing on making space for imperfect parenting, been kind to ourselves, and parenting our kids with a grace-base perspective. She shares the importance of giving lots of space for them to be kids, to make mistakes, and to learn and grow through a healthy relationship with us. Nicole's non-judgmental and shame-free approach helps parents find calm and connection with their kids. Does it really start with us? Let's talk about it, CHEERS! ——————————————— You can find Nicole Schwarz, LMFT and Parenting Coach: IG: @imperfectfamilies Facebook: /imperfectfamilies “20 Ways to Find Calm and Connection With Your Kids”: imperfectfamilies.com/free It Starts With You by Nicole Schwarz available wherever you get your books! ——————————————— Instagram @mimosaswithmoms FB /mimosaswithmoms Email email@example.com An ABC of Families by Abbey Williams - https://www.amazon.com/ABC-Families-Abbey-Williams/dp/0711256535
Show #1459 Good morning, good afternoon and good evening wherever you are in the world, welcome to EV News Daily, you trusted source of EV information. It's Sunday 8th May, it's Martyn Lee here and I go through every EV story so you don't have to. ELECTRIC VW ID BUZZ STARTS AT 65,000 EUROS "The updated list of eligible electric vehicles published by the Federal Office of Economics and Export Control (Bafa) reveals something that VW only wanted to tell us at the start of sales: the price of the ID Buzz." "Bafa, which is responsible for promoting e-cars, gives the first ID Buzz Pro model available for sale with a net price of 54,270 euros. Plus the statutory sales tax, the Bully successor is around 64,580 euros and thus well above the 40,000 euro limit for the higher subsidy. The purchase bonus for the ID Buzz this year is still 7,500 euros, of which 2,500 euros from the manufacturer, so that customers have to spend around 57,080 euros on balance." "For the commercial offshoot, the ID Buzz Cargo, interested parties have to budget 45,740 euros net. With a premium, they come to a net purchase price of 38,240 euros. They get the sales tax back from the tax office anyway." Original Source: https://t3n.de/news/bafa-leak-vw-id-buzz-65000-1470726/ FORD THROWS SHADE AT TESLA WITH A NEW AD CELEBRATING WORKERS - It starts with a nice touch of snark. Footage is shown of a hand scrolling on a smartphone with the commentary, “Right now it could seem like the only people who matter are the loudest….” Who could they be thinking of? - Then, it continues— “Those who want to tear things down and then fly away on their personal spaceships when things get hard,” A video of a rocket taking lift off fills the screen. - The rest of the ad is dedicated to profiling the workers of Ford, profiling a culturally and gender diverse cohort of people working by their first name. The narrator says that Ford assembles more vehicles in the US than other car manufacturers, which means local jobs. - The narrator continues: “… we've got 182,000 people, and they're building.” and goes on further to conclude, “you might not know their names, but these people get up every day to move us all forward.” Original Source : https://thenextweb.com/news/ford-snarks-elon-musk-and-celebrates-their-workers HOT VOLKSWAGEN ID.3 GTX TO JOIN RANGE IN 2023 - Volkswagen has been tipped to spice up its ID.3 EV with a performance version that will become the brand's first all-electric hot hatchback. And now, we know when it'll arrive. - Speaking at the launch of the new ID.5 SUV in Austria, Volkswagen product line spokesperson Martin Hube noted that the ID.3 GTX's entry to the range will coincide with the ID.3's mid-life facelift. “Of course the project is progressing,” he said, adding, “[For the] ID.3 facelift…we will get some very interesting details and of course, we are convinced that customer's expectations for a bit more power, for all-wheel drive is there, and [the] customer's wish is what we have to fulfil.” - This means the ID.3 GTX won't be launched this year - we're not expecting a facelifted ID.3 until 2023 at the earliest. - likely that the ID.3 GTX will use the same twin-motor powertrain as the ID.4 GTX, producing 295bhp. In the smaller, lighter ID.3, the GTX will lik