Podcasts about Timo

Ungarische Straßen, serbische Abgründe und ein Action-Tipp fürs Kino Die neue Folge startet mit Urlaubserlebnissen aus Ungarn – wilde Überholmanöver, teure Tomaten und die überraschende Erkenntnis, dass dort fast jeder Deutsch spricht. Außerdem wurde endlich das Hörbuch zu Der Astronaut durchgehört: nah am Film, aber mit noch mehr Details. Dann wird es richtig heftig: Timo und Zeljko sprechen über A Serbian Film – den Film, der seit über 15 Jahren für extreme Reaktionen sorgt. Timo hat ihn nach langer Zeit noch einmal gesehen und findet ihn gar nicht so verstörend wie sein Ruf, auch wenn einzelne Szenen hart sind. Sein Fazit: filmisch eher mittelmäßig, aber die Provokation gelingt. Zeljko, der den Film damals viel intensiver erlebt hat, sieht ihn heute mit mehr Distanz, erkennt aber die düstere Atmosphäre und den nihilistischen Unterton an. Beide sind sich einig: Der Film ist nichts für Unerfahrene im Horror-Genre, aber ein Verbot oder die Verurteilung der Zuschauer geht zu weit. Zum Glück gibt es dann leichtere Kost: Tschappel, eine schwäbische Comedyserie mit Eberhofer-Vibes und einigen bekannten Influencer-Gesichtern – perfekt zum Wegsnacken. The Furious wird von Zeljko als Action-Highlight angekündigt: japanische Handkanten-Action, ein gehörloser Protagonist, dessen Tochter entführt wird, und Stunts, die man heute kaum noch sieht. Kinostart ist am 18. Juni – und Zeljko war schon bei einer Vorpremiere. Sein Urteil: Eine Genregranate. Außerdem im Gepäck: die Poldi-Doku auf Netflix – sympathisch, feelgood, aber mit ein paar leisen kritischen Tönen zur Familienzeit, und die Baby Assassins-Reihe, die Zeljko komplett durchgesuchtet hat. Teil 2 und 3 steigern sich deutlich, der japanische Humor ist Geschmackssache, aber wer darauf klarkommt, bekommt actionreiche und herzlich-witzige Unterhaltung. Also, Ohren auf und ab in die Welt von "Once Upon A Time In Cinema - Der Filmpodcast" - jeden Sonntag um 10:00 Uhr, überall wo es Podcasts gibt! Inhalt:(00:00) Intro (13:45) A Serbian Film (31:00) The Furious (38:45) Tschappel (41:30) Poldi (49:15) Baby Assassins 2 & 3 ____ Der Film-Podcast mit Zeljko und Timo Anfragen: ouatic@gmx.de https://letterboxd.com/OuaticPodcast https://instagram.com/onceuponatimeincinema_

Wat is belijdenis doen eigenlijk? Wie doet dat nog en hoe? Timo van der Heijden schreef er zijn masterthesis over en noemt het een ‘ritueel van inwijding'. Dat geldt ook voor het vormsel, dat in de Oud-Katholieke kerk van Louis Runhaar als inwijding wordt gevierd.Koos gaat in gesprek met Timo en Louis, want ja, er zijn verschillen – zoals de zalving bij de oud-katholieken - maar gedurende het gesprek wordt duidelijk dat de rituelen rondom inwijding steeds dichter naar elkaar toe kruipen, en er van elkaar te leren valt.Als Louis beeldend vertelt hoe hij de olie (zalf) voor het vormsel mag bereiden, ‘met gewone olijfolie uit de supermarkt, maar wel met fijne kruiden, want het moet wel lekker ruiken', antwoordt Timo: “Ik voel me echt een ‘hoofdkerk' als ik dit zo hoor.”Timo van der Heijden is predikant van de Fonteinkerk in Apeldoorn (PKN).Zijn masterthesis (2024): Belijdenis doen tegen het licht gehouden - Theologische UniversiteitenLouis Runhaar is priester van het aartsbisdom Utrecht van de Oud-Katholieke Kerk en pastoor van de (oud-katholieke) parochie Utrecht.Heilige Grond is een podcast van de Protestantse Theologische Universiteit en de Theologische Universiteit Utrecht.

Pas als je huiswerk af is, mag je spelen. Kom nooit te laat. Maak geen fouten. Toon geen emoties. Timo leerde deze regels al heel vroeg in zijn leven. Niet bewust, maar zijn systeem trok ze wel degelijk als conclusie. Want zijn moeder stelde hoge eisen. Dus maakte hij leefregels. En die werkten. Ze maakten hem tot een uitstekende leerling. Een betrouwbare zoon. Later een bewonderde ondernemer met een strak draaiend techbedrijf. Twintig jaar lang.Tot zijn lichaam ermee stopte. Want wat ooit bescherming bood, kan later ballast worden.

Een onderwerp waar we nog nooit aan aflevering aan hebben gewijd, maar dat voortdurend terugkomt in de Kroegpraat-community: daten. Daarom is podcastmaker en date-expert Timo Harmelink te gast. Hinge, Raya, Bumble, Tinder en Grindr: hoe staat de datingappwereld ervoor? Tussen slechte matches, onoriginele foto's en ingewikkelde prompts als ‘long term, open to short' lijkt de dating fatigue groter dan ooit. Werkt offline daten misschien toch beter? Hoe ga je om met afwijzing? En hoe houd je plezier in het daten? Van fietsflirten tot vrienden pitchen: Timo deelt zijn beste inzichten en praktische tips.Onze sponsors:Arla Skyr is de sponsor om meer uit jouw ochtend te halen!Matt Sleeps bestaat 10 jaar en viert dat met de hoogste kortingen ooit tot wel 50%! Ga naar mattsleeps.com/kroegpraat en gebruik code KROEGPRAAT voor een extra verrassingskorting bovenop de lopende acties. (Geldig t/m 30 juni 2026)Productie: Meer van ditMuziek: Keez GroentemanWil je adverteren in deze podcast? Stuur een mailtje naar: Adverteerders (direct): adverteren@meervandit.nl(Media)bureaus: adverteren@bienmedia.nl Hosted on Acast. See acast.com/privacy for more information.

Teresa, Coni y Leticia analizan los diversos ángulos del Mundial y las protestas en MéxicoEnlace para apoyar vía Patreon:https://www.patreon.com/julioastilleroEnlace para hacer donaciones vía PayPal:https://www.paypal.me/julioastilleroCuenta para hacer transferencias a cuenta BBVA a nombre de Julio Hernández López: 1539408017CLABE: 012 320 01539408017 2Tienda:https://julioastillerotienda.com/ Hosted on Acast. See acast.com/privacy for more information.

In dieser Folge sitzt endlich wieder das Original-Trio zusammen im Kölner Savoy Hotel. Es geht um den WM-Hype, seltene Sticker mit absurden Sammlerwerten, teure Fußballtrikots und die Frage, ob der moderne Fußball langsam kaputtgemacht wird. Außerdem sprechen Aaron, Marvin und Timo über aktuelle YouTube-Projekte, Gerichtstermine, verrückte Geschichten aus Köln und die bevorstehende Darmspiegelung, bei der natürlich die Kameras mitlaufen.Zum Tippspiel: https://www.kicktipp.de/derkiosk/Lob, Kritik und Freundschaftsanfragen wie immer an:https://www.instagram.com/einfachtimo/

Neste episódio do MateCast Guri de Uruguaiana bate um papo com a cantora Aninha Soares, da banda Sétimo Sentido!

No está bien, eso lo tiene claro Timo desde el principio. La historia flojea, la evolución del personaje es gratuita y las reglas mágicas que le dan los poderes al prota se rompen cuando conviene. Y aun así salió contento del cine. Nosotros tampoco lo entendemos, pero ahí está.

Kausi 3, jakso 20. Millaista on eletty kristinusko, joka ei ole solmussa tai rähmällään johonkin suuntaan? Timo ja Lasse pohtivat uskon olemusta ja sudenkuoppia Raimo Mäkelän kirjan “Terve mieli – terve usko” (2007) johdattelemana.Armon anatomiaa on podcast, jossa studioon istutetaan yksi pappi, perheenisä ja aviomies Pohjanmaalta (Lasse Pesu) ja toinen Savo-Karjalasta (Timo Liiri) ja heidät laitetaan keskustelemaan kristinuskon eri sisällöistä. Joka jakson tarkoituksena on ottaa jokin uskoon liittyvä teema ja katsoa, mistä se koostuu, mitä se merkitsee ja mitä kaikkea annettavaa sillä on meille.Tue podcastin tekemistä MobilePay-numerolla 25322. Rahankeräyslupa: https://sro.fi/rahankerayslupa/

Timo & Mattey widmen sich in dieser Folge den Großen Preis von Monaco 2026. Die Jungs analysieren die Siegesserie von Kimi Antonelli, das Strafen-Chaos im Fürstenstaat und die Zukunft des Traditionsrennens. Viel Spaß!

In honor of Father's Day ..... we replay out 2020 interview with best-selling author Tim O'Brien, talking about "Dad's Maybe Book," which recounts what it was like for him to become a father for the first time at the age of 56.

Von echten Notrufen, vertauschten Rollen und einem Freund aus dem All Die neue Folge startet entspannt mit Biergeschmack und Kalorientipps, wird dann aber schnell sehr ernst. Timo und Zeljko sprechen über The Voice of Hind Rajab – ein Hybrid aus Spiel- und Dokumentarfilm über ein sechsjähriges Mädchen, das im Gazastreifen in einem Auto unter Beschuss gerät und den Notruf wählt. Die Original-Audioaufnahmen sind verstörend, die Situation aussichtslos. Der Film hat beide tief getroffen. Kein einfacher Stoff, aber ein wichtiger. Wer Downer verträgt, sollte ihn sich anschauen – alle anderen vielleicht an einem besseren Tag. Zum Glück gibt es dann Ladies First mit Sacha Baron Cohen: Eine Gender-Twist-Komödie, in der ein Macho-Chef nach einem Unfall in einer Welt aufwacht, in der das Matriarchat regiert. Der Joke ist schnell erzählt, der Film keine Offenbarung, aber für einen lockeren Abend zwischendurch völlig okay. Timo empfiehlt stattdessen lieber Game Night oder Tucker & Dale vs. Evil – die echten Komödien-Highlights. Film der Woche: Der Astronaut – Project Hail Mary – endlich die Verfilmung des Bestsellers von Andy Weir (dem Autor von Der Marsianer). Ryan Gosling als Naturwissenschaftslehrer, der ohne Erinnerung auf einem Raumschiff erwacht und nach und nach seine Mission rekonstruieren muss: Die Erde retten, bevor die Sonne stirbt. Der Film ist bildgewaltig, warmherzig und überraschend witzig. Eine ganz besondere Beziehung steht im Mittelpunkt, die für viele emotionale und humorvolle Momente sorgt. Ein lockerer, herzerwärmender Interstellar für alle, die Science-Fiction mit Herz mögen. Also, Ohren auf und ab in die Welt von "Once Upon A Time In Cinema - Der Filmpodcast" - jeden Sonntag um 10:00 Uhr, überall wo es Podcasts gibt! Inhalt:(00:00) Intro (03:00) The Voice of Hind Rajab (22:10) Ladies First (28:30) Der Astronaut - Project Hail Mary ____ Der Film-Podcast mit Zeljko und Timo Anfragen: ouatic@gmx.de https://letterboxd.com/OuaticPodcast https://instagram.com/onceuponatimeincinema_

Auch diese Woche begrüßen wir euch unter dem Motto „3 Mikrofone, 3 Meinungen“ zu den folgenden Themen in dieser Ausgabe:
 ► BTC: Kommt jetzt der große Absturz?
 ► Ist alles eine große Blase?
 ► Berkshire: Endlich tut einer was!
 ► Iran-Krieg: Diese Aktien profitieren von Frieden!
 ► Hörerfrage von Thomas: Was halten wir von Thyssen Krupp?
 ► Mega-Trend: Recycling!
 ► Rheinmetall: Das musst du wissen!
 ► Hier die brandneue BuyTheDip PLUS App herunterladen: https://www.buy-the-dip.de
 Sichere dir diese Vorteile:
 •⁠ ⁠Exklusive LIVE-Updates & Sessions
 •⁠ ⁠Detaillierte Aktien-Analysen & -Updates
 •⁠ ⁠Wöchentlicher Q&A-Podcast
 •⁠ ⁠Das BuyTheDip PLUS ETF-Depot
 •⁠ ⁠Watchlists: Aktien, ETFs, Krypto
 •⁠ ⁠Käufe & Verkäufe von Timo & Sebastian
 Ein wichtiger abschließender Hinweis: Aus rechtlichen Gründen dürfen wir keine individuelle Einzelberatung geben. Unsere geäußerte Meinung stellt keinerlei Aufforderung zum Handeln dar. Sie ist keine Aufforderung zum Kauf oder Verkauf von Wertpapieren.
 Die verwendete Musik wurde unter AudioJungle - Royalty Free Music & Audio lizensiert. Urheber: original_soundtrack.
 Offenlegung wegen möglicher Interessenkonflikte: Die Autoren sind in den folgenden besprochenen Wertpapieren bzw. Basiswerten zum Zeitpunkt der Veröffentlichung investiert: Bitcoin, Berkshire Hathaway, Alphabet, NVIDIA

En este episodio hablamos con Jesús G. Maestro, catedrático de Teoría de la Literatura y autor de "El fracaso de la felicidad", quien desmonta sin complejos los pilares del pensamiento positivo, la autoayuda y el idealismo contemporáneo. Exploramos conceptos clave como la triple D (desengaño, decepción y desencanto) que define a la generación cervantina, la peligrosa sustitución de la libertad por la felicidad como valor social, y por qué El Quijote es en realidad un manual de supervivencia contra el engaño. 00:00:00 - El problema fundamental: la felicidad ha reemplazado a la libertad.00:02:03 - Presentación del libro: El fracaso de la felicidad.00:03:58 - La "Triple D": Desengaño, Decepción y Desencanto en la generación actual.00:05:42 - La contradicción entre prometer la paz y prepararse para la guerra.00:08:20 - Cómo se anestesia la conciencia de las necesidades humanas.00:10:18 - Crítica sobre la eutanasia frente a la búsqueda de inmortalidad de las élites.00:15:30 - El fracaso del conocimiento y su sustitución por ideologías y emociones.00:19:35 - ¿Qué es más importante: la libertad o la felicidad?00:24:18 - El trabajo como herramienta para madurar y enfrentarse a la realidad.00:27:07 - El mito de la felicidad laboral en los países nórdicos.00:34:55 - La irrupción de la Inteligencia Artificial y su impacto en la realidad.00:47:20 - El propósito de la universidad y la obediencia a las élites.00:51:10 - El confort actual como un sedante para la libertad.00:54:35 - Crítica al idealismo alemán como causa de frustraciones humanas.00:58:30 - La "neotenia literaria": la infantilización del ser humano adulto a través de la lectura.01:05:10 - Por qué el Quijote es la mejor obra de la historia y el genoma de la literatura.01:14:15 - Análisis de La vida es sueño de Calderón de la Barca.01:16:50 - Lista de las 30 obras canónicas que todo ser humano debería leer.01:30:25 - El Don Juan de Tirso de Molina como manual contra el narcisismo y relaciones tóxicas.#Felicidad #Libertad #Filosofía #JesúsGMaestro #Literatura #ElQuijote #PensamientoCrítico #Realismo #Cultura #Educación #Sociedad #UriSabatEL LIBRO de La Fórmula del éxito. Aqui lo puedes conseguir

Rodolfo Gomes, Felipe Oliveira, Alexandre Ferreira e Murilo Franco debatem sobre os rivais de São Paulo. O Fala, Rival! tem apresentação de Edu Futirinhas! APOIO BETNACIONALSe for maior de 18 anos aposte na BetNacional:⁠⁠⁠⁠⁠⁠⁠⁠⁠https://betnacional.bet.br/⁠⁠⁠⁠⁠⁠⁠⁠⁠REDES SOCIAIS:Instagram:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/futebotecotv/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Twitter:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/FutebotecoTV⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Facebook:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.facebook.com/futebotecotv⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠TikTok:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.tiktok.com/@futebotecotv?⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Kwai:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.kwai.com/@futebotecoTV⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠------------------------------------------------------------APRESENTADORES:Edu Futirinhas⁠https://www.instagram.com/edufutirinhas/Rodolfo Gomes⁠⁠https://www.instagram.com/rodox_gomes⁠⁠Felipe Oliveira⁠⁠⁠⁠https://www.instagram.com/felipe_futeboteco⁠⁠Alexandre Ferreira ⁠⁠⁠⁠https://www.instagram.com/ale_ferrei⁠⁠ra_sccp⁠⁠Murilo Franco⁠⁠⁠⁠https://www.instagram.com/murilomaisfranco/⁠⁠PRODUÇÃO:Cadu Souza⁠⁠⁠https://www.instagram.com/cedusouza_/⁠⁠⁠João Rodrigues⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/joaor_r⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠

Kap der Angst (Apple TV) | Neue Thriller-Serie mit Starbesetzung und Nervenkitzel-Potenzial Bei Apple TV startet am 05. Juni die Thriller-Serie „Kap der Angst“ (OT: "Cape Fear"). Als ausführende Produzenten wirken die Oscar-Preisträger Martin Scorsese und Steven Spielberg mit, ebenso der ebenfalls Oscar-prämierte Javier Bardem, der zugleich die Rolle des Max Cady übernimmt. Im Zentrum stehen die Anwälte Amanda und Steve Bowden (Amy Adams und Patrick Wilson), deren Leben aus den Fugen gerät, als der gefährliche Ex-Häftling Max Cady aus ihrer Vergangenheit entlassen wird. Die Vorlage basiert auf dem Roman „The Executioners“ von John D. MacDonald, der bereits als Grundlage für den Film von 1962 („Ein Köder für die Bestie“) sowie für Scorseses Remake von 1991 diente. Die zehnteilige Serie wird als Hitchcock-inspirierter Thriller beschrieben. Ob die Vorschusslorbeeren gerechtfertigt sind und ob sich „Kap der Angst“ wirklich lohnt, diskutieren Sven und Timo im Podcast. Viel Spaß mit der neuen Folge vom Tele-Stammtisch! Trailer Werdet Teil unserer Community und besucht unseren Discord-Server! Dort oder auch auf Instagram könnt ihr mit uns über Filme, Serien und vieles mehr sprechen. Website | Youtube | PayPal | BuyMeACoffee Großer Dank und Gruß für das Einsprechen unseres Intros geht raus an Engelbert von Nordhausen. Thank you very much to BASTIAN HAMMER for the orchestral part of the intro! I used the following sounds of freesound.org: 16mm Film Reel by bone666138 wilhelm_scream.wav by Syna-Max backspin.wav by il112 Crowd in a bar (LCR).wav by Leandros.Ntounis Short Crowd Cheer 2.flac by qubodup License (Copyright): Attribution 4.0 International (CC BY 4.0)

Tässä jaksossa herkutellaan erilaisilla tuotteilla, kuten sienillä täytetyllä hatsapurilla, homeisella luolajuustolla ja tunkiossa mädätetyllä lampaalla. Mutta kerrankin Timo ei halua tunkea mitään takapuoleen. Mittailemme myös setämieheytemme astetta ja istumme karvanojatuoleissa kuuntelemassa klassista musiikkia. Aamuklubin parhaissa paloissa kehutaan Mannerheimia, ihmetellään Madonnan paljasta tissiä ja saadaan hyvät kyydit veneeltä ja Sirkalta.

Este episodio de “GMX Informa” nos centramos en el transporte marítimo como alternativa estratégica frente al terrestre, destacando la infraestructura portuaria de México, sus retos y oportunidades, y la importancia de contar con una póliza especializada para embarcaciones. Acompáñanos a conocer mas sobre esta interesante cobertura. ¿Tienes dudas, comentarios o deseas ponerte en contacto con nosotros? Escríbenos a: podcast@gmx.com.mx GMX Seguros es una empresa mexicana de Seguros especializada en Responsabilidad Civil y Daños, la cual cuenta con diferentes líneas de negocio. Con 28 años de trayectoria, conocemos el mercado de los seguros; lo que nos ha hecho desarrollar de manera constante productos innovadores, que resuelven las necesidades de protección ante distintos riesgos.

Este episodio de “GMX Informa” nos centramos en el transporte marítimo como alternativa estratégica frente al terrestre, destacando la infraestructura portuaria de México, sus retos y oportunidades, y la importancia de contar con una póliza especializada para embarcaciones. Acompáñanos a conocer mas sobre esta interesante cobertura. ¿Tienes dudas, comentarios o deseas ponerte en contacto con nosotros? Escríbenos a: podcast@gmx.com.mx GMX Seguros es una empresa mexicana de Seguros especializada en Responsabilidad Civil y Daños, la cual cuenta con diferentes líneas de negocio. Con 28 años de trayectoria, conocemos el mercado de los seguros; lo que nos ha hecho desarrollar de manera constante productos innovadores, que resuelven las necesidades de protección ante distintos riesgos.

Timo, Steven en Janneke duiken in het nieuwe datingprogramma Daten in het dorp op Texel. Als (quasi-)dorpsgenoten zijn zij bij uitstek het aangewezen trio om dit programma te ontleden.De mannen passeren uitgebreid de revue. Van Jacco, die stiekem uit Volendam blijkt te komen, tot de Texelse radio-dj 'Mike Jagger'. Ook Mark blijft niet onbesproken na zijn ontdekking dat oesters een nogal opwindende werking kunnen hebben. Gelukkig brengt de sympathieke Paul wat romantische stabiliteit: hij vormt nu al het koppel van het jaar met Jeltien.Daarnaast verbazen de hosts zich over de stroom aan vrouwen die in grote getale per boot het eiland bereikt, al is er tot nu toe nog geen enkele naam blijven hangen. Tot slot blikken ze vooruit: is dit format de potentie om de nieuwe Boer Zoekt Vrouw te worden, en hoe kan de NPO het programma nóg sterker maken?See omnystudio.com/listener for privacy information.

In dieser Folge ist Aaron zurück und direkt komplett im Fiebertraum: Slapfight-Moderation, Champions-League-Finale in Budapest, verspätete Flüge und Baumhaus-Diskussionen mit dem Kind. Außerdem geht's um Kindertag, Puff-Geschichten, Politik, alte BILD-Zeiten und warum Timo in den Kommentaren komplett zerlegt wird.Lob, Kritik und Freundschaftsanfragen wie immer an:https://www.instagram.com/einfachtimo/Unser Gast Nathalie auf Instagramhttps://www.instagram.com/nathalie_yk/?hl=de

Welcome to All Saints Church Worcester! In this podcast, we invite you to join us for a heartfelt worship gathering that celebrates our faith and community. 

Viele Selbstständige und Unternehmer glauben, dass gute Arbeit automatisch zu Erfolg führt.Ich habe das früher übrigens auch geglaubt.Mein heutiger Gast Timo Hannemann hat diese Erfahrung auf besonders intensive Weise gemacht. Jahrelang ist er mit seinen Selbstständigkeiten gescheitert, obwohl die Qualität seiner Arbeit gestimmt hat. Erst als er begann, sich mit Marketing auseinanderzusetzen, hat sich sein gesamtes Leben verändert.In dieser Folge sprechen wir darüber, warum Können allein oft nicht genügt und weshalb Sichtbarkeit kein Luxus, sondern eine Voraussetzung für Erfolg ist.Timo erzählt offen von seinem Weg: Vom Spitzensportler und Weltmeister über schwere gesundheitliche Rückschläge bis hin zu seiner heutigen Arbeit als Marketingexperte.Wir sprechen unter anderem darüber:warum viele Selbstständige an fehlender Sichtbarkeit scheiternweshalb Marketing nichts mit Manipulation, aber viel mit Psychologie zu tun hatwarum die besten Produkte oft übersehen werdenwelche Rolle Disziplin und Konsequenz auf dem Weg zum Erfolg spielenweshalb Feedback einer der größten Erfolgshebel überhaupt istwarum Talent überschätzt und Training unterschätzt wirdwie man komplexe Botschaften so kommuniziert, dass Menschen sie wirklich verstehenBesonders spannend fand ich Timos Sicht auf Erfolg:Nicht die Idee entscheidet. Nicht die Motivation entscheidet. Sondern die Fähigkeit, über Jahre hinweg die richtigen Dinge konsequent zu tun.Außerdem sprechen wir über eine Frage, die viele Menschen beschäftigt:Warum kommen manche scheinbar so viel schneller voran als andere?Die Antwort hat oft weniger mit Talent zu tun, als wir glauben – und deutlich mehr mit Fokus, Training, Feedback und der Bereitschaft, Hilfe anzunehmen.Ein Gedanke aus dieser Folge ist mir besonders geblieben:Es reicht nicht, viel zu tun. Du musst die richtigen Dinge tun – und sie richtig tun.Die Botschaft dieser Folge: Qualität ist wichtig. Aber erst wenn Menschen verstehen, welchen Wert du wirklich lieferst, kann daraus Erfolg entstehen.

Timo & Mattey widmen sich in dieser Folge dem anstehenden Großen Preis von Monaco in Monte Carlos, die Gerüchte um einen Wechsel bei Cadillac und natürlich den Einstieg von Gucci als Namenssponsor bei Alpine. Am Schluss gibt es außerdem wie gewohnt die Tipps für das kommende Rennwochenende. Viel Spaß!

Darien from Muses of Mythology joins The Great Project as we examine how this episode of Sabrina the Teenage Witch was almost certainly written to be about more parks than the one that opened two days prior to airing.Hosted by Tim O'Connor and AJ SalisburyCover art by @chipstercreates.bsky.social on BlueskyFacebook: facebook.com/Standby-LineInstagram: instagram.com/standbylinepodcastPatreon: patreon.com/standbylinepodcastEmail: standbylinepodcast@gmail.comNo portion of this episode may be used for AI training purposes or to create derivative works without express written permission from the creators and co-hosts Timothy O'Connor or Anthony Salisbury.

Federico analiza la declaración del perito Pedro Martín Molina en la comisión del Senado.

Every watch collector has wondered about this at some point. If you could go back to the beginning, armed with everything you know now, what would you do differently? Would you buy fewer watches, take bigger risks, or even skip certain phases altogether? In this episode of Fratello Talks, Nacho is joined by RJ and Timo to tackle exactly that question. Looking at today's watch landscape rather than the one they entered years ago, the three discuss the watches they would buy if they were starting their collecting journeys from scratch. Along the way, they touch on changing tastes, lessons learned, and how the market itself has evolved.

Hello Fluffle Fam! People often are not aware of how unique and different every single bunny is from another. Today's episode is a loving tribute to the very specific, very individual, sometimes completely inexplicable things that my four bunnies do/did. From Roo's mysterious rug opinions and snow flops, to Kumo's upstairs zoomies detours and wiggly dances, to Linus kissing inanimate objects and Timo's obsession with foot snuggles - these are four completely distinct little souls and our stories will show that. This one made me laugh and it made my heart very full. I hope it does the same for you.

Heute ist Nathalie aus unserem Team zu Gast. Wer wohl die berühmteste Person in ihrem Telefonbuch ist? Timo und Marvin sind erschöpft vom Leben und stellen fest: das was wir in unserem Job in einem Jahr erleben, erleben andere im ganzen Leben. Nathalie auf Insta https://www.instagram.com/nathalie_yk/?hl=deLob, Kritik und Freundschaftsanfragen wie immer an:https://www.instagram.com/einfachtimo/

My guest this week is Tim O'Brien and he joins me to chat about 'The Tim O'Brien Songbook', a handpicked selection of 40 of his songs, complete with notation, chords, Nashville number charts and thoughts from Tim on singing and songwriting.We talk about Tim's journey from being an instrumentalist, to a singer, then a songwriter, and some of the key points along the way, as well as how he set about choosing the songs for the book. He shares his thoughts on co-writing and why songs don't always need an introduction, plus some insights into his process and what he's learned over several decades as one of the best loved singers and songwriters in the acoustic world.You can buy the songbook (along with many of Tim's recordings) via Tim's website, where you'll also find tour dates and links to his social channels. Support the show===Thanks to Bryan Sutton for his wonderful theme tune to Bluegrass Jam Along (and to Justin Moses for playing the fiddle!)Bluegrass Jam Along is proud to be sponsored by Collings Guitars and Mandolins and Token premium guitar picks- Sign up to get updates on new episodes - Free fiddle tune chord sheets- Here's a list of all the Bluegrass Jam Along interviews- Follow Bluegrass Jam Along for regular updates:InstagramFacebook- Review us on Apple Podcasts

Deze keer een iets andere aflevering. Timo, Tom en Sophie bespreken de schandalen rondom MAFS UK. Afgelopen week kwam naar buiten dat twee vrouwen zijn verkracht tijdens de opnames van Married At First Sight UK. Een derde vrouw heeft melding gemaakt van vermeend seksueel geweld. Ze zeggen dat het programma onvoldoende heeft gedaan om hen te beschermen, dat de producent op de hoogte was van de beschuldigingen voor de afleveringen werden uitgezonden en dat ze er toch gewoon mee zijn doorgegaan. Inmiddels is de Britse show volledig van de buis en zijn alle seizoenen per direct van de streamingplatforms verwijderd. Wat zegt dit over Reality TV en wat betekent dit schandaal voor de toekomst van MAFS? Heb jij iets meegemaakt, of ken je iemand die iets heeft meegemaakt en wil je erover praten? Dan kun je 24/7 terecht bij Centrum Seksueel geweld op 0800-0188. Praat je liever met de politie, bel dan 0900-8844 of een politiebureau bij je in de buurt.See omnystudio.com/listener for privacy information.

Vieraana Varjon toimitusjohtaja Timo Toikkanen https://varjo.com/ Mythos found 271 zero days in Firefox https://arstechnica.com/information-technology/2026/05/mozilla-says-271-vulnerabilities-found-by-mythos-have-almost-no-false-positives/ Mythos ja Curl https://daniel.haxx.se/blog/2026/05/11/mythos-finds-a-curl-vulnerability/ Game On Tampere https://www.tampere-talo.fi/tapahtuma/gameon/ Summer Games Done Quick https://gamesdonequick.com/ H7 Skrolli t-paita https://skrolli.fi/product-category/t-paidat/ Latitude 25, Helsinki https://www.latitude25.fi Mont Saint-Michel https://fi.wikipedia.org/wiki/Mont_Saint-Michel

Johannes' Nerven liegen blank. Als sein neugeborener Sohn sich nicht beruhigen lässt, schreit er seine Freundin so heftig an, dass sie aus der Wohnung flieht. „Das ist Gewalt“, sagt sie bei der Rückkehr. Lange möchte Johannes das nicht wahrhaben. Stukenberg, Timo www.deutschlandfunkkultur.de, Plus Eins

Live from the University of Evansville campus and the Shanklin Theatre, where Rami Malek once trod the boards… One True Podcast welcomes Alex Vernon for an interview recorded live in front of a captive audience of students, faculty, and community members in Evansville, Indiana, as he discusses his magnificent new biography of Tim O'Brien, Peace Is a Shy Thing: The Life and Art of Tim O'Brien.Vernon explains his process of how to write a true biography, O'Brien's life and relationship to the Vietnam War, what distinguishes O'Brien's style as a writer, the enduring power of some of his greatest work, and much more. It is a generous, penetrating Q&A session with the world's preeminent O'Brien scholar.Vernon – who has previously joined One True Podcast for a discussion of Hemingway and War, as well as an episode devoted to “Soldier's Home” – lends his essential perspective to this essential contemporary writer.** Special thanks to the UE students for their insightful questions at the end, and to the wizardry of sound designer Jon Robertson for his assistance. ** Episode BibliographyTim O'Brien works mentioned:Going After CacciatoIf I Die in a Combat ZoneIn the Lake of the WoodsThe Things They CarriedOther works mentioned:Five-volume biography of Hemingway by Michael Reynolds (The Young Hemingway, Hemingway: The Paris Years, Hemingway: The Homecoming, Hemingway: The 1930s, Hemingway: The Final Years)

"Voll der Autist!". Sprache kann schnell stigmatisieren und ausgrenzen - mit Folgen für Betroffene. Forschung zeigt, wie auch medizinische Begriffe neurodivergente Menschen abwerten. Allerdings ändert sich allmählich etwas. Opitz, Till; Grampes, Timo; Kühn, Kathrin www.deutschlandfunk.de, Systemfragen

"Voll der Autist!". Sprache kann schnell stigmatisieren und ausgrenzen - mit Folgen für Betroffene. Forschung zeigt, wie auch medizinische Begriffe neurodivergente Menschen abwerten. Allerdings ändert sich allmählich etwas. Opitz, Till; Grampes, Timo; Kühn, Kathrin www.deutschlandfunk.de, Systemfragen

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

Irán ha respondido a la última propuesta de EEUU para poner fin al conflicto y lo ha hecho a través, nuevamente, de Pakistan. Su respuesta llega poco después de que tanto Washington como Tel Aviv hayan amenazado al régimen con volver a los ataques.Vamos a estar con nuestro corresponsal en Jerusalén, Santi Echevarría. Además, hoy tendremos entrevista con Beatriz Martos, responsable de pena de muerte en Amnistía Internacional España. Esta organización ha publicado hoy su informe anual sobre la pena capital y las ejecuciones en el mundo, que han aumentado en 2025 con Irán y China liderando el ranking.Vamos a estar en Reino Unido, donde a raíz de la lucha en el laborismo por intentar sacar del poder a Keir Starmer, ha resurgido con fuerza el debate en torno al Brexit.Tenemos un reportaje sobre la guerra en torno a la fresa en Francia, estaremos en Perú donde los dos candidatos a la segunda vuelta de las presidenciales ya están en campaña y también en Bolivia, siguiendo de cerca las protestas contra el gobierno de Rodrigo Paz. Además, seguiremos de cerca las novedades en torno al brote de ébola declarado en República Democrática del Congo y lo que ha dicho la OMS al respecto.Escuchar audio

Rodolfo Gomes, Felipe Oliveira, Alexandre Ferreira e Murilo Franco debatem sobre os rivais de São Paulo. O Fala, Rival! tem apresentação de Edu Futirinhas! APOIO BETNACIONALSe for maior de 18 anos aposte na BetNacional:⁠⁠⁠⁠⁠⁠⁠⁠⁠https://betnacional.bet.br/⁠⁠⁠⁠⁠⁠⁠⁠⁠REDES SOCIAIS:Instagram:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/futebotecotv/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Twitter:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/FutebotecoTV⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Facebook:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.facebook.com/futebotecotv⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠TikTok:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.tiktok.com/@futebotecotv?⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Kwai:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.kwai.com/@futebotecoTV⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠------------------------------------------------------------APRESENTADORES:Edu Futirinhas⁠https://www.instagram.com/edufutirinhas/Rodolfo Gomes⁠⁠https://www.instagram.com/rodox_gomes⁠⁠Felipe Oliveira⁠⁠⁠⁠https://www.instagram.com/felipe_futeboteco⁠⁠Alexandre Ferreira ⁠⁠⁠⁠https://www.instagram.com/ale_ferrei⁠⁠ra_sccp⁠⁠Murilo Franco⁠⁠⁠⁠https://www.instagram.com/murilomaisfranco/⁠⁠PRODUÇÃO:Cadu Souza⁠⁠⁠https://www.instagram.com/cedusouza_/⁠⁠⁠João Rodrigues⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/joaor_r⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠

The Great Project looks at Boy Meets World headed to Florida, and how in sitcoms, no one is allowed to have a normal conversation, even when they're actively trying.Hosted by Tim O'Connor and AJ SalisburyCover art by @chipstercreates.bsky.social on BlueskyFacebook: facebook.com/Standby-LineInstagram: instagram.com/standbylinepodcastPatreon: patreon.com/standbylinepodcastEmail: standbylinepodcast@gmail.comNo portion of this episode may be used for AI training purposes or to create derivative works without express written permission from the creators and co-hosts Timothy O'Connor or Anthony Salisbury.

Rodolfo Gomes, Felipe Oliveira, Alexandre Ferreira e Murilo Franco debatem sobre os rivais de São Paulo. O Fala, Rival! tem apresentação de Edu Futirinhas! APOIO BETNACIONALSe for maior de 18 anos aposte na BetNacional:⁠⁠⁠⁠⁠⁠⁠⁠⁠https://betnacional.bet.br/⁠⁠⁠⁠⁠⁠⁠⁠⁠REDES SOCIAIS:Instagram:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/futebotecotv/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Twitter:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/FutebotecoTV⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Facebook:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.facebook.com/futebotecotv⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠TikTok:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.tiktok.com/@futebotecotv?⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Kwai:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.kwai.com/@futebotecoTV⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠------------------------------------------------------------APRESENTADORES:Edu Futirinhas⁠https://www.instagram.com/edufutirinhas/Rodolfo Gomes⁠⁠https://www.instagram.com/rodox_gomes⁠⁠Felipe Oliveira⁠⁠⁠⁠https://www.instagram.com/felipe_futeboteco⁠⁠Alexandre Ferreira ⁠⁠⁠⁠https://www.instagram.com/ale_ferrei⁠⁠ra_sccp⁠⁠Murilo Franco⁠⁠⁠⁠https://www.instagram.com/murilomaisfranco/⁠⁠PRODUÇÃO:Cadu Souza⁠⁠⁠https://www.instagram.com/cedusouza_/⁠⁠⁠João Rodrigues⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/joaor_r⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠

Timo, Stephanie en Dook vragen zich deze aflevering af of Anton Linda echt een ‘kutwijf’ heeft genoemd, of postuur iets anders is dan dik en waarom er niet gevingerd wordt in de hottub. Verder bespreken ze het opklapbed van Linda, is dat aandachttrekkerij? Was die therapie-cirkel nou echt nodig? En is Do gevaarlijk omdat hij Fer zijn identiteit ontneemt? Heb jij een hot take, spannende achtergrondinformatie of wil je heel graag je mening met ons delen? Stuur ons dan een (voice)berichtje op Instagram. En volg ons daar voor memes, behind the scenes en meer! Ga naar @realitycheck_depodcast op Instagram en Tiktok. Wil je adverteren in deze podcast? Dat kan! Mail naar adverteren@dagennacht.nlSee omnystudio.com/listener for privacy information.

In dieser Folge wird's maximal unangenehm: Wir fragen uns, wann endlich in unseren Wikipedia-Artikeln steht, dass wir heimliche P***oproduzenten sind. Außerdem erzählt Aaron eine absurde Story von seinem letzten Flug, bei dem niemand im Flieger Erdnüsse öffnen durfte, weil jemand eine extrem heftige Allergie. Timo wird derweil von fünf Thais abgezogen und Marvin steht morgen vor Gericht. Eine Folge zwischen Achtung Abzocke, Halbwahrheiten und Knast. Lob, Kritik und Freundschaftsanfragen wie immer an:https://www.instagram.com/einfachtimo/

Gründen mit Kindern als Zielgruppe

Helloooo! We're back! And this time, we have video! That's right, you finally get to put a face to the bunmom voice. In today's episode I'm sharing the things that having my four bunnies - Roo, Linus, Timo, and Kumo - has taught me. Things I never expected, didn't see coming, and wouldn't trade for anything. It's personal, it's a little funny, and it comes straight from the heart. Grab your cup of tea and come sit with me. I'm so glad you're here. Video is available on Spotify and YouTube! Come watch over there if you want to finally see bunmom in person!

Episode 790: May 2, 2026 playlist: Pop Will Eat Itself, "1000 X No (PWEI.40 Rework feat. Stephen Mallinder)" (1000 X No (PWEI.40 Rework)) 2026 Republic of Music Robert Aiki Aubrey Lowe, "The Colony" (Manifestations in the Shadow of an Unknown Land) 2026 Kou Anjimile, "Like You Really Mean It" (You're Free to Go) 2026 4AD Shawescape Renegade, "78 Light Years From Earth" (Exoframe) 2026 Tresor Cate Kennan, "Devil's Hour" (Shadows) 2026 Kranky Dove, "After All the Rain Has Gone" (After All the Rain Has Gone / Grind On) 2026 Deena Carl Craig, "Meditation Five" (Meditations) 2026 Planet E Jac Berrocal, Vincent Epplay, Timo van Luijk, (Anne Gillis), "Sphere de Dyson" (Ste Cy) 2026 La Scie Doree Ibrahim Alfa Jnr., "Naked Lunchbreak" (Infinite Black Inside) 2026 FO Cloud Circuit, "When My Lover Is Across the Ocean" (Cloud Circuit) 2026 Watch That Ends The Night Eluvium, "A.M." (Virga III) 2026 Temporary Residence Email podcast at brainwashed dot com to say who you are; what you like; what you want to hear; share pictures for the podcast of where you're from, your computer or MP3 player with or without the Brainwashed Podcast Playing; and win free music! We have no tracking information, no idea who's listening to these things so the more feedback that comes in, the more frequent podcasts will come. You will not be put on any spam list and your information will remain completely private and not farmed out to a third party. Thanks for your attention and thanks for listening.

In this episode, I sit down with Tim O'Connor—golf coach, author of Getting Unstuck, and one of the most refreshing voices in golf psychology—to unpack why so many golfers stay trapped in the same frustrating cycles year after year. Tim explains why being "stuck" has less to do with mechanics and more to do with unconscious patterns, repetitive thinking, fear-based control, and a disconnect from the physical experience of playing golf. We also explore surrender, awareness, gratitude, adaptability, and why the golfers who improve fastest are often the ones who stop trying so hard. In this episode, you'll learn: What being "stuck" actually feels like for golfers Why fixing your swing mid-round keeps you trapped How awareness is the first step to lasting change Why golfers overthink because they're disconnected from feel How to stop bringing swing thoughts to the course Why surrender creates more control than forcing outcomes How gratitude can instantly improve your relationship with golf If you've ever chased swing tips mid-round, sabotaged a great start, overthought every shot, or felt like your scores no longer reflect your ability, this conversation will hit home. Get your pencils ready and start listening.  Apply for 1-1 High-Performance Hypnotherapy and Mindset Coaching: Click here to apply to work with me. The 90-Day Golf Identity Upgrade Accelerator: This is a private 3-month coaching container designed to help serious golfers rapidly upgrade their beliefs, rewire their golf identity, and accelerate lower scores through deep subconscious transformation — not surface-level tactics. Click here to learn more and DM me "identity upgrade" on Instagram (@thepaulsalter) to learn more.  More About Tim O'Connor Tim O'Connor is a performance coach with more than 30 years of experience in golf as an author and coach. Tim is co-host of the Swing Thoughts podcast. Tim is mental performance coach of the GTS Academy in Las Vegas and Zone Golf Academy in British Columbia and co-host of the Swing Thoughts podcast with "Humble Howard" Glassman. He's written five books including The Feeling of Greatness: The Moe Norman Story, and Getting Unstuck: 7 Transformational Practices for Golf Nerds. And he plays bass guitar in a punk rock band in Guelph. Play to Your Potential On (and Off) the Course Schedule a Mindset Coaching Discovery Call Subscribe to the More Pars than Bogeys Newsletter Download my "Play Your Best Round" free hypnosis audio recording. High-Performance Hypnotherapy and Mindset Coaching Paul Salter - known as The Golf Hypnotherapist - is a High-Performance Hypnotherapist and Mindset Coach who leverages hypnosis and powerful subconscious reprogramming techniques to help golfers of all ages and skill levels overcome the mental hazards of their minds so they can shoot lower scores and play to their potential. He has over 16 years of coaching experience working with high performers in various industries, helping them get unstuck, out of their own way, and unlock their full potential. Click here to learn more about how high-performance hypnotherapy and mindset coaching can help you get out of your own way and play to your potential on (and off) the course.  Instagram: @thepaulsalter Key Takeaways: Most golfers stay stuck because they repeat familiar patterns. Thinking more often creates worse golf, not better golf. Feel is frequently the missing link in performance. Great golf requires adaptability, not perfection. Gratitude brings you back to the present moment. Key Quotes: "You cannot change what you are not aware of." "Most golfers have never actually felt their swing because they're trapped in their head." "The game is about hitting shots—not building the perfect swing." "The more you try to control everything, the less free you are to perform." "Your suffering in golf often comes from wanting it too badly." Time Stamps: 00:00: Understanding the Feeling of Being Stuck in Golf 02:37: The Importance of Awareness in Overcoming Stuckness 05:22: Experiencing the Physical Sensation of the Swing 08:22: Breaking Through Performance Barriers 11:14: The Role of Surrender and Letting Go in Golf 14:06: Creating a Warm-Up Routine for Success 16:42: Adapting to Your Game on the Course 25:06: Breaking Free from Expectations 25:33: Predictable Sabotage in Golf 27:22: The Complexity of Golf Performance 28:37: Understanding Variance in Golf 30:27: Expectation Management in Golf 31:46: The Writing Journey of 'Getting Unstuck' 34:25: Target Audience for 'Getting Unstuck' 36:27: The Key Takeaway: Awareness