Podcasts about Fleet

Declining Russian Oil Production and the Shadow Fleet. Guest: Michael Bernstam. Russian oil production is falling due to aging fields and a lack of investment, failing to meet OPEC quotas. While Russia utilizes a "shadow fleet" to bypass sanctions, it must offer steep discounts to India and China as Brent crude prices decline and fiscal pressures mount. 61944

Recorded live at ACT Expo 2026, this podcast episode features Matt McLelland of Covenant Logistics discussing how the company evaluates diverse fleet technologies, from autonomous vehicles and electric trucks to data analytics. He highlights practical implementations like electric APUs and shares how combining data sources provides the context needed to proactively improve driver safety and wellbeing.

Tom Mueller is driving his candy green Porsche Taycan Turbo S the way he builds rocket engines: with a terrifying amount of instantaneous thrust and little regard for the local speed limits of El Segundo. He is headed west on Marine Avenue, cutting through the smog-tinted sunlight of Los Angeles' South Bay aerospace corridor, talking about Earth's limitations.  “If we continue to grow like we have, eventually you just use up all the metals, you use up all the energy,” says Mueller, 65, who is especially concerned by the energy demand of AI data centers. “By about 2045, the total power that the world is generating right now would be needed just for compute. Exponential growth can crush resources on Earth.” From behind his reflective wrap-around shades, Mueller spots a gap in the afternoon congestion. His electric sports car can rocket from zero to 60 in 2.3 seconds, and Mueller seems eager to demonstrate the point. “This is where we accelerate,” he says, stomping on the pedal. The torque hits like a physical blow, pinning us against the leather seats as Mueller cackles. “The moon and the near-Earth asteroids,” he continues moments later, now parked at a red light, “contain billions of tons of metal, silicon, water and ice, so we have to start using it. It seems a little farfetched to start using it now, because we just haven't built the space economy. We haven't got there yet.” By John Hyatt, Forbes Staff Alicia Park, Reporter Learn more about your ad choices. Visit megaphone.fm/adchoices

Northam is a small town approximately 100KM East of Perth. During WW2 it supported the US Navy's 7th Fleet operating out of Fremantle. The nearby locality of Springhill housed the bunkers of the '7 Naval Ammunition Depot' (7 NAD) storing ordnance the US, British and Dutch submarines needed to take the war to the Japanese. Torpedoes, shells, small arms and explosives were housed there and shipped by rail to the port at Fremantle. 7 NAD was one of three US Naval Ammunition Depots throughout Australia, the others being at Mount Coot-tha, Brisbane and Newington, Sydney.   

Future Missions for Miniaturized Space Technology. Guests: Paulo Lozano and Amelia "Mia" Bruno. With an unlimited budget, Paulo Lozano envisions a fleet of autonomous small satellites exploring near-Earth asteroids for scientific value. Mia Bruno aims to use improved propulsion to reach the moons of Jupiter and Saturn much faster than current missions allow. They also discuss performing complex orbital plane changes using chemical maneuvers. 41953

Big changes are being discussed for Star Trek Fleet Command, and this episode breaks down what players need to know after the latest conversations with Cameron Stewart and the creator community. We talk through Scopely's new focus on tech stability, culture, economy, regular players, seven-day streaks, bulk claim, and why “happy players spend money” might finally be more than a slogan. We also dig into upcoming arc direction, including M92, M93 Anthology, M94's slower experience-driven approach, and the introduction of seasons beginning around M95. Plus, we cover the creator program's changing role, min-maxer feedback, economy repair, officer design, community mod support, and why player feedback may be more important right now than it has been in years.   0:50 Welcome to Talking Trek Live 5:39 Stupid News and opening chaos 13:01 Bundle claim improvements explained 17:14 Multi-claim and faster store interactions 22:00 Backend tech changes and server communication 25:21 Boost mode for high-traffic systems 28:18 Cam's three pillars: tech, economy, and culture 31:48 “Happy players spend money” returns 32:20 Regular Players become the key KPI 37:04 Seven-day streaks and why Cam values them 39:20 Why quality of life should not be a reward 41:19 Community homework: what should the seven-day bonus be? 46:01 Cam's 50+ one-on-one meetings with the STFC team 48:16 Failure, learning, and changing Scopely's internal culture 55:34 David Eckleberry is back in an advisory role 58:13 Engineering council and better technical feedback 1:02:30 M92, playtests, and the culture shift around shipping content 1:03:59 M93 Anthology confirmed as the content pause 1:04:21 M94 described as slower and more experience-driven 1:24:14 Why the creator program is becoming more important 1:31:23 How creator feedback is being routed back to Scopely 1:41:34 M92, M93, M94, and the road to seasons 1:42:04 Seasons begin with M95 1:46:39 Why Scopely wants feedback from hyper-engaged players 1:50:04 The economy problem and why min-maxers matter 1:56:11 Two-way communication and the changing creator program 2:02:25 Officer systems and captain maneuver concerns 2:07:16 Making officers more accessible while monetizing upgrades 2:12:01 Seven-day rewards: efficiency vs quality of life 2:22:01 Recap of the biggest open questions for players 2:24:12 Official community mod is now supported by STFC 2:37:00 Final plugs and closing chaos

This week on the IBA Insider Podcast, hosted by Neil Fraser, CFA, our experts unpack three of the biggest stories shaping aviation today:Fleet Risk Management in Conflict Scenarios – Jordan Amos explores how lessors and airlines can strengthen resilience and protect assets in an increasingly uncertain geopolitical environment.Norwegian's Leisure Bet – James Li-Tremble examines the airline's strategy of owning the holiday experience, not just the flight, and what it means for the wider market.Can African Aviation Weather the Fuel Crisis and Keep Growing? – Dan Taylor discusses the impact of rising fuel costs and the outlook for one of aviation's most dynamic regions.Sign up for the newsletter - https://www.iba.aero/sign-up/LinkedIn - https://www.linkedin.com/company/iba-aviation-consultancy/YouTube - https://www.youtube.com/channel/UCSkPhTf-05htY99V79fklMAWebsite - www.iba.aero

P.M. Edition for June 18. WSJ senior video and national security reporter Shelby Holliday discusses the technology on the dilapidated ships carrying sanctioned oil that makes them a risk around the world. Plus, the Supreme Court rules that not all drug users can be banned from owning guns, expanding the reach of the Second Amendment. And CME, the U.S.'s leading futures exchange, sues the CFTC to stop prediction-market platform Kalshi from diving into the market for the trendy derivatives known as “perps.” Alex Ossola hosts. Sign up for the WSJ's free What's News newslette Learn more about your ad choices. Visit megaphone.fm/adchoices

Michael Bernstam explains that Russia faces a fiscal catastrophe due to declining oil production and falling global prices. He notes that Ukrainian drone strikes and Western sanctions on the shadow fleet are depleting Moscow's budget. (16)

Captain James Fanell emphasizes the critical need for expanded United States naval power to counter China's massive fleet. He advocates for increased ship production and more vertical launch cells to maintain global maritime security standards. (8)

Gregory Copley addresses the crisis in the UK Ministry of Defense, marked by high-level resignations and budget cuts. He describes the Royal Marines' seizure of a Russian "shadow fleet" tanker and a Russian warship firing warning shots at a yacht. Copley argues years of neglect have degraded British naval power. (9)

The Cybercrime Magazine Podcast brings you daily cybercrime news on WCYB Digital Radio, the first and only 7x24x365 internet radio station devoted to cybersecurity. Stay updated on the latest cyberattacks, hacks, data breaches, and more with our host. Don't miss an episode, airing every half-hour on WCYB Digital Radio and daily on our podcast. Listen to today's news at https://soundcloud.com/cybercrimemagazine/sets/cybercrime-daily-news. Brought to you by our Partner, Evolution Equity Partners, an international venture capital investor partnering with exceptional entrepreneurs to develop market leading cyber-security and enterprise software companies. Learn more at https://evolutionequity.com

Send us Fan MailThese special, condensed conversations were recorded at the 2026 U.S. Christian Chamber of Commerce SWC Conference in OrlandoBen Fleet - Corporate Giving Manager for Crossroads Prison Ministries - shares his faith and his impactful work including growing up in a Christian home; putting his faith in Jesus at 14; how 9/11 brought  him closer to Jesus; having criminal justice “in his DNA”; switching over to the ministerial program; how he responded to the threat of pulling funding from his college education; a church plant in Montreal; Crossroads Prison Ministries; correspondence based ministry; bringing hope to their students (those incarcerated); how prison ministry reduces recidivism rates; how bringing hope reduces taxpayer money through prison ministries; and much more! https://cpministries.orgEpisode starts at the 20:47 markRobert & Kay Lee Fukui - Founders of i61 Business Development Network - takes us on their journey of faith, family, and how to help the two work in tandem including Kay Lee growing up in the church and Robert being a PK (preacher's kid); Robert growing up with a “rebellious” spirit; growing up with family as secondary to the ministry; Kay Lee being the catalyst to bring Robert back to church; how an unusually empty tourist stop at the Jordan River in Israel transformed their lives; how their respective upbringings led them to their marriage ministry;  how relationships are really all you have in the end; how the unexpected death of Robert's first wife brought clarity; prioritizing family activities on calendar; spiritual and practical applications to strengthen your marriage; and much more! https://marriedentrepreneur.co/Support the show

Day 1,571.In what could prove one of the most consequential weeks of the year for international diplomacy, Francis and Dom assess what a ceasefire in Iran might mean for the war – and whether it could help unlock a pathway towards peace after another bloody weekend in which a Russian attack left one of Kyiv's most historic cathedrals in flames. They also examine the significance of British Royal Marines boarding and seizing a Russian shadow fleet tanker, and report the latest on Ukraine's EU negotiations as formal accession talks kick off today. Finally, Dom considers the sweeping military reforms now being undertaken by Kyiv that could have profound consequences for Ukraine's armed forces and those fighting on the frontline.Contributors:Francis Dearnley (Host on Ukraine: The Latest). @FrancisDearnley on X.Dominic Nicholls (Host on Ukraine: The Latest). @DomNicholls on X.Producer: Rachel PorterSenior Producer: Lilian FawcettVideo Producer: Sophie O'SullivanSocial Producer: Tom SteedStudio Director: James EnglandExecutive Editor: Francis DearnleyCreated by David KnowlesNOW IN FULL VIDEO WITH MAPS & BATTLEFIELD FOOTAGE:Every episode is now available on our YouTube channel shortly after the release of the audio version. You will find it here: https://www.youtube.com/@UkraineTheLatest CONTENT REFERENCED:Our sister podcast Iran: The Latest: https://www.telegraph.co.uk/iran--the-latest/Trump negotiators to visit Moscow after birthday call with Putin (The Telegraph)https://www.telegraph.co.uk/world-news/2026/06/14/iran-ukraine-g7-witkoff-kushner-russia/ Russia bombs historic Kyiv cathedral (The Telegraph)https://www.telegraph.co.uk/world-news/2026/06/15/russia-bombs-kyiv-cathedral/ Royal Marines seize Russian shadow fleet tanker in Channel (The Telegraph)https://www.telegraph.co.uk/news/2026/06/14/british-armed-forces-russian-oil-tanker-english-channel/ Inside six-hour mission to storm Putin's shadow oil tanker (The Telegraph)https://www.telegraph.co.uk/news/2026/06/14/inside-six-hour-mission-to-storm-russias-shadow-oil-tanker/ EU countries weigh ‘tearing apart' bloc's diplomatic service (Financial Times)https://www.ft.com/content/a7278d93-98fc-4fa7-a14c-d0c089b693dd?syn-25a6b1a6=1 Russian MP warns Putin: We're on the brink of social collapse (Antonia Langford for the Telegraph)https://www.telegraph.co.uk/world-news/2026/06/13/russian-mp-warns-putin-were-on-the-brink-of-social-collapse/ It Was Meant to Unify. Now the G7 Is Dogged by Chaos and Divided by Trump (New York Times)https://www.nytimes.com/2026/06/14/world/europe/g7-summit-evian-trump.html Donald Trump stages show of political domination with UFC bout on White House lawn (Financial Times)https://www.ft.com/content/11f71770-5872-4769-9ea5-a21f12151e10?syn-25a6b1a6=1 EMAIL US:Contact the team on ukrainepod@telegraph.co.uk. We continue to read every message, and seek to respond to as many as possible.HIGHLIGHTS:'Barbarism' as Moscow bombs historic Kyiv cathedralBritish commandos seize Russian shadow fleet ship Hosted on Acast. See acast.com/privacy for more information.

During long flights or extended air combat missions, aerial refueling tankers can eliminate the need for military planes to land. Having this capability is vital for some missions, like rapid long-distance strikes or when landing to refuel isn'…

The Smart 7 is an award winning daily podcast, in association with METRO, that gives you everything you need to know in 7 minutes, at 7am, 7 days a week…With over 20 million downloads and consistently charting, including as No. 1 News Podcast on Spotify, we're a trusted source for people every day and we've won Gold at the Signal International Podcast awardsIf you're enjoying it, please follow, share, or even post a review, it all helps... Today's episode includes the following:https://x.com/SkyNews/status/2066079426022985809/video/1https://x.com/SkyNews/status/2066093111185457324/video/1 https://x.com/atrupar/status/2066152796429115847/video/1 https://x.com/Acyn/status/2066168775708426345/video/1 https://x.com/BBCPolitics/status/2066096913871450600/video/1 https://x.com/SkyNews/status/2066081902130299349/video/1 https://x.com/SkySportsF1/status/2066186072569126950/video/1 https://youtu.be/gvS5GIkPBQg https://x.com/i/status/2065748114632274394 Contact us over @TheSmart7pod or visit www.thesmart7.com or find out more at www.metro.co.uk Voiced by Jamie East, using AI, written by Liam Thompson, researched by Lucie Lewis and produced by Daft Doris. Hosted on Acast. See acast.com/privacy for more information.

Royal Marine Commandos have boarded a Russian shadow fleet oil tanker in the English Channel in the early hours of Sunday morning.Marines, joined by National Crime Agency officers, with the support of the RAF, intercepted and boarded the vessel in a six-hour operation - the first operation of its kind by UK armed forces.The vessel, Smyrtos, will be held and monitored off the south coast of England as investigations continue, the MoD said.Joe Pike joins Laura and Paddy to go through what we know about the operation, and put it into context in light of a week of resignations over the government's defence investment plan.A full list of candidates and loads more information about the Makerfield by-election is available here: https://www.bbc.co.uk/news/articles/cgrp1z8n4w2oYou can now listen to Newscast on a smart speaker. If you want to listen, just say "Ask BBC Sounds to play Newscast”. It works on most smart speakers.You can join our Newscast online community here: https://bbc.in/newscastdiscord Get in touch with Newscast by emailing newscast@bbc.co.uk or send us a WhatsApp on +44 0330 123 9480.New episodes are released every day. If you're in the UK, for more News and Current Affairs podcasts from the BBC, listen on BBC Sounds: https://bbc.in/4guXgXdNewscast brings you daily analysis of the latest political news stories from the BBC.The presenters were Laura Kuenssberg and Paddy O'Connell. It was made by Chris Flynn. The social producer was Jem Westgate. The technical producer was Gareth Jones. The assistant editor is Chris Gray. The senior news editor is Sam Bonham.

Sir Keir Starmer says Russia has been dealt a 'blow' by British forces intercepting one of President Putin's sanctioned 'shadow fleet' oil tankers in the Channel. Helicopters and Royal Navy frigates were involved in the operation early this morning. Also: Israel has carried out fresh strikes on a suburb of Beirut -- after President Trump said a deal to end the fighting between the US and Iran was scheduled to be signed today. And: Lewis Hamilton wins his first Grand Prix as a Ferrari driver.

See omnystudio.com/listener for privacy information.

Podcast guest 1867 is Lori Ann Spagna, starseed & alien contactee who channels a group of non-physical beings called The Collective, which includes the fleet, ascended masters, divine goddesses, angels, interstellar beings and more.Disclosure: As an Amazon Associate I earn from qualifying purchases.Lori's Book: How Psychic Are YOU? 7 Simple Steps to Unlocking YOUR Psychic Potential: The Keys to Accessing Your Intuitive Gifts - https://amzn.to/4dNOeUw #adivasi Lori's YouTube Channelhttps://www.youtube.com/@LoriSpagnaLori's Websitehttps://lorispagna.com/homeLegal Disclaimer:All experiences shared on this channel—including accounts of anomalous phenomena or extraterrestrial encounters—are personal narratives and subjective claims. This content is for educational, documentary and reflective purposes only and is not professional medical, psychological, or legal advice. The views expressed by guests do not necessarily reflect the views of the channel. Please consult a licensed professional for any health or mental health concerns.CONTACT:Email: jeff@jeffmarapodcast.comAmazon Wish Listhttps://www.amazon.com/hz/wishlist/ls/1ATD4VIQTWYAN?ref_=wl_shareTo donate crypto:Bitcoin - bc1qk30j4n8xuusfcchyut5nef4wj3c263j4nw5wydDigibyte - DMsrBPRJqMaVG8CdKWZtSnqRzCU7t92khEShiba - 0x0ffE1bdA5B6E3e6e5DA6490eaafB7a6E97DF7dEeDoge - D8ZgwmXgCBs9MX9DAxshzNDXPzkUmxEfAVEth. - 0x0ffE1bdA5B6E3e6e5DA6490eaafB7a6E97DF7dEeXRP - rM6dp31r9HuCBDtjR4xB79U5KgnavCuwenWEBSITEwww.jeffmarapodcast.comNewsletterhttps://jeffmara2002.substack.com/?r=19wpqa&utm_campaign=pub-share-checklistSOCIALS:Instagram: https://www.instagram.com/jeffmarapodcast/Facebook: https://www.facebook.com/jeffmarapodcast/Twitter: https://www.twitter.com/jeffmaraP/

Rancho Mesa's Alyssa Burley sits down with Rory Anderson, Partner with the Tree Care Group, to talk about how telematics and AI are changing fleet risk.Show Notes: ⁠⁠⁠⁠⁠⁠Subscribe to Rancho Mesa's Newsletter⁠⁠⁠⁠⁠⁠Host: Alyssa BurleyGuest: ⁠⁠⁠⁠⁠⁠Rory Anderson⁠Producer/Editor: ⁠Jadyn Brandt⁠Music: "Home" by JHS Pedals, “Breaking News Intro” by nem0production© Copyright 2026. Rancho Mesa Insurance Services, Inc. All rights reserved.

In "Fleet Profitability Unleashed: The Optimal Dynamics Advantage", Joe Lynch and Zach Schuchart, Senior Vice President, Head of Sales at Optimal Dynamics, discuss how decades of academic research and advanced decision intelligence are being used to automate complex logistics and maximize carrier profitability. Zach Schuchart Zach Schuchart is the Senior Vice President, Head of Sales at Optimal Dynamics. He has over 20 years of experience in the North American and European transportation industries, including roles at UPS, CHAINalytics, and XPO, he brings deep expertise and leadership to the Optimal Dynamics team. As Head of Sales, he oversees a talented group of Account Executives and Solutions Engineers, guiding prospective customers through the evaluation of advanced optimization solutions that drive operational success. About Optimal Dynamics  Optimal Dynamics provides the decision intelligence layer that powers logistics transformation. Born out of 40 years of research at Princeton University, Optimal Dynamics leverages proprietary artificial intelligence technology to automate, optimize, and radically improve decision-making across trucking and transportation operations. Headquartered in New York City, Optimal Dynamics is backed by marquee investors including Koch Disruptive Technologies, Bessemer Venture Partners, The Westly Group, and Activate Capital. Learn more at www.optimaldynamics.com. Key Takeaways: Fleet Profitability Unleashed: The Optimal Dynamics Advantage In "Fleet Profitability Unleashed: The Optimal Dynamics Advantage", Joe Lynch and Zach Schuchart, Senior Vice President, Head of Sales at Optimal Dynamics, discuss how decades of academic research and advanced decision intelligence are being used to automate complex logistics and maximize carrier profitability. From Research to Reality: The Princeton Pedigree. Optimal Dynamics isn't just another tech startup; it is built on 40 years of academic research from Princeton University. This provides a level of scientific rigor and proprietary AI that differentiates their solutions from standard off-the-shelf logistics software. The Power of "Decision Intelligence". While many platforms focus on data visibility (showing you what is happening), Zach highlights the shift toward Decision Intelligence. This layer automates and optimizes the choice itself, helping carriers move from reactive management to proactive, data-driven execution. Bridging the Gap Between Planning and Execution. Leveraging Zach's 20+ years of experience at giants like UPS and XPO, the episode explores how traditional planning often fails when it hits the "real world." Optimal Dynamics focuses on creating dynamic plans that account for the inherent volatility in trucking operations. Leveraging High-Dimensional Artificial Intelligence. The core technology focuses on solving "high-dimensional" problems. Instead of looking at simple variables, the platform uses AI to process thousands of data points simultaneously—such as driver hours, fuel costs, and lane profitability—to find the "Optimal" solution. Automating the Complexities of Trucking. Automation isn't just about replacing manual tasks; it's about augmenting human capability. Zach discusses how their solutions allow sales and operations teams to evaluate complex scenarios in minutes rather than days, drastically reducing the "evaluation-to-action" cycle. Maximizing Profitability in Volatile Markets. In an industry with razor-thin margins, "Optimal Dynamics" means finding the most profitable way to move freight despite fluctuating market conditions. The platform helps fleets identify which loads to accept and how to route them to ensure maximum fleet utilization. Strategic Backing for Long-Term Transformation. The company's growth is fueled by marquee investors like Bessemer Venture Partners and Koch Disruptive Technologies. This level of backing underscores the industry's belief that Optimal Dynamics is a foundational player in the future of global logistics infrastructure. Learn More About Fleet Profitability Unleashed: The Optimal Dynamics Advantage Zach Schuchart Optimal Dynamics | Linkedin Optimal Dynamics Optimizing for the Future: D.M. Bowman Embraces Decision Automation Shifting From Manual Grind to Automated Growth Driving Strategic Growth and Innovation with Decision Automation How Smarter Planning Leads to Stronger Performance Rapid Transformation and Record-Breaking Results at Grand Island Express During Freight Recession, BCB Transport Sees 19.6% Increase in Revenue Per Truck After Embracing Artificial Decision Intelligence The Logistics of Logistics Podcast If you enjoy the podcast, please leave a positive review, subscribe, and share it with your friends and colleagues. The Logistics of Logistics Podcast: Google, Apple, Castbox, Spotify, Stitcher, PlayerFM, Tunein, Podbean, Owltail, Libsyn, Overcast Check out The Logistics of Logistics on Youtube

What does it actually take to break into a male-dominated industry, get passed over because of excuses, and still rise to manage a fleet of nearly 3,800 assets? Shae Davies, Fleet Manager for the City of Aurora, Colorado, joins host Facundo Tassara for the debut episode of the Women in Fleet series on the Fleet Success Show. Shae has nearly 30 years in public fleet, starting as an apprentice mechanic with the City of Seattle and working her way into leadership through grit, skill, and a willingness to be the first. In this episode, Shae and Facundo cover: How a fight with her dad led to a 30-year career in the trades What it means to be the first woman in the room, and what it costs The real story behind managing an aging, underfunded fleet of 3,800 assets How she is building an executive-level capital risk narrative to change budget decisions Why fleet managers need to stop being a line item and start being a business partner The mechanic labor shortage and why wages are going to get very uncomfortable Her hot take on language, respect, and how we talk about women in the trades QR codes on fleet assets and the untapped opportunity to tell your agency's story Whether you are a fleet manager, a fleet director, a tradesperson, or someone thinking about entering the industry, this conversation will challenge the way you think about fleet, leadership, and what the next generation of this workforce needs. Subscribe for more episodes of the Fleet Success Show and the full Women in Fleet series.     Chapters:  0:00 – Intro to Women in Fleet  1:48 – Shae's background and 30 years in fleet  3:19 – The fight with her dad that started it all  5:17 – Getting hired and entering public fleet  6:28 – From mechanic to leadership  10:13 – Being passed over and having to be the first  13:49 – Navigating bias and building resilience  17:30 – Hot take: stop calling women "females"  22:05 – Shae's photo in the US Capitol building  25:37 – Managing 3,800 assets at the City of Aurora  28:52 – Telling the executive story to drive capital investment  32:17 – 230 underutilized vehicles and what the data shows  33:46 – QR codes on fleet assets as community storytelling tools  38:18 – The number one thing impacting fleet today  41:33 – Advice for women thinking about entering fleet  44:38 – Fleet as a business partner, not a department  50:09 – The future of mechanic wages and the labor shortage  55:33 – Closing thoughts and upcoming Women in Fleet guests     Connect with RTA Fleet: https://www.rtafleet.com Learn more about Fleet360: https://www.rtafleet.com/fleet360 #WomenInFleet #FleetManagement #FleetSuccessShow #PublicFleet #FleetManager #Trades #WomenInTrades #MunicipalFleet #FleetLeadership Looking to take the next step to fleet success? Start by requesting your free copy of The Fleet Success Playbook. Written by fleet professionals for fleet professionals, the Playbook breaks down the four key pillars of fleet success, and gives you the tools you need to build a truly great fleet. Request your free (yes, really, free!) copy here: https://rtafleet.com/resources/fleet-success-playbook?utm_source=simplecast&utm_medium=footer_notes&utm_campaign=episode_213 Control fleet chaos with RTA Fleet360, proven software designed by fleet managers for fleet managers: https://rtafleet.com/book-a-demo?utm_source=simplecast&utm_medium=footer_notes&utm_campaign=episode_213

Send us Fan MailFleet Maull inspires Fairfax, Virginia, criminal defense lawyer Jonathan Katz for his extensive experience applying mindfulness with highly challenging situations, making the most of his fourteen years in prison for a drug conviction, and emerging from prison continuing to help inmates and by now helping so many people beyond those in the criminal justice system, with resilience while ready for the dangers that can lurk around the corner. (Check out this month's free online Somatic Healing Summit, where Fleet will be talking.)When Jon Katz first met Fleet over ten years ago at a weekend program that Fleet was leading, Fleet included a great exercise that underlined that we can treat circumstances as neutral, which does not mean the absence of plenty of terrible world events, but that "we, not circumstances, are in charge of our lives and destiny." Radical Responsibliity, by Fleet Maull. Fleet also is great leading guided meditation, which he does early in this podcast episode with a few-minute sit. Fleet was trained in-depth in mindfulness at Naropa Institute (which became Naropa University) before getting convicted for alleged drug trafficking that apparently had taken place a good amount of time before being prosecuted. Fleet spent fourteen years in federal prison. No matter how much of a chunk of his adult life that represented, at least he avoided the even more draconian federal statutory criminal sentencing increases that took hold not long after he got convicted. Fleet does not candycoat his prison experience. He points out the racial disparities in the criminal "justice" system, his coming to terms that the people he was imprisoned with would be his "brothers and sisters" while there, six run-ins that could have taken an awful turn (and many more minor run-ins), the importance of not being passive nor too aggressive in prison, and knowing that people could walk in through an inmate's unlocked cell door and even kill them. Fleet made the best of his prison situation. Helped other inmates along the way, and emerged from prison -- whether immediately or later -- a ball of positive energy and inspiration. This Beat the Prosecution interview with Fleet Maull is riveting. This episode is also available on YouTube https://www.youtube.com/watch?v=fi33kl8qIFQ and Apple Podcasts. https://podcasts.apple.com/us/podcast/winning-with-resilience-while-ready-for-danger-fleet-maull/id1721413675?i=1000772153117This podcast with Fairfax, Virginia criminal / DUI lawyer Jon Katz is playable on all devices at podcast.BeatTheProsecution.com. For more information, visit https://KatzJustice.com or contact us at info@KatzJustice.com, 703-383-1100 (calling), or 571-406-7268 (text).  If you like what you hear on our Beat the Prosecution podcast, please take a moment to post a review at our Apple podcasts page (with stars only, or else also with a comment) at https://podcasts.apple.com/us/podcast/beat-the-prosecution/id1721413675

What if you could consolidate all of your fleet analytics, from toll and bypass data to safety signals, into one cohesive dashboard? Quinn Cochrane of Fleetworthy joins us to explain how they are revolutionizing fleet intelligence by consolidating multiple core products into a single, federated data source! He also shares how a unified vehicle management approach eliminates operational roadblocks for carrier networks and owner-operators and the real-world applications of smart data hydration, highlighting how combining compliance and safety data optimizes workflows, drastically reduces compliance risk, and puts actionable insights directly into the hands of fleet managers and drivers!   About Quinn Cochrane Quinn Cochrane is the Director of Product, Unified Experience at Fleetworthy, where he leads platform initiatives across connected transportation technology, data infrastructure, APIs, and embedded mobile experiences, helping organizations unlock new product capabilities and business opportunities. Quinn is based in the Seattle-area and has spent his career focused on creating scalable platforms that empower both developers and end users. Prior to Fleetworthy, he worked at Amazon. Outside of technology, Quinn is also a competent bagpiper and enjoys bringing a bit of tradition and character to friend and family events.   Connect with Quinn Website: https://fleetworthy.com/  LinkedIn: https://www.linkedin.com/in/quinn-c-93232b12/  

U.S. Customs and Border Protection is moving forward on AI-powered autonomous surveillance towers that are expected to be deployed across the southern border, signing a $71 million task order with GDIT last week. The award is the latest in a massive indefinite delivery/indefinite quantity contract, worth up to $1.8 billion, that kicked off three years ago and is aimed at modernizing and expanding CBP's surveillance tower system. GDIT is a key player in CBP's modernization plans as the prime contractor on a remote video surveillance program, the developer of a CBP database with quantum sensors and a fundamental part of a number of other projects including the smart border wall. Michael Wagner, VP of biometrics, border and transportation security at GDIT, told FedScoop that the company started working on this next-generation autonomous tower about three years ago and has gone through several iterations of solutioning and testing and validating out in the field. The American military deployed an autonomous Corsair maritime drone built by Saronic to find and recover two soldiers who were stranded near the Strait of Hormuz on Monday after their Army AH-64 Apache helicopter crashed during a patrol operation, U.S. Central Command spokesperson Capt. Tim Hawkins told DefenseScoop. The confirmation of this unique rescue mission comes as military tensions are surging in the Middle East amid the United States-Iran conflict. It marks the U.S. military's first publicized use of an autonomous surface vessel to locate and retrieve downed aircrew in real-world warfare, following years of experimentation with different types of sea drones. Hawkins said the drone used in the operation was a U.S. Navy Corsair unmanned surface vessel operated by U.S. 5th Fleet's Task Force 59. In that rescue operation, he told DefenseScoop, the maritime drone picked the two pilots up “and transported them to another location on the water where they were then hoisted up to a helicopter for further transport.” The Daily Scoop Podcast is available every Monday-Friday afternoon. If you want to hear more of the latest from Washington, subscribe to The Daily Scoop Podcast  on Apple Podcasts, Soundcloud, Spotify and YouTube.

Good afternoon, I'm _____ with today's episode of EZ News. Tai-Ex opening  The Tai-Ex opened down 122-points this morning from yesterday's close, at 44,581 on turnover of 8.6-billion N-T. The market staged a technical rebound (技術性反彈) on Tuesday led by the electronics sector, after tech stocks rallied on Wall Street overnight, while buying also rotated to (輪動至) the financial sector, to give an additional boost to the broader market. Lai touts Shinzo Abe's legacy at Tokyo forum  President Lai Ching-te said Taiwan and Japan face identical security challenges along the First Island Chain. In a pre-recorded address at the inaugural (首屆的) Shinzo Abe and Modern Japan International Research Forum in Tokyo, Lai said the late Prime Minister's declaration that "a Taiwan contingency (緊急事態) is a Japanese contingency" highlights the importance of continued peace and stability across the Taiwan Strait. The president also used the opportunity to thank Japan's Prime Minister Sanae Takaichi for continuing Abe's legacy. The forum was cohosted by the National Chengchi University's Shinzo Abe Research Center and the Japan Institute for National Fundamentals think tank… it brought together experts from Taiwan, Japan and the U-S to discuss Abe's legacy and strategy. Hsinchu gas explosion cause under investigation  Fire investigators (調查人員) and police are looking into the cause of an explosion that left two people dead and two others injured in Hsinchu City on Tuesday. The explosion ripped through (炸穿 / 猛烈摧毀) a lunchbox store on Gaocui Road in the city's East District. The blast collapsed a wall onto a neighboring bakery - where the two elderly victims were sleeping. Both were later pronounced dead at a nearby hospital. Firefighters believe the blast was due gas accumulating (累積 / 聚積) overnight inside the lunchbox store after it closed. US Launches New Attacks on Iran Following Helicopter Incident Bahrain has sounded its missile alert sirens as Iran said it targeted the island nation to retaliate (報復) for US strikes. Iran said it had targeted the U.S. Navy's 5th Fleet headquarters in Bahrain, the island nation in the Persian Gulf off the coast of Saudi Arabia. Bahrain's Interior Ministry urged (呼籲) the public to seek shelter. The US launched fresh strikes on Iran following the downing of an Apache helicopter near the Strait of Hormuz, putting any new peace agreement in jeopardy (陷入危險). Mitch McCann reports. … That was correspondent Mitch McCann. Brazil Crackdown on Smugglers of Cuban Migrants Brazilian police have rescued more than 100 Cuban migrants from human smugglers (走私者 / 偷渡集團) at the northern border with Guyana. Officials say the 108 migrants are in custody while authorities work to regularize (使合法化) their immigration status. Five people have been arrested on smuggling charges. The smugglers, known as "coyotes," charged high fees and provided unsafe travel conditions. The operation, conducted Monday, marks the largest humanitarian rescue in the state. Cuban migration to Brazil has surged since 2022 due to Cuba's economic crisis and U.S. sanctions. More affluent migrants often fly to Sao Paulo, while others travel overland through northern Amazon states. That was the I.C.R.T. EZ News, I'm _____. -- Hosting provided by SoundOn

Send us Fan Mail“We're magical beings designed to live magical lives.”-Fleet MaullExclusive Insights from This Week's EpisodesFounder stress turns costly when blame, survival thinking, and reactivity drive decisions. Fleet Maull reveals how radical responsibility protects health, leadership, and freedom.EPISODE HIGHLIGHTS[00:07:00] Fleet rebuilds from federal prison, debt, and a criminal record into executive coaching, consulting, and Inc. 5000 growth[00:17:00] Radical responsibility shifts founders from blame, betrayal, and victim thinking into ownership, possibility, and better decisions[00:24:00] The drama triangle exposes how rescuing, controlling, and being right quietly damage team morale, profits, culture, and trust[00:33:00] Breath, meditation, and self-regulation help founders move from survival reactivity into clearer leadership under pressure[00:46:00] Fleet shares simple breath practices founders can use before high stakes decisions to protect health, clarity, and executionFull show notes, transcript, and resources for this episode:https://podcast.deepwealth.com/549The Deep Wealth PodcastMost entrepreneurs do not fail.They just carry too much for too long.The business grows. Pressure grows faster. Profits get harder to predict. Decisions cost more energy. Over time, focus slips and health takes the hit.The Deep Wealth Podcast and Deep Wealth Mastery are built from real experience. We're the only system based on a 9-figure exit. This system exists because guessing gets expensive.

Fleet electrification is scaling right now. Here is what fleet leaders and infrastructure experts are seeing on the ground. Headlines suggest fleet electrification is stalling, but the people building and operating EV fleets tell a different story. Siemens' Head of U.S. Fleet, Adam Orth, joins Mike Finnern and John Heaton of WSP to unpack what is actually happening across public transit, private service fleets, and the charging infrastructure that supports them. Drawing on real projects and Siemens' own experience, they explain how fleet electrification decisions play out in practice, and why progress looks uneven from the outside. Key takeaways: Why fleet electrification follows many paths, depending on duty cycles, geography, and operations How charging infrastructure and software shape fleet electrification outcomes as much as vehicles do What slows fleet electrification most often, including adoption, change management, and workforce readiness Lessons from Siemens as it passes the halfway point toward electrifying its full U.S. fleet by 2030 If you want a grounded view of fleet electrification beyond the headlines, this episode shows what scaling looks like when real fleets make the shift.

Andrew Bayliss, a classicist from the University of Birmingham, discusses the military strategies of Sparta and Athensduring their historic conflict. He explains that while Sparta was self-sufficient, Athens relied heavily on its fleet for food imports. Bayliss details how Pericles moved the rural population behind city walls, creating a crowded environment similar in size to LAX.MINOAN CRETE

What does fleet management look like when your "shop" spans the entire globe? In this episode of the Fleet Success Show, host Marc Canton sits down with Chief Master Sergeant Adam Walker of the U.S. Air Force at the NAFA Institute and Expo 2026. Adam oversees vehicle management operations across 175 Air Force bases, 100,000 vehicles, and 5,500 military and civilian personnel. His team's mission: keep the vehicles running so the Air Force can fly, fight, and win. The conversation goes deep on the challenges, the systems, and the leadership principles that hold it all together and what civilian fleet managers can take directly from the military playbook. In this episode: How the Air Force manages 100,000 vehicles across 175 global locations Mission Capable Rate, fleet health scoring, and service level agreements: the Air Force way Why the Air Force ran MS-DOS fleet software until 2016 and what they learned from the transition How AI is being integrated into Air Force vehicle management operations The Fleet Gap DoD SkillBridge program and how it can help with your technician shortage Succession planning lessons from an organization that turns over entire crews every 18 months Tabletop exercises, psychological safety, and building leaders who thrive under pressure What civilian fleets get wrong about military fleet operations If you're a fleet manager, fleet director, or fleet leader who wants to run a tighter, more resilient operation, this episode is for you. Speaker Bios Marc Canton Marc Canton is Vice President of Fleet Strategy at RTA Fleet and host of The Fleet Success Show. A recognized fleet industry leader, Marc helps public and enterprise fleets improve performance through data-driven decision-making, operational excellence, and strategic fleet management. Drawing from extensive experience leading fleet organizations and advising fleets across North America, he is passionate about helping fleet professionals solve complex challenges, develop stronger teams, and build fleets they are proud to lead.Adam Walker Chief Master Sergeant Adam Walker serves in the United States Air Force as a Major Command Functional Manager for the Vehicle Management community. In his role, he leads workforce development, training, and talent management initiatives supporting approximately 3,500 military and civilian personnel responsible for maintaining nearly 100,000 vehicles across 175 global locations. Beginning his career as a vehicle maintainer, Adam has served in leadership roles spanning maintenance operations, fleet management, and organizational development. He is also a strong advocate for military-to-fleet workforce transition programs, helping retiring and separating service members connect with career opportunities throughout the fleet industry. Looking to take the next step to fleet success? Start by requesting your free copy of The Fleet Success Playbook. Written by fleet professionals for fleet professionals, the Playbook breaks down the four key pillars of fleet success, and gives you the tools you need to build a truly great fleet. Request your free (yes, really, free!) copy here: https://rtafleet.com/resources/fleet-success-playbook?utm_source=simplecast&utm_medium=footer_notes&utm_campaign=episode_213 Control fleet chaos with RTA Fleet360, proven software designed by fleet managers for fleet managers: https://rtafleet.com/book-a-demo?utm_source=simplecast&utm_medium=footer_notes&utm_campaign=episode_213

The Missouri State Highway Patrol's annual school bus inspections are out, and KMOX wanted to know exactly what goes into keeping a district's fleet of big yellow buses ready for the road. KMOX's Michael Calhoun talks with Travis Warren, transportation operations and fleet manager for Parkway Schools. Warren says Parkway received a 98% score on a recent Missouri state inspection, finding just one brake adjustment that needed to be made, and one faulty signal bulb, both were quickly fixed. 'It's quite a large operation' says Warren. (Photo by Emily Elconin/Getty Images)

0:14 Podcast Introduction0:23 Jonah Series Conclusion2:38 Nineveh Repents4:43 Jonah's Angry Heart12:53 God's Merciful Name19:52 Jonah's Irony Exposed24:08 The Plant and the Worm30:35 Theology Under Pressure34:57 Grace for Nineveh38:49 Good News for AllSign up for my newsletter to receive fresh posts, encouragement, and Bible reflections straight to your inbox. There is a blog post that accompanies this episode at PrMarlon.comConnect with me.Check out our church at Cloverdale.orgThe intro music Fleet of Happy Fingers by Ryan Bell

How do you manage and maintain more than 18,000 connected trucks? Data. Lots of it.Waste Connections' Chuck Palmer explains how telematics, predictive maintenance, safety analytics, and AI help keep vehicles on the road and drivers safe in this episode of HDT Talks Trucking.Hear his thoughts on AI, predictive maintenance, alternative fuels and electric vehicles, in-cab cameras and more.

In this episode of The President's Daily Brief: New satellite imagery is offering a clearer picture of the damage Iran inflicted on U.S. military facilities during the recent conflict, raising important questions about the growing threat posed by drones and missiles—and what lessons the Pentagon may need to learn before the next war. France has intercepted a Russian-linked oil tanker in a move that highlights Europe's continuing effort to squeeze Moscow's energy exports, while Ukraine unveils a new artificial intelligence-powered drone designed to help identify and strike Russian logistics routes behind the front lines. In today's Back of the Brief, Colombia's presidential election is headed to a runoff after a surprisingly strong showing by a right-wing outsider candidate, setting up a contest that could have major implications for U.S.-Colombia relations and regional security. To listen to the show ad-free, become a premium member of The President's Daily Brief by visiting https://PDBPremium.com. Please remember to subscribe if you enjoyed this episode of The President's Daily Brief. YouTube: youtube.com/@presidentsdailybrief Lean: Get 20% off plus free rush shipping when you go to https://TAKELEAN.com and use code PDB Tax Relief Advocates: End your tax nightmare today by visiting us online at https://TRA.com or call 800-583-6515 Cardiff: Get fast business funding without bank delays—apply in minutes with Cardiff and access up to $500,000 in same‑day funding at https://Cardiff.co/PDB Learn more about your ad choices. Visit megaphone.fm/adchoices

I'm excited to work with Microsoft once again as the presenting sponsors of the AI Engineer World's Fair! We'll streaming live from MS Build today for a special crossover pod with our friends at No Priors and the one and only Satya Nadella. However we did not hold back with this interview - we asked all the burning questions about uptime and Copilot that we know you have in your minds. Lets go!For almost two decades, GitHub has been the home of software, where both open source and closed flow, through commits, pull requests, reviews, actions, etc.This ecosystem flourished as open-source maintainers and contributors would continue shipping code for the benefit of the community. However as coding agents began to ship mass quantities of code - growing 1400% in 2026, it marked a new era that was both extremely exciting and challenging for GitHub.While these agents help more people ship more projects, they also significantly increase the floor of how much code is shipped, how often it is shipped, how many people commit code, and basically orders of magnitude multiples in every dimension of GitHub infrastructure:Now GitHub inevitably experiences more pressure on their infrastructure which was originally designed around human developers moving at human speed. This has resulted in a very publicly notable uptime story:So it begs the question of whether current systems around code can absorb what AI produces. Can CI/CD keep up when every idea becomes a build? Can open source maintainers survive floods of AI-generated slop contributions? Can GitHub preserve the human social contract of software while becoming the operating layer for agents?Which brings us to the perfect person to answer these questions: GitHub COO Kyle Daigle. In this episode, he joins swyx to unpack what happens when AI doesn't just autocomplete code, but starts changing how companies operate, how open source works, how pull requests get reviewed, and how GitHub itself has to scale. We go deep on GitHub's internal AI workflows: micro-skills, WorkIQ, MCP, Slack, Teams, email, Copilot workflows, the new Copilot desktop app, CLI, cloud agents, and how Kyle uses agents to look backwards across company context before deciding what to do next. Kyle also reflects on GitHub's history building webhooks, APIs, Actions, npm, Dependabot, and Semmle, why the AI era is breaking GitHub in new ways, how Actions became a general-purpose compute layer, and what Copilot becomes after code completion.Full Video PodWe discuss:* Kyle's expanded role across GitHub* How AI got Kyle coding again after years in leadership* Why GitHub rolls out AI through existing workflows instead of forcing new tools* WorkIQ, MCP, Slack, Teams, email, and GitHub as company context* Why massive “mega-skills” are giving way to small, atomic micro-skills* How AI changes summarization, communications, marketing, and analyst work* Why former developers in leadership may have a unique advantage in the AI era* Kyle's “15 agents on Saturday” workflow* How Kyle built an AI-generated executive presentation for CRO/CFO teams* Why AI changes the chief of staff role without removing the human work* GitHub Actions, webhooks, arbitrary code execution, and secure agent compute* The npm acquisition, supply-chain security, 2FA, and token invalidation* Slop forks, vendoring, and whether AI agents change dependency management* What pull requests become when most PRs come from agents* Prompt requests, vouching, AI review, and trust in open source* What counts as a “developer” when AI lowers the barrier to building* GitHub Spark, low-code, and why GitHub refuses to hide the code* 14x commit growth, Actions load, databases, monorepos, and availability* Copilot's evolution from completion to CLI, desktop app, cloud agents, and SDK* Context, memory, rules, and making GitHub “act like Kyle wants it to act”* Ambient AI, OpenClaw, enterprise security, and the new operating system for agents* What swyx should ask Satya Nadella about Microsoft's AI futureKyle Daigle* LinkedIn: https://www.linkedin.com/in/kyledaigle* X: https://x.com/kdaigleTimestamps00:00:00 Introduction00:03:36 Why AI Got Kyle Coding Again00:07:04 Running GitHub with AI: WorkIQ, MCP, Slack, Teams, and Skills00:15:39 The Golden Age for Former Developers in Leadership00:17:31 15 Agents on Saturday and AI-Generated Executive Work00:20:20 How AI Changes the Chief of Staff Role00:21:45 GitHub's History: Actions, npm, Webhooks, and Open Source00:28:45 Slop Forks, Vendoring, and AI Dependency Management00:33:57 Pull Requests, Prompt Requests, and Trust in Agent-Generated Code00:41:21 GitHub Stars, 200M+ Developers, and the New AI Builder Wave00:45:15 GitHub Spark, Low-Code, and Why GitHub Still Shows the Code00:47:38 GitHub's Hardest Era: 14x Growth, Reliability, and Scale00:59:21 Actions as the Compute Layer for CI/CD and Automation01:02:04 The State and Future of GitHub Copilot01:08:24 Ambient AI, Background Agents, and the Future of the SDLC01:13:09 OpenClaw, Enterprise Security, and the New OS for Agents01:18:03 Build Announcements, WorkIQ, FoundryIQ, and Microsoft Context01:21:41 What Should swyx Ask Satya?TranscriptIntroduction: Kyle Daigle's Expanded Role at GitHub and MicrosoftSwyx [00:00:00]: We're here with Kyle Daigle, COO of GitHub. Welcome.Kyle [00:00:07]: Hey, thanks for having me.Swyx [00:00:08]: You're not just CEO of GitHub. People know you as that. You have a new role.Kyle [00:00:11]: So I have an expanded role now. I've been working at GitHub for thirteen years and doing all things developer. Joined as a developer myself. And now, I'm also responsible as the CMO of Developer for Microsoft. And so all the kind of learnings and passion for developers and how we work with them and how we communicate and how we bring our products to market, we're also bringing that expertise to the broader Microsoft ecosystem and helping every developer that uses a Microsoft product or would like to have a sort of similar experience that they've had with GitHub over the years. So it's a different role in some ways, but it's also just building on the experience that I've had at GitHub of just sort of tell the truth, be authentic, show people how to use it and then let the products speak for themselves. Now just doing that with, all of Microsoft.Swyx [00:01:09]: We'll be releasing this in conjunction with Build. You got lots of stuff planned, and we can sort of touch on that whenever it's appropriate. I think one of the interesting things is I rarely meet a COO who's also a CMO. I think you're a very outward facing and you're very confident publicly. That's rare. Do you actually view yourself as COO? What's What is your thing?From GitHub Developer to COO/CMO: Building the Platform and Operating GitHubKyle [00:01:33]: I think for me, it's been funny. The titles have always been, a— have always felt a little strange to me. I joined GitHub as a developer? I wrote so much of theSwyx [00:01:46]: Let's bring that up. You wrote the back ends?Kyle [00:01:48]: I was going through, I was going through, some old photos, when folks were talking about how things were being built or how there was a build GitHub. I built, webhooks and worked with teams building the API, built the platform layer. Anything that integrated with GitHub, up until really twenty eighteen, I built or ran the engineering teams. And that's kind of where my the beginning of my passion always was helping people build things, deliver them to, their customers. And so being a developer, building for developers was always super unique. In a— I think as my role expanded, it became my ability to talk to not just developers, but also enterprise customers or business leaders and have this translation layer. And then through all those years, GitHub has always operated pretty uniquely. Post-pandemic, working remotely was not as novel as it was when GitHub started in two thousand and eight. But all that expertise of running remote teams, doing it well, became this sort of bigger role, ultimately turning into the COO role of how do we operate GitHub in the way that GitHub's always operated after the Microsoft acquisition. And kind of so on from there. So like for me, I think the— I've, I still code. I love coding but the problem has always been, people. It's a much harder problem to both support our own employees, a harder problem to communicate to developers and enterprise buyers what we're building why it matters, ‘cause those are two very different messages. And so getting to work in the mix of COO, CMO, also just being a dev, I think is what's kept me at GitHub for so long.AI Workflows for Leadership: Commits, Retrospectives, and ContextSwyx [00:03:40]: Apparently, you have— your commits have gone up. What's this? What's going on?Kyle [00:03:45]: Rui's called me out pretty aggressively. So I think— as you can imagine, right, you can see my normal era of being a dev In the twenty thirteen, twenty fourteen era, and then moving into management, and then ultimately the COO role. I think what you see there is me, really getting back to coding thanks to AI. I— similar to, attaching problems between how to market and how to operate a business and how to code, I find, building agents and workflows that are connecting very disparate problems to be what's driving this. So that's, some of it's writing software. A lot of it is, connecting a ton of a different data sources to, help me out. But that is completely me really diving in on the AI side in trying out our tools, trying out everyone's tools, But building for me, building for the non-technical leader, though I'm technical and how we're, able to use these tools more than just the simple, call and response that I think a lot of the non-technical, your employers, you have to get— you have to use AI, and so everyone uses, ChatGPT or Copilot or Claude or whatever. To really get into, how is this going to help me out, it— I find that it's not the I need to write a blog post, I need to those simple examples. Helping people find the workflows of, “Okay, I need you to go through all the PRs today. I need you to go through everything that we've posted online. I need you to go through what we did the last three months. Go through all of my Obsidian notes for any mentions of this then go through my transcripts at work.” We use, Teams, so, using WorkIQ, go call that MCP server, grab all the transcripts, go through all the Slack, and then build me out the plan of, what this week's messaging actually was. That's something that was, impossible because for me, I find AI in a what most of this launch here is actually, less building forward. It's actually, a recursive loop backwards. I'm always looking at what had happened first. Go back through the week and tell me what we did, what worked, what didn't work? And then tell me in the next three or four days-What would you tweak based on this sort of like looking backwards and then looking ahead a little bit? I find that to be so much more valuable, especially for like non-technical, because that retrospection is actually LLMs are very good at that. Like finding all the patterns, pulling them out, and then applying that retrospection to just a couple of days or just like a short period of time. Is all a bunch of apps that I've built and launched a bunch of, internal tools. I use the new, GitHub Copilot app, the desktop app with workflows. Every time I crack open my laptop, it's running workflows for me. It's just a ton of different stuff and of course, it all ends up on, it all ends up on GitHub.Swyx [00:06:47]: Of course. That's where, that's where, stuff is hosted. Man, there's so much to ask you. I was going to leave the how do you run a company with AI thing at the end. I have to ask one— double click one thing. You said, you are looking back at the week. You're, you're understanding what happens. When you say we That's three thousand people. How?Rolling Out AI Internally: Skills, CLIs, and Company ContextKyle [00:07:09]: I think when we started rolling out AI internally beyond engineering, right? One of the things that I was really, passionate about is like we have to do this in a way where no one has to change how they work. I don't want to have to teach you a tool. I don't want to have to teach you something new. And so for us, we tried out a few tools. Most of them don't work because I got to get you on board? I got to teach you how to use it. What we've actually ended up doing is we've built like a set of skills internally. We have we each have our set of skills, and we've just been distributing even to the non-technical folks, the CLI. And then effectively, we're just giving it access to like read about everything that we're writing. So that's for us, that's usually GitHub, Teams, Email, and Slack. So Teams for, video chat, generally speaking.Swyx [00:08:03]: Teams and Slack?Kyle [00:08:04]: so we use Teams for video communication, but we don't use it for chat. W-we— GitHub for a long history, right? We're alwaysSwyx [00:08:13]: Also SlackKyle [00:08:14]: Talking about ChatOps and like everything is built into Slack. Like every command, every flow.Swyx [00:08:18]: So even though you have been acquired for I don't know, eight years nowKyle [00:08:22]: we stillSwyx [00:08:23]: You still use Slack?Kyle [00:08:23]: it's a purpose-built tool for us, and I think the reality is that moving off of it would be so bluntly expensive? Simply because all the tooling is, baked in with that paradigm. And they both have their pros and cons but they don't work the same way at all. We still use a bunch of different tools Because it's the purpose-built tools that We need. And thenSwyx [00:08:47]: Well, the same doesn't go for the rest of Microsoft, presumably.Kyle [00:08:50]: like the like various teams like operateSwyx [00:08:53]: They make their own decisionsKyle [00:08:54]: Various ways. I think it just matters what you're trying to what you're trying to do. But we do we do work across kind of every tool that we use, and then by giving everyone access to all of that context and the new WorkIQ MCP server, which is quite cool if you do live in the M365 like world. I can ask it all these backwards-facing questions, and it's incredibly important for our teams that are working remotely. There's a lot of stuff you miss when you're not in an office, and we are spread out all over the world. So most of that is looking back. And then we post, we post either auto-automatically into GitHub issues or discussions, these sorts of like findings or like our industry reports. Like what's happening this morning, today, yesterday. A little automation gets run. We'll use the app. We might use GitHub Actions like with, our agentic workflows just to go do that run, and then we push it into GitHub, and w-we keep having a conversation. So usually for us, it's about that sort of like looking back, looking forward on the non-technical side. And then of course for a lot of those folks, it's also building an app, pushing it to GitHub pages or pushing it somewhere to host it et cetera. But it's just like enabling everyone with that power of it's going to take me a week to figure this out. Instead, we're going “Okay I built a skill. Let's put it into a repo. We'll all share that skill together, and then we'll use the CLI or now the app-” “just to run it.”Micro Skills vs. Mega Skills: How GitHub Uses AI at WorkSwyx [00:10:26]: All right. I think, I think we're going straight into like the team management and productivity thing. I think a lot of people are getting various levels of LLM psychosis. How do you manage the bloat of skills? Like everyone Has their thing, and they're Like trying to promote it to the rest of their peers in their org, right? And obviously, whoever becomes a skill influencer internally becomes like an AI leader, right? Of sorts. I assume you have those.Kyle [00:10:50]: like I think we haveSwyx [00:10:52]: And I assume it's a mess a Yeah.Kyle [00:10:54]: there's like I— like I think the reality is there's two pieces. Like first is I think that we're ending the era of these like massive, beautiful, perfect skills that are just like not any of those things. ‘cause for a while, right every tweet every day is like go download the skills, the perfectly managed thing to do this entire workflow. And I think that like what we've found and what— I was just with my team, this week, and we were talking about the skill side, and we're really talking about these like incredibly micro skills that are just doing one thing for us very well Versus a skill that's going to do I said, that full report. That doesn't really exist on our side anymore. It's usually how do— like a single skill that's going to identify the most important marketing information given any MCP server. Like this is the most important thing. Less about stitch a bunch of tools together and have it produce this mega output because then weeks go by, months go by, things change, and you want to tweakSwyx [00:11:58]: It's brittleKyle [00:11:58]: Your mega skill and you're screwed? You can't do that. And so now we're really just talking about the Legos we're using and just letting the instruction book be something we're all putting together. Whereas I think a lot of AI skills for a while have been that mega instruction book style.Swyx [00:12:15]: I've, thought a lot about Postel's law. I don't know if that's a term that is, means things to folks. It's the idea that you should be liberal in what you accept and strict in what you output, right? And I think that's like a good framing principle for skills. This is my skills, obviously on GitHub. I feel like everyone should have like how like some repos In GitHub are special repos? I feel like we should sort of reify the slash skills and everyone like give it some kind of special presentation. Anyway, so, yeah, this is one of those like download Download anything, transcribe anything, and then you can string together the atomic skills that do one thing well Into like some kind of orchestration skill that calls other skills. I assume, does that match?Kyle [00:12:56]: I like I think so. I think that theSwyx [00:13:00]: Summarize anything.Kyle [00:13:01]: Like I think the- For me, summarizing something for I do communications and PR and analyst relations and marketing and customer activities, and so my summarize everything is very different for each one of those like Contexts. What ‘Cause if I'm summarizing something for an analyst, that's a very different thing than, probably how I'm going to summarize something for like a customer meeting or an engagement. So that's I think like the difference when we're talking about the like the tools I might use on Saturday or the skills I might use on a Saturday when it's just for Kyle. Yeah, those are kind of like they have an atomic actual tool underneath or maybe skill, and then Kyle cares about X. But I think when we're talking about work and enabling the the marketers, communicators there, it's the atomic, this is what good summarization is, and then this is what I care about as for marketing for communications For whatever. And that I think is like the interesting matrix problem when we go from like a developer set of concerns to all kinds of different professions, is that what that word means to me is different than it means to you is different than it means to the analyst or the salesperson, and that's where I think the matrix mess is that we're starting to like still starting to find. It's about these mega skills but they're all just slight permutations, but those permutations are really important. It's the difference between someone reading this and going “Did AI make this?” what Or “This makes total sense, and I would expect this when I'm giving a briefing to Gartner,” or like whatever else.Swyx [00:14:37]: I think the beauty of it maybe is that you don't have to be that careful about what goes in there. It doesn't have to exactly fit as long as it like roughly is contained in there. I used to complain about plugin hell, basically. Like when you have a framework and then you have a hundred things that you need to integrate, everyone does like the GitHub used to be bloated full of these things. And now we don't need them anymore ‘cause now you just use skills.Former Developers in Leadership: AI as a Creation MultiplierKyle [00:15:00]: And like I think the most magical thing is the just that like I can just also crack it open. Like Like yes, I could go like change the how the plugin is coded, or like I could go do that now with AI, but I think there's just something more magical about getting a response back and being “That's not right,” and then you just crack the skill open, you just type English words and it's different. That building block is just, I think very unique. Once I get everyone to kind of understand how to best how to best make those changes to get the most power out of them.Swyx [00:15:36]: Is there a— you have a your peer group that Of people like you. Is there a common framing for Something I'm feeling is, which is true, is that is this a golden age for former developers who are now in leadership? Because you can wield the tools, you would know the right words, you're maybe not too close to the details. Doesn't matter. But like you're more effective than someone who doesn't come from that background.Kyle [00:15:59]: I think that like the secret has always been your ability to identify patterns and solve problems, and I think that for folks that like myself that don't code day to day anymore, that has made me successful as a developer, made me successful as a COO and now CMO. And so now that I have access to get and write code, I'm now applying that sort of like pattern finding and problem solving, and I know enough still about how to then go and say, “Oh, I want to make an app, but I don't want to break into jail or create something that's not going to be able to work or to be deployed scale or whatever.” that ability to apply all that additional business knowledge and still code I think is what makes that so interesting to me. Slightly different than I think some of the other like technical leaders that became business leaders and now are going back to their apps and updating them. Good for them? But I think the more, much more interesting thing is, well, now I have this whole new set of expertise over ten plus years. Why not take that and use that as a developer with these AI tools? So I definitely think that makes me more powerful, but I think that's true for like every dev as well. Most of the dev friends I still have also have some other underlying skill and passion. There's really talented, very kind of linear computer science software devs, absolutely. I just find that the folks that came from a different career, went to school for something else, went off and did this random thing, and then became a software dev, or were a dev, did a random thing, came back. Learning that extra set of information, learning those extra skills, and now having the power of an AI where I can crank up fifteen agents on Saturday while my kids are doing lacrosse, That's like really powerful. And I think it gets me back to that feeling of like creation, and it's very hard to replicate that in most other senses? That first time you build an app and you click it and you show someone that's magical. And so being able to do that not just in code, but across all kinds of different assets that's, that's huge. We were doing we're doing our every year we do our revenue planning. We talk about okay, what is it going to look like for next year? And of course as you imagine, there's, slideshows everywhere talking about what are we going to talk about, what's the narrative, et cetera. And so as you said I'm “Okay, well, I could probably just like build something to build this and then that way I don't have to go build the whole spreadsheet or I have to pass it to my team.” So we went through this process, and I got all the information and used the skills I mentioned. I built like a little app just to make it so I could look at some of the information in a SQLite database, more easily. And I ultimately built this entire presentation without touching any of it and I was “Okay, I'm just going to present this to our CRO, the CFO, their teams,” without mentioning I'd built it with AI. I like built a skill to make it look very much not AI driven. Just not pretty.AI-Generated Presentations, Human Taste, and the Changing Chief of Staff RoleSwyx [00:19:03]: Like a design. Yeah.Kyle [00:19:03]: Not pretty. But just like very clearly not AI. Kind of like don't do anything interesting.Swyx [00:19:08]: That's, yeah, that is valuable.Kyle [00:19:08]: Just go Exactly. We did the whole thing through. It used my notes from Obsidian, it used all the context I mentioned before, the plans, and Never came up once that it was AI generated.Swyx [00:19:20]: It didn't matter.Kyle [00:19:20]: Never once. D It didn't matter. And so now I takeSwyx [00:19:23]: This is a toolKyle [00:19:23]: I can take that tool and go, “Look, I don't want you to go build slideshows.” They're just helping us share information with each other. If this thing can do it With a little bit of crafting from you and then we can look at it together, awesome. There's no value in all that extra work. I think that the ability to, make it look humanly bad and and build a little app to, manipulate the data I think is part of, that upside for devs that are now in leadership roles. Because, the thing that I feel like I said before, this that's all a people, that's all a people problem. I know if you've used a coworker or not to build a slide deck, unless you spent a bunch of time to not do it.Swyx [00:20:07]: I know, but like it was so, I think there's a certain charm to just being blatantly AI. ‘Cause I think that you're well, you're just honest about There may be mistakes here that I cannot vouch for. So how much value is there? But anyway I think, actually the real question I want to ask is, there's a— You were a chief of staff To Thomas. And in the pre-AI world, the that job would've been a chief of staff job of like Can you prep me these slides and all that? And now you do it yourself.Kyle [00:20:35]: I still, I still have a chief of staff. Because, the difference is it's sort of the discussion every time we have some sort of technology evolution is it's not that the jobs the roles don't all go away, they just change? And so yeah, I don't have someone spending all their time building out slides for me and presentations ‘cause I don't need that anymore. But now I need that person that is able to go and find all the different connections between humans in those discussions to help me find out, okay, I should be meeting with this group and this team, and they have an opportunity, and I'm going to be in San Francisco today, I'm going to be in Seattle tomorrow. Those sorts of human connection aspects are still incredibly valuable and has always been a big part of that chief of staff role. But now just like chiefs of staff are not opening up, letters to process, they're doing emails. What It's the same thing. And now they're, they're not building out as many of these presentations because they have the the ability to have a AI take it on for, and share that with me and great. Let's keep moving ‘cause it's allowing us to go faster and make better decisions more quickly.Swyx [00:21:45]: Awesome. Well, so we can dive into more sort of, Productivity insights as you go. I did want to do a little bit of a brief history of colleague and hub. Because, we started here. And then you also involved the NPM acquisition. I did, I do want to touch upon that. And then more recently, I just want to bring up to present day where we're having uptime issues Which transparently we've already Addressed publicly, but we'll, we'll discuss in the pod. Did I miss anything? Like what, any other major highlights? Obviously, it's, it's a lot of years to cover.A Brief History of GitHub: Webhooks, Actions, Acquisitions, and Platform EvolutionKyle [00:22:15]: No the I think one of one highlight was right before the acquisition closed in twenty eighteen, I got to launch the first version of ActionsSwyx [00:22:27]: OhKyle [00:22:27]: At GitHub Universe. So it was OSwyx [00:22:29]: They're that young?Kyle [00:22:30]: It was October of twenty eighteen, I think. Yeah. Yeah.Swyx [00:22:33]: Gee, Jesus.Kyle [00:22:34]: I got to I was the engineering leader on that project and got to launch that. And then, yeah, we did acquisitions of NPM you said, Semmle, Dependabot Pul Panda a whole bunch of things. That was a bigSwyx [00:22:47]: Pul Panda.Kyle [00:22:48]: Abi is doing well.Swyx [00:22:51]: DX. Holy crap.Kyle [00:22:52]: Did well on DX. I and like that was a that was the big shift, after the acquisition. I had to join the sort of business side.Swyx [00:23:00]: So I need to hit you on some of these things ‘cause you were there. Right? And how often do I get to talk to someone who was there? But yeah, Actions. Is that the number one source of security issues on GitHub?Kyle [00:23:11]: Oh, sh I think that the number one source of, security issues is probably like all, the literal code in everyone's like underlying repositories. I would say back further than that is, if you remember I had to show in this graph was this is, I'm, didn't say this before, this is ultimately webhooks.Swyx [00:23:30]: You yeah.Kyle [00:23:31]: Like circa whatever it was.Swyx [00:23:32]: It says Hookshot in there.Kyle [00:23:32]: I forget. Yeah. Yeah, Hookshot's in there. And so like back then, it says GitHub Services. Do you see, it says Hookshot FE for front end, and then it says GitHub Services. GitHub Services back in the old days, right? You we had a repository that was Ruby code, and you could write any Ruby code in there, and then we would execute that On your behalf As a service, and then that way if an if you were trying to integrate with something, it didn't we would run it for you.Swyx [00:23:57]: And of course no containers ‘causeKyle [00:23:58]: No, ‘cause it wasSwyx [00:23:59]: Well, no containersKyle [00:24:00]: Twenty fourteen. And so there was some isolation obviously, but it was mostly the separations on the server level. That's like an example as long as the very old version of Pages, which ran on its own containerization infrastructure, not on Actions.Swyx [00:24:15]: Which like all-time great product.Kyle [00:24:16]: Pages powers the internet at this point to some degree. Those were places where like clearly there were no like issues like to my knowledge. But it was those things where I'm looking at and going “Okay, well we can't be running arbitrary Ruby code,” like on everyone's behalf. Then containerizing all of that up intoUh into actions now where yeah the containerization, is r-really good. The pinning most folks aren't pinning it the like to a particularSwyx [00:24:48]: ImagesKyle [00:24:48]: Sha, et cetera like their workflows, and so that's a big that's a big place Of pain for folks if they're just doing similar to any dependency management, just V1 or newest or latest, I think. But, that journey from that day to “Okay, we're just going to run all this arbitrary code, and, it'll basically be okay,” to now, no, we have, really good containerization. We have a new, underlying, ag-agent, containerization, service. It's like we're using it under the hood. It's through Azure. They recently announced it. The Azure, Dev Compute, but it's, very fast, very fast compute to be able to, spin up your own cloud agents, or whatnot. We're using it under the hood for some parts of the new,Swyx [00:25:36]: Microsoft Dev Box?Kyle [00:25:37]: No. Dev Compute, yeah.Swyx [00:25:41]: Hmm. Not finding it just yet.Kyle [00:25:44]: Oh, it's, it's in there somewhere.Swyx [00:25:46]: All right. Well, we'll cut that out.Kyle [00:25:47]: Sorry. But with, Dev Compute, you can, run, really fast, spin up really, small VMs really quickly, so you're doing a tool callSwyx [00:25:58]: Same conceptKyle [00:25:58]: Just do it containerize exact-exactly. So we're using that so definitely moving that direction to protect us from every every piece of code that we're ultimately running.Swyx [00:26:07]: look, that grows into the full SDLC? Code hosting was just the start and and then it's grown beyond that. Let's talk about NPM may-maybe ‘cause I think that's also, a very major point in the industry. I do think, it was looking for a home. It was, kind of struggling as a business, right? I don't know, I don't know how you would characterize that whole acquisition and how itNPM, Package Security, and Keeping the Internet RunningKyle [00:26:33]: like when we were talking to the team, I think the big thing for the both of us was to find a way to keep NPM, which was basically powering the internet then and way more so now to some degree running. Keep it going keep continuing to scale. It was having scaling problems, if I recall, back at that time. They were doing some rewrites. ItSwyx [00:27:00]: that's cute compared to now.Kyle [00:27:01]: Well, that's the thing is like when I'm talking to folks now, there's there's so many more underlying uses of NPM than there were back when we had them join in with GitHub. But that was ultimately the goal. It was really okay, we used to have pages. We have, the world's code. Let's make sure that we can keep NPM running well for the world. And we put a bunch of time and investment into fixing some of the underlying backend, changes, some of which we talked about some of the manifest work, et cetera. And then now, really trying to bring the the security posture of NPM up to speed. But, it is a unique challenge in that every move that we make to make it more secure will break a lot of people. And security is paramount. And also, we take it very seriously. We're, the any time that we have a problem with GitHub or we make a change that makes us more secure but hurts, there's, a snow day for developers or a really bad fire that they have to go put out. And so we've, have changed the 2FA policies. We've changed the way the tokens work. When we find tokens that have been exposed or potentially, exposed, we invalidate them, andSwyx [00:28:22]: I love that feature in GitHub. Yeah, it's greatKyle [00:28:23]: That creates issues, but, the but that's the thing is we're trying to push the community, forward without necessarily, doing something that is going to break the contract that's been for 15 years or close to it or some amount of years on NPM.Slop Forks, Vendoring, and the Future of Open Source Supply ChainsSwyx [00:28:43]: I think the— So now we're talking about, open source and publishing. And I think there's something here with what people are calling slop forks, which, I think Malta from Vercel is doing. And, part of me thinks, well, the way to get past any vulnerabilities, we just, let's just get rid of the concept of NPM. And we only publish source code. And anytime you want to import it you have your coding agent look at it and then adapt whatever subset you're going to use into your vendor it. But, the AI vendor it. Is that realistic? I don't know. Is it— Will that solve all our security issues? I don't know.Kyle [00:29:24]: I don't think it'll solve I so Mitchell was just talking Mitchell Hashimoto Was just talking about this today, and I think that I-in some ways, it's all all things, old or new again? Yeah, absolutely vendoring everything. Like I do I do remember twenty thirteen, twenty fourteen.Swyx [00:29:42]: This is Yeah. Let's, we must return toKyle [00:29:43]: That's what is We were vendoring everything. We were having actual discussions around, or at least I remember we were “Should we take this full thing?” “Why is this so big? We only need this one file.” And so I do think there's something true there where having either taking only what you need or the dependencies just getting incredibly small over time, I think will help to some degree, but it's not going to solve the fundamental problem, I don't think, because the vulnerabilities in an agent looking at them, there's time and time again, there's a million different ways in which we can convince an agent that this thing is, secure or not and pull it in. Or we can do static code analysis or runtime testing to say whether the code works or not. That is, I think, the step that needs to continue to be, invested in. The question is just on, how much scope. Should it be this enormous project that I'm pulling down, or should it be this piece? Either most companies are running some amount of security checking on the on the packages that they're bringing in or vendoring. That I think won't change. That's like what advanced security does to some degree, Socket does some degree. Like everyone is doing a piece of that. How we each do that like especially when we're talking to enterprise customers, is just like very different. No there's no one wants one single way to do it. And I think that's always been GitHub's, unique position in the world. I talk a lot to maintainers, I talk a lot to folks about this. It's we're— we rarely start like a process and a practice and like push it onto the community. We usually wait for the sort of like RFC process socially or literally, everyone agreeing, and then we'll cement something in. Because otherwise we'reMaintainers, RFCs, Vouching, and the Social Layer of TrustSwyx [00:31:35]: That fits your role in the ecosystem, yeahKyle [00:31:36]: We're GitHub. Yeah, we don't want to shape the whole thing. We want it to be figured out. But like how do you balance that like sort of Role in the industry to keep everything as secure as is possible and make sure that you're you're not going to be compromised as a human, ‘cause that's usually how it all happens. And Not not create a process or lock us into a flow that you're not going to or like Mitchell's not going to or other open source projects aren't going to like. That's always been a tricky balance for us, and I think that's something that we haven't talked about enough is we're not going to be able to fix everything for everyone in a way that everyone is going to like. So tell, help us, tell us what is working. When Mitchell was talking about, the Upvote, the upSwyx [00:32:22]: I was going to bring up his thing. Yeah.Kyle [00:32:23]: I forget what it Yeah. When he's talking to us, I was chatting with him and talking to him about this and I put it on Twitter and we talked to, also over DM, was “We're going to keep working.” but I think the important thing is I do actually want to hear what isn't working for you. And as, be as specific and clear for your project as is possible. And to every piece of credit over the many years that we've known each other through the industry, he's always done that and I appreciate that ‘cause there are places that we need to fix up, and we hear from him, and we'll fix up just like we do all other kinds of maintainers. But that that process between making those types of improvements and being more secure and like creating, I forget what he calls it's not the proof process, not the claims process. Do what I'm talking about? He has that he his projects have a way for you to kind of like,Swyx [00:33:13]: VouchKyle [00:33:13]: Vouch. Thank you. Yeah. He has like the vouch system for saying, “Hey, you should accept my PRs.” That's beenSwyx [00:33:20]: I just built this into GitHub. I don't know.Kyle [00:33:22]: Well, see, but that's the thing is that you say that and like he and his community really likes this and then I'll go talk to other maintainers and other maintainers, globally, and they're “No, this doesn't work for me.” And that is the tension, but also the kind of beauty of GitHub, depending on which way you look at it is we want to help maintainers, so we create all these tools to let you have more control over how much you take in from AI and PRs. But you can also use this. What You can go use this project, and if it takes off and becomes the kind of mostly standard, then yeah, we probably wouldn't enforce it but we would add it in because that's the flow that we tend to do?Swyx [00:34:02]: I hear a lot of people don't know the history of the pull request. And like like that's how, that's something that GitHub standardized basically.Kyle [00:34:08]: Yeah. It was a very messy process Like beforehand, and now the we have the benefit of it being the process? And now we have to go and Figure out the next best process or what adaptations change, or what does a pull request look like when eighty percent of your PRs are just coming from your agents and not From other devs?Swyx [00:34:31]: Do you like the prompt request idea from Peter?Kyle [00:34:34]: like I think that for each like each idea I think has its merits. I'm not, I'm not avoiding saying anything good or bad, but I feel like I've seen a version of we have that we have entire Thomas' store. Take all the assets of what you've built and put that in. I think that's got great ideas. There's all these various permutations of the PR flow, but I think the reason why there's not a single answer is ultimately we're trying to codify trust. We're trying to say “Okay, if Sean reviews this I'm going to trust it because you're Sean or you're the senior dev or you're the whatever.” And right now, when we are working in a flow where an agent writes code and another agent reviews code and then Kyle goes and looks at it the trust is kind of diffuse. And most of the tools that we're talking about are talking more about verification flows. We have more assets to look at, so I can probably say whether this is a good PR or not. But that still doesn't solve, I think, the human problem of I'm looking at a PR and I want to know if I can trust it. And we're still, we still tend to use human signals for that? Mitchell approving it or Kyle approving it or whatever. And so I think that's, I think that's why most of these options haven't really solved it is because, it's a social problem ultimately. It's a it's a human problem to review it and agree. Or you fully trust the tool and you're imbuing that tool with full trust Which I think in some cases that absolutely exists.AI-Generated PRs, Trust, and the Waymo AnalogySwyx [00:36:08]: And so like in the same way that there will be a tipping point in society when we don't allow humans to drive anymore Because machines are measurably better than Than humans. I'm looking for that tipping point, right? Like Mythos is ridiculously expensive. Someday we'll have Mythos on a desktop. I don't know. Will, does that change the equation?Kyle [00:36:30]: I think it's more I took a Waymo here, and I was on my phone and not looking around at all. There are other, self-driving, vehicles that I would not trust while, staring at the road. And I think that trust is something that isSwyx [00:36:48]: Is this a Zoox thing? What is itKyle [00:36:50]: I think that is both. I think that is both. LikeSwyx [00:36:53]: There's Zoox in this robo taxi. That's it. It'sKyle [00:36:56]: Well, depending on what level Of self-driving. But, my point is sort of that I think part of that is I strongly believe that's, a mixture of verifiable proof. Like how many accidents, how much data, and so on, and the human aspect of how I feel when I'm in this car, what it tells me, et cetera. And so that's why I think some of the like Some of these some of our AI tools tend to, imbue me with more of that feeling of trust, even if the data says this is 100% accurate. I feel like it takes more time for us to go, “Should I trust this or not?” And that's in the soft sense of, startups with high agency, weekend projects, and open source. And then there's enterprises and regulated industries and everything else, and that is an even harder problem to go solve because even when it is fully verified, not only do you have to have trust from the humans on the team, you probably have to have trust from multinational,Swyx [00:37:55]: Oh my GodKyle [00:37:55]: Multi governments around the world and regulating agencies. And so that's where I feel like until we tip over to your point on the sort of like human EQ side of it. I feel okay this feels okay I've been proven enough. Then the ball will start to roll a lot faster, where we'll end up getting to the “Okay, we can trust this,” and feel good about it in the Most difficult of cases.Reputation, Sponsors, Stars, and Bot Activity on GitHubSwyx [00:38:18]: If human trust is the thing that matters, I feel like GitHub as the developer social network could maybe do more there. Like vouchers are one system But, we have star counts, and then we have Contributor rights, and that's it. And I feel like there should be more in that space. I don't know if there's any other design decisions there.Kyle [00:38:37]: I think that one of the places that we don't really expose right now in this sort of way is, some degree of like hard trust and support, which would like for me is like sponsors is a good example of that.Swyx [00:38:49]: Ah.Kyle [00:38:49]: It like costs you something. To prove that I believe in your project and I trust you To some degree or I want to support you at the very least.Swyx [00:38:56]: Solve payments for open source. Why not?Kyle [00:38:58]: I think that I think that like as we keep moving forward, right, there's more and more projects where I'm, adding more and more dollars into sponsors personally because I want to like support them, but I also like know of I've probably never met them in person, but, I know of enough of their work that I want to support them. I think the thing that I don't love about stars or commit counts or anything else is ultimately, even with all of the various, abuse and de-spamming and deduplication work that we do or anti-abuse work that we do, these are all, not active social signals. They're passive ones that are ultimately gamifiable. And you may trust me, but another open source maintainer may not. And on what heuristic should you be, trusting me? That I think, is kind of where some of our thinking is right now. What signal from me is most important to you? You— If you can define that potentially, honestly in an agentic workflow that's what we see some of these open source projects do, where you have GitHub actions, and then you have like an agentic workflow that's calling AI, and you're setting these rules. Like if Kyle has submitted and gotten accepted PRs across any given project and has a social handle tied to his account in GitHub, and that social account's older than a certain amount. Really complex measures that matter to you ‘cause most open source projects have that heuristic built into their heads, if not written down in the contributing guidelines. You could take that and then go apply that and then just say, “Oh, we're not going to accept this PR.” Building something that is, I think, malleable to everyone's needs, is a little bit better, rather than going “Hmm, this account's too young.” Because what happens? The attackers just go and go and create a multitude of accounts, and they wait Until it ages up. Needs to have a certain amount of stars. That's how star inflation happens. Need to have a certain amount of reposSwyx [00:40:46]: Oh my God. YeahKyle [00:40:47]: With PRs. They all just create repos and submit PRs to each other, and then they come in and do something nefarious. And so, it's hard. It's hard to find the measure. So I think we're, we're looking more at how can we provide you tools so you can kind of choose what's best for you. And of course, we'll give you some standards. But the trust vector, gets down to I don't know, some version of like human digital ID like everyone's been talking about. Like how do I prove that it's meSwyx [00:41:13]: Give me your eyeballsKyle [00:41:14]: On the internet. Give me your eyeballs. Exactly.Swyx [00:41:18]: The I got to keep moving on Topics, but obviously I can go all day on this stuff because, I've been involved in GitHub and open source My entire professional career. Stars. Very superficial. Everyone knows it. But I think time to one hundred thousand stars is the fastest I've ever seen. Like people just reached that in I don't know, months. And then like at the same time I don't trust it right? Like how many of these are real or bot or like whatever. I don't know how to ask this but like what can we do about it? LikeKyle [00:41:49]: JustSwyx [00:41:49]: Is stars broken? Is stars fine?Kyle [00:41:51]: I think that there's kind of two, there's like two pieces. Obviously we're constantly like trying to find ways in which like your users are producing spam, which would, I would include like be like only doing star gamification. When we find them, we pluck ‘em out and we,Swyx [00:42:08]: But it's like a Whac-A-MoleKyle [00:42:10]: It's a hundred percent like a Whac-A-MoleSwyx [00:42:11]: There's no wayKyle [00:42:11]: Now, powered by AI to be helpful. But I think more so what I'm seeing is, a lot of the like fastest time to X tends to be because we're now inviting so many more people into like software development on GitHub That like the zeitgeist is just swarming? And it'sSwyx [00:42:32]: It's not just developers anymoreKyle [00:42:33]: And it's not you and I. Like like however you want to say like what a developer is it's not just folks who have been coding for a very long time. It's folks that have maybe started coding or only joined in since the AI era. And nowSwyx [00:42:44]: what's the latest Octoverse number? I know eighty million was my lastRem- member that a number of developers on GitHubKyle [00:42:50]: Oh, we're over 200 million now.Swyx [00:42:53]: Okay. Well, so you see?Kyle [00:42:55]: Like over 200 million developers now.Swyx [00:42:56]: But it's not developers, right? It's, it's people with a GitHub account.What Counts as a Developer in the AI Era?Kyle [00:43:00]: So, so this is, this is the biggest debate that I would say, everyone loves to have at GitHub at this point. From my perspective, right, I think that there's, there's clearly a difference between, professional enterprise developer and then developers. But I think that I think that the idea that we should be I don't know, splitting hairs or segmenting developers in the early era of software development is, not worth our not worth the time. SoSwyx [00:43:29]: When you get into gatekeepingKyle [00:43:31]: 100%Swyx [00:43:31]: What is a developer?Kyle [00:43:31]: 100%. ‘Cause I wasn't a developer when I started writing code? I was going toSwyx [00:43:36]: Oh, no. I made— I cloned a thing, seven years before I learned to code. And then I and then I wrote about my learning to code journey, and people Just called me a fraud ‘cause I had a GitHub account. And I'm “Well, no, I just use GitHub, but I don't know-” “I didn't know what I was doing.”Kyle [00:43:49]: I I remember that. I remember those sets of posts, and like that's, that's b******t. So I fight very clearly on the line of, if you create code, if you have an idea and you create it into some way of, I'm, I'm going to run it and use the app right now, you may still use AI in that moment, but that's okay. At some point you're going to do the next thing. You're going to create a big— You're going to have to learn about this database. You're going to fix a bug, whatever. We're all on some same journey, and those people are also hearing about the great new agent skill package or a new CLI tool or a new whatever. And those projects are going up because you want to be a part of this moment, just like I wanted to be a part of the Ruby community when Ruby was popping off when I started becoming a developer, and now I can just click the star button. And so I think that yes, there's clearly some amount of like spamming and game gamification that we're working against, but I really think we're just seeing this whole new cohort of folks that are moving from technology to technology because they're not working on a 20-year-old software application. They're working on a side app that they built on the weekend for their friends or for their new idea or whatever. And that's how you see these enormous charts going up and to the right with With stars.Swyx [00:44:59]: I think something that's remarkable is the persistence or, that GitHub extends to those folks. Usually when I see platforms go into a new audience, they usually have to, have like a second platform with a different name that wraps the main platform. But somehow GitHub has been able to sort of persist and extend, and it's friendly and whatever? So it's, it's nice.Spark, Low-Code, and Always Showing the CodeKyle [00:45:19]: I that's partially why I think as we've tried to move into I don't know, more like low-code-y things. We so we started working on Spark as like a way to, build an app and run it. I think that the reality is that we anytime we try to, kind of put even a veneer on top of it without when we put a veneer on top of something, we still always show you the code. That's kind of like a tenant. We're never going to, hide the code from you ever, because whatSwyx [00:45:52]: Why would you?Kyle [00:45:52]: That's, yeah, that's the whole point? However, I think that what we learned with things like Spark is that really the value of Spark for most devs is, easy runtime. And you may have a runtime or a host that you're going to use for that or you just build something and run it but, the package of making that even more simple isn't really needed for folks that are trying to build software and not just trying to build, an app, which is, slightly different, a slightly different goal. So I want to get you in, I want to get you comfortable. I think the best thing for me as, someone that did not traditionally come into software dev way back, I want anyone to be able to breach that chasm and not be in the I don't know, I feel like we're, we're still in an era of, STEM. I've got a 12-year-old and an eight-year-old, and it's “We got to get ‘em into STEM,”? Over and over. And I like I do, I do the things that good parents do. I was “Oh, you want to do coding?” “Yes, I want to do coding.” Do coding classes. But now they're just not afraid of doing software. And that's, I think, the thing that's honestly kept me at GitHub for so long. Anyone should be able to go and build a thing, just like I can go change a light switch in my house. I'm not going to go into the breaker box ‘cause I'll probably kill myself? But, I can go change that light switch. Everyone should be able to go and say, “This fricking app doesn't do what I want. I want it to work like this.” And that I think, is what's kind of kept us all connected with GitHub through the years and some and during the easiest of times or in the hard times because of that opportunity of, we're the home for all developers, and we want everyone to be able to have that feeling that we've had of, had an idea, I created it and holy s**t here it is.Swyx [00:47:37]: Here it is. All right, I'm going to try to do more spicy questions.GitHub's Hardest Scaling Moment: Growth, Agents, and UptimeKyle [00:47:42]: Great.Swyx [00:47:42]: Is it an easy time now or a hard time?Kyle [00:47:45]: Oh at GitHub? It's a hard time. Like, it's a hard time and also, I was just with my team and I said, “This is also, the best and most exciting time that I think I can remember at GitHub.” BecauseSwyx [00:47:57]: Best of times, worst of times. It's never oneKyle [00:47:59]: ‘cause we've we were talking about Octoverse reports and, usually we do an Octoverse report once a year, and we look at the numbers, and we say, “Oh my goodness.” I was at Universe in October saying, “This was the fastest year of growth that we've ever had,” right? And now we're doing more in a month than we did in a year last year.Swyx [00:48:20]: You're talking about PRs.Kyle [00:48:21]: Commits.Swyx [00:48:21]: Commits, yeah.Kyle [00:48:22]: PRs. Kind of like you name it by roughly every measure that we're looking at, there's some amount of sort of growth that is much bigger, and that is breaking our system in new ways, not old ways. Like webhooks were always notoriously, unreliable over the years?Swyx [00:48:38]: Whose fault is that?Kyle [00:48:39]: not anymore mine, but for a period of time, I'm sure you could pull up a tweet that was “It was me. I'm sorry.” but, now, that got rewritten at a scale level that is still working and is not having problems today. Now what we're finding isn't just the isn't the-The simple stuff that folks are on the sometimes on Twitter or on the internet are “Hey, why is this like this?” Sure. There's absolutely silly problems that we shouldn't exist. But now we're talking about, unique, novel permission problems that happen only at a scale across all different objects or whatever, that now we have to go rewrite this underlying system. And so it's, there are problems that yeah, caught us off guard, which I think I said. Like the growth is astronomical, but also we're making such material progress in that I'm excited once we're once we've kind of like reimagined the underlying foundation layer, or pieces of it at least, what's going to be possible when it's not just all of us and all the new people that are being developers and all of their agents and all the tools like working together. Because that'll still happen in that in that GitHub tool, that GitHub community. But it's a it's a hard day anytime we can't give you what you're looking for. We have the same problem internally. We operate through github. Com. Of course, we have backups when things go down and whatnot for our own operations but we feel it too. If it's not working it's not working for us, and that's kind of like the promise of dogfooding for GitHub. It's always been true. We're using the same tool you're using. We're not using a super secret version. We and so we also need it to be great for us for our customers of course for open source. And now an exponential growth of agents, Doing it too.Swyx [00:50:32]: I wanted to load for audio listeners who maybe haven't seen your tweets, whatever. So one billion commits in twenty-five. Now it's two hundred and seventy-five million per week on pace for fourteen billion this year, if growth remains linear. Is that still the pace? I don't know. It's been aKyle [00:50:48]: it's, it's speedingSwyx [00:50:50]: Roughly.Kyle [00:50:50]: It's still speeding up.Swyx [00:50:51]: It's, it's April, so yeah.Kyle [00:50:51]: Exactly. This was in April.Swyx [00:50:53]: All right. So basically you have fourteen x growth, right? Year on year on year. And I think that's a scaling issue. I think, I'm going to like try to really steel man this thing. People have experienced fourteen x growth. They haven't had your downtime. And that's like— C-can we go dig into that? Why? Like what's the— what broke? What are we doing to fix it? Like just anything for the community to reassure them.Why GitHub Reliability Is Breaking in New WaysKyle [00:51:18]: so there's a Like I was saying, there's a couple different places that we've seen the growth issues. Some of the growth issues, which is why we're t— I was talking about pushing hard on more CPUs is in actions in particular. More tools, more agents, more PRs mean more builds, more builds mean more CPUs. And so we are expanding through not just our data center, but obviously we were talking about moving to Azure and moving to, adding an additional cloud compute because we simply need more CPUs. Not as much GPUs. We definitely need GPUs too, but now CPUs are becoming a factor.Swyx [00:51:53]: It's very CPU heavy.Kyle [00:51:54]: Underneath the hood when it comes to some of the underlying services, we've been breaking up over the years our database infrastructure, so that way we have, more cognitive separation between our the various services. The place that we continue to have pain is in, permissioning. And so right now m-many of our permissioning layers sit into a database that we like internally call MySQL One, and old Hubbers will know what I'm talking about. And so we've been pulling things out of MySQL One for many years, because like and we use we use Vitess and we use other technologies to shard and we do it as one bigSwyx [00:52:31]: Famous thing, PlanetScale was born from this andKyle [00:52:32]: A hundred percent. Sam Old Hubber and friend. And so finding these opportunities to like break this out and then do that globally. The other thing that I think is interesting and both a unique opportunity and tricky is we also run everything I just talked about in a black box container with GitHub Enterprise Server for people that work on-prem. So we take everything I just said, and we also do it on-prem, and we also do all of that and we do it in a data residence setup for customers that need to have their data in a single location. Each of these has the unique characteristic around how we're sort of storing that data in MySQL or in a permissioning setup. That's where some of these outages have oc-occurred, where you're seeing it more like across the board rather than just like the one pieceSwyx [00:53:17]: Filling the databaseKyle [00:53:17]: Isn't quite working. Exactly. And so part of it is that. I think there's been some other places where agents are much more or more projects appear to be moving towards monorepo versus we were going the other direction for many years in the industry. Repos were smaller, but there were more of them, and now we're seeing the opposite. Repos are bigger, and there's, not fewer of them per se ‘cause there's new growth, but, we're just seeing many more big repos. Big repos, big monorepos have always had, a unique performance problem. Because each one, is slightly different if, particularly if the underlying blobs are incredibly big Inside the repos. And so we've done a ton of work that you pro— like most people haven't probably experienced, unless you're in this case of the monorepo. But that Git, infrastructure layer improvement does help the overall, system because, many of the improvements that make monorepos work better make all repo infrastructure work better. And so, I could kind of keep going down the line where it's another thing where we're moving out of, We're changing how we do j I'll just say job queuing for lack of a better, explanation changing the underlying technologies there.Swyx [00:54:32]: I spent two years being a job queuing guy, so.Kyle [00:54:34]: And so it's kind of a little bit of a little bit of piece by piece, and it's mostly because as we were— as it was built, we built everything in a way that assumed, I guess in some ways that the size of the pipe of work was going to remain the same. There's just going to be more people coming through each of those pipes. But instead now in places whereA git push was, generally a certain size for example, is now, no longer true.Swyx [00:55:03]: Oh, yeah.Kyle [00:55:03]: OrSwyx [00:55:05]: I push a thousandKyle [00:55:06]: On the average. 100%Swyx [00:55:06]: A thousand line commits like dailyKyle [00:55:07]: Same thing with PRs. Like PRs same thing. And like we've talked about optimizing that and making changes where, and there were technology choices that did not work there? And it got slow, and it didn't It was not fast. It did not do what the users wanted. And so we've been reeling that all out and going “Okay, that's just not right. Let's stop putting good money after bad and do it the do it the right way or the right way now.” So there's It's a it's a lot of things, not quite when I've experienced scale at GitHub historically, it's almost always two options that we've used. We go vertical scaling, particularly with databases, right? And we go horizontal scaling. Oh, we just have more people using this service. Great. We're going to add more servers, and we rack them in our data center, or we use it in a cloud. And now we're sort of in a like diagonal, where like vertical doesn't really work anymore. Horizontal isn't work either because we're all We all have some CPU or GPU constraints in the world now, and now we have to go in and like crack open services that have been running for 10 or 15 years and go, “Okay, the rules of this service have legitimately changed, and now we have to rewrite them.” None of this is an excuse. This is like we're We have to do the work. We have to make it better.Swyx [00:56:22]: actually as an infra guy, I'm “This is like one of the most fascinating scaling challenges I've ever seen.”Kyle [00:56:26]: That's that's, that's the thing that's the thing that it's hard for Like when we weren't talking about it publicly, and I was like I came out, and I was “Hey, I just want to explain what's going on.” Part of it comes from a very old GitHub ethos, which is it's our it's our uptime. It's down. W What I know you're a developer, so you're, you're inclined to want to understand more what's going on. But at the same time us going “Hey, this service didn't, perform the way we expected, and now we have to go change it,” we weren't We're not trying to hide anything from you i

Watch this episode on YouTube: https://youtu.be/vMtf0ZtSbbA   Fleet maintenance isn't sexy — but it's one of the highest expenses in trucking, the most controllable, and by far the most ignored. Justin Brevik of Bosch FleetMe returns to the BulkLoads Podcast to break down exactly where fleets bleed money on maintenance and how to fix it, whether you run 3 trucks or 3,000. Host Jared Flinn and Justin cover the real cost of letting a truck sit at a dealership, the oil-change myth costing you thousands, why tires are your #1 maintenance expense (and the cheap fix almost nobody does), and how to move your operation from reactive to preventative to predictive maintenance. If you're an owner-operator, carrier, or fleet manager trying to protect your margins, this one pays for itself. Want to be featured on the BulkLoads Podcast? https://www.bulkloadsmedia.com/ ⏱️ CHAPTERS 00:00 Joining Bosch's Fleet Maintenance Team  05:23 Fleet maintenance strategies 09:55 360-degree DVIR integration 11:18 Streamlining fleet breakdown response 14:40 Evaluating and training technicians 19:00 Dealership repair and staffing insights 22:11 Tire maintenance and oil changes 23:45 Fleet management tools overview

The Ship Report, Monday, June 1, 2026It's Rose Festival Fleet week on the ColumbiaThis week we'll begin seeing ships arriving to head to Portland for the Rose Festival as part of the Festival Fleet.One ship is already in town on Astoria: the USS Chafee, a Navy destroyer, which will head to Portland around midnight tonight. I'll announce other ships as they appear on the schedule and include them in the ship schedule I publish during the week.You can tour ships in Portland this weekend. For more info see the Festival Website and click on the Fleet page: rosefestival.org

Joerg Grossmann, hotel director for Emerald Kaia, talks with Alan Fine of Insider Travel Report about how the new Emerald Cruises yacht is designed for warm-weather sailings, small ports, marina access, local shopping and a more private-yacht feel. Grossmann also gives advisors a deck-by-deck tour covering the spa and marina, open galley, Night Market, observation lounge, open bridge, accommodations and more. For more information, visit www.emeraldcruises.com.  All our Insider Travel Report video interviews are archived and available on our Youtube channel  (youtube.com/insidertravelreport), and as podcasts with the same title on: Spotify, Pandora, Stitcher, PlayerFM, Listen Notes, Podchaser, TuneIn + Alexa, Podbean,  iHeartRadio,  Google, Amazon Music/Audible, Deezer, Podcast Addict, and iTunes Apple Podcasts, which supports Overcast, Pocket Cast, Castro and Castbox. 

Holland America unveils 'Evolution' — a $500 million-plus renovation of six classic ships, the largest investment in the line's 153-year history, beginning with Oosterdam's drydock and adding new suites, solo verandahs, and a Grand Dutch Café. And Explora Journeys launches the bow section of Explora V at Fincantieri's Palermo shipyard, the LNG-powered fifth ship in MSC's luxury fleet expansion bound for delivery in 2027.

Day 1,557.Today, after a weekend that saw Russian ships hit by drones, hit by drones and hit by drones again, it ended with another Russian ship being seized by abseiling Frenchmen. Meanwhile, Ukraine's “logistics lockdown” continued, leading to fuel rationing in Crimea and more Russian oil refineries self-sanctioning in very dramatic ways; no wonder Putin's Finance Minister has said Russia's spending on the war has gone two trillion rubles over budget.Contributors: Dom Nicholls (Host on Ukraine: The Latest). @DomNicholls on X.Sophie O'Sullivan (Telegraph journalist).Adelie Pojzman-Pontay (Host on Ukraine: The Latest). @adeliepjz on X.With thanks to Stergios-Aristoteles Mitoulis (Associate Professor of engineering at the Bartlett School of Sustainable Construction at UCL). @DrMitoulis on X.Producer: Rachel PorterSenior Producer: Lilian FawcettVideo Producer: Sophie O'SullivanSocial Producer: Gezim HilajStudio Director: Meghan SearleExecutive Editor: Francis DearnleyCreated by David KnowlesNOW IN FULL VIDEO WITH MAPS & BATTLEFIELD FOOTAGE:Every episode is now available on our YouTube channel shortly after the release of the audio version. You will find it here: https://www.youtube.com/@UkraineTheLatest CONTENT REFERENCED:Russia overspends on Putin's war in Ukraine by $28bn (The Financial Times)https://www.ft.com/content/93674b5c-06ea-4e49-a005-dc08e1091574?syn-25a6b1a6=1 Inside the schools preparing Ukrainian children for war (The Telegraph)https://www.telegraph.co.uk/world-news/2026/05/31/inside-the-schools-preparing-ukrainian-children-for-war/ For more information on Professor Mitoulis's work, follow the links below:Bridge Ukraine: https://bridgeukraine.org/Meta Infrastructure: https://metainfrastructure.org/EMAIL US:Contact the team on ukrainepod@telegraph.co.uk. We continue to read every message, and seek to respond to as many on air and in our newsletter as possible.HIGHLIGHTS:France seizes Russian shadow fleet tanker in mission Moscow calls ‘piracy'Ukrainian drones dominate skies over occupied cities Hosted on Acast. See acast.com/privacy for more information.

James Currier is back to strip away the delusion that the market is coming to save you and dive hard into what it takes to actually build a sustainable freight strategy! In this episode of the podcast, we break down why a spike in spot market rates doesn't fix a broken capital structure, the critical role of fleet utilization through online platforms, and how carriers can survive the relentless pressure of rising fuel costs and tightening line of credit constraints from commercial banks. It's time to stress test your equipment and focus on real profitability and cash flow over top-line hype, so tune in to our conversation!    About James Currier James Currier is the Chief Revenue Officer at Finloc USA, where James leads the sales team across the country in a relentless pursuit for increased market share in the equipment finance field. After starting his professional career as a Business Analyst in the healthcare field, James came to realize that his passions were best suited to dealing with people and organizations aiming for growth. After a two year contract was completed with Fraser & Interior Health Authorities in British Columbia, a career change ensued and James has not looked back since. Combining the analytical fundamentals learned in healthcare and a natural gravitation towards people and business development, James has thrived in a sales career since 2012, leading, managing, and training dozens of people over the past several years. Subsequent to the completion of a >$400MM acquisition at his previous company, James made the jump to Finloc where he was first tasked with hiring and redeveloping the Ontario, Canada market. James was then assigned to manage the US division for Finloc as a player/coach, originating new asset-based financing opportunities and finding, attracting, and training new talent. James has worked in an exceptionally diverse range of roles since the age of 15, starting as a minor hockey league referee. His openness to new experience has allowed James to experience positions as a head of high-profile security, high-adventure whitewater rafter guide, Corporal in the Canadian Armed Forces Infantry Reserve, business analyst, VIP/Private security operative, personal support worker, guitar teacher, and sales leader. As a well-versed hobbyist who enjoys learning and new experiences, James enjoys coaching/playing/watching hockey, swimming, guitar, hunting, fly fishing, boating/canoeing, cycling, hiking, woodworking, motorcycling, reading, DIY projects, and evening walks with his wife, 2 boys, and golden retriever.   Connect with James LinkedIn: https://www.linkedin.com/in/james-currier-clfp-232b0842/?originalSubdomain=ca  Email: james.currier@finloc.com  

Most fleets already have telematics installed. The problem is, most of the data is wrong, incomplete, or being used the wrong way. In this episode of the Fleet Success Show, Fleet Hall of Famer Steve Saltzgiver sits down with Lucas Schorer, Founder & CEO of Kestrel Insights, to expose the hidden operational blind spots quietly costing fleets productivity, efficiency, and millions in preventable mistakes. They break down: why most geofencing setups fail how inaccurate fleet data creates false decisions the real ROI behind telematics why “Big Brother” fears are disappearing how AI is changing fleet operations the $250,000 cargo theft caused by ONE tiny geofence mistake why most fleets only use 10% of their technology stack If you manage fleet operations, logistics, transportation, field services, or telematics systems, this episode will completely change how you think about operational visibility. Subscribe for more fleet leadership, operations, and transportation insights from the Fleet Success Show. #FleetManagement #Telematics #Logistics #Transportation #FleetTechnology #SupplyChain #FleetSuccess #AI #OperationsManagement Looking to take the next step to fleet success? Start by requesting your free copy of The Fleet Success Playbook. Written by fleet professionals for fleet professionals, the Playbook breaks down the four key pillars of fleet success, and gives you the tools you need to build a truly great fleet. Request your free (yes, really, free!) copy here: https://rtafleet.com/resources/fleet-success-playbook?utm_source=simplecast&utm_medium=footer_notes&utm_campaign=episode_213 Control fleet chaos with RTA Fleet360, proven software designed by fleet managers for fleet managers: https://rtafleet.com/book-a-demo?utm_source=simplecast&utm_medium=footer_notes&utm_campaign=episode_213

  On today's episode, Adrian and Colin break down the stacked GKA Mykonos fleet and dive into one of the biggest storylines of the season — the Big Air debut of Gisela Pulido. They discuss what her transition from freestyle means for the women's division and who could emerge as World Champions in Mykonos.   Fantasy:   https://portraitkite.com/videos/fantasy-updates-may-2026/   Road To Pro (Japan):   https://portraitkite.com/videos/road2pro-season-2-japan-ep1/   WOO:   https://www.woosports.com/en   Portrait:   https://portraitkite.com     https://www.fantasykite.com   Follow us:   https://www.instagram.com/portraitkite/   https://www.instagram.com/kitesurf365/

Dion eventually led an invasion fleet to liberate Syracuse, but the revolution quickly descended into chaos and factional splits. James Romm explains that despite his Platonic education, Dion committed the political murder of his rival, Heraclides, which caused him a deep spiritual crisis. Dion was eventually assassinated by a faction of his own army led by Calippus, another student from Plato's Academy. Later, the historian Plutarch attempted to burnish Dion's legacy, portraying him as a "philosopher king." This defense aimed to protect the reputation of the Academy from the scandals of its students. (5/8)1839 SYRACUSE

PREVIEW for Today: Michael Bernstam analyzes Russia's shadow fleet oil exports to China, India, and Egypt. Despite China's increased reliance on Russian energy, Russia remains unable to fully capitalize on high oil prices during the ongoing global conflict.1900 Baku

1. Strategic Importance of the Strait of Hormuz The Strait of Hormuz is one of the most critical maritime choke points in the world. Over 20% of the global oil supply passes through it daily, not including broader commercial shipping. Although often perceived as narrow and easily controlled, the strait is ~21 miles wide at its narrowest, making comprehensive surveillance extremely difficult. Large commercial vessels are confined to two-mile-wide shipping lanes due to depth requirements, making them predictable and vulnerable. 2. Vulnerability of Commercial and Naval Shipping Massive oil tankers and cargo ships: Cannot maneuver quickly or stop. Take miles to change course. Become “sitting ducks” within narrow sea lanes. The remaining waters outside the main lanes provide cover for hostile actors. 3. Iranian Asymmetric Naval Strategy Iran avoids direct, conventional naval confrontation with the U.S., which it previously lost decisively. Instead, it relies on small, fast, low-profile attack boats operated by the Islamic Revolutionary Guard Corps (IRGC). These boats: Are often smaller than recreational boats. Use multiple engines for high speed. Are armed with heavy machine guns, rockets, and anti-ship missiles. Operate in swarms from multiple directions. 4. Concealment and Tactical Advantage Iranian fast boats: Operate in shallow waters close to shore. Blend in with fishing vessels and heavy commercial traffic. Remain difficult to detect by radar until moments before attack. The Persian Gulf’s dense maritime traffic makes threat identification even harder. 5. Recent Military Developments The U.S. reportedly sank six Iranian fast attack boats attempting to harass vessels. U.S. Central Command (CENTCOM) stated: Iran typically deploys 20–40 such boats, but only six were observed in this clash. U.S. naval and air assets (Apache and Seahawk helicopters) are heavily positioned in the area. Iran’s naval capabilities have been significantly degraded. 6. U.S. Position and Policy The U.S. frames its role as defensive, focused on: Protecting commercial shipping. Ensuring freedom of navigation. Hundreds of ships from 87 different countries are currently backed up in the Persian Gulf. The U.S. has offered escorted passage through the strait. 7. Escalation Risks and Political Messaging President Trump issued strong warnings to Iran, threatening overwhelming retaliation if U.S.-flagged or escorted ships are attacked. Iran insists ships must coordinate with Tehran before transiting the strait. Recent incidents include: A South Korean vessel explosion and fire. A Panama-flag cargo ship engine fire. A UAE oil tanker reportedly targeted by an Iranian drone. These events raise questions about: The durability of a fragile ceasefire. Whether strikes could expand to Iranian territory or leadership targets. Please Hit Subscribe to this podcast Right Now. Also Please Subscribe to the The Ben Ferguson Show Podcast and Verdict with Ted Cruz Wherever You get You're Podcasts. And don't forget to follow the show on Social Media so you never miss a moment! Thanks for Listening X: https://x.com/benfergusonshowYouTube: https://www.youtube.com/@VerdictwithTedCruzSee omnystudio.com/listener for privacy information.