Podcasts about branching

Database branching has, for a long time, been a troublesome piece in the modern developer workflow puzzle: a good idea in principle but in practice a slow and often expensive challenge. Get it right and you can accelerate productivity and remove bottlenecks; get it wrong and you're potentially creating all sorts of trouble for yourself, from privacy risks to additional complexity. However, things are changing. Thanks to the emergence of new platforms such as Neon, Supabase and Databricks Lakebase, branching a database can become as familiar to developers as managing code branches and multiple environments with, say, Git and Terraform.  On this episode of the Technology Podcast, host Ken Mugrage is joined by his Thoughtworks colleague Cam Casher and Databricks' Kevin Hartman to discuss the work Thoughtworks and Databricks have been doing together on Lakebase. They discuss the platform, their experience using it with Spotify's Backstage and the opportunities database branching can offer software engineering teams in an increasingly AI-assisted and agentic world. Read Cam and Kevin's recent series on using Databricks Lakebase with Backstage: https://www.thoughtworks.com/insights/blog/data-engineering/backstage-lakebase-databricks

Journey Church International is a difference making church in Lees Summit, MO with an exciting kids program, bible-based teaching and an inviting atmosphere.

So, some good news this morning. If in the weekend you noticed the kids have developed conjunctivitis, or you had an unexpectedly good time over the weekend and now need the emergency pill or help with a UTI. Today is the day that changes to the services which pharmacists can provide kicks in, meaning pharmacists will be able to provide funded medicines for pain and fever management for children, oral rehydration, and treatment for conditions such as scabies, head lice, and conjunctivitis, as well as treatment for uncomplicated urinary tract infections and emergency contraception. This is a really sensible move. Instead of waiting for a GP appointment, paying for a GP appointment, or paying over the counter prices for treatments, you can head to your local chemist where your pharmacists will now be funded to provide a consultation, and supply a funded treatment at a low cost. The benefits are obvious – patients can get more affordable care quickly, and close to home, while taking pressure off GPs and emergency departments. Only time will tell us how much this move impacts our overloaded primary care services, but on paper it looks like a win-win-win for pharmacies, GPs and patients. But now it gets a little bit more interesting – and complicated. Associate Health Minister David Seymour has been driving this change, along with the Health Minister Simeon Brown; but Seymour wants to take things further and allow pharmacies to treat more everyday conditions such as chest and ear infections, help manage long-term medication and order routine blood tests when appropriate, and provide skin lesion triage and monitoring. Now, Seymour isn't reinventing the wheel with these ideas – these proposals align with international trends which are seeing healthcare become more of a team effort. But these further proposals will require considerable additional training, strict clinical guidelines for pharmacist to operate under, and GPs will need to retain overall clinical oversight. Most importantly, pharmacists would need to know when to treat and when to refer. It sounds like a logical next step, but one which will require a lot more work to get into action than what is launching today. The management of long-term medications for stable, low-risk patients seems the most easily achievable of the ideas – many pharmacists are already assisting with monitoring, renewals, and support. Extending their responsibilities here could absolutely streamline care, and cost for patients. Branching into diagnosing chest infections or skin cancer would come with greater risks; like inappropriate antibiotic prescribing and missed diagnoses if pharmacist services are not well-regulated and connected to patients' health records. So today's move is a great use of existing health professionals to make the system more efficient and affordable. The next step is going to require careful consideration, and considerable investment to make it work. See omnystudio.com/listener for privacy information.

In this episode, Danielle sits down with Get PAIED client Melissa Eastlick, a 6/2 Emotional Manifestor, child and parent therapist, and founder of Branching with Twigs. Together, they explore what it actually looks like to decondition your wealth codes, trust your authority, and create a business rooted in alignment instead of hustle. Melissa shares how learning to work with her emotional authority, nervous system, inner child, and Manifestor energy has transformed the way she leads her business, supports families, and shows up in the world. They also dive into the deeper layers of entrepreneurship, including emotional safety, visibility, self-trust, identity evolution, and why growth often feels uncomfortable right before expansion happens. This conversation is deeply honest, insightful, and validating for anyone navigating entrepreneurship, emotional authority, deconditioning, or the journey of becoming more fully themselves. In this episode, you'll learn: What it means to decondition your wealth codes and align your business with your natural design How Melissa navigates life and business as a 6/2 Emotional Manifestor Why emotional authority is about awareness, not reacting from emotion How to recognize when your inner child is running the show in business decisions Why self-trust is one of the most important aspects of entrepreneurship The role nervous system safety plays in visibility, success, and growth How Melissa learned to stop over-responding and honor her Manifestor energy The connection between family dynamics, conditioning, and personal evolution Why entrepreneurship constantly reveals new layers of healing and identity work How to hold compassion for yourself while still continuing to grow Why consistency and staying the course matter more than chasing the next dopamine hit The difference between “wanting” energy versus true aligned action How higher self guidance creates grounded, sustainable momentum Why your triggers and emotional reactions are invitations into deeper awareness How Melissa integrates Human Design, nervous system work, and parenting support into her practice   About Melissa Eastlick Melissa Eastlick is the founder of Branching with Twigs, a therapy and coaching practice supporting children, parents, and families through nervous system-informed healing, Human Design, and aligned parenting. As a child and parent therapist, parent coach, and Human Design enthusiast, Melissa helps families understand their unique energetic blueprints so they can create more connection, regulation, joy, and alignment within the home. She is also the creator of Parenting by Design, a program that helps parents better understand themselves and their children through Human Design and embodied parenting practices.   _____________________________________________   Links & Resources Connect with Melissa on Instagram: @branching_with_twigs Visit Melissa's Website: https://www.melissa-eastlick.com Doors to Get PAIED are open Here Download Your Wealth Codes Chart Get the Email Series That Pays  

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

Morphing from racer to coach and why his personality was perfect for the role. The constant thirst for information on how to be a better athlete which gave his academy international acclaim. Branching out and tackling desert enduros as well as memories of Finke in a milestone year for the race. A podium in the Castrol 6-hour - a late circuit racing bloom. Childhood memories of the Sydney Showground Speedway a making the move into Midgets (Speedcars). A 4-wheel title win and a Sprintcar crash which took its toll. Plus the little known Supercars test and the juggle of trying to coach Matt Mladin and James Stewart Stateside. In the midst of a ripper conversation we don’t get to every yarn….like his stunt coordination role on the recent Mad Max Movies - Fury Road and Furiosa for example - but if you find yourself wanting more check out his excellent new book ‘The Stephen Gall Story: No Easy Way’ available for order at www.noeasyway.com.au Head to Rusty's Facebook, Twitter or Instagram and give us your feedback and let us know who you want to hear from on Rusty's Garage.See omnystudio.com/listener for privacy information.

In her message based on 1 Peter 4:8-11, Pastor Jen explores the concept of faith as an outward-moving force. Using the metaphor of a tree, she argues that a healthy spiritual life is not meant to “root-bind” by turning inward, but to branch out to provide shelter, shade, and life to others. The Foundation: Deep […]

Branching off a subscriber-only episode earlier in the week, Josh and Jack dive into the current perception of Matt Rhule and try to figure out what it will take to change people's tune about the fourth-year Husker head coach.0:00 - Intro10:00 - Is Jack cool?23:48 - Would 8-4 be enough for Husker fans?47:00 - What kind of jump can we expect from Anthony Colandrea?Music: Ian AeilloFor more from the I-80 Club, become a Patron and get bonus episodes, access to the I-80 Club Discord server, and so much more: patreon.com/i80clubSubscribe to the I-80 Club YouTube channel and don't miss any of our public episodes, see shorts, and other videos! Hosted on Acast. See acast.com/privacy for more information.

The The Bombpops are a San Diego punk band known for blending fast, melodic riffs with emotionally honest lyrics. Fronted by Jen Razavi and Poli van Dam, their dual vocals give their songs a raw, conversational energy. They gained recognition through releases on Fat Wreck Chords, the iconic label founded by Fat Mike of NOFX. Their music often explores themes like relationships, anxiety, and personal growth while keeping a high-energy punk sound. With catchy hooks and heartfelt storytelling, they've carved out a strong place in modern punk. I got Jen on the Zoom and this is what we chat about: Branching out to be a solo act Using Instagram to get known The San Diego punk scene Red Scare Records How they signed to Fat The limitation of the Punk festivals How do younger bands survive Being able to travel by just playing solo shows How has the sale of Fat effected her Working on the Liquid Death album Her new solo release The Fat Mike Covid house party And a ton more Lastly if you need a freelance Graphic / Motion Designer then hit me up at mike@drive80.com Design support includes: • Branding and visual identity • Marketing and campaign design • Social, print, and digital assets  Video work includes: • Podcast video clips • Short-form content for Reels, Shorts, TikTok, and ads • Long-form edits for interviews, webinars, and YouTube • Sizzle reels and brand videos • Explainer and marketing video edits • Captioning, on-screen text, and light motion graphics If any of this lines up with something you need, feel free to reach out or keep me in mind!

Shady Nattrass returns to the podcast for a long overdue catch up.

In spite of the title of this podcast, we'd have the world know that we aren't just a couple morons who love professional wrestling. We have other interests. We have range. We have thoughts. Granted, they can be few and far in between, but still… where was I? Oh yeah. Branching out and proving we're more than just geeks with an affinity for sports and sports entertainment… we also love sports movies! So we're diving into what I consider one of the most perfect sports flicks to ever grace the silver screen in this, episode 241, Juuuuuuust A Bit Outside – the majesty that is Major League!   FULL VIDEO EPISODES! That's right folks, you can see our bright smiling idiotic faces in full color on our YouTube channel. Full episodes available as well as clips.   ...AND ANOTHER THING: The Man They Call Tim suggests watching "Moneyball" Uncle Todd suggests watching Rustic Overtones live in the gym of Nokomis High School in 1999   FOLLOW US ON THE SOCIAL MEDIAS: Facebook - http://facebook.com/freerangeidiocy Instagram - http://instagram.com/freerangeidiocy YouTube - http://youtube.com/@freerangeidiocy

Why do narcissists seem to move on instantly after a breakup or divorce?In this episode, Sam and Leah break down the psychology behind “monkey branching” — a common narcissistic relationship pattern where someone lines up a new partner before leaving the current relationship. For many women, watching their ex jump into a new relationship immediately can feel deeply personal, confusing, and incredibly painful.But the truth is, this behavior has far more to do with narcissistic supply, control, and avoiding emotional accountability than it does with your worth.Sam and Leah discuss:What monkey branching actually isWhy narcissists rarely stay singleThe role of narcissistic supply and dopamine chasingWhy the new relationship often happens so quicklyHow narcissists rewrite the history of the relationshipWhy this behavior creates trauma bonds and deep confusionHow to stop personalizing their actions and start healingIf you're navigating divorce or co-parenting with a narcissistic ex, understanding these patterns can help you regain clarity, protect your peace, and start rebuilding your life with confidence.If you're looking for deeper support, tools, and community while navigating divorce and high-conflict co-parenting, check out The Next Chapter membership. Inside, we help moms heal, set boundaries, regulate their nervous systems, and rebuild their confidence after toxic relationships.

Send us Fan MailIn this episode, we're talking all about Branching Out, starring Sarah Drew as an architect and single mom on a mission to help her young daughter connect with her roots. Through a surprising journey, they seek out her biological father, played by Juan Pablo di Pace—a musician who never knew he had a daughter. As they navigate the unexpected and emotional path to family, the story beautifully explores themes of identity, belonging, and the bonds that grow in unlikely places.We're split on this one! Some of us were moved by the heartwarming moments, while others had mixed feelings about the story's direction. Tune in as we dive into the film's memorable scenes, unexpected twists, and the ways it resonated with each of us. Support the showThank you for listening to this episode of Love on the Pod!Subscribe, Rate, and Review: Don't miss an episode—subscribe to Love on the Pod on Apple Podcasts, Spotify or your favorite podcast platform. If you enjoyed the episode, please rate and review us!Shop Our Merch: https://www.loveonthepod.com/category/all-productsConnect with Us:Email: loveonthepod@gmail.comInstagram: @LoveOnThePodVisit Our Website: For show notes, episodes and more, visit https://www.loveonthepod.com.Stay tuned for our next episode, where we'll discuss another holiday favorite. See you next time!

Guests: Breanna Beck & Alec McLennan Resources Branching Out on Spotify Canadian Nursery Landscape Association (CNLA) Video version of this episode

The Big Dumb Podcast S1E5 - Super Bowl Ads, Monkey Branching & The Olympic Cheater Who Blew Up His Life - We actually start with a great list of things we watched this week. Then, onto the important part of Super Bowl Sunday. The commercials. Monkey-Branching. What is it? It's a dating thing. We'll explain. We also talk about that Olympic skier who confessed to fooling around on his girl on LIVE TV. 

Send a textIn this week's double feature of Music of the Mountains, we're bringing in Kimmerjae Macarus and Morgan McHugh to talk about their upcoming show at Ned General!The Colorado journey of folk-rock guitarist Morgan McHugh came from expanding his performing reach. Branching from projects he'd been a part of, the Bellingham-born musician brought his original songs and acoustic guitar stylings to perform solo.McHugh began performing in small bars and house concerts, touring throughout Washington, California, and Colorado. The first show he played in Colorado was as part of a house concert series hosted by artist Kimmerjae Macarus, beginning their close musical connection. The two enthusiastically share their mutual admiration. Support the showThank you for listening to The Mountain-Ear Podcast, featuring news and culture from peak to peak! Additional pages are linked below.If you want to be involved in the podcast or paper, contact: Barbara Hardt, our editor-in-chef, at info@themountainear.com Tyler Hickman, podcast host, at tyler@themountainear.com Jamie Lammers, podcast host, at media@themountainear.com General inquiries: frontdesk@themountainear.com Head to our website for all of the latest news. Subscribe online and use the coupon code PODCAST for a 10% discount for all new subscribers. Submit local events to promote them in the paper and on our website. Find us on Facebook @mtnear and Instagram @mtn.ear Listen and watch on YouTube today. Share this podcast by scrolling to the bottom of our website home page or by heading to our main hub on Buzzsprout.Thank you for listening!

Let's examine an alternate timeline that sees the Knights of Takhisis take over, corrupt Dragonlances and raise a flying Citadel from Icewall. Buy Legends of the Twins: https://www.dmsguild.com/en/product/3252/legends-of-the-twins-3-5?affiliate_id=50797  https://youtu.be/7ptaSEFzU0A Transcript Cold Open Winter should never come in summer. But in this timeline, the snow never stopped falling… And the dragonlances themselves became weapons of darkness. Intro Welcome to another DragonLance Saga episode. My name is Adam, and today we're taking a look at one of the alternate timelines found along the River of Time: the War of the Darklance. I'd like to take a moment and thank the DLSaga members and Patreon patrons, and invite you to consider becoming a member or patron–you can even pick up Dragonlance media or get $10 by signing up to StartPlaying.Games using my affiliate links. I'm referencing the Legends of the Twins sourcebook for this information. If I leave anything out or misspeak, please leave a comment below. Discussion The River of Time carries every age, every hero, and every tragedy forward—but it does not flow as a single, unbroken stream. Branching from it are countless tributaries, alternate Krynns shaped by small divergences or catastrophic changes. The War of the Darklance takes place in one such world. Here, the Graygem is never broken. Chaos is never released. Wild Sorcery and Mysticism never emerge. Ambient magic lies dormant, subdued, and tightly controlled. At first glance, this seems like a safer world. But without Chaos to disrupt the fabric of time, the Balance itself becomes rigid—and fragile. When evil learns from its failures and ceases to destroy itself, the result is not equilibrium. It is domination. At the center of this darkness stands Lord Ariakan, son of Ariakas. Unlike the Dragon Highlords of the past, Ariakan does not cling to pride, infighting, or ancient grudges. Instead, he creates something unprecedented: a unified knighthood modeled after the Knights of Solamnia, but devoted wholly to Queen Takhisis. The Knights of Takhisis embrace modern ideals. They wield magic without fear. They integrate warriors, priests, and mages into a single doctrine. And most importantly—evil does not turn against itself. For the first time, the Dark Queen's forces march with discipline, coordination, and purpose. The turning point of the war comes with an act so profane that it scars the world itself. The Knights of Takhisis cannot create weapons of light—but they can corrupt them. Captured dragonlances are brought before a ritual involving three unholy artifacts: the Altar of Takhisis, the Wand of Corruption, and the Hammer of Darkness. Placed upon the obsidian altar, the dragonlances smoke and weaken. The wand suspends them in a field of pure evil, tearing at their magical essence. Finally, the hammer strikes the blade, sealing the transformation. Thus, the darklance is born. These weapons strip the Whitestone forces of their greatest advantage. And the ritual's consequences ripple outward—into the sky, the land, and the seasons themselves. In the year 383 AC, Ansalon enters a nightmare remembered as the Summer of Frost. Temperatures steadily fall throughout spring. By summer, the world freezes. Crops fail. Livestock die. Starvation spreads faster than any army. The sky becomes perpetually overcast. Paladine seems powerless. Even Chislev cannot restore nature's order. Faith begins to crack. And it is in this moment of desperation that the invasion begins. The Knights of Takhisis strike swiftly. Kalaman falls. The Northern Wastes and Nordmaar collapse soon after. At Icewall, the dead Highlord Aren Feal-Thas is reborn as a death knight, cursed and bound to undeath. Icewall Glacier begins moving north—alive, jagged, relentless—guided by Feal-Thas's thoughts and emotions. Floating above it is Icewall Castle, transformed into a flying citadel. White dragons patrol the skies, wielding darklances, while thanoi, sivak draconians, and barbarian tribes march below. Entire villages vanish beneath the ice. As the Blood Sea freezes solid, the minotaurs see their moment. Led by Chot Es-Kalin, they march across the ice toward Ansalon, beginning a brutal campaign of genocide against the ogres. Though larger and stronger, the ogres lack discipline. Battle after battle, the minotaurs advance—until the thaw comes too late for Chot's secondary forces, which plunge into the Maelstrom beneath the melting ice. Chot himself remains stranded on the mainland, facing an ogre counteroffensive with no retreat. The war spares no one. The Qualinesti Forest burns, assaulted by dragons and Thorn Knights. Qualinost is destroyed. Elves flee—some to Ergoth, others east toward Silvanesti, where they are met with resentment and fear. The High Clerist's Tower falls for the first time in history. Tanis Half-Elven and Steel Brightblade die in its defense. Their fallen comrades are buried in mass graves, their names carved into stone. Palanthas surrenders without a fight. The Tower of High Sorcery is destroyed from within as Dalamar the Dark brings it down to prevent the Knights of the Thorn from reaching the portal to the Abyss. Whether Dalamar survives is unknown. Ergoth becomes the last refuge. Overcrowded. Hungry. Diseased. Clerics of Mishakal work tirelessly, overwhelmed by suffering. Gnomes abandon invention for joy and instead build engines of war. Even the kender feel the weight of despair. Yet resistance survives. Merinda uth Brishard leads roving Solamnic knights. Galvan Stonebreaker wages his private war. Underground movements form in Palanthas and Khur. And even within the darkness, evil begins to strain against itself. Aren Feal-Thas seeks to overthrow Ariakan. Mirielle Abrena consolidates her own power. The Blood War threatens Ariakan's eastern flank. The Balance may yet reassert itself.  This timeline has no fixed ending. The Knights of Takhisis have conquered most of Ansalon. Winter still grips the land. Another natural winter is coming. The Heroes of the Lance are gone. Now, the fate of the world rests with new champions—thieves, killers, outcasts, and survivors—people who may have to abandon honor to preserve hope. If the war can be won, the scars will remain. The land will never be the same. And the people of Ansalon will carry this darkness forever. But if the fight is abandoned—then this tributary of the River of Time ends in ice, silence, and shadow. The War of the Darklance is a world where evil learned, adapted, and nearly won. A Krynn where hope is fragile, honor is costly, and the Balance hangs by a thread.  And that makes it one of the most haunting alternate timelines in all of Dragonlance. Outro But that is all the time I have to talk about the Alternate Timeline: War of the Darklance. Do you like the idea of Dragonlance's being corrupted? Can the death Knight Feal-Thas rival Lord Soth? And finally will the Knights of Takhisis ever be overthrown? Leave a comment below. I would like to invite you to subscribe to this YouTube channel, ring the bell to get notified about upcoming videos, and click the like button. It all helps other Dragonlance fans learn about this channel and its content. Thank you for watching — this has been Adam with DragonLance Saga, and until next time, remember: A chap who can point at you and say ‘die' has the distinct advantage.

BPD Sudden Discard of Monkey Branching Crushed FutureMany people who have been in short term or long term relationships with someone with Borderline Personality Disorder experience a BPD sudden discard of monkey branching that just crushes you and all the future plans that you believed were going to be your life unfolding in the relationship with the person with BPD that you didn't know, you didn'ttruly know. The heartbreak, the loss, the shame, the toxic guilt of people with Codependency who for a time blame themselves. BPD sudden Monkey Branching discards add even more pain and confusion to what is experienced in any BPD Breakup. How can you recover from this?https://ajmahari.ca/sessions - Sessionshttps://ajmahari.ca/podcasts - Podcastshttps://ajmahari.com - Online Store new Course Modules coming soonhttps://survivingbpdrelationshipbreakup.com - This podcast and my YoutubeThis podcast is ranked in the Top 100 Relationships Podcasts on feedspot.com at:100 Best Relationship Podcasts You Must Follow in 2025Million Podcasts has ranked this podcast in the top 60 Codependency Podcasts,the top 100 Narcissistic Abuse Podcasts and the top 100 in their Toxic RelationshipPodcast lists.https://www.millionpodcasts.com/codependency-podcasts/https://www.millionpodcasts.com/narcissistic-abuse-podcasts/https://www.millionpodcasts.com/toxic-relationship-podcasts/

In a traumatic twist, Spencer finds himself planning to extricate a patient from... a tree? Does he make the right call? Can he remove this patient from a STICKy situation? Vote now on Instagram!

Jim completes this series and look into the 764 group who uses tactics such as Sextortion to take control of teens in unspeakable ways by using applications such as Discord to groom and exploit the most innocent among us. Chapters03:12 The Branching of 76404:09 Tactics of the Online Network12:41 Understanding 764 Group17:57 Personal Experiences with Doxing21:20 The Nature of Sextortion34:29 The Dark Side of Online Gaming55:00 Shocking Acts of Violence1:00:23 Predatory Behavior on Roblox1:24:23 Brand Army: A Dangerous PlatformFor commercial free early releases, bonus episodes and more! https://www.patreon.com/exposedpodcastfilesBecome a supporter of this podcast: https://www.spreaker.com/podcast/exposed-scandalous-files-of-the-elite--6073723/support.

Mike & Tommy untangle workspace, branching, and artifact chaos, exploring how to organize Fabric environments amid conflicting advice from Microsoft and consultants, and provide a practical framework for managing dev/test/prod workflows without workspace proliferation.Get in touch:Send in your questions or topics you want us to discuss by tweeting to @PowerBITips with the hashtag #empMailbag or submit on the PowerBI.tips Podcast Page.Visit PowerBI.tips: https://powerbi.tips/Watch the episodes live every Tuesday and Thursday morning at 730am CST on YouTube: https://www.youtube.com/powerbitipsSubscribe on Spotify: https://open.spotify.com/show/230fp78XmHHRXTiYICRLVvSubscribe on Apple: https://podcasts.apple.com/us/podcast/explicit-measures-podcast/id1568944083‎Check Out Community Jam: https://jam.powerbi.tipsFollow Mike: https://www.linkedin.com/in/michaelcarlo/Follow Tommy: https://www.linkedin.com/in/tommypuglia/

On The Sal Greco Show episode 139, the NYC Mayoral Race is now in the early voting stages, with a ton of flip flopping, fear mongering, and even former and current NYPD Police Commissioner's chiming in endorsing candidates.Salvatore "Sal" Greco is a Former 14 year New York Police Department (NYPD) veteran, and a Sicilian-American. Being a strict fitness enthusiast, food connoisseur, and cigar aficionado Sal is no stranger to the Good and Evil in our lives. His origin story began with food industry work and a love for how it brought everyone together. DOWNLOAD THE FREESPOKE APP :https://freespoke.app.link/grecoUse promo code : GRECO35 to get 35% off Freespoke PremiumFollow Sal:https://twitter.com/TheSalGrecohttps://www.instagram.com/thesalgrecohttps://tiktok.com/TheSalGrecoShow

Texas: What the Hell? The Lone Star State's government, a wholly-owned corporate subsidiary, solidified its ranking this year as America's #1 innovator of really bad public policies.Branching out from their usual corrupt collusion with Big Oil, industrial polluters, and other profiteering hucksters, the governor and top lawmakers came up with a whole new batch of legalized slick-um, specifically to protect and profit a new Texas stock market for big money dealers. Who needs it? After all, beaucoup markets already exist for speculators and such. Yes – but those markets are at least loosely regulated to protect investors – plus, some states want to tax stock-trading profits.So here come Texas politicos, pushing a cutely-named “Y'all Street” stock exchange, promising that it'll be “speculator friendly.” Friendly means limp regulation, little public disclosure of schemes, and hostility to taxation.For example, to spare rich stock profiteers from paying their share of taxes (like working stiffs do), Republican leaders have graciously acted to prevent state taxation on the massive profits speculators get from selling stocks, bonds, real estate, etc. And, to prove their undying plutocratic love for the rich, lawmakers plan to engrave this special tax break in the Texas Constitution, effectively closing off rich people's ill-gotten gains as a source of revenue for the state's future needs.This Lone Star stock market is a cynical big-government scam to further enrich the privileged few hoping to shift the cost of basic public services away from those most able to pay onto the backs of workaday families. If you wonder how inequality happens, study the Texas example. And hurry – the right-wing intends to bring it to your state next.Jim Hightower's Lowdown is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber. This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit jimhightower.substack.com/subscribe

ChatGPT Shortcuts for WritersYou don't need more content; you need smarter systems to reuse what you've already created.In this podcast episode, I'm sharing five practical ChatGPT shortcuts that help me write faster, stay organized, and spark fresh ideas from existing content.These are the exact methods I use when writing my book and producing weekly assets for my business.Whether you're a coach, speaker, service provider, or author, you'll walk away with time-saving ways to turn scattered ideas into polished, purpose-driven content.ChatGPT can become a creative collaborator without losing your voice in the process. What You'll Discover in This Episode:Why your creative "mess" isn't a problem, it's a content goldmineHow ChatGPT's "Branching" feature lets you work on multiple assets at the same time!The hidden shortcut to search your own content library inside ChatGPTHow "Canvas" mode helps you edit content directly in ChatGPTA repeatable workflow to repurpose an article into a podcast, newsletters, YouTube videos, and more.How to organize your ChatGPT threads with "Projects."The command that reveals every ChatGPT shortcut availableYour Next Step: AI Lab for SolopreneursFeeling like content creation for marketing takes too much time?That's why I created AI Lab for Solopreneurs, a private membership where you can learn, implement, and grow with AI in real time.Live Coaching & Demos: Monthly hands-on sessions to learn AI strategies that fit your business goals.Resource Library: Access a growing collection of guides and templates you can use right away.Custom GPTs: Exclusive access to ready-to-use AI assistants that save time and improve content quality.24/7 Support: Get your questions answered anytime inside the private community.Join AI Lab for Solopreneurs today and lock in your $37/month founding rate before it increases.Let's turn complexity into simplicity—together.Community.MarisaShadrick.comDon't Know How to Leave a Review? CLICK HERE for a quick tutorial or this link: https://youtu.be/n-yEygX1Te4?si=z-ytPFqrB957NZG0Skip Hours of Prompt Trial & Error with ChatGPTWhether you're writing, planning, analyzing, or brainstorming, my C.O.N.T.E.X.T. ™ method transforms ChatGPT into a consistent marketing assistant. No steep learning curve.Free Download!https://marisashadrick.com/prompts If you're ready to grow with effective marketing that actually feels manageable, here's your next move.Inside AI Lab for Solopreneurs, get Custom GPTs, templates, and coaching to grow your business. Join now at https://community.marisashadrick.com/Listen to the "Amplify Your Authority" Podcast! Click Here! Rate & Review: If you enjoyed this episode, please take a moment to leave a 5-star rating and review on Apple Podcasts. Tip: Answer these questions inside of ChatGPT (free or paid) and have AI craft your review! How did you discover this podcast? What's your biggest takeaway from this episode? How has this podcast helped your current journey? Thanks so much for taking a few minutes to craft a review!

This week's episode is in conversation with the insanely talented Shereen Cutkelvin. Pursuing a career in music from a very young age, Shereen's innate talent and passion for music, inspired by her father who was a professional singer, saw her signed to the hugely successful band Neon Jungle, before going on to reach the semi finals of The XFactor with her brothers as The Cutkelvins. Branching out in to acting and presenting, Shereen now cohosts the CBBC's Saturday Mash-up! and is a presenter on BBC Introducing for BBC Radio Scotland, alongside a whole host of other creative projects. With extensive experience as an actor including starring in Irvine Welsh's CRIME, Shereen is a highly skilled and gifted artist and performer who goes after the things that make her soul sing! Braw and indeed brave in every way! Follow Shereen on insta: https://www.instagram.com/shereencutty?igsh=aHdrazdpd3lkbzQy This episode is sponsored by: Creative Spark Theatre Arts A community arts charity based in Kirkintilloch striving to use the arts to connect empower everyone within their local area. www.creativesparktheatrearts.co.uk Socials- TikTok- https://www.tiktok.com/@creativesparktheatrearts?_t=ZN-90LdRhWwhcc&_r=1 Insta- https://www.instagram.com/creativesparkta?igsh=MTlrcHQ4YmM2czJnbw== Follow The Braw and The Brave Website: https://www.thebrawandthebrave.com/ YouTube: https://www.youtube.com/@TheBrawandTheBrave TikTok: https://www.tiktok.com/@thebrawandthebrave Instagram: https://www.instagram.com/thebrawandthebravepodcast/ Facebook: https://www.facebook.com/TheBrawandTheBrave

Мок-интервью для junior/начинающего middle DevOps: CI/CD, Git-ветки, AWS (VPC, S3), Kubernetes (probes, DaemonSet), Terraform. Разбираем основы, типовые вопросы и ошибки — простым языком.

ADZG 1252 ADZG Sunday Morning Dharma Talk by Rev. Hōgetsu Laurie Belzer The post Dragons report on the Branching Streams Gathering first appeared on Ancient Dragon Zen Gate.

Send us a textYou're using ChatGPT all wrong.Until now, using ChatGPT meant endless copying and pasting between your apps. A newly released feature, MCP connectors, shatters those limitations, transforming ChatGPT into a super agent that can connect to nearly any application, service, or website. This allows it to access information, talk to your apps, and take action anywhere, fundamentally changing how you work.In this episode, we'll show you exactly how to set it up, even if you're not a technical person. You'll discover: 

One of the best things about creativity is that it truly is without limits. We can see this in a variety of places, like in the worlds of film and literature. TV shows and movies will have spinoffs, sequels, and prequels—and novels do the same. For some writers, what starts as a single novel branches out until it becomes a 12-book series, plus a collection of short stories, a prequel trilogy, and more. That's what creativity does when the ideas are full of life and allowed to flourish. And as much as we might roll our eyes at the sequel movies in theaters that feel more like an attempt to get us to spend on tickets rather than a legitimate expansion to the story, this is a good thing when our projects take on a life of their own such that they branch out in a variety of ways... Podcast Notes: https://www.moneymakerphotography.com/branching-projects-and-spinoffs/ Photography Clips Podcast: https://www.moneymakerphotography.com/podcast/ Follow me: https://www.facebook.com/Will.Moneymaker  #PhotographyClips #WillMoneymaker #Photography

Join hosts Tim Wood and our very own Willem as they dive into the thrilling world of branching narratives in game development. Discover how stories come alive in every twist and turn and what it really takes to craft unforgettable, dynamic adventures.Learn more about usJoin the next episode of the Indie Game Lunch Hour LIVE every Wednesday at 12pm EST on our Discord channel to answer your own burning questions and be immortalized in the recordings.

Discover how to build a vibrant digital church community that thrives beyond traditional walls in this inspiring episode of the MyCom Church Communications and Marketing Podcast! Host Ryan Dunn sits down with Erin Beasley and Sean Stanfield to unpack the story behind The Vine United Methodist Church, a digital United Methodist faith community born out of disaffiliation. Whether you're starting an online ministry, seeking fresh discipleship strategies, or looking to deepen authentic connections in a digital world, this episode is packed with practical wisdom, innovation, and hope for the future of church communications. Connect with The Vine: https://www.thevineumc.church/ ⏰ CHAPTERS 00:00 – Introduction: Reimagining Church After Disaffiliation 01:45 – The Origin of The Vine: Meeting a Real Need 04:14 – Going Global: Leveraging Social Media for Outreach 06:08 – Creative Content: Short Sermons, Podcasts, & Tough Topics 08:59 – Building Community: Engaging Feedback & Discipleship Pathways 11:53 – Online Communion: Creating Sacred Moments Virtually 16:40 – From Viewers to Disciples: Inviting Deeper Connection 18:38 – Vulnerability Online: Why Digital Spaces Foster Openness 21:06 – Branch Groups & ‘Branch Managers': Small Group Strategies 23:10 – Digital Church Planting Models: From Branches to Congregations 26:18 – Hot Topics: Church Hurt, Justice, and Connecting the Margins 29:30 – Lessons Learned & Advice for Aspiring Digital Ministers 33:37 – What's Next for The Vine? Dreams and Missional Expansion 38:06 – Social Media Tactics: Growth on TikTok & Instagram 41:09 – Key Takeaways & Episode Close This episode brought to us by: RootedGood.org Cokesbury.com/Call-Response

Beamer is once again in for Bauerle and today, we lead things off with John Di Sciullo of WBBZ to talk about Nexstar's $6.2 billion acquisition of rival Tegna, and the local implications of that move. Branching off of that, how to you take in your news, and watch TV in general in 2025, are you a cable person, subscription, etc? Also, we talk about the fallout from yesterday's Amherst Town Board meeting on the Westwood Country Club, and preview tomorrow's star studded show in honor of National Radio Day.

Send us a textIn this INbetween episode, host Mighty Fine provides some insight into the upcoming "Virtual" Safe States Annual Conference which will be held September 9-11, 2025 online using the Whova app. Participants can expect an agenda packed full of sessions, activities, networking opportunities, gameification and so much more. Listen in to hear Mighty share some of the details about the agenda and activities planned for the upcoming Safe States conference and if you haven't registered, please visit www.safestates.org to get signed up!

Josh Letchworth has worked with some of the biggest celebrities and brands out there, but before he broke into these other industries he was regarded as one of the best wakeboard photographers to pick up a camera. Josh got a later start than some other photographers, not really diving deep into photography until after college, where he began shooting live music. His journey progressed from live events into wakeboarding, where he built a career off of telling stories through his images. Gaining self confidence, negotiating retainers, having the lab mess up your photos on a shoot for Fox, working with Nike, breaking the rules, and what makes a photo “good”. Hear all that and much more in Episode 92 of the Grab Matters Podcast with Josh Letchworth!Follow Josh: https://www.instagram.com/joshletchworth/Thank you to this shows sponsors! Liquid Force: https://www.liquidforce.com/ Slingshot: https://slingshotsports.com/Chapters:00:00 - 1:20 Intro1:40 Summer 20256:00 Early Life and Photography 10:50 Post college life15:00 Intro to wakeboarding20:00 Getting paid to photograph25:00 Guest Question: Rodrigo Donoso32:10 Guest Question: Ben Greenwood33:00 Negotiating a retainer with Quicksilver 41:40 LF'n Wheel of Questions47:30 Branching out from wakeboarding 56:00 Working with Nike1:02:20 Slingshot Silhouette Challenge 1:08:20 What makes a photo good?1:14:00 Not getting the photo1:18:00 Breaking the “rules”1:25:45 Changing media landscape/AI1:29:50 Guest Question: Chase Heavener 1:38:00 Working with celebrities 1:41:10 Mt. Rushmore of Wake photographers 1:45:20 Guest Question: Garrett Cortese1:58:00 Camera Setup2:06:10 Guest Question: Jeff McKee2:12:30 Thank you'sLinks:Detty: https://www.instagram.com/dettymarie/Guest Questions:Rodrigo Donoso: https://www.instagram.com/rodrigosnaps/Benny G: https://www.instagram.com/bennygrrr/Chase Heavener: https://www.instagram.com/chaseheavener/Garrett Cortese: https://www.instagram.com/garrettcortese/Jeff McKee: https://www.instagram.com/jeffmckee/Shoot us a text!Patreon: https://www.patreon.com/GrabMattersPodcastWebsite: https://www.grabmatters.com/YouTube: https://www.youtube.com/@grabmatters/videosInstagram: https://www.instagram.com/grabmatters/TikTok: https://www.tiktok.com/@grabmatterspodcastFacebook: https://www.facebook.com/grabmatters

Vir Das lost his voice just six weeks before he had to film his new Netflix special 'Fool Volume', and on this week's episode of 'Good One' he walks us through how Adele's doctor helped bring him back, facing legal consequences for his work, and how much better it actually is to be an Indian comedian. 00:00 Intro00:01:23 Funniest thing of the week00:03:06 Starting stand-up in Mumbai00:06:23 Being an Indian comic00:07:54 Branching out globally00:15:24 Losing his voice00:23:19 Making the special00:30:28 Legal controversy00:34:47 Protecting fellow comics00:36:02 The magazine profile he didn't do00:38:53 Making comedy with legal risk00:43:55 His performing style00:50:23 The Laughening Round Learn more about your ad choices. Visit podcastchoices.com/adchoices

Want a bushier houseplant? Here are some scientifically proven tips for branching, plus info about light, holding off on repotting a plant, and more! For soil and other incredible houseplant supplies, check out ohhappyplants.shop!

Mike & Tommy are joined one last time by Mathias as they talk technical process and strategy.Get in touch:Send in your questions or topics you want us to discuss by tweeting to @PowerBITips with the hashtag #empMailbag or submit on the PowerBI.tips Podcast Page.Visit PowerBI.tips: https://powerbi.tips/Watch the episodes live every Tuesday and Thursday morning at 730am CST on YouTube: https://www.youtube.com/powerbitipsSubscribe on Spotify: https://open.spotify.com/show/230fp78XmHHRXTiYICRLVvSubscribe on Apple: https://podcasts.apple.com/us/podcast/explicit-measures-podcast/id1568944083‎Check Out Community Jam: https://jam.powerbi.tipsFollow Mike: https://www.linkedin.com/in/michaelcarlo/Follow Seth: https://www.linkedin.com/in/seth-bauer/Follow Tommy: https://www.linkedin.com/in/tommypuglia/

In this laid-back and laughter-filled episode of Y-Chromes, CannCon, Alpha Warrior, and Cam Cooksey let loose for an evening of sharp takes, light roasting, and reflections on modern masculinity. The crew opens with Cam's recent guest spot on “Flow” and a hilarious behind-the-scenes tale from Alpha's church visit, before diving into social dynamics, both online and off. They tackle the concept of “monkey branching” in relationships, breaking down the psychology behind people who swing from one partner to another, and reflect on whether women or men are more likely to ghost or grieve after a breakup. Cam provides insight from the female perspective, sparking some honest and hilarious debate. The guys also wade into the wild world of internet drama, including recent events in the influencer space, with plenty of sarcasm and no fear of stepping on toes. From beer preferences to relationship red flags, this episode delivers a fun, unfiltered conversation that blends humor with real talk. Whether you're sipping something strong or just hanging out, this is a perfect dose of Friday night guy talk with a purpose.

Glen speaks with Georgia State University Finance Professor Jonathan Godbey about new student-led consumer research that yields some unexpected findings about Gen Z banking attitudes. Plus- Circle's IPO is roundly celebrated, Illinois kicks the interchange can down the road, and the AI Easter Egg hiding in the Big Beautiful Bill.          Links related to this episode: The Georgia Fintech Academy: https://georgiafintechacademy.org/ The Technology Association of Georgia's Fintech Ecosystem Report: https://www.tagonline.org/wp-content/uploads/2025/04/2025-Fintech-Ecosystem-Report.pdf Fintech South- in Atlanta August 19-20: https://www.fintechsouth.com/ Contact Georgia State Finance Professor Jonathan Godbey at jgodbey@gsu.edu Payments Dive's coverage of Illinois' Interchange Fee Prohibition Act extension: https://www.paymentsdive.com/news/illinois-legislature-delays-interchange-fee-ban-law/749526/ Circle's IPO: https://finance.yahoo.com/news/circle-stock-surges-15-extends-gains-for-third-day-in-a-row-since-blockbuster-ipo-153657180.html The Senate alters the House budget provision curtailing states' ability to regulate AI: https://rollcall.com/2025/06/05/ai-regulation-moratorium-dropped-in-senate-budget-package/   Join us for our next CU Town Hall- Wednesday June 11 at 3pm ET/Noon PT- for a live and lively interactive conversation tackling the major issues facing credit unions today. Industry developments keep coming fast and furious- the CU Town Hall is the place to make sense of these items together. It's free to attend, but advance registration is required:  https://www.cutownhall.com/   Join us on Bluesky!   @bigfintech.bsky.social @154advisors.bsky.social (Glen) @jbfintech.bsky.social (John) And connect on LinkedIn for insights like the Friday Fintech Five: https://www.linkedin.com/company/best-innovation-group/  https://www.linkedin.com/in/jbfintech/ https://www.linkedin.com/in/glensarvady/

Feeling more confident about finding the right reads is a common bookish goal. In today's conversation, Anne welcomes Tynisha Coleman to the show to talk about her current reading goals. Tynisha is a leadership development coach, university lecturer, and sci-fi and fantasy lover from New Jersey. She doesn't shy away from books that tackle tough plot points, which often feature in the emotionally resonant books she loves. But she does expect these trickier developments to serve a sense of purpose to the plot, and she'd like to avoid reading experiences that send her into the depths of despair. Right now, Tynisha is looking for titles that offer a sense of escapism, both in her current preferred genres, and while also keeping open to other works she'll enjoy. Anne has a bunch of ideas to share. Find the list of titles mentioned in today's episode at our show notes page, at whatshouldireadnextpodcast.com/480. We kicked off summer reading season with our 14th annual Summer Reading Guide and Live Unboxing just a few weeks ago. If you missed the launch, you can still get your copy of the digital Guide and the video replay from our Unboxing party by visiting modernmrsdarcy.com/srg. Learn more about your ad choices. Visit megaphone.fm/adchoices

More info: https://docs.anthropic.com/en/docs/claude-code/overviewThe AI coding wars have now split across four battlegrounds:1. AI IDEs: with two leading startups in Windsurf ($3B acq. by OpenAI) and Cursor ($9B valuation) and a sea of competition behind them (like Cline, Github Copilot, etc).2. Vibe coding platforms: Bolt.new, Lovable, v0, etc. all experiencing fast growth and getting to the tens of millions of revenue in months.3. The teammate agents: Devin, Cosine, etc. Simply give them a task, and they will get back to you with a full PR (with mixed results)4. The cli-based agents: after Aider's initial success, we are now seeing many other alternatives including two from the main labs: OpenAI Codex and Claude Code. The main draw is that 1) they are composable 2) they are pay as you go based on tokens used.Since we covered all three of the first categories, today's guests are Boris and Cat, the lead engineer and PM for Claude Code. If you only take one thing away from this episode, it's this piece from Boris: Claude Code is not a product as much as it's a Unix utility.This fits very well with Anthropic's product principle: “do the simple thing first.” Whether it's the memory implementation (a markdown file that gets auto-loaded) or the approach to prompt summarization (just ask Claude to summarize), they always pick the smallest building blocks that are useful, understandable, and extensible. Even major features like planning (“/think”) and memory (#tags in markdown) fit the same idea of having text I/O as the core interface. This is very similar to the original UNIX design philosophy:Claude Code is also the most direct way to consume Sonnet for coding, rather than going through all the hidden prompting and optimization than the other products do. You will feel that right away, as the average spend per user is $6/day on Claude Code compared to $20/mo for Cursor, for example. Apparently, there are some engineers inside of Anthropic that have spent >$1,000 in one day!If you're building AI developer tools, there's also a lot of alpha on how to design a cli tool, interactive vs non-interactive modes, and how to balance feature creation. Enjoy!Full Video EpisodeTimestamps[00:00:00] Intro[00:01:59] Origins of Claude Code[00:04:32] Anthropic's Product Philosophy[00:07:38] What should go into Claude Code?[00:09:26] Claude.md and Memory Simplification[00:10:07] Claude Code vs Aider[00:11:23] Parallel Workflows and Unix Utility Philosophy[00:12:51] Cost considerations and pricing model[00:14:51] Key Features Shipped Since Launch[00:16:28] Claude Code writes 80% of Claude Code[00:18:01] Custom Slash Commands and MCP Integration[00:21:08] Terminal UX and Technical Stack[00:27:11] Code Review and Semantic Linting[00:28:33] Non-Interactive Mode and Automation[00:36:09] Engineering Productivity Metrics[00:37:47] Balancing Feature Creation and Maintenance[00:41:59] Memory and the Future of Context[00:50:10] Sandboxing, Branching, and Agent Planning[01:01:43] Future roadmap[01:11:00] Why Anthropic Excels at Developer Tools Get full access to Latent.Space at www.latent.space/subscribe

More info: https://docs.anthropic.com/en/docs/claude-code/overview The AI coding wars have now split across four battlegrounds: 1. AI IDEs: with two leading startups in Windsurf ($3B acq. by OpenAI) and Cursor ($9B valuation) and a sea of competition behind them (like Cline, Github Copilot, etc). 2. Vibe coding platforms: Bolt.new, Lovable, v0, etc. all experiencing fast growth and getting to the tens of millions of revenue in months. 3. The teammate agents: Devin, Cosine, etc. Simply give them a task, and they will get back to you with a full PR (with mixed results) 4. The cli-based agents: after Aider's initial success, we are now seeing many other alternatives including two from the main labs: OpenAI Codex and Claude Code. The main draw is that 1) they are composable 2) they are pay as you go based on tokens used. Since we covered all three of the first categories, today's guests are Boris and Cat, the lead engineer and PM for Claude Code. If you only take one thing away from this episode, it's this piece from Boris: Claude Code is not a product as much as it's a Unix utility. This fits very well with Anthropic's product principle: “do the simple thing first.” Whether it's the memory implementation (a markdown file that gets auto-loaded) or the approach to prompt summarization (just ask Claude to summarize), they always pick the smallest building blocks that are useful, understandable, and extensible. Even major features like planning (“/think”) and memory (#tags in markdown) fit the same idea of having text I/O as the core interface. This is very similar to the original UNIX design philosophy: Claude Code is also the most direct way to consume Sonnet for coding, rather than going through all the hidden prompting and optimization than the other products do. You will feel that right away, as the average spend per user is $6/day on Claude Code compared to $20/mo for Cursor, for example. Apparently, there are some engineers inside of Anthropic that have spent >$1,000 in one day! If you're building AI developer tools, there's also a lot of alpha on how to design a cli tool, interactive vs non-interactive modes, and how to balance feature creation. Enjoy! Timestamps [00:00:00] Intro [00:01:59] Origins of Claude Code [00:04:32] Anthropic's Product Philosophy [00:07:38] What should go into Claude Code? [00:09:26] Claude.md and Memory Simplification [00:10:07] Claude Code vs Aider [00:11:23] Parallel Workflows and Unix Utility Philosophy [00:12:51] Cost considerations and pricing model [00:14:51] Key Features Shipped Since Launch [00:16:28] Claude Code writes 80% of Claude Code [00:18:01] Custom Slash Commands and MCP Integration [00:21:08] Terminal UX and Technical Stack [00:27:11] Code Review and Semantic Linting [00:28:33] Non-Interactive Mode and Automation [00:36:09] Engineering Productivity Metrics [00:37:47] Balancing Feature Creation and Maintenance [00:41:59] Memory and the Future of Context [00:50:10] Sandboxing, Branching, and Agent Planning [01:01:43] Future roadmap [01:11:00] Why Anthropic Excels at Developer Tools

Rapunzel, Rapunzel! Let down your golden hairrr….conditioning secrets!

She thinks its really weird how her current boyfriend still has his ex-girlfriend on his Netflix account and refuses to delete her off his account. Will we catch another cheater with War of the Roses? Listen back to the follow up conversation on demand now!

She thinks its really weird how her current boyfriend still has his ex-girlfriend on his Netflix account and refuses to delete her off his account. Will we catch another cheater with War of the Roses?

In this episode, I, Stewart Alsop III, sat down with AJ Beckner to walk through how non-technical founders can build a deeper understanding of their codebase using AI tools like Cursor and Claude. We explored the reality of navigating an IDE as a beginner, demystified Git and GitHub version control, and walked through practical ways to clone a repo, open it safely in Cursor, and start asking questions about your app's structure and functionality without breaking anything. AJ shared his curiosity about finding specific text in his app and how to track that down across branches. We also looked at using AI-powered tools for tasks like dependency analysis and visualizing app architecture, with a focus on empowering non-devs to gain confidence and clarity in their product's code. You can connect with AJ through Twitter at @thisistheaj.Check out this GPT we trained on the conversation!Timestamps00:00 – Stewart introduces Cursor as a fork of Visual Studio Code and explains the concept of an IDE to AJ, who has zero prior experience. They talk about the complexity of coding and the importance of developer curiosity.05:00 – They walk through cloning a GitHub repository using the git clone command. Stewart highlights that AJ won't break anything and introduces the idea of a local playground for exploration.10:00 – Stewart explains Git vs GitHub, the purpose of version control, and how to use the terminal for navigation. They begin setting up the project in Cursor using the terminal rather than GUI options.15:00 – They realize only a README was cloned, leading to a discussion about branches—specifically the difference between main and development branches—and how to clone the right one.20:00 – Using git fetch, they get access to the development branch. Stewart explains how to disconnect from Git safely to avoid pushing changes.25:00 – AJ and Stewart begin exploring Cursor's AI features, including the chat interface. Stewart encourages AJ to start asking natural-language questions about the app structure.30:00 – Stewart demonstrates how to ask for a dependency analysis and create mermaid diagrams for visualizing how app modules are connected.35:00 – They begin identifying specific UI components, including finding and editing the home screen title. AJ uploads a screenshot to use as reference in Cursor.40:00 – They successfully trace the UI text to an index.tsx file and discuss the layout's dependency structure. AJ learns how to use search and command-F effectively.45:00 – They begin troubleshooting issues with Claude's GitHub integration, exploring Claude MCP servers and configuration files to fix broken tools.50:00 – Stewart guides AJ through using npm to install missing packages, explains what Node Package Manager is, and reflects on the interconnected nature of modern development.55:00 – Final troubleshooting steps and next steps. Stewart suggests bringing in Phil for deeper debugging. AJ reflects on how empowered he now feels navigating the codebase.Key InsightsYou don't need to be a developer to understand your app's codebase: AJ Beckner starts the session with zero familiarity with IDEs, but through Stewart's guidance, he begins navigating Cursor and GitHub confidently. The key idea is that non-technical founders can develop real intuition about their code—enough to communicate better with developers, find what they need, and build trust with the systems behind their product.Cursor makes AI-native development accessible to beginners: One of the biggest unlocks in this episode is seeing how Cursor, a VS Code fork with AI baked in, can answer questions about your codebase in plain English. By cloning the GitHub repo and indexing it, AJ is able to ask, “Where do I change this text in the app?” and get direct, actionable guidance. Stewart points out that this shifts the role of a founder from passively waiting on answers to actively exploring and editing.Version control doesn't have to be scary—with the right framing: Git and GitHub come across as overwhelming to many non-engineers, but Stewart breaks it down simply: Git is the local system that helps keep changes organized and non-destructive, and GitHub is the cloud-based sharing tool layered on top. Together, they allow safe experimentation, like cloning a development branch and disconnecting it from the main repo to create a playground environment.Branching strategies reflect how work gets done behind the scenes: The episode includes a moment of discovery: AJ cloned the main branch and only got a README. Stewart explains that the real work often lives in a “development” branch, while “main” is kept stable for production. Understanding this distinction helps AJ (and listeners) know where to look when trying to understand how features are actually being built and tested.Command line basics give you superpowers: Rather than relying solely on visual tools, Stewart introduces AJ to the terminal—explaining simple commands like cd, git clone, and git fetch—and emphasizes that the terminal has been the backbone of developer work for decades. It's empowering to learn that you can use just a few lines of text to download and explore an entire app.Modern coding is less about code and more about managing complexity: A recurring theme in the conversation is the sheer number of dependencies, frameworks, and configuration files that make up any modern app. Stewart compares this to a reflection of modern life—interconnected and layered. Understanding this complexity (rather than being defeated by it) becomes a mindset that AJ embraces as part of becoming technically fluent.AI will keep lowering the bar to entry, but learning fundamentals still matters: Stewart shares how internal OpenAI coding models went from being some of the worst performers two years ago to now ranking among the top 50 in the world. While this progress promises an easier future for non-devs, Stewart emphasizes the value of understanding what's happening under the hood. Tools like Claude and Cursor are incredibly powerful, but knowing what they're doing—and when to be skeptical—is still key.

Allan Weitz had little idea of the grand photographic adventures in store when he signed on as host of the B&H Photography Podcast shortly before the show's debut in October 2015. As a self-described big mouth, and with more than 40 years as a working pro fueling his curiosity about all things photographic, Allan quickly honed his chops to become the voice of the show. Today's episode marks a crossroads, as Allan passes his hosting mic to the show's incoming host, Derek Fahsbender, producer and host of the B&H Event Space. During a lively chat, we celebrate Allan's long and successful career, both on assignment and at the helm of the podcast, with some never before told stories and audio clips from memorable interactions with guests. A few of the many topics we cover include, how a kid from Sheepshead Bay made a name for himself photographing classic yachts, the ways in which Allan's time behind a New Jersey deli counter enhanced his ability to engage with people on a human level—among other benefits to career reinvention—and how his shift into podcasting taught him to use his voice as an instrument. As Allan aptly summarized for attendees of the podcast team's 2018 presentation of Podcasting 101: “It's not always what you say, but how you say it.” Guest: Allan Weitz Episode Timeline  3:38: Allan's B&H Event Space segment from Podcasting 101. 8:35: The back story to Allan's one-word podcast intro “Greetings!” 10:44: Allan's chat with digital camera inventor Steve Sasson about their shared Brooklyn roots.  13:56: Allan's hosting skills as a court jester—or Tummler in Yiddish. 16:12: Gear talk, and a clip from Allan's chat with Bellamy Hunt of The Japan Camera Hunter. 21:19: Allan waxes poetic about his love for the Hasselblad Superwide, plus his early adoption of digital gear.  28:24: Branching out from commercial assignments to tech writing and other things. 38:18: Episode break 39:27: Memorable stories and life lessons from Allan's assignment career. 44:22: Allan's entrée to the world of yachting photography and portfolio tips. 50:44: Allan's career evolution in the rarified 1980s photography landscape. 57:31: The art of the interview and the value of collaboration among the podcast team.  59:53: Getting beyond difficult pictures during an interview with Bruce Gilden  1:03:50: Upcoming plans and Allan's Kodachrome book project. 1:10:31: Allan offers listeners his Tusen Takks for their trust in his time behind the mic.  Guest Bio: Allan Weitz started taking pictures when digital meant doing something with your fingers. A graduate of New York City's High School of Art and Design and the School of Visual Arts, Allan is the founding host of the B&H Photography Podcast, one of the highest-rated photography podcasts in Apple's Creative Arts category.  For more than 50 years, Allan's photographs have graced the covers and inside pages of dozens of publications, including New York magazine, Esquire, GQ, Yachting, and Nautical Quarterly. Many of these images have won him awards from the New York, Philadelphia, and New Jersey Art Directors Clubs, the Graphic Artists Guild, Art Direction Magazine, Print, and Graphis, among others.  More recently, Allan has had great success exhibiting—and winning awards for—his photos as fine art prints, as well as dabbling with artificial intelligence using the traditional photos from his vast image library as source material.  Stay Connected: Allan Weitz Website: https://www.allanweitz.com/ Allan Weitz Instagram: https://www.instagram.com/allanweitz/ Allan Weitz articles on the B&H Explora Blog: https://www.bhphotovideo.com/explora/users/allan-weitz Podcasting 101 with the B&H Photography Podcast Team: https://www.youtube.com/watch?v=Yd2KDaNSjGI Steve Sasson Podcast Episode: https://www.bhphotovideo.com/explora/podcasts/photography/invention-of-digital-camera Japan Camera Hunter Podcast Episode: https://www.bhphotovideo.com/explora/podcasts/photography/podcast-the-japan-camera-hunter Graham Nash Podcast Episode: https://www.bhphotovideo.com/explora/podcasts/photography/graham-nash-ace-photographer-digital-printing-pioneer-music-legend-the-bh Bruce Gilden Podcast Episode: https://www.bhphotovideo.com/explora/podcasts/photography/closer-look-bruce-gilden End Credits: Founding Host: Allan Weitz Incoming Host: Derek Fahsbender Senior Creative Producer: Jill Waterman Senior Technical Producer: Mike Weinstein Executive Producer: Richard Stevens

In this highly anticipated episode, we sit down with bonsai artist Sergio Cuan, whose work has become a major source of inspiration in the bonsai world. Following his incredible journey over the years, it's clear Sergio's career is only gaining momentum, and there's so much more to come. Join us as we dive into the nuances of his bonsai practice, explore his growth as an artist, and unpack the exciting developments in his work. This conversation starts strong and doesn't let up, brimming with insights and inspiration for bonsai enthusiasts and art lovers alike.   Learn more about Sergio's work here.    Also: Learn more about the Battle of the Bonsai Clubs and sign up here! Start your 7-day free trial of Mirai Mobile and explore all it has to offer!  

In today's episode, we are joined by Dr. Andrew L. Hipp, the Director of the Herbarium and Senior Scientist in Plant Systematics at The Morton Arboretum. With a Ph.D. in Botany from the University of Wisconsin-Madison, Dr. Hipp got into plant work as a way to work outdoors. Now, more than 20 years later, he has a lab that focuses on various aspects of plant biodiversity – with a strong focus on phylogenetics. Using molecular systematics, genomics, community ecology, and herbarium study, the Arboretum's Hipp Lab's current research, which includes oaks, sedges, and the use of phylogenetic and trait diversity, is not just theoretical. It is informing practical questions in ecological restoration and community ecology, making a tangible impact on the world we live in… Listen in to find out:  The history of oak tree development and diversity.  How oaks are most typically used.  Where evolutionary history and ecology intersect.  A common misconception about tree roots.  To follow along with Dr. Hipp's work at the Arboretum's Hipp Lab, click here now. And keep an eye out for his upcoming book, Oak Origins: From Acorns to Species and the Tree of Life, set to be published in December! Episode also available on Apple Podcasts: http://apple.co/30PvU9

Aman Sanger, Arvid Lunnemark, Michael Truell, and Sualeh Asif are creators of Cursor, a popular code editor that specializes in AI-assisted programming. Thank you for listening ❤ Check out our sponsors: https://lexfridman.com/sponsors/ep447-sc See below for timestamps, transcript, and to give feedback, submit questions, contact Lex, etc. Transcript: https://lexfridman.com/cursor-team-transcript CONTACT LEX: Feedback - give feedback to Lex: https://lexfridman.com/survey AMA - submit questions, videos or call-in: https://lexfridman.com/ama Hiring - join our team: https://lexfridman.com/hiring Other - other ways to get in touch: https://lexfridman.com/contact EPISODE LINKS: Cursor Website: https://cursor.com Cursor on X: https://x.com/cursor_ai Anysphere Website: https://anysphere.inc/ Aman's X: https://x.com/amanrsanger Aman's Website: https://amansanger.com/ Arvid's X: https://x.com/ArVID220u Arvid's Website: https://arvid.xyz/ Michael's Website: https://mntruell.com/ Michael's LinkedIn: https://bit.ly/3zIDkPN Sualeh's X: https://x.com/sualehasif996 Sualeh's Website: https://sualehasif.me/ SPONSORS: To support this podcast, check out our sponsors & get discounts: Encord: AI tooling for annotation & data management. Go to https://encord.com/lex MasterClass: Online classes from world-class experts. Go to https://masterclass.com/lexpod Shopify: Sell stuff online. Go to https://shopify.com/lex NetSuite: Business management software. Go to http://netsuite.com/lex AG1: All-in-one daily nutrition drinks. Go to https://drinkag1.com/lex OUTLINE: (00:00) - Introduction (09:25) - Code editor basics (11:35) - GitHub Copilot (18:53) - Cursor (25:20) - Cursor Tab (31:35) - Code diff (39:46) - ML details (45:20) - GPT vs Claude (51:54) - Prompt engineering (59:20) - AI agents (1:13:18) - Running code in background (1:17:57) - Debugging (1:23:25) - Dangerous code (1:34:35) - Branching file systems (1:37:47) - Scaling challenges (1:51:58) - Context (1:57:05) - OpenAI o1 (2:08:27) - Synthetic data (2:12:14) - RLHF vs RLAIF (2:14:01) - Fields Medal for AI (2:16:43) - Scaling laws (2:25:32) - The future of programming PODCAST LINKS: - Podcast Website: https://lexfridman.com/podcast - Apple Podcasts: https://apple.co/2lwqZIr - Spotify: https://spoti.fi/2nEwCF8 - RSS: https://lexfridman.com/feed/podcast/ - Podcast Playlist: https://www.youtube.com/playlist?list=PLrAXtmErZgOdP_8GztsuKi9nrraNbKKp4 - Clips Channel: https://www.youtube.com/lexclips