Podcasts about RFC

PHP Podcast – June 11, 2026 Guest Hosts: Sara Golemon, Elizabeth Barron & Holly Schilling Eric and John are out this week — Sara, Elizabeth, and Holly take over. Here’s what they covered: PHPVerse Recap PHPVerse just wrapped up, and Elizabeth was there in Amsterdam. The format is unusual — all speakers are flown to one location, but the audience is entirely virtual. It was a class act: professional TV crew, studio lighting, and a makeup and hair team on site. Around 2,500–3,000 people watched the live stream. Everything was broadcast as one long block; individual talk segments and possibly the documentary trailer will be cut and released separately. The full stream is available now — the PHP documentary trailer (produced by Jet Breeze, covering 30+ years of PHP history) appears around the 2:24:30 mark. PHP Foundation 2026 Strategy Document Elizabeth and the PHP Foundation released their 2026 strategy document the same day as this recording. The foundation gathered community input across numerous conversations and conferences, synthesized it into findings, and has now published a plan for the rest of the year. Key themes: repositioning PHP’s public perception (which Elizabeth calls a solvable problem), creating six special interest groups, and launching an Onboarding Initiative to build a real on-ramp for new PHP developers. Elizabeth’s view is that the two things giving her the most hope for PHP’s future are the passion and expertise of the community, and how good the language itself has gotten. Visit thephp.foundation to read the full document. The Onboarding Initiative One of the six special interest groups the foundation is launching is specifically focused on bringing new developers into PHP. Goals include creating a true learning path (not just a reference manual that assumes existing knowledge), improving educational resources, and potentially working with the php.net website to improve the first-time experience. Holly made the point that PHP’s barrier to entry is genuinely lower than almost any other language — the Hello World program is 11 characters — but that story isn’t being told outside the PHP bubble. New developers are turning to JavaScript as a first language and running into minified spaghetti instead of something approachable. AI Writing PHP — And PHP as a Second Language Holly built the entire PHP Tek conference app backend in Laravel without writing a single line of code herself — AI-generated throughout, which she reviewed and approved. The code held up to peer review at the conference with only minor style nits. She ran it on PHP 8.3 and used modern standards throughout (one piece of feedback: stop using empty()). The consensus: AI models write good modern PHP because of the vast amount of open source PHP they were trained on. The caveat Sara raised is worth thinking about — how much of that training data is PHP 4-era code and WordPress 3 repositories? Either way, Holly’s case for PHP as a second language is strong: low ceremony, low boilerplate, readable syntax, and it’s a language where you can do something useful in minutes. PHP’s Reputation Problem (and Why It’s Fixable) The group dug into PHP’s perception gap — the mismatch between how good the language actually is and how it’s perceived outside the community. Holly’s experience as a mobile developer who recommends PHP to others: the pushback is immediate (“isn’t that slow?”, “isn’t that dead?”). The benchmarks don’t support that reputation — PHP outperforms Python on most comparable workloads — but data alone doesn’t shift perception. Elizabeth’s point is that this is primarily a storytelling and coordination problem, not a language problem, and that the foundation’s repositioning work is exactly aimed at closing that gap. The community has the passion. It just needs to tell the story outside its own bubble. PHP Polling API RFC Sara walked through the RFC for a new Polling API in PHP (wiki.php.net/rfc/poll_API). The short version: PHP currently has five or six different ways to do I/O multiplexing (watching multiple streams and acting on whichever one is ready first), and which one works depends on the OS, available extensions, and PHP version. The Polling API proposal creates a single, unified interface that abstracts all of that. The immediate beneficiaries are async frameworks like Amp PHP, ReactPHP, and Revolt, which currently have to maintain multiple backend implementations to cover different environments. The bigger picture: this is a building block on the path toward true async PHP, likely contributing to something more complete in PHP 9.0. Most app developers won’t use it directly — but the libraries they depend on will. RFCs are all listed at wiki.php.net/rfc. PHP.net: Do As We Say, Not As We Do Sara, who has contributed to php.net, copped to the state of the codebase: some of it dates to the PHP 3 era, there are functions.inc files, and it is very much “do as we say, not as we do.” The historical reason is that php.net used to rely on community-administered mirrors (r-synced servers running everything from PHP 5.1 to 5.6 simultaneously), so modernizing the code was impossible without controlling the runtime. That’s changed with CDN-based load balancing — they can now control what PHP version runs on php.net — and the code has been getting better. But it’s a slow process. PHP Podcasts Past, Present, and Future Holly asked about the PHP Town Hall podcast (Ben Edmonds and Phil Sturgeon), and the group did a quick tour of PHP podcast history. The PHP Roundtable — originally started by Sammy, taken over by Eric — has produced about three episodes. Sara and producer Joe are planning to take it off Eric’s hands and actually do it properly. And Elizabeth announced that the PHP Foundation is launching a new podcast: tentatively called PHP at Scale, hosted by Ben Marx, focused on telling the stories of organizations pushing PHP to its limits. No launch date yet, but there’s already a queue of interested guests. Next Week’s Show — Moved to Wednesday Sara will be on a boat off the coast of Galicia on Thursday, so next week’s episode is moving to Wednesday. Guests will include Paul Reinheimer and (hopefully) Sean Coase — two veterans from PHP’s podcasting past. Elizabeth is going to try to make it work around the Canadian Grand Prix. Mac Mini M4 for Local LLMs Holly picked up a refurbished Mac Mini M4 (16GB RAM, 512GB storage) specifically to run LLM models locally via Ollama. Apple Silicon is a solid choice for this because the unified memory architecture gives the neural cores access to far more RAM than a discrete GPU setup. Sara is waiting for the M5, which is reportedly not coming until fall — and is already resigned to spending too much on it when it lands. Links from the show: PHP Foundation — 2026 Strategy Document PHP RFC: Polling API PHP RFC Wiki — All RFCs Under Discussion Amp PHP — Async framework ReactPHP — Event-driven async PHP Revolt — Event loop for PHP php.net website source code (github.com/php/web-php) PHP Architect Discord Guest Hosts: Sara Golemon Based in Lisbon, Portugal PHP core contributor; code contributor via the Curl project (which means she technically has code on Mars) Elizabeth Barron Executive Director, PHP Foundation Based in Germany Holly Schilling Primary mobile developer; built the PHP Tek 2026 conference app Based near Chicago, IL Streams: Youtube Channel Twitch Connect & Hire PHP Architect Website Twitter/X Mastodon Hire PHP Developers Looking to hire PHP developers? Email support@phparch.com – Joe and the team are available for consulting, infrastructure work, Ansible playbooks, and code review. Partner This podcast is made a little better thanks to our partners Displace Infrastructure Management, Simplified Automate Kubernetes deployments across any cloud provider or bare metal with a single command. Deploy, manage, and scale your infrastructure with ease. https://displace.tech/ PHPScore Put Your Technical Debt on Autopay with PHPScore Music Provided by Epidemic Sound https://www.epidemicsound.com/ Join Us Live Next Week Note: Next week’s show is on Wednesday (not Thursday) with guests Paul Reinheimer and Sean Coase. Youtube Channel Got feedback? Join us on Discord at discord.phparch.com The post The PHP Podcast 2026.06.11 appeared first on PHP Architect.

BONUS: The Communication Tax — Why Your Team Collaborates Too Much and What to Cut First In this BONUS episode, Roman Nikolaev challenges one of the most deeply held beliefs in the agile world: that more collaboration is always better. As Head of Technology at Cambri, Roman has watched teams burn their best hours in meetings and handoffs that create the feeling of productivity without the outcomes. He shares practical tools — from the vacation test to RFC processes — that help teams find the minimum viable level of collaboration. From Senior Engineer to Accidental Manager "I kind of accidentally ended up in management. I didn't want to lead anyone, I wanted to be just a senior engineer doing my stuff. But somehow, four months in the job, I was already leading a team, and then one year after, I was head of technology."   Roman's career in engineering goes back to the early 2000s. When he changed jobs during COVID, he specifically didn't want a management role — he wanted to code. But within months he was leading a team, and within a year he was running the entire technical organization at Cambri. That unexpected shift from hands-on engineering to leading teams gave him a front-row seat to how collaboration actually works — and how often it doesn't. What he noticed was that the most important differentiator for technical teams isn't technical knowledge — it's communication, and the tax you pay when communication goes wrong. The Communication Tax Is Real "The communication tax is real. The less we need to pay for communication, the more we can concentrate and own things end to end."   Roman describes a pattern most teams will recognize: stakeholders inside and outside the team — product managers, QA, scrum masters, product owners — and at some point, it becomes a game of telephone. The people doing the actual work don't have the context they need. The result? Unnecessary features, wrong implementations, suboptimal technical solutions that don't scale. His argument isn't that collaboration is bad. It's that every handoff, every meeting, every "quick sync" has a cost — and most teams aren't honest about how much they're paying. Handoffs Aren't Collaboration "If you look at a typical software development lifecycle — a ticket created by a product owner, refinement with the team, development, code review, QA, acceptance — there are quite many handoffs. If we can reduce some of this, we get a more effective workflow."   Roman walks through the standard ticket lifecycle and counts the handoffs: PO creates ticket, team refines, developer picks it up, code review with other developers, QA phase, acceptance phase. Each transition is a potential information loss. His provocation: instead of involving more people when someone struggles with a task, give the person working on it the tools and knowledge to complete it independently. The trigger for his thinking was a real team conversation where someone suggested everyone should "jump on the ticket" to help. Roman's response: wouldn't it be better to equip the individual rather than create more dependencies? Async Tools That Actually Work "Instead of gathering a meeting where people come unprepared or with some raw ideas, we have ownership for a task. Someone takes their time, writes down their thoughts, options in a document, and then we assign people to review it."   Roman shares two async practices his teams use at Cambri. First, the RFC (Request for Comments) process on Confluence — one person owns a decision, writes it up with options, and assigned reviewers sign off asynchronously. It turns out to be more effective at finding better technical solutions while spreading knowledge without requiring synchronous deep-dives. Second, his Monday written updates: every week, he spends about 90 minutes writing a detailed post covering all project statuses, what happened last week, what's coming, and business context. The team feedback in skip-level meetings is consistently positive, and he fields far fewer questions about business context and priorities than before the practice started. The Vacation Test "One heuristic would be that if one of the team members goes on vacation, the rest of the team can continue working on their task."   Roman learned this the hard way. He went on a typical Finnish one-month vacation. Before leaving, he explained the architecture and intent for a key task to his team. He came back to discover they'd built the completely wrong thing — wasting one month of a two-month project. He spent the remaining time working weekends, on planes, on trains, just to hit the deadline. The lesson wasn't that he needed more collaboration or synchronous communication before leaving. It was that he needed better communication — and a way to test whether shared context actually exists. His heuristic: if Alice goes on vacation, can Bob continue from where she stopped? If not, you don't need more meetings. You need better async context-sharing. Where to Start: Ownership First, Then Cut Meetings "I would probably first look into if a particular initiative, a feature, or some kind of process has an owner and well-defined roles. Usually, if there is no clear owner, that leads to a lot of synchronous meetings."   For Scrum Masters and team leads looking for a practical starting point, Roman offers a two-step approach. First, ensure every initiative, feature, and process has a clear owner with well-defined roles. Without clear ownership, meetings multiply because nobody is sure who's responsible, so everyone attends everything. Second, look at the team calendar starting with the biggest meetings and ask: can this be an RFC? A message? An email? Then experiment — cancel a meeting, replace it with an async channel, and see what happens. You can always bring it back. In the agile world, Roman argues, we should embrace experimentation with our own processes, not just our products. Recommended Resources Roman recommends Team Topologies by Matthew Skelton and Manuel Pais. The book gave him a clear mental model for independent teams that own their area end to end — teams aligned to value streams that own the customer problem completely. For more of Roman's thinking on collaboration, check out his Substack newsletter: Is Your Collaboration Good or Evil? on High Impact Engineering. About Roman Nikolaev Roman Nikolaev is Head of Technology at Cambri. He's spent his career thinking about how teams actually get work done — and his contrarian view that most teams collaborate too much has sparked real debate in the agile community.   You can link with Roman Nikolaev on LinkedIn.

The MacVoices Live! panel examines Spotify adopting Apple-backed video podcast technology, Instagram's disappearing posts and why anyone would want them, and  Microsoft expanding Copilot everywhere, whether it is a good idea or not. Chuck Joiner, David Ginsburg, Jeff Gamet, Guy Serle, Web Bixby, Eric Bolden, Marty Jencius, and Jim Rea also look at the risks of putting AI mini data centers in homes, and Plex's major lifetime Pass price hike. MacVoices is supported by NordLayer. Secure your network & stay compliant with one toggle-ready platform. Get an exclusive offer: up to 22% off NordLayer yearly plans plus 10% on top with the coupon code: MACVOICES10 at NordLayer.com/macvoices.  Try it risk-free—14-day money-back guarantee. Show Notes: Chapters: 00:00 Opening: exploit speed, bot limits, and bad tech features00:27 Spotify adopts Apple-backed video podcast technology01:18 Video podcast standards and Apple's role02:17 How video delivery scales across devices03:13 Apple's RFC and the origins of the standard04:26 Instagram's disappearing-post feature05:18 Why disappearing content remains popular05:55 Platform imitation and social media competition07:04 Microsoft retires Edge Copilot mode because Copilot is everywhere07:35 Copilot's expansion across enterprise tools08:13 AI mini data centers proposed for homes09:27 How home-hosted data centers might work10:17 Power, zoning, regulation, and community concerns13:08 Theft, internet traffic, and infrastructure problems16:40 NordLayer sponsor message18:02 Plex raises lifetime Plex Pass pricing18:31 Plex Pass pricing details and July 1 increase19:42 Why Plex may be pushing users toward subscriptions21:55 Panelists discuss their own Plex Pass usage22:12 What Plex Pass adds beyond free local streaming24:44 Plex's explanation for keeping lifetime passes25:31 Real-world Plex server setups and remote access27:13 Closing thoughts and warning about a fake CleanMyMac site28:02 Panelist contact information and wrap-up36:37 Chat room thanks and live show reminder37:10 Closing support, social, and sponsor information Links:   Spotify to Adopt Apple's Technology for Video Podcasts https://www.macrumors.com/2026/05/14/spotify-to-adopt-apples-tech-for-video-podcasts/   Instagram's New Snapchat Clone Makes It Too Easy to Send Disappearing Images to All Your Friends https://lifehacker.com/tech/instagram-snapchat-clone-that-lets-you-send-disappearing-messages   Microsoft is retiring Copilot Mode on Edge, because everything is Copilot Mode now – Engadget https://www.engadget.com/2172610/microsoft-copilot-edge-desktop-mobile/   The newest AI boom pitch: Host a mini data center at your homehttps://arstechnica.com/ai/2026/05/the-newest-ai-boom-pitch-host-a-mini-data-center-at-your-home/   Plex increasing Lifetime Plex Pass cost to whopping $750 https://9to5mac.com/2026/05/19/plex-increasing-lifetime-plex-pass-cost-to-whopping-750/ Guests: Web Bixby has been in the insurance business for 40 years and has been an Apple user for longer than that.You can catch up with him on Facebook, Twitter, and LinkedIn, but prefers Bluesky. Eric Bolden is into macOS, plants, sci-fi, food, and is a rural internet supporter. You can connect with him on Twitter, by email at embolden@mac.com, on Mastodon at @eabolden@techhub.social, on his blog, Trending At Work, and as co-host on The Vision ProFiles podcast. Jeff Gamet is a technology blogger, podcaster, author, and public speaker. Previously, he was The Mac Observer's Managing Editor, and the TextExpander Evangelist for Smile. He has presented at Macworld Expo, RSA Conference, several WordCamp events, along with many other conferences. You can find him on several podcasts such as The Mac Show, The Big Show, MacVoices, Mac OS Ken, This Week in iOS, and more. Jeff is easy to find on social media as @jgamet on Twitter and Instagram, jeffgamet on LinkedIn., @jgamet@mastodon.social on Mastodon, and on his YouTube Channel at YouTube.com/jgamet. David Ginsburg is the host of the weekly podcast In Touch With iOS where he discusses all things iOS, iPhone, iPad, Apple TV, Apple Watch, and related technologies. He is an IT professional supporting Mac, iOS and Windows users. Visit his YouTube channel at https://youtube.com/daveg65 and find and follow him on Twitter @daveg65 and on Mastodon at @daveg65@mastodon.cloud. Marty Jencius, Ph.D.,is a counselor educator and technology pioneer who has spent 30 years bringing emerging tech into his field — from founding one of the first professional listservs (CESNET-L) to podcasting, virtual reality, and now AI and AR. He is the founder of ThePodTalk.net, where he produces Vision ProFiles, The Old Mac Gang, A.I. Productivity Workflow, The Tech Savvy Professor, 15 Minute Bytes, The Neo Notebook, and Fade to Chat: Golden Age Cinema. He is also a regular panelist on MacVoices Live!, In Touch with iOS, and The Mac Show. Find him on Bluesky and Mastodon. Jim Rea built his own computer from scratch in 1975, started programming in 1977, and has been an independent Mac developer continuously since 1984. He is the founder of ProVUE Development, and the author of Panorama X, ProVUE's ultra fast RAM based database software for the macOS platform. He's been a speaker at MacTech, MacWorld Expo and other industry conferences. Follow Jim at provue.com and via @provuejim@techhub.social on Mastodon. Guy Serle, best known for being one of the co-hosts of the MyMac Podcast, sincerely apologizes for anything he has done or caused to have happened while in possession of dangerous podcasting equipment. He should know better but being a blonde from Florida means he's probably incapable of understanding the damage he has wrought. Guy is also the author of the novel, The Maltese Cube. You can follow his exploits on Twitter, catch him on Mac to the Future on Facebook, at @Macparrot@mastodon.social, and find everything at VertShark.com. Support:      Become a MacVoices Patron on Patreon     http://patreon.com/macvoices      Enjoy this episode? Make a one-time donation with PayPal Connect:      Web:     http://macvoices.com      Twitter:     http://www.twitter.com/chuckjoiner     http://www.twitter.com/macvoices      Mastodon:     https://mastodon.cloud/@chuckjoiner      Facebook:     http://www.facebook.com/chuck.joiner      MacVoices Page on Facebook:     http://www.facebook.com/macvoices/      MacVoices Group on Facebook:     http://www.facebook.com/groups/macvoice      LinkedIn:     https://www.linkedin.com/in/chuckjoiner/      Instagram:     https://www.instagram.com/chuckjoiner/ Subscribe:      Audio in iTunes     Video in iTunes      Subscribe manually via iTunes or any podcatcher:      Audio: http://www.macvoices.com/rss/macvoicesrss      Video: http://www.macvoices.com/rss/macvoicesvideorss

The MacVoices Live! panel examines Spotify adopting Apple-backed video podcast technology, Instagram's disappearing posts and why anyone would want them, and  Microsoft expanding Copilot everywhere, whether it is a good idea or not. Chuck Joiner, David Ginsburg, Jeff Gamet, Guy Serle, Web Bixby, Eric Bolden, Marty Jencius, and Jim Rea also look at the risks of putting AI mini data centers in homes, and Plex's major lifetime Pass price hike. MacVoices is supported by NordLayer. Secure your network & stay compliant with one toggle-ready platform. Get an exclusive offer: up to 22% off NordLayer yearly plans plus 10% on top with the coupon code: MACVOICES10 at NordLayer.com/macvoices.  Try it risk-free—14-day money-back guarantee. Show Notes: Chapters: 00:00 Opening: exploit speed, bot limits, and bad tech features 00:27 Spotify adopts Apple-backed video podcast technology 01:18 Video podcast standards and Apple's role 02:17 How video delivery scales across devices 03:13 Apple's RFC and the origins of the standard 04:26 Instagram's disappearing-post feature 05:18 Why disappearing content remains popular 05:55 Platform imitation and social media competition 07:04 Microsoft retires Edge Copilot mode because Copilot is everywhere 07:35 Copilot's expansion across enterprise tools 08:13 AI mini data centers proposed for homes 09:27 How home-hosted data centers might work 10:17 Power, zoning, regulation, and community concerns 13:08 Theft, internet traffic, and infrastructure problems 16:40 NordLayer sponsor message 18:02 Plex raises lifetime Plex Pass pricing 18:31 Plex Pass pricing details and July 1 increase 19:42 Why Plex may be pushing users toward subscriptions 21:55 Panelists discuss their own Plex Pass usage 22:12 What Plex Pass adds beyond free local streaming 24:44 Plex's explanation for keeping lifetime passes 25:31 Real-world Plex server setups and remote access 27:13 Closing thoughts and warning about a fake CleanMyMac site 28:02 Panelist contact information and wrap-up 36:37 Chat room thanks and live show reminder 37:10 Closing support, social, and sponsor information Links:   Spotify to Adopt Apple's Technology for Video Podcasts https://www.macrumors.com/2026/05/14/spotify-to-adopt-apples-tech-for-video-podcasts/   Instagram's New Snapchat Clone Makes It Too Easy to Send Disappearing Images to All Your Friends https://lifehacker.com/tech/instagram-snapchat-clone-that-lets-you-send-disappearing-messages   Microsoft is retiring Copilot Mode on Edge, because everything is Copilot Mode now – Engadget https://www.engadget.com/2172610/microsoft-copilot-edge-desktop-mobile/   The newest AI boom pitch: Host a mini data center at your homehttps://arstechnica.com/ai/2026/05/the-newest-ai-boom-pitch-host-a-mini-data-center-at-your-home/   Plex increasing Lifetime Plex Pass cost to whopping $750 https://9to5mac.com/2026/05/19/plex-increasing-lifetime-plex-pass-cost-to-whopping-750/ Guests: Web Bixby has been in the insurance business for 40 years and has been an Apple user for longer than that.You can catch up with him on Facebook, Twitter, and LinkedIn, but prefers Bluesky. Eric Bolden is into macOS, plants, sci-fi, food, and is a rural internet supporter. You can connect with him on Twitter, by email at embolden@mac.com, on Mastodon at @eabolden@techhub.social, on his blog, Trending At Work, and as co-host on The Vision ProFiles podcast. Jeff Gamet is a technology blogger, podcaster, author, and public speaker. Previously, he was The Mac Observer's Managing Editor, and the TextExpander Evangelist for Smile. He has presented at Macworld Expo, RSA Conference, several WordCamp events, along with many other conferences. You can find him on several podcasts such as The Mac Show, The Big Show, MacVoices, Mac OS Ken, This Week in iOS, and more. Jeff is easy to find on social media as @jgamet on Twitter and Instagram, jeffgamet on LinkedIn., @jgamet@mastodon.social on Mastodon, and on his YouTube Channel at YouTube.com/jgamet. David Ginsburg is the host of the weekly podcast In Touch With iOS where he discusses all things iOS, iPhone, iPad, Apple TV, Apple Watch, and related technologies. He is an IT professional supporting Mac, iOS and Windows users. Visit his YouTube channel at https://youtube.com/daveg65 and find and follow him on Twitter @daveg65 and on Mastodon at @daveg65@mastodon.cloud. Marty Jencius, Ph.D.,is a counselor educator and technology pioneer who has spent 30 years bringing emerging tech into his field — from founding one of the first professional listservs (CESNET-L) to podcasting, virtual reality, and now AI and AR. He is the founder of ThePodTalk.net, where he produces Vision ProFiles, The Old Mac Gang, A.I. Productivity Workflow, The Tech Savvy Professor, 15 Minute Bytes, The Neo Notebook, and Fade to Chat: Golden Age Cinema. He is also a regular panelist on MacVoices Live!, In Touch with iOS, and The Mac Show. Find him on Bluesky and Mastodon. Jim Rea built his own computer from scratch in 1975, started programming in 1977, and has been an independent Mac developer continuously since 1984. He is the founder of ProVUE Development, and the author of Panorama X, ProVUE's ultra fast RAM based database software for the macOS platform. He's been a speaker at MacTech, MacWorld Expo and other industry conferences. Follow Jim at provue.com and via @provuejim@techhub.social on Mastodon. Guy Serle, best known for being one of the co-hosts of the MyMac Podcast, sincerely apologizes for anything he has done or caused to have happened while in possession of dangerous podcasting equipment. He should know better but being a blonde from Florida means he's probably incapable of understanding the damage he has wrought. Guy is also the author of the novel, The Maltese Cube. You can follow his exploits on Twitter, catch him on Mac to the Future on Facebook, at @Macparrot@mastodon.social, and find everything at VertShark.com. Support:      Become a MacVoices Patron on Patreon      http://patreon.com/macvoices      Enjoy this episode? Make a one-time donation with PayPal Connect:      Web:      http://macvoices.com      Twitter:      http://www.twitter.com/chuckjoiner      http://www.twitter.com/macvoices      Mastodon:      https://mastodon.cloud/@chuckjoiner      Facebook:      http://www.facebook.com/chuck.joiner      MacVoices Page on Facebook:      http://www.facebook.com/macvoices/      MacVoices Group on Facebook:      http://www.facebook.com/groups/macvoice      LinkedIn:      https://www.linkedin.com/in/chuckjoiner/      Instagram:      https://www.instagram.com/chuckjoiner/ Subscribe:      Audio in iTunes      Video in iTunes      Subscribe manually via iTunes or any podcatcher:      Audio: http://www.macvoices.com/rss/macvoicesrss      Video: http://www.macvoices.com/rss/macvoicesvideorss

Brought to you by SEKO!On this week's pod: Shout outs:Good luck Scotland!Get well soon Christian EriksenRangers Ladies Lunch NARSA business:Destination NARSA - Nashville 2026 - THIS WEEKTENNENT's lager will be available!Individual nights tickets on sale now: narsa.ca/ticketsFriday night is a western themeDavie Cooper Memorial Topgolf Tournament now on sale - https://narsa.ca/tickets/RFC Executive Director, Fraser Thornton and RFC CEO, Jim Gillespie, and Greg Marshall are joining us at NARSA 2026!!!RFC 9-in-a-row legends: Derek Ferguson, Scott Nisbet, David Robertson, and Mark WaltersRFC Historian: David MasonEntertainment: MC David Edgar, Stuart Hay, Rebecca Auchterlonie, DJ Angry Bear, and Danny Magic!TICKETS NOW ON SALE: $199 USD | NARSA 2026 NashvilleCommunications:Fan Advisory Board - Open for nominationsInstagram and TikTok - follow us at narsacomms#NARSA #RangersFC #WeeklyUpdatehttps://narsa.ca/

ElevenLabs is licensing Hasbro's Transformers characters for commercial AI voice use — and the RFC crew is not entirely sold on it. Also this week: Siege Greenlight is back and up for pre-order, Missing Link Ratchet pre-orders open Friday, and Matt finally has his Haslab Liokaiser. Episode 990 is a full one. The post Radio Free Cybertron 990 – Siege Greenlight Is Back (And Cheaper) appeared first on Radio Free Cybertron.

ElevenLabs is licensing Hasbro's Transformers characters for commercial AI voice use — and the RFC crew is not entirely sold on it. Also this week: Siege Greenlight is back and up for pre-order, Missing Link Ratchet pre-orders open Friday, and Matt finally has his Haslab Liokaiser. Episode 990 is a full one. The post Radio Free Cybertron 990 – Siege Greenlight Is Back (And Cheaper) appeared first on Radio Free Cybertron.

Imagine going into business with a partner who tells you upfront: at the end of every year, I'll decide how much of the profits I keep. You'd never agree to that. But Ira Work says millions of Americans already did the day they opened a traditional IRA.That's one of several hard truths Ira Work, a 42-year financial industry veteran, addresses head-on in his new book and in this conversation. After 17 years working for firms like Smith Barney and Shearson Lehman Brothers, Ira walked away from the traditional brokerage model — not because he failed, but because he saw how it was failing clients.In this episode, Ira breaks down four persistent myths that quietly erode investor wealth, explains why tax-deferred retirement accounts may carry more risk than most people realize, and makes the case for financial coaching over traditional advising. Listeners will walk away with a clearer picture of what questions to ask, what costs to watch for, and what it actually means to have a financial plan built around their life and not just their portfolio.About Ira WorkIra Work is an Investor Coach and founder at First Financial Coaching, Inc., with over 42 years of experience in the financial industry. He holds multiple advanced designations including ChFC, RFC, AIF, AAMS, CASL, and CRPS. After spending his first 17 years at major wirehouses, Ira transitioned to independent financial coaching focused on investor education, behavioral science, and evidence-based investing. He is the author of The Investor's Coach: How You Can Rise Above Wall Street's Myths and Build Real Wealth.What We CoverWhy stock picking and market timing feel logical in the moment but fail investors over timeThe real reason 10-year fund track records are nearly meaningless for picking investmentsHow hidden trading costs inflate what investors actually pay beyond the stated expense ratioThe IRA tax trap: why deferring taxes today could mean paying far more tomorrow if rates riseThe one question Ira asks every new client that most advisors never think to raiseThe difference between a financial advisor and a financial coach, and why one asks about your life while the other asks about your moneyResources MentionedThe Investor's Coach by Ira Work — available on AmazonCome Back America by David Walker (U.S. Comptroller General) — referenced in the tax trap discussionNavigating the Fog of Investing — documentary film featuring Morningstar's CEO on fund ratingsConnect with Ira WorkWebsite: irawork.com / firstfinancialcoach.comEmail: irawork@firstfinancialcoach.comSupport the show

An airhacks.fm conversation with Bruno Borges (@brunoborges) about: discussion about the JAZ command launcher for Java, JVM tuning and default ergonomics for containers versus dedicated cloud environments, replacing the Java launcher with jaz in container images, supporting Java 8 to 25, maximizing resource utilization on kubernetes to reduce waste, running Java on Azure Functions, Azure App Service deploying a fat JAR without a container image, Azure Container Apps as a platform on AKS without YAML, Azure Kubernetes Service and AKS Automatic, Bicep as infrastructure as code, deploying a JAR to Kubernetes via OCI artifacts and a custom operator, Microsoft Foundry and the Microsoft Agent Framework, Semantic Kernel learnings, the Copilot SDK for Java communicating with headless CLIs, A2A and ACP protocols and MCP, agents as microservices with scoped tasks, guardrails, and sandboxing, per-agent model selection for cost and reasoning trade-offs, observability and traceability between agents with opentelemetry, grounding LLMs against MicroProfile, Jakarta EE, JAX-RS normative RFC 2119 specifications for hallucination-free Java code generation, the Boundary Control Entity pattern and business components as Java packages, package-info.java for semantic context, GitHub Copilot skills and custom instructions in Visual Studio Code, the AI Rails skills site, zero-dependency Java CLI scripting, reducing dependencies by reusing source code instead of JARs, the org.json reference implementation reduced to five classes, StackGres and OnGres running Quarkus and GraalVM to manage Postgres on Kubernetes, the Digg Into Java community Bruno Borges on twitter: @brunoborges

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

On this week's pod: Shout outs:Curtis & Shankland shine for ScotlandRangers Ladies Lunch NARSA business:Destination NARSA - Nashville 2026 - 9 days / 1 weekIndividual nights tickets on sale now: narsa.ca/ticketsFriday night is a western themeDavie Cooper Memorial Topgolf Tournament now on sale - https://narsa.ca/tickets/RFC Executive Director, Fraser Thornton and RFC CEO, Jim Gillespie, and Greg Marshall are joining us at NARSA 2026!!!RFC 9-in-a-row legends: Derek Ferguson, Scott Nisbet, David Robertson, and Mark WaltersRFC Historian: David MasonEntertainment: MC David Edgar, Stuart Hay, Rebecca Auchterlonie, DJ Angry Bear, and Danny Magic!TICKETS NOW ON SALE: $199 USD | NARSA 2026 NashvilleCommunications:Rangers Women's team blew it (again)Fan Advisory Board - Open for nominationsInstagram and TikTok - follow us at narsacomms#NARSA #RangersFC #WeeklyUpdatehttps://narsa.ca/

Hasbro has filed a trademark for "Hasbro Makits," a new in-house model kit line — and the RFC crew has a lot of thoughts about what that could mean for Blokees, Yolopark, and the future of Transformers collecting. Plus, the Liokaiser HasLab arrives for most of the team, and Brian declares it his favorite HasLab ever. The post Radio Free Cybertron 989 – Hasbro Files the “Makits” Trademark — What Does It Mean? appeared first on Radio Free Cybertron.

Hasbro has filed a trademark for "Hasbro Makits," a new in-house model kit line — and the RFC crew has a lot of thoughts about what that could mean for Blokees, Yolopark, and the future of Transformers collecting. Plus, the Liokaiser HasLab arrives for most of the team, and Brian declares it his favorite HasLab ever. The post Radio Free Cybertron 989 – Hasbro Files the “Makits” Trademark — What Does It Mean? appeared first on Radio Free Cybertron.

Today's conversation centers around a new Best Current Practices (BCP) RFC draft written by Jordi Martinez. Our hosts explore the document for service providers and enterprises, including prefix sizing for point-to-point links, the pros and cons of numbering choices, and best practices for prefix pool allocation. Episode Links: IPv6 Prefix Assignment to End-Sites – RFC... Read more »

Today's conversation centers around a new Best Current Practices (BCP) RFC draft written by Jordi Martinez. Our hosts explore the document for service providers and enterprises, including prefix sizing for point-to-point links, the pros and cons of numbering choices, and best practices for prefix pool allocation. Episode Links: IPv6 Prefix Assignment to End-Sites – RFC... Read more »

This is a recap of the top 10 posts on Hacker News on May 26, 2026. This podcast was generated by wondercraft.ai (00:30): Spain blocks prediction markets Polymarket, Kalshi over lack of gambling licenceOriginal post: https://news.ycombinator.com/item?id=48279316&utm_source=wondercraft_ai(01:56): Netherlands blocks US takeover of vital digital supplierOriginal post: https://news.ycombinator.com/item?id=48278406&utm_source=wondercraft_ai(03:23): Big tech's anti-labor playbook has come for WikipediaOriginal post: https://news.ycombinator.com/item?id=48285592&utm_source=wondercraft_ai(04:50): Motorola phones have started hijacking the Amazon app to insert affiliate codesOriginal post: https://news.ycombinator.com/item?id=48274794&utm_source=wondercraft_ai(06:17): The real cost of owning a homeOriginal post: https://news.ycombinator.com/item?id=48281611&utm_source=wondercraft_ai(07:44): Dropbox CEO Drew Houston to step downOriginal post: https://news.ycombinator.com/item?id=48279453&utm_source=wondercraft_ai(09:11): DynIP – Dynamic DNS with RFC 2136, IPv6, DNSSEC, and BYODOriginal post: https://news.ycombinator.com/item?id=48276363&utm_source=wondercraft_ai(10:38): Chemistry behind the Garden Grove chemical tankOriginal post: https://news.ycombinator.com/item?id=48284712&utm_source=wondercraft_ai(12:05): The user is visibly frustratedOriginal post: https://news.ycombinator.com/item?id=48275059&utm_source=wondercraft_ai(13:32): Uber, Lyft drivers in Massachusetts form first US ride-share unionOriginal post: https://news.ycombinator.com/item?id=48281509&utm_source=wondercraft_aiThis is a third-party project, independent from HN and YC. Text and audio generated using AI, by wondercraft.ai. Create your own studio quality podcast with text as the only input in seconds at app.wondercraft.ai. Issues or feedback? We'd love to hear from you: team@wondercraft.ai

On this week's pod: Shout outs:CondolencesRangers Ladies Lunch NARSA business:Destination NARSA - Nashville 2026 - 16 days / 2 weeksFriday night is a western themeDavie Cooper Memorial Topgolf Tournament now on sale - https://narsa.ca/tickets/RFC Executive Director, Fraser Thornton and RFC CEO, Jim Gillespie, and Greg Marshall are joining us at NARSA 2026!!!RFC 9-in-a-row legends: Derek Ferguson, Scott Nisbet, David Robertson, and Mark WaltersRFC Historian: David MasonEntertainment: MC David Edgar, Stuart Hay, Rebecca Auchterlonie, DJ Angry Bear, and Danny Magic!TICKETS NOW ON SALE: $199 USD | NARSA 2026 NashvilleHotel: Cambria Hotel Nashville Midtown | Booking: https://www.choicehotels.com/reservations/groups/OI25P7Phoning: +1 615-931-0777 (NARSA is the keyword)Room rate: $199 + Taxes & Fees | Room rate available 3-days prior and 3-days postCommunications:Rangers Women's team blew itFan Advisory Board - Open for nominationsAnother message of thanks for former captain James TavernierInstagram and TikTok - follow us at narsacomms#NARSA #RangersFC #WeeklyUpdatehttps://narsa.ca/

On this episode: Rust has another convert, npm takes another stab at stopping the hackers, and Jack had a coding battle against robots.Timestamps:1:00 - Bun switches to Rust6:45 - Jack's battle against AI on Greenfield Games16:01 - npm RFC to block install scripts22:10 - State of Web Dev AI survey results37:10 - Mark Erikson joins the AI revolution41:45 - What's making us happyNews:Paige - Bun, but in RustJack - Jason Lengstorf's Greenfield Games TV showTJ - npm RFC to block install scriptsLightning News: State of Web Dev AI survey resultsMark Erikson joins the AI revolutionWhat Makes Us Happy this Week:Paige - Riding in WaymosJack - Wilma the Bat Dog for the Portland PicklesTJ - Dungeon Crawler Carl book seriesThanks as always to our sponsor, the Blue Collar Coder channel on YouTube. You can join us in our Discord channel, explore our website and reach us via email, or talk to us on X, Bluesky, or YouTube.Front-end Fire websiteBlue Collar Coder on YouTubeBlue Collar Coder on DiscordReach out via emailTweet at us on X @front_end_fireFollow us on Bluesky @front-end-fire.comSubscribe to our YouTube channel @Front-EndFirePodcast

Take the 2026 AI Engineering Survey and get >$2k in credits and AIE WF tickets!This was recorded before Railway suffered a major GCP outage on May 19, despite being a multi-AZ, multi-zone mesh ring, with HA fiber interconnects between their Metal GCP AWS, because workload discoverability was unintentionally still tied to GCP. All has been resolved with a post-mortem.Railway did not start as an AI infrastructure company.It was founded in 2020 years before agents became the default way people thought about deploying software. Jake Cooper, formerly at Bloomberg and Uber, started Railway with a simple obsession: the activation energy to ship something to production should be near zero. Push code, get a URL, iterate. No Docker files, no Kubernetes manifests, no Ansible scripts stacked on Ansible scripts.For years, this was a slow grind. Railway spent its first 18 months hand-acquiring its first 100 users with Jake personally greeting every Discord signup on a second monitor.Today, Railway has raised $124m and is growing very fast. A 35-person team supports 3 million users, adding roughly 100,000 signups a week. Their bare metal data centers have a 3-month payback period vs. renting in the cloud, with 70% margins funding aggressive cloud bursting when needed. The servers they own have actually appreciated in value as RAM prices have climbed basically meaning the value of their hardware now exceeds the capital they've raised.From rebuilding Railway's network overlay over a weekend to moving the vast majority of workloads onto its own bare metal data centers, Jake Cooper is trying to build a new cloud for an agent-native world. In this episode, Railway's founder and “conductor” joins swyx and Alessio to unpack why the next era of software infrastructure is not just “Heroku but newer,” what agents need that humans did not, and why the old deployment loop of Git, PRs, CI/CD, and static cloud resources may be heading for a rewrite.We go deep on Railway's infrastructure stack: own-metal data centers, three-month cloud payback periods, cloud bursting, data center debt, Railpack, Nixpacks, Temporal, feature flags, Central Station, content-addressable filesystems, agent-safe production forks, and why the CLI may become more important than the canvas in an agent world. Jake also shares the founder journey behind Railway, how the company survived losing $500K/month, why it now serves millions of users with only 35 people, and why he believes the pull request is dying.We discuss:* How Railway went from a slow six-year grind to adding 100,000 users a week* How Railway thinks about agents as the next dominant software species* Why agents need version control, observability, compute, storage, and orchestration at 1000x scale* The economics of Railway's own-metal data centers and three-month payback* How Railway uses cloud bursting while scaling its own infrastructure* Why data center debt can be a better tool than venture debt for infra startups* Central Station, Railway's internal system for clustering customer feedback and incidents* Why responsible disclosure and over-communication matter for platforms* Why feature flags, progressive rollouts, and shadow traffic are essential for agents* Temporal's strengths, pain points, and why workflows matter for agents* Railpack, Nixpacks, Nix, and lazy-loaded content-addressable filesystems* Why “cattle, not pets” may change if you can clone the pets* Why Railway is building a new cloud from scratch instead of copying hyperscalers* The solo founder path, focus, writing, and how Jake thinks about company buildingRailway:* Website: https://railway.com/* X: https://x.com/RailwayJake Cooper:* LinkedIn: https://www.linkedin.com/in/thejakecooper/* X: https://x.com/JustJakeTimestamps00:00:00 Introduction: What Is Railway?00:02:07 Jake's Path to Railway00:06:13 Railway's Six-Year Growth Story00:08:52 Rebuilding the Business After the Free Tier00:11:17 Agents as the Next Software Platform00:13:29 Railway's Infrastructure Philosophy00:15:42 Bare Metal, Cloud Economics, and the Compute Crunch00:17:22 Cloud Bursting and Five-Cloud Networking00:20:20 Data Center Debt and Infra Financing00:23:31 Data Centers in Space00:25:24 What Agents Need From Infrastructure00:28:24 CLIs, Canvas, and Agent-Native UX00:35:15 Central Station, Incidents, and Responsible Disclosure00:40:30 Safe Rollouts, SRE Agents, and Production Forks00:45:00 AI SRE, Specs, Code, and Tests00:48:24 Self-Replicating Infrastructure and the New Serverless00:53:18 Heroku, Temporal, and Workflow Engines01:04:07 Railpack, Nixpacks, and Lazy-Loaded Filesystems01:06:01 Coding Agents, Token Spend, and Roadmap Acceleration01:10:56 The Pull Request Is Dying01:12:28 Feature Flags and the Agent-Era SDLC01:16:15 Cattle, Pets, and Cloning Machines01:19:29 Solo Founder Lessons01:24:12 Focus, GPUs, and Building a New Cloud01:28:20 Closing ThoughtsTranscriptAlessio [00:00:00]: Hey, everyone. Welcome to the Latent Space Podcast. This is Alessio, founder of Kernel Labs, and I'm joined by Swyx, editor of Latent Space.Swyx [00:00:10]: Hey, hey, hey. Today we're in the studio with Jake Cooper of Railway.Alessio [00:00:14]: Conductor of Railway.Swyx [00:00:15]: Conductor at Railway. Yeah.Alessio [00:00:16]: Choo-choo.Swyx [00:00:17]: Do you actually have that anywhere, like on your business card?Jake [00:00:20]: We call some of our volunteer moderators conductors. I don't have a business card. We're not that big yet. At some point I will. I got handed a nice business card from the Supermicro folks, and I was like, “Damn, this is pretty official.”Swyx [00:00:30]: Business cards are coming back.Jake [00:00:32]: They're cool. They're hip. The conductor thing is good. We're trying to figure out what we want to call each other internally. Some people think it's super cringe and say, “You don't need a name for people internally.” Some people want to call each other something. We still don't have a really good one.Jake [00:00:55]: We've got New Railcrews, Trainiacs. Nothing has stuck yet.Swyx [00:01:00]: I like Trainiac. Trainiac sounds good. Railwayians. For those who don't know, what is Railway? Let's give people a crisp definition up front.Jake [00:01:09]: Railway is the easiest way to ship anything. You go to the canvas, or you talk with Claude, and you say, “Deploy a Postgres instance, deploy my GitHub repository, run this code,” and you're off to the races.Swyx [00:01:22]: You've got a nice animation on the landing page.Jake [00:01:24]: Thank you. None of my work, by the way. They don't let me touch the design stuff anymore.Jake [00:01:25]: We want to make it trivially easy not just to deploy things, but to evolve applications over time. Most tooling right now stacks entropy on top of entropy: Docker, Kubernetes, Ansible scripts, and all these other things. If we can version all of your software and keep track of all the changes, then we can make it trivial to clone environments, fork into a parallel universe, get copies of production data, get copies of any services, make changes, validate them, and collapse them back in without reproducing everything across a staging environment.The Railway Origin Story: From Uber Systems to a New CloudSwyx [00:02:07]: I was looking at your background: Bloomberg, Uber. Nothing immediately stands out as, “This guy is going to found the next great platform as a service.” What prepared you for Railway?Jake [00:02:21]: It was curiosity to keep going deeper. I started out on front-end stuff, working on Wolfram Mathematica and porting it over. Then I briefly moved to Bloomberg, then toward Uber and distributed systems, taking the Jump Bikes systems and moving them to a distributed system built on top of Cadence, the pre-Temporal Temporal.Swyx [00:02:44]: Which, by the way, I'm happy to talk about, pros and cons.Jake [00:02:48]: Totally.Swyx [00:02:51]: But let's do the Railway story.Jake [00:02:52]: It has been a continual step of wanting an experience. Whether it's walking up to a bike, unlocking it, and having it work frictionlessly, or something else, the depth required to make that happen follows from the experience. A lot of the work I do, and a lot of the team does, is in service of that experience. We fundamentally don't care how deep we have to go. We will swim to the bottom of the swimming pool to get the experience.Jake [00:03:17]: I don't have a physics PhD. I did an EECS degree. It has always been about figuring out the next step: how do we get there? That's what led to starting Railway for that experience and then moving all the way to bare metal data centers. I was adding patches to the kernel this week to get the experience there because I can see how much better it can be.Swyx [00:03:49]: Other patches to the Linux kernel this week?Jake [00:03:51]: Yeah. Not upstream. Our fork.Swyx [00:03:52]: That's a flex. Railpack? No, this is different. This is the OS on top of Railpack?Jake [00:03:57]: No, this is an actual kernel patch. It's always literally: what do we have to do to get that experience? Then figure it out. Anything is figureoutable.Swyx [00:04:10]: Would you send the patch upstream, or does it not fit other use cases?Jake [00:04:13]: Maybe. We have to work out the experience internally. It has to do with the storage layer we're building for some of the agentic stuff. Maybe it'll be useful upstream, but it's deeply useful for us internally.Open Source, Forks, and Non-Deterministic VersioningSwyx [00:04:29]: You mentioned open source before. How do you think about starting from open source, and then coding agents letting you do a lot more from forks of it?Jake [00:04:38]: GitHub's original sin is that it's almost a series of broken pointers. You have this thing, then you clone it, and now you've lost the whole upstream. How do we make it trivial for people to modify really small pieces of it?Jake [00:04:51]: We think of Git in a discrete sense: I've either made a change and merged upstream, or I haven't. What would it look like if it were percentage-based, a little more non-deterministic, or a stream of changes that users traverse as a percentage rolled out in general and then rolled all the way up?Jake [00:05:13]: We have the open-source kickback program and let you deploy templates because we want to make it trivial for people to version these shards over time. It solves a large problem around authentication, authorization, and security. NPM has a way to define, “Don't take any new packages.” The ideal end state is that you roll out progressively to users with the minimum impact zone and continue rolling up. JPMorgan should probably be the last one on the patch line, for all our sakes, because our money and livelihoods are there.Jake [00:05:53]: It's okay if Johnny Vibe Coder gets a broken patch because there's so much entropy in the system that the rubber has to meet the road at some point. You have to test at varying levels.The Long Grind: First Users, Free Tier, and Making the Business WorkSwyx [00:06:13]: I wanted to pull up this glorious chart, which is your usage or number of daily signups?Jake [00:06:22]: Daily signups, I think.Swyx [00:06:24]: You started six years ago. It was a slow grind, and now you're on a rocket ship. You say, “Don't doubt your fight and don't quit.” Maybe pick out certain points that were key inflections for the company.Jake [00:06:40]: At the start, it's about getting your first 100 users, hell or high water. We had a website and a support link. The support link was the Discord channel. I had notifications on with two monitors: the monitor I was working on and the other monitor with Discord. If anybody came in, I was immediately like, “Hey, how's it going?” It was rare, so getting those first 100 users to come back was the start.Jake [00:07:14]: Then you build a consultancy factory because users want all these things. You have to go back to the board and ask, “What is the actual product offering I want to build on top of this?”Jake [00:07:28]: VCs want charts that always go up and to the right, but in reality you don't necessarily want charts that look like that. For us, there have been periods of expansion where we add features to test use cases, and periods of compaction where we ask, “If the experience we have is good, how do we make it significantly better?” Maybe we strip out features that don't fit our ICP anymore.Jake [00:07:57]: The boom from 2022 to 2023 came from the free tier. Everybody under the sun was using it.Swyx [00:08:09]: A lot of Reddit bots and Discord bots.Jake [00:08:12]: And crypto miners. When you build an open product on the internet where anybody can sign up, the internet is a horrible place with so many things. You go through periods of asking, “How do I reach as many people as possible?” Then, “How do I fit the exact use case for the people who really matter and are really excited about this specific thing?”Jake [00:08:39]: Then there was a two-year period of making the actual business work. During the free-tier era, we were losing about half a million dollars a month.Swyx [00:08:59]: On a $20 million bank account.Jake [00:09:02]: On a $20 million bank account with maybe $50,000 a month in revenue. That's a horrible business. I don't know how anybody invested. But you have to go through it and say, “We have an experience people love, but the business has to work.”Jake [00:09:17]: There are two schools of thought. You can run the horrible business all the way up with bad margins, or you can go back and make it work. We've always wanted a super lean team. We're 35 people right now. It's very small.Swyx [00:09:36]: Supporting three million already?Jake [00:09:38]: Yeah. We're adding 100,000 users a week right now, so it's growing fast. We don't want to add headcount for the sake of headcount or throw bodies at problems. We want to build systems. It's hard to build systems during expansion because you're adding things to the system because people are asking for them or things are breaking.Jake [00:10:00]: We had to cut off the free users for a little while, rebuild the business, and make sure it worked. We want to reach as many people as possible because software is important. It's become difficult to create things in the physical world, so it's important to make it easy for people to build in the virtual world and have access to creation. But there are legs to that journey.Jake [00:10:30]: You can see divots in the charts. If you follow between 2025 and 2026, it's either summer or winter. People go on holiday with family.Swyx [00:10:50]: It affects that much?Jake [00:10:51]: Yeah. It's kind of B2C and kind of B2B. People are shipping constantly, then they stop. Our activation curve now shows more people activating on weekdays because we have more business users, so it smooths out over time.Agents as the New Interface to DeploymentSwyx [00:11:17]: Was there a point where you started prioritizing AI development or agent development?Jake [00:11:24]: We've prioritized agentic as a top-of-funnel thing. Over the last six months, we've deeply prioritized agentic as a mechanism to build and deploy things because we believe the curve is so steep and that is how people will build and deploy software.Jake [00:11:42]: It almost fundamentally doesn't matter whether this is dot-com or not because we're all on the internet anyway. If agents are going to deploy a bunch of things and we hit an inference wall at some point, we'll fix those problems. The dominant species over the next 10 years is that we've moved from assembly to C to C++ to JavaScript to words. You're going to need to close that loop.Swyx [00:12:13]: When you say this is dot-com, did you mean buying the domain, or the general case?Jake [00:12:17]: I mean the dot-com era, when companies had a huge run-up because people understood the internet was important. Then they hit bottlenecks, fundamental laws of physics, math didn't work, and everybody came back down to earth. But it didn't matter because the internet became so impactful. If you operate on a long enough time horizon, you should build these things anyway because you can see where it's going.Jake [00:12:45]: That's where I think a lot of agent stuff is. You get to a point where you're running thousands of agents in parallel. What is the inference cost? What is the compute cost? How do you make that efficient? How do you coordinate all this? We have issues coordinating humans; we don't even have good tooling for that. Now we have to figure out how to get agents to coordinate, safely version changes, and know when to raise their hand for someone to intervene. Otherwise it becomes an interrupt factory.Railway's Infrastructure Thesis: Network, Compute, Storage, and MetalSwyx [00:13:19]: Let's go right into the technical side. What are the core infrastructure or architectural beliefs of Railway that allow you to do what you do?Jake [00:13:29]: The primitives matter a lot for us. We need network, compute, storage, and orchestration around it. You need control over a lot of those things. We've talked a lot about how we don't really use Kubernetes because we want higher-order control to place workloads in very specific places.Jake [00:13:48]: The reason is that you have to be very efficient with agents: memory reuse and all these other things, or you're going to massively blow up your cost structure. Being able to rack and stack your own servers and build your own metal unlocks performance and cost. Experiences where you're running 1,000 agents in parallel are not massively cost prohibitive.Jake [00:14:13]: Token use and compute use are blowing up. Over time, those things have to get a lot more efficient. You can get a lot of margin to make those experiences solid by building your own metal. That's all in service of offering a differentiated experience to as many people as humanly possible.Swyx [00:14:51]: You have a data center in Singapore.Jake [00:14:53]: Yeah. We have two in every other region now. In Singapore, we're adding a second one in Q3.Swyx [00:14:58]: What's it like? I've never built a data center. Do you go to Equinix and say, “I want some slots?”Jake [00:15:05]: Yeah. Equinix. You basically go and say, “I want power and I want a cage.” They say, “Great, here's what it's going to be.” You rent the cage for a period of time, fill it with racks and servers, and hook up internet to it. That's all the pieces.Swyx [00:15:36]: Then you handle everything else.Jake [00:15:37]: You handle everything else.Swyx [00:15:39]: What's the math versus clouds doing it for you?Jake [00:15:43]: If we rented in the cloud, our payback period when we go to metal is about three months.Swyx [00:15:50]: Which is crazy.Jake [00:15:51]: It's nuts. That's four years of depreciated hardware. You're going to see a lot of this compute crunch because hyperscalers are buying up a lot of stuff. We're working directly with OEMs, resellers, and people building these machines: Supermicro, Dell, and others.Jake [00:16:11]: Upstream, there's a bunch of supply pressure. When we raised our last round, between deploying capital for servers and now, the amount of money we've raised is less than the amount of money we have in the bank plus the value of the servers because the servers have appreciated as RAM has gone up. It's nuts how valuable hardware has become.Jake [00:16:50]: If you look at hyperscalers, they deployed around $80 billion of capital expenditures this year, and next year will be more. That's a massive infrastructure build-out. You look at that and think it's crazy that they're spending way more than the Manhattan Project. But if every person is going to run dozens or hundreds of agents in parallel, you have no conceptual idea how much compute is required to make that experience happen, even if you're deeply efficient and sharing resources. And that doesn't even count inference.Swyx [00:17:22]: How do you plan the build-out? The growth chart is so vertical. Are you usually at 100% utilization as soon as racks are live? How far ahead are you planning?Jake [00:17:33]: We still maintain cloud presence for bursting. We work with AWS, GCP, and a few other clouds. We can rent, and then the moment we get space or power, we compact those workloads off the cloud. We started on the clouds, then built a system to migrate to our own metal. There's nothing that says you can't continually do that again, and that's exactly what we do. We never want to be compute constrained.Jake [00:18:09]: At the start of the year, we actually became compute constrained because one upstream provider wasn't able to give us quota at the rate we needed, and the hardware was slower. I spent a weekend rebuilding our entire network overlay so we could straddle five clouds: Oracle, AWS, ourselves, GCP, and one other one. We can do more than that now.Jake [00:18:38]: We got into a spot where we were trying to pack instances tight because we couldn't get enough compute. That led to a few reliability issues, which are now past us. I made a tweet pointing out that it's becoming harder and harder to acquire compute at the rate these models need to acquire compute. We got bit by it.Swyx [00:19:15]: How do you think about pricing knowing you might not have your own metal available at all times? Are you pricing assuming you need extra margin if you end up going into the cloud?Jake [00:19:26]: Because we've built out our metal data centers, our margins on metal are around 70%. We can deeply subsidize the cloud business if we want to scale at a reasonable rate. We have a few levers: metal, which makes the margins; cloud burst; debt to buy servers; and venture capital. It's an interesting operational problem: how much cash do we have, how much should we raise, how quickly can we deploy it, and can we scale revenue as quickly as we scale compute?Jake [00:20:05]: If we continue making it trivially easy for people to build and deploy, then the faster we close that loop and the more operationally excellent we are with capital, the faster the business can scale. It's almost a straight linear deployment rate.Financing Infrastructure: Hardware Debt, VC, and Operational LeverageSwyx [00:20:20]: I think infra startups raising debt is a tool people don't utilize enough or know enough about. What can you tell us about that? Is it secured against your CPUs?Jake [00:20:32]: It's secured against our hardware.Swyx [00:20:37]: What rates do you get? Who are the lenders?Jake [00:20:39]: We pay prime plus a spread, and we can refinance any of the debt as rates go down. The terms are pretty good. The unfortunate thing is that Twitter has no nuance, so people say, “Venture debt bad.” But as with all things, there are specific tools and areas where you can be deliberate instead of using one tool as a hammer. Venture capital is not the hammer for everything. You have to explore and figure out what works.Swyx [00:21:12]: VC is usually the most expensive financing you can get.Jake [00:21:15]: Yeah. I also think people think about VC incorrectly from a capital-raising perspective. Most people think, “How do I raise as much money as possible from whoever is probably the best I can get at that time?” That's close to right, but what we've tried to do is figure out what unfair advantage we can buy with that equity.Jake [00:21:34]: It's the most expensive equity you're going to give away at that point in time, assuming the company keeps getting better. How do you use it to work with someone stellar who complements you? In the seed stage, I had never started a company. Ray Tonsing had good advice, and I could text him all the time. He was really fast. Awesome.Jake [00:22:01]: Then with John and Erica at Unusual, they said, “You roughly know what you're doing building a product. We'll mostly leave you alone and be available for advice.” Amazing. Then we got to Series A and the business was an operational tire fire because we didn't know how to scale a business. Work with Erica, and Jordan is over at Redpoint, so bonus.Jake [00:22:28]: Now we've raised from TQ and FPV as we're moving into enterprises. Every step of the way, we've asked: who can we partner with at this specific time to unlock the next section of the journey? I don't know enterprise sales. As an engineer, I can eyeball what features we might need, and we have wonderful people internally who can help. But you want boardroom dynamics where everyone is aligned and asking, “How do we win this?” instead of bickering about strategy.Data Centers in Space and the Physics of ComputeSwyx [00:23:31]: You had a tweet about data centers in space. Why no data centers in space?Jake [00:23:37]: It's not “no data centers in space.” My hot take is that I think it is solvable. I've just never seen anybody solve it.Swyx [00:23:49]: You said, “How are you going to dissipate that much heat in a vacuum?” You're making a physics claim.Jake [00:23:55]: I haven't seen anybody prove how you're going to dissipate that much heat in a vacuum. It doesn't mean it's not possible. It just means nobody has brought it up yet.Swyx [00:24:05]: Astrophage.Jake [00:24:06]: I don't know what that is.Swyx [00:24:07]: The Martian thing. Okay, you're very logical.Jake [00:24:09]: It could work. A lot of people are putting the cart before the horse. They say, “We're going to put data centers in space.” Okay, but how? “We have time to figure it out.” It's like in The Martian where they ask how they're going to intercept something and say, “We'll figure it out.”Swyx [00:24:36]: Making a bet on human invention is weird because you blind trust that it can be solved. But with physics, there are first-principles bounds you can put on it. Maybe not. Maybe you're asking to travel time or break a fundamental thermodynamic law.Jake [00:24:57]: I don't know how VCs do this either. How do you know what's not possible and a grift versus what's possible but sounds completely insane? “We're going to put data centers in space.” Coin flip as to which it is, and I guess you'll know in 10 years. That's one cycle.What Agents Need: Versioning, Observability, and 1,000x ScaleSwyx [00:25:23]: Moving back to agents. The branching, fast spin-up, and orchestration you do feels like pre-work that happened to be exactly what agents want. What do agents want differently than humans?Jake [00:25:37]: They want the ability to version things. It's not that different; it materializes slightly differently. Agents want a way to test changes incrementally. Engineers have feature flags. Is there a reason agents can't use feature flags? I don't think so.Jake [00:25:54]: They want version control. Can we use Git or not Git? That one is up in the air. I think something outside Git will emerge for how we version these things over time. They need observability. You need to query what happened, when it happened, which steps failed, traces, logs, metrics, and all the rest. They need network, compute, and storage. They need to write files, save files, iterate on files, and snapshot file systems.Jake [00:26:25]: A lot of what humans needed is in line with what agents need. Branching and forking are not different; we're just moving 1,000 times quicker. It can look like you need something massively different, but what you need is something massively better than what existed. You need orchestration massively better than Kubernetes. You need networking probably better than Envoy. It goes all the way down the stack.Jake [00:26:55]: If the workload profile doesn't change so much as it gets massively compressed because you need thousands of these things, what assumptions change? etcd is going to melt. You need to replace it with something. You can go all the way down the stack and say, “That part has to change, that part has to change, and that part has to change.”Jake [00:27:19]: The interesting thing about the super-exponential curve is that you have to build systems where you can rip out those parts at any time because a new bottleneck might emerge. You get good at parallel agents, and a different part of the system breaks. So it's similar to what humans needed, but at 1,000x scale.Jake [00:27:55]: How do you do code review in the age of agents?Swyx [00:28:00]: You throw more agents at it.Jake [00:28:01]: You don't. But then who reviews for CVEs and all these other things?Swyx [00:28:07]: More agents.Jake [00:28:08]: And that's how we hit the inference wall. You can continually throw agents at the problem, but I think there's a limit to the number of agents you can throw at a problem.CLI, Agent Handles, and Closing the LoopSwyx [00:28:24]: You already had a CLI before it was cool. How is the shape of what you're exposing changing, if at all?Jake [00:28:28]: CLIs have always been cool. The CLI changes because we think about how to give Claude, Codex, ChatGPT, or any model a handhold.Jake [00:28:50]: A CLI is a single command: deploy, get logs, and so on. Things that were prohibitively annoying to humans are not annoying to agents. They're nice. If I handed you a CLI with 40 arguments and 600 flags, you'd think, “I'm never going to use all of this.” But if you hand it to an agent, it says, “This is excellent. I have so many handles to work with.”Jake [00:29:24]: If you're going to expose things to agents that way, you want as many handles as possible where they can get information, query dynamic information, and close the loop quickly. Most problems right now are about how to close the loop as quickly as possible. Where does the agent get stuck, and how can you remove that?Jake [00:29:49]: Telemetry is important. If you can tell where the agent gets stuck from the CLI and say, “12% of people deviate from the happy path because of this, and now I add this argument and drive it down to 2%,” you massively increase the rate of loop closure.Jake [00:30:03]: That's how we think about not just the CLI, but every point in the dashboard. It's a user journey: I hear about Railway. I get something deployed. I get my first green build or aha moment. I see an endpoint, logs, whatever. Then I iterate. The iteration loop is indefinite. The user wants to deploy a new thing, a Postgres instance, change code, and keep iterating.Jake [00:30:36]: If you focus on the iteration loops and what's blocking them from closing quickly, one thing we say internally is: you never want to be waiting on compute anymore. You always want to be waiting on intelligence. If you're waiting on compute, there's a bottleneck that needs to be destroyed because eventually that bottleneck becomes so large that another workflow emerges to change it.Jake [00:31:04]: We've built a product where you push code, build it, and so on. But I fundamentally believe the push-pull loop is going away. We'll get to a point where you make a small change in production, that change is versioned across your infrastructure, you're working alongside copy-on-write versions of your database and infrastructure, and then you merge it in and it's instantaneously live. That's the holy grail of loops. The push-pull-rebuild thing is a point of friction that we're removing entirely.Canvas as Output: Dashboards, Context Anchors, and HyperstructuresSwyx [00:31:43]: It's incredibly fast. If anyone hasn't tried it, that fast feedback is great. My hot take is that Railway was famous for its canvas, which visualizes your infrastructure and lets you manipulate it visually. But that was for humans. For the next phase of growth, Railway CLI is more important than canvas.Jake [00:32:05]: The canvas is funny because it's a mechanism to show changes over time. You're right that previously we used it a lot as an input. Moving forward, its goal is more like an output. You would go to the canvas, make changes, see them, and watch your infrastructure evolve. Now agents have access to the CLI and can make those changes. So the canvas becomes an output: what information does the human need at this moment to make suitable decisions about control requests? Do I approve this or not?Jake [00:32:57]: It also has to be an anchor for your context, a port in the storm. Think of it like layers in a file system. You start with a project, then drill down into services, then into a function or code, because you want to represent the entire thing not just in your head, but in the canvas. Other people can share that representation, think on the same wavelength, and move quickly.Jake [00:33:33]: A lot of organizations get in trouble as they scale because all the context lives in someone's head. “How does this microservice work?” “I have no idea; go ask this person.” Then you have whole categories of products built around context discovery. A lot of that melts away if you have a solid hierarchy and can infinitely nest services, code, context, and everything else all the way down. That's what lets you build these structures over time.Jake [00:34:18]: It's also what lets us build what I've called hyperstructures: things that are way bigger. You look at the Golden Gate Bridge and ask, “How did we build that?” There's a meme that we lost the technology. To some extent, yes, because the coordination that built those things evolved and changed. We lost some of the art of building structure as we jammed everything into Slack.Swyx [00:34:52]: But you jam everything in Discord.Jake [00:34:53]: Same point. It doesn't matter. It's message passing and interrupts, message passing and interrupts.Swyx [00:35:00]: So you're arguing there should be something better and more structured than Slack?Jake [00:35:04]: Yeah. For sure. I think Slack is awful, and Discord is awful too.Central Station: Context Routing, Support, and Incident ClustersSwyx [00:35:09]: This is the equivalent of my mom test. What have you done that has your solution to this?Jake [00:35:15]: Internally, we've built a tool called Central Station that aggregates all the context from our users. Every piece of feedback, every customer support item, everything gets aggregated into clusters. If an incident is brewing, we can determine how many users are affected and break off a discussion based on that.Jake [00:35:40]: That is more helpful than long-running channels where you're trying to decide which channel to put something in. If you can dynamically aggregate information and dynamically route it to the right person based on context, it works better. We know internally that these four people are close to networking. If we see a networking thing, we can drill it down to those four people. If it's with this part, we can look at the commits. This is no longer a manual process internally.Jake [00:36:13]: If you go to station or help.railway.com, that's why we built it. We wanted to scale with a massive amount of leverage by aggregating feedback.Swyx [00:36:27]: This is built in-house?Jake [00:36:28]: Yep.Swyx [00:36:29]: I remember helping out on this one with Angelo in 2023. You scale a lot with a very small team.Jake [00:36:38]: Yeah. We're about 10 times bigger now.Swyx [00:36:40]: You have your full developer code here? Very cool.Jake [00:36:44]: If you go to railway.com/stats, we expose this as a pub-sub-able thing. It's all real-time metrics. There's a way to get it as JSON somewhere if you care.Jake [00:37:01]: We're big on trying to build everything in public and talk about what we're working on. We've had issues in the past, and we'll say, “Here's how we're fixing these things.” We've gotten compliments and flak for incident reports. We're always trying to make them better and talk with people.Incidents, Disclosure, and Progressive RolloutsSwyx [00:37:20]: You had a big one recently. I liked that it was scoped to 3,000. You presumably used Central Station. Talk through what happened and how you address it internally as a team.Jake [00:37:38]: Internally, this one really sucked. It had to do with an upstream provider that didn't do the behavior it said it documented, which is unfortunate given they wrote the RFC for how the behavior should work. We rolled those things out, and Central Station caught it initially when a couple users said caches weren't invalidating. We turned it off immediately.Jake [00:38:03]: When you roll out to a large user base of three million people, you get a lot of disparate behaviors. We tested in staging and had tests, but we hit an edge case. We've hardened those systems, and now we can make that better. But it was a tough one.Swyx [00:38:39]: I always wonder how private disclosure is supposed to work if people find an issue. Are they supposed to contact you first? When you run a platform, these things will happen. What channels should people pursue to quietly resolve it before it becomes a bigger incident?Jake [00:38:59]: There's responsible disclosure. We err on the side of over-disclosing and letting you know something is wrong versus having your provider gaslight you. We've erred on sharing those things more publicly, even if they impact a small subset of users. That's a decision we've made internally. We have four values. One is honor. The honorable thing is to notify people to the widest degree at which they may have been affected or there was an issue, and then confront it head-on: why did it happen, what can we do better?Swyx [00:39:45]: Not the whole user base. That's because of incremental rollouts and other things?Jake [00:39:50]: Yeah. Progressive rollouts.Swyx [00:39:54]: That should be the norm at all large platforms.Jake [00:39:58]: It should. A variety of companies do this. There's the quote that Meta runs 10,000 different versions of Meta. To our earlier point about agents, they need the same thing. They need shadow traffic and all these other things. We've built so much ceremony around production being sacred that we need to make it trivially easy to test different behaviors in a safe environment. Then you can make mistakes in a safe environment.Safe AI SRE: Customer Agents, Forked Environments, and Production ParityAlessio [00:40:30]: Do you see a world where these things get automatically caught, not necessarily by your agent, but by your customer's agent? The cache invalidation issue seems easy to check if you know to look for it.Jake [00:40:44]: It's hard because to determine it, we almost need to hook into your observability infrastructure. That's why we have the template loop on the platform: so you can roll things out progressively. You can roll out to Johnny Vibe Coder initially, or push a shard that someone consumes at their own leisure. Or you can roll it out over weeks: 0.1% of people, 1% of people, early adopters, then all the way up. That's the non-deterministic version control we talked about earlier.Jake [00:41:30]: I believe that's where most things should go, because most companies end up building staged rollout systems in-house. It's the same thing built again and again at every company. There's a massive opportunity to consolidate developer debt.Alessio [00:41:45]: You should have a free tier. Model providers give free tokens if you let them use the data. You could give free compute if someone is the number-one shard that goes out and lets you plug into their observability.Jake [00:41:55]: We do that. That's why we talked about the impact on 3,000 people. We start with lower-impact people. Larger companies on the platform are last to receive those rollouts so they have a version of the platform that's deeply stable.Alessio [00:42:16]: I have three services, so I'm sure I get the first rollout. You can nuke my thing at any time. There are all these SRE agent companies. Observability people also want agents that fix upstream problems. You have your own agent in the canvas now. How do you see that playing out?Jake [00:42:39]: It's the stacking entropy problem. If you don't have primitives to make iteration in production safe, it becomes difficult. If you're an observability provider saying, “Here's the fix to this error,” assume 80% are good and make sense. But in the last 20% long tail of complex issues, if you let somebody stamp it, you create an opportunity for an incident.Jake [00:43:08]: That's why forked environments are important. People have staging, but it always drifts from production. You need primitives, workflows, and experience built first-party on the platform so you can fork any service at any point in time.Jake [00:43:33]: I think of the canvas as a sheet of transparency paper. The agent is a little guy you push up into the canvas. It should say, “I need to copy that service and that service so I can test these two things.” It gets a read-only copy of production. Anything that's PII gets marked as a transform when we clone the database, create a copy-on-write version, or read from it. Then the agent makes changes and asks, “Does this actually work?” as close to production as possible.Jake [00:44:22]: That's how close you have to be, or you get massive drift. The system becomes unstable. You see this with massive systems built on Docker for local, Kubernetes for production, and a specific thing for something else. That complexity slows developers and becomes unstable at scale, making it hard to iterate. We want to compress that way down and say, “As close to prod as possible is where we want to be.”From AISRE Skeptic to Agent BelieverSwyx [00:45:00]: I was texting Erica for questions, and she says you were originally not a believer in AISRE. Have you come around on it?Jake [00:45:10]: I flipped, but I'm still not a believer in AISRE if you don't have the primitives to make it safe. If you unleash AISRE on production infrastructure without safe primitives for copying volumes and making sure things are fine, it's going to nuke your production database. It's not a matter of if, but when. I'm a big believer in making those loops safe.Jake [00:45:33]: I was a deep AI skeptic until 2023. In 2024, I thought, “Maybe I can roughly make this thing do it.” In 2025, I thought, “Now I can hold this.” Over winter break, everybody came back saying, “It's almost impossible to hold this.”Swyx [00:46:01]: Did you see this on the Claude docs? CloudBot? OpenCloud?Jake [00:46:06]: It's gotten to a point where it's harder to hold it wrong than to hold it right. There's a scene in Avengers where Vision picks up Thor's hammer and says it's terribly well-balanced. It self-balances and works well. I'm a deep believer at this point that this will be the dominant species: assembly, C, C++, JavaScript, words.Swyx [00:46:35]: It feels like a big jump.Jake [00:46:37]: It is. But it's not like you abandon CPU-based discrete logic and move straight to fuzzy logic. You need both. Your skills should call code or applications or some static structure. You can use skills to distill what the procedure should be or how the code should act.Jake [00:47:02]: I'm coming to a thesis: you need three points. You need a clear spec defining the system, the code, and the tests. When you say it out loud, if you've been in engineering long enough, you're like, “Of course. That's an RFC, tests, and code.” But they all matter. Having them together lets them reinforce each other: the spec and tests match, but the code doesn't, so reconcile it. Or the tests and code match but the spec doesn't, so reconcile that. That's the iteration loop.Jake [00:47:41]: That's why you're seeing people talk about software factories, docs, and reconciliation. Some of that is architectural astronomy if you don't implement it, but that loop is where most things will end up.Swyx [00:48:07]: For listeners, we've been talking about this on the pod for three years: the holy trinity of specs and tests. Itamar Friedman from Qodo is the reference if people want to look it up.Self-Modifying Infrastructure and the End of Push-Pull-RebuildSwyx [00:48:18]: One thing I want to mention on the OpenCloud idea is self-modification. I don't know how Railway would support it, but I have my OpenClaw, and I just tell it it has the Railway CLI and can do whatever. In theory, whatever capabilities or new infra it needs, it can call the Railway CLI, provision it, and add it to itself. The agent can modify its own infra.Jake [00:48:45]: It's nuts. I have a loop set up where you put the Railway CLI on top of something that runs on Railway. You're authenticated as whatever the current box is, and you can make any changes to it. Then you call Railway deploy, and it deploys itself.Jake [00:49:04]: It's like: “I need to spin up this instance of this environment. I already exist in this environment. Excellent, I have access to a Postgres instance now.” That's where we want to go with agentic, self-replicating infrastructure. That's your loop: iterate in production. You continue making changes. If it works, merge it upstream. If it doesn't, throw it away.Jake [00:49:37]: How do you make throwaway copies trivial to spin up and super cheap? The era of “I have an AWS instance with four vCPU and 16 gigs of RAM” is going to get destroyed. If you do that for agents, you need a thousand of those machines. It's prohibitively expensive compared with what we've spent a ton of time figuring out: the atomic unit of deploy, whether you call it isolates, sandboxes, or something else. Only pay for what you use, spin up instantaneously, and close the loop as quickly as possible.Jake [00:50:15]: If the system can self-replicate safely and say, “This is my environment, I'm making these changes,” it can come back with, “Does this look good? This is a new state of infrastructure given this prompt. I think I've solved it.” Then you go back and say, “Actually, it looks different.” It does the loop again. Then you say, “Cool. Apply.”Swyx [00:50:38]: That's retroactively obvious, which is the most useful kind. Any other comments on agent deployment on Railway?Jake [00:50:51]: It's getting better every day. I'm on X or Twitter. You can always yell at me about the parts not working as well as they should, because plenty of things should work way better.The New Serverless: Stateful, Long-Running, Pay-for-What-You-Use LinuxSwyx [00:51:04]: At this stage, when people want massively or embarrassingly parallel compute, they usually talk serverless. I feel like there's a new serverless compared to the previous five years of serverless. You're in that new bucket. Do you have comparisons or philosophical differences you want to call out?Jake [00:51:31]: It's somewhere in between. It's the ability to run stateful, long-running workflows or executions.Swyx [00:51:42]: Vercel has Fluid Compute, Cloudflare has some container thing, Google has App Runner and others.Jake [00:51:55]: That's where everything is roughly going, and it's why we've been working on this for six years. We believe users need access to a computer: a box that speaks Linux. They need to deploy what they want. Other systems change the surface area of what you can build. For us, users need a computer and need to deploy anything they truly want. That's why we've focused on the primitives: network, compute, storage. If we give you those and expose them so you can run things indefinitely, that's where we believe it's going.Jake [00:52:43]: Twitter has no nuance, so everyone says “servers” or “serverless.” It's always somewhere in the middle: I want to run it for a long time, but I don't want to provision the resource statically or pay for things I'm not using. That's been our thesis from day one: pay only for what you use, run it indefinitely, and it is full Linux.Swyx [00:53:12]: That's why I like the naming of Fluid. It's fluid. Flexible.Heroku, Focus, and Carrying the Torch Without Becoming the PastSwyx [00:53:18]: Another milestone is the Heroku official deprecation. You're one of the presumptive new Herokus. “New Heroku” has been a category for as long as I've been in developer tooling. It's finally happening. What was that like? Any behind-the-scenes of, “This is the moment”?Jake [00:53:42]: You have people where you're like, “You were running stuff on here? You, as this company?” It's crazy that names you would know are running on it and now coming to us saying, “We want to move a lot of this off.”Swyx [00:54:00]: Any behind-the-scenes on why Salesforce let Heroku stagnate?Jake [00:54:05]: I can only guess. It's hard when it's not your business. Salesforce's business is to build a great CRM. That's their focus. Then you acquire a compute business as an offshoot. A lot of early Meta people talk about focus. Boz has a write-up about how in the early days of Meta they had no money, so they were forced to focus. Then they turned on the money tree and had no reason not to split their focus.Jake [00:54:52]: But that dilutes your product. You get offshoots where you ask, “Is this the focus of the business?” If it's not core, it languishes. A lot of companies get in trouble when they split focus because they're fighting a multi-front war, not just externally but internally for alignment. Where are we going? What are we doing? What is our purpose?Jake [00:55:24]: If you're Salesforce-built and mission-driven, you want to work on Salesforce. Heroku is off to the side. It's not core to the business. Getting resources, budget, focus, and alignment internally becomes hard. It was a matter of time.Swyx [00:56:06]: Kudos for them to call it out instead of leaving it unknown.Jake [00:56:12]: Their release was a little odd. They called it out, but they didn't say they were shutting it down. Behind the scenes, I think they issued messages to people saying they should close accounts and that they were going to deprecate and remove things over time.Jake [00:56:30]: It's crazy because some of my first deployment experiences were on Heroku. You start with dragging things into an FTP server, then you try to get a deploy working, and then it's Heroku. It was the on-ramp for us. But the wheel turns. New things emerge. We're happy to carry the torch for a lot of that. But we don't want to be the new Heroku. We want to be the way people build and deploy software, and ultimately the way people monetize software over time.Swyx [00:57:19]: It's still a big crown to be the new Heroku. There are 50 companies that fought for that.Jake [00:57:23]: Everybody is holding some portion of it. We're happy to support people and companies. The platform works differently. The game loop is similar, but we've been dogmatic about where these things are going: primitives, agents, fan-out. Some things fit; some workflows need to change. We have an approximation of Heroku pipelines with the environment system. It's exciting. We've got a ton of people we can support, and it's growing a lot.Temporal, Workflow Engines, and State MachinesSwyx [00:58:12]: I have one more technical question about Temporal. I've sold my shares. You're a power user and one of our earliest customers. I met you through Temporal. You built on Temporal. You have complaints. This may be the most neutral and informed conversation anyone will hear about Temporal without someone working at the company.Jake [00:58:39]: That's fair. I've used Temporal for almost 10 years because of Cadence at Uber.Swyx [00:58:52]: Give people a sense of what Cadence was at Uber.Jake [00:58:57]: Cadence was the precursor to Temporal. It powers trip actions, rides, when you rent a Jump bike or scooter or car. You're running workflows for a period of time and saying, “This ride will run indefinitely until it finishes.” You attach information: you paused in this zone, so add this charge to the bill. When you end the trip, the workflow is done. That experience was powered by Cadence at the time.Swyx [00:59:34]: I used to say it's like programming the entire user journey top-down as one function.Jake [00:59:39]: It's a powerful idea and important. It's also important for the next phase of the agentic journey. You want an agent to do a specific task, be complete or incomplete on that task, and move on to the next thing. You need a way to manage workflows dynamically.Jake [00:59:59]: Temporal was always great in theory, and great when you got it working the way you wanted in production. But it required you to model the entire journey in your head. If you didn't, you could cause issues where replaying the state of the workflow causes non-determinism.Swyx [01:00:25]: Because it works on deterministic workflow history.Jake [01:00:28]: Exactly. I describe it as a jet engine. If you know how to operate it and run it, it's great. But you can't hand it to people trying to build complicated things if they don't have the whole state in their head.Jake [01:00:48]: We run our whole deployment pipeline on top of it. That's a reasonably complicated workflow: pre-commit hooks, signaling, queuing, and all the rest. We ran into the same thing at Uber. As you express a large workflow, it gets more complicated, with more states in the state machine that you have to map back to the workflow.Swyx [01:01:15]: It's a lot of ifs.Jake [01:01:16]: Exactly. At Uber, we built a system for doing the state machine and testing it. We've started to build some of those things here because it's grown heavily. It's not quite love-hate. When it works well, it works super well. But if someone who doesn't have full context puts something into the system that invalidates state or causes non-determinism, or spins off a ton of activities, you have to keep track of underlying SRE knobs like activity slots. Those should scale with memory, vCPU, and so on. It becomes a bear to scale.Swyx [01:02:10]: You need a capable sysadmin running things behind the scenes. If you moved off, what would you do?Jake [01:02:19]: We'd build our own workflow engine. We have a few internally that we've worked on.Swyx [01:02:27]: This is one of those classes of things you typically wouldn't vibe code, but I'm wondering if you can.Jake [01:02:33]: I still don't think you should vibe code it. You still want to run decent tests to make sure it works.Swyx [01:02:39]: Timo didn't invent that from scratch either. There are libraries you can run. On top of that, it's just a state machine that you have to map out. Ultimately, you define the instructions you want and run them through a state machine.Jake [01:03:00]: It's very doable. Workflow stuff is interesting. Restate is doing neat stuff here.Swyx [01:03:10]: You're tied into JavaScript. Are you a JavaScript maxi?Jake [01:03:13]: Internally, we have TypeScript, Rust, and Go. We don't add more languages. Actually, we have a little C because we write BPF code and hooks. But those are the languages.Swyx [01:03:28]: Is this for sidecars?Jake [01:03:32]: No. It's for the networking stack, volumes, and things like that. We use TypeScript a lot because it powers the dashboard, but we're moving a lot of workflow stuff off the dashboard stack and into the infrastructure stack.Railpack, Nixpacks, and Content-Addressable FilesystemsSwyx [01:04:00]: Cool. Any other technical infrastructure stuff? Railpacks?Jake [01:04:07]: We built an engine for determining dependencies based on source code. It's called Railpack. We built the first version, Nixpacks, on top of Nix, and then we moved.Swyx [01:04:17]: People have been trying to get me to adopt Nix and NixOS for four years. Is it ever going to be a thing?Jake [01:04:23]: I don't know. We're excited about it, but it has pain points. Think of it as a stack of versioned binaries at specific slices in time. If you want version X and version Y, you bloat the package space, which blows up image size and makes real-world workloads difficult.Swyx [01:04:53]: But you content-address it and cache it. In theory, there are optimizations.Jake [01:05:00]: In theory, yes. But with a large enough user base and disparate enough machines, you run into a problem Meta described in the XFAAS paper, their internal serverless system. It becomes difficult at scale unless you break out specific runtimes.Jake [01:05:24]: We didn't want to do that because we wanted to truly allow you to deploy anything. That was our initial thing with Nix. But we've moved toward interesting work around content-addressable file systems that can lazy-load anything from any point and page it into memory.Swyx [01:05:48]: Amazing.Jake [01:05:49]: The future is very bright. It's crazy, and it's going to be nuts.Coding Agent Spend, Roadmaps, and Token ROISwyx [01:05:54]: Founder journey stuff?Alessio [01:05:56]: Your cloud usage: you tweeted you're going to spend $300K this month?Jake [01:06:01]: I think we got to $200K.Alessio [01:06:02]: Coding agents?Jake [01:06:03]: Yeah.Swyx [01:06:04]: Across the company?Alessio [01:06:05]: You only have 35 people, so I'm sure they're not all spending $10K a month. What's the distribution?Jake [01:06:10]: I think I'm at about $25K. We have power users all the way down. We came back from winter break, and I basically said, “If you're writing code by hand, you're doing this wrong.” The tools are good enough now that you can move extremely quickly. There are issues and pain points, but you should be reviewing the code you are writing instead of writing it by hand.Jake [01:06:40]: Architectural patterns matter more now than ever, but you shouldn't spend your time generating code you would write. If you know how to write it, ask the agent to write it and reconcile it until it looks like you would have written it yourself.Jake [01:06:58]: People misconstrue my propensity to push people toward agents as connected to our growth and some reliability bumps. They're not necessarily related. The tools are good enough to move extremely quickly and build things way larger than you could before.Jake [01:07:19]: To the earlier point about cooling data centers in space: I don't know. But with software, you can ask, “How would I build block storage from scratch? How would I do these things?” I have ideas because I have history and have read papers. Let me work them out and build massive test benches with thousands of tests, because those are now free to author. If you're not using AI systems to speed-run your roadmap and reconcile your existing system onto the future, you're missing a large point of what's happening.Alessio [01:08:12]: What's the path to spending $3 million a month? Is it bound by ideas and things customers can absorb?Jake [01:08:19]: For most companies, it's bound by deployment at this point. That's why we've seen a massive boom in users and companies, from Fortune 50s down, asking how to get developers to move faster. You'll probably hit your CFO before any technical limits because they'll look at the eye-watering amount of money spent on tokens. Inference costs have to come down, but we're inference constrained now. There will be price discovery around what makes sense for an org to adopt.Jake [01:09:06]: I think you'll end up with the F1 driver concept. If someone is really adept at these things, it makes sense to put them in a $3 million car. If they're not, it probably doesn't make sense. You'll take a few people and say, “You can drive the F1 car. We need to go in this direction. Figure out if it works and prototype it.”Jake [01:09:33]: We've done some of that and vastly accelerated our roadmap. We thought we'd ship something in a few years; now we can probably ship it in a few months because we validated it and don't have to build it incrementally. We can skip steps and move toward our vision.Alessio [01:09:58]: A lot of people are realizing the roadmap doesn't always have a business impact, so they say tokens are too expensive. But if your roadmap were built to make more money by the time you built it, you'd have token pricing for it, the same way you do with sales. You'd spend a billion dollars on sales if you knew you would get $2 billion of revenue.Jake [01:10:19]: Exactly. A naive way to measure this is the percentage of tokens that end up in production. If you can measure impact because those tokens end up in production, that's awesome. But the burden of proof will rise. Internally, we have a growing number of pull requests that haven't merged. The question becomes: how do you get this into production? It's about how quickly you can build and deploy software, which is exciting because that's our whole thing.The SDLC Shift: Prompt Requests, Feature Flags, and Safe RolloutsSwyx [01:10:56]: The SDLC is changing. One thesis is that the pull request is dying. It's going to be the prompt request. Beyond that, code review is also kind of dying if you have all the other systems in place. What else is changing about the SDLC?Jake [01:11:19]: The AISRE and the tools to make it happen. AISRE is pie-in-the-sky aspirational. What does it take to get an AISRE? What tools do you need to build?Swyx [01:11:32]: You should expose your tooling to customers at some point. The Central Station command center.Jake [01:11:39]: We have it for template maintainers. Template maintainers can deploy and maintain templates, and they get feedback. We're going to expose those things incrementally.Swyx [01:11:51]: Clustering around incidents. Everyone has a version of that, but I don't think anyone has solved it.Jake [01:11:56]: I won't say we've solved it internally, but it's gotten so good that we can see incidents forming pretty quickly. At some point, those will be things either someone else builds or we build. We've always built things purpose-built for us. If it makes sense to make it useful for users, monetize it, or turn that loop into a profit center instead of a cost center, we want to do that.Jake [01:12:28]: Pull request is definitely dying.Swyx [01:12:29]: Do you do first-party feature flagging and incremental rollout stuff?Jake [01:12:34]: We have a feature-flagging engine we built internally and will eventually roll out.Swyx [01:12:38]: I don't see it as a user. How come you didn't give us what you have?Jake [01:12:43]: We have to beta test it. We care a lot about the quality of the things. There's plenty we've used internally that doesn't make it all the way through the journey because it fails. It works for one service but not multiple services. We'd have to build it for multiple services and know that if we released it, we'd rebuild it again and again. Some things are worth that, but many inform the roadmap.Jake [01:13:18]: We don't want to dilute the experience by saying, “This works, but only for this service,” unless it's a core initiative. Over the next few months, we'll roll out things that work for a single service, then multiple services, then multiple services across the environment. You have to be deliberate. Otherwise you create broken disparate experiences and support load because people ask how to use the feature.Jake [01:13:52]: It's the earlier expansion and compaction pattern. You expand the company to get features, then compact and smooth them out so the experience is stellar. You told me in the hallway, “It's gotten so much better.” Internally we're saying, “This part really sucks. We need to make it significantly better.”Swyx [01:14:11]: I can attest to that over the last three years watching you build Railway. For listeners, feature flagging is a huge part of Uber culture. So much so that they have too many feature flags and another thing to remove feature flags. Facebook has Gatekeeper. Agents are going to need this. It's fundamental to incremental rollouts. OpenAI acquired Statsig. GPT-5 is routing and flagging through different models.Jake [01:14:56]: It's super important. If the software development lifecycle is going to change because we're doing things 1,000 times faster and 1,000 times more concurrently, what becomes important at scale?Jake [01:15:16]: Before I started Railway, I built a feature-flagging product and tried to sell it. It was an easier version of LaunchDarkly. I ran into a problem: anyone small enough to adopt your technology doesn't care about feature flags, and anyone large enough to need feature flags needs so much scale that you have to build out all the infrastructure. I scrapped it.Jake [01:15:42]: But what is old is new again. Companies are trying to move quickly, but you can't YOLO a vibe-coded thing straight into production. You need to say, “Here's my blast radius, my impact, and I want to shadow it for these users.” Feature flags. You're going to need the tools larger companies built to maintain their structures. Everything gets compressed by 1,000x so everybody can build those structures quickly.Jake [01:16:07]: That's exactly where we are: compressing the software development lifecycle, then expanding it and adding more new things.Cattle, Pets, and Clonable InfrastructureSwyx [01:16:15]: Another term that comes to mind for newer developers is “cattle, not pets.” People treat production like a pet. It has a name. You baby it and keep it alive. With cattle, you can mass farm, roll out, portion parts out, and kill them.Jake [01:16:37]: I think that might change. You can move toward having pets as long as you have a cloning machine for your pets.Swyx [01:16:52]: Yeah.Jake [01:16:52]: If you can snapshot every single thing at every frame, it doesn't matter if something gets obliterated because you have a snapshot of it. The things we've built right now are designed to block changes from the hermetically sealed DevOps line. You have to write a Dockerfile because you nee

On this week's pod: Game segment:Let's add in even more stupidity while we wrap up the season...Shout outs:Birthday wishesRFC charity game NARSA business:Destination NARSA - Nashville 2026 - 23 days / 3 weeksFriday night is a western themeDavie Cooper Memorial Topgolf Tournament now on sale - https://narsa.ca/tickets/ - PLEASE BOOK THIS WEEKRFC Executive Director, Fraser Thornton and RFC CEO, Jim Gillespie, and Greg Marshall are joining us at NARSA 2026!!!RFC 9-in-a-row legends: Derek Ferguson, Scott Nisbet, David Robertson, and Mark WaltersRFC Historian: David MasonEntertainment: MC David Edgar, Stuart Hay, Rebecca Auchterlonie, DJ Angry Bear, and Danny Magic!TICKETS NOW ON SALE: $199 USD | NARSA 2026 NashvilleHotel: Cambria Hotel Nashville Midtown | Booking: https://www.choicehotels.com/reservations/groups/OI25P7Phoning: +1 615-931-0777 (NARSA is the keyword)Room rate: $199 + Taxes & Fees | Room rate available 3-days prior and 3-days postCommunications:Gers Guide Women's team thump that mob and take it to the last dayAndrew Cavenagh's communications campaign from yesterdayInstagram and TikTok - follow us at narsacomms#NARSA #RangersFC #WeeklyUpdatehttps://narsa.ca/

【プロモーション：コインチェック株式会社】2026/5/31までの期間限定！対象者全員に最大で2500円分のビットコインをプレゼントキャンペーン参加はこちらから：https://coincheck.com/ja/cp_lp/yurupc202605?utm_source=podcast暗号技術が破られるとはどういうことか？ ハッシュ関数を例にして、直観的に説明しました。【目次】0:00 暗号技術は死んでいく5:54 ハッシュ関数って何？10:30 ハッシュ値を計算してみよう15:12 ハッシュ関数をハックしよう19:37 ハッシュはどこで使われている？23:41 業界を震撼させた無名の女性25:06 Web全部を揺るがす脆弱性29:52 日々進化し続ける暗号技術34:44 コインチェックとタイアップキャンペーン【参考文献】◯CRYPTO 2004 ( https://www.iacr.org/conferences/crypto2004/ )→国際学会 CRYPTOの詳細はこちらから。◯CITP Blog「Report from Crypto 2004」( https://blog.citp.princeton.edu/2004/08/18/report-crypto-2004/ )→ スタンディングオベーションが起きた話はここから。◯Collisions for Hash Functions MD4, MD5, HAVAL-128 and RIPEMD ( https://eprint.iacr.org/2004/199.pdf )→ 王小雲が2004年のCRYPTOで発表したもの。◯Flame malware collision attack explained ( https://www.microsoft.com/en-us/msrc/blog/2012/06/flame-malware-collision-attack-explained/ )→ Flameについての詳細情報◯RFC 1321「The MD5 Message-Digest Algorithm」( https://www.ietf.org/rfc/rfc1321.txt )→ MD5の仕様、MD4の後継であること◯Online Etymology Dictionary「hash」 https://www.etymonline.com/word/hash→ hashの語源◯ Washington Post「U.S., Israel developed Flame computer virus」( https://www.washingtonpost.com/world/national-security/us-israel-developed-computer-virus-to-slow-iranian-nuclear-efforts-officials-say/2012/06/19/gJQA6xBPoV_story.html )→ Flameが米国・イスラエルの合同でイラン攻撃用に開発された◯NIST「NIST Selects Winner of Secure Hash Algorithm (SHA-3) Competition」( https://www.nist.gov/news-events/news/2012/10/nist-selects-winner-secure-hash-algorithm-sha-3-competition )→ SHA-3について◯現代経済学の直観的方法（バリューブックス）→ https://www.valuebooks.jp/bp/VS0057255792（Amazon）→ https://amzn.to/42toyqQ【サポーターコミュニティへの加入はこちらから！】⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://yurugengo.com/support⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠【親チャンネル：ゆる言語学ラジオ】⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.youtube.com/@yurugengo⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠【実店舗プロジェクト：ゆる学徒カフェ】⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.youtube.com/@yurugakuto⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠【お仕事依頼はこちら！】info@pedantic.jp【堀元見プロフィール】慶應義塾大学理工学部卒。専攻は情報工学。理屈っぽいコンテンツを作り散らかすことで生計を立てている。Twitter→⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/kenhori2⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠noteマガジン→⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://note.com/kenhori2/m/m125fc4524aca⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠個人YouTube→⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.youtube.com/@kenHorimoto⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠【水野太貴プロフィール】1995年生まれ。愛知県出身。名古屋大学文学部卒。専攻は言語学。本業は雑誌編集者。著書に『会話の0.2秒を言語学する 』（新潮社）などがある。Podcast「神保町で会いましょう」のパーソナリティも務める。Twitter→⁠⁠⁠⁠⁠⁠⁠⁠⁠https://x.com/yuru_mizuno⁠⁠⁠⁠⁠⁠⁠⁠⁠神保町で会いましょう→⁠⁠⁠⁠⁠⁠⁠⁠⁠https://open.spotify.com/show/6cYkvDO0HnJKLPgDBGUjjS

Hello everyone, and welcome to another episode of the Performance Psychcast. Today we are very fortunate to be speaking with returning guests, Jenny Coe and Amy Whitehead.  Amy is a Reader in Sport Psychology and Coaching and teaches across the Sport Coaching, Physical Education and Sport Psychology programmes at Liverpool John Moores University. Amy is a BPS accredited sport and exercise psychologist and has worked for organisations such as St. Helen's RFC, British Cycling, the FA, the Professional league and non-league football and European Tour Golfers.  Jenny has been involved with elite sport for most of her life, having played as a guard in basketball for Ireland and WIT Wildcats before joining UK Coaching in 2018, where she supported coaches across multiple high-performance Olympic sports on their respective journeys. Currently one of her roles is in the FA, titled, Senior Lead Workforce Development.  Jenny and Amy have edited the book called 'Women working in Sport." It offers a fresh, unapologetic lens on these challenges and moves decisively toward solutions. Through the voices of coaches, psychologists, administrators, academics and directors, this book sheds light on what's holding women back and more importantly, how we move forward. Book: https://www.sequoia-books.com/product/women-in-sport/  Jenny: https://x.com/jennycoady10?s=21&t=PzxOOVXwQNXq8vmIVQ_W3w Amy: https://x.com/a_whitehead1?s=21&t=PzxOOVXwQNXq8vmIVQ_W3w www.arcope.co.uk  www.focuperform.co.uk  #focusperform #arcope #performance #sport #psychology 

On this week's pod: Game segment:3rd it is...Shout outs:RFC player of the year awardsThank you Captain James Tavernier NARSA business:Destination NARSA - Nashville 2026 - 30 days / 4 weeksFriday night is a western themeDavie Cooper Memorial Topgolf Tournament now on sale - https://narsa.ca/tickets/ - PLEASE BOOK THIS WEEKRFC Executive Director, Fraser Thornton and RFC CEO, Jim Gillespie, and Greg Marshall are joining us at NARSA 2026!!!RFC 9-in-a-row legends: Derek Ferguson, Scott Nisbet, David Robertson, and Mark WaltersRFC Historian: David MasonEntertainment: MC David Edgar, Stuart Hay, Rebecca Auchterlonie, DJ Angry Bear, and Danny Magic!TICKETS NOW ON SALE: $199 USD | NARSA 2026 NashvilleHotel: Cambria Hotel Nashville Midtown | Booking: https://www.choicehotels.com/reservations/groups/OI25P7Phoning: +1 615-931-0777 (NARSA is the keyword)Room rate: $199 + Taxes & Fees | Room rate available 3-days prior and 3-days postCommunications:Gers Guide - why notWomen's team maybe going down to the final day...?Instagram and TikTok - follow us at narsacomms#NARSA #RangersFC #WeeklyUpdatehttps://narsa.ca/

PHP Podcast – May 7, 2026 Hosts: Eric Van Johnson & John Congdon Another fun episode of the PHP Podcast! Here’s what we covered: PHP Tek Is 11 Days Away — And Everyone Is Stressed The conference countdown is real: 11 days, 10 hours, and a handful of seconds on the clock. John’s travel plans hinge entirely on little league baseball — if his team wins their Tuesday playoff game, he coaches the Saturday game, then bolts for the airport. If they lose Tuesday, he’s sad but gets to Chicago earlier. Meanwhile, Eric is grinding through the PHP Tek TV redesign, trying to wire up the SessionIze API for schedule imports instead of doing it all manually from a CSV, and sending the design team a novel’s worth of badge and signage requests. Holly’s conference app now has notifications working: select a talk, and if Eric or John move it around, you’ll get pinged. Keynote and lunch notifications are also on the table for attendees who can never find the room. Conference Stress Dreams: The Motorcycle Gunman Edition John woke up mid-dream to his wife opening the blinds for the school run — and the dream he was pulled from was genuinely unhinged. He was in an Uber waiting for Uber Eats to arrive at an intersection when a motorcyclist pulled up behind them, got off, shot out the tire, then came to John’s door and started shooting at the lock to get in. The Uber app had briefly flashed the word “threat” on the map. John laid the seat back as far as it would go. The driver just stood there. Then the blinds opened and it was just a Thursday morning. John’s verdict: it’s conference stress. Hard to argue with that. JS Tek — An Honest Conversation John decided to say the quiet part out loud: JS Tek hasn’t brought in the JavaScript community the way they hoped. The PHP world is unusual in paying for speaker travel and hotel rooms; Joe in Discord confirmed this barely happens outside PHP, and somebody speaking at a Ruby/Rails conference once told Eric they not only weren’t reimbursed for travel — they had to buy their own conference ticket. Eric’s takeaway: the JS track itself is a great idea for PHP developers, but trying to recruit an entirely new community into the fold didn’t work out. Next year’s structure will probably look different. The PHP 7-to-8 Upgrade That Failed Three Times Eric’s consulting team has been struggling with a client upgrade from PHP 7 to 8 — unusual, because they’ve done this many times and know the pitfalls. After three failed attempts, a deep dive revealed the culprit: an abandoned Laravel Shift branch left behind by a previous developer who had started an upgrade and walked away, with missing config files baked right into the inherited codebase. The fix wasn’t just another attempt — it was getting the management team to produce a proper testing playbook, and more importantly, actually getting trained on the application. The team had been fixing bugs in code they’d never seen working correctly. Today they finally got that training session, and Eric says the excitement and “ah-ha” moments from his developers made it clear this should have happened much sooner. The Database on the Same Server Problem A related discovery from the same client: the database lives on the same machine as the application. Every upgrade means shutting the app down, exporting the database, migrating it somewhere else, and starting over. Eric’s head doesn’t compute why this is still the case in 2026. Even a second machine designated as a database server would be a massive improvement. In a moment of uncomfortable honesty, Eric also admitted that PHP Architect’s own conference site has the same setup — Forge makes it so easy to throw a database on the same box that you just don’t think about it, until you do. Laravel Shift, Laravel Cloud, and the Pre-Check Tool The conversation circled back to Laravel Shift — JMAC’s automated upgrade tool — which Eric notes has become less essential as Laravel’s upgrade paths have smoothed out considerably compared to the wild west of early Laravel development. But Shift is still out there and still useful. More interestingly, JMAC has a new free Shift specifically for Laravel Cloud readiness: run it against your app and it’ll tell you whether your application is compatible with Laravel Cloud’s serverless model, flag any system commands that won’t be available, and help you understand what services you’d need. Laravel Cloud itself is Taylor’s “don’t worry about servers” deployment platform, and if you’re not a sysops person, having a Shift that holds your hand through the setup could be the difference between trying it and not. PHP Internals Made Readable — Externals and PHP RFC Watch Eric plugged two tools for following what’s happening in PHP core. The first is externals.io — a much more readable front-end for the PHP internals mailing list, with search, read-tracking, and threaded discussions. The second is a newer discovery: php-rfc.watch, which focuses purely on RFCs, showing what’s active, what’s been voted on, and how the votes broke down. It’s more of a quick-glance dashboard than a full discussion forum. Eric also highlighted a specific RFC from Ben Ramsey: a proposal to update the PHP license, accompanied by a detailed blog post called “PHP License Simplified” that walks through the history and rationale. If you’ve ever been curious about why license choice matters (especially at the enterprise level where legal teams block open source based on license type), Ben’s post is worth the read. NeoVim’s Flash Plugin — Used Wrong for Years Eric has been using Flash.nvim, a NeoVim navigation plugin, for years. He recently discovered he had been using it completely incorrectly the entire time. He thought he understood what it did. He did not. A YouTube video explaining the plugin properly (titled something like “How to Jump Anywhere Instantly in NeoVim”) revealed that what he’d been doing was essentially pressing the wrong keybinding and stumbling through a fraction of the plugin’s actual functionality. This sent the conversation into a longer Vim origin story: Eric learned Vim because he was flying around the country installing Cyborg firewalls on remote servers and Vi was just there. John picked it up at an enterprise job and never thought about alternatives until he saw a developer using MacVim to write Rails and had his mind blown. The core message: you can use a tool for decades and still be using it wrong, and that’s okay — but watch the tutorial. Eric Doesn’t Know How Old He Is Eric has been confidently telling people for a full year that he’s 55. His wife Bek has known for some time that this is not correct. The moment of reckoning came when Eric asked Alexa: “If I was born in 1969, how old would I be now?” Alexa hedged on the birthday thing but confirmed the range. Bek stepped in. Alexa, a full 30-60 seconds later, stepped back in and confirmed: “Your birthday’s May 8th, you’re turning 57.” Eric is apparently going directly from 55 to 57, having skipped 56 entirely. He also noted at the Padres game with his wife that their Costco membership is older than a 13-year-old kid they saw on the Jumbotron, and that it could legally babysit him. John is turning 50 this year. Everyone is fine. Links from the show: externals.io — PHP Internals Discussion Reader PHP RFC Watch — Track Active PHP RFCs Ben Ramsey: PHP License Simplified Laravel Shift — Automated Laravel Upgrade Tool Laravel Cloud How to Jump Anywhere Instantly in NeoVim (Flash.nvim Tutorial) PHP Tek 2026 — Chicago PHP Architect Store PHP Architect Discord Host: Eric Van Johnson X: @shocm Mastodon: @eric@phparch.social Bluesky: @ericvanjohnson.bsky.social PHPArch.me: @eric John Congdon X: @johncongdon Mastodon: @john@phparch.social Bluesky: @johncongdon.bsky.social PHPArch.me: @john Streams: Youtube Channel Twitch Connect & Hire PHP Architect Website Twitter/X Mastodon Hire PHP Developers Looking to hire PHP developers? Email support@phparch.com – Joe and the team are available for consulting, infrastructure work, Ansible playbooks, and code review. Partner This podcast is made a little better thanks to our partners Displace Infrastructure Management, Simplified Automate Kubernetes deployments across any cloud provider or bare metal with a single command. Deploy, manage, and scale your infrastructure with ease. https://displace.tech/ PHPScore Put Your Technical Debt on Autopay with PHPScore CodeRabbit Cut code review time & bugs in half instantly with CodeRabbit. Music Provided by Epidemic Sound https://www.epidemicsound.com/ Join Us Live Next Week Youtube Channel Got feedback? Join us on Discord at discord.phparch.com The post The PHP Podcast 2026.05.07 appeared first on PHP Architect.

On this week's pod: That'll be that thenGame segment:The final nail...Shout outs:Happy birthdaysHappy anniversary Stevie GNARSA business:Destination NARSA - Nashville 2026 - 37 days / 5 weeksFriday night is a western themeDavie Cooper Memorial Topgolf Tournament now on sale - https://narsa.ca/tickets/ - PLEASE BOOK THIS WEEKRFC Executive Director, Fraser Thornton and RFC CEO, Jim Gillespie, and Greg Marshall are joining us at NARSA 2026!!!RFC 9-in-a-row legends: Derek Ferguson, Scott Nisbet, David Robertson, and Mark WaltersRFC Historian: David MasonEntertainment: MC David Edgar, Stuart Hay, Rebecca Auchterlonie, and DJ Angry BearTICKETS NOW ON SALE: $199 USD | NARSA 2026 NashvilleHotel: Cambria Hotel Nashville Midtown | Booking: https://www.choicehotels.com/reservations/groups/OI25P7Phoning: +1 615-931-0777 (NARSA is the keyword)Room rate: $199 + Taxes & Fees | Room rate available 3-days prior and 3-days postCommunications:Gers Guide - nopeWomen's team had a solid weekRFC response to SPFL nonsenseInstagram and TikTok - follow us at narsacomms#NARSA #RangersFC #WeeklyUpdatehttps://narsa.ca/

Hasbro dropped Studio Series 86 Cyclonus, Blitzwing, and Cliffjumper at CCXP — and the RFC crew has some feelings. Cyclonus gets new legs and a new head and basically earns unanimous approval. Cliffjumper... does not. Plus Iron Studios' $350 Soundwave statue, a massive New Age Junkion wave, Brian's surprise acquisition, and what should happen at episode 1,000? The post Radio Free Cybertron 985 – Studio Series 86 Cyclonus, Blitzwing, and Cliffjumper Revealed at CCXP appeared first on Radio Free Cybertron.

Hasbro dropped Studio Series 86 Cyclonus, Blitzwing, and Cliffjumper at CCXP — and the RFC crew has some feelings. Cyclonus gets new legs and a new head and basically earns unanimous approval. Cliffjumper... does not. Plus Iron Studios' $350 Soundwave statue, a massive New Age Junkion wave, Brian's surprise acquisition, and what should happen at episode 1,000? The post Radio Free Cybertron 985 – Studio Series 86 Cyclonus, Blitzwing, and Cliffjumper Revealed at CCXP appeared first on Radio Free Cybertron.

Shareholder Advocacy in 2026: A Season Defined by Upheaval and Resilience *A deeper look at the key themes and proposals in the Proxy Preview 2026 report by As You Sow and Proxy Impact* The 2026 proxy season is arriving amid one of the most turbulent regulatory environments shareholder advocates have faced in decades. Actions by the Securities and Exchange Commission (SEC) under Chair Paul Atkins have introduced a series of new barriers to shareholder participation — limiting who can file resolutions, restricting exempt solicitations on EDGAR, and signaling a broader retreat from the corporate disclosure requirements that have defined the modern era of investor oversight. Filing thresholds have been quietly tightened. The procedural goalposts have moved. And the agency that once served as a neutral referee on what does and does not belong on a proxy ballot has, in practice, stepped off the field. And yet, shareholders are not retreating. As Proxy Preview publisher Andrew Behar puts it, they are “standing shoulder to shoulder” — the early warning system that corporations have long relied on, whether they admit it or not. The proposals filed this year are, if anything, more ambitious than in seasons past. Investors are not waiting to see how the regulatory landscape settles. They are filing, litigating, and engaging on the assumption that the right to ask questions about material risk is theirs to exercise regardless of who chairs the SEC. This year’s Proxy Preview, produced by As You Sow and Proxy Impact, offers a sweeping look at the environmental, social, and governance (ESG) proposals headed to shareholder votes in 2026. The themes range from the data center buildout reshaping America’s electricity grid, to the legal liabilities mounting against Big Tech, to the quiet but consequential question of who gets to decide what counts as “proper business” at an annual meeting. Here’s what investors need to know. The Political and Legal Backdrop The story of the 2026 season cannot be told without first addressing what happened to the SEC’s no-action process. Historically, when a company wanted to exclude a shareholder proposal from its proxy statement, it would file a no-action request with the SEC, which would review the proposal on its merits and issue guidance. That process — imperfect but functional — was effectively suspended this year, triggered in part by a prolonged government shutdown that left the agency without the bandwidth to render decisions. The result was a free-for-all. Companies, sensing an opening, filed notices of intent to exclude proposals on a range of novel theories. The most aggressive of these was the so-called “Delaware Proper Business” argument, which holds that advisory shareholder proposals — the non-binding resolutions that have been the backbone of shareholder advocacy for decades — are not “proper business” for an annual meeting under Delaware corporate law. If accepted, that theory would effectively wipe out the entire category. Shareholders pushed back, hard. Lawsuits were filed against AT&T, Axon, Chubb, BJ’s Wholesale, and PepsiCo. AT&T and Pepsi settled quickly, restoring the proposals to their proxies. At Axon, a federal court ordered the parties to explore a negotiated resolution rather than rule on the merits — a signal that judges are skeptical of the broad exclusion theories companies have been advancing. The Chubb and BJ’s cases remain in active litigation as of this writing. Meanwhile, in a parallel front, a federal court struck down Texas Senate Bill 13 — the state’s anti-ESG law that restricted public pension funds from doing business with financial firms deemed to “boycott” fossil fuel companies — as unconstitutionally overbroad and vague. It is the first federal court decision to invalidate this type of statute, and it sets up a potential precedent that could unwind similar laws in roughly a dozen other states. The pattern, taken together, is clear. Where companies and state legislatures have tried to use procedural and legal tools to silence shareholder voice, the courts have so far been unwilling to go along. Climate: Data Centers, Stranded Assets, and Insurance If there is one new climate story dominating the 2026 season, it is the AI buildout. The numbers are striking. In 2025, the number of proposed fossil gas plants in the U.S. nearly tripled, driven almost entirely by soaring electricity demand from new data centers. Utilities that had been quietly retiring coal and gas capacity are now reversing course, citing grid commitments to hyperscale tech customers as the rationale. Investors are responding. Proposals at Amazon, Meta, and Alphabet request disclosure on how the companies’ growing data center operations are compatible with their previously announced climate commitments — many of which include net-zero pledges that look increasingly difficult to reconcile with multi-gigawatt computing expansion. Similar proposals target the utility side of the equation, including Dominion Energy and Southern Company, both of which are major suppliers to data center hubs in Virginia and Georgia. At the same time, the U.S. is in the middle of a climate-driven insurance crisis that is starting to attract serious investor attention. Insured natural-catastrophe losses reached $117 billion in 2024 — more than double the ten-year average. Homeowners insurance premiums rose 24% between 2021 and 2024, and entire ZIP codes in California, Florida, and Louisiana have effectively become uninsurable on the private market. As You Sow has filed a novel “subrogation” proposal at Chubb, asking the insurer to explore using subrogation claims against large emitters to offset climate-related losses. The legal theory borrows from the playbook used against tobacco and opioid manufacturers: if you can identify the parties whose conduct caused the harm, you can pursue them for the cost of paying out claims. Climate transition planning remains a critical investor concern more broadly. Proposals at Harley-Davidson and Verizon push these companies — both of which have ambitious net-zero commitments but published no sustainability reports in 2025 — to develop credible, stand-alone transition plans. The implicit argument is that a target without a plan is not a commitment; it is a press release. Biodiversity: Horseshoe Crabs and Avocado Supply Chains Two of the most distinctive proposals this season concern biodiversity, and both illustrate how shareholder advocacy can move industries that regulators have not. The pharmaceutical industry’s dependence on horseshoe crab blood for drug safety testing is under fresh scrutiny. The compound extracted from the crabs — limulus amebocyte lysate, or LAL — is used to detect bacterial endotoxins in injectable drugs and implantable medical devices. Each year, roughly 1.1 million horseshoe crabs are harvested and bled, with the industry historically claiming low post-bleeding mortality. Independent research suggests the actual mortality rate is closer to 30%, with knock-on effects for shorebirds and other species that depend on horseshoe crab eggs as a food source. Synthetic alternatives — recombinant Factor C, or rFC — have been commercially available since 2003 and are used routinely by Eli Lilly and others. The U.S. Pharmacopeia, the standards body that governs pharmaceutical testing in the U.S., updated its standards in November 2024 to place rFC on equal regulatory footing with the animal-derived test. That removes the last meaningful technical barrier to transition. Proposals at Abbott and Merck request disclosure about transition timelines. The avocado story is, in some ways, a more hopeful one — a case study in what sustained shareholder engagement can accomplish over time. Mexican avocado production has long been linked to illegal deforestation, with growers clearing protected forest in Michoacán to plant new orchards. As You Sow’s decade-long push for Pro Forest Avocado (PFA) certification — a satellite-based system that monitors orchards in real time for evidence of land-use change — has transformed the supply chain. As of March 2026, over 60 Mexican avocado packers are PFA-certified, and major U.S. retailers including Costco, Walmart, and Kroger have committed to sourcing from certified suppliers. The notable holdout is Albertsons, which has not responded to repeated engagement requests and is the focus of a 2026 proposal. Social: Human Rights, Surveillance, and Child Safety Big Tech is facing what Michael Passoff of Proxy Impact calls its “Big Tobacco moment” — the period when accumulating evidence of harm crosses the threshold from controversial to legally actionable, and the financial consequences begin to compound. The numbers from the past twelve months are difficult to dismiss. In March 2026, Meta was found guilty of violating New Mexico’s consumer protection law and penalized $375 million for its handling of minors on Instagram. Separately, a California court found Meta and Google guilty of creating addictive platform designs that harm young users’ mental health, in a verdict that is likely to be the template for similar cases in other states. Meta’s stock dropped 8% following the verdicts, suggesting the market is finally beginning to price in legal risk that shareholders have been flagging for years. On surveillance, investors at Alphabet/Google and Home Depot are pressing for oversight of customer and user data. The specific concerns are concrete. Home Depot cameras installed in parking lots have, according to public reporting, enabled ICE raids targeting day laborers. Google was hit with a $425.7 million verdict for tracking 98 million users after they had explicitly turned location tracking off. In both cases, the proposals ask not for the companies to change their business models, but for the boards to take responsibility for the data practices their products create. New this year, and likely to attract significant attention: a proposal at Palantir asking the company to conduct a Human Rights Impact Assessment related to its products and services. The proposal follows reports that Palantir’s software is being used by ICE to track and target migrants, including in operations that have separated families and detained individuals without prior criminal records. Palantir has historically resisted human rights disclosure on the grounds that its government contracts are confidential; the proposal tests whether shareholders can compel disclosure of the broader policy framework even when specific contract terms remain under seal. Political Spending and Lobbying Corporate political spending is under heightened scrutiny as the 2026 midterm elections approach. The Center for Political Accountability (CPA), which has been the leading shareholder voice on this issue for two decades, filed disclosure proposals at 29 companies this proxy season. The proposals ask for disclosure of corporate political contributions, including those made to trade associations and other intermediaries that often serve as a workaround for direct disclosure requirements. What is striking is the response. Despite the SEC’s effective invitation to exclude most shareholder proposals this year, only 7 of the 29 companies chose to do so. The other 22 let the proposals proceed to a vote — a tacit acknowledgment that the political risk of being seen to suppress shareholder voice on political spending now outweighs the cost of disclosure. The CPA proposal averaged 41.4% support over 13 votes in 2025, including five majority votes, putting it well above the threshold at which boards typically engage seriously with proponents. The lobbying disclosure campaign also continues, though with a revised proposal structure following a 2025 setback when the SEC sided with Air Products and Chemicals on a technical exclusion argument. The new, streamlined proposal — focused on direct federal and state lobbying amounts and third-party recipients — is being filed at 7 companies including Goldman Sachs, J.P. Morgan Chase, and Morgan Stanley. The narrower scope is designed to be procedurally bulletproof, leaving the substantive question — should a public company tell its owners how much it spends to influence legislation — on the table for shareholders to answer. Governance: Board Accountability and Executive Pay Several governance proposals this season cut to the question of what boards are actually responsible for. Shareholders are requesting that boards provide specific oversight of AI development, climate change, Indigenous peoples’ rights, and data protection — areas where the gap between executive decision-making and board supervision has become particularly wide. A notable Vote No campaign: NYC Pension Funds, the third-largest public pension system in the country, urged Starbucks shareholders to vote against the re-election of two directors, citing over 700 unfair labor practice charges, 60 adverse administrative law decisions, and the quiet disbanding of a labor relations oversight committee that had been formed in response to earlier shareholder pressure. The campaign is significant not only for its scale but for the specificity of its case: this is not a general grievance about management, but a documented record of regulatory findings the directors are charged with overseeing. A new executive compensation proposal at Meta links CEO and executive bonuses to improvements in child safety metrics — a direct response to the company’s mounting legal liability over platform harms to minors. The proposal is structurally interesting because it does not ask the company to take any specific action; it asks only that the compensation committee tie pay to outcomes the company itself has acknowledged as material. If child safety is, as Meta has repeatedly stated in public, a top priority, then linking executive pay to it should be uncontroversial. The vote will reveal whether the board agrees. The Bottom Line The 2026 proxy season is, more than anything, a test of whether shareholders can maintain their voice in corporate governance amid a hostile regulatory environment. The evidence so far is encouraging. When companies have tried to unilaterally exclude proposals, they have largely faced legal challenges and backed down. When state legislatures have tried to penalize ESG-aligned investing, federal courts have intervened. When boards have tried to ignore mounting legal liability, the markets have begun to do the disciplining themselves. As shareholder advocate Nell Minow writes, the likely cost-benefit analysis from executives “who thought they could keep the proposals from going to a shareholder vote was not clear to them until they faced the very real possibility that a court ruling on the legitimacy of the challenged proposal would be a much bigger problem.” In other words: the bet that the SEC’s retreat would translate into a free hand for management has not paid off. The deterrents have simply moved from the regulator to the courts and the proxy ballot itself. Fundamental ownership rights — the right to ask questions about material risks — are not granted by regulators. They are inherent to ownership itself. The 2026 season is shaping up to be the year that principle gets tested, and so far, it is holding. — *Sources: Proxy Preview 2026, published by As You Sow and Proxy Impact. Full report available at [proxypreview.org](https://www.proxypreview.org/).*

On this week's pod: Aye, well done RangersGame segment:A complete mess of a gameShout outs:Captain James Tavernier leaving RangersRFC Player of the Year dinnerCondolences for Quentin 'Cutty' YoungJimmy Denning obtains his duck egg blue cardMaurice Edu shirt available for a good homeNARSA business:NASHVILLE 2026 IS FOR EVERYONE ANYONEFriday night is a western themeDavie Cooper Memorial Topgolf Tournament now on sale - https://narsa.ca/tickets/ - PLEASE BOOK THIS WEEKRFC Executive Director, Fraser Thornton and RFC CEO, Jim Gillespie are joining us at NARSA 2026!!!RFC 9-in-a-row legends: Derek Ferguson, Scott Nisbet, David Robertson, and Mark WaltersRFC Historian: David MasonEntertainment: MC David Edgar, Stuart Hay, Rebecca Auchterlonie, and DJ Angry BearDestination NARSA - Nashville 2026 - 44 days / 6 weeksTICKETS NOW ON SALE: $199 USD | NARSA 2026 NashvilleHotel: Cambria Hotel Nashville Midtown | Booking: https://www.choicehotels.com/reservations/groups/OI25P7Phoning: +1 615-931-0777 (NARSA is the keyword)Room rate: $199 + Taxes & Fees | Room rate available 3-days prior and 3-days postCommunications:Gers Guide - nopeWomen's team had a similar experience to the menRangers Pubs - https://www.rangerspubs.comInstagram and TikTok - follow us at narsacomms#NARSA #RangersFC #WeeklyUpdatehttps://narsa.ca/

In this episode of Coffee Talk with Bryan & Marie, we sit down with Brian — a Navy Commander whose career spans shipboard leadership, university instruction, strategic planning, and financial expertise. Brian graduated from Auburn University in 2006 with a degree in Political Science and was commissioned into the United States Navy the same day. Over ten years on active duty, he served aboard three different classes of ships, deploying twice to the Persian Gulf and once to Southeast Asia. His roles included First Lieutenant on USS Gettysburg (CG‑64), Operations Officer on USS Defender (MCM‑2), and Operations Officer on USS Arleigh Burke (DDG‑51).Brian later joined the faculty at Villanova University as an Instructor of Naval Science, earning a nomination for Naval Service Training Command's Instructor of the Year and becoming the only non‑PhD to win Villanova's prestigious “Junior Faculty Award for Excellence in Teaching.” He also completed his Master of Arts in Political Science during his time there.After transitioning to the Navy Reserve in 2015, Brian entered the financial world as a planner with Pultro Financial Management, earning advanced certifications including AIF, BFA, RFC, and the IARFC “Ethics Certified” designation. The Navy recalled him to active duty in 2018, where he served as a Strategic Planner in the Iran Branch at U.S. Central Command. Today, he continues to serve as a Commander and Staff Officer at Carrier Strike Group Four.Outside of uniform, Brian is deeply committed to family, community, and service. He spends his free time with his wife, three sons, and two golden retriever rescues, and serves on the boards of the Auburn University Alumni Association, the Villanova University Alumni Association, and the LPL Financial Government Relations Advisory Council.Join Bryan and Marie for a thoughtful, wide‑ranging conversation about leadership, service, transition, teaching, financial ethics, and the evolving mission of today's Navy.

On this week's pod: Behave like championsGame segment:Recharged for the final 5Shout outs:Manny Fernandez in PFA Scotland Team of the YearBelated birthday shoutoutMaurice Edu shirt available for a good homeLondon Marathon for the Royal British Legion (one last time)NARSA business:NASHVILLE 2026 IS FOR EVERYONE ANYONEDavie Cooper Memorial Topgolf Tournament now on sale - https://narsa.ca/tickets/ - PLEASE BOOK THIS WEEKRFC Executive Director, Fraser Thornton and RFC CEO, Jim Gillespie are joining us at NARSA 2026!!!RFC 9-in-a-row legends: Derek Ferguson, Scott Nisbet, David Robertson, and Mark WaltersRFC Historian: David MasonEntertainment: MC David Edgar, Stuart Hay, Rebecca Auchterlonie, and DJ Angry BearDestination NARSA - Nashville 2026 - 51 days / 7 weeksTICKETS NOW ON SALE: $199 USD | NARSA 2026 NashvilleHotel: Cambria Hotel Nashville Midtown | Booking: https://www.choicehotels.com/reservations/groups/OI25P7Phoning: +1 615-931-0777 (NARSA is the keyword)Room rate: $199 + Taxes & Fees | Room rate available 3-days prior and 3-days postCommunications:Gers Guide - sort ofWomen's team top of the table actionRangers Pubs - https://www.rangerspubs.comInstagram and TikTok - follow us at narsacomms#NARSA #RangersFC #WeeklyUpdatehttps://narsa.ca/

【PR：Surfshark】プロモリンク ⁠⁠https://surfshark.com/yurucom⁠⁠ にアクセスするか、チェックアウト時にプロモコード yurucom を使用すると、Surfshark VPN が4か月分追加されます！30日間の返金保証付き！ぜひご利用ください！ネット回線を速くする方法を話します。たった一本ケーブルを通すだけで爆速になるし、機械オンチでもできます。【目次】0:00 悩み抱えたまま暮らす機械オンチ1:06 ネット回線は工夫で速くなる4:43 ルーターのトラップ12:37 キーワードは「壁内配線」29:15 不親切な初期設定のワケ37:17 LANケーブルの選び方41:18 置かれた場所で咲かないで【参考文献】◯四字熟語辞典オンライン「浅薄愚劣」https://yoji.jitenon.jp/yojil/5755◯四字熟語辞典オンライン「頑陋至愚」https://yoji.jitenon.jp/yojik/5144四字熟語辞典オンライン「無知蒙昧」https://yoji.jitenon.jp/yojic/1217◯四字熟語辞典オンライン「浅学非才」https://yoji.jitenon.jp/yojic/1379◯コトバンク（精選版 日本国語大辞典）「不学無術」https://kotobank.jp/word/不学無術-2079229◯四字熟語辞典オンライン「無学無知」https://yoji.jitenon.jp/yojim/6172◯マスタリングTCP/IP―入門編―(第6版)(バリューブックス) ⇨ https://www.valuebooks.jp/bp/VS0056092275(Amazon) ⇨ https://amzn.to/4mnhGV9◯lightyear「Ethernet vs WiFi: Comparing Network Latencyhttps://lightyear.ai/tips/ethernet-versus-wifi-latency◯I-O DATA「LANケーブルのカテゴリーはどれがおすすめ？主な種類と選び方を解説」https://www.iodata.jp/column/nas/043/index.htm◯RFC 1812「Requirements for IP Version 4 Routershttps://datatracker.ietf.org/doc/html/rfc1812【サポーターコミュニティへの加入はこちらから！】⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://yurugengo.com/support⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠【親チャンネル：ゆる言語学ラジオ】⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.youtube.com/@yurugengo⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠【実店舗プロジェクト：ゆる学徒カフェ】⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.youtube.com/@yurugakuto⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠【お仕事依頼はこちら！】info@pedantic.jp【堀元見プロフィール】慶應義塾大学理工学部卒。専攻は情報工学。理屈っぽいコンテンツを作り散らかすことで生計を立てている。Twitter→⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/kenhori2⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠noteマガジン→⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://note.com/kenhori2/m/m125fc4524aca⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠個人YouTube→⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.youtube.com/@kenHorimoto⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠【水野太貴プロフィール】1995年生まれ。愛知県出身。名古屋大学文学部卒。専攻は言語学。本業は雑誌編集者。著書に『会話の0.2秒を言語学する 』（新潮社）などがある。Podcast「神保町で会いましょう」のパーソナリティも務める。Twitter→⁠⁠⁠⁠⁠https://x.com/yuru_mizuno⁠⁠⁠⁠⁠神保町で会いましょう→⁠⁠⁠⁠⁠https://open.spotify.com/show/6cYkvDO0HnJKLPgDBGUjjS

We asked for follow ups and you did not disappoint! On today's show we respond to listener comments and corrections on multicast, routing protocols, security, and more. We also have a technical correction for the RFC 1918 Class B private address range. A big thank you to everyone who sent in responses. If you'd like... Read more »

We asked for follow ups and you did not disappoint! On today's show we respond to listener comments and corrections on multicast, routing protocols, security, and more. We also have a technical correction for the RFC 1918 Class B private address range. A big thank you to everyone who sent in responses. If you'd like... Read more »

On this week's pod: Channeling our inner RoryGame segment:Entertaining in FalkirkShout outs:Chairman in PhillySome birthday shoutoutsORSA 2027Maurice Edu shirt available for a good homeLondon Marathon for the Royal British LegionNARSA business:NASHVILLE 2026 IS FOR EVERYONE ANYONERFC Executive Director, Fraser Thornton and RFC CEO, Jim Gillespie are joining us at NARSA 2026!!!RFC 9-in-a-row legends: Derek Ferguson, Scott Nisbet, David Robertson, and Mark WaltersRFC Historian: David MasonEntertainment: MC David Edgar, Stuart Hay, Rebecca Auchterlonie, and DJ Angry BearDestination NARSA - Nashville 2026 - 58 days / 8 weeksTICKETS NOW ON SALE: $199 USD | NARSA 2026 NashvilleHotel: Cambria Hotel Nashville Midtown | Booking: https://www.choicehotels.com/reservations/groups/OI25P7Phoning: +1 615-931-0777 (NARSA is the keyword)Room rate: $199 + Taxes & Fees | Room rate available 3-days prior and 3-days postDavie Cooper Memorial Topgolf Tournament now on sale - https://narsa.ca/tickets/Communications:Gers Guide Rangers Disabled Supporters AssociationRangers Pubs - https://www.rangerspubs.comInstagram and TikTok - follow us at narsacomms#NARSA #RangersFC #WeeklyUpdatehttps://narsa.ca/

インターネット接続の0.2秒を科学する。パソコンがネットワークに繋がるまでの壮大なドラマとは…？【目次】0:00 『インターネット接続の0.2秒を科学する』2:16 まずはルーターに接続7:53 パソコンもご近所あいさつをする15:53 宛先を変換するやつはどこにでもいる20:18 プロバイダって何？32:48 人間とインターネット通信は違う？【参考文献】◯会話の0.2秒を言語学する(バリューブックス) ⇨ https://www.valuebooks.jp/bp/VS0063352236(Amazon) ⇨ https://amzn.to/46Qgp2N◯日経クロステック「IPアドレスを自動割り当て、思わず膝を打つ「DHCP」の巧みさを図解」https://xtech.nikkei.com/atcl/nxt/column/18/00780/062000010/◯マスタリングTCP/IP―入門編―(第6版)(バリューブックス) ⇨ https://www.valuebooks.jp/bp/VS0056092275(Amazon) ⇨ https://amzn.to/4mnhGV9◯RFC 2131 「Dynamic Host Configuration Protocol」https://datatracker.ietf.org/doc/html/rfc2131◯RFC 791「Internet Protocol（IPv4）」https://datatracker.ietf.org/doc/html/rfc791【サポーターコミュニティへの加入はこちらから！】⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://yurugengo.com/support⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠【親チャンネル：ゆる言語学ラジオ】⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.youtube.com/@yurugengo⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠【実店舗プロジェクト：ゆる学徒カフェ】⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.youtube.com/@yurugakuto⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠【お仕事依頼はこちら！】info@pedantic.jp【堀元見プロフィール】慶應義塾大学理工学部卒。専攻は情報工学。理屈っぽいコンテンツを作り散らかすことで生計を立てている。Twitter→⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/kenhori2⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠noteマガジン→⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://note.com/kenhori2/m/m125fc4524aca⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠個人YouTube→⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.youtube.com/@kenHorimoto⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠【水野太貴プロフィール】1995年生まれ。愛知県出身。名古屋大学文学部卒。専攻は言語学。本業は雑誌編集者。著書に『会話の0.2秒を言語学する 』（新潮社）などがある。Podcast「神保町で会いましょう」のパーソナリティも務める。Twitter→⁠⁠⁠⁠⁠⁠https://x.com/yuru_mizuno⁠⁠⁠⁠⁠⁠神保町で会いましょう→⁠⁠⁠⁠⁠⁠https://open.spotify.com/show/6cYkvDO0HnJKLPgDBGUjjS

Liege Maximo has hit US retail — and Big Convoy is coming with him whether you like it or not. The crew also digs into the Takara Tomy MPG-20 Hot Rod (same transformation, five times the price), and new comparison shots of the G2 Stunticons confirm the Takara set is the one to have — though JT Prime says the Hasbro versions are closer than you think. In What We Got: Diecast adds FansToys Long Haul to push his Devastator build to four of six, and Brian lands the big one — a boxed, complete G1 Grand Maximus, the piece he never expected to find. RFC 982.

Liege Maximo has hit US retail — and Big Convoy is coming with him whether you like it or not. The crew also digs into the Takara Tomy MPG-20 Hot Rod (same transformation, five times the price), and new comparison shots of the G2 Stunticons confirm the Takara set is the one to have — though JT Prime says the Hasbro versions are closer than you think. In What We Got: Diecast adds FansToys Long Haul to push his Devastator build to four of six, and Brian lands the big one — a boxed, complete G1 Grand Maximus, the piece he never expected to find. RFC 982.

So much of what is happening these days seems utterly nonsensical, from Trump’s war crime and profanity-laced Easter rant, to the whipsaw on Iran. So, is it simply Occam’s razor, or is there more going on here than we’re led to believe? Since I entered politics, I have chiefly had men’s views confided to me privately. Some of the biggest men in the United States, in the field of commerce and manufacture, are afraid of somebody, are afraid of something. They know that there is a power somewhere so organized, so subtle, so watchful, so interlocked, so complete, so pervasive, that they had better not speak above their breath when they speak in condemnation of it. — President Woodrow Wilson, The New Freedom: A Call for the Emancipation of the Generous Energies of a People (1913) The real truth of the matter is, as you and I know, that a financial element in the larger centers has owned the Government ever since the days of Andrew Jackson — and I am not wholly excepting the Administration of W. W. The country is going through a repetition of Jackson’s fight with the Bank of the United States — only on a far bigger and broader basis. — President Franklin D. Roosevelt, letter to Col. Edward Mandell House (21 November 1933); as quoted in F.D.R.: His Personal Letters, 1928-1945, edited by Elliott Roosevelt (New York: Duell, Sloan and Pearce, 1950), pg. 373 I would suggest nothing we’re seeing, including (especially) the seemingly nonsensical, is ‘accidental’ or coincidental. It is PSYOP/PSWAR, a potent toxic mixture of POSIWID and chaos theory designed and intended to rapidly produce maximum chaos resulting in a ‘Clash of Civilizations‘ and The End of History and the Last Man, to ultimately bring about a ‘Novus Ordo Seclorum’1234 a la Genesis 11 → Genesis 6 → culminating in Psalm 2 → Revelation 19. Links Videos / Clips [x] = Played Trump says Americans against war with Iran are ‘foolish’ [x] 2:00–5:15 [x] 8:33–9:12 ‘Apparently I'm an idiot': Three-time Trump voter in Pennsylvania sounds off on Iran war [x] 3:15–3:45 Lucifer Has a NASA Moon Mission named Artemis. Here’s What They’re Hiding. Headlines [x] = Mentioned / Discussed Trump: “A Whole Civilization with Die Tonight” If President Trump carries out his threat to kill the entire civilization of Iran, he will join the ranks of Cato the Elder, Genghis Khan, Cortez, and other villains in history who chose the policy of destroying an entire civilization. Needless to say, this is not what Washington, Madison, Adams, Jefferson, and Franklin had in mind when they founded the US Constitutional Republic. Members of the US government—as well as We the People—should think about the reflections of multiple Roman authors who regarded the total annihilation of Carthage as an outrage and repudiation of Rome's republican values and virtues. In the Aeneid, Virgil frames the Punic Wars as a fateful conflict initiated by the Punic Queen Dido’s curse on Aeneas’s descendants. I interpret this as Virgil's way of condemning the “unspeakable” destruction of Carthage. The American people should be aware of the fact that if our US government does indeed annihilate the Iranian nation forever, it will certainly have a vast array of terrible consequences for us and for all of mankind. Among other disasters, it is likely that millions of Iranians will be forced to flee to other lands, including those of Europe. Many young men who see their mothers, fathers, brothers, sisters suffer will be animated with a burning desire for revenge. I anticipate great horrors ahead for all of us. Trump's F-Bomb on Iran Joins America's Rollicking History of Presidential Profanity White House Easter egg roll Monday: How to watch live White House Easter Egg Roll honors America’s egg farmers, says President Trump | Fox News [x] Pentagon's new plans in Iran give Trump a way out of war crime accusations – POLITICO [x] Trump threatens to jail journalist who reported on crew's rescue in Iran if they don't reveal source – POLITICO [x] Iran Says US Airman Rescue May Have Been Cover to ‘Steal Enriched Uranium' Artemis ‘Launch’ April Fool’s Day / Easter – Amazing ‘Coincidence’ [x] [Published April Fool's Day! Same as Artemis II 'launch'] Did Van Allen Belts Stop the Moon Landings? Myth vs Fact – FreeAstroScience [x] Artemis II live updates: Nasa astronauts returning to Earth after seeing parts of Moon ‘no human has ever seen' | The Independent Artemis – Wikipedia “Isis, Astarte, Diana, Hecate, Demeter, Kali, Innana…” & Asteroids | Fixed Stars Are the goddesses Ashteroth, Remphan, Isis, Ishtar, Belit, Anahita, Artemis, and Diana the same goddess with different names? – Quora Pan: The Complete Guide to the Greek God of Nature (2023) The Rest [x] = Mentioned / Discussed [x] Deutsche Bank – Wikipedia [x] Deutsche Bank [00:27, 17 May 2024 revision] – Wikipedia [x] Trump family faces high-stakes testimony in Manhattan fraud trial [x] At Trump Org fraud trial, ex-banker recalls ‘hunting' for Trump's business | Courthouse News Service [x] Finra Suspends Trump's Former Personal Banker – AdvisorHub [x] Rosemary Vrablic – Wikipedia [x] Jared Kushner – Wikipedia The thinly sourced theories about Trump's loans and Justice Kennedy's son (Jul 12, 2018) by Salvador Rizzo | The Washington Post [x] Why Trump Is Mentally Unfit to Be President: Pathology of Narcissism (Apr 5, 2017) by Alex Morris | Rolling Stone [x] Taibbi on the Madness of Donald Trump (Sep 19, 2017) by Matt Taibbi | Rolling Stone [x] Donald Trump Is About to Be a Loser, His Lawyers Say (Mar 22, 2023) by Asawin Suebsaeng and Adam Rawnsley | Rolling Stone [x] Donald Trump, Trickster God (Mar 4, 2016) by Corey Pein | The Baffler [x] Kushner and Witkoff – by esc [x] IMEC: Trump's War With Iran Is About Global Trade. Period. [x] What The Iran Attack Is Really All About – Road Warrior Radio [x] Road Warrior Radio with Chris Hinkley, March 10, 2026 Hour 1 – Republic Broadcasting Network [x] Road Warrior Radio with Chris Hinkley, March 10, 2026 Hour 2 – Republic Broadcasting Network On This Day Events April 2026 Calendar of Public Holidays | Office Holidays Holidays and Observances in the United States in 2026 What day is it today? Important events every day ad-free | United States OTD On This Day – What Happened on April 7 Today in History: April 7, Rwandan genocide begins | AP News What Happened on April 7 – On This Day What Happened on April 7 | HISTORY April 7 – Wikipedia What Happened On April 7 In History? 07 | April | 2020 | Executed Today Holidays National Beer Day (United States) Historical Events 2022 – The Senate confirmed Ketanji Brown Jackson – “Pizzagate” judge who was unable to define ‘woman' – to the Supreme Court, securing her place as the court's first Black female justice. 2021 – COVID-19 shenanigans: The Centers for Disease Control and Prevention announces that the SARS-CoV-2 Alpha variant has become the dominant strain of COVID-19 in the United States. 2020 – COVID-19 shenanigans: China ends its lockdown in Wuhan. 2020 – COVID-19 shenanigans: Acting Secretary of the Navy Thomas Modly resigns for his handling of the COVID-19 ‘pandemic’ on USS Theodore Roosevelt and the dismissal of Brett Crozier. 1994 – A day after the presidents of Rwanda and Burundi died in a missile attack on their aircraft, the moderate Hutu prime minister of Rwanda, Agathe Uwilingiyimana, and her husband were killed by Rwandan soldiers; in the 100 days that followed, Hutu extremists slaughtered hundreds of thousands of minority Tutsi and Hutu moderates. 1990 – John Poindexter is convicted for his role in the Iran–Contra affair. In 1991 the convictions are reversed on appeal. 1984 – The Census Bureau reported that Los Angeles had overtaken Chicago as the nation's “second city” in terms of population. 1980 – During the Iran hostage crisis, the United States severs relations with Iran. 1970 – John Wayne wins Best Actor Oscar: The legendary actor John Wayne wins his first—and only—acting Academy Award, for his star turn in the director Henry Hathaway's Western True Grit. Known for his tough, rugged, uniquely American screen persona, Wayne appeared in some 150 movies over the course of his long and storied career. 1969 – The internet is born: With the publication of RFC 1, The Advanced Research Projects Agency (ARPA) awarded a contract to build a precursor of today’s world wide web to BBN Technologies. The date is widely considered as the internet’s symbolic birthday. 1968 – Riots continue in over 100 US cities following the Apr 4 assassination of Martin Luther King Jr. 1966 – The U.S. Navy recovered a hydrogen bomb that the U.S. Air Force had lost in the Mediterranean Sea off Spain following a B-52 crash. 1964 – IBM announces the System/360. 1963 – Tito is made president of Yugoslavia for life: A new Yugoslav constitution proclaims Tito the president for life of the newly named Socialist Federal Republic of Yugoslavia. Formerly known as Josip Broz, Tito was born to a large peasant family in Croatia in 1892. 1961 – JFK lobbies Congress to help save historic sites in Egypt: President John F. Kennedy sends a letter to Congress in which he recommends the U.S. participate in an international campaign to preserve ancient temples and historic monuments in the Nile Valley of Egypt. The campaign, initiated by UNESCO, was designed to save sites threatened by the construction of the Aswan High Dam. 1954 – Domino Theory: President Dwight D. Eisenhower coined one of the most famous Cold War phrases, held a news conference in which he outlined the concept of the “domino theory” as he spoke of the importance of containing the spread of communism in Indochina, saying, “You have a row of dominoes set up, you knock over the first one, and what will happen to the last one is the certainty that it will go over very quickly.” 1953 – Sweden's Dag Hammarskjöld elected U.N. head: By a vote of 57 to 1, Dag Hammarskjöld is elected secretary-general of the United Nations. The son of Hjalmar Hammarskjöld, a former prime minister of Sweden, Dag joined Sweden's foreign ministry in 1947, and in 1951 formally entered the cabinet as deputy foreign minister. 1950 – President Truman receives NSC-68 report, calling for “containing” Soviet expansion: President Harry S. Truman receives National Security Council Paper Number 68 (NSC-68). The report was a group effort, created with input from the Defense Department, the State Department, the CIA, and other interested agencies; NSC-68 formed the basis for America's Cold War policy for the next two decades. 1949 – Tony-winning musical South Pacific opens on Broadway: The Rodgers and Hammerstein musical South Pacific opens at the Majestic Theatre on Broadway in New York City. The romantic musical about World War II, which touches on controversial racial themes, goes on to run for almost five years, becoming one of the most popular musicals of the 1950s. 1948 – World Health Organization established: The WHO, a privately funded United Nations agency front organization, ostensibly concerned with fighting disease and epidemics worldwide, building up national health services, and improving health education in its 194 member states. 1945 – World War II: The Imperial Japanese Navy battleship Yamato, one of the two largest ever constructed, is sunk by United States Navy aircraft during Operation Ten-Go, in Japan's first major counteroffensive in the struggle for Okinawa. Weighing 72,800 tons and outfitted with nine 18.1-inch guns, the battleship Yamato was Japan's only hope of destroying the Allied fleet off the coast of Okinawa. 1943 – The National Football League makes helmets mandatory. 1943 – Holocaust in Ukraine: In Terebovlia, Germans order 1,100 Jews to undress and march through the city to the nearby village of Plebanivka, where they are shot and buried in ditches. 1940 – Tuskegee Institute founder Booker T. Washington becomes the first Black American to be honored with a postage stamp. It will take nearly four decades for a Black woman to receive a similar honor: Harriet Tubman in 1978. 1939 – Benito Mussolini invades Albania, declares an Italian protectorate over Albania and forces King Zog I into exile. 1933 – National Beer Day: Prohibition in the United States is repealed for beer of no more than 3.2% alcohol by weight, eight months before the ratification of the Twenty-first Amendment to the United States Constitution. (Now celebrated as National Beer Day in the United States.) 1927 – First long-distance television transmission: an image of Secretary of Commerce Herbert Hoover is sent from Washington, D.C. to NYC by AT&T 1922 – Teapot Dome Scandal: Interior Secretary Albert B. Fall signed a secret deal to lease U.S. Navy petroleum reserves in Wyoming and California to his friends, oilmen Harry F. Sinclair and Edward L. Doheny, in exchange for cash gifts; Fall would eventually be sentenced to prison on bribery and conspiracy charges in what became known as the Teapot Dome Scandal. 1868 – Thomas D’Arcy McGee, one of the Canadian Fathers of Confederation is assassinated by the Irish, in one of the few Canadian political assassinations, and the only one of a federal politician. 1862 – American Civil War: Battle of Shiloh concludes: Two days of heavy fighting conclude near Pittsburgh Landing in western Tennessee. Union forces led by Gen. Ulysses S. Grant and Maj. Gen. Don Carlos Buell are victorious after the Confederate attack stalled on April 6, and fresh Yankee troops drove the Confederates from the field on April 7. 1832 – The Man Who Sold His Wife: Most modern readers believe Thomas Hardy was plunging into deep fiction when he wrote about a man selling his wife. He wasn’t. Nagging wives needed to be careful in 19th Century England, for, as Hardy recounted in The Mayor of Casterbridge, her husband might put her up for sale. That's just what happened on this day to Mary Thompson, according to a local newspaper report. 1829 – Joseph Smith, Jr., founder of the Latter Day Saint cult, commences translation of the Book of Mormon, with Oliver Cowdery as his scribe. 1827 – First friction match sold: English chemist John Walker produced and sold the first operable matches. They were soon banned in France and Germany because burning fragments would sometimes fall to the floor and start fires. 1805 – German composer Ludwig van Beethoven premieres his Third Symphony, at the Theater an der Wien in Vienna 1805 – Lewis and Clark depart Fort Mandan: After a long winter, the Lewis and Clark expedition departs its camp among the Mandan tribe and resumes its journey West. The Corps of Discovery had begun its voyage the previous spring, and it arrived at the large Mandan and Minnetaree villages along the upper Missouri River (north of present-day Bismarck, North Dakota) in late October. 1798 – The Mississippi Territory is organized from disputed territory claimed by both the United States and the Spanish Empire. It is expanded in 1804 and again in 1812. 1788 – American Pioneers to the Northwest Territory arrive at the confluence of the Ohio and Muskingum rivers, establishing Marietta, Ohio, as the first permanent American settlement of the new United States in the Northwest Territory, and opening the westward expansion of the new country. 1776 – Captain John Barry and the USS Lexington captures the Edward. 1739 – Dick Turpin is executed in England for horse stealing 1724 – Johann Sebastian Bach’s St. John Passion premiered: St. John’s Passion premieres on Good Friday at St. Nicholas Church in Leipzig, Electorate of Saxony (now Germany). The sacred oratorio is the oldest extant Passion by the German composer. The highly popular work is a dramatization of the final days of Jesus Christ, according to the Gospel of John. 1521 – Ferdinand Magellan arrives at Cebu. 529 – First draft of Corpus Juris Civilis or the Justinian Code (a fundamental work in jurisprudence) is issued by Eastern Roman Emperor Justinian I 451 – Attila the Hun captures Metz in France, killing most of its inhabitants and burning the town. 30 – Scholars estimate for the crucifixion of Jesus by Roman troops at the behest of Jewish leadership (Caiaphas the high priest, chief priests, scribes, elders) on Golgotha outside Jerusalem [or April 3] Births 1964 – Russell Crowe, New Zealand/Australian actor, singer, producer 1954 – Jackie Chan, Hong Kong-born actor and director noted for acrobatic stunt work in hits like “The Young Master” and the “Rush Hour” series. 1939 – Francis Ford Coppola, American director, producer, screenwriter 1938 – Jerry Brown, American lawyer and politician, 34th and 39th Governor of California 1931 – Daniel Ellsberg, American activist and author (died 2023) 1928 – James Garner, American actor, singer, and producer (died 2014) 1920 – Ravi Shankar, Indian/American sitar player, composer (died 2012) 1915 – Billie Holiday, American Jazz singer-songwriter, actress whose soulful intensity earned her the nickname “Lady Day.” Signature hits like “Strange Fruit” and “God Bless the Child.” (died 1959) 1897 – Walter Winchell, American journalist and radio host (died 1972) 1893 – Allen Dulles, American lawyer and diplomat, 5th Director of Central Intelligence (died 1969) 1890 – Marjory Stoneman Douglas, journalist, conservationist, activist best known for her advocacy for the preservation of Florida’s Everglades region. (died 1998) 1860 – Will Keith Kellogg, American businessman, ardent eugenicist, Seventh-day Adventist cult member, founded the Kellogg Company (died 1951) 1772 – Charles Fourier, French philosopher, communist (died 1837) 1770 – William Wordsworth, English poet (died 1850) Deaths 1947 – Henry Ford, American businessman, founded the Ford Motor Company (born 1863) 1928 – Alexander Bogdanov, Russian physician, philosopher, and author (born 1873) 1891 – P. T. Barnum, American businessman, co-founded Ringling Bros., Barnum & Bailey Circus (born 1810) 1804 – Toussaint Louverture, Haitian general (born 1743) 1733 – Samuel Partridge, very stupid and unconcern'd From the New England Weekly Journal, July 23, 1733 — a three-month-old news item (part of a roundup of dated minor dispatches) that had to cross the Atlantic from the mother country. Ipswich, April 7. Last Saturday Samuel Partridge was executed here, for robbing Mr. Barwell of Brockley in this City, of 31l, 10s., a Horse, and other Things, in Company with another Person not yet taken. He said he was born at Debden in Suffolk, that he was about 22 years of Age, and was brought up in Husbandry; he appeared to be very illiterate, for he could neither read nor write, and was entirely ignorant of the first Principles of Christianity. He denied the Fact for which he suffered, and said he was perswaded to own the Robbery by a Soldier that was in Halsted Bridewell with him, he telling him, that if he confessed the Fact he would come off very well; and that he advised him to say, that he had made use of a Bolt instead of a Pistol, and that he had hid it in a certain Place, where it was found according to his Direction. At the Place of Execution he seemed very stupid and unconcern'd; only, as directed, he called on God for Mercy when he was turned off. Elon Musk Tweets ‘Novus Ordo Seclorum' After Donald Trump Wins Reelection. MAGA Is The Pied Piper – winepressnews.com ↩ Novus Ordo Seclorum – History of Motto on Great Seal’s Unfinished Pyramid ↩ Novus ordo seclorum – Wikipedia ↩ Annuit cœptis – Wikipedia ↩

On this week's pod:Happy Easter! | It's the business end of the season, so we start by analyzing the draws that we've had this season thus far...Game segment:Comfortable against UnitedShout outs:Erin's recoveryArlen's shoulder ORSA 2027Maurice Edu shirt available for a good homeLondon Marathon for the Royal British LegionNARSA business:RFC Executive Director, Fraser Thornton and RFC CEO, Jim Gillespie are joining us at NARSA 2026!!!RFC 9-in-a-row legends: Derek Ferguson, Scott Nisbet, David Robertson, and Mark WaltersRFC Historian: David MasonEntertainment: MC David Edgar, Stuart Hay, Rebecca Auchterlonie, and DJ Angry BearDestination NARSA - Nashville 2026 - 65 days / 9 weeksTICKETS NOW ON SALE: $199 USD | NARSA 2026 NashvilleHotel: Cambria Hotel Nashville Midtown | Booking: https://www.choicehotels.com/reservations/groups/OI25P7Phoning: +1 615-931-0777 (NARSA is the keyword)Room rate: $199 + Taxes & Fees | Room rate available 3-days prior and 3-days postDavie Cooper Memorial Topgolf Tournament now on sale - https://narsa.ca/tickets/Communications:Gers Guide Rangers women's team - WHAT A WEEK!Mike Moore's THFC pieceEaster message from the Rangers' ChaplainRangers Pubs - https://www.rangerspubs.comInstagram and TikTok - follow us at narsacomms#NARSA #RangersFC #WeeklyUpdatehttps://narsa.ca/

Un Teaser della puntata speciale slle RFC del primo di aprile! entrate nel supporters club per ascoltarla tutta.Come funziona il protocollo HTTPS? e quali sono gli standard per l'invio e la ricezione delle e-mail?Uno degli aspetti più belli dell'informatica è che la maggior parte degli standard non sono imposti da nessuno, ma sono figli di una reale procedura bottom-up, probabilmente la più reale in tutto il mondo della tecnologia.Chi ha una buona idea la scrive e la sottopone alla comunità come richiesta di commenti (Request For Comment, RFC), e la comunità stessa, in forma straordinariamente democratica e partecipata si decide cosa sarà adottato a livello mondiale.Tutto questo per 364 giorni all'anno… perché il 1º aprile… le cose cambiano un pochino.Diventa un supporter di questo podcast: https://www.spreaker.com/podcast/scientificast-la-scienza-come-non-l-hai-mai-sentita--1762253/support.

In this episode of PING, APNIC Chief Scientist Geoff Huston discusses an emerging concern about how the IETF interprets the concept of ‘Best Current Practice‘ (BCP). In his previous episode, Geoff explored emerging questions around DNS provisioning over IPv6, including experimental observations on its performance characteristics. Towards the end of the discussion, we turned to how the Internet Engineering Task Force documents standards and protocols through Best Current Practice (BCP) publications. In the traditional view, BCPs are intended to provide clear, implementation-focused guidance that remains neutral across different operational contexts. This includes networks of all scales — from home environments to enterprise, national, and international infrastructure. These systems rely on a shared understanding of protocol behaviour, and BCPs help define the set of practical, interoperable choices available for deployment today. To be designated as a BCP, an IETF RFC undergoes additional review and scrutiny. This is similar to the ‘Standard' (STD) designation, which elevates an RFC beyond a general publication and gives it greater weight in operational and procurement contexts. While RFCs are not legally binding, they are frequently referenced in national regulations, procurement frameworks, and service specifications. In contrast, Experimental and Informational RFCs explicitly indicate that they are not intended for such use. BCPs, along with Proposed Standards and Standards, carry greater normative weight due to the more rigorous processes required for their approval, making them more suitable as references for real-world deployment and decision-making. An emerging perspective suggests that BCPs may be treated as aspirational as well as definitional — potentially describing behaviours that are not yet widely deployed, or in some cases not deployed at all. This represents a subtle shift from the traditional view of BCPs as documenting established, operational practice. This tension has surfaced in discussions around the DNS/IPv6 draft mentioned in the earlier PING episode. The conversation involves multiple parts of the IETF process, including the DNSOP Working Group, the DNS Directorate (which reviews DNS-related work across Working Groups) and the Internet Engineering Steering Group (IESG), responsible for final document review and status approval before publication as an RFC. These discussions reflect an evolving question: Should BCPs remain a record of established operational consensus, or can they also serve to guide and shape future practice? Advocacy is an important part of the IETF process. But it's important to distinguish between advocating for a new path in systems and specifying what the current best choice is in the specification of systems behaviour.

On this week's pod:A RFC Guest Announcement for NARSA 2026!Shout outs:Jack Butland's 150th appearanceHappy birthdays - Neil and HudsonLondon Marathon for the Royal British LegionNARSA business:RFC Executive Director, Fraser Thornton and RFC CEO, Jim Gillespie are joining us at NARSA 2026!!!RFC 9-in-a-row legends: Derek Ferguson, Scott Nisbet, David Robertson, and Mark WaltersRFC Historian: David MasonEntertainment: MC David Edgar, Stuart Hay, Rebecca Auchterlonie, and DJ Angry BearDestination NARSA - Nashville 2026 - 72 days / 10 weeksTICKETS NOW ON SALE: $199 USD | NARSA 2026 NashvilleHotel: Cambria Hotel Nashville Midtown | Booking: https://www.choicehotels.com/reservations/groups/OI25P7Phoning: +1 615-931-0777 (NARSA is the keyword)Room rate: $199 + Taxes & Fees | Room rate available 3-days prior and 3-days postDavie Cooper Memorial Topgolf Tournament now on sale - https://narsa.ca/tickets/Communications:Gers Guide Rangers women's Sky Sports Cup disappointmentChairman's messageRangers Pubs - https://www.rangerspubs.comInstagram and TikTok - follow us at narsacommsPlease like and subscribe wherever you hear this podcast - Especially now that we're on video!#NARSA #RangersFC #WeeklyUpdatehttps://narsa.ca/

Send us Fan MailHearing aid returns aren't just a number on a dashboard, they're a clue about what your patients experienced from the first hello to the first follow-up. We talk through the real reasons people bring devices back and why “return for credit” (RFC) should push us toward better systems, not more self-blame.We break down six practical ways to reduce hearing aid returns in a hearing clinic or audiology private practice. That starts with access through appropriate financing options, because many patients simply don't have the savings to say yes with confidence. From there, we dig into motivational interviewing and the exact kinds of open-ended questions that reveal what the patient and their spouse actually want, how socially active they are today, and whether they're truly ready to commit to hearing technology.Next, we zoom in on onboarding and follow-up scheduling, the patient experience that turns a transaction into a program. We also explain how best practices like real ear measurement, speech-in-noise testing, and tools such as the Abbreviated Profile of Hearing Aid Benefit (APHAB) support better outcomes and fewer surprises. Finally, we cover setting realistic expectations, renaming the “trial period” into an “adjustment period,” and recommending the appropriate level of hearing aid technology based on test results, lifestyle, and communication goals.If you want fewer returns, happier patients, and more word-of-mouth referrals, hit play. Subscribe, share this with a colleague, and leave a review so more hearing care providers can build clinics that patients trust.Visit our website and take our quick online hearing screener. And if you're ready to take the next step, our online hearing care provider locator can help you find a trusted hearing care professional near you. Taking that first step can make a meaningful difference, helping you stay connecting to the people and moments that matter most.  Connect with the Hearing Matters Podcast TeamEmail: hearingmatterspodcast@gmail.com Instagram: @hearing_matters_podcast Facebook: Hearing Matters Podcast

It's a rare thing when a Transformers podcast episode is almost entirely good news — but Episode 979 is exactly that. Join Brian and the RFC crew as they dig into one of the most anticipated HasLab releases in years, and debate how many Ultra Magnuses is too many Ultra Magnuses.

It's a rare thing when a Transformers podcast episode is almost entirely good news — but Episode 979 is exactly that. Join Brian and the RFC crew as they dig into one of the most anticipated HasLab releases in years, and debate how many Ultra Magnuses is too many Ultra Magnuses.

The PHP Podcast streams live, typically every Thursday at 3 PM PT. Come join us and subscribe to our YouTube channel. Another fun episode of the PHP Podcast! Here’s what we covered: Elizabeth Barron’s New Role – We discussed Elizabeth Barron’s appointment as Executive Director of the PHP Foundation and recommended checking out the extended Alive & Kicking interview from Tuesday (it’s really good!). ElephantAlert.com Launch – Joe from the PHP Architect team launched a new community resource for tracking PHP elephant plushie sales! Never miss a limited edition elephant again at elephantalert.com – a fun way to stay updated on the collectibles the community loves. Real Coding Stories – Eric shared his experience going “old school” and manually coding an S3 image upload feature with workflow triggers after Claude kept misinterpreting the requirements. Sometimes you just gotta type it yourself! AI Reality Check – An honest discussion about AI’s current limitations: the promise vs. the reality of productivity gains, struggles with OpenClaw workflows, the frustration of repeated formatting issues, and concerns about junior developers being over-relied upon with AI tools. Eric’s worried we’re approaching an “AI unraveling” moment in the industry. AI in Healthcare – Eric had to opt-in to AI-assisted medical procedures at a doctor’s appointment – a glimpse into how AI is spreading into high-stakes environments (and potential liability nightmares). Laravel Artisan TUI – Eric’s excited about Artisan Browse, a new terminal user interface (TUI) for Laravel’s Artisan commands. Perfect for his tmux workflow! Nothing you *need*, but everything you *want* when you live in the terminal. SlideWire Released – Wendell (who writes the PHP Enterprise column) released SlideWire – a package for creating presentations using Blade and Livewire. Eric’s planning to use it for his next talk (maybe the PHP Tech opening?). Magazine Updates – February print issue finally shipped after the usual back-and-forth with the printer about safe print areas. Features a monster-themed FrankenPHP cover that’s quickly becoming a favorite! Laravel 13 Official Release – Laravel 13 is now the default version! No breaking changes expected, lots of attribute updates in the framework. Pretty smooth upgrade path for most projects. PHP UK Videos Live – PHP UK conference videos are now available on their YouTube channel. Chris and Mike attended and had a great time! PHP Tek 2026 Countdown – Just 61 days away! Schedule is posted (though still subject to minor adjustments). Remember: your ticket includes access to PHP Tech TV for all recorded talks, so don’t stress about conflicts. PHP Internals Discussion – Covered the “PHP Community” RFC proposing ways to make PHP development more community-driven with faster iteration. Eric and John discussed the balance between community input and maintaining code quality/stability – suggesting perhaps a community vote that counts as a weighted portion of the total RFC votes. DevOps Wins – Eric successfully migrated all sites from Envoyer to Laravel Forge’s new zero-downtime deployment feature, saving money and simplifying the stack. Sometimes consolidation is the right move! Pool Player App Updates – John’s dealing with real-world edge cases now that his pool league management app is in production. Main pain point: email notifications going to spam. Twilio SMS integration coming soon to solve the time-sensitive notification problem. 3D Printing Crunch Time – John was up until 2 AM printing keychains for his wife’s school fun run (thought he had a week, turns out it was the next day). The hum of the printer became the unofficial background soundtrack of the episode! Links from the show: ElephantAlert.com – Community PHP Elephant Sales Tracker Artisan Browse – TUI for Laravel Artisan SlideWire – Presentations with Blade and Livewire Laravel 13 Documentation PHP UK Conference YouTube Channel PHP[tek] 2026 – May 19-23, Chicago PHP Community RFC – Faster Moving Community Driven PHP Laravel Forge PHP Score – Technical Debt Monitoring X: https://x.com/phparch Mastodon: https://phparch.social/@phparch Bluesky: https://bsky.app/profile/phparch.com Discord: https://discord.phparch.com Subscribe to our magazine: https://www.phparch.com/subscribe/ Host: Eric Van Johnson X: @shocm Mastodon: @eric@phparch.social Bluesky: @ericvanjohnson.bsky.social PHPArch.me: @eric John Congdon X: @johncongdon Mastodon: @john@phparch.social Bluesky: @johncongdon.bsky.social PHPArch.me: @john Streams: Youtube Channel Twitch Partner This podcast is made a little better thanks to our partners Displace Infrastructure Management, Simplified Automate Kubernetes deployments across any cloud provider or bare metal with a single command. Deploy, manage, and scale your infrastructure with ease. https://displace.tech/ PHPScore Put Your Technical Debt on Autopay with PHPScore CodeRabbit Cut code review time & bugs in half instantly with CodeRabbit. Music Provided by Epidemic Sound https://www.epidemicsound.com/ The post The PHP Podcast 2026.03.19 appeared first on PHP Architect.

The NWSL season kicked off last week, and your Seattle Reign took what could have been a nightmare and turned it into a dream. Keely Dunning and Laura Schott breakdown an impressive 2-1 road win vs Orlando Pride, a match that included a nearly 3-hour delay due to lightning strikes. And the schedule only gets tougher: Schott previews RFC’s next match at rival Portland Thorns on Friday. And history in the making — the Reign are headed to Spokane One Stadium for their first three home matches of the season. Eastern Washington, get ready. Tickets available here. See omnystudio.com/listener for privacy information.

Just when you think you have a handle on how a company will react to rising oil prices, Delta Airlines goes and flips the idea on its head. Even though the industry could be facing significant increases in fuel prices, the carrier gave shocking rosy earnings projections at a recent industry event. Plus, Mastercard's foray into stablecoins and a sample of stories we're watching Tyler Crowe, Matt Frankel, and Lou Whiteman discuss: - Delta's rosy outlook - The changes in the airline industry - Mastercard's bet to become a crypto payments company - The wall between fintech and traditional finance crumbling - Bye bye, quarterly filings - NVIDIA's $1 trillion projection - Who's gonna insure that data center? Companies discussed: DAL, AAL, LUV, UAL, BA, MA, V, COF, SOFI, JPM, BAC, TFC, RFC, PNC, NVDA, META, GOOG, AMZN Host: Tyler Crowe Guests: Matt Frankel, Lou Whiteman Engineer: Dan Boyd Disclosure: Advertisements are sponsored content and provided for informational purposes only. The Motley Fool and its affiliates (collectively, “TMF”) do not endorse, recommend, or verify the accuracy or completeness of the statements made within advertisements. TMF is not involved in the offer, sale, or solicitation of any securities advertised herein and makes no representations regarding the suitability, or risks associated with any investment opportunity presented. Investors should conduct their own due diligence and consult with legal, tax, and financial advisors before making any investment decisions. TMF assumes no responsibility for any losses or damages arising from this advertisement. We're committed to transparency: All personal opinions in advertisements from Fools are their own. The product advertised in this episode was loaned to TMF and was returned after a test period or the product advertised in this episode was purchased by TMF. Advertiser has paid for the sponsorship of this episode. Learn more about your ad choices. Visit ⁠⁠⁠⁠⁠⁠⁠⁠megaphone.fm/adchoices⁠⁠ Learn more about your ad choices. Visit megaphone.fm/adchoices

In episode # 600, we are joined by Justin and Rob from RFC to talk about herping for pythons in Australia. MPR Network SocialsFB: https://www.facebook.com/MoreliaPythonRadioIG: https://www.instagram.com/morelia_python_radio/YouTube: https://www.youtube.com/channel/UCtrEaKcyN8KvC3pqaiYc0RQEmail: moreliapythonradio@gmail.com Merch store: https://teespring.com/stores/mprnetworkPatreon: https://www.patreon.com/moreliapythonradio ★ Support this podcast on Patreon ★