Podcasts about larger

Q 149, Is any man able perfectly to keep the commandments of God? This is the text from the Westminster Larger Catechism for the Chapel Library - William Gouge's name is attached as a representative of the entire assembly.

Exodus 20:13 Thou shalt not kill. This is the text from the Westminster Larger Catechism for the Chapel Library - William Gouge's name is attached as a representative of the entire assembly.

This is the text from the Westminster Larger Catechism for the Chapel Library - William Gouge's name is attached as a representative of the entire assembly.

This is the text from the Westminster Larger Catechism for the Chapel Library - William Gouge's name is attached as a representative of the entire assembly. 4 Thou shalt not make unto thee any graven image, or any likeness of any thing that is in heaven above, or that is in the earth beneath, or that is in the water under the earth: 5 Thou shalt not bow down thyself to them, nor serve them: for I the LORD thy God am a jealous God, visiting the iniquity of the fathers upon the children unto the third and fourth generation of them that hate me; 6 And shewing mercy unto thousands of them that love me, and keep my commandments.

Exodus 20:8 Remember the sabbath day, to keep it holy. 9 Six days shalt thou labour, and do all thy work: 10 But the seventh day is the sabbath of the LORD thy God: in it thou shalt not do any work, thou, nor thy son, nor thy daughter, thy manservant, nor thy maidservant, nor thy cattle, nor thy stranger that is within thy gates: 11 For in six days the LORD made heaven and earth, the sea, and all that in them is, and rested the seventh day: wherefore the LORD blessed the sabbath day, and hallowed it.This is the text from the Westminster Larger Catechism for the Chapel Library - William Gouge's name is attached as a representative of the entire assembly.

Exodus 20:12 Honour thy father and thy mother: that thy days may be long upon the land which the LORD thy God giveth thee. This is the text from the Westminster Larger Catechism for the Chapel Library - William Gouge's name is attached as a representative of the entire assembly.

Exodus 20:7 Thou shalt not take the name of the LORD thy God in vain; for the LORD will not hold him guiltless that taketh his name in vain. This is the text from the Westminster Larger Catechism for the Chapel Library - William Gouge's name is attached as a representative of the entire assembly.

Exodus 20:14 Thou shalt not commit adultery. This is the text from the Westminster Larger Catechism for the Chapel Library - William Gouge's name is attached as a representative of the entire assembly.

Exodus 20 15 Thou shalt not steal. This is the text from the Westminster Larger Catechism for the Chapel Library - William Gouge's name is attached as a representative of the entire assembly.

Exodus 20:16 Thou shalt not bear false witness against thy neighbor. This is the text from the Westminster Larger Catechism for the Chapel Library - William Gouge's name is attached as a representative of the entire assembly.

This is the text from the Westminster Larger Catechism for the Chapel Library - William Gouge's name is attached as a representative of the entire assembly.

Exodus 20:17 Thou shalt not covet thy neighbour's house, thou shalt not covet thy neighbour's wife, nor his manservant, nor his maidservant, nor his ox, nor his ass, nor any thing that is thy neighbor's.

John Puls, a psychotherapist and clinical social worker who works with teens and young adults, joins Megan Lynch. Why are seemingly more teens taking part in 'takeovers', some of which become violent? 'They want to experience this rush,' and gain more attention, says Puls. 'There's a group-think mentality' when they're are with each other explains Puls, 'the off-switch doesn't exist.'

This week, we'll see how Paul practices living into a larger story even in the midst of very painful circumstances.

The Lost Art of Common Sense Live!We give our blue collar Common Sense thoughts on current events, bringing on interesting guests and talking about whatever random topics come to mind!We'll also throwing out our winners and losers of the week, running down the Happenens of the week and Matt will be reviewing "Obsession".Guest Project Links:Dr. Nelva Lee: Running for Georgia State Superintendent of Schoolshttps://www.drnelvalee.com/Sean Martin: Frontman for The Quarantinedhttps://thequarantined.com/musicDr. Chase Spearshttps://chasespears.com/Digital Democracy Project:Get informed and your voice heardhttps://digitaldemocracyproject.orgTom Joseph - America's Main Street Party:https://x.com/americasmainstGuest Book Links:Pastor Jackson Lahmeyer Book: Chasing After the Wind. https://books.jacksonlahmeyer.com/products/chasing-after-the-windLinks to Barry D. Todd's Book: Stand Your Ground: One Man's Self-Defense Nightmare.https://standyourgroundbook.com/Video Links:The Founding Fathers Thought's on 2A Regulations: A Grok3 Extrapolationhttps://youtu.be/aflX6EjPSak?si=BJntRHHusTrQQKTGMerch Shop:https://www.etsy.com/shop/LostArtofCommonSense?ref=seller-platform-mcnavSponsor Links:www.yummytummybbq.com#CommonSense #democrat #republican #politics #moviereview #trump #news #winnersandlosers #happenings #funny #subversion

On today's show we look at some AppleTV and Home announcements from the Apple WWDC and look at what that fuss is about the new Sony's True RGB TVs. We also read your emails and take a look at the week's news. News: Households Used More Than 10 Video Services Daily Google Rolls Out a Major Update to Its Google TV Streamer 4k Apple TV from Apple's WWDC 2026 Key takeaways for Apple TV from Apple's WWDC 2026 are relatively modest and software-focused, as the event emphasized iOS 27. tvOS 27 Highlights for Apple TV Larger Text / System-Wide Text Size Adjustment: A new accessibility option lets users increase on-screen text size across supported apps and the interface. AI-Generated / On-Device Subtitles: tvOS 27 adds real-time automatic subtitle generation for videos lacking built-in captions (including personal content).  Other Refinements: Expect Liquid Glass UI polish, performance/stability improvements, smarter recommendations, and better smart home/HomeKit ties. Siri upgrades (more conversational, on-screen awareness) should improve voice control on Apple TV, though full Apple Intelligence features may wait for new hardware. tvOS 27 developer betas are available now post-keynote, with public release expected in fall 2026 alongside other OS updates. As far as the Apple Home app goes, updates  mainly dealt with Apple Intelligence integration for smarter camera handling and notifications: The Home app now uses Apple Intelligence to generate natural language descriptions of compatible camera footage, letting you search clips conversationally by saying something like,  "show me when the dog was in the backyard" Smarter batched notifications that feel less overwhelming. Alerts are intelligently grouped and dynamic instead of constant floods. Accessory updates update in real-time as conditions change. With deeper Siri AI and Shortcuts integration you can describe automations in natural language and let Siri build them (including Home shortcuts). Voice control becomes more conversational and context-aware. Hardware Notes No new Apple TV 4K hardware was announced at WWDC (consistent with expectations). A refreshed model with A17 Pro (or similar) for full Apple Intelligence/Siri 2.0 support, better smart home capabilities, and possibly Wi-Fi 7 has been "ready for months" but is being held for later in 2026 to align with the advanced AI features. What is Sony's True RGB TV All About? Sony's True RGB is Sony's marketing name for their advanced RGB Mini-LED backlight technology, introduced in 2026 for high-end BRAVIA TVs the BRAVIA 9 II and BRAVIA 7 II series. How True RGB Works Traditional Mini-LED or QLED TVs typically use white or blue LEDs as the backlight, then pass that light through color filters or Quantum Dots to create colors. This filtering process can reduce color purity, brightness, and efficiency. Sony's True RGB technology takes a different approach by using tiny independent red, green, and blue (RGB) LEDs in the backlight, with each color LED controllable separately across thousands or even millions of local dimming zones, generating color directly at the light source before it reaches the LCD layer rather than filtering white light. Sony's True RGB technology delivers purer and more accurate colors with a significantly wider color volume and gamut, higher peak brightness while maintaining excellent color accuracy, superior contrast and black levels that can challenge OLED performance in certain scenarios, improved energy efficiency through smart power distribution algorithms that use less power than previous generations, and outstanding off-angle viewing with minimal color shift. Key Advantages Sony Highlights Sony's True RGB technology delivers true-to-source color accuracy, backed by the company's deep professional monitor expertise and decades of innovation in RGB technology dating back to the groundbreaking 2004 QUALIA series. This is powered by advanced RGB Backlight Master Drive processing that expertly manages the immense complexity of controlling millions of individual colored diodes in real time. Overall, it successfully combines the best of Mini-LED brightness with near-OLED levels of color performance and contrast. In short, True RGB is Sony's premium implementation of direct RGB Mini-LED backlighting. Sony emphasizes not just the hardware (RGB LEDs), but their proprietary optical design, drivers, and image processing to make it perform better than competing RGB LED TVs from other brands. Sony True RGB Models with Pricing (2026 Lineup) Prices are MSRP/launch pricing (as of mid-2026; actual street prices and sales vary by retailer like Best Buy, Crutchfield, or Sony's site). Larger sizes command big premiums. BRAVIA 7 II - more accessible entry into True RGB, excellent color and brightness for the price 50" — ~$1,600 55" — ~$2,100 65" — ~$2,600 75" — ~$3,100 85" — ~$4,000 98" — ~$9,000 BRAVIA 9 II - higher brightness, more advanced processing, better anti-glare, and local dimming performance 65" — ~$3,600 75" — ~$4,600 85" — ~$6,500 115" — ~$31,000 (a massive premium flagship option)

Retirement confidence is at its lowest level since 2017, and the twist is that many people are doing “fine” on paper. So why are folks hesitant to stop working? I walk through what I see after helping hundreds of retirees: Confidence is not built by a bigger portfolio. It is built by a clear plan you can follow when inflation spikes, the market drops, or health care costs surprise you.We start with the data behind the 2026 Retirement Confidence Survey and the real drivers of anxiety: Inflation, rising medical costs, Social Security and Medicare uncertainty, market volatility, and the fear of outliving your money. Then I break down the five building blocks of retirement confidence: Reliable income, cash reserves (including the five-year “war chest” to manage sequence of returns risk), a retirement tax strategy that considers RMDs, Social Security taxation, and IRMAA, thoughtful health care and long-term care planning, and most importantly a written retirement plan that ties it all together.

069 We've all heard of using jackpots, right? But what if it really is about making every reward mean more? In this episode, Megan talks about a recent article from neurosciencenews.com and shares how she's already been applying this information and what she observes in her learners. Here's the article: Large Reward Events Accelerate Learning Speed by Extending Brain Signals Episode mentioned in this podcast: Maintaining the Value of Your Reinforcers or View on Youtube Join the conversation in the free community and comment directly on this post to share your thoughts.

Life sciences is a hub of dealmaking activity. Over the past year, more than 30 transactions valued at $1 billion or more have crossed the finish line. But the picture in other segments of healthcare is more mixed. At RBC Capital Markets' Global Healthcare Conference in New York, Darren Campili, Global Head of Healthcare Investment Banking, hosts colleagues David Levin, Ahmed Attia and Jason Levitz to explore what's driving deals and where the opportunities are heading.Key PointsHealthcare M&A is strong, with a surge of high-value deals in life sciences.Equity performance is challenging, but investors in life sciences and biotech have seen good outcomes.IPO activity has rebounded; again, life sciences and biotech are most successful.Dealmaking has been largely unaffected by regulatory uncertainty, though challenges remain on reimbursement and MFN pricing.Larger companies believe they have the edge in using AI for profitability and competitiveness.Introductions [00:25]Host Darren Campili, Global Head of Healthcare Investment Banking, introduces the podcast and guests: David Levin, Co-Head of U.S. M&A; Ahmed Attia, Managing Director, Healthcare M&A; and Jason Levitz, Head of Healthcare Equity Capital Markets.M&A strength in healthcare [01:11]The M&A market in life sciences is extremely strong. The number of $1 billion-plus deals has tripled in the past year. There has been significant activity among mid-caps as well as large-cap companies, and a diversity of premiums.Healthcare in the equity markets [13:24]In the broader context of the U.S. equity markets, healthcare is performing poorly, particularly among large-cap medtech and services companies. At the same time, life sciences and biotechs are outperforming, leading to diverse outcomes for investors.IPO activity [15:20]IPO volumes have rebounded after some disappointing years. Deal flow has centered on oncology, I&I, and CNS.Political impact [24:15]Dealmaking has continued despite uncertainty over the FDA. Tariff policy has been a net positive for U.S. inflows as pharma businesses seek U.S. capabilities. Managing reimbursement and Most Favored Nation pricing remains challenging for some.

Life sciences is a hub of dealmaking activity. Over the past year, more than 30 transactions valued at $1 billion or more have crossed the finish line. But the picture in other segments of healthcare is more mixed. At RBC Capital Markets' Global Healthcare Conference in New York, Darren Campili, Global Head of Healthcare Investment Banking, hosts colleagues David Levin, Ahmed Attia and Jason Levitz to explore what's driving deals and where the opportunities are heading.Key PointsHealthcare M&A is strong, with a surge of high-value deals in life sciences.Equity performance is challenging, but investors in life sciences and biotech have seen good outcomes.IPO activity has rebounded; again, life sciences and biotech are most successful.Dealmaking has been largely unaffected by regulatory uncertainty, though challenges remain on reimbursement and MFN pricing.Larger companies believe they have the edge in using AI for profitability and competitiveness.Introductions [00:25]Host Darren Campili, Global Head of Healthcare Investment Banking, introduces the podcast and guests: David Levin, Co-Head of U.S. M&A; Ahmed Attia, Managing Director, Healthcare M&A; and Jason Levitz, Head of Healthcare Equity Capital Markets.M&A strength in healthcare [01:11]The M&A market in life sciences is extremely strong. The number of $1 billion-plus deals has tripled in the past year. There has been significant activity among mid-caps as well as large-cap companies, and a diversity of premiums.Healthcare in the equity markets [13:24]In the broader context of the U.S. equity markets, healthcare is performing poorly, particularly among large-cap medtech and services companies. At the same time, life sciences and biotechs are outperforming, leading to diverse outcomes for investors.IPO activity [15:20]IPO volumes have rebounded after some disappointing years. Deal flow has centered on oncology, I&I, and CNS.Political impact [24:15]Dealmaking has continued despite uncertainty over the FDA. Tariff policy has been a net positive for U.S. inflows as pharma businesses seek U.S. capabilities. Managing reimbursement and Most Favored Nation pricing remains challenging for some.

Listen and subscribe to Money Making Conversations on iHeartRadio, Apple Podcasts, Spotify, www.moneymakingconversations.com/subscribe/ or wherever you listen to podcasts. New Money Making Conversations episodes drop daily. I want to alert you, so you don’t miss out on expert analysis and insider perspectives from my guests who provide tips that can help you uplift the community, improve your financial planning, motivation, or advice on how to be a successful entrepreneur. Keep winning! Two-time Emmy and Three-time NAACP Image Award-winning, television Executive Producer Rushion McDonald interviewed Todd Kroupa A former firefighter turned top-producing real estate agent in Georgia. Todd explains his journey from a physically demanding fire department career to becoming a highly successful real estate broker, team leader, and luxury/equestrian property specialist. The conversation walks through: His transition from the fire service to real estate Opening and managing a 400‑agent office in Florida Relocating to Georgia and re-establishing his business How he advises both first-time homebuyers and experienced sellers Emotional decision-making in buying and selling Inspections, deal-breakers, and buyer/seller behavior Multi-generational housing trends post‑COVID Why real estate remains a wealth-building tool Advice for navigating neighborhoods, schools, and due diligence His eventual ranking as #1 single agent for Berkshire Hathaway in Georgia (2024–2025) Todd emphasizes integrity, long-term relationships, and guiding clients toward the right house — not just closing a deal. Purpose of the Interview The purpose of Todd Kroupa’s appearance is to: Share a motivational career-change story — moving from firefighter to top real estate agent. Educate listeners on the real estate process — including buying, selling, inspections, and market strategy. Give practical tips for first-time homebuyers, families, and multi-generational households. Promote best practices for choosing neighborhoods, navigating emotion in home buying, and avoiding pitfalls. Highlight Todd’s success and position him as a trusted resource for Georgia real estate clients. Key Takeaways 1. Career Transition & Motivation Todd became a firefighter in 1992, retired in 2014, and began real estate in 2002. Real estate appealed to him because it allowed him to continue helping people without the physical strain. He built and managed a 400-agent office before returning to working directly with clients — his true passion. 2. Balancing Firefighting and Real Estate He often worked both jobs full-time, with limited days off. Eventually, maintaining both became impossible: “I can’t do this anymore,” he told his wife. 3. Buyer Advice Buyers make decisions emotionally first, then logically. Within the first 3–5 minutes in a home, buyers often know if they like it. Lighting, paint color, home condition, and layout heavily influence emotional response. First-time buyers need extra guidance — like “teaching someone to drive for the first time.” 4. Seller Advice Selling isn’t just about market timing — presentation matters. Neutral paint colors and bright white lighting help increase buyer appeal. Every showing is won or lost in the first few minutes. 5. Inspections Matter — and Are Deal Breakers Top inspection walk‑aways: Mold Foundation issues Roof problemsTodd stresses that if a buyer is uncomfortable before closing, “you won’t be comfortable after you close.” 6. Emotion vs. Logic Many buyers get emotionally attached and ignore red flags. Todd’s rule: commissions should never drive decisions. 7. Multi-Generational Living Is Rising Driven by COVID, high child-care costs, rising home prices. Families are choosing: ADUs (Accessory Dwelling Units) “In-law suites” Larger family compounds 8. Real Estate as a Wealth Builder Unlike stock investments, real estate allows you to: Control, improve, alter, and live in the asset. Tax advantages like 1031 exchanges and mortgage deductions compound long-term value. 9. Don’t Buy the Most Expensive House in the Neighborhood Surrounding homes cap your resale value. You may have to wait years for nearby homes to “catch up.” 10. Neighborhood Due Diligence Realtors must avoid discrimination (Fair Housing Act). Buyers should: Visit neighborhoods at night and on weekends Speak with neighbors Review school ratings and county resources Notable Quotes (from the transcript) Career & Purpose “I love helping people. That’s why I became a fireman. Real estate was another way to help people.” “I wasn’t quite sure I wanted to manage long term… my heart was with clients.” Ethics & Commission “Commissions should never be above the people.” “If you’re focused on commissions, you need to pick a different industry.” Emotions in Home Buying “Buyers think they’re looking logically, but they’re looking emotionally first.” “Within the first 3–5 minutes, they already know if they like the home.” Inspections “If you’re not comfortable with the property now, you won’t be comfortable after you close.” Neighborhood Choice “Focus on the house, but look at the neighborhood — you can’t change your neighbors.” Wealth Building “With stocks you can’t control it, improve it, or live in it. With a home, you can.” Success & Determination “Someone told me when I moved to Georgia I wasn’t going to make it. Now I’m the number one salesperson in Georgia.” #SHMS #STRAW #BESTSupport the show: https://www.steveharveyfm.com/See omnystudio.com/listener for privacy information.

Listen and subscribe to Money Making Conversations on iHeartRadio, Apple Podcasts, Spotify, www.moneymakingconversations.com/subscribe/ or wherever you listen to podcasts. New Money Making Conversations episodes drop daily. I want to alert you, so you don’t miss out on expert analysis and insider perspectives from my guests who provide tips that can help you uplift the community, improve your financial planning, motivation, or advice on how to be a successful entrepreneur. Keep winning! Two-time Emmy and Three-time NAACP Image Award-winning, television Executive Producer Rushion McDonald interviewed Todd Kroupa A former firefighter turned top-producing real estate agent in Georgia. Todd explains his journey from a physically demanding fire department career to becoming a highly successful real estate broker, team leader, and luxury/equestrian property specialist. The conversation walks through: His transition from the fire service to real estate Opening and managing a 400‑agent office in Florida Relocating to Georgia and re-establishing his business How he advises both first-time homebuyers and experienced sellers Emotional decision-making in buying and selling Inspections, deal-breakers, and buyer/seller behavior Multi-generational housing trends post‑COVID Why real estate remains a wealth-building tool Advice for navigating neighborhoods, schools, and due diligence His eventual ranking as #1 single agent for Berkshire Hathaway in Georgia (2024–2025) Todd emphasizes integrity, long-term relationships, and guiding clients toward the right house — not just closing a deal. Purpose of the Interview The purpose of Todd Kroupa’s appearance is to: Share a motivational career-change story — moving from firefighter to top real estate agent. Educate listeners on the real estate process — including buying, selling, inspections, and market strategy. Give practical tips for first-time homebuyers, families, and multi-generational households. Promote best practices for choosing neighborhoods, navigating emotion in home buying, and avoiding pitfalls. Highlight Todd’s success and position him as a trusted resource for Georgia real estate clients. Key Takeaways 1. Career Transition & Motivation Todd became a firefighter in 1992, retired in 2014, and began real estate in 2002. Real estate appealed to him because it allowed him to continue helping people without the physical strain. He built and managed a 400-agent office before returning to working directly with clients — his true passion. 2. Balancing Firefighting and Real Estate He often worked both jobs full-time, with limited days off. Eventually, maintaining both became impossible: “I can’t do this anymore,” he told his wife. 3. Buyer Advice Buyers make decisions emotionally first, then logically. Within the first 3–5 minutes in a home, buyers often know if they like it. Lighting, paint color, home condition, and layout heavily influence emotional response. First-time buyers need extra guidance — like “teaching someone to drive for the first time.” 4. Seller Advice Selling isn’t just about market timing — presentation matters. Neutral paint colors and bright white lighting help increase buyer appeal. Every showing is won or lost in the first few minutes. 5. Inspections Matter — and Are Deal Breakers Top inspection walk‑aways: Mold Foundation issues Roof problemsTodd stresses that if a buyer is uncomfortable before closing, “you won’t be comfortable after you close.” 6. Emotion vs. Logic Many buyers get emotionally attached and ignore red flags. Todd’s rule: commissions should never drive decisions. 7. Multi-Generational Living Is Rising Driven by COVID, high child-care costs, rising home prices. Families are choosing: ADUs (Accessory Dwelling Units) “In-law suites” Larger family compounds 8. Real Estate as a Wealth Builder Unlike stock investments, real estate allows you to: Control, improve, alter, and live in the asset. Tax advantages like 1031 exchanges and mortgage deductions compound long-term value. 9. Don’t Buy the Most Expensive House in the Neighborhood Surrounding homes cap your resale value. You may have to wait years for nearby homes to “catch up.” 10. Neighborhood Due Diligence Realtors must avoid discrimination (Fair Housing Act). Buyers should: Visit neighborhoods at night and on weekends Speak with neighbors Review school ratings and county resources Notable Quotes (from the transcript) Career & Purpose “I love helping people. That’s why I became a fireman. Real estate was another way to help people.” “I wasn’t quite sure I wanted to manage long term… my heart was with clients.” Ethics & Commission “Commissions should never be above the people.” “If you’re focused on commissions, you need to pick a different industry.” Emotions in Home Buying “Buyers think they’re looking logically, but they’re looking emotionally first.” “Within the first 3–5 minutes, they already know if they like the home.” Inspections “If you’re not comfortable with the property now, you won’t be comfortable after you close.” Neighborhood Choice “Focus on the house, but look at the neighborhood — you can’t change your neighbors.” Wealth Building “With stocks you can’t control it, improve it, or live in it. With a home, you can.” Success & Determination “Someone told me when I moved to Georgia I wasn’t going to make it. Now I’m the number one salesperson in Georgia.” #SHMS #STRAW #BESTSee omnystudio.com/listener for privacy information.

Anorexia nervosa has one of the highest mortality rates of any psychiatric illness, yet effective biological treatments remain limited. For many people living with the condition, even after successful weight normalization, persistent psychological symptoms, including obsessive thoughts about food, shape, and weight, continue to drive relapse.In this conversation, Dr. Bret Scher sits down with Dr. Guido Frank, Professor of Psychiatry at UC San Diego with over 25 years of experience in eating disorder treatment, to discuss results from the first-ever clinical trial of ketogenic therapy in anorexia nervosa.This 14-week supervised feasibility trial enrolled 22 individuals with weight-normalized anorexia nervosa. Among the 18 study completers:✅ 72% scored in the recovered range on eating disorder assessments, no longer meeting the criteria for an anorexia nervosa diagnosis✅ 100% of study completers saw improvements in depression symptoms, with 72% scoring within the normal range.✅ Participants did not experience significant weight change throughout the studyIn this conversation, Dr. Frank also discusses:What led a self-described skeptic to investigate ketogenic therapy for anorexia nervosaHow the study was structured, who it enrolled, and what the weekly supervision looked likeWhat participants experienced as symptoms improved, including reports of mental clarity and reliefHow weight remained stable throughout the ketogenic interventionThe pushback from colleagues and how to engage with the skepticismWhat comes next, including ongoing brain imaging research and plans for a randomized controlled trialEarly observations in bulimia nervosa and what they may suggest about metabolic factors in eating disordersThis trial demonstrated that ketogenic therapy is well tolerated by this population. Larger, controlled studies are needed to better evaluate efficacy.This intervention was conducted under close supervision by a licensed eating disorder specialist, with weekly check-ins, ketone monitoring, and regular psychiatric assessments. Anyone interested in exploring this approach should do so under close medical supervision and in partnership with their care team. If you or someone you care for is living with anorexia nervosa, please speak with your healthcare provider before making any changes.

In the CYME booth at NAB in Las Vegas, Matthieu Kopp, Chief Technology Officer, previews the next Peakto release, highlighting support for much larger media libraries, expanded collaboration, guest sharing, and secure on-premise access without cloud uploads. He also discusses other features such as new culling tools, improved ingest control, subclips for video workflows, and how AI agents may shape future media asset management.  Show Notes: Chapters: [0:03] Introduction from NAB 2026 [0:43] CYME previews the next Peakto release [0:58] Supporting millions of media assets and larger archives [1:23] Expanded collaboration, access rights, and web interface features [1:53] Guest sharing, downloads, comments, and local Frame.io-style workflows [2:40] Access privileges for studios, reviewers, and outside guests [3:23] Security, peer-to-peer access, and avoiding cloud uploads [4:54] Library size limits, video indexing, and upcoming benchmarks [6:06] Working with multiple libraries and large content collections [8:06] New culling tools for photographers [8:36] Improved ingest control and pausing [9:17] Streamlined interface and differences between photo and video workflows [10:05] Subclips, fast editing needs, and support for Premiere or DaVinci workflows [10:44] Different creative personas and media asset management expectations [11:57] AI agents and future workflow possibilities [12:45] Where to learn more about CYME and Peakto [13:10] Closing from NAB in Las Vegas Support:      Become a MacVoices Patron on Patreon      http://patreon.com/macvoices      Enjoy this episode? Make a one-time donation with PayPal Connect:      Web:      http://macvoices.com      Twitter:      http://www.twitter.com/chuckjoiner      http://www.twitter.com/macvoices      Mastodon:      https://mastodon.cloud/@chuckjoiner      Facebook:      http://www.facebook.com/chuck.joiner      MacVoices Page on Facebook:      http://www.facebook.com/macvoices/      MacVoices Group on Facebook:      http://www.facebook.com/groups/macvoice      LinkedIn:      https://www.linkedin.com/in/chuckjoiner/      Instagram:      https://www.instagram.com/chuckjoiner/ Subscribe:      Audio in iTunes      Video in iTunes      Subscribe manually via iTunes or any podcatcher:      Audio: http://www.macvoices.com/rss/macvoicesrss      Video: http://www.macvoices.com/rss/macvoicesvideorss

In the CYME booth at NAB in Las Vegas, Matthieu Kopp, Chief Technology Officer, previews the next Peakto release, highlighting support for much larger media libraries, expanded collaboration, guest sharing, and secure on-premise access without cloud uploads. He also discusses other features such as new culling tools, improved ingest control, subclips for video workflows, and how AI agents may shape future media asset management.  Show Notes: Chapters: 0:03] Introduction from NAB 2026 [0:43] CYME previews the next Peakto release [0:58] Supporting millions of media assets and larger archives [1:23] Expanded collaboration, access rights, and web interface features [1:53] Guest sharing, downloads, comments, and local Frame.io-style workflows [2:40] Access privileges for studios, reviewers, and outside guests [3:23] Security, peer-to-peer access, and avoiding cloud uploads [4:54] Library size limits, video indexing, and upcoming benchmarks [6:06] Working with multiple libraries and large content collections [8:06] New culling tools for photographers [8:36] Improved ingest control and pausing [9:17] Streamlined interface and differences between photo and video workflows [10:05] Subclips, fast editing needs, and support for Premiere or DaVinci workflows [10:44] Different creative personas and media asset management expectations [11:57] AI agents and future workflow possibilities [12:45] Where to learn more about CYME and Peakto [13:10] Closing from NAB in Las Vegas Support: Become a MacVoices Patron on Patreon      http://patreon.com/macvoices      Enjoy this episode? Make a one-time donation with PayPal Connect: Web:      http://macvoices.com Twitter: http://www.twitter.com/chuckjoiner      http://www.twitter.com/macvoices Mastodon:      https://mastodon.cloud/@chuckjoiner Facebook:      http://www.facebook.com/chuck.joiner MacVoices Page on Facebook:      http://www.facebook.com/macvoices/ MacVoices Group on Facebook:      http://www.facebook.com/groups/macvoice LinkedIn:      https://www.linkedin.com/in/chuckjoiner/ Instagram:      https://www.instagram.com/chuckjoiner/ Subscribe:      Audio in iTunes      Video in iTunes      Subscribe manually via iTunes or any podcatcher: Audio: http://www.macvoices.com/rss/macvoicesrss      Video: http://www.macvoices.com/rss/macvoicesvideorss

Colorado Springs Mayor Yemi Mobolade — the independent who won a culturally conservative city by running as a true centrist who refuses to be boxed into either party — joins the Chuck Toddcast to make the case that quality-of-life governance still beats partisanship when voters are actually given the chance to choose it. Mobolade, who adapted his governing principles from Abraham Lincoln, argues that there's a genuine and growing appetite for leadership that isn't red or blue — but warns that working for unity is incredibly hard and tiring work that few politicians want to do anymore. He walks through Colorado Springs' fight to retain Space Command after Trump and Biden moved the headquarters back and forth between Colorado Springs and Huntsville, Alabama, and explains why he ultimately chose not to sue over the relocation (the decision was within the president's purview, and burning that bridge would have cost the city more than it gained). Mobolade describes hiring his own mayoral opponent Wayne Williams after the campaign — a move he calls part of his "radical collaboration" approach — and argues that mayors don't have the luxury of partisan posturing because their job is fundamentally about producing deliverables for actual residents who want safer streets, better services, and a higher quality of life. The conversation moves into the practical challenges facing every American mayor in 2026, with data centers emerging as the political pain point in nearly every community across the country. Mobolade describes calling an emergency meeting to develop a data center strategy for Colorado Springs, walks through the balanced-but-responsible-growth framework his team has settled on, and explains the tradeoffs honestly: residents are worried about quality-of-life impacts, but the tax revenue from data centers is exactly what cities need to fund essential services. Larger data centers in his city are now forced to pay impact fees to offset their costs, some are being placed on military bases for security purposes, and Mobolade is candid with residents that they cannot have the services they demand without the revenue base to pay for them. The conversation turns to Colorado Springs' housing shortage — the city has been named one of the best places for young people, but only if young people can actually afford to live there — and Mobolade discusses his work with HUD to expand supply, his belief that the country needs genuine innovation in finding cheaper ways to build, and his frustration with a Colorado political landscape that he says no longer has room for center-left and center-right voices the way it used to. His closing argument is the one that ties the whole episode together: the country needs more independent leadership, not because partisanship is bad in theory, but because the current version of it is incapable of delivering the basics that voters actually care about. Link in bio or go to https://getsoul.com & enter code TODDCAST for 30% off your first order. Thank you Wildgrain for sponsoring. Visit http://wildgrain.com/TODDCAST and use the code "TODDCAST" at checkout to receive $30 off your first box PLUS free Croissants for life! Timeline: (Timestamps may vary based on advertisements) 00:00 Mayor Yemi Mobolade joins the Chuck ToddCast 01:30 The people care more about quality of life than partisanship 02:45 Adapted governing principles from Abraham Lincoln 03:45 Colorado Springs is culturally conservative, yet elected an independent 05:30 Ran as a true centrist, hard to box in his politics 06:45 There’s an appetite for leadership that isn’t red or blue 7:30 Trump & Biden moved space command back and forth from Co. Springs 08:45 The city fought hard to keep space command 09:30 Worked with the mayor of Huntsville to ensure smooth transition 10:30 Why did you decide not to sue over relocation of space command? 11:15 The decision was within the president’s purview 12:30 The city is safer now than when he took office 13:45 A mayor’s job is to produce deliverables for the people 15:45 There’s a lack of competition of ideas in Colorado politics 16:45 Have a good relationship with the governor and statehouse 17:30 People get too stuck in their partisan lanes 18:00 Working for unity is incredibly hard and tiring 20:15 There used to be room for center-left and center-right in Colorado 21:15 Hired his mayoral opponent Wayne Williams 21:45 Wayne ran a more traditional campaign, Yemi ran on different leadership 23:00 The goal was radical collaboration and the community embraced it 23:45 Data centers are a political pain point of every local community 24:30 Called an emergency meeting to discuss data center strategy 25:15 The sweet spot of data center policy is balanced but responsible growth 26:00 Residents are worried data centers will lower their quality of life 27:30 Data centers being placed on military bases for security 29:30 Larger data centers are forced to pay a fee to offset impact 33:00 Data centers bring in much needed tax dollars 34:00 The city budget needs the revenue to provide essential services 34:30 Residents want services but no data centers… can’t have it both ways 36:30 Colorado Springs also struggling with a housing shortage 38:30 Working with HUD to try to increase housing supply 39:15 Colorado Springs named one of the best cities for young people 40:45 Need innovation in housing construction, find cheaper ways to build 42:30 The country needs more independent leadershipSee omnystudio.com/listener for privacy information.

Chuck Todd opens with the latest from the Iran war's increasingly costly stalemate, arguing Trump doesn't actually want a deal — he wants the ability to declare an accomplishment without ever looking like he capitulated, the same trick he ran with NAFTA and the JCPOA where he ripped up agreements only to sign nearly identical ones under new names. June, Chuck warns, is when the energy shock will start showing up in domestic prices, every day Hormuz stays closed exponentially increases the damage, consumers may begin behaving irrationally and hoarding, and a single bad natural disaster on top of all this could trigger a genuine crisis. But the heart of the episode is Chuck’s meditation on a single phrase: character is destiny in politics. It's not whether character flaws exist — everyone has them — but when those flaws become public and start affecting the people you were elected to serve. Trump's character problems were on display long before he ever became president, but his defenders now include the exact same Rubios and Grahams who used to blast him as morally unfit. And the most uncomfortable part of Chuck argument for the Democratic base: the same progressives who mocked Trump supporters for excusing his behavior are now using essentially identical defenses for Maine's Graham Platner — who has been accused of sexting in 2023, behavior that isn't youthful indiscretion and isn't going away. Chuck argues political parties used to function as imperfect but real vetting organizations, that once voters become emotionally invested in a candidate they will defend literally anything, that running for office sometimes becomes a substitute for therapy rather than a vehicle for service, and that democracy itself depends on elected officials being able to separate their personal motivations from their public obligations — something Biden failed at when his family obligations led to those preemptive pardons. He notes the Bidens were genuinely beloved before the election but Biden's ambition did real harm to his party, his family, and his own legacy. Todd points to Pope Leo as a potential moral leader Americans seem desperate for at exactly the moment when neither party seems remotely interested in finding the best possible actors. He observes that Platner vs. Collins is starting to feel like a rerun of Trump vs. Clinton in 2016 — two candidates voters genuinely don't want to choose between — and closes with quick hits on Jill Biden's forthcoming memoir, the California gubernatorial primary (where Xavier Becerra and Tom Steyer could finish in the top two), and the increasingly strange Los Angeles mayoral race in which Karen Bass appears to be deliberately ignoring Spencer Pratt because she would much rather face him in a general election than the genuinely formidable Nithya Raman. Then, Colorado Springs Mayor Yemi Mobolade — the independent who won a culturally conservative city by running as a true centrist who refuses to be boxed into either party — joins the Chuck Toddcast to make the case that quality-of-life governance still beats partisanship when voters are actually given the chance to choose it. Mobolade, who adapted his governing principles from Abraham Lincoln, argues that there's a genuine and growing appetite for leadership that isn't red or blue — but warns that working for unity is incredibly hard and tiring work that few politicians want to do anymore. He walks through Colorado Springs' fight to retain Space Command after Trump and Biden moved the headquarters back and forth between Colorado Springs and Huntsville, Alabama, and explains why he ultimately chose not to sue over the relocation (the decision was within the president's purview, and burning that bridge would have cost the city more than it gained). Mobolade describes hiring his own mayoral opponent Wayne Williams after the campaign — a move he calls part of his "radical collaboration" approach — and argues that mayors don't have the luxury of partisan posturing because their job is fundamentally about producing deliverables for actual residents who want safer streets, better services, and a higher quality of life. The conversation moves into the practical challenges facing every American mayor in 2026, with data centers emerging as the political pain point in nearly every community across the country. Mobolade describes calling an emergency meeting to develop a data center strategy for Colorado Springs, walks through the balanced-but-responsible-growth framework his team has settled on, and explains the tradeoffs honestly: residents are worried about quality-of-life impacts, but the tax revenue from data centers is exactly what cities need to fund essential services. Larger data centers in his city are now forced to pay impact fees to offset their costs, some are being placed on military bases for security purposes, and Mobolade is candid with residents that they cannot have the services they demand without the revenue base to pay for them. The conversation turns to Colorado Springs' housing shortage — the city has been named one of the best places for young people, but only if young people can actually afford to live there — and Mobolade discusses his work with HUD to expand supply, his belief that the country needs genuine innovation in finding cheaper ways to build, and his frustration with a Colorado political landscape that he says no longer has room for center-left and center-right voices the way it used to. His closing argument is the one that ties the whole episode together: the country needs more independent leadership, not because partisanship is bad in theory, but because the current version of it is incapable of delivering the basics that voters actually care about. Finally, Chuck hops into the ToddCast Time Machine to revisit two stories that occurred on the same day… the Tiananmen square massacre, and Poland’s first post-soviet elections. He also answers listeners’ questions in the “Ask Chuck” segment. Predict the action all the way through the finals. Sign up now for your twenty-five dollar bonus on https://fanduel.com/predicts Link in bio or go to https://getsoul.com & enter code TODDCAST for 30% off your first order. Thank you Wildgrain for sponsoring. Visit http://wildgrain.com/TODDCAST and use the code "TODDCAST" at checkout to receive $30 off your first box PLUS free Croissants for life! Timeline: (Timestamps may vary based on advertisements) 00:00 Chuck Todd’s introduction 05:30 Iran war/ceasefire has settled into a costly stalemate 06:45 Trump doesn’t want a deal, just ability to declare an accomplishment 07:30 Trump doesn’t want to look like he capitulated 08:00 Trump ripped up other deals, then got same deals with new names 09:15 June will be when the impacts of energy shock show up domestically 10:30 Every day Hormuz remains closed exponentially increases the damage 11:30 Consumers may begin to behave irrationally, start hoarding 12:30 If a natural disaster hits during energy shock, it could be major crisis 13:45 Pulling out of WHO has exacerbated Ebola outbreak 15:00 We can’t foresee all negative impacts, we just know they’re coming 16:15 Character is always destiny in politics, it’s a matter of when people see it 18:00 Everybody has their own motivation for voting, character isn’t always important 18:45 People defending character flaws are a huge part of the problem 20:00 Rubio & Graham used to blast Trump’s character, now defend it 20:30 People criticizing Trump’s behavior are now defending Graham Platner’s 22:00 People run for office for a variety of reasons, and sometimes not good ones 23:15 Sometimes entering politics become a substitute for therapy 24:30 Character matters because it’s predictive 25:30 Trump’s character flaws did not stay private, they became public 26:30 Biden ran for office when his kids were in crisis 27:30 Biden’s family obligations competed with public ones, gave preemptive pardons 28:15 Democracy depends on elected officials separating personal & public 29:15 Political parties used to be vetting organizations, even if imperfect 30:00 Once people become emotionally invested in a candidate, they defend them 30:45 Character flaws don’t just disappear, they show up… and affect us all 33:00 Democrats in a difficult spot having to defend Graham Platner 33:45 Plater accused of sexting in 2023, these aren’t youthful indiscretions 34:45 Eric Swalwell’s indiscretions were ignored until they became too much to ignore 37:15 Platner can still win, Susan Collins has worn out her welcome 38:00 Progressives may have put blinders on for Platner 38:45 People who mocked support for Trump using same defenses for Platner 40:00 At some point credibility will matter to a majority of voters 42:30 Trump’s bad behavior has alienated 1/3rd of Republican voters 44:30 Trump is politicizing celebrating America 250…making it hard to celebrate 45:45 Trump’s character flaws were on display well before he became president 46:30 The Pope may become the moral leader Americans are desperate for 48:30 Parties don’t seem to be worried about finding the best possible actors 49:30 Platner vs. Collins feels like a rerun of Trump vs. Clinton in 2016 51:15 Jill Biden to release new memoir - Bidens seem insulated from public opinion 52:15 Before election, the Biden family was fairly beloved by most 52:45 Biden’s ambition did real harm to the party, family and their legacy 53:30 The Bidens are good people and people were willing to overlook their flaws 54:30 Xavier Becerra & Tom Steyer could finish in Top 2 spots in CA gov primary 56:30 Karen Bass has mostly ignored Spencer Pratt in LA mayoral race 57:00 Bass wants to face Pratt rather than Nithya Raman 1:07:00 Mayor Yemi Mobolade joins the Chuck ToddCast 1:08:30 The people care more about quality of life than partisanship 1:09:45 Adapted governing principles from Abraham Lincoln 1:10:45 Colorado Springs is culturally conservative, yet elected an independent 1:12:30 Ran as a true centrist, hard to box in his politics 1:13:45 There’s an appetite for leadership that isn’t red or blue 1:14:30 Trump & Biden moved space command back and forth from Co. Springs 1:15:45 The city fought hard to keep space command 1:16:30 Worked with the mayor of Huntsville to ensure smooth transition 1:17:30 Why did you decide not to sue over relocation of space command? 1:18:15 The decision was within the president’s purview 1:19:30 The city is safer now than when he took office 1:20:45 A mayor’s job is to produce deliverables for the people 1:22:45 There’s a lack of competition of ideas in Colorado politics 1:23:45 Have a good relationship with the governor and statehouse 1:24:30 People get too stuck in their partisan lanes 1:25:00 Working for unity is incredibly hard and tiring 1:27:15 There used to be room for center-left and center-right in Colorado 1:28:15 Hired his mayoral opponent Wayne Williams 1:28:45 Wayne ran a more traditional campaign, Yemi ran on different leadership 1:30:00 The goal was radical collaboration and the community embraced it 1:30:45 Data centers are a political pain point of every local community 1:31:30 Called an emergency meeting to discuss data center strategy 1:32:15 The sweet spot of data center policy is balanced but responsible growth 1:33:00 Residents are worried data centers will lower their quality of life 1:34:30 Data centers being placed on military bases for security 1:36:30 Larger data centers are forced to pay a fee to offset impact 1:40:00 Data centers bring in much needed tax dollars 1:41:00 The city budget needs the revenue to provide essential services 1:41:30 Residents want services but no data centers… can’t have it both ways 1:43:30 Colorado Springs also struggling with a housing shortage 1:45:30 Working with HUD to try to increase housing supply 1:46:15 Colorado Springs named one of the best cities for young people 1:47:45 Need innovation in housing construction, find cheaper ways to build 1:49:30 The country needs more independent leadership 1:50:30 ToddCast Time Machine - June 4th, 1989 - Tiananmen Square massacre 1:51:00 The image of a man standing in front of a tank is iconic 1:52:00 On the same day, Polish citizens were casting ballots in a post soviet election 1:52:30 One communist system responded with elections, another responded with force 1:53:30 The Chinese students protesting were easy to empathize with 1:54:15 At the time it felt like freedom was advancing and communism was retreating 1:55:15 The elections in Poland humiliated the communist government 1:56:00 Chinese leaders closely watched events in Europe 1:56:45 Protest movement in China was one of the largest in their history 1:58:15 Chinese government cracked down on reformers and protest movement 1:59:00 Martial law was declared and troops moved into Beijing 1:59:45 We don’t have an accounting of the total death toll of protestors 2:00:15 The image we all remember is “tank man” 2:00:45 The incorrect assumption was that China’s middle class would demand rights 2:02:00 China proved that their model could survive and remain durable 2:04:00 Tiananmen ultimately was the birth of the current bipolar world 2:05:00 Poland chose the ballot box, China chose the tank 2:05:30 Ask Chuck 2:05:45 Would you ever consider running for president? Colbert as a running mate? 2:09:00 Do you think Paxton heads into the general overconfident? 2:15:45 Could the “Wyoming Rule” be a more realistic step than expanding house? 2:18:45 Any lesser known founding fathers that deserve more credit? 2:23:45 Thoughts on the Catholic church as a source of moral authority? 2:27:45 Any advice for people needing to step back from news while staying informed?See omnystudio.com/listener for privacy information.

US inflation in April reached its highest level in three years, driven in part by the war in Iran. The volume of oil flows affected by the conflict is three times larger than the disruption caused by the Russian invasion of Ukraine, yet many firms – especially in the US – don't seem too concerned. According to our analysts, they should be. Join us for an enlightening, if not light-hearted, discussion about the impact of this crisis and how it affects the economic future for the US, Europe, and the global economy. Our guests: Jane Foley, Head of Foreign Exchange Strategy, RaboResearch Christian Lawrence, Head of Americas & Energy Market Strategy, RaboResearch Joe DeLaura, Senior Energy Strategist, RaboResearch Relevant time stamps: 2:11 – The US-Israel campaign against Iran and the immediate energy market shock. 6:52 – Why markets could be underestimating the length and impact of the crisis. 14:02 – The macroeconomic, inflationary, and consumer impacts of higher energy prices. 27:04 – Implications of the Iran war for Fed policy and interest rates. 31:21 – How the conflict is shifting our perspectives on globalization and geopolitics. 44:43 – Broader macroeconomic themes: taxes, tariffs, European growth, and the economic growth outlook for the rest of the year. Have a question, qualm, or story to tell? Reach out via email: Bourcard.Nesin@Rabobank.com Sign up to access our written research: RaboResearch sign-up Note: The content and opinions presented within this podcast are not intended as investment advice, and the opinions rendered are those of the individuals and not Rabobank or its affiliates, and should not be considered a solicitation or offer to sell or provide services. Disclaimer: Please refer to our global RaboResearch disclaimer at https://www.rabobank.com/knowledge/disclaimer/011417027/disclaimer for information about the scope and limitations of the material published on the podcast.

Don't miss out on your RACE-approved CE—completely free. Strengthen your veterinary dentistry skills with practical, case-based training you can apply immediately in practice. https://ivdi.org/free --------------------------------------------------------------------------------------- Host: Dr. Brett Beckman, DVM, FAVD, DAVDC, DAAPM --------------------------------------------------------------------------------------- This week's episode answers some of the most common surgical extraction questions submitted during recent veterinary dentistry trainings. Dr. Brett Beckman shares practical guidance for improving extraction technique in general practice, with a focus on flap elevation, bone removal, luxation technique, fractured root tip retrieval, and surgical decision-making during difficult extractions. The conversation centers around real-world challenges veterinarians encounter during canine and maxillary tooth extractions—including managing soft tissue attached during flap creation, how deep to remove bone around roots, preventing root fractures, and approaching difficult maxillary fourth premolar and molar extractions safely and efficiently. --------------------------------------------------------------------------------------- What You'll Learn in This Episode

Chapter Three: Time, Quartz Hills and ResolutionTrash and quartz can exist within the same geography… if we let it.Today, I want to talk about time. Time, to me, is the movement of objects through space. As we witness movement, we call this “time”. A clock does not depict time, it depicts movements of its arms around the clock face. The movement of objects through space.The reason I am talking about time is that our stay at our Reservoir of Power has been clocked by movement of objects and people.But when objects start appearing and disappearing from space, or spaces that were not there before, suddenly are, we can no longer ignore that when we say “yes” to a Gaia and high-frequency human collective request, things are going to step out of time and into the realm of conscious co-creation.OK, the above might sound a bit cryptic, so let me tell you what has been happening, and you can share your own conclusions around it during our Friday Meetup for Driving To The Rez.Our guests as well as our Olympic Peninsula tribe and the co-conspirators in my Birthday Party Celebration, left Colorado and went home. Some went home via long routes to other locations, but eventually they all got there. Suddenly, there was silence in the land, coffee for two instead of twenty, desert birds singing instead of laughter.The silence after everyone left was enormous.For days the land had been full of movement. Music, generators, conversations, shovels, laughter, vehicles arriving and leaving, people cooking, people in discussion, people hugging, people working. And then suddenly there were only the two of us, our three dogs, the wind, and whatever remained behind after the gathering dispersed.Even the Reservoir of Power itself felt different. Larger somehow.It is weeks later now and Larry and I are still at the land, which does not feel exactly like home, but not exactly away from home either.I knew, coming in, that Larry and I would need to stay at least another few working days in Colorado, as I had received clear indications that we had to sort out our legal land claims as well as claiming the space completely away from darkness. And that we needed to remove living structures left behind from last October. I mentally planned to do that after everyone left.In case you are new to this story, the land we own in Colorado is desert land that was completely covered in drug addicts and their shanty town. Gaia requested, no, actually she demanded that we remove all that darkness from this land. After which she revealed that this land was, in fact, a reservoir of power.Larry and I are softies, and when some of those people who had been evicted seven months ago asked for more time for them to be able to remove their prior living quarters, we allowed them to procrastinate for months. Seven months, in fact.While here, and as our guests, who are all highly skilled in expansion of awareness, can testify, the removal of those living structures was important. The structures impinged greatly, despite their small footprint on the vast acreage. An impression beyond the physical.Darkness likes to make you wait because as you wait, they still have an energy line straight into your life. Lightworkers think that waiting for darkness to sort itself out before moving out is compassionate, it is not.Anyway, the few extra days needed to get the land fully into our names have now turned into nearly a month. The path was filled with what Larry calls “monkey mind communication.” In other words, it wasn't a simple “Gaia asks us to remove these things from the land” and we do it. If we had done it, maybe we would be home by now.Every time we prepared to leave before things were settled, another obstacle appeared forcing us to stay.When we ignored the requests, things escalated. One of the people who had left last October decided she was moving back in. When we refused entry, she physically attacked us. It escalated into both criminal and civil court very quickly, but resolution moved much slower. Delays stacked upon delays, keeping us on the land a few more days at a time.Once the pattern became clear, we decided to stop resisting what we were being asked to do and simply do it.Also, if monkey-mind communication is required, we would much rather receive it through a mountain full of quartz crystals than through violent confrontation.Done!Things started moving.Spaces became visible that were otherwise invisible. I woke up one day with the words “Tartaria” in my mind. The Larger Earth. What the heck?? That was my initial reaction, then I became curious. So, Larry and I started exploring mountains and canyons with our eyes wide open.The canyons themselves felt impossible. Massive walls of stone, strange formations, an entire hill glittering in the sunlight as if someone had cracked open the inside of the Earth and left it exposed. A mountain of quartz pieces! The deeper we drove, the stranger the landscape felt. Not dangerous. Not even unfriendly. Just… hidden in plain sight. Radical changes in landscape from desert dry to forests and lakes. The earth would go from deep red to black, to brown, to gold.Lost objects started appearing back on our land, we detected Tartaria technology nearby, chemtrails filled the skies, and we found out that there is something very strange happening in Delta, Colorado.By all appearances, Delta is a small, insignificant city. Barely bigger than a town, really. However, as we started noticing how odd this town was, including what increasingly appeared to us to be a major power reservoir northeast of the city… We also noticed a ton of other strange things, such as billionaires/trillionaires living all around it, the city logo being an Illuminati pyramid, and signs of Tartaria left in the canyons and hills close by.It might, by all appearances, seem that Larry and I stopped moving through time. After all, we still have not started our journey back to Washington.But in truth, it feels as if we are standing in the center of immense movement through space. Space expanding. Revealing a past covered in mud, a present filled with wonder and power, and perhaps a future written by what we are willing to imagine into being.Will next week see us finally begin the journey home?Perhaps.But then again, Bilbo Baggins did return home eventually, and yet he was never entirely the same afterward. Nor was the Shire untouched by what he brought back with him. We don't plan on a ring to rule them all, that's for sure. At most, maybe a truck full of quartz.We will share some of photographs and videos of our strange and wondrous discoveries on the Wisdom Keeper hour of DrivingToTheRez.comThe discussion doesn't stop here - listen to the full podcast episode for unfiltered insights from Inelia and our panelists. This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit dttr.substack.com/subscribe

Ireland has long been recognised as a place where global technology meets local ingenuity. From ambitious start-ups in Dublin and Cork to research-led projects emerging from universities and innovation hubs, the country's technology sector is no longer defined only by multinational investment. Increasingly, it is shaped by entrepreneurs, engineers, scientists and social innovators who want to build tools that solve real problems. The next stage of Ireland's digital journey will not be measured simply by the number of apps launched or platforms scaled. It will be judged by whether technology can become more trustworthy, sustainable and useful in everyday life. Artificial intelligence, cyber security, clean technology, digital health and responsible data governance are now central to that conversation. Artificial intelligence is transforming how businesses operate, how public services are delivered and how people interact with information. Yet the rapid rise of AI has also created urgent questions around transparency, bias, regulation and control. For Ireland, this presents both an opportunity and a responsibility. Irish researchers and founders are well placed to help shape AI systems that are not only powerful, but also accountable. Rather than chasing automation for its own sake, the most valuable AI companies of the coming decade will be those that improve decision-making while keeping humans firmly in the loop. Whether in healthcare diagnostics, legal technology, agriculture, education or financial services, the strongest products will be built on trust. Climate change has made sustainability a business necessity rather than a marketing preference. This is where Ireland's green tech and clean tech communities can play a major role. Smart energy management, circular economy platforms, low-carbon manufacturing, precision agriculture and climate data tools all offer ways to reduce waste while creating commercial value. For small and medium-sized enterprises, sustainability is often a practical challenge. They need affordable tools that help them monitor energy use, manage supply chains, reduce emissions and report progress clearly. Even routine office choices, from cloud infrastructure to printing supplies such as Brother ink cartridges, can become part of a wider conversation about responsible procurement and waste reduction. The companies that succeed will be those that make sustainability easier, measurable and economically sensible. Ireland's technology ecosystem benefits from a rare combination of academic strength, entrepreneurial energy and international connectivity. However, innovation does not happen in isolation. Start-ups need access to funding, mentors, test environments, skilled graduates and early customers. Larger companies need fresh thinking and agility. Public bodies need practical solutions that can scale. Collaboration between these groups will be essential. A medtech founder may need AI expertise from a university lab. A cyber security company may need support from an enterprise agency to reach European markets. A green tech start-up may need pilot partnerships with local councils or established manufacturers. When these connections work well, Ireland can turn good ideas into globally relevant companies. The most exciting future for Irish technology is not purely digital; it is human-centred. The aim should be to create systems that improve health, protect privacy, reduce environmental harm and support better work. That means designing products with accessibility in mind, communicating clearly with users and thinking carefully about unintended consequences. As AI becomes more capable and connected devices become more common, public confidence will matter more than ever. People will not adopt technology simply because it is new. They will adopt it when it is reliable, ethical and genuinely helpful. Ireland's next digital leap will depend on more than technical talent. It will require responsible leaders...

SUPPORT THE SHOW ON PATREON https://www.patreon.com/lionsledbydonkeys SEE US LIVE MAY 29TH IN LONDON: https://www.eventbrite.co.uk/e/lions-led-by-donkeys-podcast-live-in-london-29th-may-tickets-1985443952308 CAN'T MAKE IT? WE'RE STREAMING IT! GET YOUR STREAMING TICKETS: https://www.eventbrite.co.uk/e/livestream-lions-led-by-donkeys-podcast-live-in-london-29th-may-2026-tickets-1985444086710 PRE ORDER JOE'S NEW BOOK! https://www.amazon.com/Highlands-Burn-Foundling-Brigade-Saga-ebook/dp/B0GSG5CNXX/ref=sr_1_1?crid=QWHSPAADI07D&dib=eyJ2IjoiMSJ9.uLEY0I7D6t0IC9GWsF7SH1FKEgKqsqTLmV4PQ_lLi-wVUCYgTqIv0BWd9_-x3VzP.xn7v2CqU5MjngXmmSbYvVGsY_fxkvgsz-LA2tkhHHTs&dib_tag=se&keywords=joseph+kassabian&qid=1774247705&s=digital-text&sprefix=%2Cdigital-text%2C176&sr=1-1 Once upon a time the Russian Empire funded the construction of what might be the world's dumbest tank that is arguably not a tank at all. Larger than any of its peers during WWI, the Tsar Tank goes down in history due to its strange shape, weird wheels, and the fact that developers of the Battlefield video game series thought it was too unrealistic to put it in one of their games. SOURCES: Zaloga, Steven. Grandsen, James. Soviet Tanks and Combat Vehicles of World War Two. Milsom, John. Russian Tanks, 1900-1970 https://interestingengineering.com/innovation/the-tsar-tank-is-possibly-the-strangest-tank-ever-devised https://www.rbth.com/defence/2014/09/29/the_first_russian_tanks_a_long_and_difficult_road_to_the_battlefield_40199.html https://www.thearmorylife.com/tsar-tank-russias-secret-wwi-weapon/ http://www.landships.info/landships/tank_articles/Lebedenko.html

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

5/19/26 (Co-Host - Carrie Baker) Paradise City Arts Festival at the Fair Grounds this weekend—we visit with the show Director, Mariah Swanson—200+ artists and craftspersons, musicians (new, larger stages) and perfect weather for the show. Sci- Tech Café with MHC Prof Kerstin Norstrom & Hampshire Coll Ecology & Global Change Prof Jennifer Van Wyk: bees (gender is a social construct!), No Mow May, and bugs v insects. Also, Hampshire College's commencement and its closing. Comedy Quiz –on bugs and bees—with Happier Valley Comedy's Maddy Benjamin, Scott Braidman, Sally Ekus & special contestant Carrie Baker. Feminist Futures with Smith Coll Prof Carrie Baker. Carrie interviews Marianne Winters, Ex Dir of Safe Passage about the two recent domestic violence homicides in our community—at UMass and in Belchertown.

Elbridge Colby explains that the binding strategy addresses the psychological aspect of war by preparing for the resolve and morale required for a larger conflict. It aims to force China into a dilemma: accept the status quo or take actions that inevitably catalyze the coalition's collective resolve. By integrating the defense of allies like Japan and Australia, the U.S. ensures that a Chinese move against Taiwan precipitates a wider war China would likely lose. This strategy leverages Thumos, or spiritedness, to ensure that Chinese aggression triggers a "don't tread on me" reaction from nationalistic regional powers. (7/8)SEPTEMBER 1932

Ukraine's innovative defense industry has enabled it to resist a larger Russian force. Mary Kissel criticizes weak European leadership and argues that only overwhelming military force will effectively bring Iran back to diplomatic negotiations. (10/16)1930

Grand Rapids gets all the attention, but the best places to live in West Michigan might actually be just outside of it. In this video, Josh May with RE/MAX of Grand Rapids breaks down 4 hidden gem communities within 45 minutes of Grand Rapids that more people should be talking about.*VIDEO CHAPTERS*Introduction (0:00) Rockford, Michigan (1:06) Saugatuck, Michigan (2:22) Greenville, Michigan (3:21) Ada, Michigan (4:24) Big Takeaway (5:25)*Michigan's Hidden Gems: Cool Cities Beyond Grand Rapids*When people start researching a move to West Michigan, Grand Rapids is almost always the starting point. It makes sense. It is the second-largest city in Michigan and has a lot going for it. But what a lot of people discover after digging a little deeper is that some of the most desirable places to live in the entire region are the smaller communities just outside of it.In this video, we highlight four communities that consistently surprise people with how much they offer.*Rockford, Michigan* sits about 15 to 20 minutes north of Grand Rapids and has one of the most authentic small-town feels in all of West Michigan. The entire downtown is built around the Rogue River, making it walkable, connected, and genuinely enjoyable to spend time in. Local restaurants, coffee shops, boutiques, and the Riverwalk trail system make Rockford the kind of place where people actually live in their community. It also has strong schools and a good mix of home styles and price points.*Saugatuck, Michigan* is a completely different experience, and that is exactly the point. Located about 40 minutes west along the Lake Michigan shoreline, Saugatuck is defined by its coastal feel, vibrant art scene, and the kind of lifestyle that makes it feel like a permanent vacation. Oval Beach is one of the best beaches in the state, and the downtown is filled with galleries, shops, and waterfront character. For buyers who put lifestyle above everything else, Saugatuck is worth serious consideration.*Greenville, Michigan* is about 30 minutes northeast of Grand Rapids and has become a go-to for buyers who want more home for their money. Larger lots, more square footage, and lower price points make Greenville attractive to people who are feeling priced out of closer-in communities. Beyond the value story, Greenville has a growing downtown, riverfront parks along the Flat River, and a strong local community that keeps people rooted there long-term.*Ada, Michigan* has transformed significantly over the past several years into one of the most sought-after areas in West Michigan. The village has been redeveloped with intention, featuring a walkable downtown anchored by the Ada Hotel, alongside luxury homes, private wooded settings, and gathering spaces that feel high-end without being cold. Ada sits just minutes from Grand Rapids, making it the ideal option for someone who wants privacy, upscale living, and easy access to the city all at once.Whether you are drawn to Rockford's river town walkability, Saugatuck's lakefront lifestyle, Greenville's space and affordability, or Ada's luxury and community, there is a version of West Michigan built for how you want to live. You do not have to be in Grand Rapids to have an incredible life here.

Host Janet Michael sits down (virtually) with VDOT's Ken Slack for a wide-ranging update on major road improvement projects along Interstate 81 in Virginia's Shenandoah Valley. From bridge replacements to public meetings, Ken breaks down what drivers can expect in the months and years ahead. Topics Covered I-81 Widening at Strasburg Project is approximately 40% complete Key work includes replacing the southbound bridge over Cedar Creek and widening the span over the CSX railway Traffic expected to shift toward the median around August to allow the next phase of bridge work Bridge replacements are done in stages to keep traffic moving Emergency Bridge Repair in Woodstock A dump truck with its bed raised struck a bridge on Route 604 in Woodstock last fall; a tractor trailer collision followed VDOT replaced a steel support beam, requiring a temporary southbound closure Extensive outreach was coordinated across Shenandoah, Frederick, and Warren counties I-81 Bridge at Millwood (Exit 313) — Winchester Existing seven-lane bridge will be replaced with a nine-lane structure New bridge will be built just north of the existing one; traffic will shift when ready Surrounding improvements include turn lanes, auxiliary lanes, and pedestrian accommodations Project involves Routes 50, 17, and 522 — one of the most heavily traveled crossings on I-81 Winchester North Improvements (Mile Markers 317–319) Widening of approximately two miles of I-81 on the north end of Winchester Major reconstruction of Exit 317 (Martinsburg Pike/Route 11) Exit 317 will become a diverging diamond interchange — a new design for this part of Virginia Redbud Road relocation is already underway to make way for the project All work bundled under a single design-build contract Public meeting tentatively scheduled for late June — watch VDOT's website and social media for details How VDOT Selects Contractors Projects go out for competitive bid, typically with a 1–2 month window Complex projects may use a design-build approach, allowing contractors to bring innovation to the design Local/regional contractors often have a "home court advantage" with established resources and relationships Larger projects may attract contractors from outside Virginia Public Meetings & Community Input VDOT holds informal open-house style meetings — no podium, no formal testimony required Display boards, one-on-one conversations with engineers, and court reporters available Online surveys run simultaneously so anyone can participate remotely Public input genuinely shapes design decisions — local knowledge of traffic patterns is valued Oranda Park and Ride (Exit 298, Strasburg) Current gravel lot with ~43 spaces will be expanded to approximately 130 spaces Upgrades include full paving, striping, improved lighting, curbing, and a crosswalk across Oranda Road Construction bid awarded soon; work expected to begin summer 2026 No impact anticipated on Route 11 or I-81 traffic during construction Resources & Links improve81.org — Interactive map, project details, public meeting info, and updates on all I-81 capital improvement projects VDOT website — Search "VDOT projects" for information on all projects in the Staunton District Improve 81 Newsletter — Quarterly updates on I-81 CIP projects (sign up at improve81.org)

The final message (Part 6) in our Easter series called, "A Larger Hope." You can watch the entire service on YouTube: https://youtu.be/MP0Y-5fSSXU If you had questions during the message, text them to 567-246-0807 and we will contact you to discuss your thoughts. *Closing Songs are: 1. "King Of My Heart" - John Mark McMillan - Lyrics: John Mark McMillan, Sarah McMillan - © 2015 Meaux Jeaux Music; Raucous Ruckus Publishing; Sarah McMillan Publishing 2. "How Great Is Our God" - Chris Tomlin - Lyrics: Chris Tomlin, Ed Cash, Jesse Reeves - © 2004 Rising Springs Music; Vamos Publishing; worshiptogether.com songs; Wondrously Made Songs *Songs used in this service are performed by the WCC band with permission under CCS License #4935

Hour 1 - The Vrabel story is unrelenting, it seems like every few days there are new pictures. Are you uninterested in it now or are you obsessed with it? Scheim wants Diggs back and JB and Stephen A Smith are fighting again.

Host Janet Michael sits down with Winchester City Parks Director Chris Konyar at Jim Barnett Park for an update on everything happening in Winchester's parks system — from a brand-new playground to a 250th anniversary drone show. Topics Covered

Dr. James Hollis is a Jungian analyst, trained in Zurich, Switzerland, and based in Washington, D.C. He is the author of twenty-two books, including The Middle Passage, Swamplands of the Soul, The Eden Project, Finding Meaning in the Second Half of Life, Living an Examined Life and his latest book, co-written with L.A.-based artist Enrique Martínez Celaya, Tending the Fire: Creativity, Purpose, and the Unfolding Self. Hollis taught humanities for twenty-six years in various colleges and universities before retraining as a Jungian analyst at the Jung Institute of Zurich. He served for many years as Executive Director of the Jung Educational Center in Houston, Texas and was Executive Director of the Jung Society of Washington until 2019, where he now serves on the Board of Directors. He is a retired Senior Training Analyst for the Inter-Regional Society of Jungian Analysts, was the first Director of Training of the Philadelphia Jung Institute, is Vice-President Emeritus of the Philemon Foundation and serves as Professor of Jungian Studies at Saybrook University. Explore more https://creative.voyage/

Artificial intelligence is evolving faster than ever - and the debate over AI safety, regulation, and control is intensifying. In this episode of Ways to Change the World, Krishnan Guru-Murthy speaks to Jack Clark, co-founder and Head of Policy at Anthropic, the company behind the Claude AI systems. A former journalist turned AI insider, Clark has been at the centre of some of the biggest debates shaping the future of this technology - from safety and regulation to the race between innovation and control.They discuss Clark's journey from reporting on AI to building it, his decision to leave OpenAI over concerns about safety, and the growing fear that powerful systems are outpacing our ability to manage them. From warning governments at the UN to grappling with the risks as a father, Clark reflects on the tension at the heart of his work: what does it mean to build something you believe could be dangerous?

he Rise and Fall of Early Ukrainian Statehood and the HolodomorFollowing the 1917 collapse of empires, two short-lived democratic Ukrainian republics emerged but were crushed by larger powers like Poland and the Soviet Union. Joseph Stalin later solidified control through the Holodomor (1932-1933), a purposeful famine that killed millions of Ukrainians to break their resistance and fund Soviet industrialization. Stalin viewed Ukraine as a vital "breadbasket" and a security buffer against Western invasion. By 1945, though the landscape was devastated and its Jewish population largely annihilated, Moscow achieved its goal of total subordination, creating a myth of unified sacrifice. Guest: Professor Eugene Finkel. (3/8)1856

As the wine world stumbles through difficult times (in early 2026), Karen MacNeil, author of The Wine Bible and co-founder of Come Over October, believes part of the disconnect stems from time. The fastness of the modern, social media fueled world and the slowness of wine. Her solution is to focus the narrative of wine with well-being and wine's long-standing role as a beverage that brings people together. Detailed Show Notes: Karen's background: author of The Wine Bible, writer, speaker, teacherWorried that a change in culture, to a faster one with social media (took off in 2012 when Facebook hit 1B active users and >50% of the population had smart phones), has left wine, a slower product, behindWhite wine's appeal may be partly that it implies fastnessWine is slower to create (can take 3-5 years) and to consume (high acid, tannins for reds)Larger selection of beverages may also be competing for wine's share, including functional beverages that are marketed as “mindful”Wrote an article, “Is wine really in the alcohol business?” on how wine is more than alcohol, but threaded in the culture of food, history, religion, and artBelieves wine should promote the notion of wellbeing vs health, which includes better relationships from sharing wine with peopleStarted Come Over October w/ Gino Colangelo and Kimberly Charles, PR professionals2025: reached 2.9B media impressions, had 1,400 retail store promotions, raised $250kSister campaign is Share and Pair Sundays - to go beyond October, involve food, and help engage more restaurantsAll campaigns need a time, a reason, and a behaviorSeneca Lake Wine Trail doing Share and Pair SundaysTexas Wine Country doing “Come Over October Y'all”Most impactful event was an interview with Pink and sports figures, showing wine connects people across industriesThe wine industry will need to invest to get more people involved, the “Got Milk” campaign spent $23M in the first year Hosted on Acast. See acast.com/privacy for more information.

Raising equity used to be the easy part—today, it's the biggest hurdle. Veteran real estate securities attorney Eugene Trowbridge unpacks the legal landmines, capital challenges, and shifting dynamics in apartment syndication. From SEC rules to struggling deals and cautious investors, this conversation connects the dots on why deals aren't penciling—and what smart operators must do to survive and win in today's market. Key Takeaways: The New Reality of Raising Equity 1) Equity has gone from abundant to scarce almost overnight 2) Many investors are either fully deployed or sitting on the sidelines waiting for clarity 3) Larger deals ($10M+) increasing require multiple GPs and creative capital stacks Legal Structure Matters More Than Ever 1) Understanding Regulation D (506B vs 506C) is critical. 506B: Relationship-based, no advertising, limited sophisticated investors 506C: Allows advertising but requires strict accreditation verification. Market Stress is Exposing Weak Deals: Rising interest rates + bridge debt + depleted reserves = distressed assets. The Hidden Risk in Capital Raising: Not all "capital raisers" are operating legally. Transaction-based compensation without property licensing can trigger SEC enforcement. Final Thought: Today's market is separating professionals from pretenders. Capital is harder, deals are riskier, and the legal framework matters more than ever. The operators who understand both the financial AND regulatory side of the business will be the ones still standing when the market turns. To contact Gene Trowbridge: gene@tnllp.com Ready to unlock the potential of multifamily syndications? Learn how Michael Becker's proven real estate syndication strategies can help you grow wealth and build long-term financial success. Visit SPIADVISORY.COM to start your journey today.