Podcasts about solves

Learn more about your ad choices. Visit podcastchoices.com/adchoices

Andrew Wilson is the host of The Crucible and a frequent guest on the Whatever podcast. He sits down for a cigar and a deep dive into feminism and gender roles. We'll also talk about his debate style and his take on some of the woke pop culture coming out of Hollywood. You don't want to miss this one.Let American Financing help you regain control of your finances. Go to https://americanfinancing.net/crowder or call 1-800-974-6500. NMLS 182334, http://nmlsconsumeraccess.org/DOWNLOAD THE RUMBLE APP TODAY: https://rumble.com/our-apps Join Rumble Premium to watch this show every day! http://louderwithcrowder.com/Premium Get your favorite LWC gear: https://crowdershop.com/ Bite-Sized Content: https://rumble.com/c/CrowderBits Subscribe to my podcast: https://rss.com/podcasts/louder-with-crowder/FOLLOW ME: Website: https://louderwithcrowder.com/ Twitter: https://twitter.com/scrowder Instagram: http://www.instagram.com/louderwithcrowder Facebook: https://www.facebook.com/stevencrowderofficial Music by @Pogo

Send us a textManaging 400 Amazon accounts takes more than guesswork, it starts with a proven system. This video shows how teams stay consistent using a step-by-step strategy guide. See what drives real results and keeps client work on track across hundreds of accounts.Grab the free SEO toolkit and start improving your Amazon listings today: https://bit.ly/434zbQY#AmazonSOP #BrandManagement #ClientResults #EcommerceTeamwork #AmazonStrategyWatch these on YouTube:What's Good, Bad, & The SEO/PPC Golden Ratio: https://www.youtube.com/watch?v=9SGtB1oLJis&list=PLDkvNlz8yl_bJFHwDexEcnnEZ8f98kdZHYou're Losing Money If You Don't Know This About Amazon Targeting https://www.youtube.com/watch?v=mkyM-bDanck&list=PLDkvNlz8yl_YEKE1B5o1uhbBm1QQcPzmY----------------------------------------------Book a free strategy call to get expert advice on growing your Amazon sales: https://bit.ly/44uHuaRWant better ads on Amazon? Get the PPC guide that shows you what really works: https://bit.ly/4k4pDw3Timestamps:00:00 - The Question Agency Owners Always Ask00:07 - Who Is Kevin Sanderson & What Is My Amazon Guy00:17 - Scaling Across 400 Clients and 500 Staff00:31 - Internal Strategy Guide for New Team Members00:43 - What's in the Brand Strategist Playbook01:05 - What Critical Impact Means in Advertising01:19 - How We Train Beginners to Prioritize High-Value Tasks01:47 - Real Examples from Our Merchandising SOP02:12 - Final Advice on Delivering ROI for Clients02:24 - Where to Get the Playbook02:45 - Best ROI Comes From the Right Focus02:55 - Final Thoughts from Kevin----------------------------------------------Follow us:LinkedIn: https://www.linkedin.com/company/28605816/Instagram: https://www.instagram.com/stevenpopemag/Pinterest: https://www.pinterest.com/myamazonguys/Twitter: https://twitter.com/myamazonguySubscribe to the My Amazon Guy podcast: https://podcast.myamazonguy.comApple Podcast: https://podcasts.apple.com/us/podcast/my-amazon-guy/id1501974229Spotify: https://open.spotify.com/show/4A5ASHGGfr6s4wWNQIqyVwSupport the show

What happens when a CFO with a knack for numbers and a passion for people builds an offshore HR powerhouse from scratch—and grows it to 500 employees without a single cold call? In this episode of Sharkpreneur, Seth Greene speaks with John Sansoucie, founder of CogNet, an offshore HR powerhouse that now boasts over 500 employees and a place on the Inc. 5000 list. John reveals how he assists HR firms in scaling quickly by discreetly managing payroll, benefits, taxes, and accounting behind the scenes—often reducing costs by more than half. Find out how he transformed a labor crisis into a competitive advantage and why some of the industry's leading players now rely on his extended office model. Key Takeaways: → How a turnaround crisis led to a global HR empire. → Why one bold leap during COVID changed everything for CogNet. → The hidden cost most companies ignore when trying to scale. → What it takes to build a 500-person offshore team from scratch. → Why the “extended office” mindset is rewriting the rules of outsourcing.   John Sansoucie launched CogNet in 2004 after waking up in India with a bold vision, backed by 27 years of experience in TPA, HRO, and PEO. He has built and managed multiple global service operations and held senior executive roles at top HR outsourcing firms, including CFO at US Personnel and VP at Advantec. John holds a Finance degree from the University of Missouri and an MBA from the University of South Florida. Connect With John: CogNet Facebook LinkedIn   Learn more about your ad choices. Visit megaphone.fm/adchoices

In this episode of the HVAC Know It All Podcast, host Gary McCreadie talks with Tom Lorenz the Director of Product Management at Copeland and Emerson, Randy Ruiz, the chief engineer at Emersion, and Ben Reed who is the principal of Teal Maker and Technical Marketing Specialist at HVAC Know it All and measureQuick, about a new wireless HVAC tool called the Equipment Interface Module (EIM). Tom explains how it helps fix wiring problems without needing to pull new wires, making upgrades easier. Randy shares how the team built and tested the EIM to make sure it is strong and reliable. Ben adds that wireless tech is getting better and saves time and money. They also discuss how the EIM works with the Sensi Touch 2 thermostat for full system control. Tom Lorenz, Randy Ruiz, and Ben Reed talk about a new wireless tool that helps HVAC systems work without extra wiring. Tom explains how the Equipment Interface Module (EIM) makes upgrades easier, even when wires are missing or broken. Randy shares how they built and tested the product to be tough and reliable. Ben talks about why wireless tech saves time and money and is now ready for real-world use. They also explain how the EIM works with the Sensi Touch 2 thermostat to fully control heating, cooling, and air quality. Here, Tom Lorenz, Randy Ruiz, and Ben Reed talk about a new wireless HVAC tool called the Equipment Interface Module (EIM). They explain how it helps fix wiring problems without pulling new wires, making system upgrades faster and easier. They also share how the EIM makes setups simple by connecting wirelessly to the Sensi Touch 2 thermostat. The guests clear up any confusion about wireless tech, showing how tough, easy, and reliable it has become for real-world HVAC jobs. Expect to Learn: How wireless tools like the EIM make HVAC upgrades faster and easier. The Sensi Touch 2 thermostat is key to full system control with wireless tech. How building reliable wireless connections saves time, money, and effort. When and why using a wireless module is better than pulling new wires. The role of strong design and testing in making wireless HVAC tools work well. Episode Highlights: [00:00] – Intro to the guests Tom, Randy, and Ben in Part 01 [00:11] – Defining the Equipment Interface Module and its HVAC use cases [01:22] – The Engineering process behind developing the EIM [02:38] – Wireless tech evolution in HVAC: Ben's IoT experience and insights [04:44] – Solving legacy HVAC challenges with wireless control solutions [05:58] – Powering the EIM and replacing 8-wire installs in retrofit scenarios [08:33] – Outdoor EIM power setup and dual-module wireless configuration [09:50] – Cost benefits of EIM vs. traditional wiring in retrofit scenarios [12:54] – Step-by-step EIM pairing with Sensi Touch 2 thermostat interface [14:26] – Key benefits of wireless vs. wired HVAC communication [17:16] – EIM support for multi-stage HVAC, humidity, and ventilation control This Episode is Kindly Sponsored by: Master: https://www.master.ca/ Cintas: https://www.cintas.com/ Supply House: https://www.supplyhouse.com/ Cool Air Products: https://www.coolairproducts.net/ Follow the Guests, Tom Lorenz, Randy Ruiz, and Ben Reed, on: Tom Lorenz: https://www.linkedin.com/in/tom-lorenz-4632338/ Copeland: https://www.linkedin.com/company/copeland/ Emerson: https://www.linkedin.com/company/emerson/ Randy Ruiz: https://www.linkedin.com/in/randy-ruiz-3b3a3ba7/ Emerson: https://www.linkedin.com/company/emerson/ Ben Reed: https://www.linkedin.com/in/ben-reed-/ Teal Maker: https://www.linkedin.com/company/tealmaker/ HVAC Know it All: https://www.linkedin.com/company/hvac-know-it-all-inc/ measureQuick: https://www.linkedin.com/company/measurequick-application/ Follow the Host: LinkedIn: https://www.linkedin.com/in/gary-mccreadie-38217a77/ Website: https://www.hvacknowitall.com Facebook: https://www.facebook.com/people/HVAC-Know-It-All-2/61569643061429/ Instagram: https://www.instagram.com/hvacknowitall1/

Rose Brady’s job running Baltimore County’s SVU was a frustrating one. The sexual violence crimes she and her team were investigating were just the tip of the iceberg. Her department was sitting on thousands of unsolved rape cases, dating back decades - with little hope of ever finding the perpetrators. That was until Rose made an incredible discovery: At a local hospital, a diligent forensic pathologist had kept in storage all the biological evidence from every rape exam he had ever performed. This could be the key to getting justice for hundreds of desperate women. This is a story of hard work, dogged persistence and a series of incredible coincidences… If you’ve been affected by sexual violence, there are organisations which can help. In the US: https://www.nsvrc.org/survivors In the UK: https://survivorsnetwork.org.uk/get-help/ We want YOUR stories for our Girlfriends hotline! Did your bestie ever bail you out of an awful date with a fake emergency phone call? Or show up on your doorstep with three weeks’ worth of lasagne when you’d just had a baby? Or sit with you in solidarity while you grieved the loss of a beloved grandparent? We want stories that are big or small, meaningful or silly. Record yours as a voice memo (under 90 seconds) and email to thegirlfriends@novel.audio. Please don’t include your own name or anyone else’s real names. The Girlfriends: Spotlight is produced by Novel for iHeartPodcasts. For more from Novel visit Novel.AudioSee omnystudio.com/listener for privacy information.

Science has solved the splash back problem and Jackson's here for it

Support our sponsors!  Smalls https://www.smalls.com/ use code: SESH SeatGeek http://seatgeek.com/  use code: SESH10 Time Stamps 00:00:13 - intro 00:08:55 - Blue Origin trip to space 00:11:55 - Katy Perry's expedition  00:15:54 - the rest of the crew 00:27:41 - BO's mission 00:35:38 - environmental impact 00:41:19 - backlash 00:49:33 - Was it a hoax? 00:55:50 - Katy Perry interviewed by Neil deGrasse Tyson 00:58:26 - Brett vs Maria updates 01:05:40 - Brett debunked photos 01:16:09 - part 12!! 01:23:41 - the REAL cotton candy pickle kit 01:39:28 - Licking cats  Mile Higher Media website:  https://milehigher.com/   Higher Hope Foundation: https://higherhope.org/  Mile Higher Merch: https://milehighermerch.com/   Submission form: https://zfrmz.com/qm6Tj6Z2RU83wcaF5BQF    hosted by: Kendall: @kendallraeonyt  IG: https://bit.ly/3gIQPjI   TikTok: https://bit.ly/3JxPJFx Janelle: @janelle_fields_ IG: https://bit.ly/2DyP1eE   TikTok: https://bit.ly/3BrWBkO    produced by: Sydney: @syd_b93  IG: https://bit.ly/3LR0zHY Karelly: @karell.y  IG: https://bit.ly/2TcxnoD Check out our other podcasts! Lights Out https://bit.ly/3n3Gaoe Mile Higher Podcast https://bit.ly/3uDwZ2Y  Planet Sleep https://linktr.ee/planetsleep Higher Love Wellness: https://extractlabs.com/milehigher PO Box Address: Kendall Rae & Josh Thomas  8547 E Arapahoe Rd Ste J # 233 Greenwood Village, CO 80112 Music By: Mile Higher Boys YT: https://bit.ly/2Q7N5QO  Spotify: https://open.spotify.com/artist/0F4ikp62qjdIV6PMO0SlaQ?si=i5v5jI77Qcq6uhjWzFix2w    Welcome to The Sesh Podcast hosted by cousins and best friends, Kendall & Janelle! Kendall is a YouTube content creator focusing on True Crime and raising awareness for missing persons cases, and Janelle is a mental health professional with a Master's in Clinical Mental Health Counseling. Our show is focused on a variety of topics, including current events, pop culture, commentary, and a little true crime. Come hang out with us every Wednesday! Creator Hosts a documentary series for educational purposes (EDSA). These include authoritative sources such as interviews, newspaper articles and TV news reporting meant to educate and memorialize notable cases in our history. Videos come with editorial context added bolstering educational and artistic value.

In this episode of Soar Financially, Clive Thompson, a retired Swiss wealth manager with 50 years of experience, reveals the real strategy behind a potential gold revaluation reset. Could the U.S. use a massive gold price reset to erase its debt?We explore the brewing battle between Trump and Powell, the Fed's next move, and why Jerome Powell's sudden exit could spark a gold and equity market boom. From Basel III and COMEX deliveries to Bretton Woods 3.0 and dollar devaluation, Clive connects the dots between central banks, debt relief, and gold manipulation.#Gold #Powell #debtcrisis

On this episode, Dr. Alex and Dr. Priya welcome Dr. Robert B. Kerstein DMD, a leading figure in digital occlusion. Dr. Kerstein shares his immense knowledge and expertise to explain how Disclusion Time Reduction (DTR) therapy and the T-Scan system, are essential in diagnosing and treating bite-related issues, including TMJ disorders, muscle pain, and even symptoms like tinnitus. Dr. Kerstein also shares some amazing images and videos to demonstrate how DTR works. This discussion will clue you into how DTR aims to control muscle activity originating from tooth contact and underscores the limitations and inaccuracies of traditional methods like articulating paper compared to the precision of digital occlusion analysis. Enjoy!*****Disclaimer*****The information in the "Unclenched" podcast is not diagnostic.The "Unclenched" Podcast and content posted by Dr. Alex and Dr. Priya is presented solely for general informational and educational for the TMJ suffers and health care professionals. The use of information on this podcast or materials linked from this podcast or website is at the user's own risk. The contents of this podcast is not intended to be a substitute for professional dental/ medical advice, diagnosis, or treatment. Users should not disregard or delay in obtaining medical/dental advice for any medical/dental condition they may have and should seek the assistance of their health care professionals for any such conditions.© All materials and information included in this podcast are protected by U.S. and international copyright laws.The materials and information in this podcast are copyrighted by us and/or by other applicable rights holders. You may download a single copy of this podcast for your own personal, noncommercial use only, provided you include all applicable notices and disclaimers. Any other use of the materials and information is strictly prohibited without our prior written permission and the permission of the applicable rights holder(s).

In this episode of the Grow and Convert Marketing Show, we discuss our journey creating an AI writing tool designed to mirror the way we produce content.Unlike existing solutions that prioritize speed over quality, our tool first deeply understands your business before generating content.After discovering that 83% of marketers use AI-assisted content despite quality concerns, we identified the fundamental problem: generic AI writing tools produce "Google research papers" that lack a company's unique voice and arguments. Our solution? A tool that analyzes your existing content to create a comprehensive "brand summary" capturing your business's value proposition, features, target customers, and pain points.The highlight of our tool is the "super brief" feature - simply input a keyword and the AI analyzes search intent, SERP patterns, and suggests content formats while providing ways to pitch your business specifically for that keyword.Key Learnings:-Most AI writing tools fail because they don't understand your business's unique positioning and arguments-83% of marketers use AI content despite quality concerns, primarily for time savings-The "brand summary" approach ensures AI truly understands your business before writing-Our tool generates strategic ideas (not just language), reversing the typical -AI writing workflow-AI writing can be high-quality and conversion-focused when it understands your business first-The "super brief" feature analyzes keywords and SERPs to suggest angles and approaches to produce pieces that will rank-Effective AI content requires understanding both what to write and how to write itWe'd love your feedback about the tool and suggestions to make it better. Please leave feedback in the comments.Articles that we reference in the video:Pain Point SEO: https://www.growandconvert.com/seo/pain-point-seo/How Marketers Are Using AI for Writing [Survey]: https://www.growandconvert.com/ai/ai-writing-survey/

We talk about it all:  transgender sports issues, did we wrongly deport a guy, downtown sinkholes, autism.

The AI landscape saw significant activity, with OpenAI preparing new, smaller, and reasoning-focused models alongside facing capacity challenges.

"Preview: Author Patrick K. O'Donnell, "The Unvanquished," solves how Phil Sheridan found the weaknesses in the Confederate line at the APRIL 1, 1865 Battle of Five Forks that doomed Lee's army to flight and then surrender." MORE LATER. APRIL 3, 1865 RICHMOND

Send us a textWhat if the key to solving complex problems was something visual? In this episode, Justin Sirotin dives deep into the power of visual mapping and systems thinking to reveal hidden problems and streamline business efficiency. He shares how mapping techniques can be used across industries—from business and healthcare to education and entrepreneurship to enhance team collaboration, decision-making, and organizational development.Key Takeaways:How visual mapping uncovers blind spots in problem-solvingThe role of systems thinking in making better business decisionsWhy team collaboration is essential for innovation & efficiencyHow to practice problem-solving in low-risk environments to build confidenceThe power of empowering teams to take ownership of solutionsIf you're a business leader, entrepreneur, or problem-solver, this conversation will give you actionable strategies to improve efficiency and develop a smarter approach to tackling challenges.Virtual Rockstars specialize in helping support or replace all non-clinical roles.Book a free call to learn how a Virtual Rockstar can help scale your physical therapy practice.Subscribe here to our completely free Stress-Free PT Newsletter for your weekly dose of joy.

During the 4pm hour of today's show Chuck & Chernoff talked about Braves Twitter, Deion Sanders, Fat Casey's 8th Annual Mock Draft, a Braves Puzzle, Dale Murphy, DH's and an 18 game NFL season before a visit from Doc McChuckins and the final "Buck's Shining Moment" of the year. See omnystudio.com/listener for privacy information.

The Ringer's Tate Frazier is joined by J. Kyle Mann to discuss Houston's miraculous comeback vs. Duke (1:29), Florida's hard-fought win over Auburn (20:44), and a quick look-ahead to the national championship matchup between Houston and Florida (33:05). Host: Tate Frazier Guest: J. Kyle Mann Producer: Kyle Crichton Learn more about your ad choices. Visit podcastchoices.com/adchoices

Investigator Alina Burroughs examines murder cases ripped from the headlines. She explores prosecution and defense teams' tactics to highlight the evidence that argues their case. Alina knows it can't bring the victims back -- but it can bring them home.Alinas IG https://www.instagram.com/alinaburroughs/?hl=enhttps://www.alinaburroughs.comFollow me on all socials!Instagram: https://www.instagram.com/insidetruecrime/TikTok: https://www.tiktok.com/@mattcoxtruecrimeDo you want to be a guest? Fill out the form https://forms.gle/5H7FnhvMHKtUnq7k7Send me an email here: insidetruecrime@gmail.comDo you want a custom "con man" painting to shown up at your doorstep every month? Subscribe to my Patreon: https: //www.patreon.com/insidetruecrimeDo you want a custom painting done by me? Check out my Etsy Store: https://www.etsy.com/shop/coxpopartListen to my True Crime Podcasts anywhere: https://anchor.fm/mattcox Check out my true crime books! Shark in the Housing Pool: https://www.amazon.com/dp/B0851KBYCFBent: https://www.amazon.com/dp/B0BV4GC7TMIt's Insanity: https://www.amazon.com/dp/B08KFYXKK8Devil Exposed: https://www.amazon.com/dp/B08TH1WT5GDevil Exposed (The Abridgment): https://www.amazon.com/dp/1070682438The Program: https://www.amazon.com/dp/B0858W4G3KBailout: https://www.barnesandnoble.com/w/bailout-matthew-cox/1142275402Dude, Where's My Hand-Grenade?: https://www.amazon.com/dp/B0BXNFHBDF/ref=tmm_pap_swatch_0?_encoding=UTF8&qid=1678623676&sr=1-1Checkout my disturbingly twisted satiric novel!Stranger Danger: https://www.amazon.com/dp/B0BSWQP3WXIf you would like to support me directly, I accept donations here:Paypal: https://www.paypal.me/MattCox69Cashapp: $coxcon69

The boys kiss (on the cheek) X-Manhunt goodbye. They music montage celebrate the feminist motifs in celebrated X-men: Evolution episode “Walk on the Wild Side” (S2E13, name unrelated to anything). They recast all the characters in the new Avengers movie and no one is happy about it.

Send us a text

“His entire world revolved around her” --When cops break into the Groene home on May 16th 2005 after receiving a call from a concerned neighbor, no one is prepared to find the family murdered, and as they identify everyone, they notice that the younger children, Dylan, 9, and Shasta, 8, are missing. As the authorities race against time to find the missing kids, Shasta is trapped in the woods with her family's killer, nearly 100 miles away, and starts to plan her own escape.

This week they discuss the report that a quantum computer solved a problem that would take super computers 1 million years to solve. They drink an 8 Year old Trail's End Bourbon and smoke the Partagas Heritage. They get onto the topic of 'living like kings', which I believe we all are. https://www.msn.com/en-us/news/technology/world-first-us-quantum-computer-solves-problem-million-years-faster-than-supercomputer/ar-AA1AQriH?ocid=socialshare&cvid=19e32725356c47d9b6b14981babacef8&ei=12  

Terrence Howard says he solved the three-body problem, so why does nobody seem to care? Also this week, the Trump administration suffers perhaps the dumbest leak ever after a journalist was looped in on a group thread about attacks in Yemen (before the bombs fell). We discuss that, whether Biden's pardons will be recognized, Sam's dad's pioneer status in the realm of autism, Hawk Tuah's apology, why Snow White is flopping at the box office, the return of Sam Tripoli's Traffic Court, and so much more.Go to www.get.stash.com/broken to see how you can receive $25 towards your first stock purchase and to view important disclosures!$THC is the official crypto of Broken Simulation! They're paying us to talk about them (we have to say this, obviously) but we really like the project and the community around it. Don't put in any money you can't afford to lose, and check them out at www.tinhatcat.com!More stuff: Get episodes early, and unedited, plus bonus episodes: www.rokfin.com/brokensimulation or www.patreon.com/brokensimulationWatch Broken Simulation: https://www.youtube.com/samtripoliSocial media: Twitter: @samtripoli, @johnnywoodard Instagram: @samtripoli, @johnnyawoodardWant to see Sam live? Visit www.samtripoli.com for tickets!Broken Simulation Hosts: Sam Tripoli, Johnny Woodard

Tired of the same old wholesaling grind? Today, we have Karl Spielvogel, who uncovers hidden real estate opportunities by tackling the complex problems others avoid. Karl specializes in properties with tangled title issues, judgments, and other unique challenges. He'll share his secrets for turning these complicated situations into lucrative deals with less competition, offering a fresh perspective for ambitious wholesalers.Karl made $249,000 on one deal after finding out two of the owners were deceased. He left a note and a FedEx package explaining the situation to the living owner, and after nine months, she contacted him, leading to the deal. In this deal he bought three properties — one was bought for $57,000 and sold for $125,000! KEY TALKING POINTS:0:00 - An Overview Of Karl Spielvogel's Business0:45 - Why He Specializes In Harder Deals That Turn Other Investors Away3:00 - What Is A “Variance”?3:57 - Title Issues He Had With A Complex Deal5:07 - The Mindset That's Allowed Him To Focus On The Harder Problems6:01 - What He Was Trying To Accomplish When He Started His Business8:11 - How He Got His Creativity In Business Deals9:56 - What He Learned Recently12:56 - Using Long Term Investment Strategies & His Exit Strategy15:43 - The Ins And Outs Of Purchasing A Judgment22:08 - What Karl's Looking Forward To In 202523:15 - How To Get In Touch With Karl And His Deal Criteria24:40 - Outro LINKS:Contact Karl: 704-995-5385Instagram: Karl Spielvogelhttps://www.instagram.com/karlspielvogel/ Website: Karl Spielvogelhttps://www.legacylinkproperties.com/consultants Instagram: David Leckohttps://www.instagram.com/dlecko Website: DealMachinehttps://www.dealmachine.com/pod Instagram: Ryan Haywoodhttps://www.instagram.com/heritage_home_investments Website: Heritage Home Investmentshttps://www.heritagehomeinvestments.com/

Lars Bendsen joins the spotlight to discuss how AC883 helps operators source turbine parts to cut costs and reduce downtime. AC883 can offer faster response times and better pricing than manufacturers based in Europe. Lars shares how his company's approach helps prevent extended turbine downtime by providing quick access to critical components. Fill out our Uptime listener survey and enter to win an Uptime mug! Sign up now for Uptime Tech News, our weekly email update on all things wind technology. This episode is sponsored by Weather Guard Lightning Tech. Learn more about Weather Guard's StrikeTape Wind Turbine LPS retrofit. Follow the show on Facebook, YouTube, Twitter, Linkedin and visit Weather Guard on the web. And subscribe to Rosemary Barnes' YouTube channel here. Have a question we can answer on the show? Email us! Allen Hall: In the wind industry, a turbine standing still often means one thing, waiting for parts that should be readily available. This week on the uptime spotlight, we're joined by Lars Benson of AC 8 83, which is based in Canada. AC883 has direct connections to manufacturers in Denmark where most critical worm turbine components are actually produced Lars shares, house site operators can cut costs and dramatically reduce downtime by bypassing the OEM middleman and sourcing parts directly from the original suppliers. Welcome to Uptime Spotlight, shining Light on wind Energy's brightest innovators. This is the progress powering tomorrow. Allen Hall: Lars, welcome back to the show. Thank you. Spare Parts is a huge issue all over the world, but it seems like in the US and Canada, there's always a shortage. They're looking for spare parts. They don't know where to get them, and the easy answer has been to call the original equipment manufacturer in terms of the GE Vestus Siemens, cesa, Nordex, whoever that may be, and just to place a order. There are other opportunities out there. What happens when a wind side in Texas just decides to buy from the wind turbine manufacturer? How much are they paying overpaying for that part? Lars Bendsen: I can't say exactly on on dollars and cents, but but we know the markup from the OEMs. Then they're not shy of earning money on that, those parts. And yeah, so it's very simple. We can get those parts directly from Europe directly from the suppliers to the OEMs. Allen Hall: Yeah. And if I'm an operator, and I haven't been over to Denmark to look at the situation there, a significant number of critical parts are actually manufactured in Denmark or in the surrounding areas. You have no way of knowing that if you own the turbine, Lars Bendsen: that's true. You don't. Somehow the OEMs have been really good and keeping a bit of cloud cloudy around that area. It's actually pretty simple. They all produced either in in Denmark and Germany for basically all turbines. GE turbines is a target turbine from Germany that that they bought back when. So that's why sim that's a German turbine as well. It's not a US turbine at all. Allen Hall: And the supply chain has remained that way for a long time. Lars Bendsen: It's a BP parts. It's standard parts. There's no rocket sites in it. Of course, there's some legacy some software parts and stuff that we could be desk, some, what we call it electronic boards, which software on, of course we can't do that. That's fair enough, right? That's actually where the OOM has its value. That's totally good. Joel Saxum: I think part of the reason that you see this, that gap there in the industry is the simple fact that, and I don't take this as a slight Lars because I love your website and what you guys do for marketing and branding, but in that corner of the world, and Alan, you and I were just talking about this couple of German companies we're talking about they're not that good at global branding and global marketing. As a unit like culturally, so you don't see really what's going on almost behind t...

Slam Dunc from S4 Episode 39: The Immigration Policy That's Separating a Child from his Family Watch the full episode here: https://youtu.be/ex-PgBVv8tk PLUS… New episodes 7pm weekdays! Website: https://www.rova.nz/home/podcasts/duncan-garner---editor-in-chief. Instagram: @DuncanGarnerpodcast TikTok: @DuncanGarnerpodcast

Florida Man solves the egg shortage with Florida ingenuity (aka iguana eggs), BOOB TUBE BONANZA: "Adolescence," and "Running Point," and ABFAB: We love "Good Hang" with Amy Poehler Learn more about your ad choices. Visit podcastchoices.com/adchoicesSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Florida Man solves the egg shortage with Florida ingenuity (aka iguana eggs), BOOB TUBE BONANZA: "Adolescence," and "Running Point," and ABFAB: We love "Good Hang" with Amy Poehler Learn more about your ad choices. Visit podcastchoices.com/adchoices

Episode 295: How can you build a high trust culture that empowers your team to solve problems faster, innovate more, and reduce stress? In this episode, we explore the power of a high trust culture and how it can completely transform your team's ability to collaborate and solve problems effectively. If you've been facing challenges with getting your team to share ideas, open up, or work together seamlessly, this episode will give you proven strategies to overcome those hurdles and build the trust your team needs to thrive. By tuning in, you'll learn: The #1 skill for building trust: how to model the behaviors you want to see in your team. How to communicate your vision consistently to reinforce the culture you're building. The importance of follow-through: using celebration and accountability to reinforce trust and keep momentum. Press play now and start building the trust culture that will accelerate your team's performance today! Check out: (02:57) – The power of modeling – Learn how setting the right example can be the key to building a high-trust culture that drives collaboration and problem-solving. (05:36) – The five-by-five communication plan – Discover how consistent and clear communication can reinforce your trust culture and keep your team aligned. (10:35) – Celebration and accountability – Find out how to actively reinforce trust with follow-through, celebrating early wins and holding your team accountable for maintaining the culture. Leadership Without Using Your Soul podcast offers insightful discussions on leadership and management, focusing on essential communication skills, productivity, teamwork, delegation, and feedback to help leaders navigate various leadership styles, management styles, conflict resolution, time management, and active listening while addressing challenges like overwhelm, burnout, work-life balance, and problem-solving in both online and in-person teams, all aimed at cultivating human-centered leadership qualities that promote growth and success. Learn more about your ad choices. Visit megaphone.fm/adchoices

A new hope has emerged! Artificial Sky unveils revolutionary lighting tech set to bring daylight to even the darkest secure sectors, a force far superior to existing illumination. Discover the future of light-side technology at https://artificialsky.com/. May the light be with you! Artificial Sky City: Detroit Address: Website: http://www.artificialsky.com Email: sales@artificialsky.com

0:00 - The NBA has a 3-point problem. Too many teams are jacking up 100 3s a game and bricking most of them. It's borderline unwatchable. Thankfully, Vic has the solution. 16:05 - Would Cooper Kupp fit Sean Payton's plan and the mold of receiver he likes?33:40 - It's our favorite part of the week DRUNK TAKESSSSSSSSSS

Ah! The time has finally come again! We have a shorter version (2 hours) of one of our MONSTER EPISODES of Jay of the Dead's New Horror Movies, The Gold Standard of Horror Movie Podcasts! Here in Episode 138, a few of our Horror Avengers and guests bring you two Feature Reviews of brand-new Horror movie releases from 2025: Wolf Man (2025) and Presence (2025). Well, the latter is subject to some controversy, but it wouldn't be Jay of the Dead's New Horror Movies with that! We are also pleased to welcome two special guests: The Twisted Temptress and Grisly Gus Reynolds! But perhaps most remarkably, the contemptible Mister Watson actually solves an age-old mystery that the Horror Avengers have been puzzling about for years now! He reveals it for us right in this episode! So, join us! Be sure to subscribe to Jay of the Dead's new Horror movie podcast on: Apple PodcastsSpotifyDeezer   You are welcome to email our show at HauntingYourHeadphones@gmail.com, or call and leave us a voicemail at our new number: (801) 980-1375. You can also follow Jay of the Dead'sNew Horror Movies on X: @HorrorAvengers Jay of the Dead'sNew Horror Movies is an audio podcast. Our 10 Horror hosts review new Horror movies and deliver specialty Horror segments. Your hosts are Jay of the Dead, Dr. Shock, Gillman Joel, Mister Watson, Dr. Walking Dead, GregaMortis, Mackula, Ron Martin, Dave Zee and Spawn of the Dead! Due to the large number and busy schedule of its 10 Horror hosts, Jay of the Dead'sNew Horror Movies will be recorded in segments, piecemeal, at various times and recording sessions. Therefore, as you listen to our episodes, you will notice a variety of revolving door hosts and segments, all sewn together and reanimated like the powerful Monster of Dr. Frankenstein!

Want to turn AI and digital disruption into your competitive advantage as a service-based business? Join the MindShift Inner Circle.Want help to market, grow, and scale your business? Schedule a free strategy session. Are you a marketing team of one, wearing all the hats and struggling to create content for multiple platforms? In this episode, Darrell reveals how the power of AI can transform just one piece of video content into an entire marketing campaign. Learn the exact step-by-step process we use in our agency to help overwhelmed marketers get leverage without sacrificing their authentic voice.KEY TAKEAWAYS:One 11-minute video can provide all the raw material needed for a complete marketing campaignClaude AI is particularly effective at analyzing your voice and maintaining your authentic toneUpload your buyer persona details and brand voice guides before starting any content creationMost visitors only see the top third of your pages, so prioritize headlines and opening linesWork through campaign elements one by one instead of asking AI to do everything at onceEven if you don't want to be on camera, you can create valuable video content by answering common customer questionsWe love feedback. Send us a text message.Revolutionize your marketing with AI in a community of established founders and CEOs. Join the MindShift Inner Circle today and stay ahead of the curve! If you enjoyed this episode, please consider leaving us a rating and review on Apple Podcasts or Spotify. Your feedback helps us more than you know.

Poems are just arrangements of sounds, marks on a page. But the right one can change history, outlast civilizations, and turn a respectable men into wandering vagabonds. In this episode: poetry, why we need it, and how a 13th century love affair changed it forever. Ten Life-changing Poems (For People Who Don't Read Poetry)"A Brief for the Defense" Jack Gilbert"I Imagine the Gods" Jack Gilbert"Lost" David Wagoner"Otherwise" Jane Kenyon"The Guest House" Jalaluddin Rumi"The Summer Day" Mary Oliver"Wild Geese" Mary Oliver"Hope Is The Thing With Feathers" Emily Dickinson"God Says Yes to Me" Kaylin Haught"Dog's Death" John Updike

Joe had a TON of police cars out in front of his apartment complex... is there a murder that went down late last night in St. Pete?

We get more details from Joe's fiance about what could be a huge murder mystery that has gone unsolved in St. Pete!

James Gurd and Paul Rogers discuss the challenges of product data quality in ecommerce with Vidar Trojenborg, co-founder of Emfas.Vidar has a lot of experience building ecommerce tech stacks to improve and manage product data, having previously held the role of Head of Data & Technology at ASKET.In the po dcast, we explore how AI can automate product data management, improve catalog quality, and bridge the gap between product and ecommerce teams. Vidar shares insights on the importance of context-aware AI, the role of guidelines in maintaining brand integrity, and the future of ecommerce technology. The conversation also touches on translation challenges and the integration of Emfas with existing ecommerce platforms.Key takeaways:Data quality issues are a common challenge in ecommerce.Bridging the gap between product and ecommerce teams is crucial.Emfas uses AI to maintain content authenticity and tone of voice.The platform automates the auditing of product data.Guidelines can be set for AI-generated content.Emfas can handle large catalogues efficiently with rules.Context-aware AI ensures accurate product descriptions.Translation rules can be customised for different languages.The future of ecommerce will heavily involve AI technology.

Join Game Theory Host Tom as he solves the LORE of Amanda The Adventurer 2!

A jogger who died of a heart attack leads police to the unrelated murder of a woman who's been using the Social Security number of Marcella Celaya, who was killed ten years ago. Detectives Briscoe and Green learn that Rafael Berseño, the victim's husband, used to have the last name Celaya also. Before they question him further, they spot a jealous wife running over her husband with her car again and again. Then, Green discovers a note on a bathroom mirror from a pregnant woman saying she's been kidnapped. Meanwhile, they hear Rafael's brother Reynaldo just got out of prison for killing his wife Marcella, though her body was never found.Reynaldo tells McCoy and Southerlyn he already served his sentence for killing Marcella, even though she wasn't dead, and they can't convict him twice for killing the same person. Still on the job, Briscoe and Green learn Rafael and Marcella set up Reynaldo so they could be together. When he got out of prison, he forced his brother to kill his (their) wife. Briscoe gets a lead on the kidnapping. The mom-to-be was abducted by an infertile woman. They rescue her just as she goes into labor, forcing Lennie to deliver the baby himself.  Before they can finally punch out for the night, Dr. Rogers calls to say that jogger didn't have a heart attack...he'd been poisoned!We're talking about one crazy day for the detectives in Law & Order season 13 episode 23* "Couples." Our guest is Sarah Carradine from the Crime Seen podcast.Among the many inspirations for this story include the case of Clara and David Lynn Harris.*Note: Hulu incorrectly lists this as episode 24. For exclusive content from Kevin and Rebecca, sign up on Patreon.

Xeno was unveiled at a recent hackathon—the first fully decentralized payment terminal on the XRP Ledger. Seamlessly tap-to-pay with stablecoins (RLUSD), zero fees, and a frictionless merchant & user experience.~This episode is sponsored by Uphold~Uphold Get $20 in Bitcoin - Signup & Verify and trade at least $100 of any crypto within your first 30 days ➜ https://bit.ly/pbnuphold00:00 intro00:20 Sponsor: Uphold00:50 Swipe Fees01:39 Paul Searches For Zero Fees03:08 Crypto Fees Suck Too04:03 Hidden Fees & New Fees04:36 Solana Partnered With Visa05:34 Visa Crypto Cards06:05 Bitcoin POS System Sucks06:38 Worst Solution EVER? Polkadot07:55 Stablecoins Growing Exponentially08:36 Hackathon Kid Solves Problem?09:06 Xenu Demo on XRP Ledger10:38 XRP POS System Details11:18 Revenue Model: Swap Spread Fees11:45 Pay-To-Earn Adoption12:20 Live Demo at Apex Event12:44 Visa TPS Speed13:00 Bank POS systems Incoming13:32 Ethereum Light Nodes14:39 ETH Gas Fees Falling14:50 Layer-2 TPS15:02 Conclusion15:38 outro#Crypto #XRP #Ethereum~Kid Solves $1 Trillion Problem with XRP?

This release officially sunsets the old Mystery Sounds featured in our Sound Test Episodes from Episode 124 all the way to Episode 291.  MrNiceGuy takes a shot at some of the historical sounds, and does a dang good job of it too!  Going forward we will keep 10 sound tests active for guessing, and every […]

Our main guest for this episode is Jocelyne Fiume, the founder of Kiyamel Skincare Solutions. Jocelyne shares her inspiring journey of creating a natural, clinically tested skincare line specifically for people with eczema and sensitive skin. She talks about her motivation, which stemmed from her daughter's struggle with eczema, and how she turned that into a successful business.Subscribe to the Social Proof Podcast:Apple Podcasts: https://podcasts.apple.com/us/podcast...Spotify: https://open.spotify.com/show/6GT6Vgj...

This week, on episode 495, I'm talking with Will Schafer, founder of Altisnooze. The First-of-its-kind sleep aid for high-altitude. After struggling for years with sleeping during alpine adventures, Schafer came to learn from a sleep doctor that altitude insomnia is a thing. He connected with formulation experts to develop a natural solution, ALTISNOOZE. Facebook   Twitter   Instagram Love the show? Subscribe,  rate, review, and share! Sign up for my Newsletter  HERE I'd love to hear your feedback about the show! You can contact me here:  rick@theoutdoorbizpodcast.com What Happened: For years, I chalked up my awful sleep in the mountains to bad luck. Every time I went to Summit County, Colorado, my nights were a mess—staring at the ceiling, waking up feeling like I'd been run over by a snowcat, and then trying to enjoy the outdoors while running on fumes. I blamed it on travel, excitement, bad pillows—you name it. But then I started noticing something weird. Friends on ski trips and camping adventures were having the same problem. Some of them, tough-as-nails hikers and backcountry warriors, were walking around like zombies after a single night at altitude. That's when I met Dr. Michael Breus, a legit sleep doctor, who hit me with a truth bomb: altitude insomnia is real. And worse? It affects up to 75% of people. Your body's struggling with low oxygen, which wrecks your sleep cycle, making it nearly impossible to rest. So, I set out on a mission to fix it. After a deep dive into research, testing a ridiculous amount of natural ingredients, and countless sleepless nights (for science), I created Altisnooze—a sleep aid designed specifically for high-altitude adventures, without the grogginess of melatonin. Principle: Bad sleep = bad adventure. Period. You can have the best gear, the most epic trail planned, and a perfect sunrise waiting for you—but if you don't sleep well, your trip is going to suck. Most people don't even realize altitude is the issue. They just assume they're bad sleepers, or that their body needs to “adjust.” But waiting around for a week to acclimate? Not ideal when your trip is only a few days long. Good sleep isn't just about comfort—it's about performance, recovery, and actually enjoying the adventure you planned. Transition: A lot of outdoor lovers deal with this and don't even realize what's holding them back. They push through exhaustion, drink too much caffeine, or try to knock themselves out with melatonin—only to wake up feeling worse. That's exactly why I created Altasnooze. Because when you finally fix your sleep at altitude, everything changes—your energy, your performance, your mood, and most importantly, how much fun you have. That's Why: …we want to introduce you to Altisnooze and just dropped an episode of the Outdoor Adventure Lifestyle Podcast with Will Schaefer, founder of Altisnooze. He went from being a sleep-deprived mess in the mountains to developing a game-changing solution for adventurers who want to feel fabulous at altitude. In this episode, we dive into the science of altitude insomnia, how it messes with your body, and what you can do to fix it—so your next high-altitude trip doesn't turn into a sleepless disaster. Call to Action: If you've ever struggled to sleep in the mountains, this episode is your wake-up call. (Pun intended.) Don't let altitude ruin your adventure—get the inside scoop on fixing your sleep at high elevation and feeling your best. #Outdoor Adventure Lifestyle Podcast, #altitude insomnia, #AltiSnooze, #high altitude sleep aid, #altitude sickness, #sleep doctor, #Michael Breus, #adventure travel, #melatonin-free, #sleep disturbance, #alpinists, #electrolytes, #high altitude adventures, #natural supplements, #altitude symptoms

- Scout EREV Motor Mounted by Rear Axle - Honda Wants Nissan CEO Gone for Merger - ZF Considers Selling EV Drivetrain Business - GM to Add Tahoe EV to Orion Plant - Renault and Geely Join Forces in Brazil - Renault Solves EV Battery Fires - Trump to Kill California ZEV Waiver - Volvo XC60 Gets New Front End - Toyota Puts Sauna in HiAce Van

- Scout EREV Motor Mounted by Rear Axle - Honda Wants Nissan CEO Gone for Merger - ZF Considers Selling EV Drivetrain Business - GM to Add Tahoe EV to Orion Plant - Renault and Geely Join Forces in Brazil - Renault Solves EV Battery Fires - Trump to Kill California ZEV Waiver - Volvo XC60 Gets New Front End - Toyota Puts Sauna in HiAce Van

Alan interviews Erez Halfon. Erez Halfon liked working in his garage - but it lacked ventilation - and got hot and stuffy inside. He invented the solution - a solar-powered ventilation system that cooled with fans. Today, he markets his Zula Ventilation system to homeowners who love his solution to stuffy garages. Make sure to subscribe to the podcast at Apple Podcasts, or wherever you get your podcasts, so you won't miss a single episode. Website: www.MobenoSolarSolutions.com  

Have you ever felt like you're spinning your wheels, working tirelessly but not seeing the growth you desire?  In this episode of Life After Corporate, host Deb Boulanger explores the intricacies of scaling a business with guest Meryl Simmons, an experienced EOS implementer. Together, they'll uncover the secrets of building a robust business foundation, learn how to overcome growth ceilings and discover the power of a strategic coaching approach. With Meryl's expertise, you'll explore the Entrepreneurial Operating System (EOS) and its potential to revolutionize your business journey, regardless of its size or stage. This episode is full of actionable nuggets that will equip you to scale effectively and thrive in the services sector.  Don't wait until you hit your next ceiling; listen now to learn how intentional systems and processes can set your business on the path to sustainable growth!    [00:05- 13:29] Understanding Business Operating Systems   EOS provides tools to clarify vision, execute strategy, and build healthy teams   Designed for companies with 20-300 employees seeking disciplined growth   Helps align team energy through shared language and accountability frameworks   Solves common challenges like unclear priorities and inconsistent execution       [13:30 -19:19] Identifying Growth Ceilings   First warning sign: Persistent lack of strategic direction   Second indicator: Previously successful tactics stop working   Third red flag: Inability to prioritize high-impact activities   Fourth challenge: Founder becomes bottleneck through poor delegation   Fifth symptom: Team operates without clear role definitions       [19:20 -24:56]  Performance Measurement Tools     Weekly dashboards tracking 5-15 leading indicators   Balanced scorecards combining lagging and leading metrics   Revenue goal breakdowns into monthly/client targets   Activity-based KPIs (e.g., sales conversations per week)     [24:56 - 31:04] Sustainable Growth Practices   Annual structural audits for functional seat effectiveness   Continuous scorecard refinement based on metric relevance   Delegation checklists defining outcomes and success metrics   Prevention of founder burnout through role evolution    Connect with Meryl Simmons Website:  https://www.justgetfocused.com/ Website: http://Www.eosworldwide.com/meryl-simmons Email: meryl@outpaceenterprises.com LinkedIn:  https://www.linkedin.com/in/merylsimmons/   Books mentioned on this episode   Traction: Get a Grip on Your Business  Traction: Get a Grip on Your Business: Wickman, Gino: 9781936661831: Amazon.com: Books   Get a Grip   Amazon.com: Get A Grip: An Entrepreneurial Fable . . . Your Journey to Get Real, Get Simple, and Get Results eBook : Wickman, Gino, Paton, Mike: Kindle Store Free Tools mentioned on this episode   https://www.eosworldwide.com/meryl-simmons#downloads   Scorecard https://www.justgetfocused.com/get-focused-coaching-weekly-business-dashboard-download      Ready to turn insights into action? Don't just listen—join the movement! The Life After Corporate Community (https://lifeaftercorporate.com/community) is where ambitious women like you connect, collaborate, and get the strategies, tools, and high-level support to grow a thriving, profitable business. Join us now and start making the powerful connections that will elevate your success!   Go to https://lifeaftercorporate.com/podcast  for all episodes 168.  The Chris Voss Method for Closing the Deal! 163.  Joyce Marter's Financial Mindset Fix: The Key to Unlocking Your True Abundance!   87.  Secrets of Great Copywriting with Julie Cabezas Tweetable Quotes: "Every business needs an operating system to run effectively and efficiently and really operate and build a better business." Meryl Simmons on Aligning Human Energy "I left and I went out on my own, and I, my husband, who's a lifelong entrepreneur, really encouraged me to do that."...Meryl Simmons on Aligning Human Energy on Entrepreneurial Journey   **TRANSCRIPT AVAILABLE UPON REQUEST**   SUBSCRIBE & LEAVE A FIVE-STAR REVIEW and share this podcast to other growing entrepreneurs!  Get weekly tips on how to create more money and meaning doing work you love and be one of the many growing entrepreneurs in our community. Connect with me on LinkedIn; https://www.linkedin.com/groups/12656341/  or on Instagram or our website at www.lifeaftercorporatepodcast.com .

If you're in SF, join us tomorrow for a fun meetup at CodeGen Night!If you're in NYC, join us for AI Engineer Summit! The Agent Engineering track is now sold out, but 25 tickets remain for AI Leadership and 5 tickets for the workshops. You can see the full schedule of speakers and workshops at https://ai.engineer!It's exceedingly hard to introduce someone like Bret Taylor. We could recite his Wikipedia page, or his extensive work history through Silicon Valley's greatest companies, but everyone else already does that.As a podcast by AI engineers for AI engineers, we had the opportunity to do something a little different. We wanted to dig into what Bret sees from his vantage point at the top of our industry for the last 2 decades, and how that explains the rise of the AI Architect at Sierra, the leading conversational AI/CX platform.“Across our customer base, we are seeing a new role emerge - the role of the AI architect. These leaders are responsible for helping define, manage and evolve their company's AI agent over time. They come from a variety of both technical and business backgrounds, and we think that every company will have one or many AI architects managing their AI agent and related experience.”In our conversation, Bret Taylor confirms the Paul Buchheit legend that he rewrote Google Maps in a weekend, armed with only the help of a then-nascent Google Closure Compiler and no other modern tooling. But what we find remarkable is that he was the PM of Maps, not an engineer, though of course he still identifies as one. We find this theme recurring throughout Bret's career and worldview. We think it is plain as day that AI leadership will have to be hands-on and technical, especially when the ground is shifting as quickly as it is today:“There's a lot of power in combining product and engineering into as few people as possible… few great things have been created by committee.”“If engineering is an order taking organization for product you can sometimes make meaningful things, but rarely will you create extremely well crafted breakthrough products. Those tend to be small teams who deeply understand the customer need that they're solving, who have a maniacal focus on outcomes.”“And I think the reason why is if you look at like software as a service five years ago, maybe you can have a separation of product and engineering because most software as a service created five years ago. I wouldn't say there's like a lot of technological breakthroughs required for most business applications. And if you're making expense reporting software or whatever, it's useful… You kind of know how databases work, how to build auto scaling with your AWS cluster, whatever, you know, it's just, you're just applying best practices to yet another problem. "When you have areas like the early days of mobile development or the early days of interactive web applications, which I think Google Maps and Gmail represent, or now AI agents, you're in this constant conversation with what the requirements of your customers and stakeholders are and all the different people interacting with it and the capabilities of the technology. And it's almost impossible to specify the requirements of a product when you're not sure of the limitations of the technology itself.”This is the first time the difference between technical leadership for “normal” software and for “AI” software was articulated this clearly for us, and we'll be thinking a lot about this going forward. We left a lot of nuggets in the conversation, so we hope you'll just dive in with us (and thank Bret for joining the pod!)Timestamps* 00:00:02 Introductions and Bret Taylor's background* 00:01:23 Bret's experience at Stanford and the dot-com era* 00:04:04 The story of rewriting Google Maps backend* 00:11:06 Early days of interactive web applications at Google* 00:15:26 Discussion on product management and engineering roles* 00:21:00 AI and the future of software development* 00:26:42 Bret's approach to identifying customer needs and building AI companies* 00:32:09 The evolution of business models in the AI era* 00:41:00 The future of programming languages and software development* 00:49:38 Challenges in precisely communicating human intent to machines* 00:56:44 Discussion on Artificial General Intelligence (AGI) and its impact* 01:08:51 The future of agent-to-agent communication* 01:14:03 Bret's involvement in the OpenAI leadership crisis* 01:22:11 OpenAI's relationship with Microsoft* 01:23:23 OpenAI's mission and priorities* 01:27:40 Bret's guiding principles for career choices* 01:29:12 Brief discussion on pasta-making* 01:30:47 How Bret keeps up with AI developments* 01:32:15 Exciting research directions in AI* 01:35:19 Closing remarks and hiring at Sierra Transcript[00:02:05] Introduction and Guest Welcome[00:02:05] Alessio: Hey everyone, welcome to the Latent Space Podcast. This is Alessio, partner and CTO at Decibel Partners, and I'm joined by my co host swyx, founder of smol.ai.[00:02:17] swyx: Hey, and today we're super excited to have Bret Taylor join us. Welcome. Thanks for having me. It's a little unreal to have you in the studio.[00:02:25] swyx: I've read about you so much over the years, like even before. Open AI effectively. I mean, I use Google Maps to get here. So like, thank you for everything that you've done. Like, like your story history, like, you know, I think people can find out what your greatest hits have been.[00:02:40] Bret Taylor's Early Career and Education[00:02:40] swyx: How do you usually like to introduce yourself when, you know, you talk about, you summarize your career, like, how do you look at yourself?[00:02:47] Bret: Yeah, it's a great question. You know, we, before we went on the mics here, we're talking about the audience for this podcast being more engineering. And I do think depending on the audience, I'll introduce myself differently because I've had a lot of [00:03:00] corporate and board roles. I probably self identify as an engineer more than anything else though.[00:03:04] Bret: So even when I was. Salesforce, I was coding on the weekends. So I think of myself as an engineer and then all the roles that I do in my career sort of start with that just because I do feel like engineering is sort of a mindset and how I approach most of my life. So I'm an engineer first and that's how I describe myself.[00:03:24] Bret: You majored in computer[00:03:25] swyx: science, like 1998. And, and I was high[00:03:28] Bret: school, actually my, my college degree was Oh, two undergrad. Oh, three masters. Right. That old.[00:03:33] swyx: Yeah. I mean, no, I was going, I was going like 1998 to 2003, but like engineering wasn't as, wasn't a thing back then. Like we didn't have the title of senior engineer, you know, kind of like, it was just.[00:03:44] swyx: You were a programmer, you were a developer, maybe. What was it like in Stanford? Like, what was that feeling like? You know, was it, were you feeling like on the cusp of a great computer revolution? Or was it just like a niche, you know, interest at the time?[00:03:57] Stanford and the Dot-Com Bubble[00:03:57] Bret: Well, I was at Stanford, as you said, from 1998 to [00:04:00] 2002.[00:04:02] Bret: 1998 was near the peak of the dot com bubble. So. This is back in the day where most people that they're coding in the computer lab, just because there was these sun microsystems, Unix boxes there that most of us had to do our assignments on. And every single day there was a. com like buying pizza for everybody.[00:04:20] Bret: I didn't have to like, I got. Free food, like my first two years of university and then the dot com bubble burst in the middle of my college career. And so by the end there was like tumbleweed going to the job fair, you know, it was like, cause it was hard to describe unless you were there at the time, the like level of hype and being a computer science major at Stanford was like, A thousand opportunities.[00:04:45] Bret: And then, and then when I left, it was like Microsoft, IBM.[00:04:49] Joining Google and Early Projects[00:04:49] Bret: And then the two startups that I applied to were VMware and Google. And I ended up going to Google in large part because a woman named Marissa Meyer, who had been a teaching [00:05:00] assistant when I was, what was called a section leader, which was like a junior teaching assistant kind of for one of the big interest.[00:05:05] Bret: Yes. Classes. She had gone there. And she was recruiting me and I knew her and it was sort of felt safe, you know, like, I don't know. I thought about it much, but it turned out to be a real blessing. I realized like, you know, you always want to think you'd pick Google if given the option, but no one knew at the time.[00:05:20] Bret: And I wonder if I'd graduated in like 1999 where I've been like, mom, I just got a job at pets. com. It's good. But you know, at the end I just didn't have any options. So I was like, do I want to go like make kernel software at VMware? Do I want to go build search at Google? And I chose Google. 50, 50 ball.[00:05:36] Bret: I'm not really a 50, 50 ball. So I feel very fortunate in retrospect that the economy collapsed because in some ways it forced me into like one of the greatest companies of all time, but I kind of lucked into it, I think.[00:05:47] The Google Maps Rewrite Story[00:05:47] Alessio: So the famous story about Google is that you rewrote the Google maps back in, in one week after the map quest quest maps acquisition, what was the story there?[00:05:57] Alessio: Is it. Actually true. Is it [00:06:00] being glorified? Like how, how did that come to be? And is there any detail that maybe Paul hasn't shared before?[00:06:06] Bret: It's largely true, but I'll give the color commentary. So it was actually the front end, not the back end, but it turns out for Google maps, the front end was sort of the hard part just because Google maps was.[00:06:17] Bret: Largely the first ish kind of really interactive web application, say first ish. I think Gmail certainly was though Gmail, probably a lot of people then who weren't engineers probably didn't appreciate its level of interactivity. It was just fast, but. Google maps, because you could drag the map and it was sort of graphical.[00:06:38] Bret: My, it really in the mainstream, I think, was it a map[00:06:41] swyx: quest back then that was, you had the arrows up and down, it[00:06:44] Bret: was up and down arrows. Each map was a single image and you just click left and then wait for a few seconds to the new map to let it was really small too, because generating a big image was kind of expensive on computers that day.[00:06:57] Bret: So Google maps was truly innovative in that [00:07:00] regard. The story on it. There was a small company called where two technologies started by two Danish brothers, Lars and Jens Rasmussen, who are two of my closest friends now. They had made a windows app called expedition, which had beautiful maps. Even in 2000.[00:07:18] Bret: For whenever we acquired or sort of acquired their company, Windows software was not particularly fashionable, but they were really passionate about mapping and we had made a local search product that was kind of middling in terms of popularity, sort of like a yellow page of search product. So we wanted to really go into mapping.[00:07:36] Bret: We'd started working on it. Their small team seemed passionate about it. So we're like, come join us. We can build this together.[00:07:42] Technical Challenges and Innovations[00:07:42] Bret: It turned out to be a great blessing that they had built a windows app because you're less technically constrained when you're doing native code than you are building a web browser, particularly back then when there weren't really interactive web apps and it ended up.[00:07:56] Bret: Changing the level of quality that we [00:08:00] wanted to hit with the app because we were shooting for something that felt like a native windows application. So it was a really good fortune that we sort of, you know, their unusual technical choices turned out to be the greatest blessing. So we spent a lot of time basically saying, how can you make a interactive draggable map in a web browser?[00:08:18] Bret: How do you progressively load, you know, new map tiles, you know, as you're dragging even things like down in the weeds of the browser at the time, most browsers like Internet Explorer, which was dominant at the time would only load two images at a time from the same domain. So we ended up making our map tile servers have like.[00:08:37] Bret: Forty different subdomains so we could load maps and parallels like lots of hacks. I'm happy to go into as much as like[00:08:44] swyx: HTTP connections and stuff.[00:08:46] Bret: They just like, there was just maximum parallelism of two. And so if you had a map, set of map tiles, like eight of them, so So we just, we were down in the weeds of the browser anyway.[00:08:56] Bret: So it was lots of plumbing. I can, I know a lot more about browsers than [00:09:00] most people, but then by the end of it, it was fairly, it was a lot of duct tape on that code. If you've ever done an engineering project where you're not really sure the path from point A to point B, it's almost like. Building a house by building one room at a time.[00:09:14] Bret: The, there's not a lot of architectural cohesion at the end. And then we acquired a company called Keyhole, which became Google earth, which was like that three, it was a native windows app as well, separate app, great app, but with that, we got licenses to all this satellite imagery. And so in August of 2005, we added.[00:09:33] Bret: Satellite imagery to Google Maps, which added even more complexity in the code base. And then we decided we wanted to support Safari. There was no mobile phones yet. So Safari was this like nascent browser on, on the Mac. And it turns out there's like a lot of decisions behind the scenes, sort of inspired by this windows app, like heavy use of XML and XSLT and all these like.[00:09:54] Bret: Technologies that were like briefly fashionable in the early two thousands and everyone hates now for good [00:10:00] reason. And it turns out that all of the XML functionality and Internet Explorer wasn't supporting Safari. So people are like re implementing like XML parsers. And it was just like this like pile of s**t.[00:10:11] Bret: And I had to say a s**t on your part. Yeah, of[00:10:12] Alessio: course.[00:10:13] Bret: So. It went from this like beautifully elegant application that everyone was proud of to something that probably had hundreds of K of JavaScript, which sounds like nothing. Now we're talking like people have modems, you know, not all modems, but it was a big deal.[00:10:29] Bret: So it was like slow. It took a while to load and just, it wasn't like a great code base. Like everything was fragile. So I just got. Super frustrated by it. And then one weekend I did rewrite all of it. And at the time the word JSON hadn't been coined yet too, just to give you a sense. So it's all XML.[00:10:47] swyx: Yeah.[00:10:47] Bret: So we used what is now you would call JSON, but I just said like, let's use eval so that we can parse the data fast. And, and again, that's, it would literally as JSON, but at the time there was no name for it. So we [00:11:00] just said, let's. Pass on JavaScript from the server and eval it. And then somebody just refactored the whole thing.[00:11:05] Bret: And, and it wasn't like I was some genius. It was just like, you know, if you knew everything you wished you had known at the beginning and I knew all the functionality, cause I was the primary, one of the primary authors of the JavaScript. And I just like, I just drank a lot of coffee and just stayed up all weekend.[00:11:22] Bret: And then I, I guess I developed a bit of reputation and no one knew about this for a long time. And then Paul who created Gmail and I ended up starting a company with him too, after all of this told this on a podcast and now it's large, but it's largely true. I did rewrite it and it, my proudest thing.[00:11:38] Bret: And I think JavaScript people appreciate this. Like the un G zipped bundle size for all of Google maps. When I rewrote, it was 20 K G zipped. It was like much smaller for the entire application. It went down by like 10 X. So. What happened on Google? Google is a pretty mainstream company. And so like our usage is shot up because it turns out like it's faster.[00:11:57] Bret: Just being faster is worth a lot of [00:12:00] percentage points of growth at a scale of Google. So how[00:12:03] swyx: much modern tooling did you have? Like test suites no compilers.[00:12:07] Bret: Actually, that's not true. We did it one thing. So I actually think Google, I, you can. Download it. There's a, Google has a closure compiler, a closure compiler.[00:12:15] Bret: I don't know if anyone still uses it. It's gone. Yeah. Yeah. It's sort of gone out of favor. Yeah. Well, even until recently it was better than most JavaScript minifiers because it was more like it did a lot more renaming of variables and things. Most people use ES build now just cause it's fast and closure compilers built on Java and super slow and stuff like that.[00:12:37] Bret: But, so we did have that, that was it. Okay.[00:12:39] The Evolution of Web Applications[00:12:39] Bret: So and that was treated internally, you know, it was a really interesting time at Google at the time because there's a lot of teams working on fairly advanced JavaScript when no one was. So Google suggest, which Kevin Gibbs was the tech lead for, was the first kind of type ahead, autocomplete, I believe in a web browser, and now it's just pervasive in search boxes that you sort of [00:13:00] see a type ahead there.[00:13:01] Bret: I mean, chat, dbt[00:13:01] swyx: just added it. It's kind of like a round trip.[00:13:03] Bret: Totally. No, it's now pervasive as a UI affordance, but that was like Kevin's 20 percent project. And then Gmail, Paul you know, he tells the story better than anyone, but he's like, you know, basically was scratching his own itch, but what was really neat about it is email, because it's such a productivity tool, just needed to be faster.[00:13:21] Bret: So, you know, he was scratching his own itch of just making more stuff work on the client side. And then we, because of Lars and Yen sort of like setting the bar of this windows app or like we need our maps to be draggable. So we ended up. Not only innovate in terms of having a big sync, what would be called a single page application today, but also all the graphical stuff you know, we were crashing Firefox, like it was going out of style because, you know, when you make a document object model with the idea that it's a document and then you layer on some JavaScript and then we're essentially abusing all of this, it just was running into code paths that were not.[00:13:56] Bret: Well, it's rotten, you know, at this time. And so it was [00:14:00] super fun. And, and, you know, in the building you had, so you had compilers, people helping minify JavaScript just practically, but there is a great engineering team. So they were like, that's why Closure Compiler is so good. It was like a. Person who actually knew about programming languages doing it, not just, you know, writing regular expressions.[00:14:17] Bret: And then the team that is now the Chrome team believe, and I, I don't know this for a fact, but I'm pretty sure Google is the main contributor to Firefox for a long time in terms of code. And a lot of browser people were there. So every time we would crash Firefox, we'd like walk up two floors and say like, what the hell is going on here?[00:14:35] Bret: And they would load their browser, like in a debugger. And we could like figure out exactly what was breaking. And you can't change the code, right? Cause it's the browser. It's like slow, right? I mean, slow to update. So, but we could figure out exactly where the bug was and then work around it in our JavaScript.[00:14:52] Bret: So it was just like new territory. Like so super, super fun time, just like a lot of, a lot of great engineers figuring out [00:15:00] new things. And And now, you know, the word, this term is no longer in fashion, but the word Ajax, which was asynchronous JavaScript and XML cause I'm telling you XML, but see the word XML there, to be fair, the way you made HTTP requests from a client to server was this.[00:15:18] Bret: Object called XML HTTP request because Microsoft and making Outlook web access back in the day made this and it turns out to have nothing to do with XML. It's just a way of making HTTP requests because XML was like the fashionable thing. It was like that was the way you, you know, you did it. But the JSON came out of that, you know, and then a lot of the best practices around building JavaScript applications is pre React.[00:15:44] Bret: I think React was probably the big conceptual step forward that we needed. Even my first social network after Google, we used a lot of like HTML injection and. Making real time updates was still very hand coded and it's really neat when you [00:16:00] see conceptual breakthroughs like react because it's, I just love those things where it's like obvious once you see it, but it's so not obvious until you do.[00:16:07] Bret: And actually, well, I'm sure we'll get into AI, but I, I sort of feel like we'll go through that evolution with AI agents as well that I feel like we're missing a lot of the core abstractions that I think in 10 years we'll be like, gosh, how'd you make agents? Before that, you know, but it was kind of that early days of web applications.[00:16:22] swyx: There's a lot of contenders for the reactive jobs of of AI, but no clear winner yet. I would say one thing I was there for, I mean, there's so much we can go into there. You just covered so much.[00:16:32] Product Management and Engineering Synergy[00:16:32] swyx: One thing I just, I just observe is that I think the early Google days had this interesting mix of PM and engineer, which I think you are, you didn't, you didn't wait for PM to tell you these are my, this is my PRD.[00:16:42] swyx: This is my requirements.[00:16:44] mix: Oh,[00:16:44] Bret: okay.[00:16:45] swyx: I wasn't technically a software engineer. I mean,[00:16:48] Bret: by title, obviously. Right, right, right.[00:16:51] swyx: It's like a blend. And I feel like these days, product is its own discipline and its own lore and own industry and engineering is its own thing. And there's this process [00:17:00] that happens and they're kind of separated, but you don't produce as good of a product as if they were the same person.[00:17:06] swyx: And I'm curious, you know, if, if that, if that sort of resonates in, in, in terms of like comparing early Google versus modern startups that you see out there,[00:17:16] Bret: I certainly like wear a lot of hats. So, you know, sort of biased in this, but I really agree that there's a lot of power and combining product design engineering into as few people as possible because, you know few great things have been created by committee, you know, and so.[00:17:33] Bret: If engineering is an order taking organization for product you can sometimes make meaningful things, but rarely will you create extremely well crafted breakthrough products. Those tend to be small teams who deeply understand the customer need that they're solving, who have a. Maniacal focus on outcomes.[00:17:53] Bret: And I think the reason why it's, I think for some areas, if you look at like software as a service five years ago, maybe you can have a [00:18:00] separation of product and engineering because most software as a service created five years ago. I wouldn't say there's like a lot of like. Technological breakthroughs required for most, you know, business applications.[00:18:11] Bret: And if you're making expense reporting software or whatever, it's useful. I don't mean to be dismissive of expense reporting software, but you probably just want to understand like, what are the requirements of the finance department? What are the requirements of an individual file expense report? Okay.[00:18:25] Bret: Go implement that. And you kind of know how web applications are implemented. You kind of know how to. How databases work, how to build auto scaling with your AWS cluster, whatever, you know, it's just, you're just applying best practices to yet another problem when you have areas like the early days of mobile development or the early days of interactive web applications, which I think Google Maps and Gmail represent, or now AI agents, you're in this constant conversation with what the requirements of your customers and stakeholders are and all the different people interacting with it.[00:18:58] Bret: And the capabilities of the [00:19:00] technology. And it's almost impossible to specify the requirements of a product when you're not sure of the limitations of the technology itself. And that's why I use the word conversation. It's not literal. That's sort of funny to use that word in the age of conversational AI.[00:19:15] Bret: You're constantly sort of saying, like, ideally, you could sprinkle some magic AI pixie dust and solve all the world's problems, but it's not the way it works. And it turns out that actually, I'll just give an interesting example.[00:19:26] AI Agents and Modern Tooling[00:19:26] Bret: I think most people listening probably use co pilots to code like Cursor or Devon or Microsoft Copilot or whatever.[00:19:34] Bret: Most of those tools are, they're remarkable. I'm, I couldn't, you know, imagine development without them now, but they're not autonomous yet. Like I wouldn't let it just write most code without my interactively inspecting it. We just are somewhere between it's an amazing co pilot and it's an autonomous software engineer.[00:19:53] Bret: As a product manager, like your aspirations for what the product is are like kind of meaningful. But [00:20:00] if you're a product person, yeah, of course you'd say it should be autonomous. You should click a button and program should come out the other side. The requirements meaningless. Like what matters is like, what is based on the like very nuanced limitations of the technology.[00:20:14] Bret: What is it capable of? And then how do you maximize the leverage? It gives a software engineering team, given those very nuanced trade offs. Coupled with the fact that those nuanced trade offs are changing more rapidly than any technology in my memory, meaning every few months you'll have new models with new capabilities.[00:20:34] Bret: So how do you construct a product that can absorb those new capabilities as rapidly as possible as well? That requires such a combination of technical depth and understanding the customer that you really need more integration. Of product design and engineering. And so I think it's why with these big technology waves, I think startups have a bit of a leg up relative to incumbents because they [00:21:00] tend to be sort of more self actualized in terms of just like bringing those disciplines closer together.[00:21:06] Bret: And in particular, I think entrepreneurs, the proverbial full stack engineers, you know, have a leg up as well because. I think most breakthroughs happen when you have someone who can understand those extremely nuanced technical trade offs, have a vision for a product. And then in the process of building it, have that, as I said, like metaphorical conversation with the technology, right?[00:21:30] Bret: Gosh, I ran into a technical limit that I didn't expect. It's not just like changing that feature. You might need to refactor the whole product based on that. And I think that's, that it's particularly important right now. So I don't, you know, if you, if you're building a big ERP system, probably there's a great reason to have product and engineering.[00:21:51] Bret: I think in general, the disciplines are there for a reason. I think when you're dealing with something as nuanced as the like technologies, like large language models today, there's a ton of [00:22:00] advantage of having. Individuals or organizations that integrate the disciplines more formally.[00:22:05] Alessio: That makes a lot of sense.[00:22:06] Alessio: I've run a lot of engineering teams in the past, and I think the product versus engineering tension has always been more about effort than like whether or not the feature is buildable. But I think, yeah, today you see a lot more of like. Models actually cannot do that. And I think the most interesting thing is on the startup side, people don't yet know where a lot of the AI value is going to accrue.[00:22:26] Alessio: So you have this rush of people building frameworks, building infrastructure, layered things, but we don't really know the shape of the compute. I'm curious that Sierra, like how you thought about building an house, a lot of the tooling for evals or like just, you know, building the agents and all of that.[00:22:41] Alessio: Versus how you see some of the startup opportunities that is maybe still out there.[00:22:46] Bret: We build most of our tooling in house at Sierra, not all. It's, we don't, it's not like not invented here syndrome necessarily, though, maybe slightly guilty of that in some ways, but because we're trying to build a platform [00:23:00] that's in Dorian, you know, we really want to have control over our own destiny.[00:23:03] Bret: And you had made a comment earlier that like. We're still trying to figure out who like the reactive agents are and the jury is still out. I would argue it hasn't been created yet. I don't think the jury is still out to go use that metaphor. We're sort of in the jQuery era of agents, not the react era.[00:23:19] Bret: And, and that's like a throwback for people listening,[00:23:22] swyx: we shouldn't rush it. You know?[00:23:23] Bret: No, yeah, that's my point is. And so. Because we're trying to create an enduring company at Sierra that outlives us, you know, I'm not sure we want to like attach our cart to some like to a horse where it's not clear that like we've figured out and I actually want as a company, we're trying to enable just at a high level and I'll, I'll quickly go back to tech at Sierra, we help consumer brands build customer facing AI agents.[00:23:48] Bret: So. Everyone from Sonos to ADT home security to Sirius XM, you know, if you call them on the phone and AI will pick up with you, you know, chat with them on the Sirius XM homepage. It's an AI agent called Harmony [00:24:00] that they've built on our platform. We're what are the contours of what it means for someone to build an end to end complete customer experience with AI with conversational AI.[00:24:09] Bret: You know, we really want to dive into the deep end of, of all the trade offs to do it. You know, where do you use fine tuning? Where do you string models together? You know, where do you use reasoning? Where do you use generation? How do you use reasoning? How do you express the guardrails of an agentic process?[00:24:25] Bret: How do you impose determinism on a fundamentally non deterministic technology? There's just a lot of really like as an important design space. And I could sit here and tell you, we have the best approach. Every entrepreneur will, you know. But I hope that in two years, we look back at our platform and laugh at how naive we were, because that's the pace of change broadly.[00:24:45] Bret: If you talk about like the startup opportunities, I'm not wholly skeptical of tools companies, but I'm fairly skeptical. There's always an exception for every role, but I believe that certainly there's a big market for [00:25:00] frontier models, but largely for companies with huge CapEx budgets. So. Open AI and Microsoft's Anthropic and Amazon Web Services, Google Cloud XAI, which is very well capitalized now, but I think the, the idea that a company can make money sort of pre training a foundation model is probably not true.[00:25:20] Bret: It's hard to, you're competing with just, you know, unreasonably large CapEx budgets. And I just like the cloud infrastructure market, I think will be largely there. I also really believe in the applications of AI. And I define that not as like building agents or things like that. I define it much more as like, you're actually solving a problem for a business.[00:25:40] Bret: So it's what Harvey is doing in legal profession or what cursor is doing for software engineering or what we're doing for customer experience and customer service. The reason I believe in that is I do think that in the age of AI, what's really interesting about software is it can actually complete a task.[00:25:56] Bret: It can actually do a job, which is very different than the value proposition of [00:26:00] software was to ancient history two years ago. And as a consequence, I think the way you build a solution and For a domain is very different than you would have before, which means that it's not obvious, like the incumbent incumbents have like a leg up, you know, necessarily, they certainly have some advantages, but there's just such a different form factor, you know, for providing a solution and it's just really valuable.[00:26:23] Bret: You know, it's. Like just think of how much money cursor is saving software engineering teams or the alternative, how much revenue it can produce tool making is really challenging. If you look at the cloud market, just as a analog, there are a lot of like interesting tools, companies, you know, Confluent, Monetized Kafka, Snowflake, Hortonworks, you know, there's a, there's a bunch of them.[00:26:48] Bret: A lot of them, you know, have that mix of sort of like like confluence or have the open source or open core or whatever you call it. I, I, I'm not an expert in this area. You know, I do think [00:27:00] that developers are fickle. I think that in the tool space, I probably like. Default towards open source being like the area that will win.[00:27:09] Bret: It's hard to build a company around this and then you end up with companies sort of built around open source to that can work. Don't get me wrong, but I just think that it's nowadays the tools are changing so rapidly that I'm like, not totally skeptical of tool makers, but I just think that open source will broadly win, but I think that the CapEx required for building frontier models is such that it will go to a handful of big companies.[00:27:33] Bret: And then I really believe in agents for specific domains which I think will, it's sort of the analog to software as a service in this new era. You know, it's like, if you just think of the cloud. You can lease a server. It's just a low level primitive, or you can buy an app like you know, Shopify or whatever.[00:27:51] Bret: And most people building a storefront would prefer Shopify over hand rolling their e commerce storefront. I think the same thing will be true of AI. So [00:28:00] I've. I tend to like, if I have a, like an entrepreneur asked me for advice, I'm like, you know, move up the stack as far as you can towards a customer need.[00:28:09] Bret: Broadly, but I, but it doesn't reduce my excitement about what is the reactive building agents kind of thing, just because it is, it is the right question to ask, but I think we'll probably play out probably an open source space more than anything else.[00:28:21] swyx: Yeah, and it's not a priority for you. There's a lot in there.[00:28:24] swyx: I'm kind of curious about your idea maze towards, there are many customer needs. You happen to identify customer experience as yours, but it could equally have been coding assistance or whatever. I think for some, I'm just kind of curious at the top down, how do you look at the world in terms of the potential problem space?[00:28:44] swyx: Because there are many people out there who are very smart and pick the wrong problem.[00:28:47] Bret: Yeah, that's a great question.[00:28:48] Future of Software Development[00:28:48] Bret: By the way, I would love to talk about the future of software, too, because despite the fact it didn't pick coding, I have a lot of that, but I can talk to I can answer your question, though, you know I think when a technology is as [00:29:00] cool as large language models.[00:29:02] Bret: You just see a lot of people starting from the technology and searching for a problem to solve. And I think it's why you see a lot of tools companies, because as a software engineer, you start building an app or a demo and you, you encounter some pain points. You're like,[00:29:17] swyx: a lot of[00:29:17] Bret: people are experiencing the same pain point.[00:29:19] Bret: What if I make it? That it's just very incremental. And you know, I always like to use the metaphor, like you can sell coffee beans, roasted coffee beans. You can add some value. You took coffee beans and you roasted them and roasted coffee beans largely, you know, are priced relative to the cost of the beans.[00:29:39] Bret: Or you can sell a latte and a latte. Is rarely priced directly like as a percentage of coffee bean prices. In fact, if you buy a latte at the airport, it's a captive audience. So it's a really expensive latte. And there's just a lot that goes into like. How much does a latte cost? And I bring it up because there's a supply chain from growing [00:30:00] coffee beans to roasting coffee beans to like, you know, you could make one at home or you could be in the airport and buy one and the margins of the company selling lattes in the airport is a lot higher than the, you know, people roasting the coffee beans and it's because you've actually solved a much more acute human problem in the airport.[00:30:19] Bret: And, and it's just worth a lot more to that person in that moment. It's kind of the way I think about technology too. It sounds funny to liken it to coffee beans, but you're selling tools on top of a large language model yet in some ways your market is big, but you're probably going to like be price compressed just because you're sort of a piece of infrastructure and then you have open source and all these other things competing with you naturally.[00:30:43] Bret: If you go and solve a really big business problem for somebody, that's actually like a meaningful business problem that AI facilitates, they will value it according to the value of that business problem. And so I actually feel like people should just stop. You're like, no, that's, that's [00:31:00] unfair. If you're searching for an idea of people, I, I love people trying things, even if, I mean, most of the, a lot of the greatest ideas have been things no one believed in.[00:31:07] Bret: So I like, if you're passionate about something, go do it. Like who am I to say, yeah, a hundred percent. Or Gmail, like Paul as far, I mean I, some of it's Laura at this point, but like Gmail is Paul's own email for a long time. , and then I amusingly and Paul can't correct me, I'm pretty sure he sent her in a link and like the first comment was like, this is really neat.[00:31:26] Bret: It would be great. It was not your email, but my own . I don't know if it's a true story. I'm pretty sure it's, yeah, I've read that before. So scratch your own niche. Fine. Like it depends on what your goal is. If you wanna do like a venture backed company, if its a. Passion project, f*****g passion, do it like don't listen to anybody.[00:31:41] Bret: In fact, but if you're trying to start, you know an enduring company, solve an important business problem. And I, and I do think that in the world of agents, the software industries has shifted where you're not just helping people more. People be more productive, but you're actually accomplishing tasks autonomously.[00:31:58] Bret: And as a consequence, I think the [00:32:00] addressable market has just greatly expanded just because software can actually do things now and actually accomplish tasks and how much is coding autocomplete worth. A fair amount. How much is the eventual, I'm certain we'll have it, the software agent that actually writes the code and delivers it to you, that's worth a lot.[00:32:20] Bret: And so, you know, I would just maybe look up from the large language models and start thinking about the economy and, you know, think from first principles. I don't wanna get too far afield, but just think about which parts of the economy. We'll benefit most from this intelligence and which parts can absorb it most easily.[00:32:38] Bret: And what would an agent in this space look like? Who's the customer of it is the technology feasible. And I would just start with these business problems more. And I think, you know, the best companies tend to have great engineers who happen to have great insight into a market. And it's that last part that I think some people.[00:32:56] Bret: Whether or not they have, it's like people start so much in the technology, they [00:33:00] lose the forest for the trees a little bit.[00:33:02] Alessio: How do you think about the model of still selling some sort of software versus selling more package labor? I feel like when people are selling the package labor, it's almost more stateless, you know, like it's easier to swap out if you're just putting an input and getting an output.[00:33:16] Alessio: If you think about coding, if there's no ID, you're just putting a prompt and getting back an app. It doesn't really matter. Who generates the app, you know, you have less of a buy in versus the platform you're building, I'm sure on the backend customers have to like put on their documentation and they have, you know, different workflows that they can tie in what's kind of like the line to draw there versus like going full where you're managed customer support team as a service outsource versus.[00:33:40] Alessio: This is the Sierra platform that you can build on. What was that decision? I'll sort of[00:33:44] Bret: like decouple the question in some ways, which is when you have something that's an agent, who is the person using it and what do they want to do with it? So let's just take your coding agent for a second. I will talk about Sierra as well.[00:33:59] Bret: Who's the [00:34:00] customer of a, an agent that actually produces software? Is it a software engineering manager? Is it a software engineer? And it's there, you know, intern so to speak. I don't know. I mean, we'll figure this out over the next few years. Like what is that? And is it generating code that you then review?[00:34:16] Bret: Is it generating code with a set of unit tests that pass, what is the actual. For lack of a better word contract, like, how do you know that it did what you wanted it to do? And then I would say like the product and the pricing, the packaging model sort of emerged from that. And I don't think the world's figured out.[00:34:33] Bret: I think it'll be different for every agent. You know, in our customer base, we do what's called outcome based pricing. So essentially every time the AI agent. Solves the problem or saves a customer or whatever it might be. There's a pre negotiated rate for that. We do that. Cause it's, we think that that's sort of the correct way agents, you know, should be packaged.[00:34:53] Bret: I look back at the history of like cloud software and notably the introduction of the browser, which led to [00:35:00] software being delivered in a browser, like Salesforce to. Famously invented sort of software as a service, which is both a technical delivery model through the browser, but also a business model, which is you subscribe to it rather than pay for a perpetual license.[00:35:13] Bret: Those two things are somewhat orthogonal, but not really. If you think about the idea of software running in a browser, that's hosted. Data center that you don't own, you sort of needed to change the business model because you don't, you can't really buy a perpetual license or something otherwise like, how do you afford making changes to it?[00:35:31] Bret: So it only worked when you were buying like a new version every year or whatever. So to some degree, but then the business model shift actually changed business as we know it, because now like. Things like Adobe Photoshop. Now you subscribe to rather than purchase. So it ended up where you had a technical shift and a business model shift that were very logically intertwined that actually the business model shift was turned out to be as significant as the technical as the shift.[00:35:59] Bret: And I think with [00:36:00] agents, because they actually accomplish a job, I do think that it doesn't make sense to me that you'd pay for the privilege of like. Using the software like that coding agent, like if it writes really bad code, like fire it, you know, I don't know what the right metaphor is like you should pay for a job.[00:36:17] Bret: Well done in my opinion. I mean, that's how you pay your software engineers, right? And[00:36:20] swyx: and well, not really. We paid to put them on salary and give them options and they vest over time. That's fair.[00:36:26] Bret: But my point is that you don't pay them for how many characters they write, which is sort of the token based, you know, whatever, like, There's a, that famous Apple story where we're like asking for a report of how many lines of code you wrote.[00:36:40] Bret: And one of the engineers showed up with like a negative number cause he had just like done a big refactoring. There was like a big F you to management who didn't understand how software is written. You know, my sense is like the traditional usage based or seat based thing. It's just going to look really antiquated.[00:36:55] Bret: Cause it's like asking your software engineer, how many lines of code did you write today? Like who cares? Like, cause [00:37:00] absolutely no correlation. So my old view is I don't think it's be different in every category, but I do think that that is the, if an agent is doing a job, you should, I think it properly incentivizes the maker of that agent and the customer of, of your pain for the job well done.[00:37:16] Bret: It's not always perfect to measure. It's hard to measure engineering productivity, but you can, you should do something other than how many keys you typed, you know Talk about perverse incentives for AI, right? Like I can write really long functions to do the same thing, right? So broadly speaking, you know, I do think that we're going to see a change in business models of software towards outcomes.[00:37:36] Bret: And I think you'll see a change in delivery models too. And, and, you know, in our customer base you know, we empower our customers to really have their hands on the steering wheel of what the agent does they, they want and need that. But the role is different. You know, at a lot of our customers, the customer experience operations folks have renamed themselves the AI architects, which I think is really cool.[00:37:55] Bret: And, you know, it's like in the early days of the Internet, there's the role of the webmaster. [00:38:00] And I don't know whether your webmaster is not a fashionable, you know, Term, nor is it a job anymore? I just, I don't know. Will they, our tech stand the test of time? Maybe, maybe not. But I do think that again, I like, you know, because everyone listening right now is a software engineer.[00:38:14] Bret: Like what is the form factor of a coding agent? And actually I'll, I'll take a breath. Cause actually I have a bunch of pins on them. Like I wrote a blog post right before Christmas, just on the future of software development. And one of the things that's interesting is like, if you look at the way I use cursor today, as an example, it's inside of.[00:38:31] Bret: A repackaged visual studio code environment. I sometimes use the sort of agentic parts of it, but it's largely, you know, I've sort of gotten a good routine of making it auto complete code in the way I want through tuning it properly when it actually can write. I do wonder what like the future of development environments will look like.[00:38:55] Bret: And to your point on what is a software product, I think it's going to change a lot in [00:39:00] ways that will surprise us. But I always use, I use the metaphor in my blog post of, have you all driven around in a way, Mo around here? Yeah, everyone has. And there are these Jaguars, the really nice cars, but it's funny because it still has a steering wheel, even though there's no one sitting there and the steering wheels like turning and stuff clearly in the future.[00:39:16] Bret: If once we get to that, be more ubiquitous, like why have the steering wheel and also why have all the seats facing forward? Maybe just for car sickness. I don't know, but you could totally rearrange the car. I mean, so much of the car is oriented around the driver, so. It stands to reason to me that like, well, autonomous agents for software engineering run through visual studio code.[00:39:37] Bret: That seems a little bit silly because having a single source code file open one at a time is kind of a goofy form factor for when like the code isn't being written primarily by you, but it begs the question of what's your relationship with that agent. And I think the same is true in our industry of customer experience, which is like.[00:39:55] Bret: Who are the people managing this agent? What are the tools do they need? And they definitely need [00:40:00] tools, but it's probably pretty different than the tools we had before. It's certainly different than training a contact center team. And as software engineers, I think that I would like to see particularly like on the passion project side or research side.[00:40:14] Bret: More innovation in programming languages. I think that we're bringing the cost of writing code down to zero. So the fact that we're still writing Python with AI cracks me up just cause it's like literally was designed to be ergonomic to write, not safe to run or fast to run. I would love to see more innovation and how we verify program correctness.[00:40:37] Bret: I studied for formal verification in college a little bit and. It's not very fashionable because it's really like tedious and slow and doesn't work very well. If a lot of code is being written by a machine, you know, one of the primary values we can provide is verifying that it actually does what we intend that it does.[00:40:56] Bret: I think there should be lots of interesting things in the software development life cycle, like how [00:41:00] we think of testing and everything else, because. If you think about if we have to manually read every line of code that's coming out as machines, it will just rate limit how much the machines can do. The alternative is totally unsafe.[00:41:13] Bret: So I wouldn't want to put code in production that didn't go through proper code review and inspection. So my whole view is like, I actually think there's like an AI native I don't think the coding agents don't work well enough to do this yet, but once they do, what is sort of an AI native software development life cycle and how do you actually.[00:41:31] Bret: Enable the creators of software to produce the highest quality, most robust, fastest software and know that it's correct. And I think that's an incredible opportunity. I mean, how much C code can we rewrite and rust and make it safe so that there's fewer security vulnerabilities. Can we like have more efficient, safer code than ever before?[00:41:53] Bret: And can you have someone who's like that guy in the matrix, you know, like staring at the little green things, like where could you have an operator [00:42:00] of a code generating machine be like superhuman? I think that's a cool vision. And I think too many people are focused on like. Autocomplete, you know, right now, I'm not, I'm not even, I'm guilty as charged.[00:42:10] Bret: I guess in some ways, but I just like, I'd like to see some bolder ideas. And that's why when you were joking, you know, talking about what's the react of whatever, I think we're clearly in a local maximum, you know, metaphor, like sort of conceptual local maximum, obviously it's moving really fast. I think we're moving out of it.[00:42:26] Alessio: Yeah. At the end of 23, I've read this blog post from syntax to semantics. Like if you think about Python. It's taking C and making it more semantic and LLMs are like the ultimate semantic program, right? You can just talk to them and they can generate any type of syntax from your language. But again, the languages that they have to use were made for us, not for them.[00:42:46] Alessio: But the problem is like, as long as you will ever need a human to intervene, you cannot change the language under it. You know what I mean? So I'm curious at what point of automation we'll need to get, we're going to be okay making changes. To the underlying languages, [00:43:00] like the programming languages versus just saying, Hey, you just got to write Python because I understand Python and I'm more important at the end of the day than the model.[00:43:08] Alessio: But I think that will change, but I don't know if it's like two years or five years. I think it's more nuanced actually.[00:43:13] Bret: So I think there's a, some of the more interesting programming languages bring semantics into syntax. So let me, that's a little reductive, but like Rust as an example, Rust is memory safe.[00:43:25] Bret: Statically, and that was a really interesting conceptual, but it's why it's hard to write rust. It's why most people write python instead of rust. I think rust programs are safer and faster than python, probably slower to compile. But like broadly speaking, like given the option, if you didn't have to care about the labor that went into it.[00:43:45] Bret: You should prefer a program written in Rust over a program written in Python, just because it will run more efficiently. It's almost certainly safer, et cetera, et cetera, depending on how you define safe, but most people don't write Rust because it's kind of a pain in the ass. And [00:44:00] the audience of people who can is smaller, but it's sort of better in most, most ways.[00:44:05] Bret: And again, let's say you're making a web service and you didn't have to care about how hard it was to write. If you just got the output of the web service, the rest one would be cheaper to operate. It's certainly cheaper and probably more correct just because there's so much in the static analysis implied by the rest programming language that it probably will have fewer runtime errors and things like that as well.[00:44:25] Bret: So I just give that as an example, because so rust, at least my understanding that came out of the Mozilla team, because. There's lots of security vulnerabilities in the browser and it needs to be really fast. They said, okay, we want to put more of a burden at the authorship time to have fewer issues at runtime.[00:44:43] Bret: And we need the constraint that it has to be done statically because browsers need to be really fast. My sense is if you just think about like the, the needs of a programming language today, where the role of a software engineer is [00:45:00] to use an AI to generate functionality and audit that it does in fact work as intended, maybe functionally, maybe from like a correctness standpoint, some combination thereof, how would you create a programming system that facilitated that?[00:45:15] Bret: And, you know, I bring up Rust is because I think it's a good example of like, I think given a choice of writing in C or Rust, you should choose Rust today. I think most people would say that, even C aficionados, just because. C is largely less safe for very similar, you know, trade offs, you know, for the, the system and now with AI, it's like, okay, well, that just changes the game on writing these things.[00:45:36] Bret: And so like, I just wonder if a combination of programming languages that are more structurally oriented towards the values that we need from an AI generated program, verifiable correctness and all of that. If it's tedious to produce for a person, that maybe doesn't matter. But one thing, like if I asked you, is this rest program memory safe?[00:45:58] Bret: You wouldn't have to read it, you just have [00:46:00] to compile it. So that's interesting. I mean, that's like an, that's one example of a very modest form of formal verification. So I bring that up because I do think you have AI inspect AI, you can have AI reviewed. Do AI code reviews. It would disappoint me if the best we could get was AI reviewing Python and having scaled a few very large.[00:46:21] Bret: Websites that were written on Python. It's just like, you know, expensive and it's like every, trust me, every team who's written a big web service in Python has experimented with like Pi Pi and all these things just to make it slightly more efficient than it naturally is. You don't really have true multi threading anyway.[00:46:36] Bret: It's just like clearly that you do it just because it's convenient to write. And I just feel like we're, I don't want to say it's insane. I just mean. I do think we're at a local maximum. And I would hope that we create a programming system, a combination of programming languages, formal verification, testing, automated code reviews, where you can use AI to generate software in a high scale way and trust it.[00:46:59] Bret: And you're [00:47:00] not limited by your ability to read it necessarily. I don't know exactly what form that would take, but I feel like that would be a pretty cool world to live in.[00:47:08] Alessio: Yeah. We had Chris Lanner on the podcast. He's doing great work with modular. I mean, I love. LVM. Yeah. Basically merging rust in and Python.[00:47:15] Alessio: That's kind of the idea. Should be, but I'm curious is like, for them a big use case was like making it compatible with Python, same APIs so that Python developers could use it. Yeah. And so I, I wonder at what point, well, yeah.[00:47:26] Bret: At least my understanding is they're targeting the data science Yeah. Machine learning crowd, which is all written in Python, so still feels like a local maximum.[00:47:34] Bret: Yeah.[00:47:34] swyx: Yeah, exactly. I'll force you to make a prediction. You know, Python's roughly 30 years old. In 30 years from now, is Rust going to be bigger than Python?[00:47:42] Bret: I don't know this, but just, I don't even know this is a prediction. I just am sort of like saying stuff I hope is true. I would like to see an AI native programming language and programming system, and I use language because I'm not sure language is even the right thing, but I hope in 30 years, there's an AI native way we make [00:48:00] software that is wholly uncorrelated with the current set of programming languages.[00:48:04] Bret: or not uncorrelated, but I think most programming languages today were designed to be efficiently authored by people and some have different trade offs.[00:48:15] Evolution of Programming Languages[00:48:15] Bret: You know, you have Haskell and others that were designed for abstractions for parallelism and things like that. You have programming languages like Python, which are designed to be very easily written, sort of like Perl and Python lineage, which is why data scientists use it.[00:48:31] Bret: It's it can, it has a. Interactive mode, things like that. And I love, I'm a huge Python fan. So despite all my Python trash talk, a huge Python fan wrote at least two of my three companies were exclusively written in Python and then C came out of the birth of Unix and it wasn't the first, but certainly the most prominent first step after assembly language, right?[00:48:54] Bret: Where you had higher level abstractions rather than and going beyond go to, to like abstractions, [00:49:00] like the for loop and the while loop.[00:49:01] The Future of Software Engineering[00:49:01] Bret: So I just think that if the act of writing code is no longer a meaningful human exercise, maybe it will be, I don't know. I'm just saying it sort of feels like maybe it's one of those parts of history that just will sort of like go away, but there's still the role of this offer engineer, like the person actually building the system.[00:49:20] Bret: Right. And. What does a programming system for that form factor look like?[00:49:25] React and Front-End Development[00:49:25] Bret: And I, I just have a, I hope to be just like I mentioned, I remember I was at Facebook in the very early days when, when, what is now react was being created. And I remember when the, it was like released open source I had left by that time and I was just like, this is so f*****g cool.[00:49:42] Bret: Like, you know, to basically model your app independent of the data flowing through it, just made everything easier. And then now. You know, I can create, like there's a lot of the front end software gym play is like a little chaotic for me, to be honest with you. It is like, it's sort of like [00:50:00] abstraction soup right now for me, but like some of those core ideas felt really ergonomic.[00:50:04] Bret: I just wanna, I'm just looking forward to the day when someone comes up with a programming system that feels both really like an aha moment, but completely foreign to me at the same time. Because they created it with sort of like from first principles recognizing that like. Authoring code in an editor is maybe not like the primary like reason why a programming system exists anymore.[00:50:26] Bret: And I think that's like, that would be a very exciting day for me.[00:50:28] The Role of AI in Programming[00:50:28] swyx: Yeah, I would say like the various versions of this discussion have happened at the end of the day, you still need to precisely communicate what you want. As a manager of people, as someone who has done many, many legal contracts, you know how hard that is.[00:50:42] swyx: And then now we have to talk to machines doing that and AIs interpreting what we mean and reading our minds effectively. I don't know how to get across that barrier of translating human intent to instructions. And yes, it can be more declarative, but I don't know if it'll ever Crossover from being [00:51:00] a programming language to something more than that.[00:51:02] Bret: I agree with you. And I actually do think if you look at like a legal contract, you know, the imprecision of the English language, it's like a flaw in the system. How many[00:51:12] swyx: holes there are.[00:51:13] Bret: And I do think that when you're making a mission critical software system, I don't think it should be English language prompts.[00:51:19] Bret: I think that is silly because you want the precision of a a programming language. My point was less about that and more about if the actual act of authoring it, like if you.[00:51:32] Formal Verification in Software[00:51:32] Bret: I'll think of some embedded systems do use formal verification. I know it's very common in like security protocols now so that you can, because the importance of correctness is so great.[00:51:41] Bret: My intellectual exercise is like, why not do that for all software? I mean, probably that's silly just literally to do what we literally do for. These low level security protocols, but the only reason we don't is because it's hard and tedious and hard and tedious are no longer factors. So, like, if I could, I mean, [00:52:00] just think of, like, the silliest app on your phone right now, the idea that that app should be, like, formally verified for its correctness feels laughable right now because, like, God, why would you spend the time on it?[00:52:10] Bret: But if it's zero costs, like, yeah, I guess so. I mean, it never crashed. That's probably good. You know, why not? I just want to, like, set our bars really high. Like. We should make, software has been amazing. Like there's a Mark Andreessen blog post, software is eating the world. And you know, our whole life is, is mediated digitally.[00:52:26] Bret: And that's just increasing with AI. And now we'll have our personal agents talking to the agents on the CRO platform and it's agents all the way down, you know, our core infrastructure is running on these digital systems. We now have like, and we've had a shortage of software developers for my entire life.[00:52:45] Bret: And as a consequence, you know if you look, remember like health care, got healthcare. gov that fiasco security vulnerabilities leading to state actors getting access to critical infrastructure. I'm like. We now have like created this like amazing system that can [00:53:00] like, we can fix this, you know, and I, I just want to, I'm both excited about the productivity gains in the economy, but I just think as software engineers, we should be bolder.[00:53:08] Bret: Like we should have aspirations to fix these systems so that like in general, as you said, as precise as we want to be in the specification of the system. We can make it work correctly now, and I'm being a little bit hand wavy, and I think we need some systems. I think that's where we should set the bar, especially when so much of our life depends on this critical digital infrastructure.[00:53:28] Bret: So I'm I'm just like super optimistic about it. But actually, let's go to w

A Course in Miracles is a clear pathway to take us out of living a troubled and problematic life and into a peaceful existence that is deeply fulfilling. In this episode, Jennifer offers her own understanding of how forgiveness took her from pain to Peace. True forgiveness is a powerful way to liberate from the self-inflicted suffering. To learn more about A Course in Miracles please visit JenniferHadley.com. For the transcript of this episode and more please visit LivingACourseinMiracles.com. We can have a peaceful mind. Learn more about your ad choices. Visit megaphone.fm/adchoices

In this week's "Ask Me Anything" episode, Ryan Michler and Kipp Sorensen tackle the headline topics of overcoming regrets, the power of mission, and why young men need responsibility. They share practical advice on finding purpose, building emotional resilience, and learning from life's challenges. Viewers' questions include reflections on Christmas traditions, dating after divorce, goal-setting for young men, and personal achievements. Packed with humor, heartfelt moments, and actionable insights, this episode delivers a thought-provoking discussion on growth, responsibility, and becoming the man you're meant to be. SHOW HIGHLIGHTS: 00:00 - Episode Introduction 00:44 - Opening and Catching Up   06:13 - The Blackmail Systems in Politics   07:30 - Foreign Drones and Government Responses   14:50 - Best and Worst Christmas Presents   21:18 - Contribution Quadrant Goals   26:28 - Overcoming Regrets and Turning Them Into Growth   36:37 - Family Traditions for Christmas and New Year's   40:21 - Greatest Achievements of 2024   48:17 - Tactics to Overcome Self-Consciousness   57:16 - Tips for Dating in Your 30s   1:03:52 - Goal-Setting for Young Men: Responsibility and Resilience   1:09:23 - Call to Action and Closing Remarks Battle Planners: Pick yours up today! Order Ryan's new book, The Masculinity Manifesto. For more information on the Iron Council brotherhood. Want maximum health, wealth, relationships, and abundance in your life? Sign up for our free course, 30 Days to Battle Ready