Podcasts about restate

Benvenuti in questo nuovo episodio di 16NONI, dove analizziamo il panorama cinematografico attuale tra horror virali e grandi classici. Apriamo il sipario con Backrooms, l'inquietante esordio di Kane Parsons che, dopo aver spopolato sul web, conquista il grande schermo: un incubo liminale che gioca con la realtà, supportato da un cast di alto livello con Chiwetel Ejiofor e Renate Reinsve. Dalla tensione psicologica passiamo all’impegno civile con No Good Men della regista Shahrbanoo Sadat. Ambientato a Kabul, è un racconto potente sulla lotta di una donna per la propria dignità e la propria voce in un contesto dove il pregiudizio sembra dominare, offrendo uno sguardo crudo sulla condizione femminile poco prima del ritorno dei talebani. Infine, spazio alla nostalgia e alla grande regia: torna in sala, in una imperdibile versione integrale, Kill Bill: The Whole Bloody Affair. Un evento che riporta l’iconica “Sposa” di Tarantino sul grande schermo, mescolando arti marziali e vendetta in un’esperienza visiva totale. Restate sintonizzati, perché dopo il cinema ci addentreremo nelle serie TV più attese della stagione! L'articolo 16NONI: Incubi digitali, impegno sociale e il ritorno della Sposa proviene da Young Radio.

In the latest episode of the Radical Reformers podcast, Andrew Laird sits down with Joe Hill, Director of Strategy at Restate (and the winner of last year's Think Tanker of the Year award!), for a timely and thought-provoking conversation about the importance of really bold public service reform ideas. From his journey through the civil service and Treasury to his work shaping some of the most influential policy thinking in Westminster, Joe offers a fascinating perspective on how change really happens. At the heart of the episode is his powerful critique of “everythingism” - the idea that every policy should try to deliver every objective, everywhere, all at once. A problem many people working in public services will instantly recognise: blurred priorities, diluted focus and policy that tries to do too much. This episode is about the importance of new ideas, the role of think tanks in shifting debate, and why real reform depends on people being willing to say the uncomfortable thing out loud. Above all, it's a compelling call to be courageous - to think clearly, write honestly, challenge consensus and push for something better. If you care about public service reform, policy innovation and the future of government, head here to listen

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

Cari ascoltatori, la storia di Marco dimostra che ciò che spesso chiamiamo “amore romantico o spirituale” è in realtà l'architettura perfetta che il nostro Ego utilizza per punirsi, per non evolvere, per rimanere nell'ombra.Se passi la vita ad aspettare un fantasma che si nutre solo delle tue crisi, non stai compiendo una missione divina. Stai solo permettendo a un contratto inconscio di prosciugare la tua incarnazione attuale.La Nuova Frequenza della Terra non ammette più queste distorsioni. Il tempo delle maschere è finito.Se avverti che la tua vita sentimentale, professionale o finanziaria è ostaggio di un'attesa logorante, smetti di cercare risposte nei tarocchi o nelle teorie standard. Il tuo percorso è unico. Il tuo codice sorgente è unico.Quando sarai stanco di abitare una sala d'attesa e sarai pronto a riprendere il controllo del tuo destino, io sono qui per aiutarti a decodificare la tua Ferita Sacra.Non sprecare altri vent'anni. Il tunnel ha una fine, ma la porta si apre solo dall'interno.Prenota ora il tuo consulto privato per la lettura dei tuoi Registri Akashici.Smetti di aspettare il futuro. Inizia a crearlo.Restate nella verità del vostro potere.Diventa un supporter di questo podcast: https://www.spreaker.com/podcast/la-spa-dell-anima--4291391/support.

In this episode, Cindy Esliger discusses why receiving feedback can feel so emotionally overwhelming and how it can quietly derail careers if left unchecked. She describes the common experience of replaying performance reviews long after they happen, questioning our abilities, and letting a single piece of criticism overshadow everything else. Cindy focuses on how feedback often triggers imposter syndrome, especially in environments where scrutiny already feels high, and why learning to process criticism effectively is essential for building a resilient and successful career.  Cindy explains that our reactions to feedback are deeply connected to how our brains process perceived threats. Because of the brain's negativity bias, criticism can trigger a stress response that makes us defensive, emotional, or stuck replaying the conversation. She also highlights three red flags to watch for when receiving feedback, helping us recognize when criticism is useful and when it may simply be noise: 1. Distinguish between vague personal attacks and specific behavior-based feedback, 2. Pay attention to timing and setting, and 3. Notice when we start adding our own story.  To help us manage feedback more effectively, Cindy shares eight practical strategies for handling criticism without spiraling and instead turning it into useful information: 1. Pause before reacting to interrupt the emotional response, 2. Develop a feedback filter, 3. Seek clarification when feedback is vague or unclear, 4. Reframe the story we're telling ourselves about the feedback, 5. Look for patterns over time, 6. Respond thoughtfully instead of reacting impulsively, 7. Practice gratitude for the information, and 8. Restate and paraphrase the feedback to confirm understanding. By approaching criticism with curiosity and intention, Cindy reminds us that feedback doesn't have to become a spiral of self-doubt. Instead, it can become a powerful tool for growth, self-awareness, and building the career we truly want. Resources discussed in this episode: Guide to Handling Feedback Gracefully Astronomic Audio Confidence Collective — Contact Cindy Esliger  Career Confidence Coaching: website | instagram | facebook | linkedin | email Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

As is tradition, this week we're tackling the romances of all ten Best Picture nominees, from Sinners to Train Dreams! Join in as we discuss our favorite un-nominated romances, an unusually good(ish) year for Best Original Song, transportation logistics, and a few small beers. Plus: Are recliners bad for cinema? Why does Frankenstein look like that? Do we need to bring back projectionists? And is there any romance in Bugonia after all? Make sure to rate, review, and subscribe! Next week: Him (2025)-----------------------------------------------------Key sources and links for this episode:"Oscars: Film Academy Establishes Stunt Design Award" (The Hollywood Reporter)"KPop Demon Hunters is Officially Eligible for the Oscars" (Associated Press)"Only Two Original Song Nominees to Perform Live at Oscars" (Variety)"Matt Damon Says Netflix Wants Movies to Restate the Plot 'Three or Four Times in the Dialogue' because Viewers are on 'Their Phones while They're Watching'" (Variety)"Benicio Del Toro on Bonding with Leo, Rewriting PTA, and His First Oscar Nom in Decades" (The Hollywood Reporter)"I Survived the Long Walk Treadmill Challenge" (IndieWire)Cahiers du Cinema's rave review of Ella McCay (via Letterboxd)"The Secret Agent's Kleber Mendonca Filho and Wagner Moura on Brazil's Urban Legend of the Hairy Leg" (Deadline)

✨ Questa sera si accendono le luci su Speciale Sanremo 2026!

Il quadro di riferimento settimanale a cura del Team Advisory di Ersel per la settimana del 23 febbraio 2026. I principali temi:Nuovo dazio globale al 15%: In risposta alla sentenza, Trump ha firmato un nuovo ordine basato sull'Articolo 122 del Trade Act del 1974Situazione complessa anche per Su rimborsi per i dazi dichiarati illegittimi dalla Corte SupremaCome evolveranno gli accordi commerciali In attesa delle trimestrali di Nvidia del 25 febbraio dopo la chiusura di Wall Street: i mercati attendono con estrema attenzione questi dati, considerati il principale barometro per l'intero settore dell'Intelligenza Artificiale.Restate aggiornati e buon ascolto!l presente podcast è destinato esclusivamente a scopi informativi/ di marketing non sostituendosi al prospetto informativo o ad altri documenti legali di prodotti finanziari ivi eventualmente richiamati. Nel caso, si prega di consultare il prospetto dell'OICVM/documento informativo e il documento contenente le informazioni chiave per gli investitori (KID) prima di prendere una decisione finale di investimento che può essere effettuata solo previa valutazione dell'adeguatezza del servizio o dello strumento finanziario rispetto al profilo individuato con il questionario MiFID. Solo la versione più recente del prospetto, dei regolamenti, del Documento chiave per gli investitori, delle relazioni annuali e semestrali del fondo può essere utilizzata come base per decisioni di investimento. Il presente podcast non costituisce né un'offerta né una sollecitazione all'acquisto, alla sottoscrizione o alla vendita di prodotti o strumenti finanziari o una sollecitazione all'effettuazione di investimenti. Ersel ha verificato con la massima attenzione tutte le informazioni rappresentate nel presente podcast e compiuto sforzi per garantire che il contenuto di questo podcast sia basato su informazioni e dati ottenuti da fonti affidabili, ma non garantisce della loro esattezza e completezza non assumendosi alcuna responsabilità. Ersel non si assume alcuna responsabilità circa le informazioni, le proiezioni o le opinioni contenute nel presente podcast e non risponde dell'uso che terzi potrebbero fare di tali informazioni, né di eventuali perdite o danni che possano verificarsi in seguito a tale uso. Il presente podcast può fare riferimento alla performance passata degli investimenti: i rendimenti passati non sono indicativi di quelli attuali o futuri. Le indicazioni e i dati relativi agli strumenti finanziari, forniti dalla Società, non costituiscono necessariamente un indicatore delle future prospettive dell'investimento o disinvestimento. È vietata la riproduzione e/o la distribuzione del presente podcast, non espressamente autorizzata.

Il quadro di riferimento settimanale a cura del Team Advisory di Ersel per la settimana del 16 febbraio 2026. I principali temi:la rivoluzione copernicana in Europala novità in arrivo dalla Banca Centrale Europea sull'euroi negoziati tra Russia, Ucraina e Stati Unitil'andamento del settore IAil calmo recupero dell'oro  Restate aggiornati e buon ascolto!l presente podcast è destinato esclusivamente a scopi informativi/ di marketing non sostituendosi al prospetto informativo o ad altri documenti legali di prodotti finanziari ivi eventualmente richiamati. Nel caso, si prega di consultare il prospetto dell'OICVM/documento informativo e il documento contenente le informazioni chiave per gli investitori (KID) prima di prendere una decisione finale di investimento che può essere effettuata solo previa valutazione dell'adeguatezza del servizio o dello strumento finanziario rispetto al profilo individuato con il questionario MiFID. Solo la versione più recente del prospetto, dei regolamenti, del Documento chiave per gli investitori, delle relazioni annuali e semestrali del fondo può essere utilizzata come base per decisioni di investimento. Il presente podcast non costituisce né un'offerta né una sollecitazione all'acquisto, alla sottoscrizione o alla vendita di prodotti o strumenti finanziari o una sollecitazione all'effettuazione di investimenti. Ersel ha verificato con la massima attenzione tutte le informazioni rappresentate nel presente podcast e compiuto sforzi per garantire che il contenuto di questo podcast sia basato su informazioni e dati ottenuti da fonti affidabili, ma non garantisce della loro esattezza e completezza non assumendosi alcuna responsabilità. Ersel non si assume alcuna responsabilità circa le informazioni, le proiezioni o le opinioni contenute nel presente podcast e non risponde dell'uso che terzi potrebbero fare di tali informazioni, né di eventuali perdite o danni che possano verificarsi in seguito a tale uso. Il presente podcast può fare riferimento alla performance passata degli investimenti: i rendimenti passati non sono indicativi di quelli attuali o futuri. Le indicazioni e i dati relativi agli strumenti finanziari, forniti dalla Società, non costituiscono necessariamente un indicatore delle future prospettive dell'investimento o disinvestimento. È vietata la riproduzione e/o la distribuzione del presente podcast, non espressamente autorizzata.

Dal Vangelo secondo LucaIn quel tempo, il Signore designò altri settantadue e li inviò a due a due davanti a sé in ogni città e luogo dove stava per recarsi.Diceva loro: «La messe è abbondante, ma sono pochi gli operai! Pregate dunque il signore della messe, perché mandi operai nella sua messe! Andate: ecco, vi mando come agnelli in mezzo a lupi; non portate borsa, né sacca, né sandali e non fermatevi a salutare nessuno lungo la strada.In qualunque casa entriate, prima dite: “Pace a questa casa!”. Se vi sarà un figlio della pace, la vostra pace scenderà su di lui, altrimenti ritornerà su di voi. Restate in quella casa, mangiando e bevendo di quello che hanno, perché chi lavora ha diritto alla sua ricompensa. Non passate da una casa all'altra.Quando entrerete in una città e vi accoglieranno, mangiate quello che vi sarà offerto, guarite i malati che vi si trovano, e dite loro: “È vicino a voi il regno di Dio”».

In quel tempo, il Signore designò altri settantadue e li inviò a due a due davanti a sé in ogni città e luogo dove stava per recarsi. Diceva loro: «La messe è abbondante, ma sono pochi gli operai! Pregate dunque il signore della messe, perché mandi operai nella sua messe! Andate: ecco, vi mando come agnelli in mezzo a lupi; non portate borsa, né sacca, né sandali e non fermatevi a salutare nessuno lungo la strada. In qualunque casa entriate, prima dite: "Pace a questa casa!". Se vi sarà un figlio della pace, la vostra pace scenderà su di lui, altrimenti ritornerà su di voi. Restate in quella casa, mangiando e bevendo di quello che hanno, perché chi lavora ha diritto alla sua ricompensa. Non passate da una casa all'altra. Quando entrerete in una città e vi accoglieranno, mangiate quello che vi sarà offerto, guarite i malati che vi si trovano, e dite loro: "È vicino a voi il regno di Dio"».

Vorresti ricevere notizie, saluti, auguri dalle Apostole della Vita Interiore?Lasciaci i tuoi contatti cliccando il link qui sotto e con la nostra nuova rubrica digitale potremo raggiungerti.https://www.it.apostlesofil.com/database/- Premi il tasto PLAY per ascoltare la catechesi del giorno e condividi con altri se vuoi -+ Dal Vangelo secondo Luca +In quel tempo, il Signore designò altri settantadue e li inviò a due a due davanti a sé in ogni città e luogo dove stava per recarsi.Diceva loro: «La messe è abbondante, ma sono pochi gli operai! Pregate dunque il signore della messe, perché mandi operai nella sua messe! Andate: ecco, vi mando come agnelli in mezzo a lupi; non portate borsa, né sacca, né sandali e non fermatevi a salutare nessuno lungo la strada.In qualunque casa entriate, prima dite: "Pace a questa casa!". Se vi sarà un figlio della pace, la vostra pace scenderà su di lui, altrimenti ritornerà su di voi. Restate in quella casa, mangiando e bevendo di quello che hanno, perché chi lavora ha diritto alla sua ricompensa. Non passate da una casa all'altra.Quando entrerete in una città e vi accoglieranno, mangiate quello che vi sarà offerto, guarite i malati che vi si trovano, e dite loro: "È vicino a voi il regno di Dio"».Parola del Signore.

🧭 REBEL Rundown 📌 Key Points The 4 Steps of an ED Consult:👋 Introduce yourself and your role🎯 Lead with the outcome (the ask)🧾 Give a focused case summary (why it’s theirs + what you’ve done)🔁 Close the loop (timeline, next steps, contingencies) Click here for Direct Download of the Podcast. 📝 Introduction Today we’re tackling one of the most important (and most under-taught) skills in emergency medicine: how to call a consult in the ED and what to do when a consultant pushes back.To call a consult in the ED, start with a brief introduction, lead with the outcome you need (“the ask”), give a focused decision-relevant summary, and close the loop with timeline and next steps. If the consultant resists, clarify the “why,” restate the ask, offer alternatives, and escalate when patient safety or disposition is at risk.After two decades in emergency medicine and countless consult calls, here’s a simple framework—plus copy/paste scripts—to make your consults faster, clearer, and easier to say “yes” to. 🤔 Why Consult Skills Matter in Emergency Medicine Consults aren’t a formality—they’re a patient-care intervention. Strong consult communication:Reduces delays in time-sensitive careImproves ED throughput and dispositionDecreases conflict and miscommunicationClarifies ownership and next stepsProtects the patient (and the team) when plans are unclear 🪜 The 4-Step ED Consult Framework (Introduction → Ask → Summary → Close the Loop) Most consult friction comes from one of two problems: unclear expectations or excessive noise. This four-step structure solves both.1) Introduce yourself and your roleA simple intro sets a professional tone and removes ambiguity.Script: “Hey, this is Swami, one of the ED attendings. I’m calling for an ortho consult.” 2) Lead with the outcome (the ask)Don’t bury the lede. The consultant wants to know what you need—immediately.Script: “I’m calling about a patient with a suspected septic knee. I need you to evaluate for operative management.” 3) Give a focused, decision-relevant summaryYour summary should answer:Why this is your service’s problemWhat’s already been doneWhat I’m worried about / what decision is needed nowScript: “43-year-old man with no major PMH, 3 days of knee pain and swelling. XR negative. Febrile. Aspiration yielded purulent fluid—cultures sent. We started antibiotics after the tap. He’s hemodynamically stable.” High-yield pearl: Add quick “stability anchors” when relevant:“Airway stable, pain controlled.”“Neurovascularly intact.”“No signs of compartment syndrome.”“No hypotension or escalating oxygen requirement.” 4) Close the loop (timeline + next steps)This prevents the consult from floating in limbo and protects patient flow.Script: “When do you expect to see the patient, and do you want anything done before you arrive—NPO, repeat labs, additional imaging?” 📝 ED Consult Script General ED Consult Script “Hi, this is Dr. ___ in the ED. I’m calling for a ___ consult. The reason is ___. Briefly: ___ year-old with ___. We’ve done ___ and started ___. I’m concerned about ___. Can you see them today, and what’s your preferred next step?” Septic joint / Ortho Example “Hi, this is Swami in the ED. I need an ortho consult for suspected septic arthritis. 43-year-old with 3 days of atraumatic knee swelling and fever. XR negative. Tap produced purulent fluid—cultures sent. Antibiotics started after aspiration. Can you evaluate for operative management, and when can you see the patient?” Neurology example (time-sensitive) “Hi, this is Dr. ___ in the ED. I need neurology for suspected acute stroke. Last known well ___. NIHSS ___. CT/CTA completed (or pending). I’m calling to discuss candidacy for thrombolysis/thrombectomy and next steps. When can you evaluate and what additional workup do you want now?” ⛓️‍💥 Common ED Consult Mistakes (and Fixes) Mistake: Long story before the askFix: Lead with the outcome in the first sentenceMistake: Unfiltered data dumpFix: Provide only decision-relevant detailsMistake: No timelineFix: Ask explicitly when they’ll see the patient and what they need firstMistake: Implicit “ownership”Fix: Clarify who is admitting, who is following, and what happens if the patient worsens ✋ What to Do When a Consultant Pushes Back Even a perfect consult can meet resistance. Your job is to stay calm, keep it professional, and protect the patient.1) Ask “why?”Don’t argue first—diagnose the refusal.Script: “Help me understand your concern about seeing this patient.” Many refusals are based on misunderstanding: wrong service, missing key detail, or incorrect assumption about stability.2) Restate the consult in one sentence, then offer optionsIf the conversation starts spiraling, reset it.Script: “To be clear, I’m concerned this is septic arthritis and needs ortho evaluation. If you don’t feel you’re the right service, who should be—rheum, medicine, or another surgical team?” This keeps you collaborative while preventing dead ends.3) Humanize the decision (use sparingly)This is a “high-voltage” tool. Use it when stakes are high and you’ve already clarified the medical facts.Script: “I’m worried we’re missing something time-sensitive. If this were your family member, what would you want us to do next?” Use it to re-anchor to patient risk—not as a guilt tactic. ⚡️When and How to Escalate a Consult Escalation isn’t personal—it’s a safety mechanism when there’s an impasse that threatens timely care.When to escalateTime-sensitive condition is delayed (e.g., septic joint, cord compression, testicular torsion, GI bleed with instability)No clear disposition plan despite reasonable ED evaluationConsultant refusal blocks needed specialty decision-makingPatient safety or deterioration risk is increasing in the ED How to escalate (lowest to highest intensity)Ask for the consultant’s attending (if speaking to a resident)Call the on-call attending directlyInvolve ED leadership/medical directorEscalate to service chief/department chair (rare, but real)Hospital supervisor/admin escalation for immediate operational impasseScript: “We’re at an impasse and the patient needs a decision. I’m escalating to clarify ownership and ensure timely care.” ️ Documentation Tips for Consult Refusals Documentation should be factual and patient-centered, not punitive.Include:Your clinical concern and why the consult is neededWho you spoke with (name/role)Their stated reason for refusal or delayAlternatives discussedEscalation steps taken and final plan 👉 FAQ: Emergency Medicine Consults What is the best way to call a consult in the ED?Introduce yourself, lead with the specific ask, summarize only decision-relevant details, and close the loop with a clear plan and timeline.What should I say when a consultant refuses to see a patient?Ask why, clarify misunderstandings, restate your concern and the ask, and request an alternative plan or appropriate service.When should I escalate a consult?Escalate when an impasse delays time-sensitive care, threatens patient safety, or prevents appropriate disposition.How do I document a refused consult?Document the clinical concern, who you spoke with, their stated reason, alternatives discussed, and escalation steps taken. 🏁 Conclusion Mastering emergency medicine consults makes you faster, safer, and easier to work with. The goal isn’t to “win” a consult call—it’s to get the patient the right care, with clear ownership and a shared plan. Post Peer Reviewed By: Marco Propersi, DO (Twitter/X: @Marco_propersi), and Mark Ramzy, DO (X: @MRamzyDO) 👤 Associate Editor Anand Swaminathan MD, MPH All Things REBEL EM Meet The Team 🔎 Your Deep-Dive Starts Here REBEL Core Cast – Pediatric Respiratory Emergencies: Beyond Viral Season Welcome to the Rebel Core Content Blog, where we delve ... Pediatrics Read More REBEL Core Cast 143.0–Ventilators Part 3: Oxygenation & Ventilation — Mastering the Balance on the Ventilator When you take the airway, you take the wheel and ... Thoracic and Respiratory Read More REBEL Core Cast 142.0–Ventilators Part 2: Simplifying Mechanical Ventilation – Most Common Ventilator Modes Mechanical ventilation can feel overwhelming, especially when faced with a ... Thoracic and Respiratory Read More REBEL Core Cast 141.0–Ventilators Part 1: Simplifying Mechanical Ventilation — Types of Breathes For many medical residents, the ICU can feel like stepping ... Thoracic and Respiratory Read More REBEL Core Cast 140.0: The Power and Limitations of Intraosseous Lines in Emergency Medicine The sicker the patient, the more likely an IO line ... Procedures and Skills Read More REBEL Core Cast 139.0: Pneumothorax Decompression On this episode of the Rebel Core Cast, Swami takes ... Procedures and Skills Read More The post REBEL Core Cast 150.0: Emergency Medicine Consults: How to Call a Consult + Handle Pushback (With Scripts) appeared first on REBEL EM - Emergency Medicine Blog.

Eccoci qui in un nuovo episodio! Oggi parliamo di sogni lontani e scelte che ti fanno girare la testa: la fuga di cervelli in Australia. E se davvero ci trasferissimo… secondo voi, i nostri partner ci seguirebbero in questa avventura o ci lascerebbero partire da soli? Restate con noi, che ne chiacchieriamo insieme!

In quel tempo, il Signore designò altri settantadue e li inviò a due a due davanti a sé in ogni città e luogo dove stava per recarsi. Diceva loro: «La messe è abbondante, ma sono pochi gli operai! Pregate dunque il signore della messe, perché mandi operai nella sua messe! Andate: ecco, vi mando come agnelli in mezzo a lupi; non portate borsa, né sacca, né sandali e non fermatevi a salutare nessuno lungo la strada. In qualunque casa entriate, prima dite: "Pace a questa casa!". Se vi sarà un figlio della pace, la vostra pace scenderà su di lui, altrimenti ritornerà su di voi. Restate in quella casa, mangiando e bevendo di quello che hanno, perché chi lavora ha diritto alla sua ricompensa. Non passate da una casa all'altra. Quando entrerete in una città e vi accoglieranno, mangiate quello che vi sarà offerto, guarite i malati che vi si trovano, e dite loro: "È vicino a voi il regno di Dio"».

Dal Vangelo secondo Luca (10,1-9)In quel tempo, il Signore designò altri settantadue e li inviò a due a due davanti a sé in ogni città e luogo dove stava per recarsi.Diceva loro: «La messe è abbondante, ma sono pochi gli operai! Pregate dunque il signore della messe, perché mandi operai nella sua messe! Andate: ecco, vi mando come agnelli in mezzo a lupi; non portate borsa, né sacca, né sandali e non fermatevi a salutare nessuno lungo la strada.In qualunque casa entriate, prima dite: “Pace a questa casa!”. Se vi sarà un figlio della pace, la vostra pace scenderà su di lui, altrimenti ritornerà su di voi. Restate in quella casa, mangiando e bevendo di quello che hanno, perché chi lavora ha diritto alla sua ricompensa. Non passate da una casa all'altra.Quando entrerete in una città e vi accoglieranno, mangiate quello che vi sarà offerto, guarite i malati che vi si trovano, e dite loro: “È vicino a voi il regno di Dio”».

Vorresti ricevere notizie, saluti, auguri dalle Apostole della Vita Interiore?Lasciaci i tuoi contatti cliccando il link qui sotto e con la nostra nuova rubrica digitale potremo raggiungerti.https://www.it.apostlesofil.com/database/- Premi il tasto PLAY per ascoltare la catechesi del giorno e condividi con altri se vuoi -+ Dal Vangelo secondo Marco +In quel tempo, il Signore designò altri settantadue e li inviò a due a due davanti a sé in ogni città e luogo dove stava per recarsi.Diceva loro: «La messe è abbondante, ma sono pochi gli operai! Pregate dunque il signore della messe, perché mandi operai nella sua messe! Andate: ecco, vi mando come agnelli in mezzo a lupi; non portate borsa, né sacca, né sandali e non fermatevi a salutare nessuno lungo la strada.In qualunque casa entriate, prima dite: "Pace a questa casa!". Se vi sarà un figlio della pace, la vostra pace scenderà su di lui, altrimenti ritornerà su di voi. Restate in quella casa, mangiando e bevendo di quello che hanno, perché chi lavora ha diritto alla sua ricompensa. Non passate da una casa all'altra.Quando entrerete in una città e vi accoglieranno, mangiate quello che vi sarà offerto, guarite i malati che vi si trovano, e dite loro: "È vicino a voi il regno di Dio"».Parola del Signore.

Nel primo episodio della serie “Il lato nascosto delle sostanze psicoattive”, Francesca e Luca ci accompagnano in un viaggio che unisce mito, scienza e curiosità sorprendenti.Dalle antiche immagini dell'auriga Elio ai primi esperimenti sulla “biologia del tempo”, scopriamo come è nato il concetto di ciclo circadiano, l'orologio interno che regola sonno, energia, ormoni ed emozioni.L'episodio esplora anche cosa accade nel cervello quando ci svegliamo, il ruolo dell'adenosina e il modo in cui la caffeina riesce a ingannare i nostri segnali di stanchezza, influenzando vigilanza e qualità del sonno.Non mancano chicche inaspettate, come gli studi della NASA sui ragni esposti a sostanze psicoattive.Potete ascoltare l'episodio completo iscrivendovi al Supporters club di Spreaker o tramite donazione Paypal. In cerca di regali natalizi alternativi per i vostri amici nerd? Regala un abbonamento al supporters club di Scientificast. Questa puntata ricca e sorprendente, apre la strada ai prossimi approfondimenti sul caffè e su altre sostanze che modificano i nostri ritmi più profondi. Restate sintonizzati!https://www.spreaker.com/podcast/scientificast-la-scienza-come-non-l-hai-mai-sentita--1762253/support

Nel mese dedicato all'educazione finanziaria a livello globale, Ersel torna a riflettere sui valori chiave di questa disciplina. Federica De Giorgis, Financial Advisory di Ersel, ci guida in un percorso chiaro e concreto: investire è davvero per tutti. Come per qualsiasi maratona l'allenamento è fondamentale e anche per investire serve tempo, costanza e pazienza. Lo studio e la gestione delle proprie emozioni sono la base per investire in maniera sicura. In un'epoca in cui i social pullulano di “guru” improvvisati, è essenziale conoscere la materia per distinguere la fuffa. Restate aggiornati, ascoltateci e iniziate a costruire la vostra consapevolezza finanziaria!#comunicazionedimarketingIl presente podcast non intende in alcun modo promuovere la sottoscrizione di servizi e prodotti finanziari che può essere effettuata solo dopo aver preso visione dell'informativa precontrattuale e previa valutazione dell'adeguatezza del servizio o dello strumento finanziario rispetto al profilo individuato con il questionario MiFID. Il presente podcast non è un documento contrattualmente vincolante né un documento informativo necessario ai sensi di una disposizione legislativa e non è sufficiente per prendere una decisione di investimento.Ersel ha verificato con la massima attenzione tutte le informazioni rappresentate nella presente registrazione, ma non garantisce della loro esattezza e completezza, e non risponde dell'uso che terzi potrebbero fare di tali informazioni, né di eventuali perdite o danni che possano verificarsi in seguito a tale uso. Le indicazioni e i dati relativi agli strumenti finanziari, forniti dalla Società nel presente video, non costituiscono necessariamente un indicatore delle future prospettive dell'investimento o disinvestimento: i rendimenti passati non sono indicativi di quelli futuri. È vietata la riproduzione e/o la distribuzione, in tutto o in parte, direttamente o indirettamente, del presente podcast, non espressamente autorizzata.

ll quadro di riferimento settimanale a cura del Team Advisory di Ersel per la settimana del 3 novembre 2025. I principali temi: le riunioni della Bce e Fed, tassi e inflazione, i nuovi massimi del mercato azionario, l'attenzione sull'energia e intelligenza artificiale, gli aggiornamenti sulla situazione geopolitica. Restate aggiornati e buon ascolto!Il presente podcast è destinato esclusivamente a scopi informativi/ di marketing non sostituendosi al prospetto informativo o ad altri documenti legali di prodotti finanziari ivi eventualmente richiamati. Nel caso, si prega di consultare il prospetto dell'OICVM/documento informativo e il documento contenente le informazioni chiave per gli investitori (KID) prima di prendere una decisione finale di investimento che può essere effettuata solo previa valutazione dell'adeguatezza del servizio o dello strumento finanziario rispetto al profilo individuato con il questionario MiFID. Solo la versione più recente del prospetto, dei regolamenti, del Documento chiave per gli investitori, delle relazioni annuali e semestrali del fondo può essere utilizzata come base per decisioni di investimento. Il presente podcast non costituisce né un'offerta né una sollecitazione all'acquisto, alla sottoscrizione o alla vendita di prodotti o strumenti finanziari o una sollecitazione all'effettuazione di investimenti. Ersel ha verificato con la massima attenzione tutte le informazioni rappresentate nel presente podcast e compiuto sforzi per garantire che il contenuto di questo podcast sia basato su informazioni e dati ottenuti da fonti affidabili, ma non garantisce della loro esattezza e completezza non assumendosi alcuna responsabilità. Ersel non si assume alcuna responsabilità circa le informazioni, le proiezioni o le opinioni contenute nel presente podcast e non risponde dell'uso che terzi potrebbero fare di tali informazioni, né di eventuali perdite o danni che possano verificarsi in seguito a tale uso. Il presente podcast può fare riferimento alla performance passata degli investimenti: i rendimenti passati non sono indicativi di quelli attuali o futuri. Le indicazioni e i dati relativi agli strumenti finanziari, forniti dalla Società, non costituiscono necessariamente un indicatore delle future prospettive dell'investimento o disinvestimento. È vietata la riproduzione e/o la distribuzione del presente podcast, non espressamente autorizzata.

ll quadro di riferimento settimanale a cura del Team Advisory di Ersel per la settimana del 27 ottobre 2025. I principali temi: gli incontri del weekend tra Bessent e Vicepremier cinese, le attese per le trimestrali, banche centrali e tagli di tassi, il mercato bond americano, la settimana volatile per l'oro. Restate aggiornati e buon ascolto!Il presente podcast è destinato esclusivamente a scopi informativi/ di marketing non sostituendosi al prospetto informativo o ad altri documenti legali di prodotti finanziari ivi eventualmente richiamati. Nel caso, si prega di consultare il prospetto dell'OICVM/documento informativo e il documento contenente le informazioni chiave per gli investitori (KID) prima di prendere una decisione finale di investimento che può essere effettuata solo previa valutazione dell'adeguatezza del servizio o dello strumento finanziario rispetto al profilo individuato con il questionario MiFID. Solo la versione più recente del prospetto, dei regolamenti, del Documento chiave per gli investitori, delle relazioni annuali e semestrali del fondo può essere utilizzata come base per decisioni di investimento. Il presente podcast non costituisce né un'offerta né una sollecitazione all'acquisto, alla sottoscrizione o alla vendita di prodotti o strumenti finanziari o una sollecitazione all'effettuazione di investimenti. Ersel ha verificato con la massima attenzione tutte le informazioni rappresentate nel presente podcast e compiuto sforzi per garantire che il contenuto di questo podcast sia basato su informazioni e dati ottenuti da fonti affidabili, ma non garantisce della loro esattezza e completezza non assumendosi alcuna responsabilità. Ersel non si assume alcuna responsabilità circa le informazioni, le proiezioni o le opinioni contenute nel presente podcast e non risponde dell'uso che terzi potrebbero fare di tali informazioni, né di eventuali perdite o danni che possano verificarsi in seguito a tale uso. Il presente podcast può fare riferimento alla performance passata degli investimenti: i rendimenti passati non sono indicativi di quelli attuali o futuri. Le indicazioni e i dati relativi agli strumenti finanziari, forniti dalla Società, non costituiscono necessariamente un indicatore delle future prospettive dell'investimento o disinvestimento. È vietata la riproduzione e/o la distribuzione del presente podcast, non espressamente autorizzata.

ll quadro di riferimento settimanale a cura del Team Advisory di Ersel per la settimana del 20 ottobre 2025. I principali temi: nuovi record storici dell'indice azionario, la guerra commerciale tra Cina e Stati Uniti, l'accordo sul cessate il fuoco su Gaza, il report delle trimestrali, le novità dall'Ucraina, la corsa all'oro, la situazione francese traballante. Restate aggiornati e buon ascolto!Il presente podcast è destinato esclusivamente a scopi informativi/ di marketing non sostituendosi al prospetto informativo o ad altri documenti legali di prodotti finanziari ivi eventualmente richiamati. Nel caso, si prega di consultare il prospetto dell'OICVM/documento informativo e il documento contenente le informazioni chiave per gli investitori (KID) prima di prendere una decisione finale di investimento che può essere effettuata solo previa valutazione dell'adeguatezza del servizio o dello strumento finanziario rispetto al profilo individuato con il questionario MiFID. Solo la versione più recente del prospetto, dei regolamenti, del Documento chiave per gli investitori, delle relazioni annuali e semestrali del fondo può essere utilizzata come base per decisioni di investimento. Il presente podcast non costituisce né un'offerta né una sollecitazione all'acquisto, alla sottoscrizione o alla vendita di prodotti o strumenti finanziari o una sollecitazione all'effettuazione di investimenti. Ersel ha verificato con la massima attenzione tutte le informazioni rappresentate nel presente podcast e compiuto sforzi per garantire che il contenuto di questo podcast sia basato su informazioni e dati ottenuti da fonti affidabili, ma non garantisce della loro esattezza e completezza non assumendosi alcuna responsabilità. Ersel non si assume alcuna responsabilità circa le informazioni, le proiezioni o le opinioni contenute nel presente podcast e non risponde dell'uso che terzi potrebbero fare di tali informazioni, né di eventuali perdite o danni che possano verificarsi in seguito a tale uso. Il presente podcast può fare riferimento alla performance passata degli investimenti: i rendimenti passati non sono indicativi di quelli attuali o futuri. Le indicazioni e i dati relativi agli strumenti finanziari, forniti dalla Società, non costituiscono necessariamente un indicatore delle future prospettive dell'investimento o disinvestimento. È vietata la riproduzione e/o la distribuzione del presente podcast, non espressamente autorizzata.

In quel tempo, il Signore designò altri settantadue e li inviò a due a due davanti a sé in ogni città e luogo dove stava per recarsi. Diceva loro: «La messe è abbondante, ma sono pochi gli operai! Pregate dunque il signore della messe, perché mandi operai nella sua messe! Andate: ecco, vi mando come agnelli in mezzo a lupi; non portate borsa, né sacca, né sandali e non fermatevi a salutare nessuno lungo la strada. In qualunque casa entriate, prima dite: "Pace a questa casa!". Se vi sarà un figlio della pace, la vostra pace scenderà su di lui, altrimenti ritornerà su di voi. Restate in quella casa, mangiando e bevendo di quello che hanno, perché chi lavora ha diritto alla sua ricompensa. Non passate da una casa all'altra. Quando entrerete in una città e vi accoglieranno, mangiate quello che vi sarà offerto, guarite i malati che vi si trovano, e dite loro: "È vicino a voi il regno di Dio"».

Dal Vangelo secondo LucaIn quel tempo, il Signore designò altri settantadue e li inviò a due a due davanti a sé in ogni città e luogo dove stava per recarsi.Diceva loro: «La messe è abbondante, ma sono pochi gli operai! Pregate dunque il signore della messe, perché mandi operai nella sua messe! Andate: ecco, vi mando come agnelli in mezzo a lupi; non portate borsa, né sacca, né sandali e non fermatevi a salutare nessuno lungo la strada.In qualunque casa entriate, prima dite: “Pace a questa casa!”. Se vi sarà un figlio della pace, la vostra pace scenderà su di lui, altrimenti ritornerà su di voi. Restate in quella casa, mangiando e bevendo di quello che hanno, perché chi lavora ha diritto alla sua ricompensa. Non passate da una casa all'altra.Quando entrerete in una città e vi accoglieranno, mangiate quello che vi sarà offerto, guarite i malati che vi si trovano, e dite loro: “È vicino a voi il regno di Dio”».

- Premi il tasto PLAY per ascoltare la catechesi del giorno e condividi con altri se vuoi -+ Dal Vangelo secondo Luca +In quel tempo, il Signore designò altri settantadue e li inviò a due a due davanti a sé in ogni città e luogo dove stava per recarsi.Diceva loro: «La messe è abbondante, ma sono pochi gli operai! Pregate dunque il signore della messe, perché mandi operai nella sua messe! Andate: ecco, vi mando come agnelli in mezzo a lupi; non portate borsa, né sacca, né sandali e non fermatevi a salutare nessuno lungo la strada.In qualunque casa entriate, prima dite: "Pace a questa casa!". Se vi sarà un figlio della pace, la vostra pace scenderà su di lui, altrimenti ritornerà su di voi. Restate in quella casa, mangiando e bevendo di quello che hanno, perché chi lavora ha diritto alla sua ricompensa. Non passate da una casa all'altra.Quando entrerete in una città e vi accoglieranno, mangiate quello che vi sarà offerto, guarite i malati che vi si trovano, e dite loro: "È vicino a voi il regno di Dio"».Parola del Signore.

Bentornati a questo nuovo episodio di Purpose, i podcast di Ersel dedicati alla responsabilità sociale di impresa. Oggi Valeria Ferrero, Responsabile ESG Strategy del Gruppo Ersel, intervista Giovanna Gregori, Executive Director di Aidaf – Associazione Italiana delle Aziende Familiari, focalizzandosi su temi di governance con un viaggio molto interessante nelle imprese familiari, pilastro fondamentale dell'economia italiana. L'associazione, nata nel 1997, lavora da quasi trent'anni per sostenere la crescita, la governance e la responsabilità intergenerazionale delle famiglie imprenditoriali. Il podcast analizza il ruolo di Aidaf nel rafforzare le imprese familiari italiane, i valori fondativi e la visione di lungo periodo e le riflessioni emerse dal XX Convegno nazionale appena concluso a Torino. Il futuro delle imprese familiari non si misura solo con i numeri, ma con la capacità di guardare lontano con visione di lungo termine e il compito di chi guida oggi è quello di lavorare con strutture di governance trasparenti lasciando dunque alle nuove generazioni non solo aziende solide e innovative, ma anche una cultura di governance che sia inclusiva, sostenibile e lungimirante. Restate aggiornati e buon ascolto!#comunicazionedimarketingIl presente podcast è destinato esclusivamente a scopi informativi/ di marketing non sostituendosi al prospetto informativo o ad altri documenti legali di prodotti finanziari ivi eventualmente richiamati. Nel caso, si prega di consultare il prospetto dell'OICVM/documento informativo e il documento contenente le informazioni chiave per gli investitori (KID) prima di prendere una decisione finale di investimento che può essere effettuata solo previa valutazione dell'adeguatezza del servizio o dello strumento finanziario rispetto al profilo individuato con il questionario MiFID. Solo la versione più recente del prospetto, dei regolamenti, del Documento chiave per gli investitori, delle relazioni annuali e semestrali del fondo può essere utilizzata come base per decisioni di investimento. Il presente podcast non costituisce né un'offerta né una sollecitazione all'acquisto, alla sottoscrizione o alla vendita di prodotti o strumenti finanziari o una sollecitazione all'effettuazione di investimenti. Ersel ha verificato con la massima attenzione tutte le informazioni rappresentate nel presente podcast e compiuto sforzi per garantire che il contenuto di questo podcast sia basato su informazioni e dati ottenuti da fonti affidabili, ma non garantisce della loro esattezza e completezza non assumendosi alcuna responsabilità. Ersel non si assume alcuna responsabilità circa le informazioni, le proiezioni o le opinioni contenute nel presente podcast e non risponde dell'uso che terzi potrebbero fare di tali informazioni, né di eventuali perdite o danni che possano verificarsi in seguito a tale uso. Il presente podcast può fare riferimento alla performance passata degli investimenti: i rendimenti passati non sono indicativi di quelli attuali o futuri. Le indicazioni e i dati relativi agli strumenti finanziari, forniti dalla Società, non costituiscono necessariamente un indicatore delle future prospettive dell'investimento o disinvestimento. È vietata la riproduzione e/o la distribuzione del presente podcast, non espressamente autorizzata.

More Chapters

More Chapters AI Contribution: Courtesy of Google NotebookLM

In this episode of Building Better Developers with AI, hosts Rob Broadhead and Michael Meloche revisit an earlier conversation—this time through the lens of AI—to explore how constructive communication in software development creates healthier teams and better code. By analyzing their original “Advocating vs. Arguing” discussion, they uncover new ways to transform conflict into collaboration. “The goal is never to win. The goal is to find the best solution.” – Rob Broadhead What Constructive Communication Really Means Rob draws a clear line between two mindsets: Constructive communication invites evidence, empathy, and openness. Defensive arguing focuses on winning, often shutting down valuable ideas. This subtle difference determines whether a team works together to solve problems or gets stuck in endless debates. Why Constructive Communication Improves Software Development Software projects depend on diverse skills and experiences. When team members communicate constructively: Blind spots shrink. Different perspectives uncover hidden issues. Technical debt decreases. Shared understanding prevents costly rework. Client trust grows. Positive dialogue strengthens long-term relationships. Rob highlights how even an outsider's insight—like a .NET developer's idea on a Python project—can spark innovative solutions. Practical Steps to Encourage Constructive Communication Michael offers proven techniques to keep discussions positive and productive: Ask clarifying questions. Instead of “That won't work,” try “How do you see that working in this context?” Restate what you heard. Confirm understanding before you respond. Stay curious. Open-ended questions invite deeper exploration. “No is a conversation killer. Replace it with ‘Let's consider that.'” – Michael Meloche Spotting When Communication Turns Unproductive Arguments often start subtly. Watch for these warning signs: Absolutes such as “always” or “never.” Interrupting or talking over teammates. Ego-driven choices that ignore user needs or project goals. Rob recommends slowing the pace when tempers rise—pause the meeting, schedule a follow-up, or ask everyone to write down their thoughts before reconvening. Agile Practices Support Constructive Communication Rob and Michael agree that Agile's built-in rituals—backlog refinement, iterative feedback, and sprint reviews—naturally encourage constructive communication in software development. If a team frequently argues, it may be skipping these essential steps. Michael also suggests a weekly “water-cooler” session where team members share new ideas or lessons learned. These informal gatherings nurture creativity and trust. Leadership Sets the Tone Managers and leads can reinforce constructive habits by: Checking in with teammates who seem defensive or frustrated. Offering mentoring or personal support when tension surfaces. Encouraging team traditions—from inside jokes to shared hobbies—that build rapport. Rob observes that the best teams always share a unique bond, whether it's dad jokes or a favorite game, which helps them weather stressful moments. Reader Challenge: Practice Constructive Communication This Week Your Mission: Over the next seven days, pick one team interaction—a stand-up, code review, or planning meeting—and intentionally practice constructive communication in software development. Steps to Try: Listen First. Before offering your idea, restate someone else's point to confirm understanding. Replace “No” with Curiosity. When you disagree, ask an open question like “How do you see that working with our current sprint goals?” Log the Outcome. After the meeting, jot down what changed: Did the discussion stay more positive? Did new solutions surface? Share your results with your team—or even comment on the blog post—to inspire others. Challenge yourself: Can you turn at least one potential argument into a moment of advocacy this week? Key Takeaway: Build a Culture of Constructive Communication This episode underscores that constructive communication in software development is more than a soft skill—it's a project-saver. By listening first, asking better questions, and validating every voice, teams can replace conflict with collaboration and move projects forward with confidence. “Choosing one approach together is better than arguing endlessly about the perfect one.” – Rob Broadhead Whether you're leading a sprint, conducting a code review, or gathering requirements, focusing on constructive communication ensures that every idea is heard—and the best solutions rise to the top. Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources Honest Communication Is Critical For Consultants When To Vent (never) as part of Consulting Communication Use Written Communication To Improve Your Standing And Career Communication Noise vs. Content The Developer Journey Videos – With Bonus Content Building Better Developers With AI Podcast Videos – With Bonus Content

Stigall's theme today is messaging and who's winning it or losing it on multiple fronts. Brilliant commentary from Restate.com's Bonchie on the LA riots and how President Trump, the DOJ, and FBI are handling the criminals versus the Democrats who are desperate to make the public believe this is peaceful, organic, and even "fun." Former White House Press Secretary Sean Spicer discusses the messaging in the Tump/Elon battle as well as the future of the "big, beautiful bill." Chief economist Steve Moore also ads his thoughts on the messaging from entities like the CBO and their scoring of the big, beautiful bill. How about Rand Paul's opposition to the debt ceiling being raised? And the administration meets with China in London this week. Who's holding the cards? Plus, Stigall has some special messages for his show spiritual advisor as well as his wife Christine on a very special day. -For more info visit the official website: https://chrisstigall.comInstagram: https://www.instagram.com/chrisstigallshow/Twitter: https://twitter.com/ChrisStigallFacebook: https://www.facebook.com/chris.stigall/Listen on Spotify: https://tinyurl.com/StigallPodListen on Apple Podcasts: https://bit.ly/StigallShow -Help protect your wealth with real, physical gold and silver. Texas Bullion Exchange helps everyday Americans diversify with tailored portfolios, IRA rollovers, and expert support every step of the way.

A major challenge with creating distributed applications is achieving resilience, reliability, and fault tolerance. It can take considerable engineering time to address non-functional concerns like retries, state synchronization, and distributed coordination. Event-driven models aim to simplify these issues, but often introduce new difficulties in debugging and operations. Stephan Ewen is the Founder at Restate which The post Modern Distributed Applications with Stephan Ewen appeared first on Software Engineering Daily.

Stephan Ewen, Founder and CEO of Restate.dev joins the show to talk about the coming era of resilient apps, the meaning of and what it takes to achieve idempotency, this world of stateful durable execution functions, and when it makes sense to reach for this tech.

Stephan Ewen, Founder and CEO of Restate.dev joins the show to talk about the coming era of resilient apps, the meaning of and what it takes to achieve idempotency, this world of stateful durable execution functions, and when it makes sense to reach for this tech.

In part one I introduced you to the story of Jehoshaphat, one of the kings of Judah. It is found in 2 Chronicles 20 and is one of my favorite chapters in the Bible. I encourage you to read it for yourself; if you have time now, open your Bible to the 20th chapter of 2 Chronicles and follow along with me. Judah was the smallest of the two Israeli nations, with only two tribes. They were headquartered in Jerusalem, but they were small and not really equipped to fight a large enemy army. Yet, in this chapter we learn that all of a sudden three enemy armies are headed their way with the full intent to destroy all of them and take over their land. We saw how Jehoshaphat responded when he heard this frightening news. He was alarmed, as you would expect, but his first move was to inquire of the Lord. Then, from his prayer, we are gleaning seven R's that tell us what we should do when we don't know what to do. Truly Jehoshaphat had no plan of how they could ever defeat this great army coming against them. But instead of feeling sorry for himself or running away or giving up, he inquired of the Lord. First, he recited who God was, so he and his people would be God-centered instead of problem-focused. Then he remembered how God had been faithful to them in times past—he remembered how God had always been with them. So, the first two R's are: Recite who God is. Remember what God has done for you in the past. Now, we begin with the third R: #3: Recall God's promises. That's what Jehoshaphat does next. He says: If calamity comes upon us...we will stand in your presence before this temple that bears your Name and will cry out to you in our distress, and you will hear us and save us (2 Chronicles 20:9). God had given them the promise that if they would stand in his presence before the temple and cry out to God, he would hear and save them. Jehoshaphat was claiming that promise. He didn't need to remind God of his promise; he needed to recall it himself and the people of Judah needed to remember how God had promised to take care of them. The Bible has promises there just for you, did you know that? Have you learned to turn to God's Word and ask for a promise when you face an impossible situation? I remember when I first started this ministry in 1984 on one station in Chicago. That's all I ever figured it would be, and I was thrilled that God had given me that opportunity. Then shortly after, opportunities began to open, and it dawned on me that this ministry could grow and become much larger than I'd ever imagined. And I was frightened; I knew how inadequate I was for such an assignment. I knew how inexperienced I was. And I really wanted to back out. But I couldn't deny that God had opened the doors in a miraculous way. So, I sat down with my Bible and prayed, "Lord, if this is a ministry you have for me, then please, give me a promise to hang on to as I embark upon it, because I know there will be days and times when I will want to quit.”  Well, my reading that day included Isaiah 50, and right there in that wonderful chapter is God's promise for me. Let me share it with you: The Sovereign Lord has given me an instructed tongue, to know the word that sustains the weary. . .  Because the Sovereign Lord helps me, I will not be disgraced. Therefore I have set my face like flint, and I know I will not be put to shame (Isaiah 50: 4-7). I knew that was God's promise to me. Those verses are now framed in my office, and I can't tell you how many times I've gone back to them when I've been discouraged, when I've been tired, when I've been wearied of the responsibility. And that promise has sustained me and strengthened me to set my face like flint and claim the promise that I would not be put to shame. Do you need a promise from God right now? Go to his Word and ask for it; God will give one to you, too. #4: Restate the problem to God. Now, after Jehoshaphat has recited who God is,

- Premere il tasto PLAY per ascoltare la catechesi del giorno -+ Dal Vangelo secondo Luca +In quel tempo, il Signore designò altri settantadue e li inviò a due a due davanti a sé in ogni città e luogo dove stava per recarsi.Diceva loro: «La messe è abbondante, ma sono pochi gli operai! Pregate dunque il signore della messe, perché mandi operai nella sua messe! Andate: ecco, vi mando come agnelli in mezzo a lupi; non portate borsa, né sacca, né sandali e non fermatevi a salutare nessuno lungo la strada.In qualunque casa entriate, prima dite: "Pace a questa casa!". Se vi sarà un figlio della pace, la vostra pace scenderà su di lui, altrimenti ritornerà su di voi. Restate in quella casa, mangiando e bevendo di quello che hanno, perché chi lavora ha diritto alla sua ricompensa. Non passate da una casa all'altra.Quando entrerete in una città e vi accoglieranno, mangiate quello che vi sarà offerto, guarite i malati che vi si trovano, e dite loro: "È vicino a voi il regno di Dio"».Parola del Signore.

6 R'S OF THE SELF MOTIVATION CYCLE MOTIVATION CYCLE: REALIZE - RESOLVE - RESTATE - RESTART - REACH - RESULTS REALIZE - vocalize your awareness that what you wanted didn't happen - you missed the target/ goal/ opportunity  RESOLVE - you must find the passion, confidence and commitment to keep on anyway in the face of perceived failure and profound obstacles  RESTATE - you must frame the story of ‘missed expectations' as a learning experience and apply those lessons to future goal setting instruction and plans - acknowledge every small success as starter fluid for momentum RESTART - you must redouble your effort, action and focus with more intensity than before (apply 10X Rule Thinking here) REACH - Success is like swimming- you have to stretch and pull with each arm repeatedly until you reach your target - one arm won't do it. Doggie paddles won't do it. Survival swimming won't get you there. RESULTS - What looks like LUCK to others is the result of perpetual plan and persistent action continually recreating achievement and success momentum. SUCCESS BEGETS SUCCESS. “ J Loren Norris See Attitude Hack in www.StoryPowerAcademy.com for more “StoryPower is an Inside Job” J Loren Norris Watch the video 1-15-25: Online Academy for Leadership & Communication:⁠⁠⁠⁠⁠⁠⁠ https://j-loren-s-school.thinkific.com/collection Follow on Spotify - ⁠⁠⁠⁠⁠⁠⁠https://podcasters.spotify.com/pod/show/j-loren-norris⁠⁠⁠⁠⁠⁠⁠ ______________________________ Leading Leaders Podcast is a short but impactful leadership video, blog and podcast distributed 5 days a week by J Loren Norris to promote faith, family and freedom in the face of a global leadership drought. Leadership Training, Interviews and EntertainmentVisit ⁠⁠⁠⁠⁠⁠⁠https://www.jlorennorris.com/resources⁠⁠⁠⁠⁠⁠⁠ for more training material#leadingleaderspodcast #storypower #transforminggracetv #jlorennorris LOOK FOR LEADING LEADERS PODCAST ON THESE PLATFORMS: - OBBM Network TV - WorldTrumpetTV - Apple Podcast - Spotify - Amazon - Rumble - YouTube.com/jlorennorris DOWNLOAD THE FREE APP for: ⁠⁠⁠⁠⁠⁠⁠https://www.jotform.com/app/230026506289151⁠⁠⁠⁠⁠⁠⁠ - Live Stream videos, - Video based training material, - StoryPowerMasterclass Coaching products and services, - links to global Media Outlets carrying Tell It Like It Is content, - contact information for direct access to Loren and MORE new tools added regularly. Copyright 2025 Tell It Like It Is Inc

Benvenuti ai 4 Vangeli-letture in 1 anno 5 gg a settimanaOggi: Vi lascio la Mia paceGiovanni 14:25-3125 Vi dico queste cose adesso, mentre sono ancora con voi. 26 Ma quando il Padre manderà al mio posto il Consolatore e, dicendo Consolatore, intendo lo Spirito Santo, egli vʼinsegnerà ogni cosa e vi ricorderà tutto ciò che vi ho detto.27 Vi lascio un dono: la pace della mente e del cuore! E la pace che do io non è fragile come la pace che dà il mondo. Quindi, non siate tristi, non abbiate paura! 28 Ricordate le mie parole: ora me ne vado, ma tornerò da voi. Se davvero mi amate, dovreste essere contenti per me, perché ora posso andare dal Padre, che è più grande di me. 29 Vi ho detto queste cose prima che sʼavverino, così quando accadranno, crederete in me.30 Non mi resta molto tempo per parlare con voi, perché Satana, il malvagio principe di questo mondo, sʼavvicina. Per la verità, non ha alcun potere su di me. 31 Sarò io a fare di mia volontà ciò che il Padre vuole da me, così il mondo saprà che amo il Padre. Venite, andiamo!»La vera vite15 Poi Gesù disse: «Io sono la vera vite, e mio Padre è il contadino. 2 È lui che recide ogni ramo che è in me e non dà frutti, mentre pota i rami fertili, perché producano ancora di più. 3 Voi siete già puri grazie al Vangelo che vi ho annunciato. 4 Restate uniti a me, ed io resterò unito a voi, perché, se un tralcio non può dar frutti quando è staccato dalla vite, neppure voi potete darne se non siete uniti a me.5 Proprio così: io sono la vite, voi i tralci. Chi rimane unito a me ed io a lui, produce molti frutti. Senza di me, invece, non potete far nulla. 6 Se uno si separa da me, viene gettato via come un tralcio reciso, che si secca, poi viene raccolto e gettato nel fuoco a bruciare. 7 Ma se restate uniti a me e ubbidite ai miei comandamenti, potete chiedere tutto ciò che volete e vi sarà dato. 8 Ecco che cosa glorifica mio Padre: che voi produciate frutti in abbondanza e siate così miei discepoli.lascia un commentoSupport the show

- Premi il tasto PLAY per ascoltare la catechesi del giorno e condividi con altri se vuoi -+ Dal Vangelo secondo Luca +In quel tempo, il Signore designò altri settantadue e li inviò a due a due davanti a sé in ogni città e luogo dove stava per recarsi.Diceva loro: «La messe è abbondante, ma sono pochi gli operai! Pregate dunque il signore della messe, perché mandi operai nella sua messe! Andate: ecco, vi mando come agnelli in mezzo a lupi; non portate borsa, né sacca, né sandali e non fermatevi a salutare nessuno lungo la strada.In qualunque casa entriate, prima dite: "Pace a questa casa!". Se vi sarà un figlio della pace, la vostra pace scenderà su di lui, altrimenti ritornerà su di voi. Restate in quella casa, mangiando e bevendo di quello che hanno, perché chi lavora ha diritto alla sua ricompensa. Non passate da una casa all'altra.Quando entrerete in una città e vi accoglieranno, mangiate quello che vi sarà offerto, guarite i malati che vi si trovano, e dite loro: "È vicino a voi il regno di Dio"».Parola del Signore.

- Premi il tasto PLAY per ascoltare la catechesi del giorno e condividi con altri se vuoi -+ Dal Vangelo secondo Luca +In quel tempo, il Signore designò altri settantadue e li inviò a due a due davanti a sé in ogni città e luogo dove stava per recarsi.Diceva loro: «La messe è abbondante, ma sono pochi gli operai! Pregate dunque il signore della messe, perché mandi operai nella sua messe! Andate: ecco, vi mando come agnelli in mezzo a lupi; non portate borsa, né sacca, né sandali e non fermatevi a salutare nessuno lungo la strada.In qualunque casa entriate, prima dite: "Pace a questa casa!". Se vi sarà un figlio della pace, la vostra pace scenderà su di lui, altrimenti ritornerà su di voi. Restate in quella casa, mangiando e bevendo di quello che hanno, perché chi lavora ha diritto alla sua ricompensa. Non passate da una casa all'altra.Quando entrerete in una città e vi accoglieranno, mangiate quello che vi sarà offerto, guarite i malati che vi si trovano, e dite loro: "È vicino a voi il regno di Dio". Ma quando entrerete in una città e non vi accoglieranno, uscite sulle sue piazze e dite: "Anche la polvere della vostra città, che si è attaccata ai nostri piedi, noi la scuotiamo contro di voi; sappiate però che il regno di Dio è vicino". Io vi dico che, in quel giorno, Sòdoma sarà trattata meno duramente di quella città».Parola del Signore.

- Premi il tasto PLAY per ascoltare la catechesi del giorno e condividi con altri se vuoi -+ Dal Vangelo secondo Luca +In quel tempo, il Signore designò altri settantadue e li inviò a due a due davanti a sé in ogni città e luogo dove stava per recarsi.Diceva loro: «La messe è abbondante, ma sono pochi gli operai! Pregate dunque il signore della messe, perché mandi operai nella sua messe! Andate: ecco, vi mando come agnelli in mezzo a lupi; non portate borsa, né sacca, né sandali e non fermatevi a salutare nessuno lungo la strada.In qualunque casa entriate, prima dite: "Pace a questa casa!". Se vi sarà un figlio della pace, la vostra pace scenderà su di lui, altrimenti ritornerà su di voi. Restate in quella casa, mangiando e bevendo di quello che hanno, perché chi lavora ha diritto alla sua ricompensa. Non passate da una casa all'altra.Quando entrerete in una città e vi accoglieranno, mangiate quello che vi sarà offerto, guarite i malati che vi si trovano, e dite loro: "È vicino a voi il regno di Dio". Ma quando entrerete in una città e non vi accoglieranno, uscite sulle sue piazze e dite: "Anche la polvere della vostra città, che si è attaccata ai nostri piedi, noi la scuotiamo contro di voi; sappiate però che il regno di Dio è vicino". Io vi dico che, in quel giorno, Sòdoma sarà trattata meno duramente di quella città».Parola del Signore.

Stephan Ewan (@StephanEwan) is the co-founder of Restate, the open-source workflow-as-code engine. Restate is lightweight, simple, and provides durable execution. Before Restate, Stephan co-created Apache Flink, the open-source stream processing framework. Lessons learned from Flink have heavily influenced the development of Restate, although Stephan says they have exact opposite use cases. Contributor is looking for a community manager! If you want to know more, shoot us an email at eric@scalevp.com. Subscribe to Contributor on Substack for email notifications! In this episode we discuss: The history of Flink and the impact of the 2016 U.S. election Why tooling for real-time transactional problems has historically had room for improvement What constitutes “modern” workflow engines Can you use Restate for any use case? Moving from a large company to a small startup as an open-source developer Links: Restate Apache Flink People mentioned: Kostas Tzoumas (@kostas_tzoumas) Other episodes: Temporal with Maxim Fateev

Today, we're talking all about the recently-released Confession of Evangelical Conviction:-        What the confession is and what it says-        Why we signed it and got involved promoting it-        How the American church got to the point where a confession of very basic political theology like this is necessary-        And after that conversation, we talk the many layers of Christian nationalism involved in the debacle at Trump's recent trip to Arlington National CemeteryMentioned on the episode:-        The Confession of Evangelical Conviction, and the associated resources-        The video we produced to promote the confessionCredits-            Follow KTF Press on Facebook, Instagram, and Threads. Subscribe to get our bonus episodes and other benefits at KTFPress.com.-        Follow host Jonathan Walton on Facebook Instagram, and Threads.-        Follow host Sy Hoekstra on Mastodon.-        Our theme song is “Citizens” by Jon Guerra – listen to the whole song on Spotify.-        Our podcast art is by Robyn Burgess – follow her and see her other work on Instagram.-        Editing by Multitude Productions-        Transcripts by Joyce Ambale and Sy Hoekstra.-        Production by Sy Hoekstra and our incredible subscribersTranscriptIntroduction[An acoustic guitar softly plays six notes in a major scale, the first three ascending and the last three descending, with a keyboard pad playing the tonic in the background. Both fade out as Jonathan Walton says “This is a KTF Press podcast.”]Sy Hoekstra: When we first started doing this work and we published our anthology, we went on a couple of podcasts about it. A common thing that people asked of us at the time was, where do you think the White American church, where do you think the like 81 percent of the church, the White evangelical church that voted for Trump is going? And the first time I said it, I sort of surprised myself and I was like, look, it's being cut off the vine for not bearing good fruit and thrown in the fire. There's been a long time coming of a divorce, like a complete split between White evangelicals in America and followers of Jesus.[The song “Citizens” by Jon Guerra fades in. Lyrics: “I need to know there is justice/ That it will roll in abundance/ And that you're building a city/ Where we arrive as immigrants/ And you call us citizens/ And you welcome us as children home.” The song fades out.]Sy Hoekstra: Welcome to Shake the Dust, seeking Jesus, confronting injustice. I'm Sy Hoekstra.Jonathan Walton: And I'm Jonathan Walton.Sy Hoekstra: We have a great show for you today. We're doing something a little bit different. We are talking about a bit of a movement, a little, a confession that we have signed onto that we're a part of that we're producing some media around that you may have seen by the time this episode comes out. And it's a confession of sort of evangelical faithfulness to Jesus in a political context. And it is probably a little bit off the beaten path of kind of some of the political commentary that we normally engage in. And we wanted to talk to you about why we think it is a good and strategic thing for us to do during this season, give you some of our thinking behind how we kind of strategize politically and think about ourselves as part of a larger theological and political movement.So I think this will be a really good conversation. We're also gonna get into our Which Tab Is Still Open and talk to you about Christian nationalism and whiteness through the lens of Donald Trump doing absurd things at Arlington National Cemetery [laughs].Jonathan Walton: Yes.Sy Hoekstra: But we will get into all of that in a moment. Before we do, Jonathan Walton.Jonathan Walton: Hey, remember, if you like what you hear and read from us at KTF Press and would like for it to continue beyond the election season, I need you to do two things. Go to KTFPress.com and become a paid subscriber. Now, you could also tell other people to do that as well if you've already done that. We've got a ways to go if we're going to have enough people to sustain the work, but we think it's valuable, and I hope you do too. So go to KTFPress.com, sign up, and that gets you all of the bonus episodes of this show, access to our monthly Zoom calls with the two of us and more. So again, KTFPress.com. Become a paid subscriber.What is the Evangelical Confession of Conviction, and Why Is KTF Involved?Sy Hoekstra: All right, Jonathan, let's get started in our conversation. We've signed onto this document called The Confession of Evangelical Conviction. We've produced some media around it. First of all, what is it and what does it say?Some Basic Political Theology That We Need to Restate at This Cultural Moment with UnityJonathan Walton: [laughs] Well, I think the question of what it is, it's words [Sy laughs]. Like there's these things that we put together, it's words. And I think the reason that it's powerful is because of when and how it's said. And so these are basic confessions that every Christian should believe, but it seems like the reason that we're doing it right now and that I've signed onto is because there are seasons when the discipleship and formation of the church needs to be plain and centered. And so being able to say, “I give allegiance to Christ alone,” and then have that be reverberated across denominations, across movements of quote- unquote, Christians around the country that are usually so disparate, they usually don't communicate, they usually disagree with each other in very public ways, to say, “Hey, hey, hey.”We need people to understand who don't follow Jesus, that when Gandhi said, “I like Christ, I don't like Christians,” that's part of the problem. We are part of that problem. Where we don't articulate what we know, what we believe, what we know to be true. I think this is an articulation of that, speaking particularly to a cultural and political and social moment that needs the clarity that Jesus can bring.Sy Hoekstra: Yeah. So this is just to get into the weeds of it. It's a confession signed by I would say, the sort of extreme ends, at least to the people that we know about right now, I don't know who's gonna sign it in future, but center-right to more progressive left. And the basic confessions, like the seven statements of the confession are, “We give our allegiance to Jesus Christ alone. We will lead with love, not fear. We submit to the truth of Scripture. We believe the Gospel heals every worldly division. We are committed to the prophetic mission of the Church. We value every person as created in God's image.” And “We recognize godly leaders by their character.” So this is very basic theology [laughs] like you said. And you got a little bit at why it matters to put this out there, why we are involved. I agree with you. I think it's more about the context and it's also about who is saying it more than it is about the content.Because, and by the way, we should say we are giving you our reasons for signing this and why we think it's important. This is not… like there's a group of people that were involved in writing it, so there's lots of people involved who we don't know precisely why they signed [laughs] or precisely why the people who wrote it decided it was necessary. We're talking to you about our opinions. So to me, if you have something that says we pledge our allegiance to Christ alone, that's a rebuke of Christian nationalism to me.We judge godly leaders by their character, that's a rebuke of people who argue that Trump is a godly leader or a leader who has been appointed by God in some way or another. So those are important things to say. And it's with people across a pretty big spectrum of, as I said, the political range. Would Jonathan and I go a lot further than this if we said what we thought is important for political discipleship? Yes, we would, and you know that, because you've heard our other episodes. Or if you haven't, go listen to our other episodes [laughs]. We would go a lot further than that, yes. But we think, I think it's good to work with a broad range of people during a political campaign.Reaching a Broad Audience and Pushing the American Church to ChangeSy Hoekstra: Like I think when you're talking about discipleship at a moment when tensions are extremely high around theology and politics, it is good to do these kinds of things where you are trying to scale your efforts.Where you're trying to reach as many people as possible in the hopes that you will change some minds, both so that they will more faithfully follow Jesus, and in this specific context, so they won't vote for Donald Trump. That's one of my personal reasons for being involved in this [laughs]. And that's how you do campaigns in general. That's how campaigns operate. You try and call as many people as you can. You try and put commercials out there as widely as you can toward your targeted audience, whatever. Not in the hopes that the vast majority of the people who see it are going to suddenly be like, “Oh my goodness, I agree with everything you say,” but in the hopes that you'll reach enough of the people whose minds you can change to make a difference in their decision when it comes to November.You will reach them and you will start to be one of the people who affects their choices, is what I'm trying to say. So I don't know, that's kind of the strategy of it from my point of view. It is a similar way of thinking to me from the anthology. When we published the anthology four years ago, it was different because we were letting people say their own beliefs. And it was people from all over the spectrum kind of saying why they weren't voting for Trump in whatever way they saw fit [laughs], on whatever topic they saw fit. That was our approach. But this is the way some other people are going to do it, and we're gonna be happy to work with them in that way.Jonathan Walton: I think for me, I see the political strategy of it. I see the strategery that's happening, to use a word from SNL. My hope is that…Sy Hoekstra: From SNL 25 years ago [laughs].Jonathan Walton: Yeah. My hope… [laughs]. It was such a great sketch. “Strategery,” it was so good. “I'm the decider” [Sy laughs]. So I think one of the things that stands out to me, particularly in reviewing it more and assign it and then come on board, is, I hope that this is a Belhar Confession type moment for the United States and followers of Jesus. Particularly, because when we look at the Dutch Reformed Church, the Dutch Reformed Church was the theological backbone and framework for apartheid in South Africa. They gave the covering for those things to happen. It gave theological and moral legitimacy to a movement that was oppressive, violent, exploitative, and un-Christian at every level. Because there are Christian leaders who are willing to say, “You know what? This is really good. This is actually right. This is good and just, and God intended this.” And we have the exact same type of nonsense happening in the United States.There are quote- unquote, prophets and apostles and preachers and teachers and publishing houses and Amazon independent book publishers rolling out materials that say, “America first.” America is the kingdom of God. America is the kingdom of heaven. America is this baptized land on the earth, as opposed to being a land that is rooted in land theft, genocide, violence, patriarchy, greed and exploitation. Which it is that. It's actually not the kingdom of God at all. And so I hope that this creates a groundswell that goes beyond November 5th and beyond January 20th. And could this be a pivot point of orientation for people who followed Jesus to say, “You know what? Actually Jesus didn't say any of that.” If all of these people, right, left, middle, above, otherwise are saying this, maybe I should consider. “Oh, Randall Balmer said that, and Mercy Aiken” [Sy laughs]? “Shane was there too? Alright. Shane is on the same page as Curtis Chang and Sandra Van Opstal? Alright, let me jump in and get on this.” That's what I hope happens, is that it becomes impossible to avoid the question of allegiance to Jesus, or allegiance to the United States. Just like in South Africa the question was, are you pledging allegiance to apartheid or are you gonna follow Jesus?Sy Hoekstra: I totally agree with that. And I would say that it is 100 percent in line with the sort of premise of this podcast, which is helping people shake the dust and walk away [laughs] from the places where the word of God is not accepted as Jesus put it. And you let your peace return to you and you move along on your way.Jonathan Walton: Yes.How Did We Get to the Point Where This Confession Is Necessary?Sy Hoekstra: So let's actually talk about that thing that you were just saying. The thing where all these people from these different walks of life are coming together to make this specific statement at this time. How did we get here, aside from the obvious thing that Donald Trump is very good at uniting people who oppose him [laughter]. How did we get to this point in the church in America?Jonathan Walton: I think we need to narrow the scope a little bit.Sy Hoekstra: Okay.Jonathan Walton: Of how we got to this point, I think I would start at Acts 2 [laughter]. But, and then the church and then the alliance with the empire to escape persecution. Constantinople like Nicea, I mean…Sy Hoekstra: Let's focus on America.Jonathan Walton: Yeah, let's focus on the United States.Sy Hoekstra: [laughs] Zoom in a little bit.The Moral Majority Took Us Very Far down a Path Away from JesusJonathan Walton: I think that one of the pivot points in the United States is 2008 in the ascendance of Barack Obama. With Barack Obama, you have what was roiling and starting with Al Gore, but like can Christians vote for Democrats and still be Christians? Because with the ascendance of the moral majority, with what Randall Balmer talks about this coalescing around abortion as a position, and then the policies laid out by Jerry Falwell. And there was a conference in 1979 in Houston. Lots of organizations came out of that gathering. And so when those types of things occur, I think we are living in the wake of that wave, but that wave wasn't really challenged until 2008 when many, many, many, many people said, “Oh, I wanna vote for Barack Obama.”And so with the ascendance of Obama, then the question particularly among the Black community from evangelical Christians is like, can you be a Christian and vote for Obama? And that was talked about extensively in Tamice's book, Faith Unleavened, which is amazing. And that scene that she describes of the dissonance between the White evangelical church that she was sitting in, and the conversation she was having with her grandma on the phone, who she called Momma.Sy Hoekstra: Where her family was having a party because Obama had been elected and her White church was having a mournful prayer service.Jonathan Walton: Yeah. I think a lament session basically, for the United States being now overtaken by a demonic force. And so I think if we start there and move forward, like if this was a ray coming from a point, then the line actually starts to diverge from there, from the center point. And now we are actually so far apart that it's very, very difficult to justify what's happening. So if we're at our end points right now, we have followers of Jesus legitimizing sexual violence by saying Trump is fine. You have followers of Jesus legitimizing fraud, saying that that's fine. You have followers of Jesus legitimizing insurrection, saying that's fine. We are way, way down the road and very far apart from these basic confessions.And so I think people that are co-opted and indoctrinated by Fox News and the conservative White evangelical and conservative Catholic and conservative… because there's a smattering of Christian movements that have so aligned themselves with political power that it is very apparent even to non-Christians, that this is not Christ-like. And so I think for us, similar to the church in South Africa, to say, “Hey, we need to just make very plain every person is made in the image of God, and you shouldn't enslave, violate and steal from people.”If we could articulate that and do that, and have a movement around that, then I think that is how we got here, is that basic tenets of following Jesus have stayed the same, but forces, institutional, the powers, the principalities, and also people who chose to align themselves with that have taken the ball and run so far down the road that even people who don't follow Jesus and folks who just have basic biblical engagement are seeing that this is just not the way. And so I think followers of Jesus across the spectrum are starting to say, “You know what? This is a moment that we can actually speak into.”The White Evangelical ChurchA Divorce between White Evangelicals and Followers of JesusSy Hoekstra: Yeah, I agree with all that. I think, I mean, look, when we first started doing this work and we published our anthology, we went on a couple of podcasts about it. A common thing that people asked of us at the time was, where do you think the American church, where do you think the like 81 percent of the church, the White evangelical church that voted for Trump is going?” And the first time I said it, I sort of surprised myself, but I was like, “Look, it's being cut off the vine for not bearing good fruit and thrown in the fire.” That's it. There's been a long time coming of a divorce, like a complete split, I think, between White evangelicals in America and followers of Jesus.Jonathan Walton: Right.Sy Hoekstra: White evangelicals have had a whole long history of being involved in, as you said, in the exact same way that the Dutch Reformed Church was involved in apartheid, just being involved in everything. Every [laughs] terrible thing America's ever done, we've been there cheering it on and supporting it in all kinds of ways. And I think a lot of what Trump in particular, and it's sometimes a little bit hard to put my finger on why it was him, but Trump in particular, I think highlighted to a lot of Christians who viewed themselves as kind of like just nice, gentle, center right Christians who were a part of a larger movement where maybe there were some people who were a little bit off the deep end, but overall, these institutions and these people are trying to accomplish good things in the world and follow Jesus faithfully, realized that that wasn't the case.I think there are a lot of people who realized that they actually had opinions about what it meant to follow Jesus that were dramatically different than the average person in their institutions, or the average evangelical Republican.Policy Debates for White Evangelicals Have Been a Cover for Power HungerSy Hoekstra: Peter Wehner, I think would be one of these people, who writes for the New York Times. He was a George W. Bush speech writer. He recently wrote an article saying, “Look, Donald Trump has explicitly said that if you took one of these super restrictive state abortion bans and you passed it in Congress and you put it on my desk, I would veto it. I would not pass a national abortion ban.”Jonathan Walton: Right.Sy Hoekstra: Which for the pro-life movement, that's the end goal. That would be [laughs], that would be the thing they've been fighting for for decades [Jonathan laughs]. And he has said, “I will not sign this.” And do you hear anything about that from Franklin Graham [laughs]?Jonathan Walton: So Al Mohler was on the Run-Up of the New York Times this week, when you listen to this probably like two weeks ago, talking about how, “Hey, Donald Trump just said he's not gonna sign a national abortion ban. What's your position on that?” And his position hasn't changed, because again, it is framed as you all are the radical people, not us. We are the victims, not you. There's a constant revision of reality that they are gonna continue to turn out and communicate that is rooted in fear and a lust for power and control and dominance. And that is toxic as all get-out, and obviously un-Christian.Sy Hoekstra: Yeah, that was the end of my point, was that a thing that people have been arguing for a long time, which is that, this focus on abortion, this focus on prayer in school, or this focus on whatever the evangelical issue of the day is, has in fact been about power from the perspective of the leaders.Jonathan Walton: Right.Sy Hoekstra: Maybe not the rank -in-file people like marching and the March for Life or whatever.Jonathan Walton: Exactly.Sy Hoekstra: But the leaders are after power, and they always have been. That's what, if you go back a couple years to our episode with Mako Nagasawa, the first episode of season two where we talked about abortion. That's what his whole book is about, is the history of abortion policy and how it's almost never been about abortion. It's almost always been about something else like anti-immigrant sentiment or professionalizing the medical profession or whatever. It's always been about some other issue of people trying to establish themselves and gain power over somebody else. That's what I think a lot of people are realizing, and so a lot of people who are, I think more to the right in the group of people who have signed this document that we have are on that journey, like are in the middle of it.Or not in the middle of it, but they've been going on it for a few years and they've been rejected by who they thought were their people for saying things like, “Hey, should we maybe adhere a little more closely to the teachings of Jesus?” [laughs] And now they're saying, okay, they've gotten to a point where they're like, “I need to draw a line in the sand. I need to make something clear here.” And that I think is different. That is genuinely different than eight years ago when everybody was, a lot of people in the middle were just kind of waffling.Jonathan Walton: Yeah. Yeah, right.Sy Hoekstra: Were not really sure what to do yet. And they still viewed the people on the far right who were all in for Trump as possibly a minority on their side, or possibly just something like a phase people were going through. Something that would flare up and then die, and it just didn't turn out that way. I think that's kind of how I view a lot of how we got to the place that we are now.Jonathan Walton: Yeah.Sy Hoekstra: Again, zoomed in on America and not looking at the entirety of church history, which is where you wanted to go [laughter].Jonathan Walton: Yeah. And I mean, and I'll name some of the people that are key to that. So, Kristin Kobes Du Mez, like her book Jesus and John Wayne, Jemar Tisby's book, The Color of Compromise. And we could also throw in some Christianity adjacent, but loved by them books as well. So like all of the quote- unquote, anti-racist books, where people who are trying to leave the race-based, class-based, gender-based environmental hierarchy that White evangelicalism enforces, like I wrote about that in Twelve Lies as an explicit book. But you could say that Ibram X. Kendi's book is trying to get away from that. That White Fragility is trying to get away from that. That all of these books pushing back against [laughs], what now is called like Trad Wife and all these different things, it's trying to push back against these things. They're trying to call people to another reality because the one that some people have found themselves in is deeply unhelpful and not Christian.Sy Hoekstra: Yeah. I feel like that's been like you're refrain of this podcast. “And also, not Christian” [laughs].Jonathan Walton: Not Christian. Right.Sy Hoekstra: And not Jesus.Jonathan Walton: Right.Sy Hoekstra: Do we have any other thoughts on this subject, or do we want to jump into our segment?Jonathan Walton: I just think people should go sign it.Sy Hoekstra: Oh, yeah.Jonathan Walton: And there's a fun bible study there that [laughs] we talked about two weeks ago on the podcast and spread the word about it. I think it's gonna be a good thing.Sy Hoekstra: Yeah, the link to the website, the people who organized it, Jonathan said, “Hey, you can put the Bible study that we talked about in our last episode up, if you want a place for people to go to scripture on these subjects.” And they did.Jonathan Walton: Yeah.Sy Hoekstra: So that's cool. We will have the link to the confession in the show notes, as well as the link to the video that we created, which has a bunch of the signers of the confession reading parts of it, which we would love it if you would all share as widely as possible on your social media, and share the confession as well. We hope that this, as I said, changes somebody's hearts and minds, has some good effect on some people both in their discipleship and in their politics, which is what we're all about.Jonathan Walton: Yeah. Amen. There's actually a worship album that came out too. So along with Phil Vischer's cartoons for kids that can be shown in churches, there's a Return to Love album by a bunch of folks that you all may know like Will Matthews, Crystal Lewis, Ryan Edgar. These are folks that have led worship in great places that the evangelical world has followed for a long time. And so having worship leaders willing to call us out as well is pretty great. Along with Phil Vischer, because these videos will definitely be great for kids.Sy Hoekstra: Is that worship album already out?Jonathan Walton: Yeah, it's out right now [laughs]. You could click on it.Sy Hoekstra: I don't know how they did that that fast. That's incredible [laughs].Jonathan Walton: Hey man, listen. There's a thing called the Holy Spirit.Sy Hoekstra: [laughs].Jonathan Walton: And I think we all know that when Jesus moves, Jesus can do some things.Which Tab Is Still Open?: Trump at ArlingtonJonathan Walton: And so let's get into our segment, Which Tab Is Still Open?, where we dive a little deeper into one of our recommendations from the newsletter. And remember, you can get our newsletter for free by signing up for the mailing list at KTFPress.com. You'll get recommendations on articles, podcasts, and other media from both of us on things that will help you in your political education and discipleship. Plus, you'll get reflections to keep you grounded and hopeful as we engage in this challenging work together. News about KTF and what's going on, and a lot more. So go get that free subscription and a paid one too. Alright. So this is your recommendation, so let's jump into it.Sy Hoekstra: This actually has a lot to do with what we were just talking about.Jonathan Walton: Yes, it does.Sy Hoekstra: This is all about Christian Nationalism [laughter]. And Trump kind of stepping in it when it comes to dealing with his Christian Nationalist followers. So here's the story, and the article that I recommended in the newsletter was actually, it both gave the details of the story, but it was actually for me, an example of kind of the thing that I was critiquing [laughs]. It was an Atlantic article, and basically the facts of what happened are as follows. Trump went to Arlington National Cemetery, which if you don't know, is I just learned the second, not actually the largest, the second largest national cemetery in the country.Jonathan Walton: Oh. Huh.Sy Hoekstra: The largest one's on Long Island, Jonathan, I had no idea.Jonathan Walton: What!Sy Hoekstra: [laughs] Yeah.Jonathan Walton: [laughs] I did not know that.Sy Hoekstra: So the people who are buried in Arlington are soldiers who served in active duty. Some of them died, some of them were retired and passed away later. And then like very high ranking government officials, like Supreme Court justices or presidents or whatever. So Trump went and visited a specific spot that had I think 13 soldiers who died during the evacuation of Afghanistan when there was a suicide bomb attack from the Taliban.Jonathan Walton: Right.Sy Hoekstra: And he did this basically to highlight Biden administration screw ups. You didn't handle this evacuation well. And so because Harris is part of the administration, he's criticizing his opponent. And he went and took some pictures, which is fine, but he then was like specifically taking pictures in this area and like narrating a video talking about Biden screw ups and everything. And an employee of the cemetery pointed out correctly that campaign activities are illegal under federal law [laughs] at Arlington National Cemetery. And they kept going anyways. And they got in a little bit of an argument with her, and then later to the press said that she is mentally ill and was having a mental health crisis in that moment, and that she needed to be fired.And, fortunately the cemeteries said, “No, that's all a lie, and she was correctly telling you that you shouldn't have been doing what you were doing and et cetera.”Jonathan Walton: Right.Sy Hoekstra: But there were a number of people, and I don't know if this is a majority or anything like that, but there were actually some Trump supporters who viewed this as a violation, like something that Trump really shouldn't have done. He was being disrespectful to the dead, the troops who were there, by doing partisan stuff at the National cemetery. It was not necessarily about the things that he was saying, but just by conducting yourself in a way that you're not supposed to conduct yourself at a national cemetery.Sy's Experience with Arlington and it's Strong Christian NationalismSo here's my in for this. I have a very long history of military [laughs] service in my family. Somebody in my family went on Ancestry.com one time, and I have a direct ancestor who was a drummer boy in the Continental Army with George Washington [laughs].Jonathan Walton: Oh, wow.Sy Hoekstra: And somebody who enlisted in the Union Army during the Civil War. And my great-grandfather was in World War II in Korea, grandfather was in Vietnam. And my grandfather who was in Vietnam, he died when I was about 10. My grandmother remarried a very highly decorated army colonel also from Vietnam, who he passed away and we had a funeral for him at Arlington. And Arlington does like 20, 30 funerals a day. So if you're a rank-in-file soldier, it's like a very, it's an in and out thing [laughs]. But because of either his rank or his awards or both [laughs], it was an event, Jonathan. It was like, we had the bigger, more beautiful chapel, and then we had a procession, because I can't see, I can't tell you how many it was, but at the very least, dozens of soldiers with a commanding officer taking his casket from the church to the burial site, there was a 21-gun salute. There was the presentation of the flag with the shell cases from the 21-gun salute to my grandmother. It was a big thing.Jonathan Walton: Yeah.Sy Hoekstra: And if you've been to Arlington, you know that one of the key messages there is that the people who served America and the army served the kingdom of God, served Jesus. That is what they did. They served, and they may have died serving heaven [laughs] effectively. And so what that means is this is one of the holiest sites for Christian nationalism. This is one of the places where you go to be reassured with some of the highest level, like some of the world's greatest pomp and circumstance. The world's most convincing showing of pageantry and religious activity that the United States Army and the people who died serving it are also serving God, which is, you can't get more Christian nationalist than that.Jonathan Walton: Yeah.Sy Hoekstra: Which is also why we have talked about Christian nationalism, actually far more common than people think it is [laughs]. It is absolutely normal in how we talk about the military. So what I think happened here with Trump is that because what I believe about Trump is that he's a conman to the core. He is pure... he's like self-interest incarnate [laughs]. He is out to promote Donald Trump and nothing more, and nobody more than that.Jonathan Walton: Right.Sy Hoekstra: I think he forgot that his self-interest can actually diverge from Christian nationalism [laughs]. I think that he forgot that he can step on his people's toes in a way that he doesn't want to. And he's basically going to look out for where those things diverge in future in order to not have this happen again. Because he's just there doing what he does, which is promoting himself anytime, anywhere at all costs. And he forgot that one of the things that he harnesses, which is Christian nationalism, is not actually something that he believes in, and so he can misfire [laughs]. The irony to me is that I want to gain enough power to do anything and not be held accountable for it to better myself in my own position, is a pretty good summary of how kind of the operating principle of the US military in our foreign policy has been for so long.So it's actually, it's like [laughs], it's two entities, a former president and the US military kind of clashing in their basically excuse making for their own unaccountability and their own sin. Which is how I view the Christian nationalism of a place like Arlington. What I just said Jonathan, is [laughs] blasphemy to a [laughs] lot of the people that I probably, to some people that I know personally. So I will just acknowledge that. But that is what I believe, and I think is true to the Bible. So hopefully you can at least give me that credit [Jonathan laughs]. Jonathan, boy, did I just talk for a long time. I'm sorry. I actually had in the outline that I wanted to ask you first what your thoughts were before I went on my rant, and I just couldn't help myself. So, [laughs].Jonathan Walton: Well, Sy, I mean…Sy Hoekstra: Jonathan, what are your thoughts?Jonathan Walton: I think one, I just appreciated the explanation of the closeness, why it's still open for you. Because I think when I was writing Twelve Lies, I wrote about the military, and I wanted to say, “Oh, they're only going to these types of communities to get people.” That would've been my hypothesis or was my hypothesis, but the research proved different.Sy Hoekstra: And when you say that, you specifically mean exploiting like poor Black and Brown neighborhoods?Jonathan Walton: Yes.Sy Hoekstra: You're saying like, “We'll get you into college, we'll give you benefits, et cetera, if you come fight and die for us.”Jonathan Walton: Exactly. And so…Sy Hoekstra: Potentially die for us.Jonathan Walton: Right, there's this exchange that's gonna happen for your body. Whether alive or dead, there will be benefits and resources for you or your loved ones. And so I went in with that lens, but what my research showed me was that the majority of people who serve in the military are family. Their parents were in it, their grandparents were in it, their cousin was in it. It's actually like only about two percent of the United States population is affiliated with the military. We're recruiting from the same groups of people. And this would also be true for law enforcement. People who were in it essentially raise their children and bless and send them into it as well as most often. It's not actually about income.The income, if I remember correctly, was between 50 to 70 thousand dollars a year in a household, which in a rural area is at the time, 10 years ago, felt like a living wage. And so that reality was also something that's interesting for me. So when Trump came out against Mark Milley, when Mark Milley challenged him to say, “Hey, you will not use me, quote- unquote, the military, as a prop in your racism, standing in front of St. John's church holding that Bible up,” which was literally the distorted cover of our book, our anthology, because these things were happening. When he insulted John McCain, that was a moment where the military and I think those who are beholden to Christian nationalism tried to speak up. Tried to say, “Hey, we won't do this.” But then the ball continued down the road.I don't know what the fallout of the Arlington stuff will be, but I do know based on Up First the NPR podcast this morning in the morning that we're recording September the seventh, they said the military and the employees actually let this go. But the reason they brought it back up was because Trump got on Truth Social , used platform and stature to say, “This did not happen. There was no altercation. This person had a mental health episode.” And when you go into that, that's where I think the, “We will not be disrespected” thing kind of came up. Like what do you mean? No, we're gonna talk about this and we're gonna name that. You will not desecrate this holy site. Holy in holy site of Christian nationalism, as you were saying.So I hope that there are more people that are offended, because I think that if we allow ourselves to be offended, to be bothered, to be uncomfortable, then maybe there will be some movement. Because I think you're absolutely right. He is, you said self-interest incarnate. I think that is a great quote [laughs].Trump Cheapened the Spiritual Cost People Pay to Be in the MilitaryJonathan Walton: What's painful to me, so I too have, my father was in Vietnam. My brother was in the Navy, my uncle was in the Army. My other uncles were in Vietnam. And Brodnax, the town where I'm from, has many gravestones from Vietnam and Korea. And so what is fascinating to me is the level of belief that you have to have to commit acts of atrocity or commit acts of violence. Like Shane Claiborne would say, we were not made to kill people, you have to be taught to do that.And I am in no way condemning a soldier or a person who's in military service, who's listening. That's not what I'm saying. I'm observing, it costs us something to do these things. And I think the thing that Trump did was cheapen the cost that many, many, many thousands of people have paid for something that they thought was a collective interest blessed by God when Trump said, “No, you are a pawn in my game. And I will use you for my benefit.” Now you again, you will have people that say that's what's happening anyway. Trump is just doing in like what everybody else does behind closed doors. But I think that tension that he articulates or brings up for us, I hope it's allowed to rise to the surface, and then we can have a conversation about the cost.Like the silent war in the military right now is that even soldiers who have not seen active duty are committing suicide. I hope it brings to the surface the, like my dad, Agent Orange ruined some of his life. They're still figuring out what the effects of that were. You have people who are saying they support troops in one hand, but then voting against resources and benefits for them in the other hand, when the legislation comes up. Lauren Boebert did that yesterday. I hope that the perceived belovedness of our veterans and military versus the reality of how they're exploited and taken advantage of and dismissed and cast aside, we would actually acknowledge that and then do real work to ensure that they don't end up on the street.They don't end up stuck on painkillers. They do get the medical resources they need. They do get the mental health support that they need. Their families do get the resources that they need on and off-base and not just a discount at the PX. If that could be the conversation because of this, then I'd be very glad.Sy Hoekstra: Yeah. Just one more thing you said there. You said lots of people use the military as pawns and it's true. Or like props for their campaigns. It is just another one of those things about Trump where he will just do what everybody else did, but he'll turn it up to 11 [laughs].Jonathan Walton: Yeah, no, yeah. It's true.Sy Hoekstra: Everybody else, every politician, if they have a military background, if their family does, if they can visit a military site or whatever, they do it all the time. And even if their love for the military or for America is real, it is also true that they use them for their campaigns [laughs]. Use them to prop up. That has been… since we elected George Washington, the general of the Continental Army, has been true [laughter]. Right?Jonathan Walton: Right.Sy Hoekstra: So Trump is just the one who says, “Whatever your rules of decorum are, I'm going to break them.” And in most cases, that is actually his appeal. “Yes. I break rules of decorum and there's no consequences. And that's because these elitist can't tell me what to do and we need to take back power.Jonathan Walton: Oh Lord have mercy, Jesus [laughs].Sy Hoekstra: You need someone like me who can just break through all this nonsense.” You know what I mean?Jonathan Walton: Right. Yeah.Sy Hoekstra: That's usually his appeal. And in this case, it just happened to be that he crossed the wrong line for some people. I'm sure there's a lot of people who probably don't care [laughs].Jonathan Walton: Right. It may not wrangle a lot of people, but I hope it wrangles the right people.Sy Hoekstra: Yeah.Jonathan Walton: And him stretching out this poop that he stepped on and not wiping it off his foot and continue his campaign, I hope that roils people. He is a disrespectful person.Sy Hoekstra: Yeah.Jonathan Walton: And for Christians, literally James chapter four, it's that God opposes the proud. We are called to be humble people, and so I pray for Trump. I pray for his family. Not that he would win an election and all those things, but literally that they would come to know Jesus. Literally that they would know the freedom in him. Literally, that they would be able to experience the freedom that money cannot purchase and privilege cannot provide for you. And so I say all these things in hopes that everyone who is watching what happens is disquieted because we should not be comfortable with what's happening. Especially as followers of Jesus [laughs].Sy Hoekstra: Yeah. Amen to that Jonathan. Amen.Jonathan Walton: Yeah.Sy Hoekstra: I think we'll wrap it up there. Just as a reminder, as we finish, please again, go to KTFPress.com, get that newsletter and sign up as a paid subscriber to support everything that we do. We're centering and elevating marginalized voices. We're helping people seek Jesus in their discipleship and in their politics. We really do need some more support than we have right now if we're gonna make this sustainable kind of past this election season. So please do come and sign up as a paid subscriber at KTFPress.com. Our theme song is “Citizens” by Jon Guerra. Our podcast Art is by Robyn Burgess, transcripts by Joyce Ambale, editing by Multitude Productions. I am the producer along with our lovely paid subscribers. Thank you so much for joining us, and we will see you in two weeks.[The song “Citizens” by Jon Guerra fades in. Lyrics: “I need to know there is justice/ That it will roll in abundance/ And that you're building a city/ Where we arrive as immigrants/ And you call us citizens/ And you welcome us as children home.” The song fades out.]Jonathan Walton: Give me one second. One moment. I'm gonna get the name right so that you don't have to go edit this later [Sy laughs]. … So yes, we… Robert Mohler. The—Richard Mohler. Al Mohler. That's his name [Sy laughs]. Al Mohler [laughs]. It says R dot Albert Mohler. This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit www.ktfpress.com/subscribe

Human-centered leadership is the antidote to low employee morale, high turnover rates, weak team dynamics, and negative organizational culture. On this episode of The Forward Thinking Podcast, FCCS VP of Marketing and Communications Stephanie Barton sits down with Karin Hurt, Founder and CEO of Let's Grow Leaders and instructor in the Leading Leaders, FCCS Leadership Journey program for a conversation about the four dimensions of collaboration that create connection and clarity in human-centered leadership. She highlights what it means to be on a dream team, strategies for leading a team that you didn't hand-pick, and the importance of crafting daily habits that keep a team moving forward together.   Episode Insights Include:   Dream (and nightmare) leadership teams The best team Karin has ever been a part of was the Strategic Partnership Channel. This team was filled with human-centered leaders and it showed in the care that everyone showed for each other. Teams like this are filled with people who are aligned by a unifying mission, a shared goal, and trust for each other. The worst team Karin was part of was filled with conflicts that were caused by systems problems. Teams that are pitted against each other will continue to struggle to accomplish anything.   The four dimensions of collaboration Connection- do we know one another as human beings? Connection needs to be in place before difficult conversations have to happen. Use connecting words when communicating with others. Clarity- do we have a shared understanding of success? Is your team aligned on the habits that lead to success? Curiosity- are we genuinely interested in one another and in different perspectives? Commitment- do conversations culminate in accountability? Accountability is everyone's job, not just the boss.   The importance of daily habits Detailed, informative directives are far more valuable than generic feedback. Daily habits can help improve connections and performance. Specific, measurable habits will lead to greater results. Daily habits can help align a team and move everyone in the same direction. Check for understanding by assigning a number of hours to a task before starting it. Communicate an assignment five times in five different ways. Restate expectations of the next steps before the meeting is over.   Successful team-building activities Start by creating a unified team vision. Visualize or draw how you see the team today and what the future could look like. Determine what needs to happen to get from where you are to where you need to be.   Advice for leaders who didn't pick their team A team can only be built one person at a time. Start with curiosity and connection - let your team see who you are as a human being with thoughts and feelings. Create clarity about where your team is headed in the future. Empower your team to hold each other accountable, share best practices, and even meet without you.   This podcast is powered by FCCS. Resources   Connect with Karin Hurt — Karin Hurt Get in touch info@fccsconsulting.com    

In a market often driven by quick gains, it's time to take a step back and focus on what truly matters—integrity and transparency. Real success isn't just about flipping properties; it's about building trust, making informed decisions, and creating lasting value. Let's redefine the way we invest, with honesty at the forefront of every deal. ---Secure your spot at the #1 conference for real estate, entrepreneurship, and social media here - https://www.wealthcon.org/Feeling lost as an entrepreneur or real estate investor? Get access to our community, coaching, courses, and events at Wealthy University https://wealthyuniversity.com/If you want to level up, text me at 725-444-5244! ---About Ryan Pineda: Ryan Pineda has been in the real estate industry since 2010 and has invested in over $100,000,000 of real estate. He has completed over 700 flips and wholesales, and he owns over 650 rental units. As an entrepreneur, he has founded seven different businesses that have generated 7-8 figures of revenue. Ryan has amassed over 2 million followers on social media and has generated over 1 billion views online. Starting as a minor league baseball player making less than $2,000 a month, Ryan is now worth over $100 million. He shares his experiences in building wealth and believes that anyone can change their life with real estate investing.

In this podcast, Dr. Chris Solie, an emergency physician, along with Jason Hicks, Fred DeMeuse, Greta Sowels (physician assistants), working for Emergency Medicine Physicians and Consultants (EMPAC) who review journals and papers around emergency medicine. *Disclosure note: None of the speakers or planners for this education activity have relevant financial relationships to disclose with any inelgible company - who's primary business is producing marketing, selling, re-selling, or distributin healthcare products used by or on patients. Enjoy the podcast. Objectives:Upon completion of this podcast, participants should be able to: Identify emergency medicine journal articles that may be potentially practice changing. Differentiate between using a HEAR score versus a HEART score when assessing patients coming into the ED with chest pain. Restate whether vaccination during pregnancy could reduce the burden of respiratory syncytial virus (RSV) - associated lower respiratory tract illness in newborns and infants. Discuss the rate of wound infection from suturing with sterile gloves, dressings, drapes, etc. versus non-sterile gloves, dressings in emergency department. Discuss the risk-benefit of using tranexamic acid (TXA) in the treatment of gastrointestional bleeds. Identify interventions designed to reduce fatigue among emergency department physicians. Determine whether a direct oral penicillin challenge is noninferior to the standard of care of penicillin skin testing followed by an oral challenge in patients with a low-risk pencillin allergy. This activity has been planned and implemented in accordance with the accreditation criteria, standards and policies of the Minnesota Medical Association (MMA). Ridgeview is accredited by the Minnesota Medical Association (MMA) to provide continuing medical education for physicians.  CME credit is only offered to Ridgeview Providers & Allied Health staff for this podcast activity. After listening to the podcast, complete and submit the online evaluation form. Upon successful completion of the evaluation, you will be e-mailed a certificate of completion within approximately 2 weeks. You may contact the accredited provider with questions regarding this program at Education@ridgeviewmedical.org. Click the link below, to complete the activity's evaluation. CME Evaluation (**If you are listening to the podcasts through iTunes on your laptop or desktop, it is not possible to link directly with the CME Evaluation for unclear reasons. We are trying to remedy this. You can, however, link to the survey through the Podcasts app on your Apple and other smart devices, as well as through Spotify, Stitcher and other podcast directory apps and on your computer browser at these websites. We apologize for the inconvenience.)  DISCLOSURE ANNOUNCEMENT  The information provided through this and all Ridgeview podcasts as well as any and all accompanying files, images, videos and documents is/are for CME/CE and other institutional learning and communication purposes only and is/are not meant to substitute for the independent medical judgment of a physician, healthcare provider or other healthcare personnel relative to diagnostic and treatment options of a specific patient's medical condition; and are property/rights of Ridgeview.  Any re-reproduction of any of the materials presented would be infringement of copyright laws.  It is Ridgeview's intent that any potential conflict should be identified openly so that the listeners may form their own judgments about the presentation with the full disclosure of the facts. It is not assumed any potential conflicts will have an adverse impact on these presentations. It remains for the audience to determine whether the speaker's outside interest may reflect a possible bias, either the exposition or the conclusions presented. None of Ridgeview's CME planning committee members have relevant financial relationship(s) to disclose with ineligible companies whose primary business is producing, marketing, selling, re-selling, or distributing healthcare products used by or on patients.  All of the relevant financial relationships for the individuals listed above have been mitigated. RESOURCES Article 1: O'Rielly, C.M., Andruchow, J.E., McRae, A.D. et al. External validation of a low HEAR score to identify emergency department chest pain patients at very low risk of major adverse cardiac events without troponin testing. Can J Emerg Med 24, 68–74 (2022). https://doi.org/10.1007/s43678-021-00159-y Article 2: Kampmann B, Madhi SA, Munjal I, et al. Bivalent Prefusion F Vaccine in Pregnancy to Prevent RSV Illness in Infants. N Engl J Med. 2023;388(16):1451-1464. doi:10.1056/NEJMoa2216480 Article 3: Zwaans JJM, Raven W, Rosendaal AV, et al. Non-sterile gloves and dressing versus sterile gloves, dressings and drapes for suturing of traumatic wounds in the emergency department: a non-inferiority multicentre randomised controlled trial. Emerg Med J. 2022;39(9):650-654. doi:10.1136/emermed-2021-211540 Article 4: HALT-IT Trial Collaborators. Effects of a high-dose 24-h infusion of tranexamic acid on death and thromboembolic events in patients with acute gastrointestinal bleeding (HALT-IT): an international randomised, double-blind, placebo-controlled trial. Lancet. 2020;395(10241):1927-1936. doi:10.1016/S0140-6736(20)30848-5 Article 5: Fowler LA, Hirsh EL, Klinefelter Z, Sulzbach M, Britt TW. Objective assessment of sleep and fatigue risk in emergency medicine physicians. Acad Emerg Med. 2023;30(3):166-171. doi:10.1111/acem.14606 Article 6: Copaescu AM, Vogrin S, James F, et al. Efficacy of a Clinical Decision Rule to Enable Direct Oral Challenge in Patients With Low-Risk Penicillin Allergy: The PALACE Randomized Clinical Trial. JAMA Intern Med. 2023;183(9):944-952. doi:10.1001/jamainternmed.2023.2986   Thank-you for listening to the podcast. Thanks to Dr. Chris Solie, Jason Hicks, Fred DeMeuse and Greta Sowels for their expert knowledge and contribution to this podcast.

About the Guests: Noah Kagan is an accomplished entrepreneur, the founder, and CEO of AppSumo, a company aimed at enabling entrepreneurs by providing them with tools and resources to grow their businesses. He's a recognized leader in the field, renowned for his innovative approach to business and entrepreneurship. Noah is the author of the book "Million Dollar Weekend," where he shares insights on launching a successful business promptly. Taylor Wallace is an employee at AppSumo who brings a unique perspective to the entrepreneurial landscape. Rather than helming his own venture, he thrives within the structure of an established company, contributing his expertise and enjoying the security and dynamics that come with being part of a team. Episode Summary: In this "Restate Debate", we unpack the intricate dynamics between entrepreneurship and employment with guests Noah Kagan and Taylor Wallace. The dialogue delves into the compelling narrative of Noah's book "Million Dollar Weekend," an exploration of the initial steps to creating a thriving business and the exhilarating potential of a founding weekend. However, the conversation takes a fascinating twist, questioning not only how to launch a successful business but also the less-often considered – should you? In a candid and introspective exchange, Noah and Taylor navigate the dichotomies of their experiences within the workforce. They engage in a dialogue format that emphasizes empathy and understanding by having participants articulate each other's viewpoints before defending their own. With Noah advocating for the nuanced benefits of entrepreneurship and Taylor reflecting on the stability and growth opportunities found in employment, the discussion illuminates a spectrum of work and business ideologies. Key Takeaways: Starting a business carries unique creative gratification in manifesting an idea into existence and impacting lives. The stability, structure, and outlined expectations in an employee role can be as satisfying as the control and flexibility entrepreneurship affords. Personal seasons of life, risk tolerance, and lifestyle preferences play critical roles in one's choice between entrepreneurship and employment. Restate debates can foster deeper understanding and empathy by challenging individuals to fully comprehend and articulate opposing viewpoints. Entrepreneurship and employment are not binary options but rather points on a continuum of professional fulfillment and personal life choices. Notable Quotes: "The hardest part about starting a business is doing the work and starting." - Taylor "I like the structure of being an employee... They only owe me mentally till 05:00 p.m." - Noah "If you offered me Noah's salary, I would say yes. But if you offered me Noah's job, I would say no, thank you." - Taylor Resources: "Million Dollar Weekend" book by Noah Kagan AppSumo.com - Noah Kagan's platform for entrepreneurs Join my weekly newsletter. Learn more about my books and courses. Join The Essentialism Academy. Follow me on LinkedIn, Instagram, X, Facebook, and YouTube. Learn more about your ad choices. Visit megaphone.fm/adchoices

This episode is part two of three sessions with parents Molly and Alastair. Last week Leslie focused on the sibling dynamics between their daughters, 8-year-old Elizabeth and 4-year-old Katherine. This week we focus on a different kind of dynamic: the power struggle. In the fight for power between child and parent, Leslie offers an alternative: stop struggling for power and put an end to the power struggles. In this episode Leslie discusses identifying the problem behind the struggle, what the problem really is, whose problem is it, and learning to ask: can we try that again?Time Stamps:5:02 Whose problem is it? Is it the child's problem or is it the parent's problem7:07 Definition of power struggle8:15 What happens if the parent give in9:52 Example of sibling rivalry and how parents reinforce the escalation Strategies to deal with power struggles12:02 Say that you need a moment (to get into wise mind)12:39 Engage your child in the problem solving process 12:54 Do a pros and cons13:34 Notice and name what's going on14:12 Use the phrase “try it again”15:20 How to give the problem back to your child19:39 Go below the surface - Restate child's blaming statement into naming the underlying emotion23:10 Parenting using “try it again” between the parents27:31 If I had the superpower of mindreading - add levity to a situation and tapping into your child's imagination27:40 Mindreading is known as a problematic thinking problem28:23 Again - give the problem back to your child30:05 Stop and acknowledge when your child gets through a struggle - reinforce that they did it!!32:21 How to gain some distance and perspective on past experiences so you don't end up re-experiencing35:20 Naming the dialectic dilemma and identifying priorities36:10 Understanding how to find a synthesis as a solution to a dialectic dilemmaResources:  Handout titled:  Whose Problem is it?Handout on choosing between power over, power under and personal power belief systemLeslie-ism: When you don't like a Child's response use the phrase “Try Again” For a full transcript of this episode and more information about the host visit https://lesliecohenrubury.com/podcasts/ . You can also follow Leslie's work on Facebook and Instagram. Join the conversation with your own questions and parenting experiences.Credits: Is My Child a Monster? is produced by Alletta Cooper, Mia Warren, AJ Moultrié, Camila Salazar, and Leslie Cohen-Rubury. Theme music is by L-Ray Music. Graphics and Website Design by Brien O'Reilly. Transcriptions by Eric Rubury. A special thanks to everyone who contributes their wisdom and support to make this possible.

Deploy your own tech stack: Wes and Scott are joined by Kubernetes expert David Flanagan to be schooled on how Kubernetes, Docker and even WASM containers work. Show Notes 00:00 Welcome to Syntax! 01:55 Should developers know how to run their own servers? 04:57 What is “bare metal”? 11:49 What the hell is Kubernetes? 12:25 Why would somebody need Kubernetes? 15:37 Using Kubernetes to spin up different instances on cloud providers. etcd 16:43 Kubernetes managing traffic spikes. 18:46 How much downtime can you handle? 22:11 What exactly is a container? 24:06 What containers do you prefer? Docker Containerd 25:28 Some additional terminology. OCI Open Container Initiative 26:43 What about WASM? WASM WebAssembly 29:31 Building a Docker container. 31:11 Why would someone want to use a WebAssembly container? 32:12 Are people shipping this technology? 33:36 What functions would you put in WASM? 36:57 How does someone make a WASM image? 39:22 A little more about Spin. Fermyon Spin 39:56 What type of processors are used in these servers? 42:27 What are home servers running on? Turning Pi 2 Daniel Mangum Universal Blue 46:40 How should someone get started with Kubernetes? Kubernetes.io Rawkode YouTube Kubesimplify Learnk8s 48:51 Infrastructure as code. CDK for Terraform GraalVM 55:19 Sick Picks & Shameless Plugs. Sick Picks David: Golem.cloud Restate.dev Shameless Plugs David: Rawkode YouTube Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott:X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

You've been warned, fellow conservatives. Today's show contains content that seems to trigger some, but Stigall feels it needs addressing. Then, Lt. General Keith Kellogg explains what he believes a Trump response would be to the deaths of 3 of our service personnel and what he believes Biden will ultimately do. Restate.com's Bronchie also details the Republican back stabbing over a border "deal" and two members of the Squad who are at their absolute worst. -For more info visit the official website: https://chrisstigall.comInstagram: https://www.instagram.com/chrisstigallshow/Twitter: https://twitter.com/ChrisStigallFacebook: https://www.facebook.com/chris.stigall/Listen on Spotify: https://tinyurl.com/StigallPodListen on Apple Podcasts: https://bit.ly/StigallShowSee omnystudio.com/listener for privacy information.

In this episode of Do This Not That, Jay dives into the importance of call-to-action (CTA) buttons in marketing campaigns. He explains why the specific wording you use on CTA buttons can greatly impact performance, and shares tips for optimizing your buttons to drive more clicks and conversions. Listeners can expect to learn easy ways to improve their CTAs.Main Discussion Points:- Using words that focus on the benefit to the recipient rather than words about the action itself can increase CTA click-through rates by over 20% (00:02:27)- CTAs should highlight what's in it for the prospect or customer by clearly stating the offer or benefit (00:02:31, 00:05:35)- Avoid generic verbs like "submit", "download", "register" - these are overused and don't compel action (00:04:48, 00:06:44)- Restate the offer in your CTA language to reinforce the benefit (00:05:20)- CTAs can be full sentences or phrases, not just single words (00:03:55)- Use AI tools like ChatGPT to easily generate new CTA language (00:06:16)