Podcasts about Feature

In which Joshua explains why he was wrong about frugality and your goal should be to spend more money, not less. Enjoy! Joshua Sponsor: come hang out with me at Nomad Capitalist Live, November 4-7 in Cancun, Mexico. www.NomadCapitalist.com/live 

Recorded live at MAU Vegas 2026 in collaboration with AppsFlyer, Steve P. Young had a quick conversation with David LoPresti, Director of Consumer Apps at U-Haul, to break down the app strategies helping millions of customers during one of the most stressful moments in life: moving.David shares how a simple UX improvement inside the U-Haul app eliminated over 600,000 customer support phone calls and saved the company nearly $3 million in operational costs, proving that the best app growth strategies aren't always powered by AI.You'll also learn how U-Haul leverages first-party customer data, improves mobile app onboarding, reduces friction, and creates personalized customer experiences at scale.If you're building an app in 2026, this conversation is packed with actionable lessons on app UX, retention, customer experience, and mobile growth.You'll Learn:✅ How U-Haul saved millions with one app feature✅ Why reducing friction increases customer retention✅ The power of simple UX improvements✅ App growth lessons from a household brand✅ Why customer reviews reveal your best product roadmapLearn more about AppsFlyer's new Mobile Measurement:https://bit.ly/4u8OpRhWork with us to grow your apps faster & cheaper:http://www.appmasters.com/You can also watch this video here: https://youtu.be/V6pwcHqs7X0*********************************************SPONSORSThe app growth playbook is changing fast.AppsFlyer's State of eCommerce App Marketing Report 2026 breaks down the latest trends, benchmarks, fraud insights, and market-by-market data every app marketer should know before planning Q4.Download it free from the link below: https://bit.ly/4uvoHGM*********************************************Yango Ads is offering 20% revenue boost bonus, sign up here: https://yango-ads.com/adnetwork/bonus20?utm_source=yt&utm_medium=social&utm_campaign=bonus. This special offer is valid before June 30th, 2026. Don't miss your chance to monetize your apps smarter!*********************************************Follow us:YouTube: ⁠AppMasters.com/YouTube⁠Instagram: ⁠@App MastersTwitter: ⁠@App MastersTikTok: ⁠@stevepyoung⁠Facebook: ⁠App Masters⁠*********************************************

This week we welcome writer/director/producer Madison Young on the show to talk about her first feature By the Roots, which she wrote based on her memoir that she wrote in 2016. Madison talks about how she developed the story into a script and raised the money to make the film. After that I talk a bit about re-writing my script Ricky and the Ooze, enjoy! Don't forget to support us on Patreon! www.patreon.com/mmihpodcast Leave us a Review on Apple Podcasts! https://podcasts.apple.com/us/podcast/making-movies-is-hard-the-struggles-of-indie-filmmaking/id1006416952 Hosted by Simplecast, an AdsWizz company. See https://pcm.adswizz.com for information about our collection and use of personal data for advertising.

Hour 1 for 6/1/26 Drew welcomes Dr. Ken Craycraft to discuss his piece on the Blessed Virgin and political life (2:01). Topics: how Our Lady responds (7:53), and mixing politics and religion (12:38). Then, Charles Hilu from The Dispatch joins Drew to discuss his recent feature about a coalition of pro-lifers and progressives opposing assisted suicide (30:46). Topics: finding common ground (34:53), the uphill battle pro-lifers face (38:30), lessons from other countries (42:53), and one caller who wants legalized assisted suicide (47:42). Links: Dr. Craycraft's Piece https://x.com/krcraycraft Charles' Feature x.com/charleshilu73

Hosts Tasha Huo and Josh Hallman sit down with writer-directors Ryan Polly and Matt Black to talk about their wild story of theft and impersonation that led to them making their first Hollywood feature film, and about what it's like to find Hollywood success while living and working in Texas.   Questions/Comments: ActTwoWriters@gmail.com  Edited by the GREAT Paul Lundquist

Welcome to this week's episode of the PEBCAK Podcast!  We've got four amazing stories this week so sit back, relax, and keep being awesome!  Be sure to stick around for our Dad Joke of the Week. (DJOW) Follow us on Instagram @pebcakpodcast   Please share this podcast with someone you know!  It helps us grow the podcast and we really appreciate it!   Simple 6 signup link https://simple6.co/r/CFUR98   Microsoft releases a temporary mitigation script for "YellowKey," a BitLocker-bypassing Windows zero-day with no permanent fix yet https://www.bleepingcomputer.com/news/microsoft/microsoft-shares-mitigation-for-yellowkey-windows-zero-day/   Researchers uncover FAST16, a state-sponsored cyber-sabotage framework from 2005 that silently corrupted precision engineering calculations — predating Stuxnet by at least five years and linked to NSA tooling https://www.tomshardware.com/software/security-software/decades-old-pre-stuxnet-cyber-sabotage-tool-breaks-cover-nsa-listed-it-as-nothing-to-see-here-fast16-targeted-nuclear-reactors-dam-design-and-other-high-precision-civil-engineering-software-years-before-stuxnet-broke-cover https://www.wired.com/story/fast16-malware-stuxnet-precursor-iran-nuclear-attack/ https://www.sentinelone.com/labs/fast16-mystery-shadowbrokers-reference-reveals-high-precision-software-sabotage-5-years-before-stuxnet/   Riot Games clarifies its Vanguard anti-cheat doesn't brick PCs — it just renders $6,000 worth of DMA cheat hardware completely useless https://www.ign.com/articles/riot-games-says-it-would-not-and-cannot-use-vanguard-anti-cheat-to-brick-pcs-after-rumors-spread https://www.tweaktown.com/news/111774/valorants-vanguard-anti-cheat-now-destroys-dma-cheat-firmware/index.html https://x.com/dexerto/status/2057785616255860991   Apple is developing an "anti-snatch" feature that automatically locks an iPhone the moment sensors detect it's been ripped from a user's hand — and London thieves already prefer iPhones over Samsungs https://appleinsider.com/articles/26/05/27/rumored-anti-snatch-feature-will-automatically-lock-iphones-yanked-out-of-a-users-hand https://appleinsider.com/articles/25/11/18/london-thieves-snatching-iphones-but-dont-want-no-samsung   Dad Joke of the Week (DJOW)   Find the hosts on LinkedIn: Chris - https://www.linkedin.com/in/chlouie/ Brian - https://www.linkedin.com/in/briandeitch-sase/ Ben - https://www.linkedin.com/in/benjamincorll/

In this Fanbase Feature, The Fanbase Weekly co-hosts Bryant Dillon and Claire Thorne are joined by special guests David Avallone (writer – Drawing Blood, Elvira meets H.P. Lovecraft) and Paul Pakler (co-host – Paul and Corey Cross the Streams, Quality Time with Family Ties, writer - Hobo Code) to participate in a thorough discussion regarding Children of Men (2006) in light of the feature film's 20th anniversary, with topics including how the film reads differently two decades later, the religious symbolism in the film, the drastic differences between the film and the novel that inspired it, and more. (Beware: SPOILERS for Children of Men abound in this panel discussion!)

The new "Ask YouTube" feature is rolling out, and wow... it's a big update! I am sharing my honest thoughts on how this new feature could shift everything we know about YouTube search and content strategy. I am breaking down what Ask YouTube means for your channel, how to adapt, and why showing up authentically matters more than ever. ⭐️ Turn your YouTube channel into a sales funnel! Get Meredith's YouTube Funnel Playbook here: https://videobrand.link/playbook✨ STILL IGNORED IN YOUR NICHE? GET YOUR YOUTUBE VISIBILITY REPORT: https://meredithmarsh.co/visibility

Our weekly karaoke feature where Bree and Clint go head-to-head singing a song to see who can do it the best. This week the one and only Spice Girls are taking centre stage, but who will come out on top? Hear Fridayoke live on the Bree & Clint Show, 5pm Fridays on ZM.See omnystudio.com/listener for privacy information.

The Topic: Marilyn Monroe’s life and career has been dissected and displayed for almost a century. But for such a pervasive and enduring figure, Monroe’s true internal life remains mysterious: was she forced into her “dumb blonde,” “bimbo” persona, or did she use it to her advantage? Perhaps the truth lies somewhere in-between. The exhibit: In honor of what would be her 100th birthday, the Academy Museum of Motion Pictures attempts to portray Monroe as she was with their exhibition Marilyn Monroe: Hollywood Icon. The exhibition displays Monroe’s most famous costumes and other paraphernalia from her most iconic films as well as personal items that may help reveal the woman behind the camera. Details: The exhibition opens May 31st and will run through February 28, 2027. You can find more information here. The guest: Sophia Serrano, associate curator for the Academy Museum of Motion Pictures who curated the Marilyn Monroe: Hollywood Icon exhibition. Visit www.preppi.com/LAist to receive a FREE Preppi Emergency Kit (with any purchase over $100) and be prepared for the next wildfire, earthquake or emergency

This week Andrew and Ted discuss the Netflix original Comedy / Romance feature "Ladies First", starring Sacha Baron Cohen and Rosamund Pike. Damien (Cohen) is an advertising executive left to think quick on his feet when one of their biggest clients is considering pulling their business because they just didn't think that the male only executives at the ad agency could come up with a campaign that targets women. Damien says that's not true because they just appointed a woman as "Creative Director", which they had not. When faced with this announcement Damien calls the office and randomly promotes Alex (Pike) to the position as merely a facade. A bump on the head leaves Damien believing that roles within not only the agency but his sphere have him believing that women now rule the world and his office. Alex and Damien have literally reversed roles at the agency and Damien searches for a way to return his world back to what it was before he bumped his head. Along the way Damien learns what its like to be woman in the workplace.

Hi, welcome to the Business of Apps podcast! Today, we have a special episode for you. We're featuring our recent webinar, presented by Aampe - agentic infrastructure for personalized experiences. It brings together four mobile growth leaders to cut through the AI hype and share what's actually working — from app user acquisition to retention. This session goes beyond buzzwords to unpack the real unit economics of AI-driven testing, the challenges of letting go of control, and what companies like Blinkist are learning on the ground as they make the shift from automation to agentic systems. Without any further ado, let's go! The topics covered on the webinar: The real value of ai in mobile growth today AI tools for non-technical teams What is agentic ai? (plain-english explanation) Feature's "press play": automated aso at scale Trust, control & human-in-the-loop From automation to agentic: what gets harder Building knowledge bases & setting guardrails Letting go of control: risk/reward balance Observability & attribution in agentic marketing Blinkist × amp: real-world agentic crm Strategic ai vs. execution ai Reinforcement learning explained  Final takeaways & recommendations The expert panel:

This week, Luke and Chelsea cover the movie that came and went, Ready or Not 2: Here I Come! The loooong awaited follow up to the first one that came out in 2019. Let's see if this felt worth the wait! This podcast is powered by ZenCast.fm

Most people assume the Fed controls interest rates. The bond market has a different opinion — and over the past several years, it's been winning. Understanding why that matters could change how you think about the whole life insurance policy you own, or the one you've been considering. When the Fed cut rates three times in 2024, the 10-year Treasury yield didn't follow. It rose. That disconnect isn't a glitch — it's the bond market pricing in inflation and fiscal risk that the Fed was slow to acknowledge. Bond vigilantes, as economists have called them since the 1980s, sell bonds to force yields higher when they disagree with central bank policy. It's happened before, and it's happening now. What most people don't realize is that whole life insurance is quietly one of the biggest beneficiaries of this dynamic. Life insurers hold massive bond portfolios, and as older bonds mature at yields of 3.6–3.7%, they're being reinvested at 5–6% and above. That reinvestment flywheel is still accelerating — and it flows directly into dividend scales. Every major mutual carrier has raised its dividend interest rate every year since 2023. Here's the part that surprises people: the lag that drives this works in your favor, whether you already have a policy or are considering one. If you own whole life, your dividends are rising and will continue to rise as more of the portfolio turns over at higher yields. If you're new to it, you haven't missed the window — the early years of any policy show the lowest dividend impact, and the tailwind will build throughout the life of your policy. ______________________________________________ If you'd like to talk through how this applies to your situation, schedule a call with us or send us a message—we're happy to walk you through it.

The Topic: Larry Mantle speaks with the stars of the new film Tuner, about a piano repair apprentice who suffers a unique hearing condition that makes him extra sensitive to sound: a useful skill for tuning pianos as well as cracking safes. The plot: Leo Woodall, plays Niki, a former music virtuoso now serving as an apprentice to the vivacious but stubborn piano technician Harry Horowitz, played by Dustin Hoffman. Niki’s hearing condition and secret extracurriculars isolates him from his budding relationship with music composition student Ruthie, played by Havana Rose Liu. Tuner is playing at the AMC Grove and AMC Century City. It expands to more theaters May 29. Visit www.preppi.com/LAist to receive a FREE Preppi Emergency Kit (with any purchase over $100) and be prepared for the next wildfire, earthquake or emergency

Instagram dropped a new real-time photo feature called Instants. Eerily similar to BeReal and Snapchat. The sōsh team has thoughts.Michelle, Ashley, and Maggie break down Instagram's newest rollout, and whether users actually want another social feature in an already crowded app. They also explore authenticity, doomscrolling, changing social habits, Gen Z behavior, and why more people may be stepping away from screens altogether.Also: A near-miss deer story, wine-fueled casserole making, and Zoom makeup filters.Comment, review, and subscribe if you like the show!Connect with Michelle on LinkedIn: ⁠linkedin.com/in/michelledattilio ⁠Learn more about sōsh: ⁠getsosh.com ⁠ 

Kenny Stoddart operates in the space where leadership is no longer theoretical. Where pressure compresses time, uncertainty clouds judgment, and the quality of a person's thinking becomes the difference between collapse and control. As the founder of IronMind Advisors, Kenny works with executives, founders, and high level operators who are expected to perform when conditions are unstable and the stakes are real. His work is not centered on inspiration, productivity hacks, or surface level mindset language. It is about mental command. The ability to remain clear, disciplined, and decisive when most people default to reaction. What Kenny identified through years alongside elite performers is that pressure does not create weakness. It exposes it. The issue is rarely intelligence or capability. It is internal interference, emotional static, fractured focus, and the gradual erosion of precision under sustained demand. The IronMind methodology was built to eliminate that erosion. To train leaders to think cleanly under pressure, regulate themselves in real time, and execute with a level of control that remains intact regardless of external volatility. His approach is sharp, restrained, and intentional. No noise. No performance theater. Just the cultivation of a mind that can carry weight without breaking under it. Because when everything intensifies, leadership is no longer measured by confidence in calm environments. It is measured by who can still think clearly when everyone else loses composure. Today's guest: www.ironmindadvisors.com Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Rusty Schlenk led most of the American Late Model Iron Man Series Friday night at Mansfield only to finish in the runner up spot and then went to Montpelier Speedway Saturday and won the Ultimate Heart of America Late Model feature. We speak with him on his weekend and his season. Plus all the latest racing news and results. Learn more about your ad choices. Visit megaphone.fm/adchoices

This week John Poz's TMPT welcomes into the show for the feature episode, former WWF personality and nemesis of Bobby "the Brain" Heenan, John DiGiacamo FKA Jameson Winger. Host John Poz and Jameson will discuss Primetime Wrestling, through the short lived Bobby Heenan Show and managing the Bushwackers, Jameson's story of how he landed in the WWF and his tenure is a great look inside one of the most successful era's in the history of the wrestling business. We also find out what Vince McMahon's reaction was to Jameson's son being used during the intense John Cena vs. Bray Wyatt storyline.Store - Teepublic.com/stores/TMPTFollow us @TwoManPowerTrip on Twitter and IG

AI is transforming healthcare workflows, but what is the best way to integrate it into physician workflows? Join Thea Campbell and Hari Bala as they discuss how to bring AI into clinical workflows to reduce clinician burden and create scalable, secure solutions for the future of healthcare.

Rebecca Davis joins John Maytham each week to reflect on just how strange the news can be. From the most important to the very strange, John and Rebecca offer their view of what is happening in our world that makes it at times infuriating, at times inspirational but always fascinating. Presenter John Maytham is an actor and author-turned-talk radio veteran and seasoned journalist. His show serves a round-up of local and international news coupled with the latest in business, sport, traffic and weather. The host’s eclectic interests mean the program often surprises the audience with intriguing book reviews and inspiring interviews profiling artists. A daily highlight is Rapid Fire, just after 5:30pm. CapeTalk fans call in, to stump the presenter with their general knowledge questions. Another firm favourite is the humorous Thursday crossing with award-winning journalist Rebecca Davis, called “Plan B”. Thank you for listening to a podcast from Afternoon Drive with John Maytham Listen live on Primedia+ weekdays from 15:00 and 18:00 (SA Time) to Afternoon Drive with John Maytham broadcast on CapeTalk https://buff.ly/NnFM3Nk For more from the show go to https://buff.ly/BSFy4Cn or find all the catch-up podcasts here https://buff.ly/n8nWt4x Subscribe to the CapeTalk Daily and Weekly Newsletters https://buff.ly/sbvVZD5 Follow us on social media: CapeTalk on Facebook: https://www.facebook.com/CapeTalk CapeTalk on TikTok: https://www.tiktok.com/@capetalk CapeTalk on Instagram: https://www.instagram.com/ CapeTalk on X: https://x.com/CapeTalk CapeTalk on YouTube: https://www.youtube.com/@CapeTalk567 See omnystudio.com/listener for privacy information.

We often hear the ideas of great thinkers, but rarely get to understand how they actually think or who they are as people.In this episode of The Courageous Leaders Podcast, I am joined by Rory Sutherland, President Emeritus of Ogilvy UK, best-selling author, and one of the most influential voices in advertising, behavioural science, and decision-making.If you've ever wondered why some ideas take off and others die fast, why the little things in business matter more than you think, or how to rethink productivity for your team, you'll find something practical and eye-opening in this conversation. We cut through business theory and get honest about human behaviour, team culture, and leadership decisions that work in the real world.You'll come away with new ways to look at decision-making, organisational performance, and what it takes to lead bravely in uncertain times, especially with the rise of AI, complexity, and shifting workplace cultures.What We Cover:00:00 Intro01:41 Dare to Be Trivial: Why Small Things Matter13:23 Leadership, Influence & The Power of Great Teachers14:50 Why Business Is Learned Through Real Experience18:03 Time, Stress & How Rory Thinks About Control24:12 Creativity, Uncertainty & Not Knowing Yet28:00 What Leaders Miss in Strategy & Collective Thinking30:17 Why Human Businesses May Win in an AI World34:51 Why Teams Fail & The Problem with Over-Measuring35:45 The Disappearance of PAs & What It Means for Leaders36:55 Redundancies & The Danger of Short-Term Thinking40:34 How Rory's Mind Works & Why He Avoids Talking About Himself49:45 The Influence of His Mum & Understanding Human Behaviour51:22 Neurodiversity Is a Feature, Not a Bug54:24 Final Reflections & Closing ThoughtsKey Leadership Insights• Why great leaders focus on influence, not control• How creativity comes from being comfortable with uncertainty• Why measuring individuals destroys team performance• The hidden cost of short-term thinking in leadership• How silos quietly break organisations from within• Why neurodiversity is a competitive advantage, not a weakness• The courage required to back ideas others doubt• Why founder-led businesses often outperform corporatesIf you want to lead better, think differently, and understand how great leaders actually operate, this episode will challenge how you see leadership.

Ntiaj teb lub koom thiab teb chaws Democratic Republic of Congo (DRC - Congo) ho muaj tej xub ke li cas los tswj kom tus kab mob Ebola tsis txhob sib kis.

Tseem muaj cov kev sib cav txuas ntxiv txog lub neej pem suab ntawm Australia tej tax system tom qab limtiam dhau los uas tsoom fwv Albanese tau qhia nws tej nyiaj puag xyoo 2026-27 uas tus nom tswj nyiaj txiaj rau tsoom fwv teb chaws Australia ua tib zoo qhia txog nws cov kev kho peb co se rau cov negative gearing, capital gains tax thiab trusts. Tib lub caij no los pab nom koom tswj kuj tau los qhia txog nws tej nyiaj puag xyoo uas tsuas tos tej neeg txawv teb chaws tuaj raws li tej vaj tse ua tau tshiab, yuav tsis pub tej neeg nyob ruaj uas tseem tsis tau yog pej xeem Australia siv 17 cov kev pab welfare programs, yuav siv nyiaj ntau tuaj ntxiv los pab hauj lwm tub rog thiab xyuas kom Australia tau roj tsheb thiab gas ntau thiab pheej yig siv. Ua ke no los nws yuav tso tseg thiab tsis siv tsoom fwv Albanese cov kev kho tej se no.

Australia tej hluas yog cov yuav ntsib teeb meem rau tsoom fwv teb chaws tej nyiaj puag xyoo 2026-27 uas xav los kho tej se capital gains tax txo rau cov kev ua lagluam muag vaj tse thiab cov kev siv negative gearing los nqes peev lagluam. Thiab ua rau lawv tsis muaj peev xwm siv tau tej xub ke no los pab kom lawv nplua nuj rau yav pem suab li tej laus. Tej kws paub zoo txog tej hauj lwm no txhawj tias tsam yuav ua rau muaj qee yam teeb meem tsis nco faj thiab ua rau tej hluas qev tsis tau nyiaj yuav tsev, ces yuav tsis tau thawj lub tsev nyob thiab yuav ua rau tej nqe ntiav tsev kim tuaj ntxiv. Txawm li cas los ib txhia kuj xav tias yuav pab kom lawv muaj peev xwm yuav thawj lub tsev nyob thiab, uas tsoom fwv thiab cov kev kho tej se no yuav pab tsim kom tau vaj tse ntau tuaj ntxiv rau tej neeg yuav thawj lub tsev nyob.

In this Circles Off Q&A, Rob Pizzola is joined by Plus EV Analytics, Matt Buchalter, for a deep dive into sports betting modeling — how it actually works in practice, what separates good models from bad ones, and how sharp bettors think about building and evaluating their edge. This episode is built around 10 of the toughest modeling questions pulled directly from Circles Off content and community discussion. The conversation covers how to start a model from scratch, when a model is strong enough to bet real money, and how to deal with early season uncertainty like small samples, roster turnover, and regression questions. Rob and Matt also explore what matters more between getting the mean right or the distribution right, how to think about closing line value thresholds, and how to separate variance from a broken edge when results turn against you. They also get into Bayesian vs frequentist thinking, how professional bettors evaluate their models over time, and which inputs are often overrated or underrated when building a betting model. For anyone serious about sports betting models, market pricing, or long-term edge creation, this is a practical, sharp breakdown from two experienced voices in the space. Subscribe to Circles Off for more sharp betting conversations, modeling breakdowns, and market analysis.

Join Ste for Redmen Bitesize as he discusses Liverpool's Champions League hopes getting a major boost, plus the Reds who could be making their final Anfield appearances on Sunday! Hosted on Acast. See acast.com/privacy for more information.

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

The tributes keep flowing for Scott Pendlebury as the footy world celebrates another milestone for the Collingwood great. Gary Lyon questions the Crows’ latest selection calls, while anticipation builds for a blockbuster clash between the Swans and Cats. Plus, is it make-or-break time for St Kilda as pressure mounts on the Saints heading into a crucial stretch of the season?See omnystudio.com/listener for privacy information.

Electric Callboy join the show to talk about their new album Tanzanite, the meaning behind “dance envy,” secret features, viral music videos, and how they turned chaos, humour, and creativity into one of the biggest live experiences in modern heavy music. We also dive into cinematic video production, life on tour, the mystery pink box, classic rock debates, and why every Electric Callboy song has to work as a full 360° experience.Don't forget to bang your head on the links belowTikTokhttps://www.tiktok.com/@jesealee Instagramhttps://www.instagram.com/jesealee/ Podcast available on Spotify, YouTube, Apple Music and everywhere else you consume podcastsProduction by WhatTheGleeson https://www.instagram.com/whatthegleeson/Theme song by Michael Stoutengerhttps://open.spotify.com/artist/6LO5e...Subscribe to my newsletter:https://jesealee.substack.com/Everything else:https://www.jesealee.com/

Follow Emil on LinkedIn & Twitter (X) Learn more about FlashPass: flashpass.com (or search FlashPass upskilling) 00:00 FlashPass: Upskilling for the AI Era 02:08 From Dorm Room to Millions: Emil's Origin Story 03:47 The $65K Summer: Tennis, COVID & Finding His Lane 07:01 What Is FlashPass? Upskilling America for the AI Era 10:27 AI Won't Just Take Jobs — It's a Feature of Progress 12:40 How FlashPass Works: Intake, Upskill, Match 14:44 Bipartisan Support & Scaling to 20% of America 15:29 Building Courses with Industry Partners 16:49 Working with Government & What's Next 18:30 Where to Find Emil Connect with me on:All my linksBecome a guestSign up for RiversideGet Descript #DigitalMarketing #Branding #PersonalBranding #MarketingInsights #SocialMediaStrategy Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

-Meta HR head Janelle Gale has notified employees that 7,000 of them will be moved to four new organizations focused on building new AI tools and apps. -LinkedIn has long been on the frontlines of the AI slopidemic. Now, the company is taking new steps to reduce the reach of posts that bear the hallmarks of AI-generated drivel. -Apple is previewing new accessibility features including Apple Intelligence-powered updates like natural language voice input, along with a new Vision Pro app that allows eye control for motorized wheelchairs Learn more about your ad choices. Visit podcastchoices.com/adchoices

Peter Thiel gibt keine Ruhe. In geheimnisumwitterten „Antichrist-Vorlesungen“ schart er Jünger auf der ganzen Welt um sich. Er investiert verstärkt in Militärtechnik, kämpft gegen die Besteuerung von Superreichen und pflegt sein politisches Netzwerk. Von Fritz Espenlaub, Jasmin Körber, Christian Schiffer und Klaus Uhrig www.deutschlandfunkkultur.de, Feature

In Christins Tattoostudio werden Lebens-, Leidens- und Verlustgeschichten auf die Haut graviert. Die Chefin bietet allen einen sicheren Ort. Doch als der Krebs kommt, braucht Christin selbst Hilfe. Von Gülseren Sengezer www.deutschlandfunkkultur.de, Feature

Catch up on all the footy news from AFL 360, Tuesday 19th of May with Gerard Whateley and Garry Lyon. On AFL 360 Gerard Whateley and Garry Lyon break down all the major new in the world of AFL as Hawthorn is asked to end its partnership with Tasmania. While pressure mounts on Essendon head coach Brad Scott as the Bombers lose their 22nd in 23 games. For more of the show tune in on Fox Footy & KAYO.See omnystudio.com/listener for privacy information.

Aubrey Masango joined by Lwandile Nkanyuza, Creative Entrepreneur, Musician, Author discuss how creatives can better manage their businesses, their time, their money, and themselves, while still protecting the very thing that makes them creative in the first place. Tags: 702, Aubrey Masango show, Aubrey Masango, Bra Aubrey, Entrepreneurship feature, Lwandile Nkanyuza, Creative Entrepreneur, Freelancer, Independent creative The Aubrey Masango Show is presented by late night radio broadcaster Aubrey Masango. Aubrey hosts in-depth interviews on controversial political issues and chats to experts offering life advice and guidance in areas of psychology, personal finance and more. All Aubrey’s interviews are podcasted for you to catch-up and listen. Thank you for listening to this podcast from The Aubrey Masango Show. Listen live on weekdays between 20:00 and 24:00 (SA Time) to The Aubrey Masango Show broadcast on 702 https://buff.ly/gk3y0Kj and on CapeTalk between 20:00 and 21:00 (SA Time) https://buff.ly/NnFM3Nk Find out more about the show here https://buff.ly/lzyKCv0 and get all the catch-up podcasts https://buff.ly/rT6znsn Subscribe to the 702 and CapeTalk Daily and Weekly Newsletters https://buff.ly/v5mfet Follow us on social media: 702 on Facebook: https://www.facebook.com/TalkRadio702 702 on TikTok: https://www.tiktok.com/@talkradio702 702 on Instagram: https://www.instagram.com/talkradio702/ 702 on X: https://x.com/Radio702 702 on YouTube: https://www.youtube.com/@radio702 CapeTalk on Facebook: https://www.facebook.com/CapeTalk CapeTalk on TikTok: https://www.tiktok.com/@capetalk CapeTalk on Instagram: https://www.instagram.com/ CapeTalk on X: https://x.com/CapeTalk CapeTalk on YouTube: https://www.youtube.com/@CapeTalk567See omnystudio.com/listener for privacy information.

Die Enthüllungen von WikiLeaks haben für Aufsehen gesorgt. Das gilt ebenso für die Verfolgung des Wikileaks-Gründers Julian Assange durch die USA. In ihrem Feature berichten die Journalistin Lea Eichhorn und der Journalist John Goetz über das Bestreben, geheime Informationen der Öffentlichkeit zugänglich zu machen – und darüber, wie das für Assange zu einem Kampf um seine Freiheit wurde. Im Gespräch mit Palina Milling erzählen sie von den Folgen dieser Auseinandersetzung für Julian Assange. Sie gehen auch darauf ein, wie Wikileaks die Recherchearbeit der Medien verändert hat und was der Fall Assange für den Investigativjournalismus bedeutet. Von Palina Milling.

Ben Cotton, Jack Jovanovski and Ben Waterworth break down some stunning results from the weekend, including whether the Dogs are in strife, the Lions' three-peat hopes are cooked and whether the Demons can dare to dream. Plus a full preview of Round 11 of the 2026 AFL season, Fair or Farce and much more.See omnystudio.com/listener for privacy information.

Tesla has begun an initial rollout of a long-asked-for Supercharging feature. Plus: Tesla expands battery production at Giga Berlin, BMW hits an EV milestone, and more! If you enjoy the podcast and would like to support my efforts, please check out my Patreon at https://www.patreon.com/teslapodcast and consider a monthly or (10% discounted!) annual pledge. Every little bit helps, and you can support for just $5 per month. And there are stacking bonuses in it for you at each pledge level, like early access to each episode at the $5 tier and the weekly Lightning Round bonus mini-episode (AND the early access!) at the $10 tier! And NO ADS at every Patreon tier! WIN AN EV WHILE GIVING TO A GREAT CAUSE: For your chance to win your dream EV in the 2026 ChesedChicago raffle, head to https://tinyurl.com/CCraffleRTL -- Hurry, tickets are limited and only 9,999 tickets will be sold, get your tickets today and use code RTL for $25 off 2 tickets or $500 off 15 tickets. Whether you win or not, you're helping a great organization help families in need. Also, don't forget to leave a message on the Ride the Lightning hotline anytime with a question, comment, or discussion topic for next week's show! The toll-free number to call is 1-888-989-8752. INTERESTED IN A FLEXIBLE EXTENDED WARRANTY FOR YOUR TESLA? Be a part of the future of transportation with XCare, the first extended warranty designed & built exclusively for EV owners, by EV owners. Use the code Lightning to get $100 off their "One-time Payment" option! Go to www.xcelerateauto.com/xcare to find the extended warranty policy that's right for you and your Tesla. P.S. Get 15% off your first order of awesome aftermarket Tesla accessories at AbstractOcean.com by using the code RTLpodcast at checkout. Grab the SnapPlate front license plate bracket for any Tesla at https://everyamp.com/RTL/ (don't forget the coupon code RTL too!). Enhance your car with cool carbon-fiber upgrades from RPMTesla.com and use the promo code RTL5-10 for 5-10% off your next purchase. And make your garage door foolproof with the Infinity Shield – get yours at https://www.infinity-shield.com and use the promo code RTL at checkout for a $35 discount.

[A crosspost with Hollywood Woketopia, my other Substack]Every so often, a moment in culture arrives, a Sydney Sweeney ad, or Project Hail Mary. Every time, we hear that the Woke fever has finally broken. Hollywood cares about the people again. Right?The same reason Kamala Harris is likely to be the nominee in 2028, the same reason the Democrats are still selling the lie that any kind of attempt by Republicans to even out the redistricting is “Jim Crow 2.0,” is proof enough that on the Left, Woke is not going anywhere. It is who they are now. Not all of them, but the most powerful among them.Early on, when Mark Halperin and others were insisting Gavin Newsom would be the nominee in 2028, I said there was no way the Democrats would get behind a white guy, no matter how passionately he genuflects to the Woke (“Anti-woke is anti-black!”). I know the Democrats. I was one. I helped build the modern-day party of the Great Feminization and the Great Awokening. I know what fires them up every day, and it isn't just taking back power; it's foisting their religion upon the rest of us.They think it's the opposite, that it's the Right that is foisting their “Christian Nationalism” upon them. While it's true that a faction of the Right has unmasked to become the very thing Rob Reiner warned about in his movie, God and Country, they aren't the majority. Perhaps that's true on the Left. But look around. Their religion is the dominant culture in America.When news got out that Christopher Nolan had cast Lupita Nyong'o as Helen of Troy, the “most beautiful woman in the world,” whose face launched a thousand ships, it ignited yet another culture war. How you reacted was like whether or not you wore a mask outside in 2020. It was a test. You're on one side, or you're on the other. Notice it, comment on it, object to it, criticize it, and you're one of the bad people to be purged. And if that weren't enough, Nolan brought back Ellen Page from Inception, now recast as Elliot Page, the male, as an act of affirmation and yet another test. These are Orwellian 2+2=5 and force people to choose between ignoring it and going to see a big-effects movie in IMAX, or not buying a ticket and boycotting the film. Elon Musk took the bait, becoming the villain Hollywood needed to turn seeing The Odyssey into a righteous and political act. You can see them now: the bearded male feminists buying tickets ten times in a row. “Take that, Elon Musk!” The ladies of Blue Sky will go in groups, then fawn over how beautiful Lupita Nyong'o is and overuse the male pronoun for Ellen/Elliot Page. “Wasn't he great?”The game is becoming exhausting by now, as Hollywood demands the hard-working American public be impressed by them, lectured by them, and corrected by them. All audiences really want is the one thing Hollywood seems unable to accomplish: entertain them.It isn't that Nyong'o isn't pretty. She is. It's that Helen of Troy was white, famously so, even if Greek. Nyong'o is a unique beauty, not a universal one, a reality the Left wants to force, because Hollywood doesn't care about its audience. They want to look good.Probably the worst thing about the game Hollywood plays with the movie fans they helped raise is that Lupita Nyong'o is held out as a sacrificial lamb. She isn't pushing any ideology, unlike Ellen/Elliot Page. They are putting her out there and expecting her to absorb criticism about herself, including whether she is pretty enough. I met her once, back in 2013 in Telluride, before her career took off. She was too young to know how to act like a celebrity. She was so nice, I was won over. She would win an Oscar that year and become a big star in Hollywood. Is it fair to put her in this position just so they can feel good about themselves? No. Does it change anything? No. There is still such a thing as truth and reality, even if that is the thing that is unfair. The Woke Code and the Hays CodeThe Hays Code (1930-1968) represented an era wherein decency and morality were mandated in all Hollywood films. The Christian conservatism/morality mandated by the Hays Code reflected less a separation between art and governance and more a united effort toward a utopian society of goodness, especially as we moved through the last Fourth Turning, the Great Depression, and World War II, a time where the world saw true evil in Hitler and Stalin, not to mention the nuclear bomb.That isn't all that different from what the Woke Code is now. It's roughly the same kind of thing: rigid rules to depict an ideal society. The difference is that Christian advocates have been replaced by progressive activists, and the villain is the white male patriarchy. What is different now, amid our current Fourth Turning, is that the Woke Code includes only half of America. To the Left, they would rewrite this narrative to say that Hollywood depicted mostly White America, and that is what has changed. But really, if you respond to the box office, as Hollywood doesn't anymore, you will always default to the majority. It isn't rocket science — beautiful, sexy women and masculine men and a great story.The end of the Hays Code was entirely due to economics. Television became so popular in the 1950s that there wasn't much of a need to go to the movies if all you saw was the same kind of buttoned-up themes you could see on TV. That's true now, too. Movies, then, had to break out of the Hays Code and become much more subversive, leading into the 1970s, which saw some of the best films ever made. While it's true that The Odyssey will be eligible to win Oscars under the new rules, it's also true that the criteria could have been met in a way that didn't make audiences play this same exhausting game that has alienated them from everything Hollywood puts out. The casting of Nyong'o and Page is less about Oscars and more about status. Perhaps Nolan was under pressure to cast a non-white woman as Helen, or maybe he wants to be seen as a good person using his wealth and fame to make change, as the most famous white male directors reach for things money can't buy, like Martin Scorsese making Killers of the Flower Moon, Steven Spielberg making West Side Story with a real Latina, and Paul Thomas Anderson's Peak Woke Best Picture winner, One Battle After Another.No film has better exemplified Hollywood in the Trump era than this one. It says it all. ICE as the Gestapo, check. America is run by a cabal of wealthy white Nazis, check. A woman of color must save herself, check. All of it is held together by a hapless white man, Leonardo DiCaprio, who represents the film's beating heart. He's the only good white guy, which is how those in Hollywood who make these kinds of choices would like to be seen. One Battle is actually a movie about them.Had Nolan cast a blue-eyed blonde woman as Helen of Troy, all hell would have broken loose. When you go against the rules of the Woketopia, you aren't just getting hit on X with lots of angry tweets by loyal fans who continually feel betrayed; they bring out the big guns - agonizing op-eds in the New Yorker, for instance. If you obey the rules, then you are praised. The problem is that it all feels so artificial, so pre-planned, so inorganic.I used to write the Oscars report for Jane Fonda's Women's Media Center (who fired me after they found out I voted for Trump), counting the number of female nominees and winners. The statistics were always grim. Every year, it was bad news. As things began to change for women after the Academy announced its DEI mandate in 2020, that change was forced. If before merit had made too many white men winners, now we were seeing something a little closer to gender parity. So then the line moved back, and it became not just about women but women of color and trans women. Now, it's all about Marxism disguised as art. If life isn't fair, movies will make it fair. It isn't just because the Oscars have it written into their new rules, and it isn't just because activist groups like GLAAD breathe down the neck of every Hollywood studio, counting heads and making reports. It's that this is a deeply felt belief system that isn't going anywhere anytime soon. I have no doubt The Odyssey will make money. It's a Christopher Nolan film, after all. Who doesn't want to go see a giant visual effects epic filmed entirely on IMAX? If you can ignore the elephant in the room, the performative casting, you might have a great time. But if you were hoping that Woke is over, well, I think that was its own Hollywood fairy tale. It's why Kamala Harris was the nominee in 2024 and why she will once again be the nominee in 2028. This is how the ruling class in America wants to be represented. They want to force change, and they do that by elevating minority groups to high-status positions as symbols for the mostly white people who run things.Culture, like the Democratic Party, will have to be built anew. That, more than anything, explains why AI is about to completely consume the business, becoming the subversive counterculture revolution Hollywood never saw coming. They can do it all and more without the millions of dollars necessary to mount a production. AI artists don't have to be held to the same rigid standards. They can be purely about bringing in eyeballs by showing what people most want to see, rather than what Hollywood wants them to want to see. In other words, they can make the women as beautiful as they want, and no one can cancel them for it. I spent my life in movie theaters gazing up at the big screen and watching some of the best films ever made. The only way that makes sense is if you are escaping real life and finding your way into a fantasy world, and maybe for the Woke, seeing Lupita Nyong'o cast as the most beautiful woman in the world is its own kind of fantasy fulfillment. After the movie comes out, we'll have to see whether it works or not. At the moment, it feels like just another test to decide who gets to stay and who has to go. This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.sashastone.com/subscribe

PREVIEW for Later Today: Bob Zimmerman discusses a mysterious "brain terrain" image from Mars. He explains that scientists are unsure if the feature was formed by volcanic activity or ice sublimation, emphasizing the need for future geological exploration.FEBRUARY 1955

The topic: Movies on film are having a resurgence. Just take late year’s biggest movies: One Battle After Another, Sinners, and Marty Supreme. But the craft of screening movies on film is a dying one, with few projectionists experienced enough to handle the delicate prints. A film stronghold: In L.A., it's the local repertory theaters that have helped maintain the art of film projection with many offering screenings of old movies on vintage prints. The task may be tedious, but for audiences, it’s a striking viewing experience. Guests: Spencer Christiano, a senior projectionist at the Academy Museum of Motion Pictures and Boris Ibañez, technical director of Vidiots, a repertory theater and DVD/video rental store in Eagle Rock. Visit www.preppi.com/LAist to receive a FREE Preppi Emergency Kit (with any purchase over $100) and be prepared for the next wildfire, earthquake or emergency

Should you stay or should you go? Relationship ambivalence is very painful and very common. In this episode of Perpetual mOtion, Dr. mOe Anderson and relationship coach Merideth Thompson, PhD, the CEO of the Partner Lab, delve into the complexities of rocky relationships and explore how individuals can find clarity in their romantic lives.   Listen in to learn key factors to consider when selecting a partner based on relationship science, not your gut instincts. The conversation emphasizes the significance of emotional intelligence, the recognition of unhealthy patterns, and the necessity of accountability in relationships. Listeners are encouraged to reflect on their own relationship dynamics and consider mindset shifts that can lead to healthier connections.   Sound Bites "Indecision is not wisdom." "Accountability is sexy."   Takeaways Science shows that commitment perception is crucial in relationships. Emotional intelligence is essential for navigating relationship challenges. Recognizing patterns in relationships can lead to better decision-making. Accountability in relationships is vital for growth and trust. Indecision often stems from fear and can lead to emotional exhaustion. It's important to differentiate between solvable and perpetual problems in relationships. Personal experiences can shape professional approaches to relationship coaching. Mindset shifts can empower individuals to create healthier relationships.   Connect with Dr. Thompson and learn more on her website [https://www.mypartnerlab.co/]   Would you like to be a guest on this podcast? Join Podmatch and get access to this show and 1000's of other podcast hosts looking for guests to interview. https://www.joinpodmatch.com/perpetualmoetionwdrmoeanderson    Learn more about Dr. mOe's services and books on her website at www.drmOeAnderson.com. Follow us on social media!  @drmOeanderson Elevate your public speaking skills with 1x1 or online Public Speaking Coaching (https://drmoeanderson.com/coaching/) Feature your business on this award-winning podcast or book Dr. mOe for a speaking engagement! Contact us today! info@drmoeanderson.com Please support this indie, woman-owned, small business providing free educational and inspirational content. Use one of these secure, fee-free ways to support the production and distribution of this award-winning show:  1. Buy Me a Coffee: https://buymeacoffee.com/drmoeandu 2. CashApp: $drmoeanderson 3. Venmo: @drmoeanderson  

Lisa Kurdrow calls out Andy Cohen for "faking" a scene in Real Housewives of Beverly Hills. Kaelin tells us an all new feature on TikTok!See omnystudio.com/listener for privacy information.

These episodes of #thePOZcast, live from Transform 2026 in Las Vegas, are proudly brought to you by our friends at PIN. AI recruiting tools that automate candidate sourcing, screening, and scheduling across 850M+ profiles. Built for recruiters, agencies, and hiring teams. Learn more and check out a demo:  https://www.pin.com/book-a-demo?via=adam-posner Thanks for listening, and please follow us on Insta @NHPTalent and www.youtube.com/thePOZcast For all episodes, please check out www.thePOZcast.com TAKEAWAYS:  1. Same Tools, Same Results — You Have to Rebuild the Engine The insight at the heart of Pin: giving AI the same Boolean search infrastructure that human recruiters use produces the same mediocre results, just faster. The only way to get genuinely better outcomes is to rebuild the search engine itself so that AI can operate on a fundamentally different foundation. That's what Pin did — and why the results look different. 2. The Best Candidate Should Be First, Not on Page Seven The clearest signal that a recruiting search tool is working: the most qualified candidate for a role appears at the top of results, not buried deep in a list that requires manual excavation. For recruiters who've spent years digging through pages of search results, seeing the right person in slot one is a genuinely disorienting experience — in the best way. 3. Natural Language Filtering Closes the Gap Between Search and Judgment Standard filtering tools handle objective criteria — location, tenure, title. Pin's natural language feature handles the subjective judgment calls that used to require hours of resume scanning: the specific details that determine whether a candidate is actually worth a call. Resolving those questions in two questions or fewer is a meaningful time return for high-volume recruiters. 4. Pattern Recognition Learns Even Without Feedback — But Feedback Makes It Faster Pin's algorithm doesn't require explicit feedback to improve — it reads behavioral patterns in what recruiters accept and reject and adjusts accordingly. But providing reasons for rejections accelerates the learning dramatically. The system is watching, learning, and tuning, whether or not you tell it why. 5. The Curveball Candidate Is a Feature, Not a Bug Periodically surfacing a candidate who sits just outside the current search parameters isn't an error — it's deliberate calibration. When a recruiter declines that candidate, Pin learns where the line actually lies, resulting in increasingly precise results over time. The tool is always running a low-stakes experiment to get better. 6. A Visual Pipeline Changes How You Manage a Search Pin's upcoming Kanban board — drag-and-drop stages from interested through offer made — addresses one of the most persistent frustrations in recruiting: knowing at a glance where every candidate stands without digging through notes or spreadsheets. Pipeline visibility is a workflow problem as much as a sourcing one. 7. MCP + Claude Desktop = Autonomous Sourcing The MCP Server integration is the most forward-looking announcement in this episode: the ability for Claude Desktop to run Pin autonomously, without manual recruiter input, using Claude's broad knowledge base to execute searches and surface candidates. For business development and high-volume sourcing, this is autopilot for the top of the funnel. 8. The Second Company Is Easier Because the Team Already Knows How to Build Together Steven's team story is a blueprint for founder-led companies: seven people from his first venture joined him at Pin, bringing a shared language, shared trust, and a shared understanding of what works and what doesn't. The result is what Steven calls "life on easy mode" — not because the work is easier, but because the team already knows how to do it together. 9. Always Give Feedback to Your AI Tools Every rejection is a data point. Every accept is a signal. The recruiters getting the best results from AI-powered search tools are the ones who treat the interface as a two-way conversation — providing context, reasons, and reactions that train the system toward increasingly precise output. Passive use gets passive results.   CHAPTERS: 00:00 – Day 9: The Return of Steven Lu Adam, on day 9 of 10 at Transform, welcomes back Steven Lu — a returning guest and the founder of Pin, the recruiting AI tool Adam uses every day. 02:00 – Why Giving AI Boolean Tools Gets You Boolean Results The core problem Pin was built to solve: if you give AI the same search tools as a human recruiter, you get the same results. Pin rebuilt the search engine itself so AI could actually deliver better outcomes. 04:30 – The Aha Moment: Best Candidate, Slot Number One What clients experience when they switch to Pin: the best candidate for the role appears first — not buried on page seven. 06:30 – Natural Language Questions That Answer the Hard Stuff How Pin's natural language feature goes beyond standard filters — answering the nuanced, make-or-break questions about a candidate in two questions or less. 09:00 – Pattern Recognition: Learning From Every Rejection Pin's behind-the-scenes intelligence: even without explicit feedback, the platform picks up on recruiter behavior patterns and adjusts results automatically. 12:00 – The Curveball Candidates Why Pin intentionally surfaces occasional outlier candidates — to test parameters, refine the algorithm, and deliver increasingly precise results over time. 14:30 – Alpha Drop: The Kanban Pipeline Board Feature 1 in development: a visual Kanban board for tracking candidates through the hiring pipeline with full drag-and-drop functionality. 17:00 – Alpha Drop: MCP Server + Claude Desktop Integration The bigger announcement: Pin is building an MCP Server integration that allows Claude Desktop to run Pin autonomously — putting AI-powered sourcing on autopilot. 20:00 – The Team Behind Pin: Seven People Who Followed Him Seven employees from Steven's first company joined him for Pin — and that shared experience is what makes the second company feel like "life on easy mode." 22:30 – Real Results: Fees Collected, Offers Made The feedback that hits hardest: fee emails arriving up to 20 a day, and Adam's live proof point — three Pin-sourced candidates getting offers by end of the week. 24:30 – Where to Find Pin A direct listener recommendation: try pin.com, mention Adam and Steven, and see what a rebuilt search engine actually delivers.  

Summary In this episode, Andy welcomes back Steve Kahle, entrepreneur, executive, and fractional CIO, author of Leadership Recall: Harness Insights. Accelerate Innovation. LEAD WITH AUTHORITY. Steve first joined the podcast in episode 184 to discuss email overload. This time, the conversation turns to a challenge every leader faces: the forgetting curve. Research suggests we forget up to 83% of what we learn within a week, and Steve argues this is not just a learning problem, it's a leadership problem. Steve shares his CCR framework (Capture, Catalog, and Recall), along with practical tools such as the Anki flashcard app and the Email Me voice-note app, to build what he calls a learning operating system. The discussion covers how to design a recall fitness practice in as little as three minutes a day and how removing friction at every step keeps the system sustainable. If you're looking for a practical system to stop letting great insights slip away and start leading with more authority, this episode is for you! Sound Bites "I think God put in my heart to be a relentless optimizer. I like to see things work and work well." "When you really zoom out in life, those who are really successful have figured out what are the frameworks, what are the methodologies that work, and they simply apply those." "Our subconscious mind can handle about 11 million bits of data per second, but about 40 bits conscious mind." "I went all in. Christ totally transformed my heart, and I'm realizing that scripture memory is a superpower." "Time swiftly washes away the obvious." "Learning really is a privilege, and we need to be able to find time that works with our daily rhythms." "Three minutes a day is really all you need to be able to see tremendous traction on being able to recall things that matter" "Instead of 'I'm bad at remembering names,' you could, do a reframe like, 'Hey, I'm getting better at remembering people's names.'" Chapters 00:00 Introduction 01:48 Start of Interview 02:06 Early Experiences and the Instinct to Remember 04:08 Is Memory a Natural Gift or a Trainable Skill? 05:19 Forgetting as a Feature, Not Just a Bug 07:10 The Leadership Cost of Forgetting 09:10 Shifting the Bottleneck from Input to Retention 12:02 The Five-Hour Rule and Three Learning Archetypes 14:19 The CCR Framework in Practice: Capture, Catalog, and Recall 19:50 Removing Friction from Your Learning System 23:23 Inside Anki: Cloze Deletions and Building Cards 26:10 Organizing Your Recall Decks 27:30 Real-World Results: When Readers Apply the System 28:56 Building Recall Habits in Your Kids 32:50 How to Get the Book 34:01 End of Interview 34:17 Andy Comments After the Interview 37:46 Outtakes Learn More You can learn more about Steve and his work at leadershiprecall.com. For more learning on this topic, check out: Episode 184 with Steve Kahle. It's our previous conversation about keeping your head above water when drowning in email and commitments. Definitely recommend checking it out. Episode 411 with Laura Mae Martin. She's the head of productivity at Google and shares ideas that I still use to this day. Episode 376 with Nick Sonnenberg. It's a book about helping you and your team stop drowning in all the information and commitments at work. Chat with PMeLa You can chat directly with PMeLa—the podcast's AI persona—to get episode recommendations and answers to your project management and leadership questions. Visit PeopleAndProjectsPodcast.com/PMeLa to chat with her. Pass the PMP Exam If you or someone you know is thinking about getting PMP certified, we've put together a helpful guide called The 5 Best Resources to Help You Pass the PMP Exam on Your First Try. We've helped thousands of people earn their certification, and we'd love to help you too. It's totally free, and it's a great way to get a head start. Just go to 5BestResources.PeopleAndProjectsPodcast.com to grab your copy. I'd love to help you get your PMP this year! Join Us for LEAD52 I know you want to be a more confident leader–that's why you listen to this podcast. LEAD52 is a global community of people like you who are committed to transforming their ability to lead and deliver. It's 52 weeks of leadership learning, delivered right to your inbox, taking less than 5 minutes a week. And it's all for free. Learn more and sign up at GetLEAD52.com. Thanks! Thank you for joining me for this episode of The People and Projects Podcast! Talent Triangle: Power Skills Topics: Leadership, Memory, Learning, Productivity, Knowledge Management, Recall, Spaced Repetition, Personal Development, Continuous Learning, Networking, Project Management The following music was used for this episode: Music: Imagefilm 034 by Sascha Ende License (CC BY 4.0): https://filmmusic.io/standard-license Music: Tuesday by Sascha Ende License (CC BY 4.0): https://filmmusic.io/standard-license

Hour 2 of Scotty G. & The Coach with Scott Garrard and Tim LaComb. Bob Casper, Real Golf Radio G, B & U: Broncos vs Chiefs for Monday Night Aronimink will be a challenge at the PGA Championship

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