Podcasts about ftp

Brendan Housler and Landry Bobo break down a Ben Healy “lactate clearance” session: 3 x 10 minutes with 2 minutes at ~120% FTP followed immediately by 8 minutes at ~85–90% FTP, with 10 minutes easy between sets. They explain that the goal isn't the surge itself but the ability to settle back into strong aerobic riding while clearing and reusing lactate, mirroring real race demands like attacks, covering moves, and riding hard after climbs or corners. They discuss why many riders can hit VO2 efforts but struggle to continue at tempo afterward, and share ways to progress the workout (longer hard starts, adding surges, 40/20s into tempo, more repeats, or adjusting recovery). They suggest using this work in build phases, pre-race prep, and even year-round as lighter “touches” between harder blocks.

Climbing faster isn't always about increasing FTP or producing bigger power numbers. In this episode, CTS Coach Adam Pulford breaks down the pacing strategies, tactics, fueling, and key workouts that help cyclists climb faster with the fitness they already have.HOSTAdam Pulford has been a CTS Coach for nearly two decades and holds a B.S. in Exercise Physiology. He's participated in and coached hundreds of athletes for endurance events all around the world.The Problem with Chasing Data - RPE: https://www.youtube.com/watch?v=Wsywx731ki0​​Free Cycling Training Assessment: https://trainright.com/cycling-training-assessment-welcome/Interested in working with a coach? Schedule a free consult: https://trainright.com/coaching/cycling/Self-coached athlete? Check out our TrainRight Membership: https://trainright.com/membership/Find more free resources here: https://trainright.com/blog/

If you've ever wondered whether your endurance base could carry you into gravel or mountain bike racing — or whether your FTP is really the thing holding you back — this episode is a timely reality check. Dave Schell is the founder of Kaizen Endurance, based in Boulder, Colorado, and has spent 15 years coaching cyclists and endurance athletes through some of the most demanding events on the calendar — Unbound 200, Leadville, ultra-distance gravel and mountain bike. Before that, he spent seven years at Training Peaks as coach education manager, so he understands both the science and the real-world application better than most. We talk about why FTP is overrated as a race predictor, why skill and technique will give you more free speed than another training block, how to actually prepare your body for eight to ten hours in the saddle, the mental game of ultra-distance events, and why consistency remains the most unsexy and most powerful tool any athlete has. There's a lot in here that applies well beyond gravel.   5 KEY POINTS FTP is overrated for long events — after eight hours everyone regresses to the same sustainable pace. Durability and fat oxidation decide the result. Skill delivers free speed — technique improvements will outperform another fitness block for most athletes, most of the time. Race your race bike — training on the road and racing gravel leaves your body unprepared for the physical demands, regardless of fitness level. Recovery is where adaptation happens — most athletes need permission to rest, not encouragement to go harder. Consistency is the only secret — the work never changes, you just keep doing it week after week. 3 TAKEAWAYS Sign up for something that scares you — if there's no real possibility of failure, you'll wing it. The fear is what gets you out the door. Context beats data — RPE and athlete feedback tell you more than power numbers alone. Data without context is just noise. Extreme moderation wins — train at the right load, not the highest load. The athletes who stay consistent are the ones who progress. KILLER QUOTE

Hello everyone. Welcome to the latest episode of The Matchbox Podcast powered by Ignition Coach Co. I'm your host, Adam Saban, and on this week's episode we're talking about Leadville prep! Training, injury mitigation, and altitude prep.   As always, if you like what you hear, share this with your friends and leave us a five star review and if you have any questions for the show drop us an email at matchboxpod@gmail.com or head over to ignitioncoachco.com and fill out The Matchbox Podcast listener question form.    Alight let's get into it!   For more social media content, follow along @ignitioncoachco @adamsaban6 @dizzle_dillman @dylanjawnson @kait.maddox     https://patreon.com/MatchboxPodcast?utm_medium=unknown&utm_source=join_link&utm_campaign=creatorshare_creator&utm_content=copyLink   https://www.youtube.com/c/DylanJohnsonCycling https://www.ignitioncoachco.com  https://www.youtube.com/@DrewDillmanChannel   Intro/ Outro music by AlexGrohl - song "King Around Here" - https://pixabay.com/music/id-15045/    The following was generated using Riverside.fm AI technologies   Main Topics: Strategies for reintroducing training after injury, emphasizing conservative ramp-up and volume management Importance of base fitness and how aerobic capacity supports high-altitude performance Race-specific pacing and intensity focus, especially maintaining tempo to optimize endurance Incorporating torque and long sustained climbs for single speed riders Altitude acclimation: timing, frequency, and how it influences race performance Building durability and fatigue resistance through volume, stacking workouts, and targeted intervals Practical training structure during the build phase to surpass fatigue hurdles and extend endurance Managing logistics and mental preparation for race day at high elevation   Timestamps: 00:00 - Introduction and podcast goals 00:29 - Incorporating concise questions from listeners 01:16 - Brandon's background and race goals at Leadville 02:41 - Challenges of single speed racing on steep climbs and long flats 03:40 - Importance of gradual ramp-up after injury recovery 04:48 - Risks of too rapid training progression and injury considerations 05:42 - Chronic injuries and compensatory movement patterns 06:50 - Strategies for conservative ramping and avoiding injury flare-ups 08:15 - Maintaining aerobic base and leveraging it for training efficiency 09:12 - Balancing intensity types: tempo versus high-intensity workouts 10:09 - Race-specific pacing: holding tempo and avoiding over-FTP efforts 11:26 - Focus on VO2 max and lactate threshold in training 12:12 - Adapting training zones for altitude and single speed specificity 13:28 - Role of torque intervals, especially for single speed riders 14:55 - Climbing and torque interval recommendations based on geographic location 15:00 - Adjusting training volume and intensity to build endurance 16:30 - Decision-making around race participation in the GP series and logistics 17:40 - Outperforming at altitude: genetics and acclimation cycles 18:40 - Acclimation strategies and responding to altitude over time 20:30 - Training at altitude for improved performance at sea level 22:01 - Managing chronic injuries and race day approach 23:39 - Training and recovery balance for high-altitude races 25:21 - Long-term injury management and race day performance 27:42 - Final thoughts and race prep advice from Dylan and hosts 42:19 - Community encouragement and upcoming race plans

Vu Le is our guest for the Season Nine Finalé, which also serves as an installment of our ongoing Defend Nonprofits, Defend Democracy Series. Recorded with a live zoom audience during our spring webinar series, Vu discusses his burnout, funding instability, philanthropy's power dynamics, and what it will take to strengthen nonprofits in an era of rising authoritarianism. Vu argues that nonprofits and funders must stop normalizing scarcity, invest deeply in leaders and infrastructure, and organize collectively for long-term change.Drawing from his new book Reimagining Nonprofits and Philanthropy, Vu challenges conventional assumptions about fundraising, nonprofit leadership, and philanthropy itself. The conversation explores why progressive movements struggle to sustain leaders, how conservative leadership infrastructure has been built strategically over decades, and what nonprofit professionals can do right now to protect democracy and each other.Download a transcript of the episodeAbout Our GuestVu Le is a prominent writer, speaker, and former executive director of Seattle-based Rainier Valley Corps. Widely recognized for his irreverent, no-nonsense approach to social justice and philanthropy, he authors the viral blog Nonprofit AF, and is a co-founder of the Community-Centric Fundraising movement. Most recently he is author of the book, Reimagining Nonprofits and Philanthropy. In 2020, Vu was our first guest on the Fund the People: A Podcast with Rusty Stahl.Suggested Links:Vu Le's Blog, Nonprofit AFReimagining Nonprofits and Philanthropy (Book)The Sally Covington Report (Moving a Public Policy Agenda: The Strategic Philanthropy of Conservative Foundations)Community-Centric FundraisingNonprofits Are Message with Joan Garry - Episode 251 with VuTrust-Based Philanthropy ProjectNational Council of NonprofitsIndependent SectorBolder AdvocacyRules of the Game Podcast (Note: Rusty misstated the name of the podcast in the recording. The correct name provided here)Solidaire NetworkFund the PeopleFund the People Webinar SeriesRelated Fund the People Podcast Episodes:S1:E1 — Vu Le: Treating Nonprofit People Like Batteries - The very first FTP podcast episode, revisited in this conversation, on burnout, scarcity, and nonprofit workforce culture.

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

8 minutes of full-gas work. 14% VO2 max gain. But only if you do them right on the CoachCat training app. Your first 7 days FREE: https://fascatcoaching.com/app Dr. Izumi Tabata's 1996 study proved that 20-second efforts at supramaximal intensity produce more anaerobic capacity AND VO2 max gains than traditional steady-state training, and in a fraction of the time. In this training tip, Coach Frank Overton breaks down the exact workout 20+ years of FasCat athletes have used to win races: 3 sets of 8 × 20 seconds at 170% of FTP, with 10 seconds rest and 10 minutes between sets. There's a RIGHT way to do Tabatas and a WRONG way that wastes the workout. This video covers both, with the pacing strategy, terrain selection, ERG-mode trap, and mental tips you need to actually finish all 24 reps and get the adaptation Dr. Tabata's research promised.

Le geek en chef David Jeker et Robin Bonneau-Patry de Rtings viennent nous donner un masterclass sur les Supershoes. Magasinez chez Altitude Sports et économisez jusqu'à 20 % sur votre première commande avec le code UPIKA2026.  Cliquez ici pour commander

Warm weather is on the way and you need to stay hydrated. As a start, take a sip of water every time you hear the phrase "in the 90's." This week we're learning about Interactive Fiction - its history, communities, and transformations over the years - from living archive of the medium, Andrew Plotkin. As a bonus, Stephen discovers that he isn't the only one who is wrong about things! Credit for this episode's extra-thorough show notes goes to Andrew. Thanks, Andrew!Interactive Fiction CommunitiesEventsIRLNarrativeColossal Cave Adventure - William Crowther and Donald Woods, The Interactive Fiction DatabaseThe Visible Zorker: Zork 1Interactive Fiction Competition (ongoing since 1995!) - Interactive Fiction CompetitionInform IF language launched around 1993 (https://www.inform-fiction.org/). You can find the modern version at https://inform7.com/ This allowed people to create games for Infocom's original Z-machine, which was invented as a proprietary system in 1979 but is now open-source.The modern version of the IF community's FTP site - Interactive Fiction ArchiveInteractive Fiction Technology FoundationNarrascope ConferenceTwine - Chris Klimas, TwineryRise of the Video Game Zinesters - Anna Anthropy, AmazonThe Cuddled Little Vice (Sandman) - Elizabeth Sandifer, Eruditorum PressAndrew's Interactive Fiction and Game recommendations - IFcomp 2025 winners - Type Help - Roottrees are dead - Return of the Obra Dinn - Murder at the Birch Tree Theater

Most cyclists think they're doing threshold training — but most are actually riding too easy to drive real FTP gains. In this episode, we break down what true threshold work actually is, why your FTP may have plateaued for years, and how elite coaches structure intensity for maximum adaptation. Drawing on insights from Stephen Seiler, Dan Lorang, and WorldTour training models, we explain the difference between sweet spot and threshold, how much threshold work amateurs actually need, and the biggest mistakes riders make with interval pacing. Plus, we give you three proven threshold sessions you can start using this week to finally move your FTP in the right direction.One of the tools you will have heard Anthony chat about in this podcast is Training Peaks. Without this platform we can't get into the detail required to pricesly train within zones. If you want to go and check out this incredible training tool go to ⁠https://bit.ly/4qWyEKK⁠ and use ROADMAN – 20% off an annual TrainingPeaks Premium subscription⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Parlee Cycles ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠"Whether it's a tough day, a gruelling training session, an epic road trip or sitting on the side of the road, exhausted and wondering how you'll get to the top... The answer is regularly to just get back in the saddle and ride. Ride The F...ing Bike. RTFB!"Go check out their amazing bikes at https://www.parleecycles.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠4Endurance⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Pro level fuel, made accessible. Myself and Sarah trust 4Endurance for all our fuelling needs. Their reange is HUGE and won't break the bank. Go check them out here https://4endurance.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠BIKMO⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Bikmo protects you and your bike fromtheft, accidental damage, race-day disasters, and even baggage claim shenanigans. Yourhelmet, GPS, and other kit are covered too. Got more than one bike? Of course you do – you get 50% off each extra bike on the same policy.Protect your ride before it's too late – head to ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Bikmo.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ to get covered. 

Landry and Brendan break down why over-under intervals may be the best “bang for your buck” for raising FTP and building fatigue resistance, arguing they can outperform steady-state threshold work while better matching real race demands like surges, climbs, and pacelines. They explain FTP as the balance between lactate production and lactate clearance, and how alternating time just under and just over threshold trains your body to clear (and even recycle) lactate more effectively, including a nod to the Cori cycle. They also discuss when steady efforts still matter (e.g., certain time trials), warn against overdoing race specificity, and share ideas for making over-unders more fun, customizable, and improvised based on how you feel, plus where to find examples, coaching, and training plans.Chapters:00:00 Why Over Unders Win00:50 How Lactate Raises FTP02:13 Real World Race Surges03:27 When Steady State Helps04:38 Avoid Overdoing Specificity05:48 More Fun Than 2x2008:00 Lactate As Fuel08:51 Customize And Improvise10:30 Race Simulation Story12:47 Speed Focused TT Mindset14:10 Wrap Up Resources

We each have a God–given destiny. A plan that God has for our lives, which fits perfectly with who He made us to be. The problem is that many people aren't living out that destiny – because there are some obstacles in their way. So let's find out what they are, and how to get around them – so that you can live out your destiny.   Putting First Things First Most people these days live hectic lives, just scraping through each day. Personally, my list of things to do is as long as my arm and then some. There are some personal things I have to do; things to do with writing and recording and producing this radio-programme; there's an organisation to run; people to meet with; this project; that project; a new idea over here, another one over there; hundreds of e-mails each day ... Welcome to my world. Now don't get me wrong; I'm not complaining and none of those things are terribly bad at all, but the point is that with so many more things to do than I can possibly fit into my day, or my week or even my year, my process for deciding what I do is absolutely critical. Chances are, the same is true for you. One of the big mistakes I used to make is that I'd sit down in the morning, which (given that I'm a morning person) is my most lucid and productive time, and just start answering e-mails. After a while, I realised I wasn't getting anything else done because by putting my E-mails first, I was putting other people's priorities first. I was in fact dancing to their tune instead of sorting out for myself what the most important things were on my agenda, and doing those things first. There's a well-known principle or framework that you read in a lot of management books, that sets out the difference between what's urgent and what's important, and what you discover is that almost nothing that's urgent is important, and almost nothing that's important is urgent. And yet most of us react to urgent things, or at least the things that other people say are urgent, and so we spend most of our time doing urgent things, instead of the important things – day after day, week after week, month after month, year after year. And before you know it, your life is kind of slipping away, doing a whole bunch of things, which, in the scheme of things, sure, they make you busy, but how important are they? Do you see my point here? How are you spending your life, and are the things you're spending your time on important and worthwhile? I guess I'm asking those questions for you to ask them of yourself, and answer them. Come on! Be brutally honest. For instance, making sure I have some time with my beautiful wife Jacqui is important. Making sure I encourage her and give her a hug and a kiss, and spend some unhurried time with her in the morning over breakfast is really important, but it's not urgent. It's not as urgent say as the e-mail that comes in from a radio-station somewhere around the world that says they weren't able to download tonight's radio-programme from our FTP server. And yet what I used to do (because remember, mornings are my most productive time) is get up early and spend no time at all with Jacqui over breakfast, and just work furiously through that time, and by the time she comes home from work and I come home from work, we're both tired and there you go. We haven't spent any time together. Do you see how easily this stuff happens in people's lives? The urgent trumps the important in so many people's lives, and before you know it, your life is falling apart. Things are in a mess. Marriages are falling apart, all because we allow the urgent to crowd out the important. It's scary, isn't it? So what about you? What about your life? Are you letting the myriad of urgent things crowd out the important things like spending time with people, managing your finances properly, nurturing your children, developing relationships with your co-workers? See, all those things are incredibly important, and in many-a person's life, they're being cast aside simply because we're too busy doing the urgent stuff. 'I don't have time to exercise!' Well, if you don't make time for exercise (which is important), let me tell you you'll certainly be making time for sickness (which will be urgent), and actually, that's how it works. Doing the important things generally over time reduces the number of urgent things that you need to do because if the important things go undone, that leads to crises and those crises increase the number of urgent things requiring an immediate response. I don't know what your destiny is, but this is what I do know: It doesn't lie in a myriad of things that other people tell you are urgent; it lies in the things that, in your heart of hearts, you know are important. If you or I went to God, this God who handcrafted us, who designed us in His heart – blueprinted our DNA, if we went to Him and said: 'Lord, what's the most important thing that I have to do with my life', what do you think He'd answer? What would He put at the very top of our to-do list? Well, actually, we already know. A clever young lawyer once asked Him a very similar question. The lawyer sort of said (and this is my paraphrase): Well, Jesus, you and I both know that in the Law of Moses handed down over all those years, there are 613 commandments and prohibitions. That's kind of a lot. I mean that's a lot day-to-day to remember to do, so how would you sum up the Law? I mean, if I'm trying to prioritise these things in my life, which one of all those commandments is the most important one? You can read the exact words in Matthew 22 and Mark 12, and if I had to paraphrase Jesus' reply in kind of here-and-now speak, it'd run something like this: Look, I know you have a lot of things to do. There are lots of rules: Do this, do that ... They're all good things, but you can sum up the whole Law in just two commandments – to love the LORD your God with all your heart, with all your soul, all your mind and all your strength. That's the most important one, and the second one is just like it: Love the people around you as much as you love yourself. That's the whole Law in a nutshell. Do you know something? The most important thing that I do almost every day, the thing that I do before anything else, is that I spend an hour or so alone with Jesus praying; reading the Bible; asking Him questions, and that's what sets the course for my whole day – day after day, month after month, year after year. Actually, it sets the course for my whole life. It is quite simply the single-most important thing that I do, and it's through that time with Him that I've discovered my destiny.   A Lifelong Journey If I were to ask you, "What's your destiny? What were you put on this earth to achieve – to do? What impact are you meant to have on this planet of over seven billion people? What's the point of your life, and is it heading in the right direction", I wonder how you'd answer those questions. I ask those questions of people rather a lot, and I can tell you the number of people who have a clear sense of destiny and purpose and direction – well you know, it's less than five per cent – maybe one in twenty; maybe. Now I'm not saying that we should each have our lives completely mapped out because things happen along the way. There are twists and turns in life that are totally unexpected. Little things can change the whole course of a life. We can't map out our whole lives in the minutest detail and say. "Yep. That's what I'm going to do, that's where it's going", and yet deep-down, we need to have some sense of a destiny. Another way of putting it would be to have a sense of direction for our lives. Where's your life headed? And that destiny is invariably tied up with two things: Our dreams, and our skills and abilities. If you're one of the majority – one of those people who hasn't quite yet cottoned on to the direction for your life, where it's meant to be headed – then this is for you. Can you remember the dreams that you had for your life when you were young? Can you? There were some back there that were never going to fly. I mean, if you're short and slightly dumpy, and you were dreaming of becoming a famous basketball-player, well, that was obviously never going to happen. But so often, there's a dream in people's hearts that's been there for a very long time. Here's a conversation that I've had so many times with people about this whole question of destiny. We get to talking about the direction in which their life is heading, and the person says to me something like: 'But you know, I'm sure there's meant to be something else, something more, something that I don't know, something I'm meant to be doing, but I don't know what it is'. Does that sound vaguely familiar? So I ask them then, "If you had no constraints, if money wasn't an issue, if you could be anything or do anything that you wanted, what would that be?' And the answer invariably comes back along these lines: 'Oh, well! Anything I want? Well you know, I've always dreamed of" ... and then, they tell me the answer. They tell me about their destiny. It's already there; it's already been woven somehow by God into their DNA. Now of course, there's a risk that this is a short dumpy basketball-player kind of dream, and so then I follow up with my second question: 'What are the things you're really good at?' Most people can tell you that, and what I've found is that there is almost always, in 90% of cases, a wonderful fit between their dream and their natural skills and gifting. You know something? We've just discovered their destiny. We've just discovered what they're meant to be doing with their lives, and the tragedy (I mean, the absolute tragedy) is that deep down they probably already knew that. So what's held them back? The constraints we put on our lives. Remember my first question? 'If you had no constraints, if money wasn't an issue, if you could be anything or do anything that you wanted, what would that be?' My question removes the constraints. Then all of a sudden, people can look at things the way they're meant to be looking at them – through the eyes of freedom. For twenty years, I was a high-priced IT consultant, but there came a time of dissatisfaction – a time when I came to the conclusion that I wasn't fulfilling my destiny. Every few years, the opportunity emerged to do what I'm doing now – to produce these radio-programmes, and use one of the small handful of talents that I naturally have (which is to be a communicator), to bring hope and change and transformation into people's lives through these radio-programmes, but that meant taking a risk. It meant confounding people's expectations of me. It meant leaving a big salary behind, and going and working in a small, at-the-time ailing, not-for-profit organisation. And those constraints and expectations and the money thing and the risk, all those things I have to tell you, were tough issues to navigate. It wasn't an easy decision to make. It was (at the time) a huge leap of faith for me. When I look back on it now, this is what I know ... it's always like that when we have to make a decision as to whether or not we're going to get out there and fulfil our destiny, because destiny requires courage. In fact, the two seem inextricably linked. When we step out on the destiny journey, there's always a risk of failure, and yet there is nothing as fulfilling and energising as living out your destiny. These last years doing what I'm doing now, there have been some real challenges, some really tough times, but I wouldn't swap them for anything. And in pursuing this destiny, here's what I know: The only person who can make it happen in our lives is Jesus Christ. Now some may scoff at that, and sure; there's plenty of evidence of genius and achievement out there in the world. People are capable of doing amazing things, but here's what I'm absolutely certain of: Jesus the Son of God, when He laid His glory aside, when He became one of us, when He came into this world with a destiny, His destiny was twofold. It was to reveal God to us and secondly, it was to die on that cross and rise again to give you and me a free gift of eternal life. And without that Jesus who fulfilled His destiny for you and me, you and I may well be able to achieve some amazing things, but we will never achieve anything of eternal significance and value. Because of my gift of communication, I guess I can hold people's attention. I think I can make them laugh and even cry, but without Jesus, without His story, without His grace, I have nothing of eternal value to impart, 'cos he's the One that saves. He's the One that transforms. He's the One that gives new life, and my destiny lies in Him to be who He made me to be, and to do the things that He made me to do, so that His purposes will be achieved on this earth; and my friend, your destiny, your true destiny, lies in Jesus too. He has plans and purposes for your life, and He came up with them even before you were born, and when we give our lives to Him completely, wholly, fully, without constraint, without limit, without reservation, then we discover that destiny, and let me tell you it is a perfect fit (your destiny) with who He made you to be. How do I know that? Psalm 139. Go read it – His Word, His truth, your destiny.   Ugly Duckling Syndrome The final obstacle to living out our destiny is this: We compare ourselves to other people. We all do that. We all look at these talented and gifted people around us, and we convince ourselves that we can never be as good as them; we can never do what they can do; we can never live out our dream, our destiny. You know what I call that? I call it ugly duckling syndrome. Hans Christian Andersen's powerful story The Ugly Duckling is a literary classic, not so much because of the way it was written (my hunch is that the piece probably loses some of its poetry and lilt, having been translated into English) – no, the power of The Ugly Duckling, the thing that's made it a classic, is in the way that it resonates so deeply in our souls. A swan's egg, by some strange set of events, finds itself in a ducks' nest in a farmyard, and so a swan is born into a family of ducks. No one really cares why or even realises that it's happened; everyone just assumes that this little guy is meant to be a duck, and all of his little life people reject him for being an ugly duckling because he's ugly! Everyone misunderstands him; everyone rejects him, and it hurts. He's all alone, but amidst the bleakness and hopelessness of this world, there is one thing – just one – that makes his little spirit soar. Have a listen. One evening, just as the sun set amid the radiant clouds, there came a large flock of beautiful birds out of the bushes. The duckling had never seen anything like them before. They were swans, and they were curved with their graceful necks, while their soft plumage shone in the dazzling whiteness. They let out a singular cry, as they spread their glorious wings, and flew from those cold regions to warmer countries across the sea. As they mounted higher and higher into the air, the ugly little duckling felt quite a strange sensation as he watched them. He whirled himself in the water like a wheel; he stretched out his neck towards them, and uttered a cry so strange that it frightened him. Could he ever forget those beautiful, happy birds? Then when at last they were out of his sight, he dived under the water and rose again, almost beside himself with excitement. He knew not the names of these birds, nor where they'd flown, but he felt towards them as he had never felt for any other bird in the world. He wasn't envious of these beautiful creatures, but wished to be as lovely as they. Poor, ugly little creature, how gladly he would have lived even with the ducks, had they only given him some encouragement. At the moment, he didn't yet know who he was. He just knew who he wanted to be, but because he didn't know who he was, who God had made him to be, he simply didn't have a license to go and be who he'd been made to be, and even when he finally encounters those birds again, he thinks he's going to die. Surely, surely, that can be the only outcome. 'I will fly with those royal birds,' he exclaimed, 'And they will kill me because I am so ugly! And to dare to approach them ... but it doesn't matter. Better to be killed by them than to be pecked by the ducks, beaten by the hens, pushed around by the maiden who feeds the paltry, or starved with hunger in the winter.' And he flew to the water, and swam towards the beautiful swans. The moment they spied him, they rushed to meet him with outstretched wings. 'Kill me!' said the poor little bird. And he bent his head down to the surface of the water and awaited death, but then something happened that changed everything in an instant. What did he see in the clear stream below? His own image: No longer a dark grey bird, ugly and disagreeable to look at, but a graceful and beautiful swan. To be born in a ducks' nest in a farmyard is of no consequence to a bird, if it is hatched from a swan's egg. It's not until we really know who we are that we discover how inconsequential the distorted images the world's misunderstanding reflects back to us, in fact, are. My friend, as I meet people around the world (and I've met so many; more and more as the years go by), I'm so deeply impressed by the amazing abilities – the talents, ideas, creativity, perspectives, motivations – that are buried inside each and every person, each person whom I've ever met. And that's not just other people: It's each one of us. It's not just them: It's you, because each (in our own unique different way) have the capacity, the capability, the potential to do the most amazing things – to be the most amazing people. Please, please, don't fall for that ugly duckling deception. You are such a person. You have a destiny, and it's waiting for you to be lived. That's precisely the thing that God wants you to know today, when you step out on your journey of destiny – your God-given destiny, for as the apostle Paul writes in Ephesians 2:10, you are His workmanship, created in Christ Jesus to do the good works which God prepared beforehand, so that you would walk into them. See? God made you in a certain way, and He's already prepared the way – the good works, and they're waiting for you on the road ahead, and He's created you as a piece of His workmanship, perfectly suited to the destiny that you're called for. If you go back to Psalm 139:13-18, you discover that not only did God create us in our mother's womb, not only did He lay down every strand of DNA and give you a hair-colour and your heart and your eye-colour and all those characteristics, but He also at the same time wrote down in His book every day, every experience, everything that would happen on your journey, and those two (that He made you, and what He made you to do) are an absolutely perfect fit. It's about discovering that we are indeed God's workmanship, you and I. It's about discovering who we are and what our purpose is, so that we can go and walk into the good works that God prepared beforehand for us to walk into, with a certainty and a quiet confidence, in the knowledge that we're a perfect fit – that we're the right one for the job, no matter how daunting that job may first appear. Father God, we've heard Your good news. We know we've made so many mistakes. We've stepped out of Your plan. We went our own way, and each one of us (in our own way) knows it didn't work out. And so, we want to come back and we want to discover the me that you always meant us to be. Father, thank You for Jesus. We just want to accept Him; I believe that He died for me, and that He rose again; I believe that I'm forgiven because of Him, and that I have eternal life because of Him, and Father right this day, lock, stock and barrel, with everything that I am, with every hope and every dream and everything I have, I want to step back into Your plan for me. I want to step back into my destiny. I give everything I am and everything I have to You, for You to do with as You please. Father God, thank You that You do have a plan. Thank You that I can just come back because of Jesus, and thank You Father that in that plan, I'll get to know You, and as I get to know You more and more and more, I'll discover the person I was always meant to be. I'll discover the destiny that You have for me. I'll discover, in my heart and in my experience, that I am Your workmanship, created in Christ Jesus to do the good works that You prepared beforehand, so that I could walk into them. Father, in the mighty name of Jesus, I want to thank You. I want to thank You for giving me this life. Amen.

If you're over 35 and your FTP keeps sliding backwards every season, this video is for you. The truth is, it's probably not just age. There are five specific things quietly destroying your threshold power right now — and most riders never address them properly. In this video, I break down the biggest mistakes I see experienced cyclists making over and over again, from training structure to recovery and one uncomfortable factor almost nobody wants to talk about. No gimmicks, no “just ride more,” no expensive aero upgrades. Just practical, actionable insights to help you hold onto — and even rebuild — the power you thought was disappearing with age.Anthony mentions Training Peaks throughout this episode. If you want to go and check out this incredible training tool go to https://bit.ly/4qWyEKK and use ROADMAN – 20% off an annual TrainingPeaks Premium subscription⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Parlee Cycles ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠"Whether it's a tough day, a gruelling training session, an epic road trip or sitting on the side of the road, exhausted and wondering how you'll get to the top... The answer is regularly to just get back in the saddle and ride. Ride The F...ing Bike. RTFB!"Go check out their amazing bikes at https://www.parleecycles.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠4Endurance⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Pro level fuel, made accessible. Myself and Sarah trust 4Endurance for all our fuelling needs. Their reange is HUGE and won't break the bank. Go check them out here https://4endurance.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠BIKMO⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Bikmo protects you and your bike fromtheft, accidental damage, race-day disasters, and even baggage claim shenanigans. Yourhelmet, GPS, and other kit are covered too. Got more than one bike? Of course you do – you get 50% off each extra bike on the same policy.Protect your ride before it's too late – head to ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Bikmo.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ to get covered. 

Coach Castonguay nous présente différents type d'intervalles en expliquant leur avantages, inconvénients et objectifs.  Magasinez chez Altitude Sports et économisez jusqu'à 20 % sur votre première commande avec le code UPIKA2026.  Cliquez ici pour commander

Tim McKenney & Schmitty take a deep look at skateboarding from inside their car with a ripping report of Antwuan Dixon's FTP part, The Loop Hardware STFU video, Mind Freak featuring Al Partanen, Tim's "Coping Skills", David Copperfield skating, Nyjah Huston & Bro's, "The Lipslide Heard Around the World" and more... Join "THE ONE's" and become a MEMBER: https://www.youtube.com/@TalkinSchmit/membership SUBSCRIBE NOW: https://bit.ly/2RYE75F HOSTED BY: Tim McKenney and Greg Smith EXECUTIVE DIRECTOR: Sharal Camisa Smith SMFM MUSIC DIRECTOR: Shane Medanich PRODUCED BY: ⁨@Nomad_Skateboarding⁩ ⁨@jacobstokley93⁩ ​ ⁨@BillyRabon⁩ WEBSITE: https://talkinschmit.com/ YOUTUBE: http://www.youtube.com/TalkinSchmit INSTAGRAM: http://www.instagram.com/Talkin_Schmit FACEBOOK: https://www.facebook.com/TalkinSchmit CONTACT with comments or suggestions: TalkinSchmit@Gmail.com SUPPORT OUR SPONSORS: BLOOD WIZARD http://bloodwizard.com/ BLUE PLATE http://www.blueplatesf.com/ ORO COFFEE http://www.instagram.orocoffeeroasters #Skateboarding #Podcast #NyjahHuston #AntwuanDixon #SkateNews Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Viele Trainierende beschäftigen sich mit den falschen Fragen.Sie optimieren Sets, Reps, VO2max oder FTP – ohne jemals zu klären, worauf ihr Training eigentlich abzielt.Genau hier liegt das eigentliche Problem.Denn Training ist keine reine Methodik-Frage, sondern eine Frage der Prioritäten.Du kannst nicht gleichzeitig maximale Leistung, perfekte Gesundheit und maximale Flexibilität erreichen. Trotzdem versuchen genau das die meisten – und scheitern daran.In dieser Folge zeige ich dir:warum du zuerst eine grundlegende Entscheidung treffen musstwie das Spektrum zwischen Gesundheit und Leistung wirklich aussiehtwie du dich ehrlich einordnestund was diese Einordnung konkret für dein Training bedeutetDas Ziel:Mehr Klarheit, bessere Entscheidungen und Training, das wirklich zu deinem Leben passt.---Wenn du dein Training strukturierter, athletischer und nachhaltig gestalten willst:→ Everyday Athletes Programm: https://www.kaindl-athletic-system.com/everyday-athletes-programWenn du selbst Coach bist und dein Coaching auf das nächste Level bringen willst:→ Mentoring für Coaches: Email kontakt@kaindl-athletic-system.deMehr Inhalte:→ Instagram: https://www.instagram.com/kaindlathleticsystem/→

We sit down with AFL superstar and Melbourne Demons captain Max Gawn — one of the most dominant figures in Australian sport — to talk all things footy, cycling, and high performance. Gawn has built a legacy at the highest level of the game. But what might surprise you is his deep passion for cycling. We break down the biggest races of the 2026 cycling season so far before previewing what could be an all-time Giro d’Italia. Expect insights, banter, and a crossover between two sporting worlds that don’t usually collide. This episode brought to you by TriVelo Coaching, we help triathlete and endurance athletes train smarter to race faster. Your hosts are Australian Ironman Champion Gerard Donnelly and his son, Endurance Coach Jordan Donnelly. Timestamps:0:00 – Meet Max Gawn2:02 – Phil Liggett, SBS, and Cadel's era4:04 – Saudi mountain biking & climbing Europe5:51 – The brutal reality of watching cycling from Oz10:00 – Roubaix vs Sanremo: which monument wins?12:04 – What Makes Flanders/Belgium So Special19:06 – Van Aert vs Van der Poel: has the gap closed?25:00 – Is Pogačar actually beatable?30:38 – The tactic that could finally crack him34:33 – Seixas, Vingegaard & cycling's next era39:33 – Demi Vollering's quiet domination43:42 – Cross-training with AFL46:46 – Is cycling an injury risk?49:18 – Will cycling take off at the AFL level?51:32 – Max’s Intervals vs Hill training54:43 –Melbourne’s FTP era55:54 – Fueling lessons for games56:58 – Max’s longevity goals59:39 – Giro 2026 picks & wrap-up If you want to learn how to TRAIN SMARTER and RACE FASTER, go to trivelocoaching.com.au Check us out on Instagram: https://www.instagram.com/trivelocoaching Disclaimer: The Content in this podcast is in no way intended to be medical advice, treatment or diagnoses. None of our Content is intended to imply that any products mentioned, remedies or information provided are intended to prevent, diagnose, cure or alleviate a disease, ailment, defect or injury or should be used for therapeutic purposes. The Content is intended to assist you with running, cycling, swimming or triathlon and should not be substituted for medical advice by your healthcare professional. We do not accept any liability for any injury, loss, or damage incurred by the use or reliance on our Content.See omnystudio.com/listener for privacy information.

Welcome to Channel Nine. This week we talk about Fallen Footwear's "RISE" Video, 2026 Tampa Pro, The Retail Report featuring Cassette Skateshop in Chattanooga TN, Dylan Jaeb on Quasi Skateboards, Kelly's Classic Clips featuring Brian Wenning via Video Chat, Antwuan Dixon's FTP Part and much more! Become a Channel Member & Receive Perks: https://www.youtube.com/TheNineClub/joinNine Club Merch: https://thenineclub.com Sponsored By: LMNT: Grab a free Sample Pack with 8 flavors when you buy any drink mix or Sparkling. https://drinklmnt.com/nineclub AG1: Get a FREE Welcome Kit worth $76 when you subscribe, including 5 AG1Travel Packs, a shaker, canister, scoop & bottle of AG Vitamin D3+K2. https://drinkag1.com/nineclub Woodward: Purchase camp with the code NINECLUBKIDS and receive a $150 discount off of summer camp. https://www.woodwardpa.com Monster Energy: Monster Energy's got the punch you need to stay focused and fired up. https://www.monsterenergy.com Yeti: Built for the wild, Yeti keeps you ready for any adventure. https://www.yeti.com Richardson: Custom headwear for teams, brands, and businesses crafted with quality in every stitch. https://richardsonsports.com Etnies: Get 15% off your purchase using our code NINECLUB or use our custom link. https://etnies.com/NINECLUB éS Footwear: Get 15% off your purchase using our code NINECLUB or use our custom link. https://esskateboarding.com/NINECLUB Emerica: Get 15% off your purchase using our code NINECLUB or use our custom link. https://emerica.com/NINECLUB Find The Nine Club: Website: https://thenineclub.com Instagram: https://www.instagram.com/thenineclub X: https://www.twitter.com/thenineclub Facebook: https://www.facebook.com/thenineclub Discord: https://discord.gg/thenineclub Twitch: https://www.twitch.tv/nineclub Nine Club Clips: https://www.youtube.com/nineclubclips More Nine Club: https://www.youtube.com/morenineclub I'm Glad I'm Not Me: https://www.youtube.com/chrisroberts Chris Roberts: https://linktr.ee/Chrisroberts Links We Talked About: Antwuan Dixon's FTP Part: https://youtu.be/E-mUGIqhvUY?si=amXs95wx2I35ETPj Fallen Footwear's "RISE" Video: https://www.youtube.com/watch?v=5feIolHVetE Brian Wenning Photosynthesis: https://youtu.be/chPz0alsicY?si=GtBXXs3MwaP2E9qm 2026 Tampa Pro: Finals Webcast: https://www.youtube.com/live/bbsnDw9X6Kg?si=UdPkXcJWdvQkjWiz Cassette Skateshop Website: https://www.cassetteskateshop.com Cassette Skateshop Instagram: https://www.instagram.com/cassette_skateshop The Retail Report contact email: theretailreport@thenineclub.com Timestamps (00:00:00) Channel Nine (00:02:45) Content Rundown (00:04:23) Tampa Pro 2026 (00:20:00) The Retail Report featuring Cassette Skateshop (00:47:00) Our Sponsor: LMNT (00:48:00) Kelly's Classic Clips featuring Brian Wenning (01:09:00) Fallen Footwear "Rise" video review (01:33:00) Dylan Jaeb on Quasi (01:38:00) Antwan Dixon's FTP part (01:46:00) 2% ? Learn more about your ad choices. Visit megaphone.fm/adchoices

Hoy tenemos el placer de sentar en el podcast a una de las personas más interesantes (y necesarias) del panorama ciclista en español: Sebastián Sitko.Probablemente también una de las más incómodas.Doctor en ciencias del deporte, profesor universitario, entrenador de élite y autor de más de 70 artículos científicos… pero lo que realmente diferencia a Sitko no es su currículum. Es que no se calla. Y eso, en el ciclismo, tiene consecuencias.Acaba de publicar Ciclismo 2.0, un libro basado en evidencia científica con casi 200 estudios detrás, y aprovechamos la excusa para tener una conversación profunda, directa y sin filtros sobre entrenamiento, rendimiento y muchas de esas “verdades” que damos por hechas… y que quizá no lo son tanto.Hablamos de todo: entrenamiento de fuerza, zonas, FTP, métricas como TSS o CTL, cómo debería entrenar realmente un ciclista amateur con poco tiempo, las claves de la recuperación en carreras por etapas y hacia dónde va el futuro del entrenamiento con la llegada de la IA y el análisis de datos.Pero también entramos en terreno más incómodo.Analizamos sus series más polémicas en redes como “¿Paraísos? Ciclistas”, donde destroza (con bastante criterio y bastante mala leche) algunos de los destinos más idealizados del ciclismo, y sus análisis del Tour, donde deja entrever más de lo que dice… y dice más de lo que parece.Una charla en la que intentamos entender si ese personaje que vemos en redes es estrategia… o simplemente alguien diciendo lo que piensa sin filtros.Después de la entrevista, repasamos lo más destacado de la actualidad con una París-Roubaix muy comentada, el debate sobre los relevos a Pogacar, el ambiente alrededor de Wout van Aert, novedades de material como los nuevos pedales Shimano o la tendencia hacia neumáticos más anchos.También repasamos lo que está pasando en el panorama nacional con la Copa de España y varias carreras internacionales, y cerramos con nuestras sensaciones del fin de semana en Costa Atlántica.Un episodio diferente. De los que te hacen pensar. Y seguramente, de los que generan debate.Dale al play.LINKS DE INTERÉS:LIBRO: https://sitkotraining.com/libro/INSTAGRAM: https://www.instagram.com/sitkotraining/MADRID GRAVEL TOUR: https://bicilab.es/MGT26/

Hello everyone. Welcome to the latest episode of The Matchbox Podcast powered by Ignition Coach Co. I'm your host, Adam Saban, and on this week's episode we're talking about whether or not adding weekly volume at Z3 is beneficial and should you be using those handy side bib pockets if aero is your number one concern?   As always, if you like what you hear, share this with your friends and leave us a five star review and if you have any questions for the show drop us an email at matchboxpod@gmail.com or head over to ignitioncoachco.com and fill out The Matchbox Podcast listener question form.    Alight let's get into it!   For more social media content, follow along @ignitioncoachco @adamsaban6 @dizzle_dillman @dylanjawnson @kait.maddox     https://patreon.com/MatchboxPodcast?utm_medium=unknown&utm_source=join_link&utm_campaign=creatorshare_creator&utm_content=copyLink   https://www.youtube.com/c/DylanJohnsonCycling https://www.ignitioncoachco.com  https://www.youtube.com/@DrewDillmanChannel   Intro/ Outro music by AlexGrohl - song "King Around Here" - https://pixabay.com/music/id-15045/    Summary   In this episode, hosts tackle a listener's complex training schedule that involves preparing for both trail running and ultra bikepacking, while also managing late-night training routines as a busy parent. The discussion offers actionable insights on balancing multi-discipline training, periodization, strength maintenance, and optimizing sleep and recovery.Main Topics Covered: Strategies for training simultaneously for trail running and bikepacking events The importance of periodization and training ratios (running vs cycling) Incorporating strength and mobility work effectively Managing late-night training sessions and routines as a parent The nuanced use of critical power versus FTP for training zones Tools and platforms: WKO5 vs Vekta for training analysis In this episode: We analyze how to periodize training around a 30K trail race and an 800-mile bikepacking race spaced out over months Discussion on prioritization: focusing on the main event while maintaining fitness for the secondary event The role of strength training, plyometrics, and mobility in endurance performance Tips for late-night workouts, sleep considerations, and routine creation as a parent Insights into training tools, zones, and metrics, including Vecta's adaptive zones and the W prime metric Tips for athletes balancing intense training with life's obligations Timestamps: 00:00 - Introduction to multi-discipline endurance training challenges 01:11 - Can you train effectively for both trail running and bikepacking simultaneously? 02:25 - Importance of training ratios: near 50-50 split or tailored approach 03:13 - Prioritizing running for injury prevention and muscular efficiency 04:08 - Cycling complements running; form and nutrition focus for trail run 05:38 - Periodization strategies: focusing on the main event and maintaining secondary fitness 06:48 - Incorporating strength training and its timing relative to the season 08:11 - Reducing gym volume as race approaches, maintaining strength efficiently 12:58 - Role of mobility and plyometrics in injury prevention and running performance 14:39 - Challenges of fitting training into busy schedules; structuring routine 17:49 - Impact of late-night training routines on sleep and recovery 20:50 - How to adapt training around parenting schedules; morning vs night workouts 25:33 - Coaching insights: Using Vecta and critical power zones 29:44 - Comparing training platforms: WKO5 vs Vecta 32:40 - Final tips: balance, discipline, and leveraging tools for progress  

Most people trust the system to manage their money. Rod Roudi walked away from tech to build Bitcoin Park and is now redefining financial freedom in Nashville. In this special episode of The Root of All Success, recorded live at The Standard Club in front of the Leadership Society, Jason Duncan sits down with Rod Roudi, co-founder of Bitcoin Park (a mission oriented community campus for Bitcoiners), builders, and freedom fighters. After hosting one meetup that grew from 15 people to 150 in four months, Rod left his safe tech career to bet everything on permissionless money and provable scarcity. Rod breaks down why Bitcoin is "freedom money," how it outperforms gold on divisibility, verifiability, portability, and scarcity, and why merchants should stop paying 3% to Visa when that could go straight to their bottom line instead. This conversation dives into: •The rainy night at Jackalope Brewery that started with 20 people and changed everything •How Bitcoin meetups grew from 15 to 100 to 150 people in just four months •Acquiring Florida Georgia Line's old campus in Hillsboro Village for Bitcoin Park •Why Rod left a safe tech job for a mission-oriented life he could be proud of •Bitcoin 101: Freedom money that preserves future purchasing power better than any asset •The $100 remittance story: How Western Union takes $58 before gangs take the rest •Comparing Bitcoin vs. Gold across 5 metrics: divisibility, acceptability, verifiability, portability, scarcity •Why 21 million Bitcoin is provable scarcity vs. gold's unknown supply •How you can verify the entire Bitcoin blockchain yourself with free open-source software •The magic internet money protocol missing from the internet: Bitcoin •Why your $1.93 Starbucks coffee now costs $3.57 (and Bitcoin fixes this) •The 10,000 Bitcoin pizza story: How 2 pizzas in 2010 now buys a $300k house in Bitcoin •Why merchants lose 3% to credit cards and how Bitcoin returns that to their bottom line •Defining fiat: Printable money by centralized governing bodies with no supply cap •Bitcoin as the money protocol for 8 billion people (you can't invest in SMTP or FTP, but you can own Bitcoin) •Creating an "Orange Zone" in Nashville: Bitcoin-educated community building generational wealth •Senators Hagerty & Blackburn, Governor Lee, and Tennessee's crypto-friendly leadership If you're an entrepreneur tired of losing 3% to payment processors, skeptical about Bitcoin but curious, or ready to preserve your future purchasing power in a world of inflating fiat — this episode will challenge everything you thought you knew about money.

On today's show, guest host Bert Zipperer is in conversation with scholar Gianni Cicali about the famous children's play Pinocchio and how it speaks to the vital importance of the arts during times of national crisis, from the 1930s to today. Next month marks the 200th birthday of Pinocchio's creator, Carlo Collodi. They discuss the 1930s Federal Theater Project production of Pinocchio. The play was produced by Yasha Frank with the children theater division of the WPA. The program employed people who were unemployed during the Great Depression and offered low-cost tickets so more people could access the theater. The FTP production of Pinocchio played nationwide for two years and on Broadway until June 1939 when Congress and the House Unamerican Activities Committee killed the production. Gianni Cicali is a specialist in the history of Italian theater (Renaissance, Baroque and 18th-century). He holds an Italian “laurea vecchio ordinamento” (M.A. equivalent) and doctoral degrees from both Italy (Università di Firenze) and Canada (University of Toronto). His interests focus on Italian theater, opera and culture from the 15th to the 18th century; Renaissance and Baroque religious theater; cinema; migrations to the Americas of Italian theater professionals (19th-century New Orleans). Featured image: of a photo from the Federal Theatre Project's production of Pinocchio via Library of Congress. Did you enjoy this story? Your funding makes great, local journalism like this possible. Donate hereThe post Public Theater in Times of National Crisis appeared first on WORT-FM 89.9.

In this week's episode, Coach Rob answers questions from athletes navigating the messy reality of training for an Ironman alongside work, family, and unpredictable conditions.From battling bad weather to juggling early starts, this is a practical, no-nonsense Q&A focused on what actually moves the needle.You'll learn:Whether indoor training is “good enough” (and when it isn't)How to structure back-to-back sessions when time is tightThe truth about FTP testing—and why your numbers might be misleadingHow to bridge the gap between short power and long enduranceWhat a “too high” TSS score is really telling you about your pacingWhy comparing your FTP to social media is a fast track to doubt—and what to focus on insteadSimple, high-impact ways to improve bike performance before race dayIf you're training for your first Ironman or 70.3 and trying to make it work around real life, this episode will help you stay focused on what matters and let go of what doesn't.* * * * * * *SPONSORS* * * * * * * *Thinking about your first Ironman or 70.3 in 2026? At ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Team Oxygenaddict,⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ we specialise in helping busy professionals fit high-quality training around demanding jobs and family life. We've just reopened for new athletes with only a handful of slots available. Book an application call today to find out if you'd be a good fit for Team Oxygenaddict for the coming season here: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://team.oxygenaddict.com/consultation-call/ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠* * * * * * * * * * * *⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠precisionfuelandhydration.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Precision Fuel & Hydration help athletes personalise their hydration and fuelling strategies for training and racing. Use the free ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Fuel & Hydration Planner⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ to get a personalised race nutrition plan for your next event. And then⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ book a free 20-minute video consultation⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ with a member of the PF&H Athlete Support Team to refine your strategy.Listeners get 15% off their first order of fuel and electrolytes with Precision Fuel & Hydration. Simply use code OXYGEN26 at checkout to claim your 15% discount* * * * * * * * * * * *⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Watch on youtube⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Listen on Spotify⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Listen on Apple Podcasts⁠

Join our Science of Sport Supporters Club, and get all the perks mentioned on the show, including access to our listener community and their great questions and insights, and also our Live Sport chat, which resume this weekend with the Milan San Remo races. Make a monthly pledge to become a member!In this Spotlight, we run our eye and offer our insights on the world of sport, covering a range of sporting events. We start with the Six Nations, which went beyond the wire in a spectacular tournament that shows the health of "the product". We discuss the ongoing Cape Epic, where the pairs format throws up some pacing and tactical challenges for unbalanced teams. And we preview the year's first Monument, where Tadej Pogacar will have to test and challenge Mathieu van der Poel's durability and 5-min power to win the elusive title. We discuss the requirement for Pogacar and UAE to extend the efforts above FTP and even VO2max to climbs even before the Cipressa, in order to make van der Poel vulnerable to a five minute effort on the decisive Poggio climb.Switching to running, we briefly discuss the remarkable 2:10 performance by Fotyen Tesfay in Barcelona, and why it's the de factor WR, but may be as questioned as the incumbent WR by Ruth Chep'ngetich. Another dramatic finish in Los Angeles, a marathon decided by 0.01s where the 'loser' went the wrong way, and didn't, apparently, take in a single gram of carbohydrates in the race.While on the subject of dramatic finishes, recent research shows that the odds of a cardiac arrest are significantly higher in the final kilometer of running races (20km and half marathon). We compare that to triathlons, where the odds of cardiac arrests are way higher in the first part of the race, in the swim. We discuss the physiology and emotional reasons for these risk increases.We then move into the resistance training space, to talk briefly about the American College of Sports Medicine's position stand on resistance training. It says what many people know, but challenges what a lot of people think, and the reaction has been enlightening!And finally, a few short results and discussion points from around the world of sport, including an unprecedented reversal of an entire tournament result, and a rare "defeat" (on a technicality) for Johannes Klaebo in cross-country skiingLinksRelevant to the discussion on recovery after high intensity efforts, here's an article on how our 'battery' is recharged, or reconstitutedArticle on Fotyen's 2:10:51 marathonGood insights on Fotyen from Letsrun.comThe research out of Paris showing the higher risk of cardiac events in the final kilometer of racesA similar study on cardiac arrests in triathlonThe LA Marathon finish and race are discussed in this articleThe ACSM Position Stand on Resistance TrainingStuart Phillips' posts on the ACSM Position Stand on Resistance Training Hosted on Acast. See acast.com/privacy for more information.

Rob answers listener questions covering the most common real-world training challenges for busy age-group triathletes. This week: -> How to handle training when bad weather makes outdoor riding impossible...-> Why the 20-minute FTP test beats ramp tests every time...-> How to structure an FTP block versus IRONMAN-specific training... Rob also breaks down Training Stress Score — what your TSS should actually be on a long ride and what a sky-high number is actually telling you. Plus, why your current FTP matters far less than the months of training still ahead of you.* * * * * * *SPONSORS* * * * * * * *Thinking about your first Ironman or 70.3 in 2026? At ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Team Oxygenaddict,⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ we specialise in helping busy professionals fit high-quality training around demanding jobs and family life. We've just reopened for new athletes with only a handful of slots available. Book an application call today to find out if you'd be a good fit for Team Oxygenaddict for the coming season here: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://team.oxygenaddict.com/consultation-call/ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠* * * * * * * * * * * *⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠precisionfuelandhydration.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Precision Fuel & Hydration help athletes personalise their hydration and fuelling strategies for training and racing. Use the free ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Fuel & Hydration Planner⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ to get a personalised race nutrition plan for your next event. And then⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ book a free 20-minute video consultation⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ with a member of the PF&H Athlete Support Team to refine your strategy.Listeners get 15% off their first order of fuel and electrolytes with Precision Fuel & Hydration. Simply use code OXYGEN26 at checkout to claim your 15% discount* * * * * * * * * * * *⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Watch on youtube⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Listen on Spotify⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Listen on Apple Podcasts⁠

This week, we're sharing our interview with Elia Ayoub, an anti-authoritarian historian and essayist originally from Lebanon, co-founder of From The Periphery media collective, co-host of The Fire These Times podcast and many more things. We spoke about the US and Israeli war on Iran, it's escalations into the wider region of west Asia, the Axis of Resistance, nuclear weapons, motivations of the various actors involved and thoughts on where that leaves anti-authoritarians in the imperial core countries like the US. Elia links You can contact Elia by email at ayoub@thefirethesetimes.com or on Signal at @ ayoub.02 Elia's blog ( https://www.hauntologies.net/about ) and Ko-Fi account ( https://ko-fi.com/eliaayoub ) Elia's Lebanon class: https://thefirethesetimes.com/lebanonclass/ Where you'll soon find Elias latest +972 article: https://www.972mag.com/writer/elia-ayoub/ From The Periphery Patreon: https://www.patreon.com/fromtheperiphery FTP website: https://fromtheperiphery.com/ The Fire These Times Podcast: https://firenexttime.net/why-neutral-anti-imperialism-keeps-losing/ Related Episodes: Our recent interview about Iran before the war: https://thefinalstrawradio.noblogs.org/post/2026/02/15/death-to-the-dictator-uprising-and-repression-in-iran-with-anarchism-perspective/ Past interviews we've done with Elia: https://thefinalstrawradio.noblogs.org/post/category/elia-j-ayoub/ Mutual Aid in Lebanon Instagrams featuring info on some mutual aid efforts in Lebanon: https://www.instagram.com/p/DVovwUojIYq/ https://www.instagram.com/beirutbydyke/p/DVbTtyciK7m/ Lebanon Emergency Relief: https://www.chuffed.org/project/171933-lebanon-emergency-relief A Queer Lebanese mutual aid project involving Elia's co-creator, Ayman Makruem: https://www.patreon.com/qmalebanon . ... . .. Featured Track: TFSR by The Willows Whisper

Our three most experienced coaches discuss common mistakes when training and building FTP. We look at testing, interval execution and progression, adaptation timelines, periodization, fatigue management, lactate testing, and much more. We also answer your listener questions on FTP training.

What if your computer didn't need a screen in front of you to get work done? That's the shift Ben Guo, co-founder of Zo, is building toward, and this conversation gets into the specifics of what that actually looks like day to day.In this episode of Supra Insider, Marc Baselga and Ben Erez sit down with Ben Guo to explore Zo: a personal cloud computer with built-in AI agents, file storage, scheduled tasks, and the ability to receive commands over text or email. Together, they unpack how Zo differs from the OpenClaw movement and why Ben thinks the personal cloud becomes a device category everyone eventually owns.The conversation goes deep on how the Zo team actually builds software: writing AI-generated markdown plans before touching any code, reviewing those plans as GitHub PRs, and largely abandoning the traditional to-do backlog in favor of just prompting something and letting it run. They also get into the real overhead that comes with this new way of working, including context management, delegation judgment, and figuring out what belongs where.All episodes of the podcast are also available on Spotify, Apple and YouTube.New to the pod? Subscribe below to get the next episode in your inbox

This week Kathryn catches up with cycling coach Serena Bishop Gordon. Serena has been coaching for many years, and this year she is the head coach for the Feisty Winter Cycling program. She first dives into explaining the difference between training vs exercising, and the importance of building progressive load into a training program, and reminds us that rest and recovery are key parts of the training process. With all of the options for training plans out there, it can be hard to determine which plan is right for you. Serena gives us some tips on how to determine if a plan is the right fit for your training needs. She also describes how to measure progress both within one workout, and over time. Serena and Kathryn also tackle some other common questions, like what does FTP stand for, and how do you test it? Serena's reminder to us is that if you are thinking about getting into a cycling training plan, today is the best day to start!Follow Serena on Instagram @specialblendgravel and learn more about her coaching and camps at www.specialblendgravelcamp.com/

Send a textWe break down why acronyms help experts move fast and why they lock out newcomers. We map old and new ICT terms, show how meanings shift across trades, and share a free handbook and simple rules to write clear, usable documents.• barriers created by acronym-heavy talk• MDF and IDF history and current TR and ER terms• bonding and grounding updates including TMGB to PBB and TBB IBC to BBC• multiple-meaning acronyms like AP, CO, DAS, RFI, FTP• documentation best practice: write full term, add acronym, then use• efficiency vs inclusion when speaking to mixed audiences• regional and cross-discipline differences and how to navigate them• free resource: ICT Terminology Handbook and why to share it• encouraging questions and private, kind correctionsGo to Google, type in ICT Terminology Handbook. Download it and send that web link to a peer, an installer, or an apprentice so they can learn it.Support the showKnowledge is power! Make sure to stop by the webpage to buy me a cup of coffee or support the show at https://linktr.ee/letstalkcabling . Also if you would like to be a guest on the show or have a topic for discussion send me an email at chuck@letstalkcabling.com Chuck Bowser RCDD TECH#CBRCDD #RCDD

This week on the GCN Show, we dive into the "prohibitive" cost of cycling and investigate if the sport is actually cheaper than ever thanks to a booming second-hand market. We also explore a bizarre new scientific study suggesting that training in a hot tub could significantly boost your FTP. Plus, Dan recounts the moment he was overtaken by a World Champion while riding flat-out, and we take a look at Shimano's latest "self-tightening" shoe patent.

In this episode, cycling coaches Landry and Brendan from EVOQ discuss the relevance and limitations of FTP tests in cycling training. They delve into the nuances of FTP testing, including when it might be useful, its psychological and physical preparations, and alternative methods to gauge FTP. The coaches emphasize the importance of using multiple data points to estimate FTP rather than relying solely on specific tests. They also highlight the potential drawbacks of focusing too much on testing instead of actual race performance. Tune in to get practical tips on how to navigate your FTP testing and improve your cycling performance.Don't Forget About Sportful Dolomiti in June! https://cyclinghero.wetravel.com/trips/sportful-dolomiti-race-dolomites-2026-cyclinghero-inc-59742085Also, the new Cycle Sequatchie - https://www.cyclesequatchie.com/ultra EVOQ26Chapters:00:00 Introduction to FTP Testing00:54 Meet the Coaches: Landry and Brendan01:03 The Debate: Are FTP Tests Essential?02:36 Limitations of FTP Tests10:09 Alternative Methods to Gauge FTP15:00 Signs It's Time to Increase Your FTP16:01 Final Thoughts and Recommendations19:25 Bonus Content Teaser

Our Not Done Yet Coaching Community https://www.skool.com/roadmancycling/2026Most self-coached cyclists don't struggle from lack of motivation — they struggle because they keep repeating a handful of fixable mistakes.In this video, we break down five of the biggest traps ambitious riders fall into — from overbuilding fatigue and obsessing over FTP, to misusing readiness data and relying too heavily on AI. These aren't beginner errors… they're the subtle ones that quietly cap your performance.More importantly, we'll show you how to correct each mistake with simple, practical shifts you can apply immediately.

Download the Episode Transcript in .pdf formatIn this episode of the Fund the People Podcast, you'll gain practical insights into how centering workers' perspectives -- and sharing power between employees and management -- can dramatically improve job quality in nonprofit organizations.Host Rusty Stahl sits down with Brianna Rogers and Rob Hope of Rework The Bay to unpack a bold funding experiment supported by the James Irvine Foundation and conducted in partnership with Jobs for the Future. Eight California nonprofits engaged frontline staff as participatory researchers to examine their own working conditions and to co-create improvements with their organizations' top executives.The results challenge assumptions. While compensation is foundational, workers most emphasized voice, transparency, shared leadership, professional growth, and healthier work boundaries as essential components of a quality job. The project surfaced five key lessons: workers can surface what truly matters; leaders grow when they listen; power must be intentionally shared; strategies must be tailored to organizational context; and job quality is an ongoing process—not a one-time fix.Through concrete examples—from four-day workweeks to anonymous feedback systems and participatory decision-making—this conversation offers nonprofit leaders and funders actionable ideas to advance shared leadership, transform funding practices, and elevate collective voice.Part of our ongoing California Voices Series, this episode is a roadmap for anyone committed to building nonprofit workplaces where staff can thrive—and where stronger internal culture leads to stronger community impact.Speaker Bios:ReWork the Bay Initiative Officer Brianna Rogers partners on ReWork's fundraising efforts and leads our systems change projects focused on building worker power, workforce training and advancing job quality. Brianna grew up in Berkeley, attended Berkeley City College where she served as one of two student delegates to the Peralta Community College District, then transferred to UC Berkeley as a first-generation, re-entry student parent, earning her bachelor's degree in Rhetoric Studies. While at UCB, Brianna developed innovative programming for the UC Berkeley's African Student Development Center and the Department of Equity and Inclusion. She went on to receive her master's degree from the McCourt School of Public Policy at Georgetown University, got her start in philanthropy as a National Urban Fellow at the Andrus Family Fund in New York City. In October 2020, she joined the San Francisco Foundation's Partnership for HOPE SF team, where she worked until joining the ReWork team in 2022.ReWork the Bay Director Rob Hope is responsible for leading execution of ReWork the Bay's strategy, as well as fundraising, grantmaking, budget management and partnership building. Rob joined ReWork the Bay in October 2017, after serving as Chief Program Officer at Rubicon Programs. Prior professional experience includes all levels of workforce development direct services, program evaluation and policy analysis, and community building work. Rob has a Bachelor's in Sociology from Vassar College and a Master's in Public Policy from UC Berkeley.For more on Brianna and Rob, visit the staff page of ReWork the Bay.Links to Resources Discussed:Featured Initiative:Rework The BayJob Quality Project Report (June 2025)Project Partners:Jobs for the FutureThe PATH GroupFunding PartnerJames Irvine FoundationHost Organization:San Francisco FoundationParticipating Nonprofits Highlighted in the Episode:Canal AllianceCreating Restorative Opportunities and Programs (CROP)Related Fund the People Resources:Playlist for FTP Podcast's CA Voices SeriesReport on FTP's 2024-25 California ConveningsFTP Podcast Premium on PatreonFund the People - A Podcast with Rusty StahlFund the People WebsiteListen to this episode:This Episode on Apple PodcastsThis Episode on Spotify

OVERVIEWCyclists almost always report a discrepancy between the power output and/or perceived exertion between indoor and outdoor cycling. Typically, this means struggling to achieve the same power output indoors than can be achieved outdoors for common workouts like FTP intervals or VO2 max efforts. Even easier Zone 2 rides can have higher RPE values (i.e., feel harder) indoors compared to outdoors. In Episode 294 of "The Time-Crunched Cyclist Podcast", Coach Adam Pulford reveals why indoor cycling feels harder, how you can narrow the gap between indoor and outdoor performance, and whether you should use different power training zones indoors vs outdoors.TOPICS COVEREDWhy indoor cycling feels harder than outdoor ridingWhich types of cycling workouts are affected more by moving indoorsHow to narrow the gap between indoor and outdoor performanceWhen to make different indoor and outdoor power training zonesRESOURCES Indoor vs Outdoor Power ExplainedKnowledge is Watt: https://www.instagram.com/knowledgeiswatt/- Indoor vs Outdoor Power post Can a Mismatch Between Course Gradient and Resistance Affect Performance When Using ERG Mode in a Zwift Workout? ASK A QUESTION FOR A FUTURE PODCASTHOSTAdam Pulford has been a CTS Coach for nearly two decades and holds a B.S. in Exercise Physiology. He's participated in and coached hundreds of athletes for endurance events all around the world.Listen to the episode on Apple Podcasts, Spotify, Stitcher, Google Podcasts, or on your favorite podcast platformGET FREE TRAINING CONTENTJoin our weekly newsletterCONNECT WITH CTSWebsite: trainright.comInstagram: @cts_trainrightTwitter: @trainrightFacebook: @CTSAthlete

Send Me a Text MessageA new FTP is cause for celebration — especially when it proves that getting fitter after sixty isn't just possible, it's happening. Tom Butler shares his latest benchmark and what it means for anyone who thinks their best fitness days are behind them.Then, Tom sits down with Beverly Meyer, host of the Primal Diet - Modern Health podcast and a seasoned Clinical Nutritionist and Functional Health Expert. Beverly offers a refreshing lens on what it truly means to be healthy, explaining the functional health approach and why it looks beyond symptoms to uncover root causes. At the heart of the conversation is a deceptively simple idea: Eat Like a Human Being. Beverly unpacks what that means in practice and why it may be one of the most powerful things you can do for your long-term health and vitality.Whether you're chasing watts or just trying to feel better in your daily life, this episode delivers both inspiration and practical wisdom.LINKSTour de Cure Routes: ridewithgps.com/events/455983-2026-pnw-tour-de-cureBeverly's Podcast: ondietandhealth.com/resources/Beverly's Website: ondietandhealth.comHere is your invitation to join a great launch party for the summer cycling season.  Join the Cycling Over Sixty Tour de Cure PNW team.  Whether you are local or come out to experience cycling in the great Northwest, I would love to have you help make this a ride with a purpose.  And to send a message that the joy of cycling is here for everyone, regardless of age. Go to tour.diabetes.org/teams/CO60I know it is early but we are looking to get the Cycling Over Sixty Tour de Cure team together as soon as possible. You can find all the info at tour.diabetes.org/teams/CO60 Thank you Konvergent Wealth for sponsoring CO60 Jerseys for the Tour de Cure! Become a member of the Cycling Over Sixty Strava Club! www.strava.com/clubs/CyclingOverSixty Cycling Over Sixty is also on Zwift. Look for our Zwift club! NOTE: I share information about my journey. From time to time that means sharing what I do to stay healthy. None of what I share is meant to be medical advice. Always consult with your physician or other health professionals before making changes. Please send comments, questions and especially content suggestions to me at info@cyclingoversixty.com Follow and comment on Cycling Over Sixty on Instagram: https://www.instagram.com/cyclingoversixty/ Show music is "Come On Out" by Dan Lebowitz. Find him here : lebomusic.com

This week, we're unpacking all the latest news from the world of Peloton. We start with the business side of things, discussing the date for the upcoming earnings call. Then, we dive into some community news, including a security breach in the Peloton Singles Group and how the Power Zone Pack is leveraging AI for FTP tests.We'll also cover Peloton's big moves, like its presence at the Sundance Film Festival and the introduction of two brand-new badges. Plus, there are updates on the app, instructor news, and a breakdown of the latest artist collaborations, including features with Tyler The Creator, Magic Mike, and Destiny's Child. It's a packed episode with all the Peloton and fitness news you need to know.Peloton announces the date for its next earnings call.The Peloton Singles Group was reportedly hacked.The Power Zone Pack is experimenting with AI to help determine your fitness FTP.Peloton is heading to the Sundance Film Festival.Two new badges have been debuted by Peloton.The Autoplay feature has been added to the Peloton app.A Peloton Bike was spotted in the Netflix movie Finding Her Edge.Peloton Streetlight (PSL) is hiring a Production Manager.Kirra Michel is scheduled to attend the Yoga Telluride Festival.Nico Sarani provides an update from Germany.Zacharias Jensen (ZACK) makes his official Strength debut.Ash Pryor was featured on the NBC affiliate in Columbus, OH.Rebecca Kennedy & Cody Rigsby spoke at a Twin Health event.The latest Peloton artist series features Tyler The Creator.Tunde Oyeneyin has a special Magic Mike-themed ride.Destiny's Child classes are now on the schedule.An update on iFit's Amazon Prime reality show.Snooki reveals she had cancerous cells removed.Tonal & Kristin McGee are hosting a new Pilates challenge.Lululemon has stopped sales of some of its popular leggings.The Clip Out Top Five weekly recap.This Week at Peloton: A look at the week's fitness schedule.TCO Radar: Classes The Clip Out team is looking forward to.Mariana Fernandez led a Holding Space meditation class.Bench classes now have their own dedicated collection (sort of).Get ready for the big game with the Super Burn class collection.A new class type has been introduced: Retro Reise.Peloton Birthdays: Daniel McKenna (2/4).See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

In this episode of the Oxygenaddict Triathlon Podcast, Coach Rob Wilby answers 10 listener questions about Ironman training for busy age-group triathletes, especially athletes juggling work travel, family commitments, and limited training time.If you feel like you're constantly cramming sessions, missing workouts, or unsure what to prioritise, this Q&A will help you simplify your training, protect your recovery, and stay consistent all the way to race day.Topics covered include:How to structure a repeatable Ironman training week when life is hecticThe “4 key sessions” framework (what matters most when you're busy)What to do after a disrupted week (travel, missed bike sessions) — and why not to “make up” workoutsHow close you can place hard sessions together without compromising recoveryWhether a half / full marathon during an Ironman build helps or harms performanceWhen to retest FTP and why testing is about training accuracy (not ego)“My training hasn't gone to plan” - do I still have enough time before Ironman?How to approach a 70.3 as a B-race before your Ironman (race vs rehearsal vs training day)When to shift into race-specific Ironman preparationHow to know if training is working when you don't feel fitter week to weekA simple way to judge readiness using consistency metrics This episode is a practical, no-fluff guide to training smarter, so you arrive healthy, confident, and ready to execute on race day.* * * * * * *SPONSORS* * * * * * * *Thinking about your first Ironman or 70.3 in 2026? At ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Team Oxygenaddict,⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ we specialise in helping busy professionals fit high-quality training around demanding jobs and family life. We've just reopened for new athletes with only a handful of slots available. Book an application call today to find out if you'd be a good fit for Team Oxygenaddict for the coming season here: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://team.oxygenaddict.com/consultation-call/ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠* * * * * * * * * * * *⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠precisionfuelandhydration.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Precision Fuel & Hydration help athletes personalise their hydration and fuelling strategies for training and racing. Use the free ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Fuel & Hydration Planner⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ to get a personalised race nutrition plan for your next event. And then⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ book a free 20-minute video consultation⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ with a member of the PF&H Athlete Support Team to refine your strategy.Listeners get 15% off their first order of fuel and electrolytes with Precision Fuel & Hydration. Simply use code OXYGEN26 at checkout to claim your 15% discount* * * * * * * * * * * *⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Watch on youtube⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Listen on Spotify⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Listen on Apple Podcasts⁠

Learn more about TrainerRoad AI: ⁠https://www.trainerroad.com/blog/introducing-trainerroad-ai/⁠Learn more about the updated AI FTP Detection: ⁠https://www.trainerroad.com/blog/why-is-ai-ftp-detecting-an-ftp-change/⁠// SHARE AND RATE THE PODCAST!iTunes: ⁠https://trainerroad.cc/apple2⁠ Spotify: ⁠https://trainerroad.cc/spotify2⁠Google Podcasts: ⁠https://trainerroad.cc/google⁠// TOPICS COVERED(00:00:00) Welcome! TrainerRoad AI Q&A with Nate Pearson(00:00:54) How is TrainerRoad actually using AI (and what it's not doing)(00:05:26) Why TrainerRoad uses custom AI instead of ChatGPT-style models(00:10:11) How TrainerRoad AI really uses FTP (and why FTP is “functional”)(00:13:08) The biggest misconceptions about FTP testing and accuracy(00:22:31) Why TrainerRoad AI doesn't rely on FTP or progression levels internally(00:28:52) Why your FTP might go down with AI Detection (and why that's OK)(00:36:55) Why more training doesn't always make you faster(00:42:19) Why your predicted FTP can change suddenly after a workout(00:50:47) How to use progression levels and workout levels with AI training(00:56:24) Do post-workout surveys still matter with TrainerRoad AI?(01:01:26) Can TrainerRoad tell if you barely survived a workout?(01:03:28) Why your workouts keep changing on the calendar(01:08:12) What AI Predicted Difficulty and failure percentage actually mean(01:16:30) How long it takes TrainerRoad AI to feel dialed in(01:18:43) What yellow and red days mean (and when to ignore them)(01:20:50) How to use workout alternates with TrainerRoad AI(01:21:10) What to do if you miss workouts or get sickCoach Jonathan sits down with CEO Nate Pearson to answer the biggest questions athletes have about TrainerRoad AI, pulling back the curtain on how it actually works and what it means for your training. They explain why TrainerRoad's AI isn't a chatbot or large language model, but a purpose-built system trained on tens of millions of workouts and rides to predict the right workout for the right day, with guardrails that avoid “AI slop.” The conversation dives deep into FTP—why the AI doesn't truly use FTP the way athletes think, why FTP can go down without fitness going down, and how precision and consistency matter more than chasing a number. They also cover progression levels, post-workout surveys, predicted difficulty, yellow and red days, missed workouts, illness, and why plans change dynamically as you train. Throughout, the focus stays on what matters most: progressive overload, recovery, and building fitness you can actually use, with practical advice to help athletes trust the system, train smarter, and keep getting faster over time.// RESOURCES MENTIONED- Sign up for TrainerRoad! ⁠https://trainerroad.cc/GetFaster⁠- Follow TrainerRoad on Instagram

Our coaches dig into non-FTP related aspects of training and physiology that that lead to better race results, and workouts that can be done for each. We specifically consider road racing, criteriums, mountain bike and cyclocross, plus gravel and ultra racing, and a couple things to train that can easily apply to everything.