Podcasts about Merge

This is a prophetic message on 1 Peter 2 and Revelation 7 taken by the casting of the lot before the LORD. INTRODUCTORY MESSAGE TO 4:18 AND THEN WORSHIP SONG AND MESSAGE ending at 44:44. These prophetic messages are preached by the casting of the lot before the LORD to receive any two possible chapters from the Bible using a random Bible application. The 2 chapters often confirm each other to be from God by the common theme discovered in those chapters.

Ariel and the Tramp talk about our unique dynamics and the new experiences we've come across within the lifestyle so far.  Visit us at UnapologeticSwingers.comAlso visit our partners: Shivers.Store and use the discount US at checkout for 10% off your order and our newest sponsor, The Scarlet Ranch! Colorado's premier Lifestyle club

NDAA Shocker Congress Seeks To Merge US_Israeli Militaries! by Ron Paul Liberty Report

Justin is back with his solo side project The Guestlist, where he has on guests....to make lists. Joining Justin this week is Christopher of the Massachusetts indie/punk band Hedge. Hedge released their excellent new EP, Freeze Frame High Five earlier this year, and is here to discuss his favorite obscure / lesser known albums. Hedge Instagram: https://www.instagram.com/hedgebandma/ Hedge Bandcamp: https://hedgebandma.bandcamp.com/album/freeze-frame-high-five Song Clips: Hey Dude by Hedge Pillow by Loomis She Eats Her Esses by Vitreous Humor You're Not An Astronaut by Pond Mickey's Lament by Overwhelming Colorfast Never In by The 101

https://james.cridland.net/blog/2026/abc-sbs/ is where to go to find links for all these stories

UW-Milwaukee pauses plan to merge student centers until 2027. What does this mean for DEI and student support at UWM?

Episode 2 of Secretly Weekly - a new bi-weekly podcast show highlighting the most recent tracks released in the Secretly ecosystem. Everything from Secretly Group, All Flowers Group, Merge and Numero Group.   A radio show delivered to your podcast feed, once every two weeks; hosted by WFHB's Music Director, Abby Noroozi.   Track listing: 1. Jordan Patterson - Just My Friend 2. Dua Saleh - Firestorm 3. aja monet - working class musicians 4. Kevin Morby - 100,000 5. Drunk - Hand on Deck 6. Jensen McRae - Taboo 7. John Carpenter, Cody Carpenter, and Daniel Davies - Lord of the Underground 8. Closure - servant to silence 9. They Hate Change - Run the Road 10. Studio - Life's A Beach! (Todd Terje Beach House Mix)   Secretly Society Podcast on Secretly Store Secretly Society General Information Secretly Society Podcast Episodes

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

Since U.S. President Donald Trump has returned to the White House, several crises have affected the transatlantic relationship. Rym Momtaz, Rosa Balfour, and Stefan Lehne reflect on whether Europeans should stop considering the United States as the partner it once was. [00:00:00] Intro, [00:00:57] Was it Worth it for Europe to Appease Trump?, [00:13:22] EU Dependence on the U.S. in Different Domains, [00:24:56] Is the U.S. Still a Reliable Partner for Europe? Rym Momtaz, ed., May 7, 2026, “Taking the Pulse: Is it Worth it for Europeans to Placate Trump?,” Strategic Europe, Carnegie Europe. Rym Momtaz, May 5, 2026, “Europeans Are Quiet Quitting the United States,” Strategic Europe, Carnegie Europe. Rym Momtaz, ed., April 9, 2026, “Taking the Pulse: Can NATO Survive the Iran War?,” Strategic Europe, Carnegie Europe. Stefan Lehne, March 24, 2026, “Time to Merge the Commission and EEAS,” Strategic Europe, Carnegie Europe. Stefan Lehne, February 12, 2026, “What Can the EU Do About Trump 2.0?,” Carnegie Europe. Rosa Balfour, February 8, 2026, “Dependence on the United States Is Deeply Rooted in the European Mindset,” Le Monde. Rosa Balfour, January 24, 2026, “The EU Finally Used an Economic Threat Against Trump. But the Markets Forces his Climbdown,” The Guardian. Rosa Balfour, January 6, 2026, “The Cost of Europe's Weak Venezuela Response,” Strategic Europe, Carnegie Europe. Stefan Lehne, November 4, 2025, “Can the EU Meet the Trump Moment?,” Strategic Europe, Carnegie Europe. Rosa Balfour, Stefan Lehne, and Elena Ventura, September 22, 2025, “The European Radical Right in the Age of Trump 2.0,” Carnegie Europe.

The companies have entered a definitive agreement to combine in an all-stock transaction.

This episode covers the Naavik Digest newsletter published on Sunday, May 17th. This week, we conduct a focused case study within the highly competitive Merge-2 subgenre of the casual mobile F2P market, where certain Eastern developers are now consistently out-monetizing their Western counterparts while competing for the same audience pools. You can read the newsletter (with even more sections and visual detail) here: https://www.naavik.co/digest/the-eastern-playbook-for-dominating-western-audiencesWant to explore working with Naavik? Shoot us a note: https://naavik.co/contact-us/ Let us know what you think by sending us a note at podcast@naavik.co.Watch our episodes: YouTube ChannelFor more episodes and details: Podcast WebsiteFree newsletter: Naavik DigestFollow us: Twitter | LinkedIn | WebsiteSound design by Gavin Mc Cabe.

Hasbro and Mattel might finally merge into one giant toy monopoly -- a major Mattel shareholder just dropped an open letter demanding the Barbie maker explore a straight-up sale to Hasbro or private equity because the two companies have been whispering about it for decades and Hasbro's actually executing digital growth while Mattel keeps cratering. Yeah after years of both empires bleeding out on shrinking physical toy sales and streaming flops the idea of smashing Transformers with Hot Wheels and Monopoly with Barbie into one unstoppable plastic beast sounds like the only way to survive -- but good luck clearing antitrust regulators who already hate when two giants hold hands. Watch the podcast episodes on YouTube and all major podcast hosts including Spotify. CLOWNFISH TV is an independent, opinionated news and commentary podcast that covers Entertainment and Tech from a consumer's point of view. We talk about Gaming, Comics, Anime, TV, Movies, Animation and more. Hosted by Kneon and Geeky Sparkles. Get more news, views and reviews on Clownfish TV News - https://more.clownfishtv.com/ On YouTube - https://www.youtube.com/c/ClownfishTV On Spotify - https://open.spotify.com/show/4Tu83D1NcCmh7K1zHIedvg On Apple Podcasts - https://podcasts.apple.com/us/podcast/clownfish-tv-audio-edition/id1726838629 MORE CLOWNFISH TV - Official Merch Store: http://ClownfishMinus.com Facebook - https://facebook.com/ClownfishTV X - https://x.com/ClownfishTVcom Clownfish TV subreddit: https://www.reddit.com/r/ClownfishTVOfficial/ Disclaimer: This series is produced by Clownfish Studios and WebReef Media, and is part of ClownfishTV.com. Opinions expressed by our contributors do not necessarily reflect the views of our guests, affiliates, sponsors, or advertisers. ClownfishTV.com is an unofficial news source and has no connection to any company that we may cover. This channel and website and the content made available through this site are for educational, entertainment and informational purposes only. These so-called “fair uses” are permitted even if the use of the work would otherwise be infringing. #News #Podcast #FYP #Shorts #HasbroMattel #HasbroMerger #MattelSale #ToyMerger #HasbroMattelMerger #ToyIndustry #MattelShareholder #ToyDrama Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

You can spend years trying to fix your life from the mind and still feel like something essential is missing. We go straight to the root: the possibility that you are a unique facet of creator consciousness, and that remembering it is how you welcome your power back into your body, your choices, and your daily life. Michael Connell and William Linville unpack what “higher levels” means in real terms, from supportive guidance realms to the deeper “higher self” that wants to fully embody through your physical form. We talk about the heart as the center point of your unique creator facet and share a simple, felt practice for moving attention into the heart, sensing your presence, and allowing that presence to expand through the body. Along the way we explore what it can feel like when your inner frequency shifts, when intuition becomes clearer, and when support feels closer than you expected. Click subscribe, join us next time, and namaste.

Deep tech entrepreneur D. Scott Phoenix spent years building AI — now, he believes we're on the cusp of a profound merger between humans and machines. Reframing the AI debate through the lens of evolutionary biology, he shifts the question from whether we should fear or embrace AI to whether we understand what's at stake if we get it wrong. Hear his provocative case for why we need to "eat the AI." Hosted on Acast. See acast.com/privacy for more information.

368: Before You Merge: Five Factors Every Nonprofit Leader Must Weigh (Staci Barfield)Episode SummaryFor too many nonprofit leaders, the word “merger” lands like a verdict, a sign something has gone wrong. Staci Barfield, Senior Director of Consulting Excellence at Armstrong McGuire in Cary, NC, argues the opposite: a merger belongs early on a leader's strategic menu, not at the end. Drawing on her work facilitating the Arise Collective and MATCH (Mothers and Their Children) merger, Staci walks Patton through the full continuum of collaboration and unpacks the five factors every leader should weigh: mission alignment and strategic rationale, organizational and cultural fit, governance and leadership readiness, financial health and due diligence, and capacity to manage change while continuing to serve. She makes the case that funders are increasingly convening these conversations and that the strategic exercise itself has value even when it doesn't end in a merger. Listeners walk away with a practical framework for assessing any form of collaboration, and a sharper read on when a merger isn't a retreat but a way to magnify mission.About StaciStaci Barfield is Senior Director of Consulting Excellence at Armstrong McGuire, where she leads the methodologies, tools, and resources that equip the firm's advisor team to deliver consistent, high-impact client work. She came to the philanthropic sector after a long corporate career in information technology and business process improvement at Gap, Inc., Andersen Consulting (now Accenture), Sprint, AT&T, and Springs Industries. The pivot was catalyzed when a Hurricane Katrina deployment with the American Red Cross showed her that her business skill set translated directly to mission-driven work. From there she went on to serve as Vice President of Development for the National Multiple Sclerosis Society, Eastern NC Chapter, Executive Director of National Students of AMF, and CEO of Children's Flight of Hope, before joining Armstrong McGuire. Across all of it, Staci has been driven by the same instinct: maximizing an organization's opportunities for success through both strategic and operational initiatives.ResourcesConnect with Staci on LinkedInCase study referenced in the episode: Arise Collective + MATCH (Mothers and Their Children)Shared services model referenced in the episode: Ascend Nonprofit Solutions (Charlotte, NC)Companion episode: #350 with Andre Anthony: What Every Nonprofit Leader Needs to Know About MergersStaci's book recommendation: I Never Thought of It That Way: How to Have Fearlessly Curious Conversations in Dangerously Divided Times by Mónica GuzmánFollow Your Path to Nonprofit Leadership and please leave a review!Learn more about Staci's work and leadership resources at Armstrong McGuire (ArmstrongMcGuire.com)

Liam Naughton grew up in a hyper-competitive environment, from nonstop sports to a 35-day wilderness trip that pushed his limits early on. Now Head of Recruiting at Merge, he's applying that same mindset to building scalable, AI-driven systems while stepping into a new chapter of leadership and fatherhood. In this conversation, he shares how discipline, system thinking, and learning to push through tough moments continue to shape how he operates.Connect with host James Mackey on LinkedIn! Thank you to our sponsor, SecureVision, for making this show possible!  Follow us:https://www.linkedin.com/company/82436841/SecureVision: #1 Rated Embedded Recruitment Firm on G2!https://www.g2.com/products/securevision/reviewsThanks for listening!

LEADERS Special! Cătălin Striblea este live alături de politologul Cristian Pîrvulescu. S-a îndepărtat Nicușor Dan de linia europeană? Ce speră președintele Dan de la americani și ce poate primi? A fost președintele alături de PSD? Și ce guvern iese din această criză. Așteptăm opiniile și întrebările voastre.

Introducing Secretly Weekly - a new bi-weekly podcast show highlighting the most recent tracks released in the Secretly ecosystem. Everything from Secretly Group, All Flowers Group, Merge and Numero Group. A radio show delivered to your podcast feed, once every two weeks. This week's episode features WFHB's Music Director Abby Noroozi, hosting a selection of songs from the wider Secretly ecosystem and select cuts from the Secretly catalog.    Secretly Society Podcast on Secretly Store Secretly Society General Information Secretly Society Podcast Episodes

Supercell absorbs Merge Mansion, Xbox fires its veterans and hires from Instacart, and the math behind gaming's VC collapse finally gets laid out in full.In this episode of TWIG, Mishka is joined by Josh Chandley, John Wright, and Ethan Levy to break down the biggest moves in games this week, from Finland's most beloved merge studio quietly running out of road to why gaming VC funding has dropped 95% since 2021.Topics Covered:● Supercell acquires Metacore and why a profitable $30M a month game still couldn't survive● What the 70% layoffs tell us about liveops competition and the limits of celebrity UA campaigns● Xbox replaces 24-year veterans with Instacart execs, and whether growth engineering can fix a content problem● GameStop bids for eBay with no synergy pitch and why the meme stock era never really ended● Roblox voluntarily takes a billion dollar hit on bookings and why it might be the smartest long-term bet in the room● The math that broke gaming VC funding, from $12.5B in 2021 to $627M in H1 2025 and what founders should do insteadCHAPTERS:00:00 Cold Open Jail Joke00:11 Meet the Hosts01:47 Episode Headlines02:21 Theme Park Mario Talk03:13 Line Monetization Schemes04:40 Istanbul Events Plug05:37 Consulting Shoutout07:03 Supercell Buys Metacore08:38 Metacore Rise and Stumble10:51 UA Cuts and Layoffs20:00 Strategic Investor Dynamics23:14 Xbox Leadership Shakeup24:42 Game Pass and Content Gap26:48 Microsoft IP Live Service Vision28:59 Xbox IPs Need Long Runs29:55 GameStop Buys eBay Meme32:22 Roblox Safety Overhaul Fallout35:32 Age Verification Debate37:02 Roblox Monetization and 18 Plus43:03 Ustwo Cuts Costs Reality45:16 Freelancers Bands Model47:25 Premium Math Doesn't Work51:19 VC Funding Math Broke59:06 Is This the New Normal01:01:56 Wrap Up and Thanks

Every new mobile game is now a copy of a copy. And that's not a complaint — it's the strategy.We dig through the soft launch charts to surface 15+ new games released in the last three months. Voodoo's Block Pals (which is literally just Block Jam 3D again). Moon Active's two new merge games are chasing Gossip Harbor. Spike's Hexa Out, Quick Send, and Solitaire Sort. Grand Games hiding its new Aerogem on the Zimbabwe App Store to dodge takedowns. SuperSend's template-driven creative-first approach with FROZIA and Daily Farm Harvest Empire. Plus the bigger structural question: is Overwatch Rush actually going to make it?The pattern is clear - 80% works, 20% iteration. Every serious studio is following the same playbook. The question is who executes it best.⏱️ TIMESTAMPS00:00 Cold open — merge is the new match-304:04 Field Day by Bitod — ex-Supercell startup goes GTA06:15 Overwatch Rush — Blizzard's mobile play (high CPI face)09:53 Moon Active's merge wave — Reality Bay + Family Bay12:43 Voodoo's Block Pals + Century's DakiMage Color Puzzle15:35 Turkish section — Rolik, Spike, Grand Games dominance25:16 Aerogem hidden on the Zimbabwe App Store27:00 Arrows hits 6.5M DAU — the new template everyone copies28:38 SuperSend's creative-first templates: FROZIA, Daily Farm— "80% works, 20% iteration" is now the default soft launch strategy. Every game in this episode is an iteration on a proven winner — Block Jam, Gossip Harbor, Pixel Flow, Lesmore's Arrows, Township, Last War Creative.— Merge is officially being treated as the new match-3. Moon Active alone has two new merge games in soft launch. Caveat: merge is much harder to balance and live-ops than match-3, so most of these will fail.— Grand Games is hiding its new game Aerogem on the Zimbabwe App Store specifically because legal teams from incumbents (likely MiniClip / Lesmore) don't operate there. This is apparently a real soft launch tactic now.— Spike has abandoned its main App Store account and is publishing everything from a new "testing" account, releasing Hexa Out, Quick Send, and Solitaire Sort in rapid succession with the same template strategy.--------------------------------------PVX Partners offers non-dilutive funding for game developers.Go to: https://pvxpartners.com/They can help you access the most effective form of growth capital once you have the metrics to back it.- Scale fast- Keep your shares- Drawdown only as needed- Have PvX take downside risk alongside you+ Work with a team entirely made up of ex-gaming operators and investors---------------------------------------For an ever-growing number of game developers, this means that now is the perfect time to invest in monetizing direct-to-consumer at scale.Our sponsor FastSpring:Has delivered D2C at scale for over 20 yearsThey power top mobile publishers around the worldLaunch a new webstore, replace an existing D2C vendor, or add a redundant D2C vendor at fastspring.gg.This is no BS gaming podcast 2.5 gamers session. Sharing actionable insights, dropping knowledge from our day-to-day User Acquisition, Game Design, and Ad monetization jobs. We are definitely not discussing the latest industry news, but having so much fun! Let's not forget this is a 4 a.m. conference discussion vibe, so let's not take it too seriously.Panelists: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Jakub Remia⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠r,⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Felix Braberg, Matej Lancaric⁠Matej LancaricUser Acquisition & Creatives Consultant⁠https://lancaric.meFelix BrabergAd monetization consultant⁠https://www.felixbraberg.comJakub RemiarGame design consultant⁠https://www.linkedin.com/in/jakubremiarPlease share the podcast with your industry friends, dogs & cats. Especially cats! They love it!Hit the Subscribe button on YouTube, Spotify, and Apple!Please share feedback and comments - matej@lancaric.me

BlueSky and Twitter/X might merge soon?! No, Elon Musk hasn't talked about buying BlueSky (yet) but a law is being proposed in the EU that would put all American social media platforms under uniform control. This includes making X adhere to BlueSky's moderation sensibilities. Good luck with that... Watch the podcast episodes on YouTube and all major podcast hosts including Spotify. CLOWNFISH TV is an independent, opinionated news and commentary podcast that covers Entertainment and Tech from a consumer's point of view. We talk about Gaming, Comics, Anime, TV, Movies, Animation and more. Hosted by Kneon and Geeky Sparkles. Get more news, views and reviews on Clownfish TV News - https://more.clownfishtv.com/ On YouTube - https://www.youtube.com/c/ClownfishTV On Spotify - https://open.spotify.com/show/4Tu83D1NcCmh7K1zHIedvg On Apple Podcasts - https://podcasts.apple.com/us/podcast/clownfish-tv-audio-edition/id1726838629 MORE CLOWNFISH TV - Official Merch Store: http://ClownfishMinus.com Facebook - https://facebook.com/ClownfishTV X - https://x.com/ClownfishTVcom Clownfish TV subreddit: https://www.reddit.com/r/ClownfishTVOfficial/ Disclaimer: This series is produced by Clownfish Studios and WebReef Media, and is part of ClownfishTV.com. Opinions expressed by our contributors do not necessarily reflect the views of our guests, affiliates, sponsors, or advertisers. ClownfishTV.com is an unofficial news source and has no connection to any company that we may cover. This channel and website and the content made available through this site are for educational, entertainment and informational purposes only. These so-called “fair uses” are permitted even if the use of the work would otherwise be infringing. #BlueSky #Twitter #SocialMedia #MarkHammill #ElonMusk #Podcast #Commentary #News #Reaction #Gaming #Comedy #Entertainment #Hollywood #PopCulture #Tech #Anime #FYP Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Pool Pros text questions hereThis episode covers the challenges and opportunities of pool service businesses during winter, including cost management, database maintenance, and team engagement strategies. Learn practical tips to streamline operations, enhance professionalism, and maximize revenue in the off-season.keywordspool service, winter business tips, database management, team engagement, cost control, pool maintenancekey topicsCost management for island service tripsDatabase cleanup and client follow-upUsing photos and measurements for efficient serviceTeam involvement and process improvement during winterSound Bites"Your database is the value of your business""Merge and clean your client data regularly""Photos serve as proof and quality assurance"Chapters00:00Introduction and guest introduction01:14Challenges of island service trips and costs01:58Managing costs and pricing for island services03:15Impact of seasonal changes on pool service business04:08Preparing for winter: pool hibernation and maintenance06:40Winter cleanup: database and photo management08:37Importance of maintaining a clean client database11:07Strategies for identifying and merging duplicate clients13:44Using photos and measurements for service efficiency16:46Starting winter projects: cleaning and process improvements20:33On-site documentation and client communication24:18Using photos and GPS for quality assurance28:19System cleanup and data management33:28Follow-up strategies and scheduling reminders39:50Team engagement and winter productivity40:05Fun and camaraderie in team challenges41:11Closing remarks and call to actionResourcesBufferZoneXero Accounting Software Support the showThank you so much for listening! You can find us on social media:FacebookInstagramTik TokEmail us: talkingpools@gmail.com

She is going back to her original vibration, and so are you... Time to Merge with the one that created you.   I am you Magdala www.magdalas.com Buy her New Book!!!!!!!!!NOW!!!!!! Visit her website!!!!

In a move that became official at a Section XI meeting a few weeks back, the high school football programs at Hampton Bays and Southampton will merge in 2026 to become one. Hampton Bays, which has recently seen a strong resurgence of the sport after taking two years off to rebuild, will be the host school, welcoming Southampton students who would like to play. Despite the two schools legendary rivalry for the Mayor's Cup, a tradition on the South Fork going back 40 years, this new combined team program is a sign of the times and represents an effort to save football for both communities. This week, the editors are joined by news reporter (and former sports editor) Cailin Riley and Hampton Bays Athletic Director John Foster to talk about the rivalry, the plan and the love for the tradition of high school football in challenging times.

Merge K9 joins us for another very nerdy episode discussing many topics including tool bans in other countries, making training less complex, and if we REALLY can systematize our training programs

The entire theory of games is underpinned by this one theory, but how far can it's explanitory power be pushed? Phillip Black, Christopher Kaczmarczyk-Smith, and Eric Guan talk cozy Pokemon habitats, merge-game economics multipliers, AI labor-market irony, and Edward Castronova's foundational work on virtual worlds. We talk: Pokopia as the Pokemon cozy game: short production chains daily-quest systems without free-to-play monetization pressure Multipliers as the key merge-game innovation: a gas pedal on spend per hour faster energy drain faster story progression a new way to price acceleration Narrative as reward subsidy or tax: story can make the next meta milestone worth chasing story can also break flow for players who just want the core loop AI and the game-industry labor market: layoffs look more like a post-2021 correction longer unemployment spells in information work may be the cleaner AI signal AI may suppress hiring before it shows up as direct separations Castronova's virtual-world economics: challenge labor-leisure tradeoffs property rights platform dictatorships price controls why MMOs looked like the future in 2003 The player contract: games rarely grant formal property rights players still behave as if they own skins, items, and progress developers often compensate players even when the legal right is weak Chapters (00:00:00) - Game of Thrones Cast Episode 50(00:00:39) - Coming soon: The Quantitative Bar(00:01:01) - Game Economist: Jobs to AI, Episode 49(00:02:16) - Pocopia: The Pokemon Cozy Game(00:05:03) - How Does Pokepoea Work?(00:08:42) - GTA 6 vs Breath of the Wild: Why They're Both(00:11:19) - The Economics of Merge 2(00:18:33) - How to Boost the Economy of 'League of Legends'(00:20:27) - On Buying Meta-Progression(00:22:09) - Candy Crush: The Match 3 Revenue(00:23:18) - Mixed Effects of More Narrative in Merge(00:27:39) - The Problem With Non-Traditional Gamers(00:29:36) - AI and the Game Industry Labor Market(00:35:39) - The Unemployment gap between Information and Non-Information(00:44:19) - Will AI Impact Workers' Jobs?(00:48:02) - Better Employment Data for the Games Industry(00:49:53) - Vinod's Virtual Economy(00:55:00) - Bradley on Work vs Leisure(00:58:12) - On Maximalization in MMOs(01:03:58) - No Property Rights in Magic The Gathering(01:05:43) - Game Developers: Property Rights in the Blockchain(01:10:03) - Game economies vs Real-Life(01:12:58) - Paul Krugman: The optimal level of challenge

Urmărește podcastul numărul 275 de la Acasă la Măruță, unde Cătălin Măruță o are ca invitată pe Sore.#catalinmaruta #podcast #sore

And a new radio streaming app for iOS.More at https://radioland.email

What happens when a declining LCMS church chooses courage over comfort? This episode shares the real story of a church merger that brought new life, new people, and renewed faith. As more and more LCMS churches are in decline, helping churches merge like this is a path forward. To access the show notes, visit www.redletterpodcast.com.

Survivor AU: Redemption Mark Warnock Deep Dive Today, Mike Bloom dives deep with contestant, Mark Warnock, about his time on Australian Survivor: Redemption. Mark Warnock brings all the behind-the-scenes drama, starting with the shock of being the last-minute returnee, leading to one of the wildest Tribal Councils and strategy scrambles of the season. Whether it's wearing a bold “Caleb, you are not beating the allegations” shirt or orchestrating live tribals, Mark pulls back the curtain on the chaos of Redemption Beach and what it's really like to run the show—until the show runs you. Mark shares how he was contacted at the very last moment to join the “Redemption” season, returned to Samoa with a cutthroat mindset, and navigated shifting alliances, idol finds, and orchestrated blindsides. He breaks down his approaches in connecting early with competitors like Faith and Brooke, forming “head office” alliances, and executing daring live votes—including pulling people out of the voting lines to flip the result in front of the tribe. Hear candid behind-the-scenes takes on the infamous Kat vote switch, the fallout from early game power moves, and the rivalry with Johnson, as well as what it's like being targeted as “the boss” by new players. Key moments and gameplay: Mark reveals the wild scramble to join the season, how family and work played into his late decision, and what inspired him to play harder the second time. A breakdown of the live tribal that flipped the first vote from Johnson to Kat, with Mark explaining the risks, social reads, and fallout back at camp. How “head office” dynamics with Faith and Keeley controlled strategy, but also sowed the seeds for explosive betrayals at swap and beyond. Hilarious moments from camp life, including alliance-building over band tattoos and shelter-building grudges, as well as a “Cornship Cartel” underwater alliance. Deep look into tribal council strategy: creating fake idols, pivoting targets live, and the struggle to balance being both shield and target. What will happen when playing a “boss” game puts all eyes—and votes—on you? Can you truly trust your number one ally, and is it ever smart to show your idol at Tribal? Tune in to catch every twist, tribe flip, and dramatic confessional as Redemption leaves nothing off the table. Listen now for exclusive insights into idol reads, game-changing alliance flips, and the biggest blindsides of Australian Survivor: Redemption! Chapters: 0:00 Redemption Season Invitation for Mark 6:53 Mark and Wife Decide Return 13:10 Adopting Aggressive Game Approach 18:00 Brooke and Mark's Key Alliance 21:50 Building the Ruby Soho Trio 26:46 Johnson Targeted, Then Cat's Blindside 35:49 Handling Tribal Fallout with Confidence 42:01 Don Joins Mark's Cornship Cartel 49:59 Tez Falters, Mark Moves On 54:46 Tribe Swap Alters Alliances 58:52 Don's Blindside by Keeley 1:05:04 Head Office Power Struggles 1:11:27 Lindell or Rich? Deciding Loyalties 1:17:23 Tez's Insubordination Seals Fate 1:23:24 Live Tribal Reveals Mark's Threat 1:29:30 Faith's Brutal Honesty Sparks Shift 1:34:13 The Faith Blindside Operation 1:40:57 Merge and Reuniting with Brooke 1:46:29 Lottie Voted Out at Merge 1:51:47 Caleb Betrays Mark's Trust 1:53:53 Fake Idol, Real Idol Play 1:59:47 Caleb's Vote Blindsides Mark 2:32:57 Jury Villa: Shocking Arrivals 2:41:52 Final Tribal: Jury Interrogation 2:54:31 Mark Reflects on His Journey Never miss a minute of RHAP's extensive Global Survivor coverage! LISTEN: Subscribe to the Survivor Global podcast feed WATCH:  Watch and subscribe to the podcast on YouTube SUPPORT:  Become a RHAP Patron for bonus content, access to Facebook and Discord groups plus more great perks!

This is the episode we have been waiting years to make.On this episode of RWorld Talk, host Chris Krzemien sits down with RWorld President Jonathan Dolphus to share major news: a historic merger between Miami REALTORS® and RWorld. 93,000 members. $69 billion in sales volume in 2025. One organization.They talk through what actually happened, what will change for members, and what this opens up for agents across South Florida and beyond.We Covered: ➡️ How a lunch between two association presidents turned into a historic deal➡️ What will change, including full data access and no longer needing two separate MLS feeds➡️ What 93,000 voices speaking together mean for property rights and local legislation➡️ and more…This is a big moment for South Florida real estate. As we finalize the merger, the next step is a Special Membership Meeting. Register for the April 30th meeting or submit your proxy by April 29th at MiamiandRWorld.com.FOLLOW US:Instagram: @rworldtalkLinkedIn: @rworldtalkpodcastWebsite: https://rworld.com/LISTEN ON AUDIO:Spotify: https://open.spotify.com/show/6TFUYs7cTWw539wUD7aLkE?si=79cdc73ede2f4828Apple: https://podcasts.apple.com/us/podcast/rworld-talk-south-florida-real-estate/id1671206655#SouthFloridaRealEstate #MiamiRealtors #OurWorld #BeachesMLS #OurWorldTalk #RealtorNews #RealEstateMerger #GlobalRealEstate

Special two-part episode of the podcast this week! The big news in Hollywood this week has been the burgeoning effort by Hollywood creatives to fight the purchase of Warner Bros. by Paramount Skydance. Thousands of names—including some of the biggest in the business—have signed an open letter in the hopes of demonstrating that not everyone in the industry is on board with the potential deal. So I wanted to talk to some of the folks behind it.First up is an interview with Ted Hope, indie producer extraordinaire and author of the Hope for Film Substack. We talked about how indie production has changed over the last few decades and what could be lost if Warner Bros. and Paramount are allowed to merge. Then I got Jon Reiss and Jax Deluca of the Future Film Coalition on the horn. We discussed what concrete steps could be taken to help fight this merger and what media consolidation means to the indie filmmakers out there. If you found this podcast interesting or informative, I hope you share it with your friends!

Ep. 243 Desiree Cruz, CEO of Merge Worldwide and author of "Warrior Women," shares how personal trauma and loss inspired her to create a movement that empowers women to share their stories without shame. The episode explores themes of healing, legacy, and the importance of community. Desiree touches on how her daughter's passing fueled her mission to honor legacy and help women find their voices. This conversation offers insights into turning pain into purpose and creating lasting impact. "I want women to start leaning into their stories. I want them to be openly sharing their stories without shame and without guilt and without rebuttal." – Desiree Cruz Website: Home - Merge Worldwide LinkedIn: https://www.linkedin.com/in/desire-cruz-2a884334a/ Desire Cruz is the daughter of the most High, wife of Jesse Cruz, and mother of 3 beautiful daughters Haleigh, Mariah, and Faith. She is the Co-CEO OF MERGE WORLDWIDE AND LEADING AUTHOR OF WARRIOR WOMEN. Desire also is an international world traveler, event planner, transformation coach, and keynote speaker. She loves all things women empowerment, and enjoys nature in her spare time. Resources Mentioned: Join our next anthology project! Coauthor | The Liberated Woman's Movement The 200N1 Project - Ebony Nicole Smith Consulting⁠ ⁠Cristo's Wood Fired Pizza and Pasta ⁠ 1308 Buffalo Road, Rochester NY

Peter Griffin on Amazon's acquisition of satellite operator GlobalStar, which will have major implications for satellite broadband. 

It's time for the Merge of Survivor 50! We have some fights, some strategy, and a whole lot of haikus. We breakdown where each player is at and how this season could play out! 'Survivor talk starts at 14:25

Survivor 50 B&B Ep 7 Recap w/ J.E. Skeets With a new Survivor season upon us, it's time for Mike Bloom and Liana Boraas to re-open the RHAP B&B! On the B&B, Mike and Liana are inspired by the lighter side of Survivor, featuring a series of segments and games based on what's happening on Survivor that week.  This week, Mike and Liana are joined by “No Dunks” and “No Buffs” host J.E. Skeets to talk about Episode 7 of Survivor 50! Mike Bloom and Liana Boraas welcome J.E. Skeets to the Survivor B&B for a lively breakdown of Survivor 50, episode 7. This episode dives deep into the chaos of the merge, where a tribe swap breaks up the season's core alliances and launches new power dynamics, especially as a once-quiet pair steps into the spotlight. Mike, Liana, and Skeets explore the pivotal role of the Beware Advantage: Whether it's smarter to share the secret to build trust or keep it close for strategic leverage, risking paranoia and blindsides. They discuss how players use idol threats not just for protection, but as bargaining chips to drive the vote. Camp drama and challenge mishaps add fuel to the game, with the hosts debating whether work ethic and performance still carry weight in the late game or if social bonds are the true currency. The “swing” duo plays both sides, but the risk of showing their hand too soon could cost them control or lock in their path to the merge. At Tribal Council, backup plans and decoy names swirl, turning whispers into a last-minute strategy flip. Mike, Liana, and Skeets trace who truly pushes the vote, who just follows, and how journey bonds and swapped tribes complicate trust. Highlights: – How the tribe swap lifts a quiet pair into a powerful position – Idol secrecy vs. trust: the strategic trade-offs – Challenge performance as late-game leverage – Decoy plans and journey bonds: benefits and risks post-swap Looking forward, the hosts ask: Will the middle pair lose their grip or secure merge power? Does the Beware Advantage spark trust or set up the next big blindside? Survivor B&B brings playful analysis, games, and plenty of laughs. Don't miss their take on Survivor's most unpredictable moments! 0:00 Merge begins, jury starts forming 6:05 Coach ignites drama at hammock 13:05 Coach haikus and tribal missteps 18:46 Coach dances, Aubry awkwardly joins 26:42 Rizo confronts Coach, dragon talk 32:03 Dee's downfall, split vote plans 40:41 Aubry's idol mistake exposed 48:47 Cirie reads Stephenie's Exile lie 55:00 No one wants journey twist 1:02:44 Dee boot predictions judged This week's charity shoutout is the Atlanta Angels, which provides relational support to fostering family and mentoring to youth in foster care by engaging the community. Click here to make a donation. Check out Peace Corps: https://peacecorps.gov/serve To pre-order Rob's book, The Tribe and I Have Spoken, visit www.robhasabook.com Never miss a minute of RHAP's extensive Survivor coverage! LISTEN: Subscribe to the Survivor podcast feed WATCH:  Watch and subscribe to the podcast on YouTube SUPPORT:  Become a RHAP Patron for bonus content, access to Facebook and Discord groups plus more great perks!

Survivor 50 B&B Ep 7 Recap w/ J.E. Skeets With a new Survivor season upon us, it's time for Mike Bloom and Liana Boraas to re-open the RHAP B&B! On the B&B, Mike and Liana are inspired by the lighter side of Survivor, featuring a series of segments and games based on what's happening on Survivor that week.  This week, Mike and Liana are joined by “No Dunks” and “No Buffs” host J.E. Skeets to talk about Episode 7 of Survivor 50! Mike Bloom and Liana Boraas welcome J.E. Skeets to the Survivor B&B for a lively breakdown of Survivor 50, episode 7. This episode dives deep into the chaos of the merge, where a tribe swap breaks up the season's core alliances and launches new power dynamics, especially as a once-quiet pair steps into the spotlight. Mike, Liana, and Skeets explore the pivotal role of the Beware Advantage: Whether it's smarter to share the secret to build trust or keep it close for strategic leverage, risking paranoia and blindsides. They discuss how players use idol threats not just for protection, but as bargaining chips to drive the vote. Camp drama and challenge mishaps add fuel to the game, with the hosts debating whether work ethic and performance still carry weight in the late game or if social bonds are the true currency. The “swing” duo plays both sides, but the risk of showing their hand too soon could cost them control or lock in their path to the merge. At Tribal Council, backup plans and decoy names swirl, turning whispers into a last-minute strategy flip. Mike, Liana, and Skeets trace who truly pushes the vote, who just follows, and how journey bonds and swapped tribes complicate trust. Highlights: – How the tribe swap lifts a quiet pair into a powerful position – Idol secrecy vs. trust: the strategic trade-offs – Challenge performance as late-game leverage – Decoy plans and journey bonds: benefits and risks post-swap Looking forward, the hosts ask: Will the middle pair lose their grip or secure merge power? Does the Beware Advantage spark trust or set up the next big blindside? Survivor B&B brings playful analysis, games, and plenty of laughs. Don't miss their take on Survivor's most unpredictable moments! 0:00 Merge begins, jury starts forming 6:05 Coach ignites drama at hammock 13:05 Coach haikus and tribal missteps 18:46 Coach dances, Aubry awkwardly joins 26:42 Rizo confronts Coach, dragon talk 32:03 Dee's downfall, split vote plans 40:41 Aubry's idol mistake exposed 48:47 Cirie reads Stephenie's Exile lie 55:00 No one wants journey twist 1:02:44 Dee boot predictions judged This week's charity shoutout is the Atlanta Angels, which provides relational support to fostering family and mentoring to youth in foster care by engaging the community. Click here to make a donation. Check out Peace Corps: https://peacecorps.gov/serve To pre-order Rob's book, The Tribe and I Have Spoken, visit www.robhasabook.com Never miss a minute of RHAP's extensive Survivor coverage! LISTEN: Subscribe to the Survivor podcast feed WATCH:  Watch and subscribe to the podcast on YouTube SUPPORT:  Become a RHAP Patron for bonus content, access to Facebook and Discord groups plus more great perks!

The Merge has occurred. Survivor season 50 and the show will never be the same. Stan welcomes Dan Hansen from the Grand Circle Tour podcast to discuss their feelings on what's happening this season. Spoilers start right from the opening horn, so if you are still an episode or two behind... Well first of all get your priorities right then come back and listen to the show.  ----------------------- Hello and welcome to this edition of The Solo Show. THANK YOU for your support by joining us and our fun little podcast where YOU can be the co-host. Simple reach out to me at thesoloshow01@gmail.com with your idea for a show and we will see about being my co-host for a day. All you need is a love for Disney, a show idea, and a decent internet connection. ~Stan Solo ----------------------- If you enjoy the show then show some love by sharing out that your listening, and be sure to subscribe. Plus, take a few minutes to write a review on Apple Podcast…only one rule, make it good.  ----------------------- If you ever dreamed about living next to the most Magical place on Earth by moving to the Orlando area be sure to visit our sponsor Victor Nawrocki, he to help you make your dream a reality. Visit CelebratingFlorida.com today and find your future near the magic. Remember to tell him The Solo Show sent you. -------------------- Ken the Voiceover Guy is available for hire. Maybe you need him to read an ad for you, or record your podcast intro, etc. Send him an email at tvfella67@gmail.com for more information and prices. ----------------------- LET'S CONNECT!  Facebook.com/TheSoloShow01 Facebook.com/groups/TheSoloShow •Instagram.com/the_solo_show_podcast •Twitter.com/@thesoloshow1 •YouTube.com/TheSoloShow TheSoloShow.com- Visit our website for quick access to past shows. ----------------------- © 2026 - The Solo Show is in no way part of, endorsed or authorized by, or affiliated with the Walt Disney Company or its affiliates. As to Disney artwork/properties: © Disney. Disclosure | Privacy Policy  

Debjit Mukerji, Partner at NGP Capital, explains why deep tech's defining moment has finally arrived. Drawing on a thesis-driven approach, he shares how he evaluates companies at the intersection where “atoms meet bits”, backing founders building in the physical world. Debjit breaks down the convergence of three powerful forces—labor shortages, generative AI's expansion into industrial use cases, and faster hardware development cycles—that are unlocking a new era of opportunity for physical technology companies. In this episode, you'll learn: [05:28] Why venture capital? [07:40] Inside NGP Capital's deep tech focus [11:05] Why now is the moment for deep tech [17:02] What Debjit looks for in founders [19:17] The Tractian story: founder intensity [31:39] Key deep tech trends: Robotics & AI [35:43] What makes a great deep tech pitch The nonprofit organization Debjit is passionate about: MedShare About Debjit Mukerji Debjit Mukerji is a Partner at NGP Capital, where he focuses on Deep Tech investments across robotics, AI, and industrial systems. With over two decades in venture capital, Debjit brings a strong technical foundation, holding a PhD in mechanical engineering from Stanford University. His career has spanned roles across multiple leading firms and industrial technology platforms, where he has consistently focused on translating breakthrough research into real-world impact. He is particularly passionate about backing founders building at the intersection of software and the physical world—where innovation is hardest, but most enduring. About NGP Capital NGP Capital is a global venture capital firm dedicated to investing in Deep Tech companies. With a focus on “digital-physical convergence,” the firm backs startups that apply AI, software, and hardware to transform physical industries. NGP Capital invests primarily at the Series A and B stages, with a global footprint spanning North America, Europe, and beyond. The firm partners closely with founders building in sectors such as robotics, industrial software, space technology, and connected systems, supporting companies that aim to redefine how the physical world operates. Subscribe to our podcast and stay tuned for our next episode.

Join host Sam Davidson on Circle Back as he welcomes Nashville Entrepreneur Center Hall of Famer, Ron Samuels. Discover Ron's extraordinary entrepreneurial journey, from his early encounters with industry giants Kimmons Wilson (Holiday Inns) and Fred Smith (FedEx) to founding an antique store, co-founding the Mid-South School of Banking, and an innovative marketing campaign that famously mailed bricks to double market share in the building materials industry. Ron shares insights from his decades-long career in banking, navigating a landscape of constant mergers and acquisitions, and his audacious decision to start Avenue Bank at the age of 60, just before the 2008 financial crisis. Learn how Avenue Bank cultivated a unique, people-first culture, leading to rapid growth and a successful acquisition by Pinnacle. This episode also delves into Nashville's remarkable transformation, its strategic growth initiatives from Partnership 2000 to bringing professional sports, and Ron's foundational advice for entrepreneurs on character, authenticity, and empowering leadership. Episode Highlights: 0:01:03 - Meeting Kimmons Wilson (Holiday Inns) & Fred Smith (FedEx) 0:03:03 - Ron's First Entrepreneurial Endeavors: Paper Route & Mid-South School of Banking 0:05:25 - The Story Behind Starting an Antique Business ("Secondhand Rows") 0:08:30 - Early Life, Family Background, and the Path to Banking 0:17:30 - Recognizing His Entrepreneurial Spirit & Early Banking Culture 0:19:08 - Moving to Nashville in 1975 & the City's Banking Landscape 0:27:59 - Doubling Market Share in the Brick Business by Mailing Bricks 0:31:57 - Returning to Banking & Pursuing an MBA at Vanderbilt (Owen School) 0:35:21 - Navigating Decades of Banking Mergers & Acquisitions 0:40:04 - The Bold Decision to Start Avenue Bank at 60 0:43:08 - The Avenue Bank Success Story: Community, Growth, and Unique Culture 0:48:59 - Why Avenue Bank Decided to Exit and Merge with Pinnacle 0:55:20 - Reflecting on Nashville's Strategic Growth and Transformation 1:00:25 - Essential Advice for Aspiring and Seasoned Entrepreneurs Listen now to uncover the wisdom from one of Nashville's most influential business leaders! If you enjoyed this episode, please share it with a friend and leave us a review on your favorite podcast platform. Connect with Circle Back: Circle Back Podcast Follow Sam Davidson's LinkedIn Learn more about the Nashville Entrepreneur Center In partnership with Nashville Post #RonSamuels #AvenueBank #NashvilleEntrepreneur #Podcast #Entrepreneurship #Banking #NashvilleHistory #FedEx #HolidayInn #StartupLife #BusinessGrowth #Leadership #CommunityBuilding #CircleBackPodcast #SamDavidson #NashvillePost #BusinessAdvice #EntrepreneurJourney #NashvilleBusiness #MergersAndAcquisitions #BankFounder

Breaking Down the Survivor 50 Post-Merge Today, Rob Cesternino is breaking down the fallout from one of the wildest moments yet: the historic three-person elimination right at the merge. In this special recap episode, Rob explores how the “Blood Moon” shake-up completely changes the game for the 14 players left competing for the title of Sole Survivor. What does it mean to have the biggest merge vote ever, and who's really holding the power as new alliances start to take shape? Rob lays out the key groups forming around camp—including the “Honor and Loyalty 5,” featuring Coach, Joe, Jonathan, Stephenie, and Chrissy—and the tight trio of Cirie, Ozzy, and Rizo, who have a pile of idols and advantages. He unpacks why Rick and Christian's dynamic duo status could put a target on their backs and how Aubry, now a true free agent, might tip the balance between these shifting sides. The “rats before the war” speech, the idol complications from the Billie Eilish Boomerang twist, and where Tiffany and Dee stand after Kamilla's blindside are all up for debate. – The risky alliances forming after the triple Tribal Council – Cirie, Ozzy, and Rizo's idol stash and what makes them dangerous – The fallout for Jonathan as a target after betraying the “new era” players – Aubry's unique position as a swing vote who could flip the game – How the “rats before the war” warning may shape the next big move With the next Tribal Council looming, Rob examines whether the “new era” bloc will stay united or start voting out their biggest threats from within. Could old wounds or wild twists derail the majority, or will Coach's crew pull off another surprise? Get all the behind-the-scenes insight and alliance breakdowns—tune in for Rob's Survivor 50 analysis, from secret idol plays to the next possible blindside! To pre-order Rob's book, The Tribe and I Have Spoken, visit www.robhasabook.com Never miss a minute of RHAP's extensive Survivor coverage! LISTEN: Subscribe to the Survivor podcast feed WATCH:  Watch and subscribe to the podcast on YouTube SUPPORT:  Become a RHAP Patron for bonus content, access to Facebook and Discord groups plus more great perks!

Breaking Down the Survivor 50 Post-Merge Today, Rob Cesternino is breaking down the fallout from one of the wildest moments yet: the historic three-person elimination right at the merge. In this special recap episode, Rob explores how the “Blood Moon” shake-up completely changes the game for the 14 players left competing for the title of Sole Survivor. What does it mean to have the biggest merge vote ever, and who's really holding the power as new alliances start to take shape? Rob lays out the key groups forming around camp—including the “Honor and Loyalty 5,” featuring Coach, Joe, Jonathan, Stephenie, and Chrissy—and the tight trio of Cirie, Ozzy, and Rizo, who have a pile of idols and advantages. He unpacks why Rick and Christian's dynamic duo status could put a target on their backs and how Aubry, now a true free agent, might tip the balance between these shifting sides. The “rats before the war” speech, the idol complications from the Billie Eilish Boomerang twist, and where Tiffany and Dee stand after Kamilla's blindside are all up for debate. – The risky alliances forming after the triple Tribal Council – Cirie, Ozzy, and Rizo's idol stash and what makes them dangerous – The fallout for Jonathan as a target after betraying the “new era” players – Aubry's unique position as a swing vote who could flip the game – How the “rats before the war” warning may shape the next big move With the next Tribal Council looming, Rob examines whether the “new era” bloc will stay united or start voting out their biggest threats from within. Could old wounds or wild twists derail the majority, or will Coach's crew pull off another surprise? Get all the behind-the-scenes insight and alliance breakdowns—tune in for Rob's Survivor 50 analysis, from secret idol plays to the next possible blindside! To pre-order Rob's book, The Tribe and I Have Spoken, visit www.robhasabook.com Never miss a minute of RHAP's extensive Survivor coverage! LISTEN: Subscribe to the Survivor podcast feed WATCH:  Watch and subscribe to the podcast on YouTube SUPPORT:  Become a RHAP Patron for bonus content, access to Facebook and Discord groups plus more great perks!

Get the full episode here: https://www.10percenttrue.com/pricing-plans/list10PCT EP86 P1 – Benji PrefontaineChapters0:00 Intro Teaser – M1.3 Corner Speed, Avoiding the Merge, Low Level3:00 Welcome, Benji4:15 Subscriber Question (T-Stoff) – Super Étendard Carrier Ops10:35 The Hardest Flying of His Career?13:44 Route to the Air Force16:15 Initial Flying & Training Curriculum19:04 Early Impressions & Developing Mission Focus23:48 Choosing a Platform & Mission27:10 Explaining Career Choices29:15 The Mirage 2000N Mission31:32 Revisiting the Training Accident & Its Repercussions36:14 Ready for That Conversation?38:44 The Reward for That Risk40:22 Alpha Jet46:36 Air-to-Air Phase – How Formative?49:18 Armée de l'Air Culture56:00 Parents' Opinions57:37 Mirage F1CT – Introduction, Impressions & Capabilities1:06:05 Electronic Warfare Suite1:07:40 MATRA 530 – Fox 1 Capability1:13:53 Were Export F1 Variants Better?1:17:00 Diving Deeper into EW Capabilities1:20:42 M1.3 Corner Speed – Avoiding the Merge at Low Level1:23:34 “Cheating” in the F1?1:26:10 DACT Opportunities1:27:57 Taking on the Mirage 20001:30:48 Recce & Air-to-Ground Role1:36:45 ELINT System Autonomy & Mission Planning1:40:26 Datalink1:41:50 Flying Qualities (and Vices) of the F11:46:04 Bird Strikes1:48:20 Experience on the F1CT & Close Calls1:50:58 Air-to-Air Refuelling – Tankers, Techniques & Night Ops2:02:15 Geeking Out & Previewing the Next Episode

The Merge is here, and alliances are tested as the immunity challenge brings a twist never before seen.Become a supporter of this podcast: https://www.spreaker.com/podcast/challenged-a-podcast-about-the-challenge-on-cbs-mtv-and-paramount--3392015/support.Head over to ChallengedPod.Com for more info.

The industry isn't slowing down. This week, we break down the biggest shifts across games.Topics Covered:● Disney and Epic: Why the speculation is picking up and what a bigger Disney move into games could look like● Unity's latest shift: A strong earnings beat, the shutdown of Ironsource, and the sale of Supersonic● Studio closures and shutdowns: What the latest cuts across VR, live service, and Embracer say about the market● The Merge 2 rise: Why the category keeps growing and the debate over what's really driving the revenue● Cookie Run's next step: Franchise expansion and the challenge of turning one hit into something bigger● New soft-launch shooters: Ex-Supercell teams, familiar patterns, and questions about where action games fit on mobilePlus ++We also get into Tim Sweeney's role in Epic's future, Unity versus AppLovin in ad tech, card systems, soft-launch design, and Kress's latest reality check on mobile.CHAPTERS: 01:14 Mario Movie Backlash03:45 Leroy Jenkins Capital06:52 Housekeeping And Corrections09:10 Disney Buying Epic Rumor12:12 Tim Sweeney Control Fight14:55 Entertainment Gaming Graveyard17:46 Unity Dumps IronSource23:22 Vector Versus AppLovin Scale26:35 Shutdowns And VR Reality Check30:46 Matthew Ball Metaverse Spat33:38 Embracer Wildland Canceled36:50 Merge Two Boom Explained42:29 Cards Drive Revenue Debate50:48 Cookie Run Franchise Bet56:50 Soft Launch Shooter Doubts01:00:22 Field Day Hands On Review01:06:06 Kress's Mobile Reality Rant01:10:16 Episode Wrap Up

“Time won't fly, it's like I'm paralyzed by it.” What happens when you try to pin down something as slippery as time itself? This week's episode gets philosophical as we explore how Taylor Swift uses time as a literary device—as narrative structure, as metaphor, as a way to measure how much we've changed. From flashbacks and tense shifts to nostalgia and the ache of looking back, we unpack how time shapes Taylor's storytelling. Maansi traces the dramatic irony of “15” (Fearless, 2008), Jenn explores how “Timeless” (Speak Now (Taylor's Version), 2023) removes time to reveal the purest form of love, and Jodi breaks down the stream-of-consciousness time travel of “All Too Well” (Red, 2012). Grab your clocks, calendars, and time-turners—class is in session. Subscribe for free to get episode updates or upgrade to paid to get our After School premium content: aptaylorswift.substack.com/subscribe After School subscribers get monthly bonus episodes, exclusive content, and early access to help shape future topics! Stay up to date at aptaylorswift.com Discover all our book recs & episodes: https://swift-recs-explorer.lovable.app/ Mentioned in this episode: Memento (2000 film) The Night Circus, Erin Morgenstern Wuthering Heights, Emily Brontë Mrs. Dalloway, Virginia Woolf Station Eleven, Emily St. John Mandel Inside Out (2015 film) The Merge, [Author] StoryGraph Atonement, Ian McEwan The Ministry of Time, Kaliane Bradley Outlander, Diana Gabaldon The Unmaking of June Farrow, Adrienne Young The Good Place (Jeremy Bearimy)   ***   Episode Highlights: [01:12] Time as a literary device: structure, theme, and symbolism [08:52] “Fifteen,” Fearless [20:23] “Timeless,” Speak Now (Taylor's Version)   [31:39] “All Too Well,” (Red)   Follow AP Taylor Swift podcast on social! TikTok → tiktok.com/@APTaylorSwift Instagram → instagram.com/APTaylorSwift YouTube → youtube.com/@APTaylorSwift Link Tree → linktr.ee/aptaylorswift Bookshop.org → bookshop.org/shop/apts Libro.fm → tinyurl.com/aptslibro   Contact us at aptaylorswift@gmail.com Affiliate Codes: Krowned Krystals - krownedkrystals.com use code APTS at checkout for 10% off! Libro.fm - Looking for an audiobook? Check out our Libro.fm playlist and use code APTS30 for 30% off books found here tinyurl.com/aptslibro   This podcast is neither related to nor endorsed by Taylor Swift, her companies, or record labels. All opinions are our own. Intro music produced by Scott Zadig aka Scotty Z.

Short and sweet episode for you today because we were on a little bit of a time crunch and the episode actually was pretty straight forward. No journeys. No reward (with or without a *redacted* country star). Just an immunity challenge and two tribal councils. So, we thought we'd try and keep the recap short. We'll see you next week for the MERGE (?!).P.S. RIP to two of our faves. It was a tough day for Team AgieIf you're looking for a specific segment, here's a breakdown:Intro (0:00-1:44)Initial Thoughts (1:44-14:03)Episode Recap (14:03-41:51)Jeff Needs a Vibe Check (41:51-45:20)Castaway of the Week (45:20-47:29)Rapid Fire (47:29-52:40)Outro (52:40-end)Be sure to give us a follow on Instagram ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠@EscapingRealityPod⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ and on Twitter ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠@EscRealityPod⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ --  If you enjoyed this episode, please subscribe & leave us a rating/review on Apple Podcasts and/or Spotify! Make sure to tell your friends about the pod so they can join you (and us) on our journey through reality competition shows.As always, thanks for listening & thanks for Escaping Reality with us!

Quantum used to be crypto's distant sci-fi problem. Justin Drake says it now has a clock. In this episode, we unpack what “Q-Day” actually means, why Justin thinks 2032 is the date the entire industry should be planning around, and why Ethereum is targeting 2029 to get post-quantum ready. ---

This week hosts Jim DeRogatis and Greg Kot celebrate artists who found a new creative gear decades after they hit the music scene. It's Late-Career Encores, this week on Sound Opinions.Join our Facebook Group: https://bit.ly/3sivr9TBecome a member on Patreon: https://bit.ly/3slWZvcSign up for our newsletter: https://bit.ly/3eEvRnGMake a donation via PayPal: https://bit.ly/3dmt9lUSend us a Voice Memo: Desktop: bit.ly/2RyD5Ah Mobile: sayhi.chat/soundops Featured Songs:Johnny Cash, "Hurt," American IV: The Man Comes Around, American, 2002The Beatles, "With A Little Help From My Friends," Sgt. Pepper's Lonely Hearts Club Band, Parlophone, 1967Johnny Cash, "Folsom Prison Blues," Johnny Cash with His Hot and Blue Guitar!, Sun, 1955Johnny Cash, "The Mercy Seat," American III: Solitary Man, American, 2000Misson of Burma, "Academy Fight Song," Single, Ace of Hearts, 1980Misson of Burma, "2Wice," The Obliterati, Matador, 2006Wire, "1 2 X U," Pink Flag, Harvest, 1977Wire, "Joust & Jostle," Wire, Pinkflag, 2015The Staple Singers, "I'll Take You There," Be Altitude: Respect Yourself, Stax, 1972Mavis Staples, "99 and 1/2," We'll Never Turn Back, Anti-, 2007Superchunk, "Driveway To Driveway," Foolish, Merge, 1994Superchunk, "Me & You & Jackie Mittoo," I Hate Music, Merge, 2013Naked Raygun, "I Don't Know," Throb Throb, Homestead, 1985Naked Raygun, "Living in the Good Times," Over the Overlords, Wax Trax!, 2021A Tribe Called Quest, "Can I Kick It?," People's Instinctive Travels and the Paths of Rhythm, Jive, 1990A Tribe Called Quest, "We the People....," We Got It from Here...Thank You 4 Your Service, Epic, 2016Bonnie Raitt, "Thank You," Bonnie Raitt, Warner Bros., 1971Bonnie Raitt, "The Road's My Middle Name," Nick of Time, Capitol, 1989Cher, "Gypsys, Tramps & Thieves," Chér, Kapp, 1971Cher, "Strong Enough," Believe, WEA and Warner Bros., 1998Redd Kross, "Annie's Gone," Third Eye, Atlantic, 1990Redd Kross, "Candy Coloured Catastophe," Redd Kross, In the Red, 2024Converge, "Concubine," Jane Doe, Equal Vision, 2001Converge, "We Were Never the Same," Love is Not Enough, Epitaph and Deathwish, 2026John Prine, "Angel From Montgomery," John Prine, Atlantic, 1971John Prine, "When I Get to Heaven," The Tree of Forgiveness, Oh Boy, 2018Pulp, "Common People," Different Class, Island, 1995Pulp, "Spike Island," More, Rough Trade, 2025Al Green, "Belle," The Belle Album, Hi, 1977See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Most entrepreneurs believe they need to build everything alone.But the truth is, some of the fastest-growing businesses in the world are built through strategic partnerships and collaboration.In this episode of the Social Proof Podcast, David Shands and Donni Wiggins break down why the most successful entrepreneurs often merge strengths instead of competing.They talk about:• Why solo entrepreneurs grow slower than collaborative teams• The mindset shift required to scale faster• When it makes sense to pivot vs start something new• The hidden power of strategic partnerships• Why some entrepreneurs build generational businesses while others stallIf you're building a business and trying to figure out how to grow faster, this conversation will change how you think about collaboration, content, and scaling.Subscribe for more real conversations with real entrepreneurs on the Social Proof Podcast.Our Sponsors:* Check out Northwest Registered Agent and use my code socialprooffree for a great deal: https://northwestregisteredagent.comAdvertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacy