Podcasts about roadmaps

Learn what a realistic three-year IT roadmap looks like for small to mid-size businesses: a living business plan, not a static wishlist.FIT's Becky Cross and Fred Franks outline three drivers for roadmap priorities: strategic initiatives, productivity improvements, and compliance/risk needs—so technology supports business goals instead of chasing “shiny objects."Fred discusses how pacing should match an organization's appetite for change to avoid fatigue, how to handle executive conflict by returning to a shared vision and commitments, and why three-year plans should be held loosely while 12-month plans are firmer for budgeting. They also cover measuring success through agreed outcomes and ROI, celebrating wins, and how “security first, mobile first” planning enabled continuity during the pandemic.

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

This Sunday, we'll explore one of the most common questions Christians ask: What does God want me to do? We often want a detailed roadmap for the future, but God offers something better—a relationship with Him. Join us as we discover that calling is less about knowing every step ahead and more about becoming the person God has called us to be and trusting Him with the next faithful step.

ThunderCast, the official Thunderbird podcast is back for another season! In this episode we focus on the contributor journey, analyzing what we currently have and what are our plans to improve jumping into the Thunderbird community.Roadmaps: https://roadmaps.thunderbird.net/Developer guides: https://developer.thunderbird.net/Ideas for Thunderbird desktop and mobile: https://connect.mozilla.org/User support for Thunderbird desktop and mobile: https://support.mozilla.org/Submit your questions at podcast@thunderbird.net ★ Support this podcast ★

In dieser Folge sprechen Anja Schneider, verantwortlich für Customer Engagement und Adoption in Mittel- und Osteuropa bei SAP, und Christina Lehmann, Strategieberaterin mit Fokus auf Finanzt Transformation, über das SAP Business Transformation Framework (BTF) – und darüber, wie sich komplexe Veränderungsvorhaben gestalten lassen.Im Mittelpunkt steht die Frage, wie sich Transformation steuern und in messbaren Geschäftswert überführen lässt. Das BTF bündelt dafür strategische Zielbilder, operative Steuerungsinstrumente und Change-Aspekte in einem modularen Ansatz, der Fragmentierung reduziert, Transparenz schafft und Transformationsvorhaben zum Erfolg führt.Transformation gelingt, wenn sie tief mit der Unternehmensstrategie abgestimmt ist – und wenn Technologie gezielt eingesetzt wird, um diese Strategie zum Leben zu erwecken. Anja Schneider hebt disziplinierte Umsetzung, gemeinsame Entscheidungsfindung und starke Governance als die Schlüssel zu schnelleren Entscheidungen, weniger Reibung und dauerhaftem Vertrauen hervor.Christina Lehmann erläutert zudem die sieben Bausteine des Frameworks – von Roadmaps und KPIs bis zu Change-Analysen – und grenzt es von SAP Activate ab. Ergänzend geben beide Einblicke in die praktische Anwendung, etwa in Business Transformation Labs. Auch aktuelle Themen wie Generative KI, Governance und End-to-End-Orchestrierung werden eingeordnet. Transformation bleibt ein Dauerbrenner und ist zugleich aktueller denn je. Ein passender Anlass, dieses Thema in der 400. Folge aufzugreifen

Roadmaps for pediatric artificial intelligence (AI)! Nabile Safdar, MD, and Alex Towbin, MD, speak with host, Raisa Amiruddin, MBBS, about the sore spots, unsung wins, and potential targets of AI in children's healthcare while highlighting how the specialist's intuition remains the ultimate anchor for automated tools in radiology. 

Heading into deposition prep, your clients are typically nervous, anxious, overwhelmed and lacking confidence.   They are most likely in a situation they have never found themselves in before, and undoubtedly the stakes feel very high.   But we need to get them to focus, to remember, to think and answer clearly, and to let go of their fear and uncertainty.   This episodes focuses on three clear, distinct strategies that also help you remember how to get the most out of your clients at this crucial juncture. Clients will feed off of not just your confidence, but your calm demeanor and encouragement.   Elevate your practice with these insights for building a strong foundation in witness preparation. We tap into some fascinating brain science to help us all understand not just what to do, but why our brains, and therefore our emotions, function the way they do.   In this episode, learn how: Your working memory holds only three to five things at a time. Fear can block rational thought and memory retention. Using clear language and expectations supports and empowers clients. Roadmaps help clients understand their roles in depositions. Repetition is key to overcoming the forgetting curve. Role-playing scenarios help your client feel comfortable and confident during deposition. Links from this episode: Learn more about Hermann Ebbinghaus' Forgetting Curve (via growthengineering.co.uk) You can also watch today's episode on my YouTube Channel: Improve Your Clients' Memory and Confidence With These 3 Techniques [Ep 163] Follow and Review: We'd love for you to follow us if you haven't yet. Click that purple '+' in the top right corner of your Apple Podcasts app. We'd love it even more if you could drop a review or 5-star rating over on Apple Podcasts. Simply select "Ratings and Reviews" and "Write a Review" then a quick line with your favorite part of the episode. It only takes a second and it helps spread the word about the podcast.   Have a trial or mediation coming up and want to test with a focus group? Book a free consultation call with Elizabeth to learn more: www.calendly.com/elizabethlarrick Don't miss out on the Trial Lawyer Prep Newsletter that is delivered right to your email with extra tips and 'how to' information. Join the newsletter here: www.larricklawfirm.com/connect

In dieser Episode spreche ich mit Susanne Zach, Partner / AI & Data Lead bei EY.Wir sprechen über folgende Themen:Warum viele AI-Projekte in Unternehmen bei technischer Machbarkeit enden, aber nicht in echte Wirkung übersetzt werdenWie du AI-Projekte so aufsetzt, dass aus ersten Use Cases messbarer Business Value entstehtWarum User Adoption bei AI-Projekten oft wichtiger ist als der nächste Proof of ConceptWelche Rolle Datenbasis, Data Governance und AI-ready Data für erfolgreiche AI-Projekte spielenWie Unternehmen AI-Projekte priorisieren, um schnelle Erfolge und langfristige Skalierung zu verbindenWarum AI Governance kein Bremsklotz sein muss, sondern die Grundlage für skalierbare KI-Initiativen istWie Change Management und Enablement entscheiden, ob GenAI im Alltag wirklich genutzt wirdWelche Fehler Unternehmen bei AI-Projekten rund um POCs und fehlende Roadmaps immer wieder machenWie aus AI-Projekten mit klarer Vision, Skills und Operating Model nachhaltige Transformation entstehtWas Unternehmen tun müssen, damit AI-Projekte nicht nur Innovation zeigen, sondern Produktivität, Effizienz und Wirkung liefernPodcast-Moderator: Christoph PacherLinkedInInterviewgast: Susanne Zach, Partner / AI & Data Lead bei EY.LinkedIn

Elias Lieberich, Founder of Product Matters and formerly a PM at Google and YouTube, makes the case that the real gap between European and Silicon Valley product practice is in its culture. He identifies three recurring patterns in European companies: process obsession, a limited appetite for validation, and an underappreciation of engineering and design. Drawing on work with German Mittelstand businesses, deep tech startups, and large enterprises, Elias explains how to introduce product thinking without triggering resistance, through small, visible wins rather than wholesale transformation.Chapters00:56 – Elias's background: Google, YouTube, and Google X04:08 – European vs. Silicon Valley product culture07:43 – Three gaps: process obsession, lack of validation, undervaluing engineers12:04 – What European companies actually want — and the copy-paste trap13:34 – Show, don't tell: finding immediate value15:37 – Bringing the whole organisation on the journey25:02 – Roadmaps, frameworks, and meeting companies where they are26:35 – Building trust through small, compounding wins29:29 – Change aversion as a bell curve31:02 – What European companies do well — and what's worth exporting33:13 – Working with deep tech startups in Europe36:44 – The killer question: who is this for?40:25 – Practical advice: start with what's within your control42:53 – Wrap-upOur HostsLily Smith enjoys working as a consultant product manager with early-stage and growing startups and as a mentor to other product managers. She's currently Chief Product Officer at BBC Maestro, and has spent 13 years in the tech industry working with startups in the SaaS and mobile space. She's worked on a diverse range of products – leading the product teams through discovery, prototyping, testing and delivery. Lily also founded ProductTank Bristol and runs ProductCamp in Bristol and Bath.Randy Silver is a Leadership & Product Coach and Consultant. He gets teams unstuck, helping you to supercharge your results. Randy's held interim CPO and Leadership roles at scale-ups and SMEs, advised start-ups, and been Head of Product at HSBC and Sainsbury's. He participated in Silicon Valley Product Group's Coaching the Coaches forum, and speaks frequently at conferences and events. You can join one of communities he runs for CPOs (CPO Circles), Product Managers (Product In the {A}ether) and Product Coaches. He's the author of What Do We Do Now? A Product Manager's Guide to Strategy in the Time of COVID-19. A recovering music journalist and editor, Randy also launched Amazon's music stores in the US & UK.

India's greenhouse gas emissions in the hard-to-abate and power sectors are expected to rise in the decades to come, necessitating an examination of strategies deployed for energy transition in these crucial segments. Though steps have been initiated to help reduce emissions, a bespoke, sector-specific decarbonization roadmap over a multi-year timeframe can help guide this journey. Join Amit Sharma, managing director & chief executive officer at Tata Consulting Engineers, Ashish Singla, director for South Asia power and renewables research at S&P Global Energy and Ruchira Singh, editor, energy transition at S&P Global Energy, in a discussion about the requirements for India's industrial decarbonization. 

ThunderCast, the official Thunderbird podcast is back for another season! Let's kick things off with some insights on our roadmaps and what's ahead for our desktop and email clients.User testing discussions: https://thunderbird.topicbox.com/Roadmaps: https://roadmaps.thunderbird.net/Developer guides: https://developer.thunderbird.net/Ideas for Thunderbird desktop and mobile: https://connect.mozilla.org/User support for Thunderbird desktop and mobile: https://support.mozilla.org/Submit your questions at podcast@thunderbird.net ★ Support this podcast ★

Welcome back to another episode of Bubba (@bdentrek) and the Bloom (@RyanBHQ). On BATB 328, the guys begin to put the finishing touches on draft season by breaking down the hitting roadmap for draft day. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

The Transformation Ground Control podcast covers a number of topics important to digital and business transformation. This episode covers the following topics and interviews:   What ERP Vendor Roadmaps Reveal About AI in 2026, Q&A (Darian Chwialkowski, Third Stage Consulting) How Customers Are Taking Back Control of Their Technology Roadmap (Eric Helmer, Rimini Street) Why Some ECC Customers Are Being Told to Spend Over $100M on S/4HANA We also cover a number of other relevant topics related to digital and business transformation throughout the show.  

AMDG. Standardized testing is often a miserable experience, but it doesn't have to be. Student Services Director Karen Allgood and Lower Elementary Department Chair Christina Davin reveal the testing opportunities for lower grade levels and discuss the powerful benefits of testing early and often. In addition, the duo shares practical advice about how to talk to your child in a way that builds confidence rather than anxiety. With Karen and Christina's advice, choosing the right test for your child is easy.  Links mentioned & relevant:  Kolbe Academy testing services  Standardized testing article in Kolbe's Help Center  Homeschool Legal Defense Association (HSLDA) with information about testing requirements by state  State Educational Funding information from Kolbe Academy website  Getting started at Kolbe Academy  Related Kolbecast episodes:  197 Tools in a Toolbox and 269 Resources and Road Maps with Karen Allgood about Kolbe Academy's student support services  182 Festive Holidays Ahead and 189 Fit Mind, Fit Body with Christina Davin  296 Tips for Testing Success   83 This Is Only a Test  38 Substance Matters with Jeremy Tate, founder of the Classic Learning Test (CLT)  143 Partners in a Liberal Arts Renewal with CLT's Soren Schwab  127 Forging a Path with CLT's Kimberly Farley (now VP of Operations)  Have questions or suggestions for future episodes or a story of your own experience that you'd like to share? We'd love to hear from you! Send your thoughts to podcast@kolbe.org and be a part of the Kolbecast odyssey.   We'd be grateful for your feedback! Please share your thoughts with us via this Kolbecast survey!  The Kolbecast is available on Apple Podcasts, Spotify, and most podcast apps. By leaving a rating and review in your podcast app of choice, you can help the Kolbecast reach more listeners. The Kolbecast is also on Kolbe's YouTube channel (audio only with subtitles).  Using the filters on our website, you can sort through the episodes to find just what you're looking for. However you listen, spread the word about the Kolbecast! 

[SPONSORED] Health IT roadmaps used to span years. Now they are collapsing into months. The question many leaders are asking is whether vendors can actually keep up.In this interview, David Cohen, Chief Product and Technology Officer at Greenway Health, explains why the pace of change in healthcare has outgrown traditional multi-year planning cycles. He shares how Greenway is shifting to shorter delivery timelines to stay aligned with what ambulatory practices need right now, using provider–payer data exchange as a clear example of where faster execution matters.The conversation also touches on why manual workflows are becoming harder to justify, how expectations around delivery speed have changed, and what healthcare IT leaders should listen for when vendors talk about their roadmaps.How have shorter timelines changed what you expect from your technology partners?Where do you feel the most pressure to move faster?

All views are my own, not Anthropic's. This post assumes Anthropic's announcement of RSP v3.0 as background. Today, Anthropic released its Responsible Scaling Policy 3.0. The official announcement discusses the high-level thinking behind it. This is a more detailed post giving my own takes on the update. First, the big picture: I expect some people will be upset about the move away from a “hard commitments”/”binding ourselves to the mast” vibe. (Anthropic has always had the ability to revise the RSP, and we've always had language in there specifically flagging that we might revise away key commitments in a situation where other AI developers aren't adhering to similar commitments. But it's been easy to get the impression that the RSP is “binding ourselves to the mast” and committing to unilaterally pause AI development and deployment under some conditions, and Anthropic is responsible for that.) I take significant responsibility for this change. I have been pushing for this change for about a year now, and have led the way in developing the new RSP. I am in favor of nearly everything about the changes we're making. I am excited about the Roadmap, the Risk Reports, the move toward external [...] ---Outline:(05:32) How it started: the original goals of RSPs(11:25) How its going: the good and the bad(11:51) A note on my general orientation toward this topic(14:56) Goal 1: forcing functions for improved risk mitigations(15:02) A partial success story: robustness to jailbreaks for particular uses of concern, in line with the ASL-3 deployment standard(18:24) A mixed success/failure story: impact on information security(20:42) ASL-4 and ASL-5 prep: the wrong incentives(25:00) When forcing functions do and dont work well(27:52) Goal 2 (testbed for practices and policies that can feed into regulation)(29:24) Goal 3 (working toward consensus and common knowledge about AI risks and potential mitigations)(30:59) RSP v3s attempt to amplify the good and reduce the bad(36:01) Do these benefits apply only to the most safety-oriented companies?(37:40) A revised, but not overturned, vision for RSPs(39:08) Q&A(39:10) On the move away from implied unilateral commitments(39:15) Is RSP v3 proactively sending a race-to-the-bottom signal? Why be the first company to explicitly abandon the high ambition for achieving low levels of risk?(40:34) How sure are you that a voluntary industry-wide pause cant happen? Are you worried about signaling that youll be the first to defect in a prisoners dilemma?(42:03) How sure are you that you cant actually sprint to achieve the level of information security, alignment science understanding, and deployment safeguards needed to make arbitrarily powerful AI systems low-risk?(43:49) What message will this change send to regulators? Will it make ambitious regulation less likely by making companies commitments to low risk look less serious?(45:10) Why did you have to do this now - couldnt you have waited until the last possible moment to make this change, in case the more ambitious risk mitigations ended up working out?(46:03) Could you have drafted the new RSP, then waited until you had to invoke your escape clause and introduced it then? Or introduced the new RSP as what we will do if we invoke our escape clause?(47:29) The new Risk Reports and Roadmap are nice, but couldnt you have put them out without also making the key revision of moving away from unilateral commitments?(48:26) Why isnt a unilateral pause a good idea? It could be a big credible signal of danger, which could lead to policy action.(49:37) Could a unilateral pause ever be a good idea? Why not commit to a unilateral pause in cases where it would be a good idea?(50:31) Why didnt you communicate about the change differently? Im worried that the way you framed this will cause audience X to take away message Y.(51:53) Why dont Anthropics and your communications about this have a more alarmed and/or disappointed vibe? I reluctantly concede that this revision makes sense on the merits, but Im sad about it. Arent you?(53:19) On other components of the new RSP(53:24) The new RSPs commitments related to competitors seem vague and weak. Could you add more and/or strengthen these? They dont seem sufficient as-is to provide strong assurance against a prisoners dilemma world where each relevant company wishes it could be more careful, but rushes due to pressure from others.(55:29) Why is external review only required at an extreme capability level? Why not just require it now?(58:06) The new commitments are mostly about Risk Reports and Roadmap - what stops companies from just making these really perfunctory?(59:18) Why isnt the RSP more adversarially designed such that once a company adopts it, it will improve their practices even if nobody at the company values safety at all?(01:00:18) What are the consequences of missing your Roadmap commitments? If they arent dire, will anyone care about them?(01:00:29) OK, but does that apply to other companies too? How will Roadmaps force other companies to get things done?(01:00:40) Why arent the recommendations for industry-wide safety more specific? Why is it built around safety cases instead of ASLs with specific lists of needed risk mitigations?(01:02:06) What is the point of making commitments if you can revise them anytime? --- First published: February 24th, 2026 Source: https://forum.effectivealtruism.org/posts/DGZNAGL2FNJfftwgE/responsible-scaling-policy-v3-1 --- Narrated by TYPE III AUDIO.

In this episode of Between Product and Partnerships, Biljana Pecelj joins Cristina Flaschen to explain how smaller teams successfully ship integrations with larger platform partners. She makes the case that leveraging usage data and performance metrics is the key to proving your integration's value, giving you the necessary influence to move up a major partner's priority list.Biljana shares lessons from her experience managing integrations at Hootsuite during major platform shifts, including the rise of Instagram Business APIs and the emergence of new features like Stories that didn't always come with immediate API support. She also details the process of aligning internal stakeholders to ensure integration features actually ship despite shifting external APIs.The conversation also covers the operational side of integrations, this includes why observability needs to be built early, how teams detect silent failures before customers do, and how to structure internal alignment when integration work touches engineering, legal, partnerships, and revenue.Who we sat down withBiljana Pecelj is a Principal Product Manager at Ledgy with deep experience building integrations inside platform-heavy environments. She has worked extensively on partnership-driven product initiatives where execution speed depends on navigating both technical constraints and external partner relationships.Biljana brings expertise in:Building integrations in environments where APIs and features evolve asynchronouslyDesigning for observability and proactive monitoringNavigating asymmetric partner relationshipsAligning roadmap priorities across product, partnerships, legal, and engineeringManaging tradeoffs between beta opportunities and engineering capacityKey TopicsWhy integration product work is relationship workTechnical execution matters, but alignment with partners determines whether integrations actually ship and scale.Building in ecosystems you don't controlAPIs change. Features launch without endpoints. Roadmaps shift. Successful teams anticipate uncertainty rather than assume stability.The importance of observability from day oneSilent failures are common in integrations. Without monitoring, teams often learn about outages from customers instead of systems.Roadmap tradeoffs when beta opportunities ariseNew partner features can require immediate shifts in engineering priorities. Negotiation and resource reallocation become core product skills.M&A and integration complexityBrand consolidation rarely means backend integration. Teams often inherit layered systems that remain technically independent long after acquisition.Episode Highlights01:55 – How integration product management differs from core product work04:40 – Navigating power imbalances with large platform partners07:15 – Using data to strengthen partner conversations10:30 – Building observability when resources are limited13:45 – Handling silent integration failures17:50 – Managing beta features and roadmap shifts21:30 – Aligning cross-functional teams around integration priorities24:45 – Why relationships accelerate integration execution28:10 – Lessons learned from building inside platform ecosystems--For more insights on partnerships, ecosystems, and integrations, visit www.pandium.com

In this episode I'm joined by Jim Morris.  We chat about the wake-up call that pushed him from building first to testing first. Jim and I discuss loyalty programs no one wanted, roadmaps filled with sequenced risk, AI prototypes that hallucinate and the uncomfortable reality that confidence often replaces evidence.We also dig into something deeper: why smart teams ignore data, why leaders fall in love once an idea hits the roadmap, and why testing isn't about better UX,  it's about real value.Jim shares how he even tests his own teaching process for students at Berkeley.Because as he puts it:“We can build stuff. But if people don't use it, we're just creating product debt.”Enjoy my conversation with Jim Morris.TakeawaysTesting is crucial to ensure product effectiveness and user engagement.Data analysis can reveal the true usage of product features.Mindset plays a significant role in how product ideas are perceived and developed.Not all ideas will succeed; testing helps identify the viable ones.User motivation is key to the success of features and programs.Prototyping tools can enhance the testing process but require careful implementation.Learning from failures in testing is essential for growth and improvement.Roadmaps should be flexible to adapt to changing priorities and evidence.It's important to focus on the core value proposition of a product.Continuous experimentation and adaptation are vital in product management.Guest LinksWebsite: https://productdiscoverygroup.com/LinkedIn Profile: https://www.linkedin.com/in/jimmorrisstanford/ If your leadership team is about to make a big strategic bet, the real risk usually isn't the idea, it's the assumptions behind it that haven't been surfaced yet. A Decision Sprint is a focused 6–12 week engagement where we extract, map, and test those risks so leaders can make a clear Commit, Correct, or Cut decision before major capital moves. Learn more or apply at precoil.com.

Summary In this episode of Means of Grace, John Yeager explores the significance of Lent and its evolution over the years, emphasizing the importance of reflection and spiritual growth. He is joined by Reverend Dr. In-Yong Lee, who shares her experiences as a district superintendent and the challenges faced by church leaders today. The conversation delves into the practices of Lent, including fasting, prayer, and giving, and discusses the recent regionalization within the United Methodist Church, highlighting the need for community support during these challenging times. Show Note: Quietly Courageous by Gil Rendle   Chapters 00:00 Understanding Lent: A Journey of Reflection 02:57 The Role of Leadership in the Church 03:58 Navigating Challenges in Ministry 07:00 The Importance of Connection and Community 09:42 Practices of Faith: Prayer, Fasting, and Giving 12:51 The Essence of Fasting and Its Spiritual Significance 17:38 Tithing: Balancing Generosity and Responsibility 24:57 The Role of Wealth in Generosity 28:14 Understanding Regionalization in the UMC 36:01 Clergy Exhaustion and Community Support 44:43 Embracing Change During Lent 46:47 MOG-Like and Subscribe

The Developer to CEO transition rarely starts with a bold declaration like, "I'm going to run a company." More often, it begins quietly—by taking on one more responsibility, saying yes to a new opportunity, or stepping into a role that stretches just a little beyond your comfort zone. In this episode of the Building Better Developers podcast, part of our Forward Momentum season, we talk with Meeky Hwang about how that transition unfolds in real life. Her path—from developer to agency founder and CEO—reflects a pattern many experienced engineers recognize only in hindsight. Over time, those small decisions add up. You stop thinking only about code and start thinking about people, clients, sustainability, and direction. At some point, you realize you're no longer just building software—you're building a business. About Meeky Hwang Meeky Hwang's journey resonates with entrepreneurs, technical leaders, and anyone navigating the intersection of technology and business. As CEO and Co-Founder of Ndevr, a digital solutions development agency, Meeky brings over 20 years of experience building resilient, scalable platforms for organizations including Johnson & Johnson, Pfizer, Forbes, PMC, and Bloomberg. Her work goes beyond website development—she focuses on long-term digital solutions that improve performance, streamline workflows, and align technology with business strategy. Equally important is Meeky's perspective as a woman leading in a male-dominated industry. She has navigated the challenges of technical leadership, entrepreneurship, and scaling a services business while building credibility and strong teams along the way. Her experience offers an honest look at what it takes to grow as a leader without losing sight of innovation, people, or purpose. Follow on LinkedIn and her Website. Developer to CEO transition starts with "accidental" opportunities For many engineers, this transition begins almost by accident. A consulting role exposes you to different industries. A startup forces you to wear multiple hats. An agency environment teaches you how delivery, relationships, and trust intersect. None of these roles comes with a "future CEO" label. But they do build instincts—how to prioritize, how to adapt, and how to make tradeoffs when perfect solutions aren't possible. Those instincts matter far more than a perfectly mapped career plan. Developer to CEO transition lessons from consulting, startups, and agencies Each environment contributes something different to the Developer to CEO transition. Consulting sharpens communication and expectation-setting. Startups teach ownership and resilience. Agencies reveal what it takes to scale work without burning people out. Individually, these roles can feel chaotic. Together, they form a foundation that prepares developers for leadership long before they realize that's where they're headed. Developer to CEO transition and the mindset shift to full responsibility There's a moment in the transition when responsibility feels heavier. Decisions don't stop at your team or your sprint—they ripple outward. Hiring, pricing, client relationships, and long-term viability all land on your plate. Problems are no longer theoretical. They're personal. This shift changes how leaders think. It forces clarity, prioritization, and the ability to move forward without perfect information. Developer to CEO transition accelerators: mastermind and founder groups One of the most impactful accelerators in the Developer to CEO transition is joining founder communities earlier than you think you need them. Mastermind ROI for New Owners Real conversations about hiring, benefits, pricing, and mistakes Exposure to how other founders actually run their businesses Founder groups shorten the learning curve by replacing isolation with shared experience. Instead of guessing, you learn from people who've already been there. Developer to CEO transition accountability: learning faster through peers Accountability is often underestimated in the Developer to CEO transition. Founder groups create a rhythm of progress—not through pressure, but through shared momentum. The "Accidental" Path That Works Follow opportunities that increase learning, not just status Optimize early for exposure and experience, not polish When you know you'll report back to peers who care, progress stops being optional. Developer to CEO transition when your role forces personal growth The Developer to CEO transition also reshapes how leaders show up. Many founders start as quiet contributors, comfortable behind the scenes. Leadership changes that. Mindset Shifts in the Developer to CEO transition Responsibility changes how decisions feel—and how quickly they must be made Visibility and communication become part of the job Growth here isn't about changing who you are. It's about growing into what the role requires. Developer to CEO transition and evolving the agency niche over time As companies mature, the Developer to CEO transition continues through strategic evolution. Niches tighten, then expand. Focus shifts based on market feedback, strengths, and timing. The most successful agencies don't chase trends. They adjust deliberately, guided by experience rather than impulse. Developer to CEO transition: what to do earlier if you could restart Ask founders what they'd change, and many give the same answer: find peer support sooner. The Developer to CEO transition becomes clearer—and far less lonely—when you're not navigating it in isolation. This episode of the Building Better Developers podcast is a reminder that growth doesn't come from having all the answers. It comes from asking better questions, learning from others, and building momentum—one decision at a time. Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources Maintaining Momentum And Steady Progress Consistency And Momentum: Keys To Success New Year, New Momentum: What Developers Can Look Forward to in 2026 Habits, Roadmaps, and the Value of Career Momentum Building Better Foundations Podcast Videos – With Bonus Content

This the Safety Culture Excellence® podcast, hosted by Shawn Galloway, CEO of ProAct Safety.    This week's podcast reminds us about the importance of "Roadmaps." What visual representations do you have for safety?  https://proactsafety.com/blog-posts/roadmaps      Enjoy the podcast!   Shawn M. Galloway   Your planned path to safety excellence requires a known starting point. 

This episode dives into the controversy surrounding Ryan Dancey leaving AEG over generative artificial intelligence, the sudden hiatus of PaizoCon 2026, and a looming legal refund war over US board game tariffs. Listeners will also get the latest on the 2026 roadmap for D&D Beyond, a major event management merger forming Galactic Events Studio, Netflix's new film adaptation of Ticket to Ride, and how Surbrook Press builds encyclopaedic roleplaying game worlds. About Audio EXP Audio EXP is Geek Native's podcast. Each week, there's some favourite or exciting geeky news, conventions, interviews, and thought pieces. The average length of the podcast is around 10 minutes. You will find a transcript of this week's podcast and links to the stories mentioned here: https://www.geeknative.com/226118/audio-exp-podcast-322-tariffs-tech-roadmaps-and-tic-tac-toe/

Fathom was built on the assumption that transcription would become commoditized and generative models would steadily improve. Rather than training proprietary models, Richard focused on building the infrastructure around them and waiting for model capabilities to reach the right threshold.In this conversation, he explains why AI has made effort and impact harder to predict, and why that shifts product development from roadmap execution toward experimentation. He describes separating an exploratory AI team from core engineering, structuring that team to prototype and write specs, and expecting a meaningful portion of experiments not to work.Richard introduces his Jenga model for AI development, testing different models and use cases to find where resistance is lowest. He also discusses the operational realities of rapid model updates, hallucination rates, and what he calls the LLM treadmill.The discussion explores qualitative QA, organizational design, buy versus build decisions, and why leadership taste plays an increasingly important role as AI lowers the barrier to generating outputs.Key takeaways: Estimating effort and impact is becoming harderAs model capabilities improve quickly, features that require months today may take far less time in the near future. This makes traditional planning assumptions less stable.Product development increasingly resembles R&DWith shifting capabilities and uncertain outcomes, teams must experiment, prototype, and iterate rather than rely solely on long term roadmaps.Organizational structure must reflect experimentationSeparating exploratory AI work from core engineering can allow faster iteration while maintaining stability elsewhere.Rapid model updates create operational pressureFrequent improvements and changing performance levels can require teams to revisit and adjust features more often than in traditional software cycles.Qualitative judgment plays a larger roleAs AI lowers the cost of generating outputs, evaluating quality and deciding what to ship becomes increasingly important.Fathom: fathom.aiFathom LinkedIn: linkedin/company/fathom-video/Richard's LinkedIn: linkedin/in/rrwhite/00:00 Intro: Why AI Breaks Roadmaps00:19 Meet Richard White (Fathom AI)02:16 From Roadmaps to R&D04:49 Designing AI Teams for Speed07:11 The Jenga Model09:56 Failing 50% & AI Team Psychology13:40 LLMs as Interns & Anti-Planning21:01 QA, Data Pain & Developing Taste24:59 Executive Taste & Culture Rules27:20 Reacting to AI Waves28:50 Fathom's 4-Step Product Plan30:47 What New Models Unlock32:13 From Scribe to Second Brain40:32 Build vs Buy in AI45:32 The Debrief

In dieser Folge spricht Norman Müller mit Prof. Dr. Andreas Moring und Andreas Schmidt darüber, warum KI im Mittelstand zwar überall getestet wird, aber selten in echte Wirkung kommt. Im Mittelpunkt stehen die Fragen nach Verantwortung, Roadmaps, Change Management und dem Sprung von Tool-Spielerei zu echter Transformation. Es geht um Geschwindigkeit, Mut und die unbequemen Wahrheiten, die Unternehmen 2026 nicht mehr wegmoderieren können.Link zum IHK-Zertifikatslehrgang "AI Leadership & Change Manager"https://venture-ai-germany.org/ai-leadership-and-change-manager-200:00 Technischer Start und Begrüßung00:28 Warum KI im Mittelstand in Piloten stecken bleibt04:02 Hype, Realismus und der Druck durch Wettbewerb05:10 KI ist nicht gleich Chat-Abo, Definition von KI-Projekten06:12 Orientierungsphase oder Vermeidung, was bremst wirklich06:40 Wildwuchs im Unternehmen und AI Literacy als Pflicht09:59 Roadmap, Zielbild und Botschafter in der Organisation13:02 Wer trägt Verantwortung für KI im Unternehmen15:08 KI ist kein IT-Thema, Verantwortung liegt in den Fachbereichen17:13 Paradigmenwechsel, Business muss Use Cases treiben20:20 KI als universelle Technologie statt Tooldenken21:14 Raupe oder Schmetterling, Transformation vs Optimierung26:33 Generalisten, Zusammenarbeit und kollaborative Intelligenz30:14 Was passiert, wenn Unternehmen KI verpassen35:07 Disruption, Geschwindigkeit und warum Abwarten gefährlich ist39:23 Agenten, Robotik und die exponentielle Entwicklung41:14 Mut, Vertrauen und KI als Booster der Erfahrung45:25 Praxisfokus des Lehrgangs AI Leadership and Change Manager46:12 Unbequeme Wahrheiten, Change-Schmerz und Datenhausaufgaben47:51 Verantwortung, Risiken und Kontrollfragen rund um KI50:45 Ausblick, nächster Lehrgang und VerabschiedungWenn du uns dabei unterstützen möchtest, diesen Podcast zu einer Allianz von Zukunftsarchitekten der KI-Transformation zu machen, in der wir offen über Chancen, Risiken und reale Erfahrungen mit Künstlicher Intelligenz sprechen, dann abonniere uns auf YouTube, Spotify oder Apple Podcasts. Dein Abonnement kostet dich nichts, hilft uns aber sehr, noch mehr herausragende Persönlichkeiten für tiefgehende und inspirierende Podcast Gespräche zu gewinnen. Vielen Dank für deinen Support.Darüber hinaus laden wir dich ein, Teil der Plattform des Bundesverbands für KI-Transformation e.V. zu werden. Hier vernetzen sich mittelständische Unternehmen, KI Expertinnen und Experten, Startups sowie Vertreterinnen und Vertreter aus Forschung und Wissenschaft, um Wissen zu teilen, Erfahrungen auszutauschen und um an konkreten KI-Projekten zu arbeiten. In unserer Podcast Community kannst du dich einbringen, mitdiskutieren und den Bundesverband als Mitglied aktiv unterstützen und mitprägen.Zur Plattform:https://www.venture-ai-germany.spaceVernetze dich mit Norman auf LinkedIn:https://www.linkedin.com/in/muellernorman

In dieser Folge spricht Norman Müller mit Prof. Dr. Andreas Moring und Andreas Schmidt darüber, warum KI im Mittelstand zwar überall getestet wird, aber selten in echte Wirkung kommt. Im Mittelpunkt stehen die Fragen nach Verantwortung, Roadmaps, Change Management und dem Sprung von Tool-Spielerei zu echter Transformation. Es geht um Geschwindigkeit, Mut und die unbequemen Wahrheiten, die Unternehmen 2026 nicht mehr wegmoderieren können.Link zum IHK-Zertifikatslehrgang "AI Leadership & Change Manager"⁠ https://venture-ai-germany.org/ai-leadership-and-change-manager-2⁠ To hear more, visit ventureaibriefing.substack.com

If you've ever felt like you're busy but not progressing, you're not alone. The fix usually isn't a bigger plan—it's daily forward momentum. This episode kicks off a full season dedicated to getting unstuck by building a repeatable, low-friction way to move closer to your goals without burning out. The key shift: you're rarely "stuck." More often, you've plateaued—and plateaus are solvable with small, consistent action and smarter focus. Why Daily forward momentum matters Momentum is the difference between "I'm thinking about it" and "I'm shipping it." For developers and engineering leaders, it's easy to confuse activity with progress: meetings, tickets, firefighting, context switching, and endless "urgent" tasks. Daily forward momentum is how you reclaim control. It creates a stable rhythm that survives busy weeks and keeps your goals alive even when your calendar doesn't cooperate. Daily forward momentum starts by reframing "stuck" as a plateau "Stuck" can feel like a personal failure. A plateau is just a stage. You've grown, you've learned, you've pushed forward—and now the same tactics aren't producing the same results. That's normal in engineering careers, product development, and business growth. The point isn't to force the old approach harder. The point is to adjust. When you reframe stuck as a plateau, you stop spiraling and start experimenting. Daily forward momentum vs. repeating the same approach A plateau often comes from running the same playbook and expecting a different outcome. The move here is not "work more." It works differently. Try swapping: more effort → more leverage more tasks → better priorities more planning → smaller execution loops Daily forward momentum helps you test new approaches safely. You're not betting the week on a giant change. You're placing small, consistent bets that compound. Daily forward momentum and the "work in vs work on" trap This is the trap most technical leaders know too well: you can spend all your time building, coding, and delivering… and still feel like nothing is improving. Working in the work keeps things running. Working on the system—process, automation, positioning, strategy—keeps things growing. If you're a developer-founder or a tech lead, this matters because the "on" work is rarely urgent. It's just important. Daily forward momentum makes the important work non-negotiable without making it overwhelming. Keep your focus narrow Limiting yourself to 1–2 priorities prevents overwhelm and protects follow-through. A simple split works: 15 minutes in the morning + 15 minutes later in the day to keep progress alive. Daily forward momentum in 15 minutes a day The most practical idea in this episode is almost boring—which is why it works: 15 minutes a day. This isn't a productivity hack. It's a commitment device. You're proving to yourself that forward motion can happen even on messy days. A good 15-minute target looks like: Define the next smallest task Remove one blocker Draft one message Outline one section Implement one tiny change Document the next step so tomorrow starts clean Daily forward momentum in 15 minutes Choose a small, repeatable daily action that moves one goal forward. Consistency beats intensity when you're trying to break a plateau. Daily forward momentum through automation and time reclaimed One of the fastest ways to build momentum is to reclaim time. Automations—big or small—can turn recurring hour-long chores into quick workflows. That time savings becomes fuel. You reinvest it into the next constraint, the next improvement, the next deliverable. That's how momentum starts to snowball: less drag, more throughput, more clarity. Daily forward momentum challenge: pick one task for the week This episode brings back a challenge format that's simple and actionable: Write down the tasks you've been avoiding. Pick one task for the week. Touch it every day for 5–10 minutes. At week's end, review what moved and what didn't. Adjust. Callout: The Weekly Focus Challenge List the "stuck" tasks, pick one, and move it forward every day this week. End-of-week review: what progressed, what didn't, and what you'll change next. Daily forward momentum rules: keep your focus narrow (1–2 items) If you're new to this, don't juggle seven initiatives. Start with one. If you've got a big backlog of half-finished ideas, cap yourself at two. The goal is visible progress. When you can point to real movement, motivation stops being fragile. Daily forward momentum becomes your default operating system. Final Thoughts If you want more progress without more pressure, commit to daily forward momentum this week. Pick one thing, touch it daily, and let the results prove the method. If you want more practical resets like this, follow the season and bring the challenge to your team. Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources Maintaining Momentum And Steady Progress Consistency And Momentum: Keys To Success New Year, New Momentum: What Developers Can Look Forward to in 2026 Habits, Roadmaps, and the Value of Career Momentum Building Better Foundations Podcast Videos – With Bonus Content

Welcome to a special episode of Bubba and the Bloom. Bubba and Ryan are honored to stream a live episode as part of PitchCon 2026. The guys review the BloomBoards from the previous positional reviews to build a hitting roadmap. If you can, please visit pitcherlist.com/pitchcon to donate to ALS research. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Commercial technology is front-and-center of everyone's mind across the public sector ecosystem these days, but history shows that agencies have moved slow on the acquisition and adoption fronts here.Sheila Duffy, founder and chief executive of Greystones Group, views these efforts as grounded in collaboration as customer and contractor both have to agree on the roadmap for development and implementation.Duffy joins our Ross Wilkers for this episode to go over keys for good collaborations with agencies on rolling out modern tools and how Small Business Innovation Research programs can be a pathway to accomplish that.Any conversation about commercial tech in government has to include security. This one is no exception.

Sende uns Deine NachrichtWarum 2026 kein Technologiejahr wird, sondern ein Jahr der EntscheidungIn dieser Folge geht es um Künstliche Intelligenz jenseits von Hype und Heilsversprechen. Es geht um Verantwortung statt Tools, um Haltung statt Roadmaps und um die Frage, was Führung bedeutet, wenn KI selbstverständlich geworden ist. Ein Ausblick zwischen den Jahren auf ein Möglichkeitsjahr, das weniger Technik verlangt als Mut, Klarheit und menschliche Reife.Support the show________________ Abonniere den Podcast bei Apple oder Spotify und unterstütze uns mit deiner 5-Sterne-Bewertung, damit weitere spannende Gäste unserer Einladung zum Podcast-Interview folgen. Für noch mehr exklusive Inhalte, wie z.B. Videoaufzeichnungen, Live-Talks und zusätzliche Hintergrundinformationen, sowie den Zugang zur Podcast-Community registriere dich kostenfrei auf der Plattform des Bundesverbandes für KI-Transformation e.V.: https://www.venture-ai-germany.space Vernetze dich mit Norman auf LinkedIn https://www.linkedin.com/in/muellernorman

Grab my Achievement Roadmap framework here: https://live.geronimoacademy.com/achievement-roadmap Want to access more of my proven systems to grow your business without burnout? Go here: https://bit.ly/44XoX5w Picture this: you're standing on the deck of a 52ft boat, eagle flying overhead, on your way to Hawaii with your dream clients… and you realise you wrote this exact moment down in a vision book three years ago. That's exactly what just happened. And at this point, it's too cooked to call it “luck” anymore. In this episode, we're unpacking the exact Achievement Roadmap framework we use with our team and our studio owners to turn “one day” goals into “holy sht, it actually happened” reality, in business, body, bank account and life. We're talking vision books, Power 12, Separation Sunday, eagles, crows, boats, Broncos, net growth records… and why once you get this right, you honestly have to be careful what you put on the roadmap, because it will come true. Here's what we're covering: -The wild story of a made-up vision book that turned into Hawaii, boats, and record-breaking growth -What an Achievement Roadmap actually is (and why your goals keep stalling without one) -The “Holy Trinity”: Achievement Roadmap, Power 12 and Separation Sunday working together -How to turn 5-year studio goals into daily standards you actually follow through on -Why your environment matters more than your willpower (and how to get in the right arena) -Real client examples: from stuck and vague to new locations, dream teams and $100k months -The power of milestones and rewards (and why most owners are terrible at both) -How to reset and upgrade your roadmap once you hit your “dream” goals faster than expected … and a whole lot more Connect with us: My website: ⁠https://thegeronimoacademy.com ⁠ IG Geronimo: ⁠https://www.instagram.com/thegeronimoacademy⁠ IG Hey.Doza: ⁠https://www.instagram.com/hey.doza⁠ LinkedIn: ⁠https://au.linkedin.com/in/andrewhandosa⁠ Don't forget to like, subscribe, and comment below with your biggest takeaway. We read them all. Connect with us: My website: https://thegeronimoacademy.com IG Geronimo: https://www.instagram.com/thegeronimoacademy IG Hey.Doza: https://www.instagram.com/hey.doza LinkedIn: https://au.linkedin.com/in/andrewhandosa Chapters: ⏳ [00:00] Big Fck-Off Boats & Hawaii: When Your Vision Book Comes True ⏳ [06:40] From Vivid Vision to Achievement Roadmap: How It All Started ⏳ [13:20] The “Day Rock” Story: Unlocking Big Hires With Big Targets ⏳ [20:30] Power 12, Screensavers & Why You Must Be Careful What You Write Down ⏳ [26:50] Team Wins: Weight Loss, Investing, Debt-Free and Dream-Living ⏳ [33:00] In the Arena: Doing the Same Work We Ask Our Studio Owners to Do ⏳ [40:05] Milestones, Rewards & Why Money Alone Won't Fill the Meaning Gap ⏳ [46:30] Case Studies: Studios Hitting 5-Year Visions in 6–12 Months ⏳ [52:10] Why This One System Alone Can ROI Your Entire Membership ⏳ [58:00] Decide, Do, Declare: Your Next Steps With the Achievement Roadmap

Developer Relations wirkt von außen oft wie eine Bühne, ein Reisekoffer und ein paar Sticker am Messestand. Aber was, wenn genau diese Rolle der stärkste Hebel ist, um dein Produkt besser zu machen, deine Tech-Community ernsthaft aufzubauen und Entwickler:innen wirklich erfolgreich zu machen?In dieser Episode nehmen wir Developer Relations auseinander, ganz ohne Marketing-Buzzword-Bingo. Zu Gast ist Philipp Krenn, Head of Developer Relations bei Elastic. Philipp bringt nicht nur jahrelange DevRel-Praxis mit, sondern auch Community-DNA, von Viennadb-Meetups bis Papers We Love, plus Open-Source-Erfahrung rund um Google Summer of Code und das Elastic-Ökosystem.Wir klären, was DevRel eigentlich ist, wo die Grenze zu Developer Marketing verläuft und warum der wichtigste Unterschied oft die Zwei-Wege-Kommunikation ist: raus in die Community und zurück ins Produktteam. Wir sprechen über den Alltag von Developer Advocates, Konferenzen, Content, Community Support auf Discourse, Reddit, Stack Overflow und Slack und wie man Feedback so sammelt, dass es in Roadmaps landet. Dazu kommt die große Frage: Influencer oder nicht? Und warum der Personenkult für Firmen gefährlich werden kann.Außerdem geht es um Open Source, Meetups, Tech Community, Networking, KPIs ohne falsche Anreize, den DevRel-Hype-Zyklus rund um AI und welche Skills du brauchst, wenn du selbst in Developer Relations einsteigen willst.Am Ende weißt du nicht nur, ob DevRel zu dir passt, sondern auch, wie du als Entwickler:in DevRel wirklich nutzen kannst, ohne nur Socken mitzunehmen.Bonus: Wenn jemand mit Laptop und kaputter Query kommt, ist das für Philipp kein Problem, sondern der Wunschzustand.Unsere aktuellen Werbepartner findest du auf https://engineeringkiosk.dev/partnersDas schnelle Feedback zur Episode:

Store digitization promises to transform retail operations, but most retailers struggle to move beyond pilots and buzzwords. In this Omni Talk Ask An Expert episode, hosts Chris Walton and Anne Mezzenga sit down with Troy Siwek (General Manager of gStore at GreyOrange) to reveal what actually works when digitizing physical stores. Learn how digital twins are evolving from concept to operational reality, why unified platforms matter more than individual point solutions, and how to cut through the hype around retail AI. Drawing from GreyOrange's 40,000+ technology deployments, Troy shares hard-earned lessons about RFID integration, computer vision evaluation, robotics orchestration, and organizational readiness. Key topics covered: • What store digitization actually means: bridging the physical-digital customer knowledge gap • Digital twins as operational "mirrors" that surface real-time insights for associates and executives • How to evaluate computer vision vendors based on what they actually specialize in • Why most retailers should partner for core digitization tech rather than build in-house • RFID inventory accuracy reducing store tasks from a week to 18 minutes • The organizational shift: who owns store digitization across CTO, CIO, and store ops teams • How excessive decision-making processes kill retail innovation speed • When to pilot, when to scale, and when to cut failing technology experiments Whether you're building your 2026 technology roadmap or trying to scale existing store digitization pilots, this conversation provides actionable insights to help you avoid costly mistakes, accelerate decision-making, and deliver measurable improvements for store associates. Connect with Troy: https://www.linkedin.com/in/troysiwek/ Visit GreyOrange: https://www.greyorange.com #RetailTech #StoreDigitization #DigitalTwins #RetailAI #RFID #ComputerVision #OmniChannelRetail #RetailOperations #InventoryManagement #RetailInnovation #StoreTransformation #GreyOrange

A CMO Confidential Interview with Michael Treff, the CEO of Code and Theory joins us for our 150th Show to share observations on the major forces impacting the B2B space. Michael details how "empowered buyers" are forcing sellers to increase focus on customer value creation and transforming marketing and sales from "leads to information" which is also shifting spending to capital expense. Key topics include: why the next AI frontier is customer experience; the need for companies to have both a long and short-term AI plans; why budgeting won't get any easier and; the gap between the CX problems and CX actions. Tune in to hear why you need to have an "AI plan for your humans" and learn if you need " a personalized relationship with your mustard."CMO Confidential #150: Michael Treff on B2B's Year-In-Review, What's Next, and How AI Will Actually Drive Growth**B2B is being rebuilt from the core. Michael explains why budgets are shifting from media to infrastructure, how the funnel is being rewritten by agentic search, and where AI must move from efficiency to growth. We also cover the KPIs that matter, budgeting realism for 2026, and three things every CMO should know by the end of next year. Sponsored by Typeface—the agentic AI marketing platform helping brands turn one idea into thousands of on-brand experiences. Learn more: typeface.ai/cmo. **Chapters**00:00 Intro + show setup01:00 Sponsor: Typeface — agentic AI marketing, enterprise-grade & integrated02:00 Guest intro: Michael Treff, CEO of Code and Theory03:00 B2B landscape: investment shifts, changing journeys, disintermediation07:00 From MQLs to value: sales enablement and end-to-end outcomes10:00 Mid-roll: Typeface ARC agents & content lifecycle11:00 Why suites win: implementation and value realization after the sale15:00 AI phases: Wave 1 (efficiency) → Wave 2 (growth) pressures on agencies17:00 CX as the bridge: measure outcomes, not vanity metrics22:00 Roadmaps, humans, and culture—planning beyond point tools26:00 Budget reality check: deliberation, polarization, and trade-offs29:00 Personalization vs. business impact—what to fund and measure33:00 By end of 2026: know your human plan, AI maturity, and new journeys35:00 2026 prediction: the ROI vice tightens—agencies must be consultative36:00 Closing advice: “Interrogate everything yourself.”38:00 Wrap + where to find past episodes39:00 Sponsor close: Typeface—see how ASICS & Microsoft scale personalization**About our sponsor, Typeface** @typefaceai is the first multimodal, agentic AI marketing platform that automates workflows from brief to launch, integrates with your MarTech stack, and delivers enterprise-grade security—named AI Company of the Year by Adweek and a TIME Best Invention. Learn more: typeface.ai/cmo. **Tags**B2B marketing, enterprise marketing, customer experience, AI marketing, agentic AI, marketing ROI, sales enablement, Code and Theory, Michael Treff, Mike Linton, CMO strategy, marketing budget, personalization, Martech, TypefaceSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

AMDG. What does homeschooling look like in First Grade? Kindergarten? Pre-K? Advisor Pam Castor and resource teacher Emmanuelle Wilhelm share practical tips that you can implement today to set your youngest students up for success in the home.   Related Kolbecast episodes:  90 Vocations Here, Now, and Eventually with Adam & Pam Castor  269 Resources and Roadmaps   197 Tools in a Toolbox – Kolbe Academy's Student Support Services program  151 Joyful Discoveries for Preschoolers  81 The When and the How of Online Elementary  82 Move and Groove  Have questions or suggestions for future episodes or a story of your own experience that you'd like to share? We'd love to hear from you! Send your thoughts to podcast@kolbe.org and be a part of the Kolbecast odyssey.   We'd be grateful for your feedback! Please share your thoughts with us via this Kolbecast survey!  The Kolbecast is available on Apple Podcasts, Spotify, and most podcast apps. By leaving a rating and review in your podcast app of choice, you can help the Kolbecast reach more listeners. The Kolbecast is also on Kolbe's YouTube channel (audio only with subtitles).  Using the filters on our website, you can sort through the episodes to find just what you're looking for. However you listen, spread the word about the Kolbecast! 

Stop Worshipping Product RoadmapsA few years ago, I sat through a two-hour planning session where we debated every line of a shiny new roadmap. By the end, we had a color-coded masterpiece: features neatly slotted by quarter, dependencies tracked, and timelines locked...How to connect with AgileDad:- [website] https://www.agiledad.com/- [instagram] https://www.instagram.com/agile_coach/- [facebook] https://www.facebook.com/RealAgileDad/- [Linkedin] https://www.linkedin.com/in/leehenson/

Are you ready for retirement, or just hoping for the best? Abe Abich dives into the real-life challenges facing federal employees after buyouts, the critical need for a personalized retirement roadmap, and the hidden tax traps that can drain your savings. Discover actionable insights and stories that reveal how planning ahead can turn uncertainty into confidence—no matter where you are on your retirement journey. Schedule your complimentary appointment today: TheRetirementKey.com Get a free copy of Abe’s book: The Retirement Mountain: The 7 Steps To A Long-Lasting Retirement Follow us on social media: YouTube | Instagram | Facebook | LinkedInSee omnystudio.com/listener for privacy information.

In this conversation, Ryan Cadwell emphasizes the importance of nurturing relationships and self-management. He discusses how managing emotions and expectations can lead to better outcomes in personal and professional life. Additionally, he highlights the risks associated with misbeliefs and the necessity of maintaining discipline through consistent processes.   Professional Real Estate Investors - How we can help you: Investor Fuel Mastermind:  Learn more about the Investor Fuel Mastermind, including 100% deal financing, massive discounts from vendors and sponsors you're already using, our world class community of over 150 members, and SO much more here: http://www.investorfuel.com/apply   Investor Machine Marketing Partnership:  Are you looking for consistent, high quality lead generation? Investor Machine is America's #1 lead generation service professional investors. Investor Machine provides true ‘white glove' support to help you build the perfect marketing plan, then we'll execute it for you…talking and working together on an ongoing basis to help you hit YOUR goals! Learn more here: http://www.investormachine.com   Coaching with Mike Hambright:  Interested in 1 on 1 coaching with Mike Hambright? Mike coaches entrepreneurs looking to level up, build coaching or service based businesses (Mike runs multiple 7 and 8 figure a year businesses), building a coaching program and more. Learn more here: https://investorfuel.com/coachingwithmike   Attend a Vacation/Mastermind Retreat with Mike Hambright: Interested in joining a “mini-mastermind” with Mike and his private clients on an upcoming “Retreat”, either at locations like Cabo San Lucas, Napa, Park City ski trip, Yellowstone, or even at Mike's East Texas “Big H Ranch”? Learn more here: http://www.investorfuel.com/retreat   Property Insurance: Join the largest and most investor friendly property insurance provider in 2 minutes. Free to join, and insure all your flips and rentals within minutes! There is NO easier insurance provider on the planet (turn insurance on or off in 1 minute without talking to anyone!), and there's no 15-30% agent mark up through this platform!  Register here: https://myinvestorinsurance.com/   New Real Estate Investors - How we can work together: Investor Fuel Club (Coaching and Deal Partner Community): Looking to kickstart your real estate investing career? Join our one of a kind Coaching Community, Investor Fuel Club, where you'll get trained by some of the best real estate investors in America, and partner with them on deals! You don't need $ for deals…we'll partner with you and hold your hand along the way! Learn More here: http://www.investorfuel.com/club —--------------------

Join us this week as we discuss Bungie twisting or sticking with the power reset, progression and unsunsetting decisions. We go over the need for more in-game events or the possibility of longer ones to help entice guardians to carry on playing in such a low time for players. We discuss the difference between roadmaps and calendars, repeated weapon rewards, again! and share some juicy information about the upcoming Festival of the Lost event. We go into detail on the most recent Update 9.1.5 information and give our thoughts. Plus we look at the rest of the weeks news and information from Bungie, including This Week At Bungie for the 9th October 2025. We preview this upcoming weeks rotations in the sixth week of Ash & Iron and have some more YouTube videos for you to enjoy. 00:01:48 - Welcome to Making It Up 00:03:48 - Update 9.1.5 with Discussion Points 00:33:44 - This Week At Bungie: October 9th 2025 00:34:07 - Exotic Mission Feelings 00:39:00 - Delays, Roadmaps & Calendars 00:49:36 - Repeat Weapon Issues, Again 00:52:39 - Calendar Vs Roadmap & Where's Iron Banner? 00:58:04 - Trials, Arms Week & 2 Week Festival, Why? 01:13:06 - Festival of the Lost 2025 Info 01:24:10 - This Week In Destiny: Ash & Iron Update - Edge of Fate - Week 14 01:29:48 - Portal & Progression Changes 01:47:49 - Renegades Power Reset Update Discussion 02:15:24 - Arms Week Was ‘Ere, Trials & Twitch Gone 02:18:18 - Wolf Hoody 02:19:20 - Peroty's Player Support Report & End of TWAB 02:29:45 - Video Recommendations 02:34:30 -Patreon & End of the Show 02:37:08 - Fin Two Titans and a Hunter YouTube Channel Two Titans and a Hunter Twitch Two Titans and a Hunter Discord Two Titans and a Hunter - Patreon Two Titans and a Hunter Ko-Fi The100 io – GH/GD/2TAAH Group Email: twotitansandahunter@hotmail.com Two Titans and a Hunter Twitter Two Titans and a Hunter – Facebook Artwork by @Nitedemon Xbox Live: Nitedemon, & Peroty End credits theme song by Elsewhere - YouTube Channel Plus as always, thank you to Alexander at Orange Free Sounds & www.freesound.org for all the sound effects used in our podcast.  Required Stuff: Bungie - This Week at Bungie October 9th 2025 Bungie - Update 9.1.5 SayWhallahBruh - 1 Shot Bow in PvP SayWhallahBruh - Hey Bungie, I Think You Guys Broken The Game Cheese Forever - 999 RPM Illegal Trigger Mod Profane Gaming - Warlock Buddies Tested Fallout Plays - Oh God Bungie, What Have You Done SneakyBeaver - Infinite Golden Gun Build Fallout Plays - Wolfsbane Exotic Guide Week 1 Fallout Plays - Is The New Exotic Axe Any Good? Esoterickk - The Portal Reimagined CammyCakes Gaming - Best Tier 1 PvP Build Maven - Warlock Grenade Update Testing The Game Post - Festival of the Lost 2025 Info Destiny Rising - Discord Link Destiny 2 - Tier 5 Report Destiny 2 Armor 2.0 Cleaner Destiny 2 - Way Back Machine Link Twitch - GuardianDownBot Raid Checkpoints Twitch - IceBreakerCatty. Engram.Blue Link

How we build products, why we build them, and what we think they're for have always changed, but these days developers and engineers who love things like product roadmaps might find the current AI scene a little disorienting. That's because there often isn't a roadmap. If there is? It's constantly changing.This week, we meet the CTO of IBM Research and she tells us about the current landscape and what she imagines for the future. This episode was recorded at TEDAI in Vienna, Austria. We Meet:  IBM Research CTO Anna Topol Credits:This episode of SHIFT was produced by Jennifer Strong with help from Emma Cillekens, and special thanks to Dajana Doskoc and Alina Nikoloau at TEDAI Vienna. It was mixed by Garret Lang, with original music from him and Jacob Gorski. Art by Meg Marco.

Layer-1s are still the backbone of crypto, but in 2025 their role is evolving. With Ethereum's L2 ecosystem booming, modular blockchains on the rise and real-world adoption gaining momentum through stablecoins and tokenized assets, the question is no longer just about scalability. It's about utility, users and where the next wave of growth will come from.In this episode of Decentralize with Cointelegraph, we sit down with Algorand Foundation's Chief Strategy and Marketing Officer Marc Vanlerberghe to explore the state of layer-1s today, the barriers to mainstream adoption, and the innovations that could define blockchain's future. (01:08) Regulation and industry developments(03:12) The state of layer-1s vs. layer-2s in 2025(06:40) Barriers to adoption and rethinking wallets(11:58) Tackling user growth and engagement(17:26) Roadmaps, strategies and industry alignment(23:20) Enterprise use cases and tokenization(29:16) Looking ahead: the future of crypto (32:12) Takeaways for retail and institutional usersThis episode was hosted and produced by Savannah Fortis, @savannah_fortis.Follow Cointelegraph on X @Cointelegraph.Check out Cointelegraph at cointelegraph.com.If you like what you heard, rate us and leave a review!The views, thoughts and opinions expressed in this podcast are its participants alone and do not necessarily reflect or represent the views and opinions of Cointelegraph. This podcast (and any related content) is for entertainment purposes only and does not constitute financial advice, nor should it be taken as such. Everyone must do their own research and make their own decisions. The podcast's participants may or may not own any of the assets mentioned.

On episode 14 of Platform Builders, Christine Spang and Isaac Nassimi speak with Anthony Presley. Anthony walks through his journey from early consulting to creating workforce management SaaS, highlighting how persistence and customer-driven development shaped his companies. Together, they dig into the complexities of restaurant software, the importance of open ecosystems, and where dining tech is headed.

Road maps for where you need and want to go. Travel is something many of us think of as a physical movement of our mortal frame, our body. Travel starts in the inner-person far before the body takes the first step of a journey.

Spring Lake Church – Bellevue and DowntownSermon: Road MapsTeacher: Jack GuerraPassages: John 2:11, John 11:1-4, John 14:6, etc...In “Road Maps,” Pastor Jack Guerra looks at the miracles and “I Am” statements of Jesus in John, showing us how Christ reveals His power and identity. From turning water into wine to raising Lazarus, each sign points us to His Lordship. Jesus is the Bread of Life, the Good Shepherd, and the Way, Truth, and Life. As a church, we're called to step in through serving, inviting, and praying. What is your part to play in this season?springlakechurch.org | springlakechurch.org/give | springlakechurch.org/prayer

In this episode of Stats On Stats, Vinod Akunuri, founder of Jumpstart to Tech, shares his unconventional journey from struggling student to impactful tech leader. He opens up about how his personal challenges, including ADHD, early academic setbacks, and post-grad uncertainty, inspired him to build a platform that provides personalized roadmaps for tech careers.Guest Connect:LinkedIn:  https://www.linkedin.com/in/vinodakunuri/Stats on Stats ResourcesCode & Culture: https://www.statsonstats.io/flipbooks    | https://www.codeculturecollective.io  Merch: https://www.statsonstats.io/shop   LinkTree: https://linktr.ee/statsonstatspodcast   Stats on Stats Partners & AffiliatesHacker HaltedWebsite: https://hackerhalted.com/  Use Discount Code: "

How can enterprise product leaders balance customer needs, technical complexity, and strategic vision? In this podcast hosted by Cassio Sampaio, Okta VP of Product Ian Hassard will be speaking on building effective B2B SaaS roadmaps and navigating product management challenges. Ian shares insights from his extensive experience leading product teams at high-growth companies like Okta and Auth0, offering a deep dive into modern product management strategies.

Steve Gruber discusses news and headlines 

MeidasTouch host Ben Meiselas reports on the powerful speech by Illinois Democratic Governor Pritzker and Meiselas interviews Ofirah Yheskel, senior strategist at the Democratic Governors Association. Visit https://meidasplus.com for more! Remember to subscribe to ALL the MeidasTouch Network Podcasts: MeidasTouch: https://www.meidastouch.com/tag/meidastouch-podcast Legal AF: https://www.meidastouch.com/tag/legal-af MissTrial: https://meidasnews.com/tag/miss-trial The PoliticsGirl Podcast: https://www.meidastouch.com/tag/the-politicsgirl-podcast The Influence Continuum: https://www.meidastouch.com/tag/the-influence-continuum-with-dr-steven-hassan Mea Culpa with Michael Cohen: https://www.meidastouch.com/tag/mea-culpa-with-michael-cohen The Weekend Show: https://www.meidastouch.com/tag/the-weekend-show Burn the Boats: https://www.meidastouch.com/tag/burn-the-boats Majority 54: https://www.meidastouch.com/tag/majority-54 Political Beatdown: https://www.meidastouch.com/tag/political-beatdown On Democracy with FP Wellman: https://www.meidastouch.com/tag/on-democracy-with-fpwellman Uncovered: https://www.meidastouch.com/tag/maga-uncovered Coalition of the Sane: https://meidasnews.com/tag/coalition-of-the-sane Learn more about your ad choices. Visit megaphone.fm/adchoices