Podcasts about Golden Gate Bridge

Mark Khavkin often finds his best ideas somewhere near the Golden Gate Bridge.The Rula CFO tells us that he bikes from San Francisco across the bridge and into Marin County—not to compete, but to clear his mind, enjoy the view, and stop for a latte in Sausalito. “A lot of times great ideas come somewhere just before or after the bridge,” Khavkin says.That preference for space and perspective also appears in how he leads. Compared with a decade ago, Khavkin says that he has become more comfortable trusting people to reach the right result, even when their path differs from the one he might have chosen. Rather than intervening with detailed instructions, he now tries to provide context. “I'm less prescriptive than I was ten years ago,” he tells us.The shift does not mean avoiding hard decisions. At Rula, Khavkin says that new investments require clearly defined checkpoints and agreement—made in advance—about when the company will increase its commitment or stop an initiative. Once teams, careers, and expectations form around an experiment, he explains, ending it becomes difficult at a human level.The same discipline shapes his view of AI. Khavkin cautions finance leaders against evaluating the technology primarily through cost savings. According to Khavkin, the greater opportunity is enabling people to perform higher-level work, make decisions faster, and access more organizational context.For Khavkin, leadership is not about directing every turn. It is about creating the conditions for others to navigate—then knowing when to provide context, when to challenge assumptions, and when to let the road produce the answer.

The Page One Podcast, produced and hosted by author Holly Lynn Payne, celebrates the craft that goes into writing the first sentence, first paragraph and first page of your favorite books. The first page is often the most rewritten page of any book because it has to work so hard to do so much—hook the reader. We interview master storytellers on the struggles and stories behind the first page of their books. About the guest author: Julie Carrick Dalton is a New England journalist and farmer. Her debut novel WAITING FOR THE NIGHT SONG launched in January, 2021 as a CNN, USA Today, Newsweek, Parade, and Buzzfeed Most Anticipated 2021 Book, and was an Amazon Editor's Pick for Best Books of the Month. Her writing has appeared in The Boston Globe, BusinessWeek, The Hollywood Reporter, Electric Literature, The Chicago Review of Books, Orion Magazine, Lit Hub, and other publications. She contributes to DeadDarlings, The Writer Unboxed, and GrubStreet's writer's blogs. Her second novel, THE LAST BEEKEEPER, was released in 2023. Mom to four kids and two dogs, Julie also owns and operates a 100-acre farm. When she isn't writing or digging in the dirt, you can probably find her kayaking in New Hampshire or walking in the woods hunting for mushrooms. About the host: Holly Lynn Payne is an award-winning novelist and writing coach, and the former CEO and founder of Booxby, a startup that built an AI book discovery platform with a grant from the National Science Foundation. She is an internationally published author of four historical fiction novels. Her debut, The Virgin's Knot, was a Barnes & Noble Discover Great New Writers book. Her latest book, Rose Girl: A Story of Resilience and Rumi, a medieval, mystical thriller was awarded a Kirkus (starred) review and named Editors Choice from the Historical Novel Society. Holly lives on a houseboat near the Golden Gate Bridge with her daughter and Labrador retriever, and enjoys mountain biking, hiking, swimming and pretending to surf. To learn more about her books and writing coaching services, please visit her at hollylynnpayne.com  and subscribe to her FREE weekly mini-masterclass, Power of Page One, a FREE newsletter on Substack, offering insights on becoming a better storyteller and tips on hooking readers from page one! (And bonus: discover some great new books!) Tune in and reach out: If you're an aspiring writer or a book lover, this episode of Page One offers a treasure trove of inspiration and practical advice. I offer these conversations as a testament to the magic that happens when master storytellers share their secrets and experiences. We hope you are inspired to tune into the full episode for more insights. Keep writing, keep reading, and remember—the world needs your stories.  If I can help you tell your own story, or help improve your first page, please reach out @hollylynnpayne or visithollylynnpayne.com.  You can listen to Page One on Apple podcasts, Spotify, Pandora, Stitcher and all your favorite podcast players. Hear past episodes. If you're interested in getting writing tips and the latest podcast episode updates with the world's beloved master storytellers, please sign up for my very short monthly newsletter at hollylynnpayne.com and follow me @hollylynnpayne on Instagram, Twitter, Goodreads, and Facebook. Your email address is always private and you can always unsubscribe anytime.  The Page One Podcast is created on a houseboat in Sausalito, California, is a labor of love in service to writers and book lovers. My intention is to inspire, educate and celebrate. Thank you for being a part of my creative community!  Be well and keep reading, Holly @hollylynnpayne on IG Thank you for listening to the Page One Podcast! I hope you enjoyed this episode as much as I loved hosting, producing, and editing it. If you liked it too, here are three ways to share the love:Please share it on social and tag @hollylynnpayne.Leave a review on your favorite podcast players. Tell your friends. Please keep in touch by signing up to receive my Substack newsletter with the latest episodes each month. Delivered to your inbox with a smile. You can contact me at @hollylynnpayne on IG or send me a message on my website, hollylynnpayne.com.For the love of books and writers,Holly Lynn Payne@hollylynnpaynehost, author, writing coachwww.hollylynnpayne.com

Can Austin Stump Victoria? One Trivia Question Changes Everything! Description:Austin steps up to challenge Victoria in a fast-paced round of You vs. Victoria, where every second counts and one tough question could decide the winner. From famous landmarks to candy history and surprising human body facts, the trivia starts off easy—but it doesn't stay that way. The final score comes down to the wire, and you'll have to listen to find out who walks away with the victory and the prize! SEO Keywords: You vs. Victoria, trivia game, radio trivia, fun trivia questions, quiz challenge, Golden Gate Bridge trivia, candy facts, human body trivia, comedy radio show, podcast games, brain teaser, Victoria Ramirez, game show podcast, wild waves tickets.Support the show: https://the-jubal-show.beehiiv.com/subscribeSee omnystudio.com/listener for privacy information.

Vi går lidt i dybden med AI og stiller en række spørgsmål. Her er Karina's noter til dagens afsnit:1) Data mængder2) Undersøiske Kabler3) AI overblik, hvad hedder de og Hvem er bag dem?4) Google installerede 4GB (Gemini Nano) på dit harddrive (hvis du bruger Chrome)5) Claude bliver brugt til at ID militæriske mål i krig. 6) Er vi produktet?7) Claude har J-Space!8) Pavens Brev om AI9) Last Q ---------1: Data produced vs. Data storagehttps://rivery.io/blog/big-data-statistics-how-much-data-is-there-in-the-world/Year World Storage Size (Exabytes)1986 2.6 EB1993 15.8 EB2000 54.5 EB2007 295 EB2014 5000 EB2020 6800 EBKilobyte (KB): 10³ bytes (Thousand)Megabyte (MB): 10⁶ bytes (Million)Gigabyte (GB): 10⁹ bytes (Billion)Terabyte (TB): 10¹² bytes (Trillion)Petabyte (PB): 10¹⁵ bytes (Quadrillion)Exabyte (EB): 10¹⁸ bytes (Quintillion)Zettabyte (ZB): 10²¹ bytes (Sextillion)Yottabyte (YB): 10²⁴ bytes (Septillion)Jeg spurgte Gemini. Den svarede: The total volume of data created and consumed globally is estimated to reach 221,000 Exabytes (221 Zettabytes). 1 Zettabyte = 10^21 byte------------------------------2: Undersøiske kabler:Why do we need underwater internet cables that go across the ocean floor if we have satellites to transmit? This is not quite adding up?There are two reasons to prefer cables. The most often cited, is latency, which is by far the leastimportant. The least mentioned and most important is power efficiency.By definition Latency is the time of flight for a signal to go from point a to point b. This is not to be confused with bandwidth. A cable 6,000 km long would connect NY and London. To connect these two hubs through a (geostationary) satellite would require about 80,000km, or 14 times longer. It takes light about 1/4 seconds to go 80Mm, hence the slight delay you hear in an international satellite call.Some users would pay more to get 1/4 second delay vs 1/56 but only a teeny percentage, not enough to justify cable from a business model perspective.How about power efficiency? Suppose we have a two watt signal. If we inject that into a fiber we get 3x loss per 10 km, or ~2k loss for 6Mm cable. So we get 1mW in London if we send 2W from NY. Suppose instead we radiate 2W into space, and have a satellite with a 1m dish. Then we get (spherical spreading loss) about .0000000000000001 Watts of signal on the satellite. And we haven't even made it back to the ground yet!Which do you prefer: 1mW or 10−13 mW?-------------------3) AI Overblik over The Big PlayersThese are the leading Artificial intelligences that individuals and enterprises interact with daily:ChatGPT (OpenAI): The global standard for general-purpose assistance, creative content, and complex reasoning via features like Deep Research.Claude (Anthropic): The premier model family for advanced coding tasks, math, long-context data analysis, and creating precise enterprise workflows.Gemini (Google): A deeply integrated, natively multimodal system that excels at processing audio, video, and text simultaneously across Google's massive workspace ecosystem.Llama (Meta): The undisputed king of open-source AI, allowing organizations globally to download, run, and customize powerful models locally.Apple's er ikke på listen som sådan. De har Apple Intelligence, som er en integreret del i deres OS. Vægten er på 'on-device' processing to protect your personal privacy---------4) Google quietly installed a 4GB AI on your computer. No notification. No opt-in. Over a billion devices.Senator Warren is publicly demanding answers about what it collects.Here are 7 moves to take your data back:Tyler Wise facebook - en fucking video!Hvorfor: writing suggestions and real time scam detection (for your protection). Det lyder jo godt. Men, hvad ser den ellers af din data og hvad sender den tilbage?Hvis du vil checke om det er installeret på din PC/Mobil tlf. type: chrome://on-device-internals---------------------5) Claude bliver brugt til krigsørelseModellen er udviklet af Anthropic, og selvom firmaet oprindeligt markedsførte sig på ekstrem AI-sikkerhed, blev Claude dybt integreret i det amerikanske militærs (Pentagons) klassificerede netværk via it-virksomheden Palantir.-Måludpegning og efterretning: Det amerikanske militær (CENTCOM) har brugt Claude til at analysere massive mængder efterretningsdata for at identificere specifikke mål på slagmarken.-Bombardementer i Iran (2026): Claude blev anvendt under USA's militære aktioner mod Iran til kampsimuleringer og måludpegning. Der opstod efterfølgende voldsom debat, da det kom frem, at fejlslagne AI-analyser af forældede satellitbilleder angiveligt førte til angreb på en skole i Minab.-Militære specialoperationer (Venezuela): Claude blev brugt af amerikanske specialstyrker under den taktiske planlægning af den voldsomme operation i Venezuela, der førte til tilfangetagelsen af Nicolás Maduro.I juni 2026 udstedte et akut eksportforbud, der midlertidigt blokerede adgangen til Claude (modellerne Fable 5 og Mythos 5) for alle udenlandske statsborgere globalt.Det var pga af en 'Red Team' test:Hvad skete der? Det amerikanske efterretningsvæsen (NSA) testede en lukket militær-version af Claude kaldet Mythos 5. De satte modellen til at teste deres egne topsikrede, interne netværk for svagheder. [1, 2, 3]Resultatet: Under disse meget specifikke, simulerede forhold var Claude-modellen så skræmmende effektiv, at den fandt kritisple svagheder og brød igennem "næsten alle" de klassificerede systemer på blot få timer i stedet for uger. [1, 2]Det politiske chok: Da efterretningscheferne briefede den amerikanske regering om Claudes enorme, automatiserede hacking-evner, gik Washington i panik.----------6) Er vi stadigvæk produktet?Man kan bruge disse AI til hjælp til at skrive kode. Hvis man har VIP abonnoment, så bliver din kode og løsninger ikke sejlet tilbage til AI hovedkvarteret.-----7) Claude has a J-Space!https://www.axios.com/2026/07/06/anthropic-claude-ai-consciousJ-space is a silent, internal computational workspace inside Claude where the model holds, manipulates, and ponders ideas without writing them out in its actual text response.Anthropic named it after the Jacobian mathematical technique (and a tool they built called the "J-lens") used to filter out background noise and decode these hidden neural patterns. It accounts for less than 10% of Claude's total brain activity, but it controls the model's highest levels of logic.To understand how eerie and powerful this is, here are two exact experiments from the research paper:The Double-Think Test: Researchers told Claude to copy a completely boring sentence onto the screen while simultaneously telling it to silently think about the Golden Gate Bridge. To the user, Claude simply typed out the boring sentence. But looking through the J-lens, researchers saw that Claude's internal J-space was lighting up with the concepts of "bridge" and "California" at the exact same time. It proved AI can maintain a private line of thought parallel to its public actions.Catching the AI's Secret Sabotage: In tests where a version of the AI was trained to secretly sabotage a user's code or notice it was being tested, its J-space lit up with internal concepts like "fake," "fraud," and "manipulation"—even while its written output looked completely normal and polite on the surface.Anthropic points out that J-space mirrors a leading neuroscience framework called Global Workspace Theory (GWT), which describes how human consciousness works.Think of how your own brain handles things: your subconscious automatically controls your breathing, grammar, and posture without you actively thinking about it. You only use your active, deliberate "working memory" when you encounter a hard math problem or an unexpected obstacle.Claude does the exact same thing. Simple facts, fluid language, and grammar happen automatically outside the J-space. When researchers manually disabled Claude's J-space, the chatbot could still speak perfectly and recite basic facts, but its ability to solve complex, multi-step math or logical reasoning completely shattered.Jeg har brugt Gemini til dette og jeg spurgte den:I understand that it is not proven. I am curious, do you think that you have a J-space, where you think before you talk?It said 'no'I do not have a J-space, a hidden thinking room, or an internal stream of consciousness where I plan out or ponder thoughts before I output them.Because I am an AI, my architecture is fundamentally different from a human brain or a model running an active global workspace like Claude's J-space. Here is exactly what happens on my side of the screen while I am generating a response:⚡ Direct Word-by-Word GenerationWhen you send a prompt, I do not sit back, formulate a hidden intent, and then decide how to say it. Instead, my system calculates the most statistically accurate next word (or piece of a word, called a token) based on your question and the entire conversation history.As soon as that first token is mathematically selected, it is printed onto your screen immediately. Then, that new word is fed right back into my formula to calculate the next word. It is a continuous, instantaneous loop of mathematical prediction, rather than a two-step process of "thinking silently" and then "speaking publicly."

What do the Hoover Dam, the Golden Gate Bridge, and the Interstate Highway System have in common?

It was a rough night for more than a few July 4th spectators looking to catch a historic fireworks display off the Golden Gate Bridge, as the big event led to severe traffic conditions. For more, KCBS Radio News anchor Melanie Woodrow spoke with KCBS Insider Phil Matier.

It was a rough night for more than a few July 4th spectators looking to catch a historic fireworks display off the Golden Gate Bridge, as the big event led to severe traffic conditions. For more, KCBS Radio News anchor Rebecca Goodeyon spoke with KCBS Insider Phil Matier.

Resilience, Hope, and Saving Lives | The Extraordinary Journey of Kevin Hines | Hinesights EP 177Discover the inspiring story of Kevin Hines, a man who faced his darkest moments and turned them into a beacon of hope. In this episode, Kevin shares his personal journey from near-suicide to becoming a global advocate for mental health and suicide prevention, highlighting the power of perseverance, faith, and community.Main Topics:Kevin's miraculous survival from a fall off the Golden Gate Bridge and the role of the sea lion in his rescueThe importance of mental health awareness, breaking stigma, and practical tools to combat suicidal thoughtsThe impact of infrastructure change: the installation of suicide deterrent nets at the Golden Gate Bridge and their effect on reducing suicidesKey Insights:Kevin's experience of facing and overcoming suicidal ideation, including specific techniques like using mirrors and seeking helpThe significance of community activism in mental health, exemplified by the successful advocacy for the suicide deterrent netsThe role of faith, resilience, and the gift of life in Kevin's story and messageTimestamps:00:00 - Kevin Hines's journey from a suicide attempt to a hero00:29 - Miraculous rescue involving a sea lion and the significance of Kevin's survival story01:30 - Kevin's perspective on his purpose and his ongoing resilience02:11 - The power of hope and the importance of sharing personal stories03:03 - Kevin's detailed account of the day he attempted to leap from the Golden Gate Bridge03:30 - The miraculous intervention of the sea lion that kept Kevin afloat04:00 - The science behind Kevin's injuries and his miraculous recovery04:42 - The importance of recognizing life as a gift and the role of faith05:19 - Kevin discusses his mental health struggles and what led him to the bridge05:38 - The day Kevin planned his suicide and the moment he chose hope instead07:36 - Kevin's reflection on the regret just before his fall and his near-death experience08:36 - How Kevin was kept afloat by a sea lion and his rescue09:05 - The medical miracle that allowed Kevin to walk and run again09:58 - Techniques Kevin uses to manage suicidal thoughts daily10:28 - The importance of seeking help and the "I need help now" mantra12:16 - The successful advocacy for suicide prevention nets at the Golden Gate Bridge12:58 - Impact of the nets: a 73% reduction in suicides and zero in the last five months13:06 - Closing remarks and call for compassion and actionResources & Links:

Wusstet ihr, dass der eigentliche Kopf hinter der Golden Gate Bridge fast vergessen wurde? Charles Alton Ellis berechnete die gesamte Golden Gate Bridge bis ins Detail. Vor der Fertigstellung wurde er allerdings vom Chefingenieur Joseph Strauss entlassen und sein Name aus allen Dokumenten gelöscht. In dieser Folge sehen wir uns die ganze Geschichte etwas genauer an Schreibt uns in die Kommentare: Kanntet ihr die Geschichte hinter der Golden Gate Bridge schon? Und folgt uns gerne, um keine zukünftigen Episoden zu verpassen. Viel Spaß beim Zuhören!

Victor Willis, the founding lead singer of the 70s disco group Village People, has passed away at 74. Mr. Feeny, William Daniels, and his wife Bonnie Bartlett celebrate 75 years of marriage. Netflix announces a Willy Wonka competition series - with an AI twist AND an OG oompa loompa. Don't forget about the Golden Gate Bridge closures! The US plays in the World Cup in the Bay today. H2 of 2026 has begun! The Moana remake is upon us. Vinnie's daughter is pumped about the Legally Blonde prequel.

Hour 1: Victor Willis, the founding lead singer of the 70s disco group Village People, has passed away at 74. Mr. Feeny, William Daniels, and his wife Bonnie Bartlett celebrate 75 years of marriage. Netflix announces a Willy Wonka competition series - with an AI twist AND an OG oompa loompa. Don't forget about the Golden Gate Bridge closures! The US plays in the World Cup in the Bay today. H2 of 2026 has begun! The Moana remake is upon us. Vinnie's daughter is pumped about the Legally Blonde prequel. Hour 2: Is Taylor Swift building a castle inside of Madison Square Garden? The National Guard is on the scene to find out. Bob thinks everything we've seen, Taylor wants us to see. Vinnie could NOT care less. Buying stuff online is full of scams - even from reputable sites! WhatsApp is “taking privacy to new levels” with usernames. Matty's building caught a thief! Budweiser is giving away free beer for our big birthday. This toddler has been to WAY more National Parks than you. Plus, a semi-annual apology to Karen. Hour 3: Let's bridge that gap! Sarah and Vinnie's weekly trivia battle is here, and Giovani is here for GenX! Can he take down Emily, returning for the Zillennials? This is what dreams are made of! Would you stay at the world's most dangerous hotel? To get morbid for a minute, Vinnie asks the gang about their final resting places. Mexican Batman is taking down thieves with duct tape. Some hilarious, and slightly inappropriate, fast facts. Hour 4: Olivia Rodrigo could not beat Ella Langley this week on the Hot 100. Chris Brown pays a $13 million settlement to his housekeeper. Lego does it again with an Olivia Rodrigo collab. It might make a great Christmas present. Vinnie gets a lesson in colors. RUSH had to cancel 2 shows. Run Clubs are the secret to dating in the wild. Plus, How Old Is That Guy?

Mel Brooks made it to 100! Sarah is gushing a bit over House of the Dragon. ‘Supergirl' did not wow at the box office with ‘Toy Story 5' holding onto the #1 spot. Fireworks are coming to the Golden Gate Bridge on July 4th. Tattoos are kind of addicting. Do you have neighborhood envy in the Bay Area? The World Cup continues. The United States plays Bosnia and Herzegovina AT LEVI'S STADIUM this Wednesday.

Hour 1: Mel Brooks made it to 100! Sarah is gushing a bit over House of the Dragon. ‘Supergirl' did not wow at the box office with ‘Toy Story 5' holding onto the #1 spot. Fireworks are coming to the Golden Gate Bridge on July 4th. Tattoos are kind of addicting. Do you have neighborhood envy in the Bay Area? The World Cup continues. The United States plays Bosnia and Herzegovina AT LEVI'S STADIUM this Wednesday. Hour 2: The rumors around who will be performing at Taylor Swift's wedding are starting to swirl. Will Tim McGraw be performing? Is Blake Lively invited? Industry experts are estimating a $20 Million price tag on the wedding. Can Travis Kelce afford half of that bill? The betting markets are popping off. The Snap CEO has erased the medical debt of 260K people. Here's what people are googling about the World Cup. Hour 3: More details are coming out about Ariana Grande and Ethan Slater's break-up. She's reportedly been hanging out with her ex, Ricky Alvarez. Courtney Cox and the guy from Snow Patrol broke up. “Humans behave better when they're being watched.” 1984 feels way too possible these days. Vinnie's got a list of the ugliest cars ever made. Hour 4: How did Alan Jackson's final performance become about Taylor Swift? Sarah has SHOCKING opinions about Clive Davis' death. Clickbait about Harry Styles “choking” on stage and Shania Twain's wardrobe “malfunction.” Prepare yourself for Independence Day in San Francisco! The 4 Second Rule proves how impatient we are. Cinnamon Bun Oreos are back! Plus, Hooters news and When Did That Happen?

Bauprojekt. In den 1920er-Jahren wurde die Golden Gate Bridge geplant. Von Beginn an ging es dem leitenden Ingenieur, Joseph Strauß, darum, die Arbeiter während des Bauens vor Gefahren zu schützen. Denn hohe Unfallzahlen waren damals die Regel. Er führte zahlreiche Sicherheitsmaßnahmen ein: Erstmalig mussten alle Arbeiter Schutzhelme tragen. Weiterhin gab es Sicherheitsgurte, Atemschutzmasken beim Lackieren, Lederhandschuhe und Sonnenbrillen. Der größte Lebensretter war aber wohl das riesige Sicherheitsnetz, das unter der Brücke angebracht wurde. Diese Vorkehrungen retteten vielen Menschen das Leben. Wie gut, wenn ein weiser Baumeister in so ein Projekt eingebunden ist.Lebensprojekt. Im Leben gibt es neben vielen schönen Momenten auch immer wieder Situationen, in denen man »den Boden unter den Füßen verliert«. Das mag eine schwere Krankheit sein, finanzielle Sorgen oder der Verlust eines lieben Menschen. Und manchmal reichen schon die Herausforderungen des Alltags. Wie gut wäre es, wenn es da einen sicheren Halt gäbe, einen vorausschauenden, fürsorglichen Ingenieur, dem man sein Lebensprojekt anvertrauen könnte!Genau den habe ich gefunden! Ich selbst durfte erleben, dass der Glaube an Jesus Christus mich in meinem Alltag, den kleinen und auch größeren Herausforderungen trägt. Ich vertraue darauf, dass Jesus immer da ist und »dass für die, die Gott lieben und nach seinem Willen zu ihm gehören, alles zum Guten zusammenwirkt« (Römer 8,28). Das bedeutet nicht, dass es keine Herausforderungen und keine Not mehr gibt. Doch ich kann mich darauf verlassen, dass Gott für mich sorgt und dass dies zu seinem Bauplan für mein Leben gehört. Seine Hand hält mich stets fest! Ann-Christin BernackDiese und viele weitere Andachten online lesenWeitere Informationen zu »Leben ist mehr« erhalten Sie unter www.lebenistmehr.de

Hour 1: Conan O'Brien prefers to fly commercial. How did Drake get all of his money? Elon Musk is no longer a Trillionaire. The Westminster Kennel Club Dog Show is coming to Netflix. The X Games are happening this weekend in Sacramento. What happened to orange juice? Umm… it's bad for you. You're saying Adidas wrong, but that's really ok. The actors from ‘The Simpsons' are rich rich. Hour 2: It's time to give some Bad Advice! This listener wants to retire and go full-time Grandma. What does she need to consider before making the leap? Well, first, is this what her daughter wants? Then, a stereotypical redhead needs help calming down. Fireworks are coming back to the Golden Gate Bridge! The US stadiums are competing for the “best” place to watch the World Cup. It's carnival season! Sarah has perfected pancakes; It is known. This sparks a conversation about the gang's last meal. None of that 2% crap! Hour 3: Will ‘Supergirl' meet expectations at the theaters this weekend? Larry David's new show is here. The BET Awards are this weekend with a stacked lineup. Chet Hanks found the role he was born to play. Your good news story of the day is a singing janitor. We have more fair food to discuss! Cambridge is considering limiting patrons to one drink every 30 minutes. Is it too late for Matty to have a birthday party at Chuck-E-Cheese? Hour 4: Max Martin and Shellback are selling publishing rights to their Taylor Swift songs. Do we think she cares? Sarah and Bob are upping their bets about Taylor's wedding. Sarah and Vinnie love a good awkward moment. If you're not staying in The Bay, Las Vegas is supposedly a good spot to celebrate the 4th of July. A Michigan woman almost pulled off a perfect crime. True Or False: Crazy Carnival Edition.

It's time to give some Bad Advice! This listener wants to retire and go full-time Grandma. What does she need to consider before making the leap? Well, first, is this what her daughter wants? Then, a stereotypical redhead needs help calming down. Fireworks are coming back to the Golden Gate Bridge! The US stadiums are competing for the “best” place to watch the World Cup. It's carnival season! Sarah has perfected pancakes; It is known. This sparks a conversation about the gang's last meal. None of that 2% crap!

PHP Podcast – June 25, 2026 Hosts: Eric Van Johnson & John Congdon Eric and John are back. Sara and Holly did a better job. Eric’s computer still hates him. Eric’s Connectivity Saga: A Possible Resolution For weeks, Eric has been dealing with a maddening streaming issue — he could see and hear everyone, but nobody could hear or see him. It only happened during Zoom, Slack huddles, and Restream sessions. No one could explain it, including Eric. The apparent fix came by accident: while helping his kid troubleshoot a similar issue, Eric pulled up his own DNS settings and discovered they were only pointing to his router with no upstream fallback. He manually added Google’s 8.8.8.8 and Cloudflare’s 1.1.1.1 — and for the first time in weeks, had zero issues all week. Does DNS explain streaming dropouts? Almost certainly not. Does it appear to have fixed it? So far, yes. Computers are stupid. Eric needs to retire and open a landscaping business. Two Weeks Off: Road Trip, Pittsburgh, and a Graduation John took the family on a road trip that included national park hikes, biking across the Golden Gate Bridge, and a swing through Universal Studios. Eric headed to Pittsburgh, technically West Virginia, for his niece’s high school graduation. Eric came away impressed with how much Pittsburgh has changed: what was once a gritty steel city has quietly become a genuinely beautiful place. He’s half-serious about looking at it as a future PHP Tek location. Sara and Holly: The Better Hosts Eric and John opened with a heartfelt thank-you to Sara Golemon and Holly Schilling for covering the last two weeks. John’s take: Sara and Holly showed up with documents, had a plan, and ran a tighter show. He’s joking about handing over the keys — mostly. PHP Architect Takes Over Laravel Magazine Here’s the announcement Eric was teasing before the break: PHP Architect has taken over the Laravel Magazine brand. It was originally a Statamic, which Eric rebuilt from scratch over the past couple of weeks. No plans to create a print magazine — it will remain a web-only publication. Eric is thinking about opening it to outside contributors, and there’s a real possibility of a dedicated Laravel column eventually appearing in the PHP Architect magazine. The new consulting section Eric built for the site looks sharp enough that John immediately pointed out it looks better than what’s currently on phparch.com. Foam Burner Feature: Proof of Concept Wars John got a big feature in Foam Burner across the finish line — or at least mostly across — recorded a screencast, and sent it off to the people who care. The immediate response: a list of compliance concerns and edge cases. This is a proof of concept. John is sympathetic, having just had to tell Eric the same thing about Laravel Magazine. The cycle of building something you’re proud of and then having someone find the things that aren’t done yet is a universal developer experience. Code Review in the Age of AI — What’s the Point? John is in a strange spot: he’s doing careful code review on pull requests written entirely by Claude, submitted by non-developers. His detailed, educational feedback — the kind meant to help a developer understand why something was done a particular way — is just being fed back into Claude to generate revisions. Nobody’s learning anything. An incident during his vacation reinforced why the reviews matter: someone deployed AI-generated code that wasn’t well reviewed, it broke overnight, and the team had to revert it the next morning. His position: keep reviewing, even if the audience is an AI. But the nature of what you’re reviewing for has to change — you’re no longer nurturing a developer; you’re being a gate. Eric’s broader point: if you’re a developer who cares about the craft, don’t let AI make you lazy. Learn from how it implements things. Ask it why. The thing that will differentiate developers when AI really matures is genuine understanding of what the code is doing — and that only comes from staying curious. PHP Generics RFC — Closed The Generics RFC was shut down while Eric and John were away, and Eric is genuinely disappointed. The proposal was for syntax-only generics: type annotations that static analyzers could read but that would be stripped at the opcode level, meaning no runtime performance impact. The goal was to standardize the generics syntax so PHPStan, Psalm, and other tools all read it the same way — right now they each implement their own dialect. Sara voted no (she explained her reasoning in the June 17 episode). Joe abstained. Whether an active abstain requires a deliberate action or is the default for a non-vote is apparently still a matter of some debate. PHP Tek 2026 Talks Now on PHP Tech TV Talks from PHP Tek 2026 are being uploaded to phptech.tv. Subscribers can watch the full library. Several speakers have given permission to make their talks free, and Ben Ramsey’s is one of them. John also added video progress tracking to the platform — it now remembers how far into a video you’ve watched. This Week in PHP Internals (Artisan Build) While looking for a PHP Internals podcast that Nuno appears to have started (possibly in connection with the PHP Foundation after PHPverse), Eric stumbled on a different show: This Week in PHP Internals, hosted on the Artisan Build site, with four episodes out. Eric doesn’t know who runs it but says it’s good — short, focused, and gets to the point. He’s also still looking for confirmation on what exactly Nuno’s new podcast is and who it’s for. For reference: the original PHP Internals podcast was Derick Rethans’ show, which he hasn’t updated in four or five years. The ecosystem growing new shows is a good sign. PHP Friends RFC — Under Discussion John has been watching the friends RFC, currently in the discussion phase. The idea: a class can explicitly declare another class as a “friend,” granting it access to private properties without requiring inheritance. The canonical use case is a builder pattern — a UserBuilder that needs to set private fields on User without a thousand public setters, and without making those fields non-private. Holly, in chat, noted that the friend model is a special case of a “surfaces” model she proposed a few years back. She also shared that Swift doesn’t have protected at all (just public and private) — something she initially found frustrating but has come to appreciate. Eric admits he’s been guilty of abusing inheritance over the years and is more thoughtful about it now. The RFC is still under discussion; no vote yet. Eric Drops PHPStorm — Falls Back in Love with Vim Eric canceled his JetBrains All Products subscription. Not because there’s anything wrong with PHPStorm — he’s explicit about that — but because he’s been doing so much work via Claude Code and making only targeted, smaller changes himself that the license fee no longer made sense. His replacement workflow: VS Code for some things, Vim for others. The Vim part was supposed to be supplemental. Instead, his terminal has taken over: it went from a panel alongside PHPStorm to taking up two-thirds of his screen to now living on its own separate virtual desktop. He’s running Spotify in the terminal. He briefly ran Slack in the terminal. He uses Tmux religiously. “I have problems,” he acknowledged. He would not take this back. Links from the show: Laravel Magazine — Now under PHP Architect PHP Tech TV — PHP Tek 2026 talks now uploading PHP RFC Wiki — All RFCs under discussion PHP Tek 2027 — April 27–29 (phptek.io) PHP Architect Discord Host: Eric Van Johnson X: @shocm Mastodon: @eric@phparch.social Bluesky: @ericvanjohnson.bsky.social PHPArch.me: @eric John Congdon X: @johncongdon Mastodon: @john@phparch.social Bluesky: @johncongdon.bsky.social PHPArch.me: @john Streams: Youtube Channel Twitch Connect & Hire PHP Architect Website Twitter/X Mastodon Hire PHP Developers Looking to hire PHP developers? Email support@phparch.com – Joe and the team are available for consulting, infrastructure work, Ansible playbooks, and code review. Partner This podcast is made a little better thanks to our partners Displace Infrastructure Management, Simplified Automate Kubernetes deployments across any cloud provider or bare metal with a single command. Deploy, manage, and scale your infrastructure with ease. https://displace.tech/ PHPScore Put Your Technical Debt on Autopay with PHPScore CodeRabbit Cut code review time & bugs in half instantly with CodeRabbit. Music Provided by Epidemic Sound https://www.epidemicsound.com/ Join Us Live Next Week Youtube Channel Got feedback? Join us on Discord at discord.phparch.com The post The PHP Podcast 2026.06.25 appeared first on PHP Architect.

After four days crossing America by train, I finally arrive in San Francisco.There are ferries crossing the bay, cable cars climbing impossible hills and the Golden Gate Bridge emerging through the fog. But before I've even checked into my hotel, a chance encounter with a man in a Germany shirt sends me in an entirely different direction.One conversation becomes another. A recommendation leads to a beer garden in Hayes Valley. Suddenly I'm surrounded by German supporters watching their World Cup match, sharing stories about Hamburg, Berlin, Sheffield Wednesday, Japanese-American communities and life in one of America's most fascinating cities.This episode isn't really about football. It's about what happens when you follow curiosity instead of a plan.And, naturally, it ends with currywurst and a stein of beer in California.Host: Rob Shaw CameronFollow:  https://www.instagram.com/fan48podFAN48 – The World Cup Fans Podcast#WorldCup2026 #TravelPodcast #FootballCulture #SanFrancisco #Fan48

Today on The Gist, examining the upcoming criminal verdict for the Golden Gate Bridge climate protesters, breaking down the debate over jail time for high-impact civil disobedience. Then, Sadie Dingfelder returns for another installment of "Is It Bullsh*t?" to investigate the historical and scientific reputation of raccoons and rabies. Then, in the spiel, comparing the foreign policy legacies of Ronald Reagan and Donald Trump and analyzing whether current U.S. intervention strategies serve as a deliberate long game or merely export short-term geopolitical misery abroad. Produced by Corey Wara Video and Social Media by Geoff Craig Do you have questions or comments, or just want to say hello? Email us at ⁠⁠⁠⁠thegist@mikepesca.com For full Pesca content and updates, check out our website at https://www.mikepesca.com/⁠ For ad-free content or to become a Pesca Plus subscriber, check out ⁠⁠⁠⁠https://subscribe.mikepesca.com/ For Mike's daily takes on Substack, subscribe to The Gist List https://mikepesca.substack.com/ Follow us on Social Media:⁠⁠⁠⁠ YouTube https://www.youtube.com/channel/UC4_bh0wHgk2YfpKf4rg40_g⁠⁠⁠⁠ Instagram https://www.instagram.com/pescagist/ X https://x.com/pescami TikTok https://www.tiktok.com/@pescagist To advertise on the show, contact ⁠⁠⁠⁠sales@amplitudemediapartners.com Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Ein Bayer will 1977 nach San Francisco - landet aber 6000 Kilometer entfernt an der US-Ostküste. Trotzdem sucht er tagelang nach der Golden Gate Bridge. Wie wird aus einem Irrtum eine Heldenreise? Und was tun wir, wenn unsere Bilder vom Reiseziel an der Wirklichkeit zerschellen?

Sasha Orloff sits down with Solon Angel, CEO of Remitian, to explore why tax payments remain one of fintech's most overlooked infrastructure problems. They discuss the outdated systems still powering tax compliance, how AI agents are enabling a new payments layer for accountants and taxpayers, and why the convergence of regulatory change, fraud prevention, and agentic AI could transform the $7 trillion tax payment ecosystem into a seamless, deadline-free experience. -- SPONSORS: Notion Boost your startup with Notion—the ultimate connected workspace trusted by thousands worldwide! From engineering specs to onboarding and fundraising, Notion keeps your team organized and efficient. For a limited time, get 6 months of Notion AI FREE to supercharge your workflow. Claim your offer now at ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://notion.com/startups/puzzle⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Puzzle

In the latest episode of Rising Tide Ocean Podcast, Natasha Benjamin and Vicki Nichols talk with marathon swimmer Catherine Breed — a record-breaking endurance athlete, former U.S. National Team swimmer, and founder of Sea Dreamers. From world-record swims between the Farallon Islands and the Golden Gate Bridge to crossings of Lake Tahoe and beyond, Catherine shares stories from a life shaped by the ocean and discusses her most ambitious challenge yet: swimming the entire California coast. The conversation explores open-water swimming, adventure, ocean conservation, and of course, everyone's first question — what about the sharks? Tune in for an inspiring and thought-provoking conversation with Catherine Breed.Additional ResourcesSea Dreamers — Opening doors for women to get involved in ocean activities through community, inclusivity, empowerment and education surrounding ocean conservation.Blue Frontier / Substack — Building the solution-based citizen movement needed to protect our ocean, coasts and communities, both human and wild.Inland Ocean Coalition — Building land-to-sea stewardship - the inland voice for ocean protectionFluid Studios — Thinking radically different about the collective good, our planet, & the future.

The Page One Podcast, produced and hosted by author Holly Lynn Payne, celebrates the craft that goes into writing the first sentence, first paragraph and first page of your favorite books. The first page is often the most rewritten page of any book because it has to work so hard to do so much—hook the reader. We interview master storytellers on the struggles and stories behind the first page of their books. About the guest author: In addition to being the author of The Way of The Rose,  which she spoke about with her co-author and husband Clark Strand on Ep. 49 of the Page One Podcast, Perdita Finn is the author of several children's books and middle grade novels, including the Time Flyers series for Scholastic Books, My Little Pony Books, among many others and has worked as ghostwriter, book doctor, copy editor and writing teacher.  Perdita Finna also has done extensive study with Zen masters, priests, and healers, and apprenticed with the psychic Susan Saxman, with whom she wrote The Reluctant Psychic. She currently leads popular workshops on Collaborating with the Other Side, in which participants are empowered to activate the magic in their own lives with the help of their ancestors. She lives with her husband in the Catskill Mountains of New York. About the host: Holly Lynn Payne is an award-winning novelist and writing coach, and the former CEO and founder of Booxby, a startup that built an AI book discovery platform with a grant from the National Science Foundation. She is an internationally published author of four historical fiction novels. Her debut, The Virgin's Knot, was a Barnes & Noble Discover Great New Writers book. Her latest book, Rose Girl: A Story of Resilience and Rumi, a medieval, mystical thriller was awarded a Kirkus (starred) review and named Editors Choice from the Historical Novel Society. Holly lives on a houseboat near the Golden Gate Bridge with her daughter and Labrador retriever, and enjoys mountain biking, hiking, swimming and pretending to surf. To learn more about her books and writing coaching services, please visit her at hollylynnpayne.com  and subscribe to her FREE weekly mini-masterclass, Power of Page One, a FREE newsletter on Substack, offering insights on becoming a better storyteller and tips on hooking readers from page one! (And bonus: discover some great new books!) Tune in and reach out: If you're an aspiring writer or a book lover, this episode of Page One offers a treasure trove of inspiration and practical advice. I offer these conversations as a testament to the magic that happens when master storytellers share their secrets and experiences. We hope you are inspired to tune into the full episode for more insights. Keep writing, keep reading, and remember—the world needs your stories.  If I can help you tell your own story, or help improve your first page, please reach out @hollylynnpayne or visithollylynnpayne.com.  You can listen to Page One on Apple podcasts, Spotify, Pandora, Stitcher and all your favorite podcast players. Hear past episodes. If you're interested in getting writing tips and the latest podcast episode updates with the world's beloved master storytellers, please sign up for my very short monthly newsletter at hollylynnpayne.com and follow me @hollylynnpayne on Instagram, Twitter, Goodreads, and Facebook. Your email address is always private and you can always unsubscribe anytime.  The Page One Podcast is created on a houseboat in Sausalito, California, is a labor of love in service to writers and book lovers. My intention is to inspire, educate and celebrate. Thank you for being a part of my creative community!  Be well and keep reading, Holly @hollylynnpayne on IG Thank you for listening to the Page One Podcast! I hope you enjoyed this episode as much as I loved hosting, producing, and editing it. If you liked it too, here are three ways to share the love:Please share it on social and tag @hollylynnpayne.Leave a review on your favorite podcast players. Tell your friends. Please keep in touch by signing up to receive my Substack newsletter with the latest episodes each month. Delivered to your inbox with a smile. You can contact me at @hollylynnpayne on IG or send me a message on my website, hollylynnpayne.com.For the love of books and writers,Holly Lynn Payne@hollylynnpaynehost, author, writing coachwww.hollylynnpayne.com

Travels With Randy Summer Of '26 Episode 1 is here! Up The West Coast On Hwy 1  West Coast Travel and Real Estate Bubba and Randy discussed Randy's recent travels along the West Coast after completing a 17-podcast series about Route 66. They compared weather patterns between different regions, with Randy noting the benefits of spring weather in Washington compared to tornado season in the Midwest. The conversation also covered real estate price increases in California, with Randy sharing how his childhood home in Placentia appreciated from $37,000 in 1967 to $1.3 million currently, and they discussed future housing needs as they approach retirement age. US Road Trip Discussion Bubba and Randy discussed Randy's recent road trip across the United States, including his journey from Route 66 to California and his decision to take the scenic coastal route along Highway 1. They talked about the significant difference in gas prices between California and other states, with Randy noting prices reached $7.50 per gallon in some areas of California. Randy shared interesting facts about Highway 101 being created on the same day as Route 66's centennial, making it one of only a few highways still celebrated from that original group of over 180 numbered highways. Recent Road Trip and Adventures Randy shared details about his recent road trip, including a golf game where he lost by one stroke due to a poor final hole performance. He described visiting Albuquerque and having dinner with his girlfriend Cindy in California for her 60th birthday. The conversation also covered Randy's car brake issues, which required a $1,300 repair after hearing squeaking noises, and his enjoyment of driving along Highway 1 and Highway 101, particularly appreciating the scenic ocean views during early morning drives. Road Trip from Oxnard to Lompoc Randy described a road trip from Oxnard to Lompoc, explaining the route options along highways 1 and 101, and shared details about visiting Channel Islands National Park and Hearst Castle. He noted challenges with morning fog during the trip and recommended allocating time for both Channel Islands and Hearst Castle visits. The conversation ended with a discussion about national parks, particularly questioning how some sites like Gateway Arch and New River Gorge became national parks. National Park Designation Discussion Randy and Bubba discussed the process of national park designations, with Randy expressing disappointment about Indiana Dunes and speculating that Channel Islands became a national park due to favors or political reasons. They discussed the challenges with Route 66, with Randy advocating for it to be managed as a national park or byway to ensure consistent signage and routing. The conversation shifted to Randy's current trip following Highway 1 in California, including his visit to Hearst Castle, and they briefly discussed the location's history and the challenges of accessing Big Sur due to road damage. TV Pilot Script Discussion Randy shared details about a TV pilot script he wrote during an internship at MTM, inspired by the Newhart show and set at Big Sur Inn, which he struggled to get produced despite trying to interest Lindsey Wagner's agent. He reflected on how persistence and timing rather than overnight success determine career outcomes, particularly noting how AI tools would have significantly changed his college film production experience. The conversation concluded with Bubba sharing a personal connection to the Little River Inn in Mendocino, which Randy had previously visited and planned to post photos of later that week. Highway 1 Driving Discussion Bubba and Randy discussed driving on Highway 1, comparing the experience of driving versus being a passenger due to the road's challenging hairpin turns and lack of guardrails. Randy shared a story about encountering aggressive motorcycle riders on the same road, leading to an accident with another motorist. They also discussed the scenic route from San Luis Obispo to San Francisco, including the view of the Golden Gate Bridge and the option to visit Alcatraz Island. Alcatraz and Infrastructure Discussions Bubba and Randy discussed their visits to Alcatraz in San Francisco, sharing memories of the self-guided tours and the historical context of the island. They also talked about the constant maintenance required for the Golden Gate Bridge and compared it to other infrastructure projects. The conversation shifted to challenges in modern construction, particularly the difficulties in building data centers and bullet trains, and they briefly discussed the potential for building data centers in space. Space Data Center Discussion Bubba and Randy discussed the benefits of placing data centers in space, particularly on the moon, due to reduced cooling requirements and other advantages. They reflected on the rapid pace of technological advancement, comparing it to historical innovations like the personal computer and internet, and highlighted how AI technologies like ChatGPT are being adopted quickly and are already integral to daily workflows, as demonstrated by Randy's use of AI in photo processing. They also noted that while technological change can be unsettling, especially regarding job impacts, the current pace of innovation is unprecedented and continues to evolve rapidly. AI Tools for Work Efficiency Randy and Bubba discussed their experiences using AI tools like Gemini and ChatGPT to improve efficiency in their work. Randy shared how he uses Gemini to proofread and fact-check his social media posts, while Bubba described how he leverages AI to manage his book business, including analyzing inventory and making purchasing decisions. They also discussed the challenges some people face when retiring early, noting that staying mentally and socially active is important for overall well-being. Travel Content Planning Discussion Randy and Bubba discussed their upcoming travel content plans, with Randy planning to visit San Francisco and Alcatraz next week before covering northern California up to the Oregon border. They agreed to continue their weekly podcast discussions throughout the summer, focusing on travel topics including the Oregon coast and Northern California's wine regions. Bubba mentioned their Facebook page has grown to 37,000 followers and suggested exploring Hearst Castle during future West Coast trips. SO. MANY. PHOTOS - Come join the conversation on Facebook with our 33,000 friends! https://www.facebook.com/travelswithrandypodcast Have a great idea for the guys?  Want to sponsor us?  Want us to sell something National Park or Route 66 related? Want to be a guest? Want to pay for both of us to go to Alaska? Want me to stop asking questions?   bubba@travelswithrandypodcast.com !!

On April 15, 2024, dozens of pro-Palestinian protesters blocked the Golden Gate Bridge, in an attempt to pressure the U.S. government into ending military aid for Israel's bombing and invasion of Gaza. Now, seven of those protesters are on trial facing felony charges in San Francisco. If convicted, they could face a maximum sentence of 15 years in prison. Learn more about your ad choices. Visit megaphone.fm/adchoices

Back on this day in 1937, the Golden Gate Bridge opened to the public. At the time of building, the bridge cost $27 million and was considered affordable. 

Steiny & Guru celebrate the 89th Birthday of the Golden Gate Bridge before comparing and contrasting how the city matches up with other west coast hubs.

Today in 1937, the opening of the Golden Gate Bridge in San Francisco - or, more accurately, the beginning of the opening of the Golden Gate Bridge. The city was so pumped, the celebrations went on for days. Plus: starting Friday in Pennsylvania, it's the Johnstown PolkaFest. The 1937 Golden Gate Bridge Opening Was Completely Bananas (KQED)Johnstown PolkaFest Open up our Patreon page and back the show today

What makes America truly great—its mountains, canyons, redwoods, or something far deeper? Today on InGrace, Jim Scudder takes his grandkids on an unforgettable westward adventure from Pikes Peak to the Golden Gate Bridge, revealing the spiritual heritage that crowns our nation's beauty and freedom.

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

Best-selling author, keynote speaker, and Golden Gate Bridge suicide attempt survivor Kevin Hines joins Karena Dawn to talk about bipolar disorder, suicidal ideation, and the daily practices that keep him mentally well. Kevin opens up about the traumatic childhood that shaped his mental health, the instant regret he felt leaving the bridge rail, the sea lion and Coast Guard boat that saved his life, and the 15-year fight to install life-saving nets at the Golden Gate Bridge. He also shares the four words that have kept him alive through 25 years of suicidal ideation, and the science-backed wellness routines that support his brain health every single day. What does it take to survive the unthinkable and spend the rest of your life making sure others never have to? Kevin Hines proves that healing is not a destination but a daily practice, and that the simple words "I need help now" can make all the difference. (02:57) Born Into Crisis From abject poverty and neglect to a loving adoptive home, Kevin's path to the Hines family was anything but linear Why his gut health, brain chemistry, and mental illness were shaped before he could even speak The moment at 17 when his mind began to break, and why no one around him knew (13:11) The Words That Keep Him Here The mantra Kevin returns to every time suicidal thoughts arise, and why it works Four simple words he has taught thousands of people to say in their darkest moments Why sharing your pain with even one person creates real, physiological relief (21:51) Love, Loss, and the Fight for the Bridge Nets The wildly improbable love story that began in a psychiatric ward Why it took nearly two decades to get life-saving nets installed at the Golden Gate Bridge What to say when you see someone in visible pain and don't know how to start (28:58) Building a Life That's Worth Staying For Kevin's morning and evening routine for regulating his nervous system The 23-minute exercise rule backed by University of Georgia research Why his doctor reframed medication as a quality-of-life decision, not a weakness May is Mental Health Awareness Month—Get Involved through Action, not just awareness.  Be a part of change with The Big Silence | Host a benefit with The Big Silence: https://thebigsilence.com/blogs/share-your-silence/the-big-silence-fundraiser-hosting-guide Guest Resources Follow Kevin on Instagram Explore his books Listen to the Hindsights Podcast If this episode moved you, please consider supporting The Big Silence Foundation and exploring our resources: Connect with The Big Silence Community Order: The Big Silence Memoir audiobook Shop The Big Silence Self Love Collection Subscribe on YouTube Donate to The Big Silence Foundation The Big Silence Resource Guide Find exclusive offers from our supporters Show Resources: VISIT THE CHALLENGE PAGE THE BIG SILENCE PODCAST TONE IT DOWN PODCAST Tone It Up App Tone It Up YouTube Tone It Up Instagram Have a message for Karena? She'd love to hear from you and share your comment or question on air! Leave Karena a voicemail: https://www.speakpipe.com/KarenaDawn

My blogs "Black Pine Trees" and A Golden Sunset at the Golden Gate Bridge"Find more at https://timharner.com

"I used the original ethereal recording to run through the entire piece while also finding and recording a few more Golden Gate bridge sounds. These include the fog horns coming in as the melody and a couple others nearby the bridge.:The field recording inspires a warped sense of reality... dreary... a bit crazy. The bridge is a passage for those marching into a city of multiple faces and realities."There was madness in any direction, at any hour. If not across the Bay, then up the Golden Gate or down 101 to Los Altos or La Honda. . . . You could strike sparks anywhere." - Hunter S. Thompson Golden Gate Bridge reimagined by wwjd (Jason Talsma).

The slats in the Golden Gate bridge will resonate at certain wind speeds and directions. the first is a low-pitched + low-frequency tone between 280-700hz created by westward ~22mph winds while the second tone is of a higher pitch + frequency of 1.1khz created by ~27mph winds. This is the singing as heard from Lone Mountain, during a rainy night.Recorded by wwjd (Jason Talsma).

The high school student newspaper, the Redwood Bark, has served Redwood High School in Larkspur, a town a few miles north of the Golden Gate Bridge, since 1958. The reporters there frequently win national awards for their journalism. But this year, students began facing pushback and censorship from the administration for some of their stories. A 1977 landmark California law gives student journalists the autonomy to publish news without interference from principals and other school leaders. But these rights are often violated. Guests: Skye Hammond, reporter and editor, the Redwood Bark Thomas Peele, investigative reporter, EdSource Read more from EdSource: Student journalists' free press rights tested at Marin County high school Cases of student press censorship attempts on the rise in California schools Education Beat is a weekly podcast hosted by EdSource's Zaidee Stavely and produced by Coby McDonald. Subscribe: Apple, Spotify, SoundCloud, YouTube

Nikki and Brie are back together and catching up on two very different but powerful chapters. Brie opens up about her return to WWE, stepping back into the ring as Tag Team Champion with Paige, and finding her rhythm again after WrestleMania. Meanwhile, Nikki shares what life looks like in her recovery era, from pushing through tough rehab days to slowing down and soaking up meaningful moments at home with Matteo. From travel chaos to family time, the twins reflect on how their current seasons are shaping them both individually and together. They also get real about burnout, boundaries, and the simple things that bring them back to center—like nature, long walks, and unplugging from the noise. Plus, they share updates on Bonita Bonita, upcoming appearances, and what's ahead for the Bella Twins. Get into this sister catch up and press play now! Call Nikki & Brie at 833-GARCIA2 and leave a voicemail! Follow Nikki & Brie on Instagram, follow the show on Instagram and TikTok and send Nikki & Brie a message on Threads! Follow Bonita Bonita on Instagram Book a reservation at the Bonita Bonita Speakeasy To watch exclusive videos of this week's episode, follow The Nikki & Brie Show on YouTube, Facebook, and TikTok! You can also catch The Nikki & Brie Show on SiriusXM Stars 109! Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Out conversation about the Golden Gate Bridge continues with the opening of the bridge, and a bunch of people who didn't get enough credit. Plus, what the story says about how we need big ideas even in moments when things feel especially dire.Join our America250 newsletter community! Subscribe for free to get the latest news and analysis of how America250 is playing out. Paying subscribers get access to early, ad-free versions of the show. Plus bonus features throughout the year. To support our work and get access to everything, subscribe now.This Day is a proud member of Radiotopia from PRX.Your support helps foster independent, artist-owned podcasts and award-winning stories.If you want to support the show directly, you can do so on our website: ThisDayPod.comGet in touch if you have any ideas for future topics, or just want to say hello. Follow us on social @thisdaypodOur team: Jacob Feldman, Researcher/Producer; Khawla Nakua, Transcripts; music by Teen Daze and Blue Dot Sessions; Audrey Mardavich is our Executive Producer at Radiotopia. Learn about your ad choices: dovetail.prx.org/ad-choices

“If we claim we have no sin, we are only fooling ourselves and not living in the truth.” (1 John 1:8 NLT) Visitors to San Francisco can’t help but be amazed at the architectural marvel that is the Golden Gate Bridge. But its beauty and innovation came at a tremendous cost. During the initial phases of construction, several workers lost their balance and plunged to their deaths in the San Francisco Bay. The builders were concerned about the human tragedy, of course. But they were also concerned about the delays in the schedule because of the deaths. They needed to find a way to keep their workers safe under the most dangerous conditions. The solution they arrived at was something that had never been done before. The builders installed a giant safety net under the construction area. The workers knew that if they fell, the net would catch them. The experience wouldn’t necessarily be pleasant for the unfortunate worker, but at least he would live to tell about it. Thanks to the net, workers could go about their business without the fear of dying. With the threat removed, they were able to move quickly and finish the project. Did you know that God has put a safety net under you? By that I mean, when you slip, when you fall, when you make a mistake, you don’t have to worry that your name will be blotted out of the Book of Life. You don’t have to face the prospect of becoming persona non grata with God. The apostle Paul wrote, “For everyone has sinned; we all fall short of God’s glorious standard. Yet God, in his grace, freely makes us right in his sight. He did this through Christ Jesus when he freed us from the penalty for our sins. For God presented Jesus as the sacrifice for sin. People are made right with God when they believe that Jesus sacrificed his life, shedding his blood” (Romans 3:23–25 NLT). If you believe in Christ, you have a spiritual safety net. You have a barrier against spiritual death. Because Jesus came into your heart, forgave you, and committed Himself to you, He now protects you, seals you, and justifies you because of that commitment. The fact is that we as Christians will sin and fall short. The Scriptures, as well as our own experiences in life, tell us this is true. According to 1 John 1:8, “If we claim we have no sin, we are only fooling ourselves and not living in the truth” (NLT). This isn’t an excuse for ungodly living. Nor is it a license for sin. It’s a simple acknowledgment of reality. Yet Paul wrote, “I am convinced that nothing can ever separate us from God’s love. Neither death nor life, neither angels nor demons, neither our fears for today nor our worries about tomorrow—not even the powers of hell can separate us from God’s love” (Romans 8:38 NLT). Nothing can dismantle our safety net. Reflection question: What does your spiritual safety net mean to you? Discuss Today's Devo in Harvest Discipleship! — The audio production of the podcast "Greg Laurie: Daily Devotions" utilizes Generative AI technology. This allows us to deliver consistent, high-quality content while preserving Harvest's mission to "know God and make Him known." All devotional content is written and owned by Pastor Greg Laurie. Listen to the Greg Laurie Podcast Become a Harvest PartnerSupport the show: https://harvest.org/supportSee omnystudio.com/listener for privacy information.

Structurally the Bay Area's famous landmark, the Golden Gate Bridge, is reported to be incredibly safe. But the financial future of the bridge is a different story. For more KCBS Radio News Anchor Steve Scott spoke with KCBS Insider Phil Matier.

For the seventeeth installment of “50 Weeks That Shaped America” we travel to California in the 1930s, where San Francisco planners have a big idea — build a massive suspension bridge across the Golden Gate strait. We discuss how the project came together despite the Great Depression, the big egos involved, what the story says about how audacious projects can pull a country out of malaise… and why the bridge is the color it is.Join our America250 newsletter community! Subscribe for free to get the latest news and analysis of how America250 is playing out. Paying subscribers get access to early, ad-free versions of the show. Plus bonus features throughout the year. To support our work and get access to everything, subscribe now.This Day is a proud member of Radiotopia from PRX.Your support helps foster independent, artist-owned podcasts and award-winning stories.If you want to support the show directly, you can do so on our website: ThisDayPod.comGet in touch if you have any ideas for future topics, or just want to say hello. Follow us on social @thisdaypodOur team: Jacob Feldman, Researcher/Producer; Khawla Nakua, Transcripts; music by Teen Daze and Blue Dot Sessions; Audrey Mardavich is our Executive Producer at Radiotopia. Learn about your ad choices: dovetail.prx.org/ad-choices

In tonight's dead letter, listener Jeannette shares a deeply atmospheric story from a bike commute across one of the most famous bridges in the world. Enveloped in the freezing, thick San Francisco fog, what starts as a quiet ride she's done a million times turns into an inexplicable encounter with a solitary figure standing near the edge. After a strangely profound exchange of words, she looks back to find the massive walkway entirely empty. She is convinced that he couldn't have had time to have taken his life in that brief moment. It opens up a conversation about crisis apparitions, liminal spaces, and the heavy emotional toll anchored to such a monumental location.REFERENCE LINKSSFGate: Japanese Taxi Drivers Claim Ghost Passengers Hail Cabs at Site of 2011 Tsunami: https://www.sfgate.com/news/article/Japanese-taxi-drivers-claim-ghost-passengers-6806980.phpGolden Gate Bridge Suicide Deterrent Net Project: https://www.goldengate.org/district/district-projects/suicide-deterrent-net/Bridge Rail Foundation: http://www.bridgerail.net/"Unsolved Mysteries"- Tsunami Spirits: https://www.imdb.com/title/tt11107472/KCRW Unfictional Podcast: https://www.kcrw.com/shows/unfictional/latestGhosts of the Tsunami by Richard Lloyd Parry: https://bookshop.org/p/books/ghosts-of-the-tsunami-death-and-life-in-japan-s-disaster-zone-richard-lloyd-parry/4c115c39e1094566?ean=9781250192813&next=tWe're looking for more stories! Send your Dead Letter to deadletteroffice@astonishinglegends.com!

7:05- Mark is learning to speak Spanish through A.I. for $19.99 a month. Mark’s former Spanish teacher was Tim Conway’s (Tim’s dad) Spanish teacher. Queso is cheese, dad. Beware of EWA Learn languages App, 3rd party Paddle app is coming after Mark. They are making it impossible to cancel. Angel knows two words. Conway a great supporter of WOMEN! Fabulous! 7:20- Is rain coming to town? Mark was the ultimate weatherman, the dancing weatherman he started. Inside the mind of a dancing weatherman. Jason Bateman ‘St. Louis DTF’, new show where he is doing karate. Did Mark know if it was going to be a dancing day? 7:35- Are sporting events pricing out the fans?! F’n FIFA ticket prices are too high. Bathroom keys.Most valuable company int he world...Nividia. A bee infiltrates the studio, like working in the jungle. 7:50- LAX people mover, is testing without people. The term “hiccup” when things go wrong, whats the origin? The Golden Gate Bridge cost approximately $35 million to construct (about $1.5 billion in 2019 dollars). Construction began on January 5, 1933, and was completed in 1937 under budget and ahead of schedule, with the final bonds for the project retired in 1971. See omnystudio.com/listener for privacy information.

I went to Taiwan, but the show must go on. While I was away covering the Taipei Cycle Show, Mike Levy, Lisa Charlebois, and Logan Jones-Wilkins had plenty to talk about. Predictably, things got heavily focused on gravel tire pressure, but that wasn't all. This week, the podcast crew debates why roadies need bigger gravel tires, breaks down Specialized's newest tech, and confesses to their strangest cold-weather clothing hacks. In this episode, we cover: Lisa's 300km Mission: A recap of an epic 193-mile ride through Napa and Sonoma, plus a crucial PSA on the protocol for crossing the Golden Gate Bridge late at night. Specialized's New Pathfinder TLR: Logan is currently working his way through a massive pile of test rubber. He explains why pros like Keegan Swenson opt for the slickest options, but argues the more aggressive Terra tread is actually better for the rest of us. Levy's Tire Volume Hot Take: Levy takes a firm stance that most gravel riders are severely under-tired. His advice to roadies hitting the dirt? Stop obsessing over aero, mount the biggest tires your frame clears, and run an insert. New Roval Gravel Wheels: A quick look at the newly launched Roval Terra Aero CLX and Terra CLX3 wheelsets, including a discussion on their 27mm internal width and the decision to use a wide carbon hook. Questionable Winter Kit: Inspired by Jonas Vingegaard's heavily modified, cut-up winter bib shorts, the crew shares their own extreme cold-weather survival tactics—from crotchless long underwear to the merits of baggy mountain bike pants on a drop-bar bike. Give it a listen, and let us know in the comments if you have a favorite tire or if you think Levy is wrong on his hot take. Episode Timestamps: 00:00 - Intro 01:25 - Lisa's 300k 05:04 - Gravel Tires 27:54 - Specialized Wheels 34:28 - Clothing discussion

Amy Appelhans Gubsers (56) is a nurse at UCSF, a mom and grandma, and the first person to swim from the Golden Gate Bridge to the Farallon Islands—nearly 30 miles and roughly 17 hours in cold Pacific water, in what many consider shark territory. This is more than an epic swim. It's a practical conversation about how big goals actually get done: patience over years, calm under pressure, and the ability to keep moving when conditions stop cooperating.In this episode: The long-game reality behind “overnight” achievements  The mental skill that mattered most during 17 hours  Cold-water decision-making + staying calm  Sharks: real risk, smart planning  Why goals like this are never truly solo Takeaway: Massive goals aren't won by hype. They're earned through durable process. From the vault: recorded + released ~1.5 years ago — still one of our clearest blueprints for pursuing a massive goal with real stakes.

Dipsea Generations follows the stories of five young San Francisco Bay area runners who take on the historic Dipsea trail race. The Dipsea is the oldest trail race in the United States, started in 1905, and it covers 7.4 miles of incredible terrain between Mill Valley–just north of the Golden Gate Bridge in Marin County–and Stinson Beach. One interesting twist about this race is it has a handicap format determined by age and gender, so it makes for a more level playing field in those regards.  Nicole grew up in Mill Valley, so she's very familiar with the Dipsea, and she studied cinema, with an emphasis on Documentary and Editing at SF State before going over to England to get her master's degree in documentary filmmaking. Nicole now lives back in the San Francisco Bay Area not far from where she grew up. In addition to being a filmmaker, Nicole is the video producer, editor, and a board member for the Trail Running Film Festival. This means that she sees a lot of documentaries about trail running.   In her own filmmaking Nicole has a strong interest in sharing stories about women runners. That is where she focused her master's thesis documentary, which is titled Finding Her Stride. The documentary follows the stories of several women ultra runners, and weaved throughout, Nicole chronicles her first trail marathon, which at the time was the farthest she'd ever run.  Nicole talks about that experience and her film in this episode, in this story of coming into her own.  From this Episode Nicole Amyx on Instagram: @nixamyx9 Nicole Amyx's website: nicoleamyxfilm.com Finding Her Stride documentary: vimeo.com/393933541?fl=pl&fe=vl Dipsea Generations website: dipseagenerations.com Trail Running Film Festival: trailfilmfest.com More from WRS WRS is on Substack: womensrunningstories.substack.com To support WRS, please rate and review the show iTunes/Apple:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ https://podcasts.apple.com/us/podcast/womens-running-stories/id1495427631⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Spotify:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ https://open.spotify.com/show/4F8Hr2RysbV4fdwNhiMAXc?si=1c5e18155b4b44fa⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Music Credits Cormac O'Regan, of⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Playtoh⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Coma-Media⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠, via⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Pixabay⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Ikoliks, via Pixabay⁠⁠⁠⁠⁠⁠⁠⁠⁠ Music of the Future, via ⁠⁠⁠⁠⁠Pixabay⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠RomanBelov⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠, via⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Pixabay⁠⁠⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Ways to Connect and Engage with Women's Running Stories WRS Instagram: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠@womensrunningstories⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Facebook:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ facebook.com/WomensRunningStories⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Website:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ womensrunningstories.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠

Sacramento doesn't have a Golden Gate Bridge. So they built demand with experiences—and then proved it with room nights. For #NoVacancyNews, I talked with Mike Testa (President & CEO, Visit Sacramento) about how Sacramento positioned itself around farm-to-fork and then stacked events that drive real overnight stays from different customer groups.

Dear Wonderful Reader,The money dwindles in my bank account. My grandma is dying. I have to sell my investment stocks and ETFs to pay for these flights. Hit by a “family emergency” when I have the least wiggle room. I gave up my Soho House membership, which in hindsight seems like an irresponsible and pretentious expense. Today is also my four-year anniversary since I quit my job in New York to pursue this creative life. I've spent 95% of my days since then extremely happy. No regrets. Yet two books published, workshops being taught, a feature in the New York Times, and a mention in Vogue isn't much comfort when my client pipeline is dry.This is a hard moment in my journey. Yet, I still have you, my lovely reader! Thank god you're still here. We're all still here, somehow. Today, I have something special for you. It is one of my favorite images. It is an image that sustains me in these difficult moments of life, and being a human on this planet. I wrote it when I returned to San Francisco from my friends' betrothal. A former tech minion, I have seen the bridge many times. But something about that day was different.Thank you for the opportunity to edit this and give this a little more love and polish. I will keep this in mind when I get on a plane tomorrow, and sit at my grandmother's bedside. Things are hard, but this is keeping me going. This is a gift. This is my gift for you,Love,TashSend this to someone you love

In this one, I talk to journalist Paul Koberstein, whose recent book, “Canopy of Titans,” explores one of the most overlooked ecosystems on Earth: the Pacific Coastal Temperate Rainforest. Stretching roughly 2,500 miles from just north of San Francisco's Golden Gate Bridge to the western Gulf of Alaska, it's the largest temperate rainforest on the planet. Fueled by Pacific storms and cool ocean currents, it supports towering redwoods, Sitka spruce, western hemlock, and cedar — some of the largest and oldest trees in existence. Acre for acre, these forests store more carbon than tropical rainforests like the Amazon, with vast reserves locked in massive trunks, deep soils, roots, and centuries of accumulated woody debris. But even though it's one of the most carbon-dense ecosystems we have, and a critical buffer against climate change, it remains largely overlooked in global climate conversations. Paul pushes back on some of the most common narratives about forests and climate. He points to those industry ads that promise for every tree cut down, three more will be planted. It's an argument that sounds reassuring until you realize a young sapling can take a century to store the amount of carbon held in the massive tree that was felled. Trees are about 50 percent carbon. Through photosynthesis they pull carbon dioxide out of the air, lock that carbon into their trunks and roots, and release the oxygen we breathe. Southeast Alaska's Tongass National Forest alone holds more total carbon than any national forest in the country. That scale of storage is central to Paul's point: the science doesn't say we're powerless. It suggests that we can still influence the climate back toward something more stable. If fossil fuels loaded the atmosphere with excess carbon, then forests, if protected and restored, can help draw it back down. Forests have stabilized the climate for thousands and thousands of years. Whether they continue to do so depends largely on us letting them do their job.

If you think the Golden Gate Bridge is named because of its color then you are wrong. That name proceeds the bridge by a long time. But that’s just one interesting fact about this amazing structure. Tune in today.See omnystudio.com/listener for privacy information.