Podcasts about Template

Hiring the right team members can feel like searching for a needle in a haystack, especially when the candidates you're attracting aren't who you hoped for. In this episode of the Business of Apparel podcast, Rachel explains why attracting poor job candidates is often the result of a weak or generic job description rather than a lack of talent in the market. She shares how apparel brand owners can attract A-player employees by focusing less on qualifications and more on the outcomes, goals, and opportunities a role provides. 

Watch on YouTube Carson Bruce wraps up the piano sample library tutorial series by showing how to move a finished Logic Pro X Sampler patch into MainStage for live performance. He walks through locating and copying the patch from the Logic user library, pasting it into the MainStage patches folder, and loading it into MainStage. He also demonstrates how the patch works in perform mode and explains how MainStage allows you to control and solo different mic and noise channels like CAD mics, Rode stereo, close mics, pedal noise, and release triggers to customize the sound.Aerospace AudioSpotifySign up to get the free templateSupport the showThanks for listening! Subscribe here to the podcast, as well as on YouTube and other social media platforms. If you have any questions or suggestions for who you want as a featured guest in the future or a topic you want to hear, email carson@theworshipkeys.com. New episodes release every Wednesday!

God's Template for Winning in Life: Cracking the Code of Time and Chance | Phaneroo Service 582 | Apostle Grace Lubega.

God's Template for Winning in Life: Cracking the Code of Time and Chance | Phaneroo Service 582 | Apostle Grace Lubega.

Carolyn Woodard covers a landmark moment in the global conversation about AI governance: the release of Pope Leo XIV's encyclical Magnifica Humanitas, and what it means for nonprofits and philanthropy navigating an AI landscape increasingly shaped by concentrated power.The encyclical, released May 25, 2026 and addressed to people of every faith and none, draws a deliberate parallel to the 1891 Rerum Novarum, which addressed the rights of workers during the Industrial Revolution. It argues that technology built and governed by a small elite cannot serve the common good, and calls for AI to be "disarmed" from the logic of competition and monopoly. Nonprofit tech thought leaders responded quickly, with voices like Cassie Gruenstein of AI x Impact, TechSoup CEO Marnie Webb, and former TAG Executive Director Chantal Forster each bringing distinct lenses: worker dignity and organizational culture, the economics of AI pricing and shared sector solutions, and the case for philanthropy to invest not just in AI adoption but in the civic institutions that shape it.This episode also covers a cross-faith coalition context and closes with an action item: Longview Philanthropy has an open RFP funding work on AI power concentration, with a July 2 deadline.Why the encyclical's arguments on power concentration, worker dignity, and environmental impact speak directly to nonprofit values, regardless of religious affiliation.What three nonprofit tech thought leaders are drawing from the document for their own practice and recommendations.The cross-faith convergence building around shared demands for accountability, transparency, and human dignity in AI development.A concrete funding opportunity for organizations working on AI governance and power concentration.Resources Mentioned:Magnifica Humanitas, full text – The VaticanPope Calls for Robust Regulation of AI – PBS NewsHourCassie Gruenstein on Magnifica Humanitas – LinkedInMarnie Webb on Magnifica Humanitas – LinkedInChantal Forster: 10 Favorite Passages – LinkedInHow Magnifica Humanitas Offers a Template for the AI Moment – MIT Technology ReviewAI Must Remain Under Human Control – Christian Daily InternationalFaith-AI Covenant – Interfaith Alliance for Safer CommunitiesAI Power Concentration RFP – Longview PhilanthropyNew every Tuesday. _______________________________Start a conversation :)Register to attend a webinar in real time, and find all past transcripts at https://communityit.com/webinars/email Carolyn at cwoodard@communityit.comon LinkedIn on reddit/r/nonprofitITmanagementon the Community IT websiteThanks for listening. 

Install the New Human operating system by releasing outdated identity wiring and anchoring a higher-frequency nervous system architecture.

Please consider supporting the show on Patreon! You can also click here to join the free Discord server or connect with the show on Bluesky and Instagram!It's a bonus episode all about some of my favorites in the gaming realm! I like these sorts of episodes from time to time and thought this would be a nice breather. Please enjoy!Thank you for listening! Want to reach out to PPR? Send your questions, comments, and recommendations to pixelprojectradio@gmail.com! And as ever, any ratings and/or reviews left on your platform of choice are greatly appreciated!

Wir sind back mit Behind Bars! Für unsere zweite Folge haben wir uns direkt Everybody's Darling geschnappt. Oder meinen wir damit den Drink der heutigen Folge? Sagen wir einfach: Heute geht es um Everybody's Darlings! Maria und Nathalie aus der Green Door Bar haben diesmal Ruben Neideck zu Gast. Ruben prägt seit neun Jahren das Velvet in Neukölln, eine Bar, die so radikal lokal und saisonal arbeitet, dass es dort einfach gar keine Zitrusfrüchte gibt. Stattdessen wird mit allem gemixt, was im Berliner Umland wild wächst. Echtes Kiez-Terroir im Glas! Wie man ohne Limette und Zitrone trotzdem einen Weltklasse-Sour mixt und worauf man beim Sammeln achten muss, erklärt uns Ruben direkt am Tresen. Im Glas haben wir passend dazu den ultimativen Crowd-Pleaser: den Gimlet. Er ist der unkomplizierteste WG-Party-Drink aller Zeiten und gleichzeitig das perfekte Template für moderne High-End-Bars. Maria drückt uns dazu eine richtig krasse Geschichtsstunde rein und taucht tief in die wilde Skorbut-Historie der britischen Navy ein. Dazu gibt es feinsten Tratsch und herrliche Anekdoten aus dem echten Bar-Leben. Also schnappt euch einfach einen Drink und kommt mit hinter den Tresen. Folgt Ruben auf Instagram https://www.instagram.com/velvet.berlin/ Instagram https://www.instagram.com/rubenneideck/ Bestellt die „Anleitung zum Weinsaufen 2“ auf Amazon vor https://amzn.to/4umAqXX Folgt Maria auf Instagram https://www.instagram.com/mariagorbatschova/ Folgt Natalie auf Instagram https://www.instagram.com/nativanwyk/ Folgt Thomas Henry auf Instagram https://www.instagram.com/thomashenryofficial/ Folgt Terroir und Adiletten auf
Instagram: https://www.instagram.com/terroirundadiletten/ Produzent: pleasure*
Instagram: https://www.instagram.com/pleasure_berlin 
TikTok: https://www.tiktok.com/@pleasure_berlin 
Website: https://www.pleasure-berlin.com/ 
Magazin: https://www.thisispleasure.com/ 
LinkedIn: https://www.linkedin.com/company/pleasureberlin

Sarah St. Pierre shares her insights on building a vibrant, authentic brand that truly reflects who you are as a business owner. From mindset shifts to branding strategies, she offers tangible tools to help you stand out and create a purpose-driven business in 2026 and beyond. Whether you're just starting or refining your brand, this conversation will motivate you to own your uniqueness and embrace your authentic self.WE CHAT: The most important thing to create a magnetic brand (that's no logos and colours)Why you don't need to niche down to 'blow up'Tips for consistency and authenticity in branding that attracts your ideal clients How to leverage colour psychology and visual identity to stand out onlineWhy storytelling will stand the test of time in branding The value of intent, strategy, and self-awareness in brand development Check Out Sarah:Website: https://solbritestudio.com/Podcast: https://solbritestudio.com/podcast APPLE PODCASTS & SPOTIFYInstagram: https://www.instagram.com/solbritestudio/Pinterest: https://www.pinterest.com/sobritestudio/Template shop coming soon! → Join the waitlist

The best tools are borne from client challenges, not theory and here Shaun provides two that he uses as part of the investment committee. Being part of the Hall Road platform allows family offices to build practical strategies that are built to assist when they see the same issue come up. In this case - how do we establish rules for assets outside the classic SAA and how do we create a form that will allow due diligence and tracking but won't bog the office down in bureaucracy.   Hall Road Investments Pty Ltd ACN 621 299 269 is a Corporate Authorised Representative (CAR No. 001279456) of Non Correlated Advisors Pty Ltd (AFSL No.430126). Shaun Parkin is an Authorised Representative (AR No 001279458) of Hall Road Investments Pty Ltd (CAR No. 001279456) and is authorised to provide general advice to wholesale investors. Nothing in this podcast (Communication) constitutes an investment offering of any kind. This Communication is for informational purposes only. It does not constitute investment or financial advice.    

Erstelle dein eigenes digitales Produkt mit KI: https://kurse.juliatrost.de/digitale-produktwelt/?el=d220526&&htrafficsource=youtubeKostenloses Webinar: https://juliatrost.de/kostenloses-webinar-26/?el=d220526&&htrafficsource=youtubeIn diesem Video nehme ich dich mit in meinen kompletten Prozess: Wie du ein digitales Produkt mit Claude Code von der Idee bis zum verkaufsfertigen Template baust. Wir starten bei Etsy, holen uns Inspiration aus bestehenden Produkten und lassen Claude Code in wenigen Minuten eine komplette Excel-Datei plus passende Landingpage erstellen. Komplett gebrandet, mit eigenem Setup, Content-Planer und Hashtag-Bibliothek. Ich zeige dir live, wie schnell ein digitales Produkt mit KI heute entsteht – und wie du es danach über Etsy oder deine eigene Seite verkaufst.

Today's listener is looking for a template to make a website that has some specific functionality—in her case, a combination of Craigslist and Airbnb.Side Hustle School features a new episode EVERY DAY, featuring detailed case studies of people who earn extra money without quitting their job. This year, the show includes free guided lessons and listener Q&A several days each week.Show notes: SideHustleSchool.comEmail: team@sidehustleschool.comBe on the show: SideHustleSchool.com/questionsConnect on Instagram: @193countriesVisit Chris's main site: ChrisGuillebeau.comRead A Year of Mental Health: yearofmentalhealth.comIf you're enjoying the show, please pass it along! It's free and has been published every single day since January 1, 2017. We're also very grateful for your five-star ratings—it shows that people are listening and looking forward to new episodes.

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 U.S. State Department's Pax Silica initiative reframes Pax Americana for the AI age — chips, semiconductors, critical minerals, energy, data centers, payment rails. This week in Beijing, two of the Trilogy of Boards Patrick Wood predicted clicked into place. The Trilogy is now whole. In this two-and-a-half-hour conversation, Courtenay Turner and Patrick Wood — co-authors of The Final Betrayal: How Technocracy Destroyed America — walk the architecture being built around you: Pax Silica, the IMEC corridor, the Abraham Accords as the template for the China play, the Five Walls boxing China in, Gaza's new order under the Board of Peace, Taiwan as silicon shield and silicon hostage, the tokenization of property and the New York Stock Exchange, the occult roots of the technocratic movement, and how to think about preserving sovereignty, autonomy, and property in a rapidly closing system. Read the full essay: https://courtenayturner.substack.com/p/pax-silica ━━━━━━━━━━━━━━━━━━━━ CHAPTERS ━━━━━━━━━━━━━━━━━━━━ 0:00 — Opening: The Petrodollar Ends, Pax Silica Begins 1:31 — Welcome to the Technocracy Roundtable 5:11 — Property, Rights, and the Founders' Distinction 6:44 — What Is Pax Silica? (Video Explainer) 9:08 — Locke, Private Property, and Sovereign Property 13:05 — The Regime That Comes With Tokenized Property 14:01 — Tokenization, Titles, and the Loss of Control 21:57 — When Your Home Becomes a Programmable Asset 24:58 — Sovereign Farm Rights and Self-Sufficiency 25:54 — Daniel's Silicon Kingdom: The Biblical Frame 29:22 — The State Department Pax Silica Declaration 30:45 — The Allies Joining the Corridor 34:29 — Terms-of-Service Control of Everything 39:05 — Why Technocratic Countries Rise to the Top 41:53 — Trump's Empire Strategy in Beijing 46:33 — How China Gets Boxed In: The Five Walls 51:46 — Global Power Shifts: BRICS, Gulf, India 58:18 — The Trump-Xi Meeting: Body Language and Substance 1:01:31 — Abraham Accords as the Template for China 1:06:54 — Israel, Zionism, and the Technocracy Conflation 1:11:56 — Gaza's New Order: USD1, CENTCOM, and the Board of Peace 1:15:13 — Gulf Sovereign Wealth, Islamic Finance, and Tokenization 1:25:32 — Pax Silica's New Power Triangle 1:37:53 — Taiwan and the Chip Leverage Question 1:45:02 — How the Trade Boards Replace the Global Order 1:52:25 — Why Technocracy Is Beyond Politics 1:56:04 — Occult Roots, AI Consciousness, and the 2025 Conclave 2:05:21 — HOAs as Control Layers 2:08:40 — Tokenization and the Financial Fallout 2:13:19 — Protecting Assets: Cash, Land Patents, UCC Article 8 2:30:00 — Closing: "Use AI to Destroy AI" ━━━━━━━━━━━━━━━━━━━━ KEY NUMBERS & SOURCES MENTIONED ━━━━━━━━━━━━━━━━━━━━ • New York Stock Exchange (ICE): $25 trillion in U.S. assets targeted for tokenization by end of 2026; $170 trillion globally • UN Security Council Resolution 2803: Board of Peace authorized November 17, 2025 • Trump-Xi Beijing summit: Boards of Trade and Investment agreed May 14, 2026 • Pax Silica Declaration: signed in Washington, December 12, 2025 • H.R. 3633 / Digital Asset Market CLARITY Act: passed July 17, 2025 by 294–134 ━━━━━━━━━━━━━━━━━━━━ FURTHER READING ━━━━━━━━━━━━━━━━━━━━ • Courtenay Turner & Patrick Wood, The Final Betrayal: How Technocracy Destroyed America • Patrick Wood, The New Economics of Technocracy • Patrick Wood, "The China Card: Global Technocracy Is Emerging Under Trump's Reign" • Courtenay Turner, "The Tokenization of Everything" • Courtenay Turner, "The Governance Stack: How Technocracy Was Built Over 200 Years" • Henry Kissinger, Eric Schmidt & Craig Mundie, Genesis: Artificial Intelligence, Hope, and the Human Spirit ━━━━━━━━━━━━━━━━━━━━ CONNECT ━━━━━━━━━━━━━━━━━━━━ Courtenay Turner: • Substack • Website • X: @CourtenayTurner Patrick Wood: • Technocracy.News • X: @StopTechnocracy ━━━━━━━━━━━━━━━━━━━━ The Final Betrayal: How Technocracy Destroyed America — co-authored by Courtenay Turner & Patrick Wood. Available through Coherent Publishing. #PaxSilica #Technocracy #Tokenization #PatrickWood #CourtenayTurner #TheFinalBetrayal #IMEC #CLARITYAct #Geopolitics #BeijingSummit Learn more about your ad choices. Visit megaphone.fm/adchoices

Message 1 of 3 in the series "Designed to Team" by Christian Williams.

Anna Duggar used the monitored jail system to send Josh private photos and messages while he served a federal sentence for possessing child sexual abuse material a Homeland Security agent described as among the worst he'd examined. He asked for more. She engaged. Days before sentencing, he was allegedly writing about "taking things up a notch." She never left. She never confronted anyone publicly. She vented in private messages and performed in public. And when Joseph Duggar was arrested on felony charges involving a minor in Florida — charges he has pleaded not guilty to — Anna was the one who emailed him within days, put money on his books, told him which pod was safer, and warned him not to discuss anything legal because everything gets turned over. Her message about Kendra: "She loves you so much."Tony Brueski and Robin Dreeke break down how the Anna model is now allegedly being applied to Kendra. The recorded jail calls show Kendra asking Joseph one thing: do you still love me? Not asking about the nine-year-old girl. Not asking about the allegations. The IBLP framework, the homeschooling system, the forgiveness-over-justice approach — the structure is designed to keep wives in formation. Anna is the proof that it works.But there's a crack. Kendra's own parents allegedly broke from the Duggars and stood with the alleged victim. According to reports, they lost their home and their livelihood for it. That's the price this system allegedly extracts from anyone who chooses accountability over loyalty.Jim Bob's email allegedly called the charges "terrible decisions" and pivoted to getting Kendra's charges dropped. Anna forwarded Josh a message calling his conviction a "victimless crime." She told Josh privately that Jim Bob was a "dead-end road." She saw the machine clearly. She never left it. The question is whether Kendra will.Join Our SubStack For AD-FREE ADVANCE EPISODES & EXTRAS!: https://hiddenkillers.substack.com/ Want to comment and watch this podcast as a video? Check out our YouTube Channel. https://www.youtube.com/channel/UC8-vxmbhTxxG10sO1izODJg?sub_confirmation=1 Instagram https://www.instagram.com/hiddenkillerspod/ Facebook https://www.facebook.com/hiddenkillerspod/ Tik-Tok https://www.tiktok.com/@hiddenkillerspod X Twitter https://x.com/TrueCrimePodThis publication contains commentary and opinion based on publicly available information. All individuals are presumed innocent until proven guilty in a court of law. Nothing published here should be taken as a statement of fact, health or legal advice.#AnnaDuggar #KendraDuggar #JosephDuggar #JoshDuggar #DuggarFamily #DuggarWives #IBLP #HiddenKillers #TrueCrime #RobinDreeke

Watch on YouTube: https://youtu.be/-tJ2i4p-ahg In Episode 341 of the Glass and Out Podcast, we're joined by the Goaltending Development Coach for the Vancouver Canucks, Ian Clark. Clark has been with the Canucks since the 2019-20 season and previously served as the club's goaltending coach from 2002-2010. In between, he was a member of the coaching staff with the Columbus Blue Jackets. During his time in the NHL, he has mentored the likes of Roberto Luongo, Sergei Bobrovsky, and Thatcher Demko, to name a few. He also operated a successful goalie school for several decades, helping launch the careers of many other high-profile puck stoppers. Clark has also launched the From The Crease app. FTC provides both goalies and coaches with a top-to-bottom playbook for developing all aspects of the position. Users are given video explanations of drills, the ability to track their progress, and a progression-based curriculum that keeps aspiring goalies focused on the right details at the right stage of their development. You can check out the app here. Listen as he shares why we need to train goalies to handle pressure, why coaching shouldn't follow a template, and his seven ingredients for great goaltending. Secure your TCS Live ticket: https://thecoachessitelive.com/ Download the TCS app: https://www.thecoachessite.com/app Start your 30 Day Free Trial: https://www.thecoachessite.com/ Learn more about our presenting sponsors: Hudl: hudl.com/tcs Biosteel: BioSteelTeams.com/Glassandout

I accepted a job offer just eight weeks after getting laid off. And you can too. It's a repeatable process. In this episode, I talk about my job search journey and I answer all your job search questions to help you land a job offer too! I talked about mindset, resume optimization, leveraging LinkedIn, and the support I had in this process.  Tune in to learn:  What the job interview process looks like in 2026 Which job boards are most effective for finding jobs How to best structure your days when job searching Is it better to change your resume for each role or to use the same one? Should you narrow your job search by job title or type of company? And so much more. Whether you're just starting out in your job search or need new energy after being on the job search for a while, this episode is for you.  Resources:  Get a Raise in Any Economy - Get instant access via thefirstgencoach.com/freetraining 6-Month 1:1 Coaching: https://calendly.com/thefirstgencoach/discovery-call Apply for On-Air Coaching: https://forms.gle/JshV6Z6TfUw6BBnk6 Download your⁠⁠⁠⁠⁠⁠ ⁠FREE Resume Guide and Template⁠⁠⁠⁠⁠⁠⁠ Follow @⁠⁠⁠⁠⁠⁠⁠CarlaTheFirstGenCoach⁠⁠⁠⁠⁠⁠⁠ on Instagram Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

The AppLovin setup playbook. No micromanaging, no manual optimization, no bullshit. UA template for you! Applovin UA explained!Solo for episode three of the MVP UA Template series (after Facebook and Google), this time breaking down AppLovin / Axon end-to-end. Tracking setup, campaign structure, bidding, ROAS targets, the new CPM-vs-CPI billing change, creative strategy, the real Axon dashboard with real numbers from his own game, and the patience required to actually scale.The headline lesson: AppLovin is a beast, but it really matters what you feed it. Garbage MMP signals = garbage results. Playables aren't optional. And the geo-bucket strategy that works on Facebook and Google does NOT work here — worldwide campaign with geo targets is the only sensible setup.If you've been avoiding AppLovin because it feels like a black box, this is the episode that demystifies it.⏱️ TIMESTAMPS00:00 Axon dashboard preview02:20 Why AppLovin and what this episode covers04:14 Budget, MMP signals, and the "garbage in, garbage out" rule07:42 Worldwide campaign + geo targets (NOT geo buckets)10:58 D7 vs D28 ROAS — which attribution window to pick12:57 CPM vs CPI billing — the new setting most teams miss14:40 Creative strategy: 80% playables, 60 new per month17:59 Push budgets hard when something works (30-50%)━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Alan's Soap https://AlansSoaps.com/ToddHonor John's memory and the legacy he created for Ian and Alan with Alan's Artisan Soaps “John's Favorites” bundle.  Get one bar of each of his favorites for only $28.99. Bulwark Capital https://KnowYourRiskPodcast.comBe confident in your portfolio with Bulwark! Schedule your free Know Your Risk Portfolio review. Go to KnowYourRiskPodcast.com today. Renue Healthcare https://Renue.Healthcare/ToddYour journey to a better life starts at Renue Healthcare. Visit https://Renue.Healthcare/Todd Bonefrog https://BonefrogCoffee.com/ToddGet the new limited release, The Sisterhood, created to honor the extraordinary women behind the heroes. Use code TODD at checkout to receive 10% off your first purchase and 15% on subscriptions.LISTEN and SUBSCRIBE at:The Todd Herman Show - Podcast - Apple PodcastsThe Todd Herman Show | Podcast on SpotifyWATCH and SUBSCRIBE at: Todd Herman - The Todd Herman Show - YouTubeZach Abraham and I discuss how the truth about what's going on in Iran seems to be fungible at this point. The deal points going back and fourth can effect your retirement, our country, and our lives in countless ways, and Zach is here to help us make sense of it all.Episode links:TRUMP: “We are right now producing more oil than Saudi Arabia and Russian COMBINED!” “In about a year from now, we'll be doing about DOUBLE that level.” “We don't have an oil shortage. We have ‘drill, baby drill.'”Killing the Petroyuan: Secretary Bessent Turned Argentina Into a Template for Dollar Dominance

Does following up after a discovery call make you cringe? You're not alone, but done right, a follow-up can actually feel like a gift to your potential client. In this episode, I'm sharing three simple strategies to check in without feeling pushy, salesy, or awkward. What we cover: Why follow-ups feel icky — and why they don't have to Setting expectations during the discovery call so follow-ups feel natural Keeping your check-in email short, simple, and stress-free (and saving it as a template!) The "magic email" from community member Sally Farrant that gets responses fast Action steps: ✓ Mention your follow-up plan at the end of your discovery call ✓ Draft a simple one or two-line check-in email and save it as a template ✓ Offer Voxer as an alternative for clients who prefer voice messages over email ✓ Use Sally's closing email if you've heard nothing after your first two follow-ups ✓ Don't assume silence means no, a warm lead often just needs a nudge! Subscribe for more quick, actionable freelance tips you can enjoy during a tea break! Resources mentioned: Sally Farrant's pricing calculator  Timestamps: 0:00 Intro 0:20 Why Following Up Feels Icky (And Why It Shouldn't) 1:18 Tip 1: Set the Expectation During the Discovery Call 2:34 Tip 2: Keep Your Follow-Up Email Short & Simple 3:30 Tip 3: The 'Are We Done?' Email Template 4:03 The Template in Action 5:17 Recap: 3 Ways to Follow Up Without the Ick 6:27 Community & Where to Find Emma Follow me on Instagram Follow me on Bluesky Email: hello@emmacossey.com  Come join us in the free Freelance Lifestylers Facebook group Want more support? Check out the Freelance Lifestyle School courses and membership. Join the Freelance Lifestyle Discord Community: https://discord.gg/RKYkReS5Cz Order my book: The Freelance Lifestyle: Your Friendly Guide to Starting a Freelance Business

Arab Digest editor William Law invites the North Africa specialist Tarek Megerisi onto this week's podcast. The starting point for their conversation is Tarek's take on the EU's "Pact for the Mediterranean" and how a fresh approach to North Africa could shape positive outcomes in a region urgently in need of them. They explore the threat that Israel and Trump's America pose regionally as well as globally and what Europe could do to ease that threat. Tarek concludes with his assessment of the current situation in Libya. Sign up NOW at ArabDigest.org for free to join the club and start receiving our daily newsletter & weekly podcasts.

I manifested a job offer 8 weeks after getting laid off, and in this episode, I tell you how. From getting crystal clear on what I wanted from my next role, to over-preparing and over delivering in the job interview, to protecting my energy and focus, these are the exact steps that I used to land a fully remote, aligned job offer that was exactly what I was looking for as the next step in my career! I share both the strategy and the mindset that helped me implement these steps.  I don't hold anything back, including the emotional toll that being laid off had on that made it hard to do things like getting myself up off the couch to wash my hair, put on a little makeup, and talk myself into networking events. I also share the one bit of tough love that snapped me out of my pity party and helped me step back into my power.  Whether you're currently navigating a layoff or simply want to fast-track your job search, you don't want to miss this episode.  Referenced Episodes:  109. Get Job Offers Faster with These 5 Steps Job Interviews in 2026 (Instagram Live) 148. The Spiritual Side of Job Searching 34. Lowering the Stakes without Lowering Your Standards Resources:  Get a Raise in Any Economy - Get instant access via thefirstgencoach.com/freetraining 6-Month 1:1 Coaching: https://calendly.com/thefirstgencoach/discovery-call Apply for On-Air Coaching: https://forms.gle/JshV6Z6TfUw6BBnk6 Download your⁠⁠⁠⁠⁠⁠ ⁠FREE Resume Guide and Template⁠⁠⁠⁠⁠⁠⁠ Follow @⁠⁠⁠⁠⁠⁠⁠CarlaTheFirstGenCoach⁠⁠⁠⁠⁠⁠⁠ on Instagram Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

For a deeper study of God's Word, plus daily resources for your walk with Jesus, visit https://passionequip.com/. — With Passion City Online, you can join us every Sunday live at 9:30a and 11:45a, and our gatherings are available on-demand starting at 7p! Join us at https://passioncitychurch.com — Subscribe to our channel to see more messages from Passion City Church:  https://www.youtube.com/passioncitychurch — Looking for content for your Kids? Subscribe to our Passion Kids Channel: https://passion.link/passionkidsonline  — If you would like to give to our house, visit https://passioncitychurch.com/give/ — Check out Passion's books, music, and more at https://passionresources.com/ — At Passion City Church, we believe that because God has displayed the ultimate sacrifice in Jesus, our response to that in worship must be extravagant. It is our privilege and our created purpose to reflect God's Glory to Him through our praise, our sacrifice, and our song.  — Follow Passion City Church: https://www.instagram.com/passioncity/  Follow Louie Giglio: https://www.instagram.com/louiegiglio  Passion City Church is a Jesus church with locations in Atlanta and Washington D.C. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

The deepest wound in complex trauma is not emotional intensity. It is the learned loss of connection to yourself. In this episode, Jennifer Wallace and Elisabeth Kristof open the next chapter of the CPT series by starting where the roots go deepest: self-abandonment. This is the pattern they chose to name first—and intentionally so—because when the nervous system learns that staying connected to the self is unsafe, nearly every other complex trauma response grows from that adaptation. Self-abandonment is not a personality flaw or a lack of self-awareness. It is a body-based survival strategy. From a neurosomatic perspective, it is a state-dependent loss of interoceptive access—a patterned inhibition of internal signals that the nervous system learned in order to stay attached, stay safe, and maintain stability in the relational environment. And like every other output explored in this series, it made complete sense at the time it formed. The conversation moves through the neuroscience of dissociation and how it is inseparable from self-abandonment, the brain regions involved, and what their altered activity actually looks like in everyday life. It explores the fawn response—including its lesser-discussed dimension of sexual fawning—and the specific pathways through which emotional neglect and parentification set the stage for chronic self-erasure. Jennifer and Elisabeth also trace how masking—whether in the context of neurodivergence, complex trauma, or systemic oppression—is another expression of the same root pattern: authenticity does not feel safe, so the self gets hidden. But this episode does not stop at the wound. Both hosts share what the growth edge of this pattern has actually looked like for them—what building interoceptive capacity from the ground up felt like in practice—and how self-attunement, the skill of staying present with internal experience without becoming overwhelmed by it, gradually became accessible rather than threatening. This is not a quick-fix episode. It is an honest, grounded map of one of the most pervasive and least visible patterns in complex trauma—and a clear-eyed account of what actually changes it.   In This Episode, You Will Learn: Why self abandonment is a survival adaptation rooted in the nervous system, not a character flaw How interoceptive access becomes inhibited under chronic relational threat, and what that feels like day to day The neuroscience of dissociation: which brain regions are involved and how their altered activity drives functional disconnection Why emotional neglect, even without overt harm, sets the stage for chronic self erasure How parentification creates a nervous system template of self abandonment that persists long into adulthood What fawn response is, how it operates neurologically, and why sexual fawning is a real and undernamed expression of it How masking across contexts including neurodivergence, complex trauma, and racial and systemic oppression overlaps with and compounds self abandonment What self attunement actually is as a nervous system skill and how it is different from insight or emotional processing alone Why healing is capacity-based rather than cathartic, and what that means for pacing How both hosts have rebuilt interoceptive access over time and what that process has opened up for them Chapters 0:00 - The Deepest Wound in Complex Trauma Is Not Emotional Intensity 0:38 - Welcome: Who This Episode Is For 1:27 - Introducing the CPT Series and Why We Start With Self Abandonment 2:53 - Defining Self Abandonment as a Nervous System Output 4:21 - Pete Walker, Fawn Responses, and How the Child Learns to Attune Outward 4:47 - The Neuro Somatic View: Interoceptive Access Under Chronic Threat 6:08 - Embodiment as the Opposite of Self Abandonment 6:35 - Collective and Intergenerational Dimensions of Self Abandonment 7:55 - What Self Abandonment Looks Like in Real Life: A Case Study 9:21 - Dissociation: What It Actually Is and Why It Is Inseparable From Self Abandonment 10:42 - Brain Science: The Insula, Hippocampus, Amygdala, and Thalamus 14:35 - The Fawn Response and Sexual Fawning 18:17 - Self Attunement: The Opposite of Self Abandonment 21:06 - Rebuilding Interoception: Starting Small 27:19 - Emotional Neglect as the Root of Self Abandonment 29:13 - Parentification and the Template of Self Erasure 31:21 - Masking: Neurodivergence, Systemic Oppression, and Complex Trauma 36:19 - What Growth Has Actually Looked Like for Jennifer and Elisabeth 40:20 - Stress Bucket Dysmorphia and Learning Your Real Capacity Resources and Links NSI Foundations Bundle for coaches and practitioners: neurosomaticintelligence.com/foundations Two week Rewire Trial of guided neuro somatic training: rewiretrial.com Learn more about Jennifer's work at her YouTube channel: Sacred Synapse https://www.youtube.com/@sacredsynapse-23   Trauma Rewired podcast  is intended to educate and inform but does not constitute medical, psychological or other professional advice or services. Always consult a qualified medical professional about your specific circumstances before making any decisions based on what you hear.  We share our experiences, explore trauma, physical reactions, mental health and disease. If you become distressed by our content, please stop listening and seek professional support when needed. Do not continue to listen if the conversations are having a negative impact on your health and well-being.  If you or someone you know is struggling with their mental health, or in mental health crisis and you are in the United States you can 988 Suicide and Crisis Lifeline.  If someone's life is in danger, immediately call 911.  We do our best to stay current in research, but older episodes are always available.  We don't warrant or guarantee that this podcast contains complete, accurate or up-to-date information. It's very important to talk to a medical professional about your individual needs, as we aren't responsible for any actions you take based on the information you hear in this podcast. We  invite guests onto the podcast. Please note that we don't verify the accuracy of their statements. Our organization does not endorse third-party content and the views of our guests do not necessarily represent the views of our organization. We talk about general neuro-science and nervous system health, but you are unique. These are conversations for a wide audience. They are general recommendations and you are always advised to seek personal care for your unique outputs, trauma and needs.  We are not doctors or licensed medical professionals. We are certified neuro-somatic practitioners and nervous system health/embodiment coaches. We are not your doctor or medical professional and do not know you and your unique nervous system. This podcast is not a replacement for working with a professional. The BrainBased.com site and Rewiretrail.com is a membership site for general nervous system health, somatic processing and stress processing. It is not a substitute for medical care or the appropriate solution for anyone in mental health crisis.  Any examples mentioned in this podcast are for illustration purposes only. If they are based on real events, names have been changed to protect the identities of those involved.  We've done our best to ensure our podcast respects the intellectual property rights of others, however if you have an issue with our content, please let us know by emailing us at traumarewired@gmail.com  All rights in our content are reserved  

Alan's Soap https://AlansSoaps.com/ToddHonor John's memory and the legacy he created for Ian and Alan with Alan's Artisan Soaps “John's Favorites” bundle.  Get one bar of each of his favorites for only $28.99. Bulwark Capital https://KnowYourRiskPodcast.comBe confident in your portfolio with Bulwark! Schedule your free Know Your Risk Portfolio review. Go to KnowYourRiskPodcast.com today. Renue Healthcare https://Renue.Healthcare/ToddYour journey to a better life starts at Renue Healthcare. Visit https://Renue.Healthcare/Todd Bonefrog https://BonefrogCoffee.com/ToddGet the new limited release, The Sisterhood, created to honor the extraordinary women behind the heroes. Use code TODD at checkout to receive 10% off your first purchase and 15% on subscriptions.LISTEN and SUBSCRIBE at:The Todd Herman Show - Podcast - Apple PodcastsThe Todd Herman Show | Podcast on SpotifyWATCH and SUBSCRIBE at: Todd Herman - The Todd Herman Show - YouTubeZach Abraham joins to discuss the "why?" behind the cultural and spiritual decline in states like Washington, which have largely pushed productive business owners out.Episode links:Justin Trudeau is demanding the wealthy step up, limit their income, and distribute it to others. He charges $100,000 just to simply speak. He's also worth $100 million.Shots fired near Seattle mayor Katie Wilson's press conferenceWA Rainy Day Fund Drained…TRUMP: “We are right now producing more oil than Saudi Arabia and Russian COMBINED!” “In about a year from now, we'll be doing about DOUBLE that level.” “We don't have an oil shortage. We have ‘drill, baby drill.'”Killing the Petroyuan: Secretary Bessent Turned Argentina Into a Template for Dollar Dominance

Why is it so hard to stop comparing yourself to others?In this episode, I speak with Jemma Sbeg, host of The Psychology of Your 20s, a #1 global podcast with over 50 million listens, now streaming on Netflix.We explore why comparison has become so unavoidable, and how it can leave you feeling behind, stuck, and disconnected from your own life.This episode will change how you think about comparison and help you stop chasing someone else's version of success.Jemma Sbeg is a mental health advocate and host of The Psychology of Your 20s.Timestamps: (00:00) Introduction - Why Comparison Hurts(01:25) Stuck in the Template(02:42) Stay in Your Lane(05:01) Circle Not Ladder(06:47) Too Many Options(07:51) Nick's Business Detours(10:37) Why Twenties Feel Hard(13:36) Be Present in Your Chapter(16:46) Success Doesn't Fix You(20:45) Reading for Balance(23:29) The Optimization Trap(25:57) Common Sense Over Optimizing(27:29) Health Trends And Irony(28:06) Looksmaxxing And Male Pressure(33:14) Resilience Through Failure(38:08) Success Without Quitting(39:33) Podcast Fame And Pressure(43:53) Dream Bigger And Imposter Syndrome(46:39) Where To Find The Show(47:25) Advice To Younger Self(48:06) Final ThanksConnect with Nick:Instagram: https://instagram.com/nickbracksWebsite: http://nickbracks.comEmail: contact@nickbracks.comConnect with Jemma:Instagram: https://www.instagram.com/thatpsychologypodcast/Website: https://www.psychologyofyour20s.com/ Hosted on Acast. See acast.com/privacy for more information.

V12 Wrap Up Template - Prayer and Worship with Laura by TABC

In 1984, Nintendo released Golf for the Famicom, a game that almost never existed. Every developer Nintendo approached to build it turned the project down, convinced that fitting eighteen holes of course data into a Famicom cartridge was simply impossible. A twenty-three year old programmer at a tiny Tokyo company called HAL Laboratory said yes, invented his own data compression method from scratch, and delivered a game so elegantly designed that the two-click power and accuracy swing mechanic he built became the foundation every golf game since has borrowed. But the story of Golf begins long before 1984, on the windswept linksland of medieval Scotland, where a game that kings tried three times to ban slowly became a global institution. Dave and Rob trace the sport from its debated origins through the British Empire's global spread, the moment a working class caddy cracked open golf's exclusive culture on a September afternoon in 1913, and the early video game attempts that inched toward something that worked before Satoru Iwata finally got it right. Join them on the green for the full story, on today's trip down Memory Card Lane.Read transcript

Getting a job in 2026 will require you to think outside the box. But sometimes, you also have to rely on tried and true methods, such as going to career fairs. In this episode, I share practical strategies for getting hired at career fairs. I talk both logistics and self-care.  Plus, a very special announcement for episode 150! Referenced Episodes:  115. A Quick start Guide to Networking Events 78. Three Types of Coffee Chats to Increase Your Income Resources:  In honor of Financial Literacy Month, I am bringing back one of my most impactful trainings: Get a Raise in Any Economy.  This training will show you the exact steps you need to take to understand how companies determine salary and what you need to do in order to maximize your salary.  Get instant access via thefirstgencoach.com/freetraining 6-Month 1:1 Coaching: https://calendly.com/thefirstgencoach/discovery-call Apply for On-Air Coaching: https://forms.gle/JshV6Z6TfUw6BBnk6 Download your⁠⁠⁠⁠⁠⁠ ⁠FREE Resume Guide and Template⁠⁠⁠⁠⁠⁠⁠ Follow @ ⁠⁠⁠⁠⁠⁠⁠CarlaTheFirstGenCoach⁠⁠⁠⁠⁠⁠⁠  on Instagram Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

FPL GW35 Wildcard Draft for anyone playing the chip this week!

Send us Fan Mail

V12 Wrap Up Template - Sharing your Faith with Mia Clark! by TABC

As far as tough budget decisions go, we haven't seen anything on this scale since Joe Hockey's ill-fated 2014 effort.

The right mindset and strategy will go a long way towards helping you land your next role. But sometimes, you can use a little divine intervention. In this episode, I go over eight spiritual practices that I have used throughout my career and that I am using to manifest a fully aligned job offer in 30 days. Some of these spiritual practices, like lighting a candleeeeeee and setting an intention, are things I've been doing for years and have mentioned on the podcast before. Others are new to me or new to sharing on the podcast. Plus, I share an extremely personal journal entry that encapsulates how I think about job searching and calling in your next role.  NEW RESOURCE ALERT!  In honor of Financial Literacy Month, I am bringing back one of my most impactful trainings: Get a Raise in Any Economy.  This training will show you the exact steps you need to take to understand how companies determine salary and what you need to do in order to maximize your salary.  Get instant access via thefirstgencoach.com/freetraining 6-Month 1:1 Coaching: https://calendly.com/thefirstgencoach/discovery-call Apply for On-Air Coaching: https://forms.gle/JshV6Z6TfUw6BBnk6 Download your⁠⁠⁠⁠⁠⁠ ⁠FREE Resume Guide and Template⁠⁠⁠⁠⁠⁠⁠ Follow @⁠⁠⁠⁠⁠⁠⁠CarlaTheFirstGenCoach⁠⁠⁠⁠⁠⁠⁠ on Instagram Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Find the FULL TRANSCRIPT at ProsperousCoach.com/382.We're going to be talking about the difference between a DIY website, one that you do yourself using something like Wix or Squarespace or having a professional designer create a custom website for you.There are a bunch of differences and I want you to know what they are so that as you're making this decision you can go in with your eyes open.And the special guest that I have for today is my friend and colleague, Nichole Betterley. Nichole runs a company called NPoweredsites.com. 

A lot of lawn care and landscaping businesses think they need a fully custom website to look professional—but that's not always true. In this episode, we break down the real differences between templated and custom websites, the pros and cons of each, and when it actually makes sense to invest $5K–$20K+ into a custom build. If you're between $0 and $1M in revenue, this episode will help you focus on what actually drives growth—so you don't overspend on the wrong things too early. Important Links: https://www.brandedbull.com/  https://www.instagram.com/brandedbull/ https://www.facebook.com/brandedbullinc https://www.lawntrepreneuracademy.com/ 

This is the year creators stop marketing reactively and start creating intentionally.No more scattered content.No more random promotions.No more creating without a clear path for growth.This is the year of strategy.Structure.Systems.Simplicity.Scale.In this episode, I'm breaking down how to create a Marketing Plan that helps you grow your audience, increase your visibility, and create more impact, influence, and income as a creator and CEO.Because we're no longer just creating content.We're creating offers.We're creating funnels.We're creating ecosystems.We're creating brands that convert.Inside this episode, I break down:1️⃣ Marketing objectives, goals + execution2️⃣ Strategy, structure + systems for scalable growth3️⃣ One core offer + one funnel focus4️⃣ Freebies, add-ons, upsells + payment plans5️⃣ B2B2C marketing + long-term brand partnerships6️⃣ AI + automation for engagement and conversions7️⃣ SEO, blogs + email to drive traffic8️⃣ Tech + tools like ClickUp, Notion, Kajabi, HoneyBook + ManyChat9️⃣ Repurposing content across platforms with ease

340B Insight wants to make our podcast the best it can be. To help us succeed, we'd like to hear your thoughts. Please take just a few minutes to complete our listener survey, and we will enter you in a drawing to win a $100 gift card! To participate, please go to 340bpodcast.org/survey.340B lately has had a news cycle that seems to change by the hour, and 340B Health President and CEO Maureen Testoni joins us to break down some of the biggest news happening in Washington, D.C., and in courthouses around the country.HRSA Seeks Feedback on Reviving Rebates After courts halted the rebate pilot that was set to go into effect in January, Maureen notes that the Health Resources & Services Administration is seeking more information on a possible revival of its rebate plans. Hospitals are responding with their objections, as are lawmakers on Capitol Hill. Nearly 100 members of the House of Representatives wrote a letter to the committee in charge of funding HRSA urging it to block federal spending for any HRSA rebate model.Huge Rulings on the GPO Prohibition, Child Site RegistrationThe past several months have seen big 340B rulings from federal courts. One decision vacated HRSA guidance that had blocked certain 340B hospitals' use of GPOs for their initial drug inventory, finding that HRSA failed to properly explain the reasons for that restriction. The other decision found that HRSA similarly failed to explain a rationale for restricting 340B eligibility for child sites for up to 23 months after the sites come online. Maureen notes that HRSA could appeal the rulings or seek to issue new guidance.Federal Government Weighs in on State Contract Pharmacy LawsuitsFor the first time, the federal government has filed briefs in support of drug companies in several lawsuits over state contract pharmacy protection laws. In these briefs, Maureen says the government effectively is telling judges it does not believe states have the right to protect contract pharmacy because federal 340B law preempts such actions. With the federal government weighing in on the matter and a recent split among appeals courts over the issue of preemption, it is possible this issue might be appealed at some point to the U.S. Supreme Court.ResourcesUse Our Letter Template Today To Oppose Development of a New 340B Rebate ProgramNearly 100 Members of Congress Urge Funding Block for 340B Rebate ModelPlease Help Advocate for Enforcement Actions Against Drugmakers' In-House Claims Data DemandsFederal Court Vacates HRSA's 2013 GPO Prohibition PolicyFederal Court Decides HRSA Child Site Eligibility Restrictions Are UnlawfulFederal Government Backs Drug Companies in Litigation Over State Contract Pharmacy LawsAppeals Court Blocks West Virginia 340B Contract Pharmacy Law, Creating Potential Split with Other Circuits340B Health Impact Profile Guidebook and Template

“We keep getting wake-up calls and snoozing the alarm. Now is the time to actually get out of bed and confront this problem before it is too late.” — Eyck Freymann Forget Iran for a moment. The Hormuz crisis is a template for the bigger crisis of Taiwan. Eyck Freymann — Hoover Fellow at Stanford, author of the brand-new Defending Taiwan: A Strategy to Prevent War with China — believes that the fate of the 21st century may hinge on Taiwan. And he warns that if America can't handle Iran, it's certainly not ready for Beijing. Freymann argues that China doesn't need to invade Taiwan. Xi Jinping has watched Putin discover — with horror — what happens when you send unprepared forces into a country that fights back. China's lesson from Ukraine is a strategy of quarantine rather than invasion. The United States will then face a choice between accepting Chinese checkmate or escalating a crisis with no domestic or international support. Taiwan produces 90% of the world's advanced semiconductors and 99% of the cutting-edge NVIDIA GPUs used to train frontier AI models. If those chip factories shut, there will be an instantaneous global financial crisis. Forget today's Iranian theater. Taiwan will be the real existential show. Five Takeaways •       The Hormuz Alarm Bell: Iran has no navy, no air force, and supposedly no ballistic missile arsenal anymore — and yet it took 20% of global oil supply offline. The Trump administration went in thinking overwhelming military superiority would translate to political victory. It hasn't. Strategy, Freymann says, is the art of connecting ends to means. If you don't know your ends, you'll flail. China is watching every mistake: no plan for the economic shock, no domestic legitimacy for the war, excess pain falling on oil-importing US allies like Japan, South Korea, and Europe. Beijing's conclusion: we don't have to pick a military fight with the United States. Why would we? •       The Semiconductor Chokehold: Taiwan produces 90% of the world's advanced semiconductors and 99% of the cutting-edge NVIDIA GPUs used to train frontier AI models. The CHIPS Act has tried to change this. It hasn't. The Arizona facility is two generations behind Taiwan, commercially uncompetitive, and unable to scale. Taiwan is five years ahead now and will be five years ahead in five years. If the Taiwan fabs go offline, there is an instantaneous global financial crisis: the seven companies that account for roughly 40% of the S&P 500 are all essentially the AI trade. The hyperscalers are spending $600 billion in data centers this year — the only thing keeping the US economy out of recession. This is what's at stake, before you even get to the military question. •       The Quarantine: Winning Without Fighting: Xi Jinping's plan A is not invasion. It's the quarantine: seize control of who and what comes and goes to Taiwan by declaring that anyone flying to Taipei must first clear customs in Shanghai. Impound a United Airlines flight. Let the ambiguity do the work. If China can do that and get away with it, Taiwan can't rebuild its military, the US can't send more weapons, and Beijing controls the chips. It's checkmate — without a shot fired. The United States then has to accept it, or escalate in a way that has no domestic legitimacy and drives wedges between Washington and its allies. China has figured out how to extort the West with prolonged economic pain. The alarm bells keep ringing. America keeps snoozing. •       What a Taiwan War Would Actually Look Like: It would be a war at sea — fundamentally unlike anything America has fought or prepared for in eighty years. China would need to simultaneously control the skies, the undersea, and the surface on all sides of the Taiwan Strait, then send tens of thousands of men 80 miles across in amphibious vessels to storm beaches in a Normandy-style assault. The first engagements would be decided in minutes to hours by long-range precision munitions. America's operational capabilities are exceptional: the cyber assassinations, the special forces raid, the continuous bomber sorties from the continental United States. But China has home-field advantage. And it has been building systematically for this scenario for years. We could probably win if we fought today. We need to make investments for tomorrow. •       The Four-Pillar Strategy: Freymann's integrated answer: diplomacy, military deterrence, economic resilience, and allied coordination — all working together, not in separate silos. On diplomacy: maintain the principled position that Taiwan's status must be resolved peacefully and democratically. On military: show China it can't win if it escalates to war, while keeping conventional forces credible. On economics: build enough allied resilience that authoritarian powers can't extort the West by threatening prolonged economic pain. On allies: coordinate with Japan, South Korea, the Europeans on a shared plan for what happens if things collapse. This is doable. It's been done for fifty years. We just need the resolve to keep doing it. About the Guest Eyck Freymann is a Hoover Fellow at Stanford University and a Non-Resident Research Fellow at the US Naval War College's China Maritime Studies Institute. He is the author of Defending Taiwan: A Strategy to Prevent War with China (Oxford University Press, 2026), The Arsenal of Democracy: Technology, Industry, and Deterrence in an Age of Hard Choices (Hoover, 2025), and One Belt One Road: Chinese Power Meets the World (Harvard, 2021). References: •       Defending Taiwan: A Strategy to Prevent War with China by Eyck Freymann (Oxford University Press, 2026). •       “The Strait of Hormuz as a Template for Taiwan,” Financial Times, April 2026. By Eyck Freymann. •       Episode 2862: Truth Is Dead — on AI, disinformation, and American strategic confusion. About Keen On America Nobody asks more awkward questions than the Anglo-American writer and filmmaker Andrew Keen. In Keen On America, Andrew brings his pointed Transatlantic wit to making sense of the United States — hosting daily interviews about the history and future of this now venerable Republic. With nearly 2,800 episodes since the show launched on TechCrunch in 2010, Keen On America is the most prolific intellectual interview show in the history of podcasting. WebsiteSubstackYouTubeApple PodcastsSpotify 

If you think pitching is just about brand deal… then this episode is going to change how you see your entire business!Because the truth is: most creators are pitching in the smallest way possible and pitching is actually so much bigger than that.In this episode, I'm breaking down the opportunity strategy no one is teaching - how pitching can open doors for growth, visibility, relationships, and revenue in your business (not just sponsorships).We're diving into the 3 types of pitching every creator should be using… so you can start building a system that doesn't just wait for opportunities but actually creates them!

V12 Wrap Up Template - OT Figure King Josiah with Russell by TABC

(0:00) Re-Entry Monday football thoughts on the Patriots and Maxx Crosby, the NFL game in Australia, and Mike Vrabel at Arizona State's pro day last week. (11:49) A caller question on the Red Sox leads to a discussion on the teams spending in recent seasons. (28:12) Are the Milwaukee Brewers a template for how the Red Sox want to operate? (36:48) Resetting thoughts on Greg Weissert and his struggles early in the 2026 season. See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

The Prism of America's Education with Host Karen Schoen – At 3 AM on Friday, March 27th, in a near-empty chamber, you passed a bill by voice vote that excludes all funding for ICE and CBP. Let me repeat that: voice vote. No roll call. No record of who was there. No accountability. Just you, Barrasso, and a handful of senators shuffling paper in the dead of night while America slept. You could have...

Sometimes what God has promised isn’t exactly what we experience. What do we do when what God has said doesn’t seem to be the way things are? Pastor Mike Fabarez turns to an Old Testament character for clarity and encouragement.

Our conversation about the Bill Clinton and Monica Lewinsky affair continues, with a look at the changing media environment, the rise of FOX News, and how this created a template for the modern hyper-politicized scandal.Join our America250 newsletter community! Subscribe for free to get the latest news and analysis of how America250 is playing out. Paying subscribers get access to early, ad-free versions of the show. Plus bonus features throughout the year. To support our work and get access to everything, subscribe now.This Day is a proud member of Radiotopia from PRX.Your support helps foster independent, artist-owned podcasts and award-winning stories.If you want to support the show directly, you can do so on our website: ThisDayPod.comGet in touch if you have any ideas for future topics, or just want to say hello. Follow us on social @thisdaypodOur team: Jacob Feldman, Researcher/Producer; Khawla Nakua, Transcripts; music by Teen Daze and Blue Dot Sessions; Audrey Mardavich is our Executive Producer at Radiotopia. Learn about your ad choices: dovetail.prx.org/ad-choices

In January 1776, Thomas Paine told the American colonies to break free from their king. But what was supposed to come next? 250 years later, that question still doesn't have a good answer. To mark the anniversary of *Common Sense*, we traveled to Lewes, England, the town where Paine lived before he ever set foot in America, and recorded our first-ever LIVE episode inside Bull House, the building where Paine honed his ideas about citizens and their government. Joseph Adelman chairs a panel with scholars Leanne O'Boyle, Nicole Mahoney, and Jeanne Sheehan Zaino as they dig into the legacy of *Common Sense*: democracy's "day two problem," the women Paine wrote out of his own story, why "the law is king" keeps showing up on protest signs, and what a 15th-century building in a small English town can teach us about where democratic ideas actually take root. Recorded live in partnership with the Institute for Thomas Paine Studies at Iona University.Show Notes: https://www.benfranklinsworld.com/435 EPISODE OUTLINE00:00:00 Introduction00:01:06 What Happened After the Revolution?00:02:59 Live from the Bull House in Lewes, England00:04:49 A Template for Common Sense and Civic Life00:07:12 Thomas Paine's Legacy in Lewes, England00:10:24 Thomas Paine's Legacy in New Rochelle, New York00:16:04 Democracy's "Day Two Problem"00:22:50 Local Civic Engagement in Lewes00:27:46 Women and Common Sense00:34:54 Paine's Family Life in Lewes00:35:31 Reconstituting Government00:42:44 Violence and Change00:49:31 "No Kings" Protest and 'The Law is King'00:56:29 Thomas Paine's Legacy00:58:10 Audience Q&A01:18:20 Episode Wrap-UpRECOMMENDED NEXT EPISODES

As you know, the Hero's Journey is one of Paul's favorite tools to help his clients take on their challenges and begin to evolve into the people they are meant to be.Former Olympic Coach and Leadership Guru Chip Richards joins Paul on a deep dive into the Hero's Journey and how it can transform lives this week on Spirit Gym.Learn more about Chip on his website and on social media via YouTube, Instagram and Facebook. For Spirit Gym listeners: Chip is offering listeners a special discount to join him on a Heart of Leadership retreat, such as the upcoming trip to Tonga to swim with humpback whales, or to be part of the Heart of Leadership 12-month mentorship program. For more details and dates, reach out to Chip on his website and mention you heard him on Spirit Gym.Timestamps3:18 The Shero's Journey.6:09 Chip's long ago meetup with Paul in Australia that changed the story arc of his Australian Olympic Ski team.10:19 Parallel influences across oceans.26:16 Being mythed.32:01 The twisting, winding path of personal chaos is there to help us discover the divine essence within.41:06 Chip's first call to adventure as an elite athlete.51:51 Paul has experienced the Hero's Journey many times.1:07:06 “Who we really are is not the programming.”1:18:16 Tests and allies.1:27:39 A true commitment.1:34:10 What happens during the Hero's Journey when everything falls apart?1:39:03 Nature bathing surrounded by whales that allows people to let go and just be.1:56:39 “One of the things that makes [Paul's] work so special: You are living the myth we're talking about right now.”2:05:55 The elixir: The deeper answer that reveals why you went on this journey and become the embodied expression of that knowledge.2:15:48 The Hero's Journey: A journey from concept to experience.2:26:13 Tests that Chip and Paul are facing.2:34:15 Protecting the hives with very simple devotion.2:48:14 How to use the Hero's Journey as a self-reflection/self-realization tool. ResourcesThe Seed of Dreams by Chip RichardsWriting the Story Within by Chip RichardsThe Varroa miteFind more resources for this episode on our website.Music Credit: Meet Your Heroes (444Hz), Composed, mixed, mastered and produced by Michael RB Schwartz of Brave Bear MusicThanks to our awesome sponsors:PaleovalleyBIOptimizers US and BIOptimizers UK PAUL15Organifi CHEK20Wild PasturesKorrect SPIRITGYMPique LifeCHEK Institute We may earn commissions from qualifying purchases using affiliate links.

What if one of the most powerful testimonies of God's love in the scriptures comes from a woman whose story we often skip over? In this episode, BYU professor of ancient scripture Amy Easton discusses a compelling study of Hagar–the enslaved Egyptian woman who becomes the only person in the Old Testament to name God–by discussing her article "'You Are the God Who Sees Me': God's Loving-Kindness to Hagar." Professor Easton guides listeners into the heart of Hagar's story, showing how her experiences of trauma, exploitation, and exile reveal a God who is intimately aware of those on the margins. She highlights Hagar's transformative encounters in the wilderness, where God sees her, hears her, makes promises directly to her, and ultimately liberates her and her son. Through these moments, we come to understand a God who works both within hardship and beyond it. Further, Professor Easton explains how Hagar's story affirms a universal truth that God sees all His children and invites us to see and care for one another with that same loving‑kindness.    Publications:  "'You Are the God Who Sees Me': God's Loving-Kindness to Hagar," in Tender Mercies and Loving-Kindness: The Goodness of God in the Old Testament, Religious Studies Center (2026)  "A Multiplicity of Witnesses: Women and the Translation Process," with Rachel Cope, in A Hundredth Part: Exploring the History and Teachings of the Book of Mormon, Religious Studies Center (2023)  "Recognizing Responsibility and Standing with Victims: Studying Women of the Old Testament," in Covenant of Compassion: Caring for the Marginalized and Disadvantaged in the Old Testament, Religious Studies Center (2021)  "Lehi's Dream as a Template for Understanding Each Act of Nephi's Vision," in The Things Which My Father Saw: Approaches to Lehi's Dream and Nephi's Vision, Religious Studies Center (2011)    Click here to learn more about Amy Easton