Podcasts about Reliability

Complex Product Reliability Abstract Enrico and Fred discuss the difference between complex and complicated products and what it means for reliability engineering. Using examples ranging from rockets and home appliances to computers and fountain pens, they explore the limits of component-level analysis, the role of system testing, and why surprises remain unavoidable even in well-engineered […]

Everyone thinks the future of work means spending more time interacting with AI. Aaron Mitchell Finegold believes the opposite. As Head of Product Marketing at Adobe, Aaron sits at the intersection of enterprise AI, agentic workflows, brand intelligence and the future of how work gets done. In this conversation with Liam Lawson, he explains why most companies are approaching AI adoption incorrectly, what an agentic content supply chain actually looks like, and why trust, judgment and human relationships may become even more valuable in an AI-first world. Stories Covered This Week: Why most companies are deploying AI agents the wrong way What an agentic content supply chain actually looks like inside the enterprise How Adobe is building systems that combine humans and AI agents Why generative AI without guardrails can damage brand integrity The difference between work that should be done by humans versus agents How enterprises are turning brand knowledge into AI-readable intelligence Why trust matters for both humans and AI systems The personality traits that will thrive in an AI-driven workplace Aaron's vision for the future of work and why it may involve less interaction with machines than people expect Episode Timestamps: 00:00 Intro and Aaron's background 03:01 Hands-on experience building with AI 04:41 The biggest misconception about generative AI 05:38 What an agentic content supply chain looks like 07:30 When should AI agents replace humans? 08:40 How Adobe's Brand Intelligence works 10:44 Where AI starts and human creativity ends 12:09 Aaron's vision for the future of work 13:41 What trust means for humans and AI agents 16:34 Reliability, AI systems and enterprise adoption 19:34 The personality traits that will thrive in the AI era 21:38 Why do you do what you do? Connect with Aaron on LinkedIn: https://www.linkedin.com/in/finegold/ Partner Links Upgrade your AI toolkit: https://www.theaireport.ai/ai-executive-pass Subscribe to our free newsletter: https://newsletter.theaireport.ai/subscribe Join the community: www.theaireport.ai/leaders-launch-guide Learn more about your ad choices. Visit megaphone.fm/adchoices

Yep, there is a gap between available jobs and job ready candidates. There are jobs available, but employers are becoming much more selective about who they hire. A few years ago, many facilities were simply trying to fill positions. Today, employers are looking for candidates who can bring reliability, flexibility, safety awareness, and productivity on their first day.  What many of us applicants don’t realize is that employers are often evaluating far more than just experience. I'm Marty here with Warehouse and Operations as a Career. So let’s talk about that.  I recently was enjoying lunch with a long time mentor and the subject of hiring came up. He made a point I had to ponder on for a moment.  He commented that although training was expensive, and of course experience is important, he had learned or felt like, in todays environment, things like attendance history, reliable transportation, the ability to be flexible with shift times, and a strong safety mindset along with a wiliness to cross train, and at least average communication skills were what he was placing more weight on these days. And he made it a point to comment on, what he'd look for first was a stable work history.    The challenge for us applicants becomes, I can do the job is no longer enough. Employers are asking, can I depend on you to do the job consistently?  And some other hurdles for us, or a few things I thought of start off with those pesky Applicant tracking systems or ATS. Many applicants never speak to a recruiter because their application gets filtered before a human ever sees it.  And wage expectations vs market rates. Applicants often see social media posts about higher wages, while many entry level positions are paying less than expected. And I'm seeing more skilled equipment requirements. Many facilities now want forklift, reach truck, electric pallet jack, clamp truck, or inventory experience, even for positions that were once considered entry-level. And communication challenges. I hear this every day, and I think both sides are probably quilty, but Recruiters frequently comment on the struggle to reach applicants who don’t answer calls. Have full voicemail boxes. And don’t respond to texts or emails. Then we have competition from better candidates. When ten applicants apply for a position, employers often choose the one with better attendance, longer tenure, and the better interviewing skills.   The good news is that the hurdle is also the opportunity. A candidate who shows up on time, returns calls, has a positive attitude, accepts coaching, prioritizes safety, is willing to learn additional equipment can often outperform applicants with years more experience.  As we've discussed many times on WAOC, the industry still offers tremendous career opportunities. The challenge isn’t necessarily finding a job, it’s demonstrating that you’re the person an employer can trust with the opportunity.  So, if there’s applicants looking for work, and employers looking for workers, why are they not connecting? Well, I think the hiring game has changed. Twenty years ago, many warehouses and production facilities hired almost entirely on experience. Could you drive a forklift, pull an order, load a trailer, or operate a machine? If the answer was yes, there was a pretty good chance you’d get hired on the spot. Today, things are just different. Most employers are still looking for skills, but they’re looking for something else first. They’re looking for dependability. They’re looking for consistency. And they’re looking for people they can count on.  I’ve sat across the table from hundreds, maybe thousands, of hiring managers throughout my career. And I can tell you something that might surprise applicants. Many managers would rather hire a dependable employee with less experience than an experienced employee there not sure can be counted on. Think about that for a moment. The employee who shows up every day, arrives on time, follows instructions, works safely, and wants to learn often becomes more valuable than the person with years of experience but poor attendance or a negative attitude.  Let’s talk about the first hurdle many applicants never even see. The Applicant Tracking System, or ATS. Years ago, an application landed directly on someone’s desk. Today, many applications are screened by software before a recruiter ever sees them. A computer may be reviewing your application before a human being does. Now, I’m not saying that’s good or bad. It’s just reality.  If your work history is incomplete, if your resume doesn’t match the position, or if key information is missing, you may never make it to the interview stage. Many applicants think nobody called me. The reality may be nobody ever saw the application. That’s why accuracy on our part matters. Taking an extra few minutes to complete an application correctly matters. And that’s why we should tailor our resumes to the position we're applying for.   Now let’s talk about what employers are really seeking. Most people think employers hire labor. I don’t. I think employers hire reliability. Let’s say I have two candidates. Candidate A has five years of forklift experience. Candidate B has one year of forklift experience. Most people automatically assume Candidate A gets the job. What if Candidate A has changed jobs every three months and has attendance concerns and arrives late for the interview? But Candidate B has a solid work history, great references, and arrives fifteen minutes early? The decision suddenly becomes much harder. In fact, many employers will choose Candidate B. Because skills can be taught. Reliability is much harder to teach.  Here’s another challenge I see every day. Applicants submit applications. Recruiters call. Nobody answers. Recruiters text. No response. Recruiters email. No reply. A few days later, the applicant says nobody contacted me. Now, I’m not picking on anyone. But communication matters. If you’re actively looking for work, we need to answer our phone, check our voicemail and respond to texts. And watch our email. I’ve seen qualified candidates lose opportunities simply because another applicant responded first. Speed matters in recruiting. Especially in warehousing and manufacturing. Sometimes positions are filled within hours. Not days. Not weeks. Literally, just hours.  Transportation is often part of the interview before the interview. Can you reliably get to work? Can you make a 5:00 AM shift? Can you work overtime? Can you handle weekends when required? Employers understand that life happens. Cars break down. Traffic exists. Emergencies occur. But employers are also trying to determine whether attendance problems are likely to become a pattern. Remember attendance drives productivity. And productivity drives customer satisfaction. And customer satisfaction keeps facilities open and growing. Again, everything is connected.  Another thing I'm seeing is that Years ago, some facilities focused heavily on production. Today, safety and production must work together. Most employers are looking for candidates who understand safety expectations. They want associates who wear PPE correctly, follow procedures, report hazards, work safely around equipment, and take training seriously. The old mindset of I’ve been doing this for twenty years doesn’t impress many employers anymore. The new mindset is I’ve been doing this for twenty years and I’m still learning. That’s the employee organizations want. Safety conscious employees protect themselves, their coworkers, and the company.  And I think another hurdle for us is Technology. Today we have RF scanners, Warehouse Management Systems, voice picking systems, tablets, inventory software, electronic inspections and productivity tracking. Some applicants become nervous when they hear the word technology. And we can't. All systems can be learned. The bigger issue is willingness I think. Employers aren’t necessarily looking for technology experts. Again, they’re looking for people willing to learn. A positive attitude toward technology often beats resistance every time.  I think competition is stronger than ever. You’re not competing against the job. You’re competing against other applicants. Imagine ten people apply for the same position. Who gets the interview and the offer? Often, it’s the candidate who demonstrates better attendance better communication better attitude better stability better preparation. Notice that experience isn’t the only factor. Sometimes it isn’t even the most important factor. The candidate who prepares wins. The candidate who follows up and demonstrates professionalism wins.  A recruiter told me last week. If I could sit every applicant down and share one message from employers, it would be this, we want to hire you. Think about that. Recruiters don’t wake up hoping positions stay open. Supervisors don’t want to work short staffed. Managers don’t enjoy running operations with vacancies. Everyone wants positions filled. But employers need confidence. Confidence that we'll show up. Confidence that we plan on staying. Confidence that we'll work safely and represent the organization well. That’s what they’re evaluating. Not just whether we can do the work. But whether they can trust us with the work.  So, what can us applicants do? I think it's simple. If we own it. We need to show up early. And we need to dress appropriately. If we're interviewing as an equipment operator or selector, wear our steel or composite toe footwear.  We have to answer our phone and return calls. The hiring agent may be making 50 calls, the next person may answer there’s. And its so important that we bring energy to interviews. And were honest about our experience. And demonstrate willingness to learn. Show our enthusiasm. Ask questions. Express interest in advancement. Employers love hearing things like I’d like to learn more. I’d like to cross-train. I’d like to grow into a lead role someday. Those statements communicate commitment. And like we've learned, commitment gets attention.  As we wrap up today’s episode, I’d like to leave you with a challenge. If you’ve been applying for jobs and not getting results, don’t immediately assume there are no opportunities. Ask yourself a different question. Am I making it easy for an employer to hire me? Am I communicating effectively? Am I presenting myself professionally? Am I demonstrating reliability? Am I showing a willingness to learn?  It’s just a fact that in today’s world, employers are looking for more than experience. They’re looking for trust. They’re looking for consistency. They’re looking for commitment. The jobs are out there. The opportunities and careers are out there. Not to sound corny but the question isn’t always whether the job is available. The question is, Are you available for the job?  Ok, we're running over today so with all that I'll say thank you for joining me today, and please share any thoughts on job opportunities with our Facebook group @whseops or our Instagram feed waocpodcast. Until next time, be safe, stay productive, and keep building your career.

Today the gang compares cost versus reliability when buying kilns and kiln shelves. The episode starts with a question about purchasing S-type thermocouples for new kilns and a discussion about preventing warping in cordierite kiln shelves. On a related but strange note, they also talk about how a popular outdoor grill helped lead the U.S. into our current talc shortage.   Have you checked out the new For Flux Sake Patreon? This is a great way to show your support and have access to discounted merch, live hangouts, and extra episodes. Head over to Patreon and sign up today.    Today's episode is brought to you by Rohde Kilns, Monkey Stuff, The Rosenfield Collection, Cornell Studio Supply, and Ceramic Materials Workshop's Making Glaze Make Sense.   This week's episode features the following topics: S-type, K-type, thermocouple, cordierite, advancer, kiln shelf, Big Green Egg, talc  

Discover the science behind high-performance lubricants in this episode of EPARTRADE Race Industry Now featuring James Rappaport, VP of North American Sales for Industrial Fluids at Metalloid, and Anna Jurczyk, Manager of Inside Sales. Hosted by Joe Castello of WFO Radio.In this technical discussion, Metalloid explores how advanced lubricants, greases, corrosion inhibitors, cleaners, and metalworking fluids help improve reliability, reduce downtime, and protect components in demanding racing and industrial environments.Topics covered include:✅ High-performance polyurea greases for motorsports✅ Corrosion protection and penetrating lubricants✅ Metalworking fluids and fabrication applications✅ Brake cleaners and maintenance products✅ High-temperature lubrication solutions✅ Tube bending and forming lubricants✅ Racing applications from Sprint Cars to Road to Indy✅ Preventative maintenance strategies for improved reliability✅ Real-world product testing in motorsportsWhether you're a race engineer, engine builder, fabricator, machinist, manufacturer, or maintenance professional, this episode provides valuable technical insights into the role lubrication plays in performance and durability.Featuring:• James Rappaport – VP of North American Sales for Industrial Fluids, Metalloid• Anna Jurczyk – Manager of Inside Sales, Metalloid• Hosted by Joe Castello of WFO RadioAbout EPARTRADE Race Industry NowEPARTRADE Race Industry Now is the weekly webinar series connecting the global racing industry with technical experts, manufacturers, and industry leaders.

In this episode of The Electropages Podcast, host Robin Mitchell speaks with Ulderico Arcidiaco, CEO and Co-Founder of Sfera Labs, about the company's latest industrial Raspberry Pi platform, the Strato Pi Plus. Ulderico explains how Sfera Labs combines Raspberry Pi computing with industrial-grade connectivity, reliability, and edge computing capabilities. The discussion explores the challenges of designing hardware for industrial environments, including isolated RS485 communications, CAN FD networking, power management, long-term availability, and remote deployment. The conversation also covers the current memory and supply chain situation affecting Raspberry Pi products, why pricing uncertainty has become a major challenge for industrial developers, and why availability often matters more than cost for long-life industrial systems. A major focus of the episode is the architecture of the Strato Pi Plus, which combines a Raspberry Pi 5 with an RP2354 microcontroller. Ulderico explains how the microcontroller can manage communications, watchdog functions, power control, failover systems, and storage management independently of the main processor. This allows developers to create highly reliable edge computing systems capable of recovering from faults, switching boot devices, managing power consumption, and maintaining operation in remote installations. Engineers will also hear discussions on CAN bus timing, real-time processing, industrial automation, energy storage systems, environmental monitoring, maritime applications, and the benefits of combining high-performance computing with deterministic microcontroller control.  Whether you're developing industrial automation systems, edge servers, remote monitoring solutions, or Raspberry Pi-based products, this episode provides valuable insight into designing reliable embedded platforms for demanding real-world environments.

Stay informed on current events, visit www.NaturalNews.com  - PJM Grid Crisis and Data Center Impact (0:10) - PJM's Reserve Shortfall and Price Controls (3:26) - Impact of Data Centers on PJM Grid (6:04) - Preparation for Power Outages (12:44) - Battery Technology and Future Investments (27:26) - IPOs and Market Bubbles (30:56) - Introduction of First Green Electric Skid Steers (54:09) - Advantages of Electric Skid Steers (1:05:56) - Challenges and Future of Electric Equipment (1:12:49) - Remote Control and Job Efficiency (1:22:42) - Skepticism and Operator Experience (1:27:35) - Product Models and Market Positioning (1:28:39) - Pricing and Maintenance (1:30:33) - Future of Electric Heavy Equipment (1:34:40) - Safety and Operator Training (1:44:13) - Customer Experience and Dealer Network (1:49:04) - Regulatory and Market Dynamics (1:52:02) - Future of Battery Technology (1:52:43) - Decentralized Living and Off-Grid Solutions (1:53:58) - Anniversary and Guest Announcements (2:25:52) - UNA Consultations and Market Demand (2:31:45) - Legal Recognition and Benefits of UNAs (2:35:07) - Risk Management and Liability (2:37:58) - Technology and Innovation (2:40:48) - Show Production and Guest Invitations (2:52:22) - Supporting Providers and Product Recommendations (2:52:38) - Closing Remarks and Future Plans (2:52:56) Watch more independent videos at http://www.brighteon.com/channel/hrreport  ▶️ Support our mission by shopping at the Health Ranger Store - https://www.healthrangerstore.com ▶️ Check out exclusive deals and special offers at https://rangerdeals.com ▶️ Sign up for our newsletter to stay informed: https://www.naturalnews.com/Readerregistration.html Watch more exclusive videos here:

Can archaeology really confirm what the Bible records? In this episode of inContext, Dr. Michael Easley sits down with archaeologist and Dallas Theological Seminary professor Dr. Paul Weaver to discuss his new book, Faith Affirming Findings: 50 Archaeological Discoveries That Validate the Historicity and Reliability of Scripture. From the fallen walls of Jericho to Hezekiah's Tunnel, the Pool of Siloam, Peter's house in Capernaum, and the famous Lachish Reliefs, Dr. Weaver explores some of the most compelling archaeological discoveries connected to the biblical world. Together, they discuss how these findings continue to challenge skepticism and strengthen confidence in the Bible's historical reliability. Whether you're interested in biblical archaeology, apologetics, Israel, or defending your faith, this conversation offers fascinating insights into how archaeology helps illuminate Scripture and its historical context. If you've ever wondered whether the Bible can be trusted, this episode is for you. Chapters 00:00 Archaeology and the Bible: Critics Proven Wrong 00:40 Introduction to Dr. Paul Weaver 03:23 Can Archaeology Validate Scripture? 03:51 Minimalists vs. Maximalists Explained 07:56 Jericho and the Fallen Walls 12:14 The Lachish Reliefs and Assyrian Evidence 17:10 Hezekiah's Tunnel and Jerusalem's Defense 21:10 The Discovery of the Pool of Siloam 22:33 Peter's House in Capernaum 26:33 The Magdala Synagogue Discovery 33:30 Caesarea Philippi and Peter's Confession 38:13 Why Archaeology Strengthens Faith 39:16 Final Encouragement for Bible Students Key Topics Covered Biblical archaeology and Christian faith Archaeological evidence for Scripture David, Belshazzar, and historical verification Jericho and Joshua's conquest The Lachish Reliefs and King Sennacherib Hezekiah's Tunnel in Jerusalem The Pool of Siloam discovery Peter's house in Capernaum The Magdala Synagogue Caesarea Philippi and Jesus' ministry Bible reliability and apologetics Israel and archaeological discoveries How archaeology responds to skepticism Faith-affirming evidence from the ancient world Links Mentioned Faith Affirming Findings by Dr. Paul Weaver More of Dr. Weaver's books Watch the highlights and full version of this interview on our Youtube channel. For more inContext interviews, click here.

PagerDuty SVP Rukmini Reddy explains why AI is making software operations exponentially more complex — and why the companies that learn and recover fastest will be the ones that win.Topics Include:PagerDuty powers critical digital operations for enterprises and AI-native companies.Founded by early AWS employees who experienced always-on system failures firsthand.The platform evolved from simple alerting into a full operational intelligence platform.Complexity exploded with microservices, cloud-native infrastructure, and multi-cloud environments.Reliability must be a core value — not an operational afterthought.PagerDuty's culture champions the customer above everything else.Employee recognition extends beyond sales to celebrate the whole business.AI is accelerating software creation but making operations far more complex.AI fails differently — silently, unpredictably, with a much larger blast radius.Enterprises should leverage their operational history as a competitive AI asset.AI-native companies must build operational resilience early, not bolt it on later.The winners won't build fastest — they'll learn and recover fastest.Participants:Rukmini Reddy – Senior Vice President of Engineering, PagerDutySee how Amazon Web Services gives you the freedom to migrate, innovate, and scale your software company at https://aws.amazon.com/isv/

What is Reliability? Abstract What is the definition of reliability? Outside of the field of reliability, who defines it or what a failure is? Join Mojan and Fred as they explore how reliability is perceived across the product development ecosystem—from customers to suppliers to design engineers—and why the classic “but it met the spec!” defense […]

In this episode of The Cleft Palate Craniofacial Journal podcast series, Pat Chibbaro, Multimedia Specialist, interviews Amy Davies, author of the CPCJ article entitled, "Intra- and Inter-Rater Reliability and Validation of Orofacial Cleft Classification in the Cleft Collective Cohort Study" (coauthored by David Sainsbury, The Cleft Multidisciplinary Collaborative, Jibby Medina, Craig Russell, Kerry Humphries, Kate J. Fitzsimons, Jonathan Sandy, Scott Deacon, and Yvonne Wren).

Send us Fan MailThis week on Truck News Recap, we're diving into the biggest known problems reported by Nissan Frontier owners from the 2023-2026 model years.From transmission complaints and electrical glitches to recalls and owner concerns, here's what buyers need to know before purchasing a Nissan Frontier.Plus, Toyota has released new information about the Tundra engine replacement program, including details on when the updated main bearing entered production. We'll break down what the latest update means for current owners and anyone considering a new Tundra.Topics include:• 2023-2026 Nissan Frontier known problems• Transmission complaints• Electrical and infotainment issues• Frontier recalls• Toyota Tundra engine replacement update• New main bearing production timeline• Weekly truck industry newsLet me know in the comments:Would you buy a Nissan Frontier over a Toyota Tacoma?#NissanFrontier #ToyotaTundra #TruckNews #PickupTruckTalk #Nissan #Toyota #Frontier #Tundra #TruckProblems #TruckReliabilityVisit Screen Pro Tech and get 15% off: https://screenprotech.com/TimSupport the show

Joe Kuhn, CMRP, former plant manager, engineer, and global reliability consultant, is now president of Lean Driven Reliability LLC. He is the author of the book “Zero to Hero: How to Jumpstart Your Reliability Journey Given Today's Business Challenges” and the creator of the Joe Kuhn YouTube Channel, which offers content on starting your reliability journey and achieving financial independence. In our monthly podcast miniseries, Ask a Plant Manager, Joe considers a commonplace scenario facing the industry and offers his advice, as well as actions that you can take to get on track tomorrow. In this episode of Great Question: A Manufacturing Podcast, Joe Kuhn of Ask a Plant Manager discusses leadership habits that strengthen maintenance and reliability.

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

Why Gaps? Abstract Carl and Fred discuss why effective reliability planning begins with identifying the gaps between an organization's current capabilities and its long-term reliability vision. Key Points Join Carl and Fred as they discuss why identifying gaps are often missed in reliability planning and how to remedy. Topics include: Reliability planning should begin with […]

**Sponsored by EasyDNS** Move your domain or web hosting to EasyDNS and support Not On Record: https://easydns.com/NotOnRecord Use promo code: **notonrecord** In Episode 214 of *Not On Record*, criminal defence lawyer Joseph Neuberger and Diana Davison examine the important Ontario Court of Appeal decision R. v. C.P., 2026 ONCA 333 and discuss how mental illness can properly factor into assessing witness reliability and credibility in criminal trials. The case involved allegations of sexual assault against a biological father and raised complex questions about a complainant who had a documented history of hallucinations, delusions, medication non-compliance, and street drug use during the period of the alleged offences. The Court of Appeal was asked to determine whether the trial judge improperly relied on myths and stereotypes about mental illness when acquitting the accused. Joseph and Diana explain the critical legal distinction between credibility and reliability, why mental illness alone cannot be used to discount a witness's evidence, and when case-specific evidence of hallucinations, delusions, panic attacks, psychiatric symptoms, or medication issues may legitimately become relevant at trial. They also discuss third-party psychiatric records applications, the evidentiary foundation required to raise mental health issues in court, and why judges must carefully avoid discriminatory reasoning while still assessing reliability based on evidence. This episode provides valuable guidance for criminal lawyers, law students, and anyone interested in how Canadian courts balance fairness, mental health considerations, and the search for truth in the justice system. ### **Chapters** **00:00** Introduction to R. v. C.P. (2026 ONCA 333) **02:19** Mental illness, credibility, and reliability explained **04:21** Hallucinations, delusions, medication, and street drug use **07:10** Crown appeal and myths about mental illness **10:13** Evidence supporting reliability concerns **14:29** Accessing psychiatric and therapy records in criminal cases **16:11** Why the Court of Appeal upheld the acquittal **21:34** Lessons for lawyers handling mental health evidence

Success is not about luck or connections handed to you — it comes down to two things: information and access, and most people are missing both. I learned this at a dinner with a highly affluent man, and it connected back to something my brother and I were already doing as kids hustling baseball cards in Abilene, Texas. In this episode, I break down exactly how to position yourself to attract the right information and earn your way into the rooms that matter. Key Takeaways Success breaks down to two core elements: having the right information and having access to execute on it. If you are the end user of news and social media, you are not in the loop — you are the product being sold. Become an expert in your field and people will naturally bring information to you instead of you having to chase it. Reliability is the key to access — people at high levels need to know that if you say you will do something, it gets done, no excuses. Networking only works when you bring either information or access to the table — without one of them, you are just exchanging business cards with people who do not care. Action Steps Audit where your information is coming from this week — if it is only social media or news, find one expert, mentor, or industry insider you can connect with who operates closer to the source. Identify one area where you can become so reliable and excellent that people in higher rooms begin to notice and invite you in. Before your next networking event or meeting, determine whether you are bringing information or access to offer — if you cannot answer that, do the work first before you show up. Notable Quote It is so much easier to attract people than it is to chase people. Be an attraction.

Today, we're going to explore a topic that doesn't always get the attention it deserves but has a direct impact on product quality and long-term reliability. Mike Konrad is joined by Mehdi Nahali, founder of PCB Revision Control PRO. His platform is designed to replace spreadsheets, emails, and disconnected systems with a centralized approach to PCB revision lifecycle management and factory intelligence.  They going to talk about how revision control, data integrity, and process discipline impact reliability, and where manufacturers are still getting it wrong.

Craig Unger discusses U.S. unreliability and the future of the NATO alliance, noting that under Trump, the United States is seen as an unreliable partner by allies like Finland, who fear he will not honor Article 5. This lack of reliability forces European nations to consider whether they can emerge as a self-sufficient military power. (14)1936

Benjamin and Chance discuss the illustrations Bloomberg published depicting iOS 27 and the new Siri interface. Also, we talk about rumors of a revamped AirPods settings UI, phone snatching detection in iOS 26.6 code, and Digitimes says the Apple Watch Ultra 4 will feature a significant redesign. Also, has AirDrop got worse? And in Happy Hour Plus, Apple showcases the iPhone 17 Pro by producing and broadcasting the first full live sports game using ‘just' iPhones. Subscribe at 9to5mac.com/join. Sponsored by Bartender: Bartender Pro is a new option for users who want to take things up a notch. Visit macbartender.com/happyhour to check it out. Sponsored by Copilot Money: Get two months free with code 9TO5MAC at copilot.money/9to5mac. Sponsored by Shopify: See less carts go abandoned and more sales. Sign up for a $1 per month trial at shopify.com/happyhour. Hosts Chance Miller @ChanceHMiller on Twitter @ChanceHMiller on Instagram @ChanceHMiller on Threads Benjamin Mayo @bzamayo on Twitter @bzamayo@mastodon.social @bzamayo on Threads Subscribe, Rate, and Review Apple Podcasts Overcast Spotify 9to5Mac Happy Hour Plus Subscribe to 9to5Mac Happy Hour Plus! Support Benjamin and Chance directly with Happy Hour Plus! 9to5Mac Happy Hour Plus includes:  Ad-free versions of every episode  Pre- and post-show content Bonus episodes Join for $5 per month or $50 a year at 9to5mac.com/join.  Feedback Submit #Ask9to5Mac questions on Twitter, Mastodon, or Threads Email us feedback and questions to happyhour@9to5mac.com Links iOS 27 leak reveals new Siri design, Camera app, more Report: iOS 27 to revamp the AirPods settings UI Report: watchOS 27 to improve heart-rate tracking; AI health coach may not debut at launch Apple Intelligence image models to boast 'major' visual upgrades in iOS 27: report Apple Watch Ultra 4 getting two major new upgrades, per report Apple Watch could soon gain new high blood pressure feature iOS 26.6 adds new alert when you try blocking too many contacts Apple working on iPhone anti-snatching feature that locks the device automatically New Oura Ring 5 unveiled with dramatically smaller design, hypertension detection, more Apple TV to air first major live sporting event shot entirely on iPhone 17 Pro How Apple Shot an Entire MLS Game Using Only iPhone | PetaPixel Eddy Cue named 2026 Cannes Lions Entertainment Person of the Year

Haroon Inam is Co-founder and CEO of DG Matrix, a company that makes the world's most compact Power Router, aggregating distributed energy for GenAI datacenters, microgrids, fleet electrification, and associated systems. As AI workloads drive unprecedented electricity demand and legacy grid infrastructure struggles to keep pace, DG Matrix has commercialized the world's first multi-port solid-state transformer to meet the energy needs. In this episode, Inam explains why transformer bottlenecks, distributed generation, and 800V DC architectures are reshaping the future of power delivery for AI infrastructure. He discusses DG Matrix's product strategy, manufacturing scale-up plans, and the role of software-defined power systems in next-generation data centers. Finally, Inam shares his take on the future of distributed microgrids and “cellular power” and how to scale power electronics manufacturing. DG Matrix recently closed a $60 million Series A led by Engine Ventures that MCJ is proud to have participated in.  Episode recorded on May 13, 2026 (Published on May 26, 2026) In this episode, we cover:  (00:00) Overview of DG Matrix  (01:41) Introducing the Founders: Haroon Inam and Dr. Bhattacharya (05:25) How traditional grid architecture became constrained for AI workloads (09:57) Solid-state transformers (SST), multi-port systems and voltage classes (12:18) Why early SST efforts struggled economically (13:13) How DG Matrix's multi-port architecture works (16:48) Comparing DG Matrix hardware footprint to legacy power systems (20:08) Transformer shortages and data center infrastructure bottlenecks (24:27) DG Matrix's medium-voltage and low-voltage product strategies (27:55) Product rebranding and current commercial deployments (30:45) Partnerships with EPC firms, battery providers, and turbine manufacturers (34:27) Manufacturing scale-up plan and hyperscaling production (36:36) Supply chain strategy to avoid rare earth dependencies (38:16) Reliability engineering and software-defined power systems (43:47) DG Matrix's go-to-market and hybrid hardware/software business model (46:36) The vision for distributed “cellular power” (48:14) Utilities, microgrids, and the future of interconnected distributed infrastructure Enjoyed this episode? Please leave us a review! Share feedback or suggest future topics and guests at info@mcj.vc.Connect with MCJ:Cody Simms on LinkedInVisit mcj.vcSubscribe to the MCJ Newsletter*Editing and post-production work for this episode was provided by The Podcast Consultant

What happens when you spend so much time being "reliable" that you forget how to be meaningful?   In this third installment of Reports from the Creative Closet, I'm exploring the "Be Good" trap. We often learn very early that being predictable and agreeable is safer than being fully alive, but that safety comes at a high price.   I discuss the Traffic Rule Covenant—a look at how we use rules to reduce uncertainty, and what happens when we stop treating those rules as tools and start treating them as our identity. We'll explore the "quiet grief" of adulting, the friction of being "manageable" in professional environments, and why your "rough edges" are actually the parts of you the world needs most.   I'm Nancy Norbeck, and I'm your Messy Muse Mentor. I help people feel alive again through creativity, curiosity, and play.   In this episode, I discuss: The Social Survival Instinct: Why we'll do anything to avoid being "thrown out" of the community. The Traffic Light Metaphor: Understanding rules as tools for safety rather than definitions of self. The Reliability Tax: Why professional "manageability" often requires us to override our internal signals. The Adulting Lie: Why being a "grown-up" shouldn't require you to abandon your curiosity and play. If you're tired of thinking about answering a creative call but never actually doing it, come join me for an hour and start feeling like yourself again. The Follow Your Curiosity Creativity Circle is a safe, welcoming, and encouraging environment where we send the shoulds and inner critics off to summer camp where they're kept busy rather than getting in our way. Join us here!

What does success look like for transit agencies in a post-pandemic world? According to Christie Wegener, it may be time to stop measuring against 2019 altogether.In this episode of Transit Unplugged, host Paul Comfort speaks with Christie Wegener, Executive Director of the Livermore Amador Valley Transit Authority (LAVTA), about the changing realities of suburban transit, evolving commuter behavior, and why reliability may matter more than ridership.Christie explains how LAVTA serves as a critical feeder to BART while navigating the unique challenges of Bay Area travel patterns, remote work, and car-oriented suburban development. She also shares why she believes transit agencies need to rethink traditional KPIs like farebox recovery and pre-COVID ridership comparisons.The conversation also explores:Why transit agencies may need a new baseline for measuring success The operational challenges of coordinating with BART service How cloud-based transit signal priority could reduce travel times Lessons learned from LAVTA's Uber/Lyft partnership and microtransit programs The realities of serving low-density suburban communities LAVTA's new $64 million headquarters project Transit funding challenges facing the Bay Area Christie's journey from social work and public policy into transit leadership CreditsHost and Producer: Paul Comfort Executive Producer: Julie Gates Producer: Chris O'Keeffe Editor: Patrick Emile Associate Producer: Cyndi Raskin Brand Design: Tina Olagundoye Transit Unplugged is brought to you by Modaxo, passionate about moving the world's people.For more information, visit: www.Transit Unplugged.comDisclaimer: The views and opinions expressed in this program are those of the guests, and do not necessarily reflect the views or positions of Modaxo Inc., its affiliates or subsidiaries, or any entities they represent (“Modaxo”). This production belongs to Modaxo, and may contain information that may be subject to trademark, copyright, or other intellectual property rights and restrictions. This production provides general information, and should not be relied on as legal advice or opinion. Modaxo specifically disclaims all warranties, express or implied, and will not be liable for any losses, claims, or damages arising from the use of this presentation, from any material contained in it, or from any action or decision taken in response to it.

We'd love to hear from you. Send us fan mail!Role clarity is the most underleveraged driver of leadership performance, and most organizations aren't building it. In this episode of Shedding the Corporate Bitch, executive coach Bernadette Boas sits down with Jackson Lynch, founder of Talent Sherpa, to examine why talented people consistently underperform when the architecture around them is broken. Drawing on W. Edwards Deming's research that 94% of performance problems are systemic, not personal, Jackson makes a compelling case that organizations have been investing in the wrong place.The conversation moves from theory to practice quickly. Jackson breaks down what role architecture actually means: defining five to seven outcomes for any role so that everyone in the system, the incumbent, their manager, their peers upstream and downstream, knows exactly what winning looks like. Without that, accountability becomes blame, engagement flatlines, and even your highest-potential leaders are flying blind.For HR leaders, this episode reframes the function itself. Jackson challenges the compliance-first model that most human capital teams operate within and argues that the real job is to identify talent constraints before the strategy is executed, not after things go sideways. What You Will LearnWhy 94% of performance problems are architectural, not personal, and what that means for how you develop leadersHow to define the 5–7 outcomes that tell any role what winning looks likeWhy decision rights must be directly tied to accountability and what breaks when they aren'tThe difference between accountability (backward blame) and reliability (forward ownership) — and which one actually produces resultsHow to use a talent portfolio optimization model to put the right people in the highest-impact rolesWhy HR's shift from compliance partner to business constraint solver changes organizational performanceHow auditing your calendar reveals whether you are leading strategically or managing noiseEpisode Chapters [00:00 — Welcome & Why Leadership Architecture Matters More Than Talent02:00 — The Biggest Leadership Misconception: It's the System, Not the Person03:00 — What Role Architecture Actually Means — Outcomes, Decision Rights & Boundary Conditions05:00 — Role Clarity in Practice: Defining What Winning Looks Like07:00 — Reframing Accountability as Reliability — and Why It Changes Everything08:00 — The AI Fog Problem: Why Automating Unclear Roles Scales the Problem10:00 — The Real Cost of Not Defining Outcomes: Opportunity Loss13:00 — How to Drive Accountability Without Blame16:00 — Why Leaders Stay Stuck in Tasks: Dopamine, Busyness & the Arsonist Problem18:00 — The Talent Portfolio Optimization Model vs. Traditional Succession Planning21:00 — How to Sequence Talent Decisions for Maximum Business Impact23:00 — How HR and Business Leaders Should Partner on Talent Strategy29:00 — Moving Your Team From Busy to Impactful32:00 — Nobody Gets Overwhelmed Knowing What Winning Looks Like33:00 — Audit Your Calendar: The One Move That Changes Everything35:00 — Where to Find Jackson Lynch & Talent SherpaAbout the Guest Jackson Lynch is the founder of Talent Sherpa, where he works with CEOs and executive teams to build the role clarity, decision rights, and outcome-defined accountability structures that drive business performance. With 25 years in human capital — from the factory floor to senior leadership in public companies — Jackson brings an operator's perspective to the systemic gaps that most leadership development programs never address. He also publishes a weekly Substack followed by more than 6,000 human capital practitioners. Learn more at mytalentsherpa.com and connect with Jackson on LinkedIn at linkedin.com/in/jxnlynch.Related EpisodesYour Calendar is Lying: HERE  — how you need to become an attention manager vs. time managerYour Company is Not a Machine with Norman Wolfe PART 1 HERE — how leaders need to shift from managing tasks to leading the heart of the company; your people.How to Stop Managing the Machine with Norman Wolfe PART 2 HERE — the four concrete leadership skills that make the framework operational, and more importantly, why most leaders are missing all of themSubscribe If this conversation gave you something you can use, subscribe to Shedding the Corporate B!tch on YouTube, Apple Podcasts, or Access all of the full episode on Ball of Fire Coaching. Each episode is built for executives, HR leaders, and corporate professionals who want direct, no-nonsense insight on what it actually takes to lead at the highest levels. New episodes every week at ballofirecoaching.com/podcast.Support the show

The Reliability Contract Abstract Dianna and Fred discuss the reliability contract: the RE’s role as internal consultant. Key Points Join Dianna and Fred as they discuss the reliability engineer’s role as an internal consultant and why setting clear expectations is vital for project success. Topics include: the three main ways reliability experts provide value  how […]

This Sunday's message will be very different than what we are used to. Our steady diet of preaching has been (and will continue to be) exposition through books of Scripture, verse by verse. However, along our journey through Mark's gospel, we occasionally noticed missing verse numbers (7:16; 9:44), and when we finished Mark 16:1-8, the next thing we saw was brackets around Mark 16:9-20 and a study note that says something to the effect of "the earliest manuscripts do not contain these verses." The easiest thing to do would be to simply make that statement, move on, and start preaching through another book. But this section offers a unique opportunity. Sunday, we will examine how God has reliably preserved His word down through time to us and look at the actual evidence for and against Mark's longer ending. Rather than just giving you my opinion about Mark's ending, I will walk you through the process of examining the evidence, which is not hidden or out of reach for Christians. With all the objections to textual corruption, books added to or taken out of the Bible, and the idea that we Christians depend on unknown scholars to tell us what is in our scriptures, I have three goals for Sunday. I hope to show you how the New Testament documents have been reliably passed down to us, let you see and examine the evidence concerning Mark's ending, and use this opportunity to address how we know the 66 books of our Bibles are the only God-inspired books. Accomplishing those three goals in under 40 minutes will be as miraculous as parting the Red Sea, so we certainly can't say everything that needs to be said, but in the end, we will see that God has preserved His Word in the Bible that you carry. The Bible you hold in your hand is God's Word, sufficient and God-breathed, so that you would know Him through the gospel of Jesus. I. Has God Reliably Preserved His Word In the NT? II. Examining Mark's Ending: Are we depending on "scholars" we don't know? III. How do we know the books in our Bibles are the only inspired books?

Reliability and Volume Abstract Dianna and Fred discuss reliability and volume, comparing high-volume products with low-volume high-stakes products. Key Points Join Dianna and Fred as they compare reliability strategies for NASA’s one-of-a-kind lunar instruments versus mass-produced consumer electronics. Topics include: why the definition of reliability remains constant for the customer  how risks shift from craftsmanship […]

Season 26, Episode 15 - Shaun Boyce, Bobby SchindlerSummaryIn this episode, Bruce, a seasoned tennis coach and software developer, shares insights on modernizing tennis club management with innovative software, the importance of technology in increasing court utilization, and ideas for making tennis more accessible for kids. The discussion covers software features like churn detection, AI-driven court management, and strategies to grow the sport.Key TopicsTennis software development and featuresCourt management and revenue optimizationStrategies to grow tennis participation among youthChapters00:00 Introduction and Guest Background01:23 Bruce's Day-to-Day Tennis Coaching03:00 Teaching Adults vs. Kids in Tennis03:54 Bruce's Passion for Teaching and Longevity05:01 Introduction to Tennis Edge CRM Software05:48 Customizable Features for Clubs and Coaches07:13 Churn Detection and Engagement Strategies08:10 AI-Driven Revenue Opportunities in Tennis Clubs08:50 Filling Open Courts and Lesson Slots with AI09:47 Efficiency and Professionalism for Coaches10:58 Challenges with HOAs and Club Management11:57 Convincing HOAs to Invest in Technology12:58 Pricing Models and Business Sustainability13:57 The Future of Tennis Technology and AI14:48 Cost Structures and Subscription Models16:02 Bruce's Vision for Growing Tennis Participation16:53 Leveling Prize Money and Supporting Players18:02 The Impact of Technology on Tennis Revenue18:49 The Role of Software in Modern Tennis Coaching20:04 Independent Coaches and Cost-Effective Solutions20:54 Customer Service and Reliability in Software21:50 The Evolution of Court Management Technology22:46 Educating HOAs and Facility Managers24:11 Making Tennis More Accessible for Kids24:59 The Importance of Early Exposure to Tennis25:59 Growing the Sport Through School Programs26:52 Reducing Entry Barriers for New Players28:12 The Benefits of Cashless and Automated Payments28:52 The Future of Tennis Software and AI Integration29:51 Bruce's Final Thoughts and Vision for Tennis31:01 King of Tennis: Bruce's Vision for the SportKeywordsTennis software, court management, tennis coaching, sports technology, tennis industry, club management, AI in sports, tennis growth, tennis accessibility, sports innovationFull YouTube Video: https://youtu.be/3vDZmTWDLRQBruce's King of Tennis Answer: https://youtube.com/shorts/V1cjfjm1PJULearn more about TennisEdgeCRM: https://tennisedgecrm.comContact Our HostsShaun Boyce, RSPA: shaun@americanracketsportsassociation.com | https://americanracketsportsassociation.com/Bobby Schindler, RSPA: schindlerb@comcast.net | https://letsgotennis.com/windermereGeovanna Boyce: geovy@regeovinate.com | https://regeovinate.com/GoTennis Website: https://letsgotennis.com/Learn more about the Marc Kaplan Media Excellence Award we (the GoTennis! Podcast) won from USTA Georgia: https://letsgotennis.com/captivate-podcast/gotennis-podcast-wins-the-marc-kaplan-media-excellence-award/Join Our CommunityCheck out the GoTennis! Atlanta Facebook page for deals, updates, events, podcasts, news, stories, coach profiles, club information, and more.Support the ShowDonate Directly: https://gotennispodcast.captivate.fm/supportCrypto Donations: Get into crypto with https://coinbase.com/join/PEWRLWK?src=referral-linkStart Your Own PodcastConsidering your own podcast? We recommend Captivate: This podcast is hosted by Captivate, try it yourself for free.

Industrial Talk is onsite at Xcelerate 2026 and talking to Nikki Smith with Lineage and Niccolette Hyland with Fluke about "Women in Reliability". Overview The Industrial Talk podcast, sponsored by Fluke, featured a discussion on women in reliability with Nikki Smith and Niccolette Hyland. Nikki, with 18 years in reliability, shared her journey from safety to engineering after her husband's workplace accident. Niccolette , in marketing, highlighted the importance of women in engineering and reliability, citing her experience with male-dominated fields. They discussed the cultural impact at Fluke, emphasizing teamwork and psychological safety. Nikki mentioned Lineage Logistics' 500+ sites and their CMMS implementation, aiming for 100% completion in North America. The conversation underscored the need for diverse perspectives in reliability and the potential of AI to enhance maintenance. Outline Fluke's Xcelerate Event Overview Scott introduces the Industrial Talk podcast, sponsored by Fluke, highlighting the Xcelerate event.Scott praises industry professionals for their innovation and collaboration, promoting the event in Austin, Texas.The podcast aims to celebrate industry heroes and their contributions to making the world a better place. Introduction of Women in Reliability Panel Scott introduces the panel on women in reliability, featuring Niccolette and Nikki.Scott acknowledges the male-dominated nature of the industry and expresses excitement about the female participants.Nikki Smith, shares her background, working for Lineage Logistics in reliability for 18 years.Nikki mentions her Canadian background and her journey into reliability after her husband's workplace accident. Niccolette's Background and Event Planning Niccolette, introduces herself, mentioning her role in marketing and event logistics.Niccolette discusses her transition from a male-dominated field to event planning and her passion for women in engineering and reliability.Scott and Niccolette discuss the importance of women in reliability and the need for diverse perspectives.Niccolette shares her experience with Fluke's Women in Utility conference and the success of the women in reliability panel at Xcelerate. Nikki's Journey into Reliability and Safety Scott asks Nikki about her journey into reliability and safety.Nikki recounts her husband's workplace accident and her subsequent focus on safety and reliability.Nikki describes her role at Lineage Logistics, a global organization with 500+ sites, and their focus on food logistics.Nikki discusses the implementation of CMMS systems at Lineage, starting with x4 and transitioning to x5 for better enterprise-wide visibility. Challenges and Successes in Implementing CMMS Systems Scott inquires about the challenges and successes of implementing CMMS systems at Lineage.Nikki explains the importance of standardization and framework for successful implementations.Nikki highlights the ongoing implementation journey, with 104 sites live on x5 and the goal of completing North America within three months.Nikki emphasizes the need for user engagement and feedback to build a better system. Women in Reliability and Diversity in Teams Scott and Nikki discuss the importance of diversity in reliability teams.Nikki explains how different perspectives from women bring new ideas and improve reliability.Nikki shares her experience with mentors and the value of having supportive men in the industry.Nikki encourages women to step up and take opportunities in male-dominated fields. Fluke's Culture and Client Impact Scott and Niccolette discuss the culture at Fluke and its impact on clients.Niccolette highlights the supportive and collaborative environment at Fluke, which helps clients feel comfortable and engaged.Niccolette shares her experience with client interactions at Xcelerate and the positive feedback from clients.Nikki adds that Fluke's team approach and willingness to help create a positive work environment. The Role of Culture in Attracting Talent Scott and Niccolette discuss the role of culture in attracting and retaining talent.Niccolette emphasizes the importance of creating a safe and supportive environment for employees.Niccolette shares her experience with Fluke's autonomy and support for special projects and team collaboration.Nikki adds that a positive culture helps in attracting young talent and fostering a sense of belonging. The Future of Reliability and AI Scott and Niccolette discuss the future of reliability and the role of AI.Niccolette highlights the new AI features launched by Fluke and their potential to revolutionize reliability and maintenance.Niccolette emphasizes the need for companies to push the envelope and adopt new technologies.Niccolette shares examples of how AI can improve efficiency and reduce frustration in reliability tasks. Conclusion and Contact Information Scott wraps up the conversation, expressing gratitude to Nikki and Niccolette for their insights.Scott provides contact information for Nikki and Niccolette for listeners interested in reaching out.Scott encourages listeners to connect with Industrial Talk and share their stories to inspire the next generation of industrial leaders.Scott promotes the upcoming conversations and events from Xcelerate, highlighting the importance of celebrating industry professionals. If interested in being on the Industrial Talk show, simply contact us and let's have a quick conversation. Finally, get your exclusive free access to the Industrial Academy and a series on “Why You Need To Podcast” for Greater Success in 2026. All links designed for keeping you current in this rapidly changing Industrial Market. Learn! Grow! Enjoy! NIKKI SMITH'S CONTACT INFORMATION: Personal LinkedIn: https://www.linkedin.com/in/smith-nikki-260a3786/ Company LinkedIn: https://www.linkedin.com/company/onelineage/ Company Website: https://www.onelineage.com/ NICCOLETTE HYLAND'S CONTACT INFORMATION: Personal LinkedIn: https://www.linkedin.com/in/niccolette-h-4214505b/ Company LinkedIn: https://www.linkedin.com/company/fluke-corporation/ Company Website: https://www.fluke.com/ PODCAST VIDEO: https://youtu.be/xjGsHvf5awo THE STRATEGIC REASON "WHY YOU NEED TO PODCAST": OTHER GREAT INDUSTRIAL RESOURCES: NEOM: https://www.neom.com/en-us Hexagon: https://hexagon.com/ Arduino: https://www.arduino.cc/ Fictiv: https://www.fictiv.com/ Hitachi Vantara: https://www.hitachivantara.com/en-us/home.html Industrial Marketing Solutions:  https://industrialtalk.com/industrial-marketing/ Industrial Academy: https://industrialtalk.com/industrial-academy/ Industrial Dojo: https://industrialtalk.com/industrial_dojo/ We the 15: https://www.wethe15.org/ YOUR INDUSTRIAL DIGITAL TOOLBOX: LifterLMS: Get One Month Free for $1 – https://lifterlms.com/ Active Campaign: Active Campaign Link Social Jukebox: https://www.socialjukebox.com/ Industrial...

In this episode, I sat down with Jared Giblin from Draper Elevator Interiors. We talked about how their business evolved into a highly specialized niche, what goes into designing and installing custom elevator cabs, why interiors require such attention to detail, and what's next for this area of the elevator industry.Chapters:00:00 Intro01:41 The Evolution of Draper and Its Niche in Elevators07:35 Family Business Culture and Its Impact10:47 Expectations vs Reality of Entering the Business12:06 Navigating Challenges in Custom Elevator Interiors15:03 The Importance of Early Involvement in Projects23:54 Reliability and Quality in Elevator Projects27:07 The Complexity of Cab Interiors29:16 Trends in Elevator Interior Design32:43 The Future of Draper and Industry Innovations33:39 Rapid Fire Insights and Closing Thoughts35:02 The Importance of Recruitment in the Elevator IndustryResources:Subscribe: https://www.youtube.com/@elevatorcareers/Submit a Topic Idea for the Podcast: https://elevatorcareers.net/Connect With Us: linktr.ee/AllredGroupA Message from our Sponsor: Looking for top-tier talent to join your team? Call The Allred Group for your elevator recruiting needs! With a deep network and unmatched industry expertise, we quickly connect you with skilled professionals who are ready to elevate your team.  Let us handle the hiring process, so you can focus on growing your business with the best in the industry. Reach out today, and let us help you take your business to new heights!To contact us go to: http://allredgroup.com

[2 Peter 1:20-21] The Bible is not a product of human invention or clever ideas, but God's own speech written down by men who were carried along by the Holy Spirit (2 Peter 1:20-21). Just as the Lord commanded Moses to write His words on stone for every generation (Exodus 34:27), the Holy Spirit moved prophets and apostles so that what they recorded is without error and fully trustworthy. In a world full of false teaching that springs from deceptive human hearts (Jeremiah 23:16), Scripture stands as our reliable interpreter of all things and the life-giving source that enables us to bear fruit for God's glory through Jesus Christ.

Create healthier connections. These affirmations help you release insecurities and past relationship trauma, allowing you to build bonds based on trust and mutual respect. Unwind now with our positive sleep affirmations podcast. Our soothing affirmations relax the mind and prepare the body for rest. Hit play, and drift into Good Sleep... Listen to more positive sleep affirmations by subscribing to the audio podcast in your favorite podcast app:  Apple Podcasts: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://podcasts.apple.com/us/podcast/good-sleep-positive-affirmations/id1704608129⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Spotify: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://open.spotify.com/show/3OuJvYoprqh7nPK44ZsdKE⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ And start your morning with Optimal Living Daily! Apple Podcasts: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://podcasts.apple.com/us/podcast/optimal-living-daily-mental-health-motivation/id1067688314⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Spotify: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://open.spotify.com/show/1hygb4nGhNhlLn4pBnN00j?si=ca60dcfd758b44b4⁠⁠ Learn more about your ad choices. Visit megaphone.fm/adchoices

Right Tool at the Right Time Abstract Philip and Fred discuss a common challenge in reliability engineering: using the right tool—not just the one you’re most comfortable with. Key Points In this episode of Speaking of Reliability, Fred Schenkelberg and Philip Sage explore a common challenge in reliability engineering: using the right tool—not just the one […]

Create healthier connections. These affirmations help you release insecurities and past relationship trauma, allowing you to build bonds based on trust and mutual respect. Unwind now with our positive sleep affirmations podcast. Our soothing affirmations relax the mind and prepare the body for rest. Hit play, and drift into Good Sleep... Listen to more positive sleep affirmations by subscribing to the audio podcast in your favorite podcast app:  Apple Podcasts: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://podcasts.apple.com/us/podcast/good-sleep-positive-affirmations/id1704608129⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Spotify: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://open.spotify.com/show/3OuJvYoprqh7nPK44ZsdKE⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ And start your morning with Optimal Living Daily! Apple Podcasts: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://podcasts.apple.com/us/podcast/optimal-living-daily-mental-health-motivation/id1067688314⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Spotify: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://open.spotify.com/show/1hygb4nGhNhlLn4pBnN00j?si=ca60dcfd758b44b4⁠⁠ Learn more about your ad choices. Visit megaphone.fm/adchoices

Machine vision has long been used in factory automation for quality inspections, the final checkpoint separating acceptable parts from the rework pile or the scrap bin. Today, vision systems are no longer just inspectors. They are becoming adaptive, data-driven participants in the manufacturing process, capable of influencing outcomes rather than simply recording them. In this episode of Control Intelligence, written by contributing editor Joey Stubbs, editor in chief Mike Bacidore discusses how artificial intelligence has impacted the reliability and accuracy of vision systems.

Apologetics, Debate, Bible Discussions, Evangelism, and much more "Christianity is a Person, not a system" - https://youtu.be/1-02nnh5Das?si=8-p2u1cxfCS2Uo4I Discerning the fruits of the Spirit vs the fruits of self - Mark 7:5-23 "The mystic fruit bowl" - https://youtu.be/kw7QiLQMQ_M?si=356Fx_r9ohUeTLwjThe Deity of Jesus Christ and the Gospel of Salvation - https://www.youtube.com/live/gquqBQIL_0U?si=7zmPLi1X0CcW-v7f(Discussing discipleship) Bible study on Luke 9:60-62 "Let the dead bury the dead" - https://www.youtube.com/live/BkWtkOrEs-Q?si=y-zyqNGfWi3kzVu2To know more on how to be saved, what are the requirements and such, please see our playlist on the Gospel and Eternal Security (assurance of salvation) - https://youtube.com/playlist?list=PL3pJdCnnwrEeCQOCTTmDW1GjUYxpd44DG&si=_rT-lThl0klHt5Cd Our Ministries Website - https://christiancoffeetime.ca/ 1John 5:20) "And we know that the Son of God is come, and hath given us an understanding, that we may know him that is true, and we are in him that is true, even in his Son Jesus Christ. This is the true God, and eternal life."

Wind and solar resources are providing more clean, low-cost electricity to the grid than ever before, but the intermittent nature of renewable generation requires careful planning. In the latest episode of the Power Trends podcast, NYISO Director of Grid Transition Udayan Nair breaks down what the latest data reveals about wind and solar performance, and what it means for reliability in New York as electricity demand continues to grow.Notably, the electric grid has seen remarkable growth in behind-the-meter solar capacity in recent years, surpassing the solar goal in the state's Climate Leadership Community Protection Act (CLCPA).“We had a goal in CLCPA to reach 6000 megawatts by 2025,” Nair said. “We were at over 6,800 megawatts of capacity last year and it's grown by about 1,000 megawatts per year since 2020. That's a remarkable success in terms of the capacity that has been added to the grid.”Front-of-the-meter solar, which refers to grid-connected solar installments that participate in the NYISO's energy markets, has also seen increased capacity in recent years. While no new wind installments were added in 2025, existing units performed better than usual due to stronger wind patterns, Nair said. Nair discussed factors that contribute to renewable performance, including seasonal weather, demand patterns, and curtailments. He explained why solar and wind must be paired with transmission, storage, and flexible resources to keep the grid reliable, particularly during summer heat waves and winter cold snaps. The latest renewables data showcases the growing contribution of renewables in the current fuel mix and underscores the need for an all-of-the-above approach to development as New York's electric system continues to evolve. More resources: View the 2025 Renewables Report.Learn MoreFollow us on X/Twitter @NewYorkISO, LinkedIn @NYISO, Bluesky @nyiso.comRead our blogs and watch our videos

In this episode of Electric Perspectives, Gregory A. Beard, director of the Department of Energy's Office of Energy Dominance Financing (EDF), discusses how the federal government is deploying historic levels of capital to strengthen the energy grid and support long-term reliability. Director Beard outlines EDF's focus on lowering costs for customers while improving reliability and energy security, including major recent loans to electric companies and a rapid pace of capital deployment.

Here's the real difference between OpenClaw and Hermes when it comes to actually making money with AI agents. OpenClaw has the bigger ecosystem, more integrations, more community support, and way more features. Hermes is newer, but it's faster, more reliable, and learns alongside you over time through persistent memory and skill files. In practice, that means OpenClaw feels like the execution layer, while Hermes feels more like the brain. In this video I break down where each agent wins across reliability, security, features, and community, how we structure them inside our “single brain” system, why reliability matters more than features for business use cases, and the exact way we're thinking about deploying agent fleets inside companies right now. Chapters: (00:00) OpenClaw vs Hermes overview (00:28) What OpenClaw already helped us achieve (01:05) Why Hermes feels more stable (01:23) The 4 categories that matter most (01:52) How our team uses agents inside Slack (02:25) Reliability problems with OpenClaw (03:14) Security tradeoffs and risks (04:23) Why OpenClaw still wins on community (05:05) Feature comparison between both agents (05:44) Why reliability matters most for business (06:07) Hermes as the “brain” and OpenClaw as execution (06:54) Final verdict on which agent wins today

Episode 224 with Dima Rasnovsky, General Manager for Africa at Glovo, one of the world's leading quick commerce and on demand delivery platforms transforming how consumers access food, groceries, retail products, and everyday essentials across cities. Dima leads Glovo's growth and operations across African markets, helping drive the expansion of digital commerce, last mile delivery, and retail technology across some of the continent's fastest growing economies.In this episode, we explore the future of ecommerce in Africa and how quick commerce is reshaping consumer behaviour across major urban centres including Lagos, Nairobi, Kampala, and Abidjan. Dima explains how rising smartphone adoption, mobile money, digital payments, and rapid urbanisation are accelerating the growth of on demand delivery and creating new opportunities for African retailers, restaurants, supermarkets, and small businesses.From ultra fast grocery delivery and digital retail infrastructure to logistics networks and last mile delivery systems, Dima shares how Glovo is building the technology and operational systems required to support the next generation of commerce in Africa. He discusses the rise of convenience driven consumer behaviour, why African consumers increasingly expect same day or instant delivery, and how local businesses are using digital platforms to expand their reach and compete in a changing retail environment.What We Discuss With DimaThe future of ecommerce and quick commerce across Africa.How Glovo is transforming food delivery, grocery delivery, and digital retail in African cities.Building last mile logistics and delivery infrastructure in Lagos, Nairobi, Kampala, and Abidjan.Helping neighbourhood stores, restaurants, and SMEs participate in the digital economy.Why mobile money, fintech, and digital payments are critical to Africa's commerce ecosystem.Whether Africa could leapfrog traditional retail systems and shape the future of global commerce.Did you miss my previous episode where I discus The Nigerian Entrepreneur Building Africa's Sports Economy Through Boxing, Events and Entertainment? Make sure to check it out!Connect with Terser:LinkedIn - Terser AdamuInstagram - unlockingafricaTwitter (X) - @TerserAdamuConnect with DimaLinkedIn - Dima Rasnovsky and GlovoMany of the businesses unlocking opportunities in Africa don't do it alone. If you'd like strategic support on entering or expanding across African markets, reach out to our partners ETK Group:www.etkgroup.co.ukinfo@etkgroup.co.uk

Reliability is Still Important Abstract Kirk and Fred discuss how to keep reliability a priority when dealing with changing suppliers. Key Points Join Kirk and Fred as they discuss shifting suppliers and how to ensure reliability when components or manufacturing locations change. Topics include: If a product was developed using HALT methods, then it should […]

SUMMARY: We  explore one of the most overlooked bottlenecks in the AI boom: energy and infrastructure and  why power availability is becoming the limiting factor.GUEST: Wannie Park, Founder/CEO of PADO AISHOW: 1026SHOW TRANSCRIPT: The Reasoning Show #1026 TranscriptSHOW VIDEO: https://youtu.be/satMQRxKQC8SHOW SPONSORS:ShareGate - ShareGate Protect. Microsoft 365 Governance, we got this!Nasuni - Activate your data for AI and request a demoSHOW NOTES:1. AI's Hidden Constraint: PowerAI growth is no longer limited only by GPUs and computePower generation, cooling, and grid interconnects are emerging as major bottlenecksData centers could account for 10–12% of North American power demand in coming years2. Why Data Centers Are Being ReimaginedTraditional data centers were built for enterprise IT, not AI-scale workloadsAI infrastructure introduces:Massive power density needsAdvanced cooling challenges3. The Grid Wasn't Built for AIUtilities are designed around peak demand scenariosMost grids run well below peak capacity most of the timeAI workloads create volatile and unpredictable consumption patternsLong interconnection timelines are pushing companies toward alternative infrastructure models4. GPU Utilization Is Surprisingly LowGPU clusters are often underutilized because of:Scheduling inefficiencies, Cooling limitations, SLA constraintsEffective GPU utilization may be as low as 12–13% in some environments5. Cooling as a Major Optimization LayerLegacy data centers often cool entire zones inefficientlyPado AI alignsAI workloads, Cooling systems, Power allocationWorkload-aware orchestration helps optimize cooling and compute efficiency6. The Rise of “Compute Forecasting”Pado forecasts compute demand instead of energy demandThe platform models:GPU workloads, Power consumption, Cooling requirements, SLA prioritiesGoal: maximize “compute per megawatt”7. AI Workloads Become Time-AwareAI providers may increasingly:Shift workloads to off-peak periodsIncentivize delayed non-urgent jobsDynamically balance compute demandUsers are already seeing variable inference latency in real-world AI systems8. Sustainability vs Reliability vs ProfitabilityOperators must balance:Uptime expectations, Infrastructure costs, Sustainability goalsRenewable adoption is growing, but reliability still drives investment in natural gas and battery-backed systems9. Brownfield vs Greenfield OpportunitiesPado AI is focused primarily on existing (“brownfield”) data centersExisting enterprise infrastructure can often be extended and optimized instead of rebuiltEnterprises may gain significant AI capability without hyperscale GPU deploymentsFEEDBACK?Email: show @ reasoning dot showBluesky: @reasoningshow.bsky.socialTwitter/X: @ReasoningShowInstagram: @reasoningshowTikTok: @reasoningshow

Today, we're going to explore a topic that doesn't always get the attention it deserves, but has a direct impact on product quality and long-term reliability.I'm joined by Mehdi Nahali, founder of PCB Revision Control PRO. His platform is designed to replace spreadsheets, emails, and disconnected systems with a centralized approach to PCB revision lifecycle management and factory intelligence. We're going to talk about how revision control, data integrity, and process discipline impact reliability, and where manufacturers are still getting it wrong.PCB Revision Control Prohttps://www.pcbrevisionpro.com

Industrial Talk is onsite at Xcelerate 2026 and talking to Salim Jaffer, Strategic Account Manager at Mobius Institute about "Reliability success = Culture". Overview The conversation features Salim Jaffer, a strategic account manager at Mobius Institute, discussing his extensive experience in the industry, particularly in reliability and root cause analysis (RCA). He highlights his background with companies like Bentley Nevada, GE, Baker Hughes, and Emerson, and his current role in developing partnerships and training in the Gulf Coast region. Jaffer emphasizes the importance of RCA, the need for a cultural shift towards reliability, and the role of data in predictive maintenance. He also promotes Mobius Institute's professional training programs, which cover various aspects of asset management and reliability, including vibration analysis, lube oil analysis, and ultrasound training. Outline Fluke Xcelerate Event Overview Scott introduces the Industrial Talk podcast, sponsored by Fluke, highlighting the Xcelerate event.The event focused on reliability, predictive maintenance tools, and AI diagnostics.Scott emphasizes the importance of real-world strategies for teams to use today.Fluke is praised for their contributions to smarter, faster, and reliable operations. Introduction to the Podcast and Salim Jaffer Scott reiterates the podcast's mission to celebrate industry professionals and their contributions.The event, Xcelerate, is being held in Austin, Texas, and is sponsored by Fluke.Salim Jaffer is introduced as the guest, representing Mobius Institute and other organizations. Salim Jaffer's Background and Experience Salim Jaffer shares his extensive experience in the industry, including 30+ years with various companies.He details his time with Bentley Nevada, GE, Baker Hughes, and Emerson, focusing on reliability solutions.Salim is currently a strategic account manager for Mobius Institute, covering the Gulf Coast region.He discusses his role in developing partnerships and representing the Mobius Institute brand. Root Cause Analysis (RCA) and Human Nature Salim explains his three-hour session on root cause analysis (RCA) at the Xcelerate event.He emphasizes the importance of RCA and shares personal anecdotes about his instinctive problem-solving nature.The conversation touches on the challenges of human nature in plant operations and the need for a collective approach to reliability.Salim highlights the importance of training and cultural change to foster a shared responsibility for reliability. Challenges in Plant Operations and Reliability Culture Salim discusses the common issue of plant managers claiming everything is fine, despite obvious problems.He shares examples of hidden issues, such as broken sensors and improperly set-up equipment.The conversation explores the need for a culture where everyone understands and supports reliability efforts.Salim mentions the General Electric (GE) culture change training and its effectiveness in fostering a shared responsibility for reliability. The Role of Technology and Data in Reliability Salim and Scott discuss the evolving role of technology, particularly AI, in predictive maintenance.Salim shares his experience with AI and neural networks in the early 2000s, emphasizing the importance of data.The conversation highlights the need for clean data and the challenges of working with historical data.Salim promotes Mobius Institute's training programs, which include hands-on experience with data and tools. Mobius Institute's Training and Certification Programs Salim provides an overview of Mobius Institute's professional training programs.The training covers various aspects of reliability, including vibration analysis, lube oil analysis, and ultrasound.Salim emphasizes the importance of the Asset Reliability Professional (ARP) program, which is certified by ISO.The ARP program offers training at different levels, from entry to leadership, focusing on improving reliability through systematic methodologies. Conclusion and Contact Information Salim reiterates the importance of education and continuous improvement in the field of reliability.He encourages listeners to reach out to him via LinkedIn for further discussions.Scott Mackenzie wraps up the podcast, highlighting the importance of human connection and storytelling in the industrial field.The podcast concludes with a reminder to visit Mobius Institute's website for more information and to stay tuned for future episodes. If interested in being on the Industrial Talk show, simply contact us and let's have a quick conversation. Finally, get your exclusive free access to the Industrial Academy and a series on “Why You Need To Podcast” for Greater Success in 2026. All links designed for keeping you current in this rapidly changing Industrial Market. Learn! Grow! Enjoy! SALIM JAFFER'S CONTACT INFORMATION: Personal LinkedIn: https://www.linkedin.com/in/salimjaffers/ Company LinkedIn: https://www.linkedin.com/company/mobius-institute-north-america/ Company Website:  https://www.mobiusinstitute.com/mina/ PODCAST VIDEO: https://youtu.be/ST8wcA3UBkk THE STRATEGIC REASON "WHY YOU NEED TO PODCAST": OTHER GREAT INDUSTRIAL RESOURCES: NEOM: https://www.neom.com/en-us Hexagon: https://hexagon.com/ Arduino: https://www.arduino.cc/ Fictiv: https://www.fictiv.com/ Hitachi Vantara: https://www.hitachivantara.com/en-us/home.html Industrial Marketing Solutions:  https://industrialtalk.com/industrial-marketing/ Industrial Academy: https://industrialtalk.com/industrial-academy/ Industrial Dojo: https://industrialtalk.com/industrial_dojo/ We the 15: https://www.wethe15.org/ YOUR INDUSTRIAL DIGITAL TOOLBOX: LifterLMS: Get One Month Free for $1 – https://lifterlms.com/ Active Campaign: Active Campaign Link Social Jukebox: https://www.socialjukebox.com/ Industrial Academy (One Month Free Access And One Free License For Future Industrial Leader): Business Beatitude the Book Do you desire a more joy-filled, deeply-enduring sense of accomplishment and success? Live your business the way you want to live with the BUSINESS BEATITUDES...The Bridge connecting sacrifice to success. YOU NEED THE BUSINESS BEATITUDES! TAP INTO YOUR INDUSTRIAL SOUL, RESERVE YOUR COPY NOW! BE BOLD. BE BRAVE. DARE GREATLY AND CHANGE THE WORLD. GET THE BUSINESS BEATITUDES! Reserve My Copy and My 25% Discount

Consumer Reports experts answer audience questions about CVTs and electric vehicles, including why simulated shifting exists, why the experts at Consumer Reports enjoy it, and how it affects performance and efficiency. We also explore the gap between reliability and owner satisfaction, with examples like the Rivian R1T and Rivian R1S, and what that means for car buyers, as well as current owners. We also discuss alternatives to traditional car rental companies, including peer-to-peer services like Turo and Sixt, and if you can avoid getting a bad car from the vague categories rental places use. Plus, we share advice on shopping for the best used EV under $40,000, with models like the Ford F-150 Lightning, Ford Mustang Mach-E, Audi Q6 and A6 e-tron, Honda Prologue, and more.   SHOW NOTES: 00:00 - Intro 00:55 - Chad (Wichita, KS): Simulated Upshifts in Hybrids 05:34 - Joe: Rivian Reliability vs Owner Satisfaction 10:04 - Robert: Best Used EV Options (Audi vs Honda + Alternatives) 14:51 - Gordon (Atlanta, GA): Why Are Turn Signals Moving Lower? 18:20 - Daniel (Video Question): Is the Chevy Equinox EV Being Discontinued? 20:54 - Andrew (Video Question): Rental Car Hacks (Turo, Sixt, Categories) 26:44 - Outro & How to Submit Questions LINKS: Subaru Forester Hybrid Test Results: https://www.consumerreports.org/cars/subaru/forester-hybrid/2026/overview/?EXTKEY=YSOCIAL_YT 2026 Owner Satisfaction Survey Results: https://www.consumerreports.org/cars/car-reliability-owner-satisfaction/most-and-least-liked-car-brands-a1291429338/?EXTKEY=YSOCIAL_YT Best Used EVs: https://www.consumerreports.org/cars/hybrids-evs/buying-a-used-electric-vehicle-what-to-know-a7139266510/?EXTKEY=YSOCIAL_YT Chevrolet Equinox EV Test Results: https://www.consumerreports.org/cars/chevrolet/equinox-ev/2026/overview/?EXTKEY=YSOCIAL_YT Best and Worst Rental Car Companies: https://www.consumerreports.org/money/car-travel/best-and-worst-car-rental-companies-a1417885044/?EXTKEY=YSOCIAL_YT  

Consumer Reports experts answer audience questions about CVTs and electric vehicles, including why simulated shifting exists, why the experts at Consumer Reports enjoy it, and how it affects performance and efficiency. We also explore the gap between reliability and owner satisfaction, with examples like the Rivian R1T and Rivian R1S, and what that means for car buyers, as well as current owners. We also discuss alternatives to traditional car rental companies, including peer-to-peer services like Turo and Sixt, and if you can avoid getting a bad car from the vague categories rental places use. Plus, we share advice on shopping for the best used EV under $40,000, with models like the Ford F-150 Lightning, Ford Mustang Mach-E, Audi Q6 and A6 e-tron, Honda Prologue, and more.   SHOW NOTES: 00:00 - Intro 00:55 - Chad (Wichita, KS): Simulated Upshifts in Hybrids 05:34 - Joe: Rivian Reliability vs Owner Satisfaction 10:04 - Robert: Best Used EV Options (Audi vs Honda + Alternatives) 14:51 - Gordon (Atlanta, GA): Why Are Turn Signals Moving Lower? 18:20 - Daniel (Video Question): Is the Chevy Equinox EV Being Discontinued? 20:54 - Andrew (Video Question): Rental Car Hacks (Turo, Sixt, Categories) 26:44 - Outro & How to Submit Questions   LINKS: Subaru Forester Hybrid Test Results: https://www.consumerreports.org/cars/subaru/forester-hybrid/2026/overview/?EXTKEY=YSOCIAL_YT 2026 Owner Satisfaction Survey Results: https://www.consumerreports.org/cars/car-reliability-owner-satisfaction/most-and-least-liked-car-brands-a1291429338/?EXTKEY=YSOCIAL_YT Best Used EVs: https://www.consumerreports.org/cars/hybrids-evs/buying-a-used-electric-vehicle-what-to-know-a7139266510/?EXTKEY=YSOCIAL_YT Chevrolet Equinox EV Test Results: https://www.consumerreports.org/cars/chevrolet/equinox-ev/2026/overview/?EXTKEY=YSOCIAL_YT Best and Worst Rental Car Companies: https://www.consumerreports.org/money/car-travel/best-and-worst-car-rental-companies-a1417885044/?EXTKEY=YSOCIAL_YT

In this episode, Madelyn O'Farrell chats with Jay Allardyce, Chief Product Officer at Octave (part of Hexagon), about how integrated data, design, and operations can transform industrial supply chains. Jay traces his path through HP, GE, Uptake, Google Cloud, and private equity–backed software to Octave, where he oversees tools that span the lifecycle of major infrastructure from design and build to operate and protect, including public safety and 911 systems. Using Octave's partnership with the Visa Cash App Racing Bulls Formula 1 team, he explains F1 as a “traveling city” and a live example of an integrated, feedback-rich supply chain and digital thread, in contrast to the value lost at each handoff in most industries. He argues that reliability and cost efficiency start at design and depend on context-rich digital twins and continuous feedback loops, not just more data. Jay also highlights the importance of thoughtful AI adoption, praising safety-focused approaches like Anthropic's and stressing that future, software-defined supply chains will be anticipatory networks enabled as much by better human questions and mindset shifts as by new technology. Don't miss this great conversation. Highlights from their conversation include: Jay's Career Journey Across HP, GE, Uptake, and Google (0:49) What Octave Is: Design, Build, Operate, Protect Software Portfolio (3:23) Octave's Partnership With Formula 1 and Visa Cash App Racing Bulls (5:45) Treating F1 as a “Traveling City” and Supply Chain Showcase (6:20) Digital Thread, Digital Twins, and Supply Chain Feedback Loops (8:40) Cost of Broken Digital Threads and 1x–10x Value Loss at Handoffs (9:55) Reliability as System Context, Not Just Single-Part Failure (11:46) Step Back From the Data: First Principles and 360-Degree Asset View (13:30) How To Ground AI Initiatives Before Spinning Up Infrastructure (16:30) Society's Need to Retrain How We Ask Questions of AI (18:50) Future Vision: Anticipatory, Software-Defined, Networked Supply Chains (20:08) Dynamo Ventures is a venture firm backing founders upgrading the physical economy. As intelligence moves into critical infrastructure and technology collides with physics, industry is entering a new era of transformation - the industrial renaissance. Born from the dirt and grit of supply chains and shaped by operations, not spreadsheets, Dynamo focuses on the complex realities of building in the real world. We invest in companies transforming infrastructure, manufacturing, logistics, transportation, and the systems that power global commerce. Dynamo works closely with founders who combine ambition with a bias to action, bringing a builder mindset to venture capital through deep operational insight, systematic pressure-testing and hands-on partnership. Our purpose is simple: to back the relentless shaping the industrial renaissance. Learn more at www.dynamo.vc Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Car manufacturer stereotypes exist for a reason - many people would say Japanese cars are more reliable than European cars, but that's not always the case. What does reliability mean to you? The guys debate for Maya and her fiancé who are into outdoor activities but may have kids in the future. Then, Briar in Virginia Beach has been listening and following the show since he was 13! Now married, he loves RWD cars and asks the guys what he and his wife should buy next. Also, have you seen Red Bull athlete Dario Costa's latest piloting adventure? Audio-only MP3 is available on Spotify, Apple Podcasts and 10 other platforms. Look for us on Tuesdays if you'd like to watch us debate, disagree and then go drive again! 0:00 - Intro 0:18 - Stellantis Is “Re-Focusing.” How About A Jeep Or RAM Minivan? 12:13 - Topic Tuesday: What Does ‘Reliable' Mean To You? 38:18 - Car Debate #1: All The Outdoor Activities, Plus Kids In The Future 55:33 - Car Debate #2: Listening Since Age 13 1:10:30 - Did You See This? Speed, Trains, Airplanes and Cars 1:16:59 - Audience Questions On Social Media Rate and review us on Apple Podcasts, and subscribe to our two YouTube channels. Write to us your Topic Tuesdays, Car Conclusions and those great Car Debates at everydaydrivertv@gmail.com or everydaydriver.com Learn more about your ad choices. Visit megaphone.fm/adchoices

We Like Shooting - Ep 660 This episode of We Like Shooting is brought to you by: Midwest Industries (Code: WLSISLIFE) Die Free Co. (Code: WLSISLIFE) Bowers Group (Code: WLS) Otis Technology (Code: WELIKESHOOTING15) Flatline Fiber Co (Code: WLS15) Text Dear WLS or Reviews +1 743 500 2171  Public   Show Titles   GOA GOALS Aug 1-2 in Iowa. https://goals.goa.org/ GunCon.net Tickets on sale now. Use code AGENCY171 Gear Chat [Ruger] RXM The Ruger RXM is a striker-fired pistol designed with a grip angle similar to the 1911 for natural point of aim, featuring a polymer frame developed in collaboration with Magpul. It incorporates a modular FCI (fire control insert) system allowing frame swaps without a new background check and is compatible with Gen 3 Glock parts, holsters, sights, and lights. Reliability testing showed 800 rounds fired without failures, with suppressor-height tritium night sights and direct optic mounting for RMR, DPP, or RMSC footprints. Cost: MSRP $539 / Street ~$438 Special: FCI (fire control insert) system for modularity enabling frame swaps Note Ruger RXM Review [Hi-Point] Hush-Point 30 The Hush-Point 30 is a lightweight, modern suppressor designed for .30-caliber centerfire rifles like the AR-15, available in titanium and Inconel models. It features advanced flow-through technology that directs gas away from the shooter to reduce over-gassing in direct-impingement systems. The suppressor is HUB compatible and includes 1/2×28 and 5/8×24 threads for .223 and 300 Blackout calibers.0 Availability: Shipping now. Available at Guns.com (titanium: https://www.guns.com/silencers/p/hi-point-hush-point-30-ti?i=654780, Inconel: https://www.guns.com/silencers/p/hi-point-hush-point-30-inconel?i=654767).0 Cost: MSRP: Inconel $822.88, titanium $846.81.0 Special: Advanced flow-through technology that vents gas forward to reduce over-gassing, especially for direct-impingement systems; HUB compatible; includes 1/2×28 and 5/8×24 threads.0 [Inland Manufacturing] Model 1910 The Inland Manufacturing Model 1910 is a suppressor for the M1 Carbine platform, replicating the original Maxim Silencer design with modern internals. It features a monoblock monocore construction that allows easy servicing without removal from the barrel, even for cleaning, and includes an offset bore. Compatible with .30 caliber and .357/9mm calibers, it provides a throwback to early 20th-century suppressor technology patented by Hiram Percy Maxim. Availability: Shown at NRAAM 2026; available at Guns.com (https://www.guns.com/silencers?product.manufacturer=INLAND%20MANUFACTURING) Special: Monoblock monocore design with offset bore; can be cleaned without removing from barrel Note (Nick) Bus Built Projects [RevoMag] RevoMag (Nick) The RevoMag is a revolver reloading device designed to be faster than a speedstrip and more concealable than a traditional speedloader. It features a polymer magazine-style body with a reversible pocket clip, compatible with calibers such as .38 Special, .357 Magnum, and .327 Magnum. Proudly made in the USA for everyday carry and personal protection. Special: Magazine-style reload with squeeze-to-release mechanism and reversible pocket clip68 Bullet Points Gun Fights No one stepped into the arena this week. The Agency Brief Agency Update “The government looked at a piece of plastic on the back of a rifle, panicked, and spent ten years proving that gun control is a complete myth.” THE INTEL (THE STORY) The Play-by-Play: 1989 Catalyst: The Stockton school shooting gives gun control groups their emotional leverage. The media pivots away from the shooter's massive rap sheet to demonize the “evil” semi-auto rifle. What the Media Lied About: They flat-out lied that military machine guns were flooding the streets. Anti-gun activist Josh Sugarmann explicitly published this strategy: exploit the public's confusion between semi-autos and fully automatic weapons to manufacture outrage. The Architects: Bill Clinton needed a “tough on crime” headline. Sen. Dianne Feinstein drafted the ban, later admitting her true goal on 60 Minutes: “If I could have gotten 51 votes… for an outright ban… Mr. and Mrs. America, turn them all in; I would have done it.” What It Actually Did: Banned 19 specific firearms and semi-autos equipped with two or more “scary” cosmetic features (bayonet lugs, flash suppressors, folding stocks, pistol grips). It also capped new magazines at 10 rounds. The Backroom Deals: Democrats didn't have the votes for a permanent ban. They negotiated a 10-year sunset clause and grandfathered in millions of existing firearms, gambling they could just expand it later. The Workaround: The industry adapted overnight. Manufacturers removed the banned cosmetic plastic and sold functionally identical rifles. Congress literally regulated aesthetics. 2004 Sunset: The ban expires. An official, DOJ-funded study by Christopher Koper concludes the ban did absolutely nothing to reduce gun violence. The Reality Check (Hidden Incentives): Conditioning the Public: This was a psychological op to condition Americans to accept the government banning entire categories of firearms based purely on Hollywood aesthetics. Incrementalism: Lawmakers knew a total gun ban wouldn't fly, so they established the “feature test” as a foothold for future, broader bans. The True Target: The feature ban was mostly temporary political theater; starving the civilian market of standard-capacity magazines was their real long-term objective. Market Impact: They hoped shifting regulations would bankrupt the tactical firearms market with compliance red tape. Instead, they inadvertently birthed the massive modern AR-15 industry. THE 2A ANGLE (LEGAL & IMPACT) The Threat: The '94 ban is the exact blueprint tyrannical blue states (CA, NY, IL, WA) use today to terrorize FFLs and castrate standard rifles. They took a proven federal failure and turned it into permanent state-level law. For modern FFLs, this means SKU-by-SKU compliance nightmares, massive inventory risks, and the constant threat of a new federal ban—which, next time, likely won't include a grandfathering clause. Bruen Test: Text: The Second Amendment protects “arms.” Semi-auto centerfire rifles and standard capacity magazines are plainly protected arms. History & Tradition: There is zero founding-era analogue for restricting arms based on ergonomic grips or muzzle devices. The Founders didn't ban repeating arms when they emerged. Heller / McDonald Check: Arms “in common use for lawful purposes” are fundamentally protected. With over 24 million AR-15s in civilian hands right now, they undeniably satisfy the common use standard. Banning them violates the core of Heller. Bruen kills the feature-test dead; rogue appellate courts are simply playing games to delay the inevitable. Regulatory Creep: The Expanding Ratchet: The feature test is a backdoor trap. It started with bayonet lugs and flash hiders, then moved to pistol braces, threaded barrels, and parts kits. Fluid Definitions: Current AWB proposals name over 200 firearms and reduce the threshold to just one aesthetic feature. The Handgun Endgame: Once society accepts that a semi-auto action plus a detachable mag equals a “weapon of war,” your daily-carry Glock 19 or P365 is logically next. Agency Update 94-04 AWB coming next? WLS is Lifestyle Note Secret Service LPVO Drip Imgur Image yYOLY0f The provided URL points to an Imgur page at https://imgur.com/yYOLY0f. Page content indicates JavaScript is disabled, preventing access to the image or any details. No firearms, cultural elements, or product information is accessible or stated. The Alley Not Stated The webpage is a news article about an Oakland County man charged in a deadly shooting of a teen burglar. It mentions a generic ‘9mm' firearm used by the man in self-defense context, with no manufacturer or model name specified. No technical gear details matching the required format are explicitly provided. Going Ballistic ATF NFA Division: Over 1 Million Forms Processed in 2026, 6 Million Suppressors Registered (Savage) The ATF's National Firearms Act (NFA) Division processed over 1 million NFA forms in the first four months of 2026, surpassing previous annual totals due to the elimination of the $200 tax stamp for suppressors and short-barreled firearms effective January 1, 2026. Over half of these were Form 4 applications for suppressor transfers, with nearly 6 million suppressors now registered in the National Firearms Registration and Transfer Record (NFRTR) as of April 2026. This marks a historic surge, with 2026 registrations rivaling decades of prior accumulation. The Gist: National (United States): ATF NFA Division and National Firearms Registration and Transfer Record (NFRTR); applies nationwide to NFA items like suppressors and short-barreled firearms. Impact: Elimination of $200 tax stamp for suppressors and short-barreled firearms effective January 1, 2026, caused surge in processing (over 1 million forms in first 4 months of 2026 vs. 1.37 million in all of 2024); over 5.99 million suppressors registered as of April 10, 2026. Bottom Line: Historic surge in NFA adoption post-tax elimination, with 2026 early-year forms exceeding prior annual records and suppressor registrations rivaling 76 years (1934-2010) of prior totals. Post-Bruen Gun Rights Cases: Wolford v. Lopez, United States v. Mitchell, United States v. Hemani, Viramontes v. Cook County, and Roberts v. ATF (Savage) The article details several post-Bruen Supreme Court and lower court cases challenging restrictions on public carry, prohibited-person statutes under 18 U.S.C. § 922(g), AR-15 bans, and NFA registration requirements....