Podcasts about Paradigm

Crypto News: Binance founder CZ says "Bitcoin won't be "dead" for too long. Don't panic, in large friendly letters." A16z crypto, Paradigm lead $175 million bet to move global credit markets onchain. Crypto tax bills a work-in-progress as U.S. House lawmakers pose concerns. Brought to you by

In this episode of Today with Jeff Vines, we continue a series called Inside Out. Pastor Jeff walks us through the story of Moses and his encounter with God through a burning bush, found in Exodus 3.Support the show: https://www.oneandall.church/See omnystudio.com/listener for privacy information.

Have you ever been in a yoga class where the yoga teacher gives a long dharma talk about ahimsa, and then when the movement practice begins the teaching style feels very aggressive? Or maybe you have been that teacher yourself. I know I have! I think there are really subtle and beautiful ways to teach the movement part of yoga in a way that has the deeper philosophical teachings embedded within it, but most of us were not taught to do that, and it is more challenging to do than you might think!  Also, many of us claim that yoga movement can be healing, but a performative style of teaching doesn't allow for that. In this episode, I explore an idea that has become central to my work as a yoga teacher and educator: the disconnect between how yoga is often marketed as a healing practice and how it is frequently taught as a performative one. I dive into the ways traditional teaching frameworks—especially the language of "regressions," "progressions," "safe," "unsafe," "full expression," "modifcation"—can unintentionally reinforce hierarchy, competition, and performance-based thinking. If our goal is to help students feel better in their bodies, develop agency, and cultivate discernment, I believe we need a different approach. Throughout the episode, I share practical tools for teaching movement in a way that aligns more closely with healing-centered values. We explore how to move beyond visual ideals, teach from intended benefit rather than aesthetic outcomes, and help students make informed choices based on their unique experiences rather than universal standards. I also discuss the role of teacher authority, student agency, movement literacy, and why teaching in a more nuanced, non-hierarchical way is both more challenging and ultimately more effective. In this episode, you'll hear: Why yoga cannot simultaneously be a healing practice and a performance-based achievement system The hidden hierarchy embedded in common yoga teaching language Why regressions and progressions are not universal How movement experiences vary from body to body The difference between teaching shapes and teaching movement experiences Student agency, teacher authority, and finding the middle path between control and abdication Why "harder" and "easier" are often misleading descriptors Alternative frameworks for cueing movement, including active vs. passive, symmetrical vs. asymmetrical, and stability vs. mobility How to identify the intended benefit of a pose or movement The importance of sensation-based and function-based cueing Common compensation patterns and how to work with them Why nonlinear movement teaching requires more observation, education, and nuance Helping students develop movement literacy and discernment Practical examples from tabletop, lunges, Warrior III, Extended Side Angle, and more Resources Mentioned:  Episode 165: The Intended Benefit + Removing Linear Hierarchy The Sangha  This episode is sponsored by OfferingTree!   Sign up at www.offeringtree.com/mentor to get 50% off your first three months (or 15% off any annual plan).  With OfferingTree, yoga teachers put their schedule on a personally branded website where students can book classes and even pay or donate online.  All of this can be set up in 10 minutes or less.

When Thoma Bravo took a majority stake in Casepoint in January 2025 and merged it with the government-software company OPEXUS, it set the e-discovery pioneer on a broader course — deeper into the government market and squarely into FOIA and case management. Now the company has a new leader to see that course through: Paul Colangelo, a 25-year veteran of government and enterprise software, who was named Casepoint's CEO this week. In this episode, recorded just before the announcement, Colangelo joins host Bob Ambrogi for his first podcast interview in the role. He talks about the mandate he's been handed 18 months into the Thoma Bravo era, why he believes mission-critical government software is "DOGE-proof, recession-proof, pandemic-proof," and how Casepoint intends to stand apart in a crowded e-discovery field on security and governance.  He also discusses the company's investment in agentic AI and the need to keep a "human in the loop," the customer tension between AI's promise and unpredictable token-based pricing, and why he expects bolt-on acquisitions ahead. Along the way, he reflects on the founders who built Casepoint and the culture he hopes to shape as he takes the helm.   Thank You To Our Sponsors This episode of LawNext is generously made possible by our sponsors. We appreciate their support and hope you will check them out. Paradigm, home to the practice management platforms PracticePanther, Bill4Time, MerusCase and LollyLaw; the e-payments platform Headnote; and the legal accounting software TrustBooks. Briefpoint, eliminating routine discovery response and request drafting tasks so you can focus on drafting what matters (or just make it home for dinner).   If you enjoy listening to LawNext, please leave us a review wherever you listen to podcasts.  

In this episode of Today with Jeff Vines, we start a series called Inside Out. Pastor Jeff walks us through the story of Moses and his encounter with God through a burning bush, found in Exodus 3.Support the show: https://www.oneandall.church/See omnystudio.com/listener for privacy information.

"That's bulls***." That was my honest first reaction, back in 2018, to the work I now build my entire career around.In this episode of the Stuck Not Broken audiobook, I invite you to challenge your paradigm:How I came to Polyvagal Theory, and nearly dismissed itWhat a paradigm is, and why you need a new one before the science can landThe urge most of us feel to skip ahead to the fix, and why there isn't one to skip to

After seven years and nearly 300 episodes, I'm trying something I don't think anyone else is doing: giving you all of my Polyvagal Theory knowledge, directly. And free.Season 2 of the Stuck Not Broken podcast is different from the regular show. It's the full audiobook of my first book, Stuck Not Broken: Book 1 - Trauma & the Polyvagal Paradigm, read chapter by chapter, right here in the feed. No book to buy. No course. Just the whole thing.If you've ever wanted to actually understand your nervous system, what it's doing and why, this is the place to start. By the end of the audiobook, you'll have written a new, simple self-narrative and be ready for the next phase of your unstucking journey. No quick fixes. No hacks. No gimmicks.

Paradigm: a fundamental framework, pattern, or model of thought that shapes how we understand and approach the world or a problem.God wants us to understand that there is purpose in the pain; meaning in the mess.  Instead of asking why is God allowing this to happen,  we can change our paradigm and ask where is God is moving in the situation. 

What are the podcasts? Why doesn't he remember? What is Subsister?   Continue the Conspiracy on Patreon Seek the Truth on Instagram Ask the Questions on BlueSky   Subsister: A Real Podcast created by Alexander Chamberlain

On today's show, we dive into the cost structure of audio speakers. We start with an article that asks whether 'audiophile' speaker brands are milking you for $20,000. We also read your emails and cover the week's news. News: Important update to your DIRECTV account SVS Auto EQ Room Correction for R|Evolution Subwoofers YouTube TV adds Fox One, Peacock to Primetime Channels store Other: Monoprice Alpha In-Wall Speaker There's never been a better time to grab a new Google TV launcher Are 'Audiophile' Speaker Brands Are Milking You for $20,000 The listeners keep delivering great ideas for show topics. This week Mike LaBorde sent in an article published at headphonesty.com entitled A Former FTC Economist Quit His Job to Prove 'Audiophile' Speaker Brands Are Milking You for $20,000.  The author talks about how a former FTC economist quit his job to design and build affordable high-performance speakers.  He argued that many premium audiophile brands are significantly overpriced because they use similar OEM drivers from the same factories while charging massive markups for branding, cabinets, and dealer margins. We'll break down this article into five points we felt were interesting. The full article is linked and you may want to read it for more details. Many premium audiophile speaker brands rely on the same small group of OEM driver manufacturers (like Sinar Baja/SB Acoustics, SEAS (Scandinavian Electro Acoustic Systems), Scan-Speak, etc.). The same factories and engineering talent supply drivers to both high-end and mainstream brands, even when the final speakers carry vastly different logos and price tags. "Custom" or "proprietary" drivers are often overstated. Most brands customize only the "soft parts" (cone, surround, voice coil) on top of standard off-the-shelf "hard parts" from OEM suppliers, rather than designing and building drivers entirely from scratch. Pricing of speakers — The actual cost of the drivers is a tiny fraction of the retail price. In the Wilson Audio Yvette example, the three drivers cost roughly $530–$580 total, representing only about 2% of the $25,000+ selling price. The vast majority of the cost comes from cabinetry, finish, dealer margins (40-50%), distribution, marketing, and brand prestige, with a typical 5x markup from manufacturing cost to retail. Only a few brands truly manufacture their own drivers in-house. Companies like Focal, KEF, Dynaudio, Paradigm, and Bowers & Wilkins are exceptions. Most premium brands outsource driver production due to the high cost and complexity of vertical integration. High performance doesn't require extreme prices. Former FTC economist Dennis Murphy's Philharmonic Audio proves this by offering well-engineered speakers (like the $850/pair Ceramic Mini using quality SB Acoustics drivers) with minimal overhead, direct sales, and no lavish dealer/showroom costs — challenging the idea that great sound must come with five-figure price tags. The article essentially argues that much of the ultra-premium speaker market is driven more by branding and distribution economics than by revolutionary driver technology. What is the Cost Breakdown of Thousand Dollar Speakers? After going through the previous article we wondered what the actual cost breakdown of Passive bookshelf speakers retailing at $1,000 per pair? ThinkKEF Q series, ELAC Debut Reference, or similar mid to high end consumer hi-fi brands. They balance good performance with accessible pricing.  What follows is our best estimation based on the data we uncovered. If you are in the industry and have better data, please let us know and we will update this analysis. Sources for this analysis include - Audio Science Review, AVS Forum, WhatHifi, headphonesty.com, hubhifi, and a few others.  1. Design & Development (R&D) – Upfront Investment Typical cost: $50,000–$250,000+ for a new model line. Includes acoustic modeling, driver selection/tuning, crossover design, enclosure simulation, multiple prototypes, listening tests, and anechoic chamber measurements. For this price tier, brands often use a mix of off-the-shelf and mildly customized drivers rather than fully bespoke high-end ones.   Amortization: Spread over production volume and for this exercise we used a production run of 5,000–20,000 pairs. This adds roughly $5–$25 per pair at a reasonable scale. 2. Prototyping & Tooling Prototypes: 5–15 iterations at $300–$1,200 each which include custom cabinets, driver samples, hand-assembled crossovers. Tooling: CNC molds/jigs for cabinets, baffle cutting, or vinyl wrap tooling: $8,000–$40,000 upfront. Amortized to $2–$10 per pair. 3. Bill of Materials (BOM) – The Biggest Per-Unit Cost For a typical 2-way passive bookshelf (6.5" woofer + 1" tweeter) at this price point: Drivers - $80–$180 - 6.5" coated paper woofer (~$30–$70 ea.), soft dome or aluminum tweeter (~$15–$50 ea.). Brands like SEAS, SB Acoustics, or custom OEM. Cabinet -  $60-$130, - Braced MDF (18–25mm), vinyl wrap or basic veneer, internal damping, port tube, terminals. Real wood veneer adds premium. Crossover - $30-$80 - 2nd/3rd order with air-core inductors, film capacitors, resistors. Higher quality parts (Mundorf-level) push toward the upper end. Other (grille, wiring, hardware, terminals) - $20-$50 - Magnetic grilles, internal wiring, binding posts. Total BOM per pair: $190–$440 at volume production (typically in China or Vietnam for most brands). Premium touches (better drivers, thicker bracing, nicer finishes) push BOM toward the higher end. 4. Manufacturing, Assembly & Overhead Labor & Assembly: $25–$60 per pair (cabinet gluing/bracing, driver mounting, crossover soldering, final wiring, testing). Quality Control & Testing: Burn-in, frequency sweeps, distortion checks: $10–$25. Factory Overhead/Utilities: $35 - $50. Total Manufacturing per pair: $70 - $135 5. Full Cost Structure to Retail ($1,000/pair) We will assume a large brand that sells 20,000 units and has already invested in tooling and requires minimal new tooling for each new speaker design.  Design and R&D Amortized - $5 Prototype and Tooling  - $2 Bill of Materials - $315 - We split the $190 - $440 down the middle Manufacturing -  $103 - We split the $40 - $135 down the middle Shipping, duties etc to distributor per pair on average - $50 Total to Manufacture $474. The rest of the thousand dollars covers the distribution chain, branding, and profit. And in reality, depending on the efficiency of the factory and ability to leverage design histories from years of experience, the soft costs can be about a third of $110 we came up with, bringing the total cost to about $400. Key Variables Affecting Cost Volume: Higher production = lower per-unit costs. Driver Quality: Exotic materials (beryllium tweeters, carbon fiber) can double driver costs. Cabinet Finish: Vinyl vs. real walnut veneer = big difference. Brand Positioning: Established names (KEF, ELAC) have higher R&D/marketing allocation than direct-to-consumer brands. For comparison DIY builders can replicate similar performance for $300–$600 per pair in parts using higher quality drivers and crossover components and flat-pack or self-built cabinets, eliminating most of the overhead and markups. And after building over 30 sets of speakers I can say without doubt that what you build will sound as good as speakers costing ten times the amount. Plus you can use material that works best for you as well as customizing the look to match your decor. Even my latest set built from stock off the shelf components bought from Part Express for about $200 sound simply amazing!  

(Aloka Earth Room) Short Reflection on the Ten Fetters & Guided Meditation | Earthworm Practice for the Anthropocene IV | Online Wednesday-Morning

(Aloka Earth Room) Short Reflection on the Ten Fetters & Guided Meditation | Earthworm Practice for the Anthropocene IV | Online Wednesday-Morning

Neil Araujo, the CEO and cofounder of iManage, was last on this podcast almost exactly two years ago. In the dog years of the legal industry's AI age, that feels like a long time ago. Our conversation then was about law firms still feeling their way around generative AI. But now, as you will hear in this episode, the focus is about what it actually takes to put AI to work at scale — and iManage's answer is that it starts with what Neil calls a knowledge foundation: the content, context and governance layer that makes AI responses not just fluent, but relevant and trustworthy.   Two weeks before we recorded this episode, iManage unveiled the next evolution of its document- and knowledge-management platform, one built around what iManage calls a "context fabric" — an architectural layer the company says transforms an organization's accumulated documents and activity into a "living, governed foundation" for AI agents. It also announced iManage MCP, a standardized, open-protocol connection that enables any AI systems to securely access governed iManage content without custom integrations.     In this conversation with host Bob Ambrogi, Araujo discusses these and other recent developments. He also discusses where he sees the legal industry heading as AI moves from experimentation to operational reality.   Thank You To Our Sponsors This episode of LawNext is generously made possible by our sponsors. We appreciate their support and hope you will check them out.   Paradigm, home to the practice management platforms PracticePanther, Bill4Time, MerusCase and LollyLaw; the e-payments platform Headnote; and the legal accounting software TrustBooks. Briefpoint, eliminating routine discovery response and request drafting tasks so you can focus on drafting what matters (or just make it home for dinner).   If you enjoy listening to LawNext, please leave us a review wherever you listen to podcasts.  

A @Christadelphians Video: [Inspiring] **Ai Summary** – Thought-provoking, insightful, and wonderfully expositional, this outstanding episode of *The Bible Standard* reveals why humility is essential when wrestling with Scripture's most puzzling passages. We, as Christadelphians, explore the strange case of King Saul's age—does the Hebrew really say he was one year old?—and the textual twists behind Lamentations 3: “we are not consumed.” We also dive into the cutting‑edge debate over Greek verbs: do they really tell us *when* something happened, or just *how* the author saw it? This is a wonderfully revealing journey into the “things we still don't know,” reminding us that following God is a process of continual learning, not stagnant certainty.**

Welcome to the June 1, 2026 Monday News Edition of the RV Lifestyle Podcast. I'm Mike Wendland, and this week we have a show that every RV owner needs to hear before they hit the road this summer.We start with a story that I believe goes a long way toward explaining one of the biggest problems facing the RV industry right now: quality control. The National Highway Traffic Safety Administration just released the May 2026 recall report, and it covers nearly 15,000 RVs across more than a dozen separate recalls. And before you assume this is routine housekeeping, let me tell you what is on this list. A Tiffin motorhome with a fuel tank punctured by a screw during manufacturing - NHTSA's own guidance says to park it outside and away from structures until the repair is done. A Jayco motorhome missing the water heater safety valve entirely - not defective, just absent. A Winnebago Solis with a propane hose routed directly over the exhaust heat shield. Grand Design Lineage motorhomes with two separate recalls in the same month - unsecured seats and solar panels that could detach at highway speed. And a long list of brands - including our own Brinkley Model Z - with shock bolts that were never properly tightened at the factory.Here is the part that matters most: manufacturers are not required to notify owners immediately. Some of the letters for these recalls are not going out until July. Two months from now. You should not be waiting. Go to NHTSA.gov, enter your VIN, and find out right now whether your rig is on this list. It takes thirty seconds and it could save your life or someone else's. We cover every brand affected, every defect, and every manufacturer phone number you need.From there we move to our RV Blunder of the Year, and I want to be upfront with you: this one comes with an asterisk. According to Cowboy State Daily, someone driving an RV pulled into the Maverik gas station in Montrose, Colorado, and emptied their black water tank - the toilet waste tank - directly into the station's underground diesel fuel supply. Not the dump station that was right there on the property. The diesel tank. We dig into what is actually confirmed, where the sourcing falls short, why the station's silence is a little suspicious, and why the story is worth telling regardless of whether every detail holds up. The lesson at the end of it applies to every new RVer on the road this summer.Then we get into the April 2026 RV industry shipment numbers, and they are not pretty. Total shipments came in at just over 29,000 units for the month - down more than 17 percent compared to April of last year. Through the first four months of 2026, the industry is running nearly 13 and a half percent behind 2025's pace. Towable RVs - the heart of the market - are down more than 20 percent year over year. We connect those numbers directly to the quality control failures we covered in the first story, because they are connected. Consumer confidence does not survive a steady diet of recall lists like the one we just walked through. That said, there is a genuine bright spot: motorhomes finished April up 13 percent compared to last year, and Park Model RVs jumped nearly 30 percent. We break down what those numbers mean and what to watch for the rest of the summer.We close with a story that felt like a breath of fresh air after everything else this week. Alliance RV - one of the most respected independent manufacturers in the business, known for their Paradigm, Avenue, Valor, and Delta lines - just held their seventh annual owner rally in Goshen, Indiana. Nearly 400 rigs and 800 owners showed up. And when someone from the audience asked founders Coley and Ryan Brady straight out whether they planned to sell the company, the answer was a flat no. Ten-plus years of runway ahead, their words. In an industry where Thor Industries and Winnebago have absorbed so many brands it is nearly impossible to keep track, Alliance is planting a flag and saying they are building something different. We tell you why that matters and what it means for RVers who value buying from a manufacturer that still has skin in the game.

The word "ritual" is archaeology's favorite answer for everything it can't explain. It sounds like knowledge. It fills the museum placard. But it's actually an admission of total ignorance dressed in academic language. What if the things we've filed away as symbolic are actually technologies operating on principles we've abandoned or never discovered? What if the filing system itself is the problem?Call in live during the show: 702-857-6939 Full archive of 1,100+ episodes: troubledminds.org

In this message we talk about Holy Ambition through Romans 15

The new AIEWF website is live! CFPs close in 2 days and we will run our first New Engineer Orientation this weekend, get your tickets booked ASAP as they -will- sell out. Take the AI Engineering Survey and get >$2k in credits and free AIE WF tickets!One of the central tensions in the agents industry is that even while there are major decacorn agent labs like Sierra, Decagon, Notion and Cursor being built up, it is also true that it has never been easier to DIY agents, with a plethora of agent frameworks like LangGraph and Pydantic and Flue, and managed agents from Anthropic and Gemini and Amazon. There has been a wave of companies building their own background agents from Shopify to Stripe to Paradigm to Razorpay, and even Cognition's friends Ramp have built their own coding agent with other friend Modal.You'd think Cognition might feel a bit threatened, but they're not - even after all this, they were way oversubscribed for the $1B Series D they just announced:Walden Yan, coiner of context engineering and Chief Product Officer/Cofounder of Cognition, invited OpenInspect's Cole Murray to talk about why the Devin is in the Details.Full conversation live on the pod today: In retrospect, async agents were the most AGI pilled bet you could make in 2024 - the models weren't good enough yet to vibecode, and people didn't trust AI enough to let it rip, nobody (including early Cognition) was sure about the form factors. Now it is obvious:* The first wave of AI coding tools made the developer faster but remain heavily in the loop. Copilor and Cursor's tab autocomplete are prime examples However, the workflow was still heavily centered around and bottlenecked by the developer's local workflow: a developer in an IDE, watching the model, accepting or rejecting changes, and pushing code one interaction at a time.* The second wave was local agents: Claude Code, Windsurf, Cursor's agents pane: first one and increasingly many terminals all running concurrently.* The current Age of Async Agents points to a different future focused more on agent orchestration which drives end-to-end development.According to previous guest Steve Yegge, there are finer-grained 8 levels to agent adoption, but we have collapsed it into three.As Cursor's Michael Truell put it in The third era of AI software development:Cursor is no longer primarily about writing code. It is about helping developers build the factory that creates their software. This factory is made up of fleets of agents that they interact with as teammates: providing initial direction, equipping them with the tools to work independently, and reviewing their work.The agent should not sit solely inside the developer's flow. It should be setup to work in the background so that you can give it a task, a repo, a machine, a shell, a browser, tests, memory, and review loops to go do the work somewhere else.In less than a year, the sentiment has shifted from avoiding multi-agent systems:to suggesting approaches that actually work:From coining “context engineering” to building the infrastructure behind Devin's 7x PR growth and jump from 16% to 80% of commits across Cognition repos, Walden Yan has had a front-row seat to the background-agent shift. In this episode, Cognition co-founder and CPO Walden Yan joins swyx alongside Cole Murray, creator of OpenInspect, to unpack why everyone is building their own Devin, what changed after the December 2025 model inflection, and why “spec to pull request” is now becoming a real production workflow.We go deep on the architecture of background agents: harness-in-the-box vs out-of-the-box, why Devin separates the “brain” from the machine, why repo setup is still one of the hardest problems, why Docker is not always enough, and how full VMs, snapshots, scoped secrets, GitHub bots, Slack integrations, and video-based testing all fit together. Walden and Cole also dig into memory, MCP limitations, multi-agent orchestration, AI code review, SRE auto-triage, PMs shipping code from Slack, Windsurf 2.0, hybrid frontier/sub-frontier systems, and the real failure mode of uncontrolled vibe coding: your codebase regressing to your worst engineer.And as agents eat software… and software eats the world… you can draw the conclusion on what is next:We discuss:* Why the engineering world is waking up to background agents and cloud agents* The December 2025 model inflection that made spec-to-PR workflows practical* Devin's 7x merged PR growth and rise from 16% to 80% of commits* Why Cole built OpenInspect as an open-source background-agent system* The economics of $20/seat agent products and why monetization is tricky* What Cognition actually sells beyond Devin: infra, onboarding, integrations, and adoption* Harness in the box vs out of the box, and why architecture matters* Why Devin separates the brain from the machine for security and permissions* Repo setup, scoped secrets, Docker Compose, and agent-ready dev environments* Why full VMs matter when agents need to run real applications and test them* Android, macOS, Windows, nested virtualization, and machine-specific agent work* Why testing is much harder than “computer use”* Screenshots, video verification, and the “I know it works” merge moment* GitHub UX, Devin Review, AI reviewers, and agents responding to PR comments* Why MCP alone is not enough for first-class Slack and enterprise integrations* Memory, Knowledge, skills, Claude.md, and why retrieval is still unsolved* Devin's auto-generated memories and the challenge of memory pruning* Always-on agents as permanent PMs for issues, tickets, and product areas* Sub-agents, meta-Devin management, and what multi-agent systems actually add* Why pure auto-merge vibe coding breaks down after about two weeks* AI code smells, lint rules, reward hacking, and Semgrep for agent-written code* GitAI, inline context, and preserving the “why” behind code changes* Local testing, mock servers, older codebases, and preparing companies for agents* Windsurf 2.0 and the handoff between local foreground agents and cloud background agents* SRE auto-triage, support workflows, and agents as first responders* PMs, marketing, and non-engineers creating pull requests from Slack* AI agent budgets, $1k-$5k per engineer spend, and hybrid frontier/sub-frontier systems* The rise of autonomous coding factories and who Cognition is hiringWalden Yan* X: https://x.com/walden_yan* LinkedIn: https://www.linkedin.com/in/waldenyan/Cole Murray* X: https://x.com/_colemurray* LinkedIn: https://www.linkedin.com/in/colemurray/* OpenInspect / Background Agents: https://github.com/ColeMurray/background-agentsTimestamps00:00:00 Introduction00:00:43 Why Everyone Is Building Their Own Devin00:01:57 Devin's 2025 Ramp: 7x PR Growth and 80% of Commits00:03:49 OpenInspect and the Rise of Open-Source Background Agents00:07:59 What Cognition Actually Sells Beyond Devin00:09:56 Background Agent Architecture: Harness In vs Out of the Box00:12:08 Separating the Brain from the Machine00:14:07 Repo Setup, Secrets, Docker, and Full VMs00:19:13 Why Testing Is Harder Than Computer Use00:22:40 Video Verification and the “I Know It Works” Merge Moment00:23:19 GitHub UX, Devin Review, and AI Code Review00:25:42 MCP, Slack, and Enterprise Agent Integrations00:28:59 Memory, Knowledge, and Always-On Agents00:36:16 Sub-Agents, Multi-Agent Orchestration, and Meta-Devin00:43:55 Vibe Coding, Auto-Merge, and Codebase Decay00:48:38 Agent Infra, VPCs, Cloud Providers, and Fast VM Restore00:52:25 AI Code Smells, Reward Hacking, and Code Review Systems00:56:10 Making Codebases Agent-Ready00:58:30 Windsurf 2.0 and the Local-to-Cloud Agent Handoff01:01:15 SRE Auto-Triage, PMs Shipping Code, and Agent Use Cases01:04:32 Agent Budgets, Hybrid Models, and Autonomous Coding Factories01:06:51 Hiring at Cognition and OpenInspect Consulting01:07:45 OutroTranscriptIntroduction: Walden Yan, Cole Murray, and Context EngineeringSwyx [00:00:00]: All right, we're in the studio with Walden Yan, co-founder of Cognition, CPO.Walden [00:00:08]: Happy to be here.Swyx [00:00:09]: Which is a cool title. And coiner of context engineering.Walden [00:00:15]: Although I think there are many people who'd used the terms in various ways beforehand, but I did find that people, both internally and externally, enjoyed the upgrade from prompt engineering or model wrapping into maybe a more thoughtful way to build agents.Swyx [00:00:33]: For those who haven't caught up on that, I have on screen the Don't Build Multi-Agents post, which you should go read on and we might refer to, and Cole Murray, who created OpenInspect.Cole [00:00:43]: Great to be here.Swyx [00:00:43]: So let's talk about it. Everyone is building their own Devins. What's going on?The December Shift: From Handholding Models to Autonomous PRsCole [00:00:51]: So I think the engineering world is waking up to this idea of background agents, cloud agents, whatever you'd like to call it. And I think we saw a shift around the December timeframe of 2025, where the models Opus 4.5 and GPT 5.2, they reached a capability where we moved away from handholding the model and being able to actually more or less autonomously drive the model. And what I mean by that is that we could pretty much go from a specification to a completed pull request, assuming the spec was good enough, with very little friction. And that paradigm alone, I think, changed a lot of how we interact with agents, and opened this world where background agents became more practical.Swyx [00:01:41]: I think for Cole, everyone experienced this in December, but I feel like there was just this increasing ramp, right? There was this moment which was, I think, Sonnet 3.7, where, You guys rewrote Devin in one night or something. So describe 2025 or how it felt from your side.Walden [00:02:01]: In retrospect, we always thought it was ramping up, but then even now, over the last three, four months from today, it's been ramping up even faster. So it's almost funny to be talking about how, big of a leap Sonnet 3.7 was, and honestly, a lot of it was stripping out parts of Devin that were no longer needed with that jump in of intelligence. But I also just think that a lot of the recent leaps, especially, you look at, models like Opus and the latest GPT models, they are reaching levels of autonomy where people are actually finding that they actually can just be hands-off. And people who were once debating, “Oh, do I need to be in the weeds with my model in the IDE? Can I just completely move it off into the cloud?” That's a more serious conversation, and we've seen that in all of our growth charts. Internally there's this funny graph where our usage has, of PRs, our merged PRs, has grown 7X since I forget what it was called.Swyx [00:02:57]: I think Dev, maybe tweeted that. Yes.Walden [00:03:01]: it grew like 7X over, the last, I think it was, two months, three months, something like that. And then you see our engineering headcount growth. It's, gone up by, 10% or something.Swyx [00:03:11]: We were, we were afraid To release this. So this is Devin commit percentages on all Devin repos, was 16% in January and now 80% in March.Walden [00:03:25]: It's a big shift right now. And so it makes sense that a lot of people are now thinking about, buying Devin, but also maybe, trying to build their own and there's Lots of I have a lot of fun building Devin, so I can see why other people would want to build their own cloud agents as well. Matt, well, maybe it's good to hear, what initially inspired you to try to build OpenInspect?OpenInspect: Ramp, Cloud Agents, and Open SourceCole [00:03:49]: OpenInspect came about, through primarily my clients observing how they were using tools like Claude, OpenAI's Codex at the time, and seeing some of the friction that they were having with it. Primarily the Claude was being used through Slack, and a big issue they ran into was that the sessions that were launched were specific to whoever called it via Slack. And so if a PM was the one who invoked the session and they would then go to pass context to engineering can't see the session. And that in itself was a deal breaker because the PM, “Hey, engineering, can you jump in?” But there's nothing to jump in on unless they're copy-pasting out or the single response that came back. And so seeing some of these problems, I had built a similar architecture internally, just to experiment with, test out different ideas as this trend of moving off of localhost was starting to become, And as Ramp released their blog post, I had a lot of the pieces for this already in place, and just thought it would be funny to, see what Claude could do just purely from the blog post. And on my X account, there's actually a thread of where I live tweeted, going through thisCole [00:05:14]: comparing GPT and Claude as both of them are going through it.Swyx [00:05:17]: On the announcement thing or something else?Cole [00:05:19]: right after it got released. We can put it in the show notes. Yeah, it was helpful that I had already knew how to verify the system. I knew what I was looking for. I think Ramp did a great job of really illustrating, the technical aspects of how to build something. It was much more than just like, “Hey, we built a great system.” It was, “And here's how you can build it too.” And so, I resonated a lot with that, just with the problems that I was already seeing, and I thought that, looking around, I didn't really see anything in the open source community that, met this type of system. I think there's a lot that run, in localhost like Superset, Conductor, and many others.But nothing that was actually running in the cloud. And so, I built it, and I thought it was interesting to just open source it and allow anyone to then have a foundation that they can mix and match on top of.The Business of Background Agents: Open Source vs. DevinSwyx [00:06:16]: So literally after Devin was launched was, there was OpenDevin Which became All Hands. I don't know if you tried that orWalden [00:06:22]: I was going to say, one of the things that interested me a lot with OpenInspect was, you didn't try to go make it then something you monetize. There are a lot of, I think, these open source projects would then go and really try to, raise VSwyx [00:06:36]: That's why no OpenDevin. Yeah.Walden [00:06:38]: yeah, and how did you think about that? I thought that was very interesting.Cole [00:06:44]: I thought, and just what I had seen across my clients, was that having a background agent system is going to become a critical infrastructure within their company. And so because of that, I think that I wanted to open source it so that they could fork it and put in whatever customization they wanted. To that question though, I get asked all, “Oh, are you going to raise? Are you going to turn this into a service?”Walden [00:07:08]: I'm sure you've gotten offers.Cole [00:07:09]: but primarily I don't want to do that for a few reasons. One, I think that I don't want to compete for, $20 a seat. I think that is just a really difficult business. I think it's very easy to copy the main pieces of it. Again, I built this fairly quickly. And I think because you are not owning, I guess, the entire stack, it's hard to monetize. You have money being made at the sandbox layer with Daytona, E2b, many other players. You have money being made at the model layer. And you sit in this weird in-between gray area where what are you actually selling? You're selling, I guess, the infrastructure. You're selling, the integrations maybe.Swyx [00:07:55]: let's ask the guy. What are you What are you selling?Walden [00:07:59]: Well, yeah, there's multiple layers to this in practice, and actually it's funny you mentioned the infrastructure, ‘cause when we got started building Devin as well, we had to go figure out how to make the infrastructure as well because,Swyx [00:08:10]: You had to build this two years before everyone else,?Swyx [00:08:15]: Including, the model sideWalden [00:08:17]: It was not, it was not very polished at the start, when we just built it off of raw VMs from cloud providers like EC2, the boot up time was so slow, I think, And especially then, turning off the machines, saving them, and then to be able to bring them back up again when the, when you want Devin to wake up again later. It would just be out cold for like 10 minutes because that's just how long these systems took. They were not built for this repeated down and up usage. And so we actually had to go do all of that. And as a result now, one thing we offer when we go and sell Devin to people is, you don't have to worry about all the compute side of things. We'll make it work. We'll make it work in your cloud if you want it to. But aside from the product, and I want to go into the agents and the tuning of the intelligence part later, but I think a big part of what we do at Cognition as well is to just make sure that your company learns and uses and adopts these coding agents. ‘Cause I think for especially the largest enterprises in the world, you find that there is a lot of people who want to move over to using AI for their day-to-day workloads. But because of the way projects are planned, because, not everyone is literate in using AI in these ways, having a team of engineers who can actually go in and onboard you, set up all the integrations you need, the automations you need to really get to that level of, leverage with AI, is super helpful. And so We do that. We show thought partners to the customers that we work with as well.Swyx [00:09:56]: So let's talk about, architectural stuff. I think that's always, that is something that was the topic of conversation between the two of you. Is this, the mental model that you want to start with or something else? I'll just leave the floor open to you guys.Agent Architecture: Harness in the Box vs. Out of the BoxCole [00:10:11]: I think, maybe we can start here as just a general what are the pieces of a background agent system. And then maybe we can go into some of the nuances of, Decisions that you can make.Swyx [00:10:22]: But I guess I also Like, what, maybe what Walden is saying is the agent is like in this open code box, I guess. Right? This is infra, and then there's, that's the agent. And you had this discussion about whether you put the agent in here or in Out externally. Can you tease that out?Cole [00:10:39]: In a background agent systems, you have a decision to make of where the agent is actually going to run. This is typically described as the harness in the box or out of the box. With running the agent in the box, you're making some trade-offs by doing that. The negative trade-off you're making is primarily security. Because the agent is running in that box, unless you otherwise design it, all of your secrets need to go into that box as well. And given the nature of AI, it can be unpredictable, and you could very easily end up accidentally exfilling your secrets, or other unintended behavior. Now, the out of the box is the idea that we are going to have the actual agent running not directly in the sandbox, and we will have, quote-unquote, the brain of the agent running in some type of worker, control plane. That sandbox then is going to serve as the hands where the brain is basically operating and making tool calls into that environment to manipulate it. I guess other trade-off that you're making between the two systems is that, in my opinion, running it out of the box is much more complex because, you have state that has to be managed, whereas if you're running it in the box, all of the state of that agent is actually in the box, and yes, it's you could persist it elsewhere, but it's all localized and you have less concerns to worry about.Walden [00:12:08]: I think a lot of that, what you mentioned, is why we actually from the start built Devin to what we called separate the brain from the machine. The other thing that this allows you to do is reuse any existing infrastructure you have for dev boxes Perhaps. And so you don't have to worry as much about making a new type of dev box that has all the dependencies the brain needs, as you mentioned, the secrets the brain needs as well. One thing that we've seen some customers run into is, you have a GitHub app and you want Devin, your agent, whatever, be able to interact with GitHub through this application, but then you have different users with different actual permissions. If they are all interacting through the same GitHub app and there's no actual, separation between the system that decides, what it does and the actual secrets on the machine, then you run into an issue where, okay, it's hard to do the separation. But in practice, with Devin, it's much easier because we just say whatever you put on the machine, that is, the scope of basically what the user is free to do, what the agent is free to do. So only put the most scoped secrets on that machine, and then the brain is fully not accessible from the machine. So you don't have to worry about messing with the, any of the most secure parts of the brain if the user is free to do whatever they want with the machine.Swyx [00:13:31]: I was going to just bring, I have this, chart from OpenAI, where I don't know if this is, in the box, out of the box. That is something that they do use to describe it. And then also recently Anthropic did, managed agentsSwyx [00:13:44]: Which is, this is their thing. I don't know. It's all, it's all variations of the same pattern, right?Cole [00:13:49]: So this would be out of the box.Swyx [00:13:51]: Which, is preferable for them because it's less work?Cole [00:13:56]: I would say it's more work.Swyx [00:13:58]: It's more work?Cole [00:13:58]: But it, in my opinion, it is the better architecture of the two. It's just, you're taking on a bit of complexity by doing that.Repo Setup, Docker, and VM-Based Development EnvironmentsWalden [00:14:07]: One thing I've not seen a lot of other players do well is how do you manage what's actually on the box? And this can be complex for many reasons. Let's say you have a big repository that's changing and updating a lot with changing dependencies. How do you make sure that the working environment of the agent actually stays up to date, has all the credentials it needs to, let's say, run the app and test it, and all the things you want your autonomousSwyx [00:14:34]: So a repo setup.Walden [00:14:35]: Exactly. So in, internally At Cognition, we call this repo setup.Cole [00:14:39]: The hardest part ofWalden [00:14:40]: It's been a perennial problem since the start of the company, of how do we help people get this set up? Because not everyone just has, working cloud environments working out of the box. And do you find this to be a common problem withSwyx [00:14:53]: How do you solve it?Walden [00:14:53]: Your clients?Cole [00:14:54]: This is a very common problem, and through my consulting, this is a lot of what I help teams do. A lot of teams don't really have great developer environment setups, if any. A lot of the times it's, “Go talk to Bob and get the secrets,” and that obviously doesn't work when the agent needs to actually set this up. And so a lot of that, most teams are using Docker Compose or some type of microservices. And so for theSwyx [00:15:19]: Even in prod?Cole [00:15:20]: Not in prod. With the OpenInspect, you are using this primarily to interact, and make code changes. There is other use cases, but you can hook, whether through CLI, MCPs, other tools, you can then hook that into your production systems primarily for, SRE type use cases. But you are not, necessarily, trying to test your prod internal microservice through the system.Walden [00:15:48]: And you mentioned Docker Compose. I think one direction we saw some of our friends take early on was, using Docker containers as the level of abstraction for their models. There's lots of reasons, I think, why Docker containers are not great. One thing is, Docker container's not really a true security boundary, for one. But the other is, if you are running real applications, a lot of times those applications use Docker, and then you have to think about Docker in Docker, which is, really weird. And so I think part of, the really hard challenge of getting VMs to work, why did we do that? Well, it was because we realized that you actually needed, full VMs to be able to do these types of things. And especially nowadays where there's actually value in running the application and clicking around and sending you screen recordings of these things. The value just, keeps adding on top of that. But it is a decision I see people run into when they try to build their own systems, is, “Oh, do we, in addition to this, do we put the agent in the machine or out of the machine? Do we use Docker? Do we use something else?” What do you recommend people nowadays?Cole [00:16:57]: I think Docker is a good solution for maybe not running the agent, but running your infrastructure, because that is more or less the same setup your engineers are probably already using. If they're not, then I don't know what they're using. But they're probably already using Docker Compose.Swyx [00:17:14]: I've always had a small candle for web containers. I don't know if you guys have tried them before.Swyx [00:17:19]: To me, they were, supposed to be like Docker Light.Cole [00:17:22]: Is it?Swyx [00:17:22]: I don't know.Cole [00:17:22]: No, I haven't tried it. But yeah, I think any environment that you've set up that is a good experience for your developer naturally lends itself to being easy to set up for the agent. And once you figure out that local developer story, you've more or less solved the agent in a sandbox, environment setup. OpenInspect does have hooks as well, where you can, run a setup SH script that will pre-install everything. You can then pre-snapshot that build so it starts instantly, and then there is a second hook to actually then, restore the state of the sandbox when it comes back. And so you can already have all of those microservices running and basically get the same experience that you would on your machine within the sandbox.Testing Agents: Computer Use, Screenshots, and Real App WorkflowsWalden [00:18:08]: Another thing that we've been thinking a lot about is like Different VM service offerings. Have you had customers where they needed like macOS specific VMs or like Windows specificWalden [00:18:20]: VMs?Walden [00:18:22]: There are like many technologies in the world that only work on specific types of machines, right? If you're building a.NET application that has to run on Windows or like, maybe more commonly if you want to build iOS or macOS Does that workSwyx [00:18:32]: Does Commission supportSwyx [00:18:33]: Choices like that?Walden [00:18:35]: The fundamental architecture we do, because we do the separation, it does support, but the actual work in progress is happening right now on these. Another thing that we've actually recently added support now for, it's in beta, is doing Android development. To do that, we needed to support, I think, nested virtualization within our machines because the VM itself is like a, is a virtualized Firecracker instance, and then you had to then run another Android emulator inside. And there's like weird performance issues that like, it, which is why it's like still in beta. We have to think through these problems, but it unlocks a lot for anyone who wants to do Android development.Swyx [00:19:13]: I was trying to find like a reference video for the testing thing. I couldn't find it, but I think you worked on the testing, capability. Why call it testing and not like computer use or I don't know, it's, what's the general Category of problem?Walden [00:19:26]: I think that when people think about the ability of an AI to run your app and test it, I think they actually over-index on the computer use part of it because computer use in my mind is the literal, okay, you want what button you want to click. Can you emit the right coordinates to go click that button? I think testing is actually a really interesting likeWalden [00:19:48]: Problem-solving, challenge for these AIs because if you wanted to do arbitrary testing, imagine you make a change that spans the frontend and the backend, maybe, even some other like even more deeply nested service. To actually test that change, we have to reason through what-- how do you first run these applications to orchestrate with each other with the right version of the code? Then, okay, how do I trigger the feature or how do I make the thing actually happen? And this can get arbitrarily hard, maybe you have to be an admin. Maybe a certain thing has to be feature flagged on. Maybe, you have to like run two sessions and then send us a very specific word into one of them to trigger a specific behavior. And figuring out how do you do that requires a lot of code base context, requires, a lot of orchestration that we've specifically done. And in some cases, we found that you actually, no one frontier model can actually do this full end-to-end task itself.Walden [00:20:42]: We've seen cases where we actually had to orchestrate different frontier models together to solve this problem together. That is where we spend most of our time when we think about this testing problem, not so much the computer use part. Computer use for what it's worth has gotten a lot better with recent models and it's made that part of the job certainly easier.Swyx [00:20:58]: Especially with like even 4.7, that they released yesterday, apparently like way better in terms of the vision stuff, which is going to be encompassing computer use.Walden [00:21:08]: Having evals for all these as well is something that like takes a while to build up. And having the evals be right is tricky as well. Do you ever see like, clients who are building their own agents have to start standing up evals to make sure things don't regress?Swyx [00:21:25]: Not so much evals in the traditional sense, but specific to the testing part that has just gone in. I just added support for screenshots And in theory you can also do video. I need to put in a plugin to do that. But they do show up natively, and it was a very heavily requested feature, especially after Cursor's recording came out. I think that was very enlightening for everyone of like, “Oh, this is a very good feature to actually have.”, I think with Devin you guys have had this for a while.Swyx [00:21:57]: Oh, yeah. See how screenshots work. Yeah, I don't know if there's anything, super and not obvious. It's like once what feature to build, you can just prompt it and it Will mostly work.Walden [00:22:09]: I think to Walden's point, though, the computer use is a subset of the larger testing problem, and I think that's very specific to the code base that you're working and it's not something that, out of the box that you could just solve it. The-- you do need the code base context to actually know how to test it. And I think in the case of a background agent system, you fortunately do have that code base locally that what is changing and could then inspect it and use that to drive the model.Swyx [00:22:40]: For those who haven't seen it before, this is an example of how it works. You, after the PR is done, you click testing approved, and then it sends you back a video. What I really like is that it labels, It's very small here, but it actually labels what it's testing. And then it-- and then you actually see the cursor and everything. So I don't know, yeah, the engineering in this, just Whatever you want to show. ‘cause this is like, this is one of those like, oh, few of the AGI moments, right? ‘cause Once I look at this, I actually don't I wish I can just merge inside Of Slack instead of going to GitHub ‘cause I don't need to see the code. I know it works.Walden [00:23:19]: Maybe a new feature in Cursor. Yeah, the annotations at the bottom was also a big difference for me when I, when I added those.Swyx [00:23:27]: It's just like, what am I looking at? What are you trying to demonstrate?Walden [00:23:30]: Exactly. There's a surprisingly long tail of small details that ends up making a big difference for this end metric of like how fast do you actually merge the code in. One experience that we spent a lot of time tuning early on was what is the right experience on GitHub for these tools. Because I think, most tools out there when you build the agent, you'll think about, oh, it'll create the PR for you. We try to take that a step further and say, “Oh, what if we actually made sure you could interact Devin, with direct Devin directly on GitHub?” And so we made sure that you can comment on GitHub, and Devin would actually receive those comments and address them back. But there's actually quite a bit of tuning you have to do here because you can imagine that actually like-We recently have Devin Review, for example. Devin Review will post comments on his own PR And then Devin has to then goGitHub Workflows: Devin Review, Comments, and PR AutomationSwyx [00:24:23]: He answers his own comments, which is Really loopy. So like, yeah, I like that it just updates here that it's, that I have commented But usually it's just me saying like, “Hey, merged, fix any merge conflicts.”Walden [00:24:37]: The, so when Devin fixes his own comments, you might be scared that, oh, maybe I'll infinite loop. But we've put a lot of work into making sure it doesn't, both by making sure that the comments are high signal, but also that the agent is thoughtful about what comments it immediately goes and tries to fix, and what comments it's like, “Wait a second, I think you're wrong.” Actually, that's one of my favorite moments is when Devin tells me that I'm wrong, when I try to get it to do something different. But tuning that behavior, actually makes a big difference in terms of how useful the actual GitHub experience is.Cole [00:25:06]: I think to touch on that as well, I think having the AI reviewer integrated into the system is a critical part of this background system. OpenInspect does have that. It has a GitHub code reviewer that you can control the prompt. It does do comments as well. It doesn't do them automatically yet. The capability is there, but it's not fully used.Swyx [00:25:27]: So you have to ask for it?Cole [00:25:28]: you do, yeah. You can tag it on GitHub, and then whatever you named your, GitHub bot, it will then follow up on it. It will then, if you have merge conflicts or whatever you have asked it to resolve, it will then resolve it, but it doesn't do it automatically yet.Integrations: Slack, MCP, and First-Party Agent InterfacesWalden [00:25:42]: Well, I'm curious, what is, the most common thing that people end up requesting, that they still need on top of OpenInspect when you help them go implement it?Cole [00:25:52]: I think a lot of it comes down to actually integrating it into the company. It's one thing to have the background agent system set up, but if it isn't actually integrated into your larger ecosystem, it isn't that useful. It is useful to be able to kick off sessions, but what we really want to be able to do is hook it into all of our other systems, whether that is the production database with read-only credentials, the logs, a Confluence or internal knowledge-based system. I think that is where I see the huge leap for companies, and that can be a challenge for companies as well who are maybe not familiar with exactly how to approach it, especially if they're in environments that have more compliance type things where, access control can be pretty big and how do you deliberately think about these problems, I find to be, one of the problems that comes with a system like this.Walden [00:26:46]: The thing we found is So, MCPs, obviously it has been like this, really big explosion of, oh, you can go, integrate it with all these different things. But to actually get the integration right and the and get the right experience, oftentimes we found that we had to go build our own ad hoc things. I think Slack is a great example of this. You could give your agent a Slack MCP and okay, it can post messages back to you on Slack. But we actually use Devin like a coworker in Slack, and that's how it's been built from the ground up. But to do that, you actually need to, support webhooks that come back, right? And then Devin has to respond in a natural way and then hopefully don't spam your threads too much and annoy the people in your company. So you got to tune that experience just right. Especially when there's a lot of back and forths, we find that we actually have to go beyond the simple MCP integrations in these places.Swyx [00:27:39]: I just pulled up the MCP marketplace. I know this is a Fair amount of work. Is the answer to eventually take first party control of all the top MCPs? Is that theWalden [00:27:48]: I would love a world where you could have something that's more expressive than MCP. That, goes both ways, not just a set of tools, but a proper system that interacts back and lets it Have the right experience with all these interfaces.Swyx [00:28:03]: So there actually is sampling in the MCP spec, but nobody Uses it, right?Walden [00:28:07]: And so I think that's the other part is, actually we found that when the MCP spec starts to get too complicated, it starts to lose its original promise of Being like a simple one-step connect. Now then we have to go figure out how to support all these different variations of things and It starts to look a lot like just building the first party integrations in a lot of these cases now.Cole [00:28:29]: I think it matters, too, how critical it is to your company, right? If this is something that nearly every session is going through, it probably makes sense to own it so that you can make optimizations on top of it Versus just whatever is off the shelf.Swyx [00:28:43]: Awesome. Other than MCPs, what else, sorry, well, I don't know if that's Narrowing in too much on, integrations. But what else? What other elements of building OpenInspect or Devin that you guys really sink on?Memory and Knowledge: What Agents Should RememberCole [00:28:59]: I think, a problem that comes up very frequently is this idea of memories or knowledge base.Swyx [00:29:05]: Oh, boy. How do you solve it?Cole [00:29:08]: so not solved yet, is the short answer.Cole [00:29:11]: it's something, there's a open issue for it, someone asking about it.Swyx [00:29:16]: There's, I, D Wiki hasn't indexed anything about memory yet.Cole [00:29:20]: how I'm seeing it solved across my clients is primarily through skills. I find that skills can be a good gap within that or updating Claude MD, but I think memory as a whole is a pretty unsolved problem, and it is why I've been hesitant to add it. I think there is parts of memory and that can be addressed, but I think as a whole it's a very difficult retrieval problem.Swyx [00:29:44]: Oh my God. RAMP didn't write anything about memory? I see zero search results.Walden [00:29:50]: No. Memory can be quite tricky to get right because it's the retrieval, but also the generation of the memories that can be really tricky. You don't want it to just like Remember very specific details.Swyx [00:29:59]: Walk us through the Devin memory journey because I know there's been a journey.Walden [00:30:03]: the first version of memory that like stuck around for a while was A system we have called Knowledge. And the idea was we wanted it to pick up things over time and not need the user to be proactive about teaching Devin things. So, okay, any time you remind Devin, “Wait, no, that's not quite the way you're supposed to use Git”Like, we actually want Devin to say, “Hey, do you want me to actually just remember this for the future?” And for you to just basically quickly approve or reject and for it to build up over time. ‘Cause I find that, 95%, I think, or some crazy stat like that of the memories that Devin has are all through these auto-generated things. Very few people actually just want to sit down and write big docs on Here's how you're supposed to work with the technology, et cetera. The generation and the retrieval has been something that we've been trying to tune a lot over the years. Generation, you don't want it to remember something like, if you asked one time to like, “Oh, please open as a draft PR,” you don't want to be like, “Oh, everyone forever now should get their PRs as draft PRs.” But you do want some, conveyor. Maybe you want to say like, “Oh, Cole generally likes, things to be created as draft PRs.” Same with retrieval, if you have thousands of these memories, how do you actually make sure they're retrieved at the right time? And that can be quite tricky to do right without exploding the context with a bunch of useful yeah, useless information. Surprising amount of just, eval work to just make sure that, memory is, remains a reliable system as new models come and go.Cole [00:31:31]: Do you have anything that you could share on, memory pruning? And like the temporal aspect of memory?Swyx [00:31:36]: Deleting and forgetting?Walden [00:31:39]: The, today, the, So the things they could do is it could edit memories. And so if your memory used to say like, “Oh, Cole likes to open everything as like a draft PR,” then you can imagine, “No, don't do that.” And then it'll say, “Oh, do you want me to update the memory to be Cole now want everything as, open PRs?” I think that at the same time we don't know if this is going to be the final version of the system. Whatever we have here will probably, translate into the new system that we'll be coming up with. But I think one big difference between two years ago and today is these agents are really good at using anything that resembles a file system natively. And so part of us are, is thinking, “Oh, should we rebuild memories to feel more like a file system that we let the agent navigate on its own?” That's been an interesting exploration. Also similar ideas in the scale space.Swyx [00:32:35]: I am pulling up OpenClaude's memory thing right now. So memory, OpenClaude has like this like daily memory journal thing, right? And you can I mean, that is a file system you can grep through and is a source of truth. I don't know if it's the best. It's probably super noisy, but at least, if you lose something you can discover it or you can apply some, forgetting algorithm to, more ancient memories that don't get recalled again or something. I don't know.Walden [00:33:01]: One thing we've been trying to do to push the boundaries of how you use agents at your company is letting an agent basically have a very similar file, a memory.md or something, and just like be your permanent PM for a specific set of issues maybe. So we have like some Slack channels internally, maybe a Slack channel dedicated to, a specific product like DeepWiki maybe. And you can imagine that, or you want a Devin that never stops, it's just always awake, but it has this like memory dock that it can just maintain for itself about, okay, what are like the number one priorities of what we have to fix and prioritize? Who is responsible for some upcoming work? Maybe they'll even Devin will even tag you on some recurring basis. And so it's been an interesting move to see, okay, how can we actually use Devin for more than just engineering? Can we actually upstream above the engineering process and maybe it's just Devin creating tickets, which then maybe some humans do, but then maybe other Devins do.Swyx [00:34:00]: One of my more fun automations is go research competitors and just suggest stuff to me on a weekly basis. That's the automation. I can't find it right now, but basically it just like, “Look at competitors and suggest things.” “And here are three things that you've suggested that I don't want any more of,” and you just stick that in the prompts. But like I wish actually So for like when I, for example, when I reject a PR, I wish that it updated memory so that I can then just not have to go up, go back and update the scheduled, sync, but anyway, feature request.Walden [00:34:31]: what? We might change it soon. I guess OpenInspect, in the time you've been around, has there been anything you tried to implement but then you had to like undo and like do a different way?OpenInspect Architecture: Webhooks, Control Planes, and Agent StateCole [00:34:41]: Nothing yet, but something that is on my mind. The initial way that I built it was that each of the integrations lives as its own package. And so you have The Slack bot, which is what's handling the webhooks, and then is basically interacting with the control plane. As I'm seeing the system starting to be more integrated, specifically with the GitHub bot integration, I'm considering bringing that all into the central control plane because especially now I want to start, And a request that I'm getting is the ability to monitor, the actual, pull requests being merged, as well as just tracking ofSwyx [00:35:19]: What do I have open?Cole [00:35:21]: What do I have open? How many of these are getting merged? How many comments are showing up? To just understand the health of the system. And so in the case of a GitHub app, you only have one webhook. And so then it's a question of do I put that webhook in that GitHub bot package? That's weird. It doesn't really make sense to live there because that package is more for like the code reviewer. Or do I like centralize it? So that's something that's on my mind of, making that decision. I think the other one we touched on earlier is the harness in the box versus out of the box. I think long term the architecture will eventually come back out of the box. Some of the newer tools that I've added are calling back into the control plane so that you don't have the secrets in the sandbox. And so I think long term I probably will pull the actual, agent out of the box, but I think for now it's fine.Subagents and Multi-Agent Systems: When Parallelism Helps or HurtsSwyx [00:36:16]: Just, a quick question on pulling the agent out of the box. I'm One thing I'm very bullish on this year is agents calling other agents or spawning sub-agents or Whatever you want to call it. Does that make it harder or easier? I can't tell. Because if the harness is in the box, you can just spin up more boxes. If the harness is outside the box, then you're, it's less easy because you are, you have a unicorn pet of a, of a harness that's, living outside the box.Cole [00:36:45]: In theory it would be the same way, right? Whether, one agent has launched many, sub-sessions within it, OpenInspect, for example, can launch sub-sessions and actually create other environments and then monitor them. In the case where it is out of the box, that would basically just be an additional session that's running. And so that session is also running outside of the box. It's running in your worker plane, wherever you're running this. And then you really just have to think about how does your top level agent then interact with it. I do think it can be more complex, just ‘cause again, you have now a more difficult architecture. But I think if you figured it out once, it's probably fine.Swyx [00:37:26]: Well, then I'm just, throwing it open to you in terms of, I call this like meta Devin management. Which is like the, Devin's calling Devins or Devin scheduling Devins or querying trajectories or anything like that. What have you built or unshipped, anything?Cole [00:37:46]: I think one of the surprising things we've seen is that a lot of the ways that, these, separate agents work with each other, and you want them to, parallelize their work, has still mostly followed the same manager sub-agents regime. And a lot of people I think are excited about this world where you have swarms of agents that, talk with each other all over the place. We've actually given Devin an MCP so they can just go arbitrarily message other Devins And create new Devins, et cetera. But I guess, it somehow creates, a really chaotic world in that sense. And so we've still found that most practical use on a day-to-day basis has been one single Devin.Cole [00:38:33]: Figuring out how to segregate the work and get, have other Devins work on it in, a relatively isolated sense, each with their own boxes Not sharing machines, so there's, a very little room for conflict is the regime that you have to create today.Swyx [00:38:50]: I'll call out, the experiments from Cursor, right? This is Wilson Lin's work on Single agent to multi-agent, and you're obviously famously on the side of don't build multi-agent. But they went through the whole thing, only to arrive at, this Which is exactly what Devin has, I think.Cole [00:39:08]: I think there will be a revision to that post at some point AboutSwyx [00:39:12]: Tell us about itCole [00:39:12]: I think multi-agents were very much not at all possible a year ago. You do see more multi-agent experiments today, but you can argue, are they really multi-agents, or are they just just, tool calls,? There are people who, will create sub-agents to go look for XYZ file, XYZ implementation. Has really nice context management benefits because all of the tool calls and tokens that it spends then get collapsed back to just the answer for the main agent. There's a lot of benefits to doing this. We basically have Devin do this with Deep Bookie, make a call out to Deep Bookie, give you back the results, but that feels like a tool call,? It's not like these, two collaborators actually talking back with each, back and forth with each other. But I think the thing that gives me the most bullishness that multi-agents might actually be possible is actually what I said earlier about Devin will actually sometimes tell me I'm wrong and push back, and I think that demonstrates a level of maturity and communication today that makes a multi-agent world possible. One, can two agents who have seen different information come back to each other and actually figure out who is right, what is the correct implementation? They're not just, yes men. Claude, I guess is like, used to just say, what is it? “You're right,” or,Swyx [00:40:25]: “You're absolutely right.”Cole [00:40:26]: “You're absolutely right.” Yeah.Swyx [00:40:28]: The Have you seen, did you seeCole [00:40:29]: The age is overSwyx [00:40:30]: The Codex app troll in Topic? This is the Codex app. Inside of Settings, there's a little, there's a little Easter egg, right? So if you go to, the Themes or Appearance, right? There's all these, color codes, and the top is absolutely, and it's the Topic's colors. Which is such a troll. Anyway.Model Behavior: Pushback, Adversarial Prompts, and Agent SkepticismCole [00:40:53]: I love that Easter egg. Did you discover that yourself?Swyx [00:40:54]: No, it was, someone was, tweeting about it And I was like, I was like, “Is this true?” Because, sometimes people just tweet stuff to, get a rise out of you. But yeah, there you go, in Topic colors.Cole [00:41:06]: Yeah. So yeah, we're out of this regime where, it just says you're absolutely right, and they can have real conversations and real back and forths.Swyx [00:41:13]: You can prompt it as well to be more adversarial or whatever. Yeah. Okay. Yeah, that, I mean, to me, that is more intelligence, right? That is not just something that's, a dumb tool, it's actually pushing back on you I think. Yeah.Cole [00:41:24]: when you mentioned, of course, the blog posts. There was one blog they had where they fed a swarm of agents together and built a browser.Swyx [00:41:34]: That was I think that was the one.Cole [00:41:36]: You can have, likeSwyx [00:41:37]: I think it's the same oneCole [00:41:37]: Creation of it. We found a surprising success of, don't do a swarm or anything, just have one Devin, it does its own context management. Just let it keep running for a while and give it some crazy tasks. I think we asked it to, rebuild, a Windows OS system. And it managed to do it just like, going on for long enough. It'sSwyx [00:41:55]: Was this Andrew's thing?Cole [00:41:58]: there were lots of demos that we ended up not posting, ‘cause at some point we'd just be posting way too much a bunch of, Demos. But I love that because it shows that I think the multi-agent thing still has, a bit of exciting sexiness to it, which is maybe still beyond still, the actual delta it adds to the capabilities of these systems. But it's absolutely the future. I think we're heading in that direction and we can see the progress being made there already.Swyx [00:42:25]: If I were to, make one super minor pushback because I don't feel that confident about it yetCole [00:42:33]: Go for itSwyx [00:42:33]: But I've had Ryan Lopopolo from OpenAI on the pod And he's a super slop cannon, right? Oh my God, that's my coding agent being done. I downloaded this, Peon Ping. I don't know if you guys have heard this. It takes like-, sound packs from popular games like, Command and Conquer and Warcraft, and then it plays it whenever it's done. And so it's like, “Work,” or whatever, “At your command,” or something. Anyway, what I got from the Cursor code base and from Ryan's thing was that there's a slop cannon approach where you try to loosen the single agent's, bottleneck, and I feel like that is, probably an, a very important thing to try to figure out. I don't think anyone's, really solved it. Because then you just have more reviewer slop on top of the agent slop To try to wrangle it all. Ryan will probably very strongly object that I say that he hasn't solved it, but he thinks he's He thinks he's completely solved it. But I think it's still I think it's, very important, ‘cause, that is a bottleneck, right? I feel Devin is slow sometimes Because I'm like, well, yeah, this is very readable and very sensible, but also it is slower than it could be if I just, I want a button to just say, “Just ramp this up 1,000 next parallel, in parallel and just, see what happens,”? And I don't know if that's, feasible at some point in the future.Code Review, Entropy, and AI SlopWalden [00:43:55]: I And we've also run experiments internally where we've basically tried to build entire products, true products that we knew we would eventually ship, but for now, let's try to see if we can do it just by purely, vibe coding on top of each other, auto merge, no code review at all. And then there's this benchmark of how many weeks can you go onto this for Before you say, “We have the trashiest code base.”Walden [00:44:18]: “Let's actually rewrite it from scratch.”Swyx [00:44:19]: Start a new factory, yeah. What'd you find?Walden [00:44:21]: I think we found that the state-of-the-art in December was you can probably, run this for about two weeks. By the end of those two weeks, you'd find that, hey, you want to, change the color of a button. Well, it turns out this button is implemented in, 10 different places, and they, have All these different variations, and oh, you forgot one of them, and actually it's a slightly different color in one spot. And you're like, “Okay, this is too much to work with. Let's actually try to do code review at the same time.” And make sure that we're on top of our software, actually cleaning it up a bit And making sure it's done in a scalable way.Cole [00:44:54]: I think building on that, the idea of, you don't have to look at code, I think is generally a bad idea. And the meme that I have for thatWalden [00:45:03]: What timeline, all right, is Do you think that statement will be true on?Cole [00:45:06]: I think probably for a while it'll be true that you should continue to look at your code. A problem that I see a lot of teams run into that I work with who are embracing AI native, AI first coding, is The meme that I have is that your code base regresses to your worst engineer, because that engineer who is, very gung-ho about AI and is not auditing their code, their pattern starts cementing into the code, and now the AI is referencing their patterns. And so now their if/else block that, is 20 if/elses back and forth, the AI is seeing that as the pattern of how things are done and starts to then exponentially grow this slop. And I find to your point, a pretty good approach to that is having scheduled cleanup, whether by humans or through systems, that are looking for duplication. They then address that. You'll end up with like 12 helpers for how to format a date. And you need to address that, because otherwise it will continue to sprawl.Swyx [00:46:09]: Within balance, I think it's fine to have some duplication, and then sometimes To have garbage collection, right? Yeah. The What I've been, talking about with a lot of engineering leaders is that you want to be very strict about the boundaries between modules, and it's your job as an architect, as a CTO, whatever, to say like, “Okay, here's the hard contract between you guys and you guys. Whatever you do inside this black box is your business. You do whatever. But between these guys, let's be, really damn clear, and any movement must be signed off by a human or me,” or. Then, and like that's that. I don't know if you have any other modifications or advice.Walden [00:46:44]: Well, I guess generally on the topic of, where humans can be useful, I found that ‘cause, some of these, really deep infra problems, sometimes just having a human that just has, really deep expertise can make a big difference. I've actually seen this come into play when actually building agents. So we've had a few friends now, try building their own coding agents, and I think one same problem that I recurringly heard a lot of them run into was this problem of like, “Oh, Grep is really slow on our agents' machines.” And so a lot of them, I assume because they're using AI and they themselves don't have, super deep infra background knowledge, say, “Okay, we're going to go build our own custom Grep index. It's going to be really fast,” and use that as a way around this problem. When we ran into this problem About like, maybe like a year and a half ago when we were, in the early days of building Devin, we obviously didn't have AI then. We just asked our, how to, how to do this. You can just swap out a new Grep index, so.Infrastructure Details: Grep, File Systems, and SandboxesSwyx [00:47:45]: What do you mean you hand-coded Devin? What?Walden [00:47:48]: It's like, can you believe we hand-wrote this code? And we had, our infra people who are really amazing, they were looking into it and they're like, “Oh, what? We realized that actually the root cause of this problem is actually super simple, but like fine-grain detail,” which is that a lot of these virtual machines actually underlying them don't use real file systems. They use these, network file systems where things are actually cached over the network actually in S3. So when you're Grepping, you're actually making network calls Every time you're doing these things, and that's why Grep is extremely slow on these machines. And so again, goes back to, what is all of the crazy infra work that we had to do to actually get these machines working. If you try to do this yourself, there are tons of small details like this, and so we had to eventually go swap out that network file system. ButSwyx [00:48:35]: I think there's a write-up about it, right? Silas did one about the virtual file system.Walden [00:48:38]: Oh, that was a whole other thing. TheSwyx [00:48:39]: Oh, that's a different thingWalden [00:48:40]: The BlockDev file storage formatSwyx [00:48:42]: I'll bring it upWalden [00:48:42]: Which is, a file system format that we built so that the VMs could be spun up and down very quickly. Basically, the intuition behind this is-Imagine you have, a terabyte of disk, and your agent only, wrote, a hundred lines of code on top of that disk. How long does it, say, take to, save and re-bring up that disk? And most systems, because you're not optimizing for this case, it's just, on the order of a terabyte of work because you have to Save all of that and bring it back up. In our system, we try to build a file system that incrementally builds on top of each other. So every time you save and bring the machine back up, you're only doing work that is proportional to effectively the diff in the file system. And so this, shaves off a lot of time in the boot-up process of Devin. I think we This is actually now outdated. We have a newer system inside of Devin. But yeah, there's a lot of tiny details you have to get right here to actually get the day-to-day experience of Devin to be good.Swyx [00:49:39]: It's, not technically agents, but it is agent infra, and when you sell an agent as a company, you sell agent plus agent infra.Walden [00:49:46]: At least the way we do it be And the other The nice thing about having the agent infra being done together is, you We get to deploy Devin in whatever environment we want now. We don't need to wait for some underlying infra provider to also go and support VPC or on-prem or FedGovCloud, for instance. So we can actually go and figure out, okay, since we own the infrastructure, how can we get that set up for you?Cloud Providers: Modal, Daytona, and Enterprise SandboxesSwyx [00:50:12]: Whereas you're Cloudflare dependent.Cole [00:50:15]: so Cloudflare runs the control plane. The sandboxes, Modal is supported. A contributor just added Daytona. E2B is on the roadmap, and I think there's an abstraction in place that if any contributor wants to add a new provider, they can add that in.Walden [00:50:32]: Well, what are, How are the customers you work with Do they generally try to then go set up a contract with another one of these third-party providers? Do they try to do the VMs in-house?Cole [00:50:44]: most of them I see using Modal. I think Modal has a greatWalden [00:50:48]: Shout out Modal.Swyx [00:50:48]: Shout out Modal.Cole [00:50:50]: I think Modal has a great offering. It captures all of the sandbox pieces you need, snapshots being a pretty big piece of that, and given that they also offer GPUs, I think it's a pretty nice offering as a whole.Swyx [00:51:04]: no debate there.Walden [00:51:07]: Modal is great, especially, I think their container offering is, the most natural, and so especially if you are willing to, forego, the full VM requirements Modal is, a really vast place you can spin something up on.Swyx [00:51:20]: Is there a point So Modal's very Python, and I feel like most workload, has really shifted to JavaScript. I don't know if you guys Get the same feeling. So, okay, when I started Landspace and IE and all these things, I was like 50/50 Python and JS, right? That's roughly. I think that's wrong now. I think JS has won. I don't know if you guys Like, I Maybe I'm overstating it, and maybe for cognition, there's, C# and Java and what have you. But for, new greenfield apps, do you feel that Do you get that sense? Does it matter?Cole [00:51:52]: I think that most of the libraries that I see in this space are Python native first, especially in theCole [00:51:58]: Observability space. That said, I think that there is a pretty big appeal of having your entire system in one language. Especially when you have both your frontend and backend communicating, you can have one central type Which is very nice.Swyx [00:52:11]: That's my case against Modal, which is Then you have to run JS. You can run JS inside Modal. It's just, one extra step That, isn't native to the runtime. I don't know ifWalden [00:52:22]: I don't knowSwyx [00:52:23]: Reviews. Do you have numbers? I don't know.Walden [00:52:25]: the one thing I don't like about Python is whenever AI, whenever it writes Python, it always does, the weirdest patterns, andSwyx [00:52:32]: Oh, because it's, mixing two and three or what?Walden [00:52:34]: I think it's something mixing two and three, yeah. The I don't know if you see this. It always tries to do, has attribute on objects as likeCole [00:52:41]: Oh, my God.Walden [00:52:41]: But it's like But that you shouldn't be doing that. It should error if there wasSwyx [00:52:45]: Because it's training on library code?Cole [00:52:47]: I think it's more of, likeCole [00:52:48]: From what I've seen, it's more of, a reward hacking mechanism where it doesn't want to basicallyWalden [00:52:54]: It'll never error.Cole [00:52:54]: It doesn't want the code to fail. And so it Even when it knows it has the attribute, it'll call getattr on a, and for a lot of my clients who have moved towards more autonomous coding, we've put that in as a lint rule That if you do getattr, your pull request is going to fail.Slop Signatures: Comments, Backwards Compatibility, and TypesSwyx [00:53:12]: Ooh, this is a fun topic. Can you tell me more about this? What else is a sign of AI coding that you have to put guards in?Walden [00:53:21]: So we were talking just before this about Opus 4.7. One of the things this new model likes to do is it writes lots of comments. Not like, it'll, comment every line, but it'll write, paragraph, PRDs, on top of every function. But I will say, to its credit, these aren't slop, descriptions like they were before. “Oh, here's what this function does.” It's like, “Oh, here's actually the r

The third episode of SOL SPEAKS (check out Episodes 1 and 2) explores the concept of the Matrix Control System, a theoretical framework where humanity is kept in a state of spiritual stagnation and emotional exhaustion by predatory forces until, individually, we consciously shift this dynamic.

CardioNerds Dr. Joseph Kassab, Dr. Mariana Garcia-Arango, and Dr. Christopher Mason explore the technological revolution of Coronary CT Angiography (CCTA) with expert faculty Dr. Michael Gallagher. The discussion details how CCTA has evolved into a frontline diagnostic and preventive tool, moving beyond simple anatomy to incorporate physiology via CT-FFR and biology through AI-driven plaque quantification. The episode reviews landmark evidence like the SCOT-HEART and PROMISE trials, the nuances of CAD-RADS 2.0 reporting, and the emerging role of AI in monitoring treatment response and personalizing cardiovascular care. Critically, they also discuss some of the assumptions and limitations of these techniques. Stay tuned for a matching review article to be submitted to US Cardiology Review, the official Journal of CardioNerds. This episode was supported by an independent medical education grant from HeartFlow. All CardioNerds education is planned, produced, and reviewed solely by CardioNerds.  Enjoy this Circulation Paths to Discovery article to learn more about the CardioNerds mission and journey. US Cardiology Review is now the official journal of CardioNerds! Submit your manuscripts here. CardioNerds Multimodality Cardiovascular Imaging PageCardioNerds Episode PageCardioNerds AcademyCardionerds Healy Honor Roll Pearls Shift in Paradigm: CCTA is no longer just an anatomic test; with some key limitations, it can provide anatomy, physiology (CT-FFR), and plaque biology (AI-CPA) in a single non-invasive scan. The “Power of Zero” vs. Plaque: While a normal CCTA has a >95% negative predictive value, future MIs often arise from non-obstructive plaque that traditional stress tests might miss. CAD-RADS 2.0 Utility: The addition of plaque burden modifiers (P1–P4) is a “game changer,” allowing clinicians to identify high-risk patients who need aggressive lipid-lowering despite having only mild stenosis. CT-FFR as a Virtual Stress Test: CT-FFR uses computational fluid dynamics to simulate blood flow, potentially reducing unnecessary invasive catheterizations by approximately 61% without sacrificing safety. Seeing the Invisible: AI-based quantitative plaque analysis (QCPA) can identify “subvisual” plaque and low-attenuation (lipid-rich) components that are the primary drivers of acute coronary syndromes. Show Notes How has the role of CCTA changed compared to traditional functional testing? Historically, stress testing answered “is there ischemia today?”, which often reflects late-stage disease. CCTA identifies disease across the entire spectrum, asking “is there atherosclerosis and how much plaque is present?”. Landmark evidence: SCOT-HEART showed a 41% relative risk reduction in MI at 5 years attributed to intensified preventive therapies, and PROMISE showed CCTA was better at selecting patients who truly needed invasive angiography. Diagnostic CCTA imaging depends on the protocol, contrast timing, heart rate, heart rhythm, breathholding, scanner quality, and several patient factors (obesity, prior stents, heavy calcification, complex bypass anatomy, and motion artifact all may limit imaging). “CCTA is exceptional for the right patient, with the right scanner, and the right team.” What are the key modifiers introduced in CAD-RADS 2.0, and why do they matter? CAD-RADS 2.0 moved beyond stenosis severity to include plaque burden (P0 to P4), high-risk plaque (HRP) features, and the presence of ischemia based on CT-FFR. It serves as a clinical decision support tool: a patient with mild (25-49%) stenosis but “extensive” (P4) plaque burden is considered high risk and warrants aggressive risk factor modification. How is CT-FFR calculated, and when is it most useful in clinical practice? CT-FFR uses resting CCTA data and computational fluid dynamics to create a 3D model of coronary flow during simulated maximal hyperemia. It is often used for intermediate lesions (40–90% stenosis) to predict if they are  ischemia-producing, guiding the decision whether to proceed with invasive angiography.  The assumptions necessary for this computational modeling may not apply well to patients with microvascular dysfunction, significant myocardial scar or prior infarction, or ventricular hypertrophy. Still, data indicate that CT-FFR performs similarly to PET in predicting hemodynamically significant lesions.  CT-FFR performs well at the extremes (either clearly normal or clearly abnormal). Accuracy dips, however, in the intermediate range (~0.75-0.80), where decision-making is most critical. In this grey zone, additional factors can help guide the approach, including the amount of myocardium supplied, translesional gradient, and plaque features.   CT-FFR has not been validated in distal segments, stented segments, heavily calcified coronary arteries, or in patients with severe aortic stenosis. Caution with CT-FFR should be utilized in very calcified coronary segments.  What is AI-based quantitative plaque analysis (QCPA), and what metrics are ready for clinical use? This is potentially a paradigm shift, moving away from stenosis-centric thinking to a more disease burden and plaque biology focus. QCPA uses deep learning algorithms to automatically segment the vessel wall and quantify plaque volume in mm³. Ready for “prime time” metrics include: Total Plaque Volume (TPV), non-calcified plaque volume, and Low-Attenuation Plaque (LAP) burden. Can serial CCTA be used to monitor the effectiveness of medical therapies like statins? While not yet a routine guideline-driven practice, trials like PARADIGM and EVAPORATE show that therapies can stabilize plaque; notably, CCTA is better for monitoring than CAC scores, which can be misleading as statins often increase plaque calcification as part of the stabilization process. There are no randomized trials that serial CCTAs improve outcomes. Cost and radiation exposure will be notable limitations. Serial scan timing, scan acquisition and interpretation standardization would be key. Dr. Gallagher notes that we are moving toward a world in which plaque burden may become a “treatment biomarker,” similar to tumor burden in oncology.  References 1. Coronary Computed Tomography Angiography From Clinical Uses to Emerging Technologies: JACC State-of-the-Art Review. Abdelrahman KM, Chen MY, Dey AK, et al. Journal of the American College of Cardiology. 2020;76(10):1226-1243. doi:10.1016/j.jacc.2020.06.076. 2. Non-Invasive Imaging in Coronary Syndromes: Recommendations of the European Association of Cardiovascular Imaging and the American Society of Echocardiography, in Collaboration With the American Society of Nuclear Cardiology, Society of Cardiovascular Computed Tomography, and Society for Cardiovascular Magnetic Resonance. Edvardsen T, Asch FM, Davidson B, et al. Journal of the American Society of Echocardiography : Official Publication of the American Society of Echocardiography. 2022;35(4):329-354. doi:10.1016/j.echo.2021.12.012. 3. 2021 AHA/ACC/ASE/CHEST/SAEM/SCCT/SCMR Guideline for the Evaluation and Diagnosis of Chest Pain: A Report of the American College of Cardiology/American Heart Association Joint Committee on Clinical Practice Guidelines. Gulati M, Levy PD, Mukherjee D, et al. Journal of the American College of Cardiology. 2021;78(22):e187-e285. doi:10.1016/j.jacc.2021.07.053. 4. Contemporary, Non-Invasive Imaging Diagnosis of Chronic Coronary Artery Disease. van der Bijl P, Gulati M, Saraste A, et al. Lancet (London, England). 2025;406(10519):2577-2587. doi:10.1016/S0140-6736(25)01586-7. 5. State of the Art: Evaluation and Medical Management of Nonobstructive Coronary Artery Disease in Patients With Chest Pain: A Scientific Statement From the American Heart Association. Slipczuk L, Blankstein R, Bucciarelli-Ducci C, et al. Circulation. 2025;152(23):e443-e466. doi:10.1161/CIR.0000000000001394. 6. Diagnostic Performance of Fractional Flow Reserve Derived From Coronary CT Angiography: The ACCURATE-CT Study. Li C, Hu Y, Jiang J, et al. JACC. Cardiovascular Interventions. 2024;17(17):1980-1992. doi:10.1016/j.jcin.2024.06.027. 7. Clinical Outcomes Based on Coronary Computed Tomography-Derived Fractional Flow Reserve and Plaque Characterization. Sato Y, Motoyama S, Miyajima K, et al. JACC. Cardiovascular Imaging. 2024;17(3):284-297. doi:10.1016/j.jcmg.2023.07.013. 8. Clinical Use of Coronary Computed Tomography Angiography-Derived Fractional Flow Reserve: Expert Consensus by an International Working Group. Tang CX, Leipsic JA, Nørgaard BL, et al. European Radiology. 2026;:10.1007/s00330-025-12313-6. doi:10.1007/s00330-025-12313-6. 9. Diagnostic accuracy of computed tomography–derived fractional flow reserve: a systematic review. Cook CM, Petraco R, Shun-Shin MJ, et al. JAMA Cardiol. 2017;2(7):803-810. Doi:10.1001/jamacardio.2017.1314 10. Diagnostic performance of noninvasive fractional flow reserve derived from coronary computed tomography angiography in suspected coronary artery disease: the NXT trial (Analysis of Coronary Blood Flow Using CT Angiography: Next Steps). Nørgaard BL, Leipsic J, Gaur S, et al. J Am Coll Cardiol. 2014;63(12):1145-1155. Doi:10.1016/j.jacc.2013.11.043 11. Comparison of coronary computed tomography angiography, fractional flow reserve, and perfusion imaging for ischemia diagnosis. Driessen RS, Danad I, Stuijfzand WJ, et al. J Am Coll Cardiol. 2019;73(2):161-173. Doi:10.1016/j.jacc.2018.10.056. 12. 1-year outcomes of FFRCT-guided care in patients with suspected coronary disease: the PLATFORM study. Douglas PS, De Bruyne B, Pontone G, et al. J Am Coll Cardiol. 2016;68(5):435-445. Doi:10.1016/j.jacc.2016.05.057. 13. Comparison of an initial risk-based testing strategy vs usual testing in stable symptomatic patients with suspected coronary artery disease: the PRECISE randomized clinical trial. Douglas PS, Nanna MG, Kelsey MD, et al; PRECISE Investigators. JAMA Cardiol. 2023;8(10):904-914. Doi:10.1001/jamacardio.2023.2595. 14. Diagnostic and clinical value of FFRCT in stable chest pain patients with extensive coronary calcification: the FACC study. Mickley H, Veien KT, Gerke O, et al. JACC Cardiovasc Imaging. 2022;15(6):1046-1058. doi:10.1016/j.jcmg.2021.12.010. 15. Low-Attenuation Noncalcified Plaque on Coronary Computed Tomography Angiography Predicts Myocardial Infarction: Results From the Multicenter SCOT-HEART Trial (Scottish Computed Tomography of the HEART). Williams MC, Kwiecinski J, Doris M, et al. Circulation. 2020;141(18):1452-1462. doi:10.1161/CIRCULATIONAHA.119.044720. 16. AI-Guided Quantitative Plaque Staging Predicts Long-Term Cardiovascular Outcomes in Patients at Risk for Atherosclerotic CVD. Nurmohamed NS, Bom MJ, Jukema RA, et al. JACC. Cardiovascular Imaging. 2024;17(3):269-280. doi:10.1016/j.jcmg.2023.05.020. 17. Interaction of AI-Enabled Quantitative Coronary Plaque Volumes on Coronary CT Angiography, FFRCT, and Clinical Outcomes: A Retrospective Analysis of the ADVANCE Registry. Dundas J, Leipsic J, Fairbairn T, et al. Circulation. Cardiovascular Imaging. 2024;17(3):e016143. doi:10.1161/CIRCIMAGING.123.016143. 18. Prognostic Value of AI-Based Quantitative Coronary CTA vs Human Reader-Based Visual Assessment: Results From the CONFIRM2 Registry. van Rosendael A, Nakanishi R, Bax JJ, et al. JACC. Cardiovascular Imaging. 2026;19(3):345-359. doi:10.1016/j.jcmg.2025.09.021.13. Pericoronary Adipose Tissue as a Marker of Cardiovascular Risk: JACC Review Topic of the Week. Tan N, Dey D, Marwick TH, Nerlekar N. Journal of the American College of Cardiology. 2023;81(9):913-923. doi:10.1016/j.jacc.2022.12.021. 19. Effect of Icosapent Ethyl on Progression of Coronary Atherosclerosis in Patients With Elevated Triglycerides on Statin Therapy: Final Results of the EVAPORATE Trial. Budoff MJ, Bhatt DL, Kinninger A, et al. European Heart Journal. 2020;41(40):3925-3932. doi:10.1093/eurheartj/ehaa652. 20. Coronary CT Angiography Evaluation With Artificial Intelligence for Individualized Medical Treatment of Atherosclerosis: A Consensus Statement From the QCI Study Group. Schulze K, Stantien AM, Williams MC, et al. Nature Reviews. Cardiology. 2026;23(2):100-115. doi:10.1038/s41569-025-01191-6.

This week on our Cartoon 1st for the month we're checking out the totally Jawesome and out of control Street Sharks! "When the evil Dr. Paradigm starts messing around with gene-slamming he's able to transforms 4 unassuming brothers into human shark hybrids. These Street Sharks will need to find time between eating to stop Paradigm from doing even more damage." It's energetic, engaging, off the hook, unexplainable, it's wild! We hope you enjoy this review of Street Sharks! If you'd like to unlock bonus episodes from Talking Back every month, then check out our page on Patreon! Check out Tim's Youtube Channel Demo Dash! You can also support Talking Back by sending us a Coffee at Buy Us a Coffee!  Please consider leaving a 5 star rating and review on Apple Podcasts! This helps make our Podcast easier for listeners to find.  Feel free to drop us a line on Social Media at Instagram, and Facebook. Or drop us an email us at talkbackpod@gmail.com. This podcast is part of the BFOP Network 

Panama Canal follow-up: Bret Weinstein and Michael Yon return to the subject two years later after major developments. Michael appears this time with his wife and partner, Masako Ganaha sharing their unique paradigm for understanding global patterns, historical lessons, and future predictions.Find Masako Ganaha at https://note.com/masakoganaha and on X at https://x.com/ganaha_masakoFind Michael Yon on Substack at https://michaelyon.substack.com and on X at https://x.com/Michael_Yon*****Sponsors:Dose: Ready to give your liver the support it deserves? Head to http://dosedaily.co/DARKHORSE or enter DARKHORSE to get 35% off your first subscription.Puori: Amazingly clean and safe supplements and protein powders, lab tested and guaranteed. Go to http://Puori.com/DarkHorse for 32% off grass-fed whey protein with a subscription. DarkHorse code works on all products!Vanman: Go to https://vanman.shop/darkhorse26 and use code DARKHORSE26 for 15%  off your first order.*****Join DarkHorse on Locals! Get access to our Discord server, exclusive live streams, live chats for all streams, and early access to many podcasts: https://darkhorse.locals.comCheck out the DHP store! Epic tabby, digital book burning, saddle up the dire wolves, and more: https://www.darkhorsestore.orgTheme Music: Thank you to Martin Molin of Wintergatan for providing us the rights to use their excellent music.*****Mentioned in this episode:Michael Yon Panama Canal on DarkHorse https://darkhorse.locals.com/post/5179074/bret-weinstein-with-michael-yon-in-the-panama-canalCatherine Austin Fitz on Michael Yon Substack https://michaelyon.substack.com/p/amazing-talk-masako-and-catherineTrojan Migration? The 210th Evolutionary Lens with Bret Weinstein and Heather Heying https://www.youtube.com/watch?v=bwmwxo3iMAs Zionist Forces may close Strait of Hormuz https://michaelyon.substack.com/p/zionist-forces-may-close-strait-of Dutch Farmers Canaries in the Globalist Coal Mine  Michael Yon  Eva Vlaardingerbroek https://www.youtube.com/watch?v=pqHQN54XCL0 Screwworms over Texas https://michaelyon.substack.com/p/screwworms-over-texasSupport the show

Silly title, but very important principle. Listen to Matthew as he reaches back into the Isaiah Scroll to teach us something VERY important about Jesus, and who we are as his followers.

Silly title, but very important principle. Listen to Matthew as he reaches back into the Isaiah Scroll to teach us something VERY important about Jesus, and who we are as his followers.

This week on the SoundStage! Network Audiophile Podcast, host Jorden Guth is joined by Blake Alty, product manager for Paradigm and Anthem, along with John Bagby, managing director at PML Sound—the parent company behind Paradigm, Anthem, MartinLogan, and GoldenEar. Together, they discuss how brands maintain distinct identities under one corporate roof, how manufacturing scale affects modern hi-fi, the industry's generational divide, the partnership with WiiM, and whether high-end audio risks losing touch with ordinary music lovers as million-dollar systems increasingly dominate the conversation. Sources: “Paradigm Shift—The Bagbys Are Back!”: https://www.soundstagehifi.com/index.php/opinion/1350-paradigm-shift-the-bagbys-are-back “A Fantastic Gateway: A Q&A with Paradigm's Zoltan Balla and Blake Alty on the New Monitor SE 8000F Loudspeaker”: https://www.soundstageaccess.com/index.php/feature-articles/1186-a-fantastic-gateway-a-qa-with-paradigms-zoltan-balla-and-blake-alty-on-the-new-monitor-se-8000f-loudspeaker Chapters: 00:00:00 Announcement 00:00:36 Introductions 00:07:21 Maintaining separate brand identities 00:11:30 Economies of scale 00:13:54 Defining value in an uncertain economy  00:17:11 The future of million-dollar hi-fi 00:20:39 The myth that kids don't care about good sound 00:24:03 Headphones 00:25:55 The next generation 00:29:16 Wonder Twin Powers, Activate! 00:33:04 Education matters 00:34:52 Ten years down the road? 00:40:43 Outro music: "Crystal Ball” by Adv3n7ur35

Joe Fried has a theory about why verdict values stay low in conservative states. “If there are cases where somebody's asking for $30, $50 million, and they're not getting it, I may need to listen to that. But if nobody is asking for that – if they're asking for $5 million in a wrongful death case – then of course they're not getting $30.” The celebrated trucking litigator returns to TLU to share lessons from two recent cases: a $2.3–$2.4 million verdict and a near-$100 million settlement. Tune in to this conversation with host Dan Ambrose for a masterclass in finding hidden trucking coverage, mediating at the start negotiation, and managing fear – but not getting rid of it entirely. After all, your client hired you to be their voice. “I hope you feel the weight of it.”Train and Connect with the Titans☑️ Joe Fried | LinkedIn☑️ Fried Goldberg | Facebook | Instagram | LinkedIn | X | YouTube☑️ Trial Lawyers University☑️ TLU On Demand Instant access to live lectures, case analysis, and skills training videos☑️ TLU on X | Facebook | Instagram | LinkedIn☑️ Subscribe Apple Podcasts | Spotify | YouTube2026 Programming☑️ TLU Beach, June 3-6, Huntington Beach, CAEpisode SnapshotJoe describes a back-to-back trial calendar year in which cases repeatedly resolved days — or even the morning — before trial.In Newport News, Joe represented the family of a teenager who was killed when the car he was riding in struck the rear corner of an illegally parked tractor-trailer.The jury returned a verdict of $2.3–2.4 million — beating the defense's pre-trial offers by roughly a million dollars.In a different case, Joe represented a 10-month-old girl who was left an incomplete quadriplegic after a truck rear-ended her 16-year-old mother's car. The life care plan was approximately $30 million – and the case settled for just under $100 million.At the upcoming TLU Beach, Joe will present on these topics: applying trucking methodologies to non-nine-figure trucking cases (Thursday); understanding his updated “speed trial” approach (Friday), and then back-to-back sessions on connecting with witnesses and covering trucking cases from the basics through advanced strategies (Saturday).Produced and Powered by LawPods

这是备受瞩目却又非常低调的支付公链Tempo首次接受中文媒体采访，披露自己推动稳定币大规模采用、帮助成熟企业上链的业务规划、战略重点和行动手册。 我们在刚刚结束的Stripe Sessions大会的现场，和Dan Romero聊了聊，听听这位明星去中心化社交网络Farcaster的创始人「叛逃」到大企业支付公链Tempo的心路历程，更重要的是，Stripe等支付巨头入场、稳定币和企业级支付应用正在迎来真正的大规模采的时刻，听他讲讲Tempo如何用极度务实主义将互联网和金融企业带上链。 我们还讨论了Tempo面临的各种质疑，包括这条企业公链去中心化的进程、是否与以太坊竞争；当然，还有Tempo和Stripe主导的MPP协议（机器支付协议）与X402的竞争。 这是我们关于Stripe Sessions大会系列报道的一部分。之后的节目，我们会继续详细讲讲在Stripe Sessions大会上看到的情况，探讨Agent经济和智能体支付的发展趋势。 【主播】 刘锋，BODL Ventures合伙人，前链闻总编辑 【嘉宾】 Dan Romero，支付公链Tempo GTM负责人，Farcaster联合创始人 【你将听到】 00:46 离开Farcaster加入Tempo，曾被视为一个理想主义时代的结束 02:38 含着金钥匙出生的Tempo 08:26 「在加密干了12年，让人感觉挺老的，但我发现稳定币的机会非常惊人」 10:10 「加密世界正在发生变化，现在有稳定币和Crypto两种东西」 11:23 平台型marketplace和跨境支付是两个清晰的稳定币使用案例 13:23 支付的下一个大趋势是微支付主导的智能体支付 15:07 传统企业希望提供链上的DeFi收益产品给自己的用户 17:27 Tempo和以太坊之间并不是正面竞争 18:19 「如果Tempo能够吸引100万个企业和10亿个消费者，对加密货币和以太坊都不是坏事」 20:18 希望用两年时间实现Tempo的去中心化 22:03 机器支付协议（MPP）vs. X402：智能体不关心两者的差异 24:12 让Agent满意，关键在于无需人类介入 【后期】 AMEI 【运营】 朱婕 【BGM】 Mumbai - Ooyy 【在这里找到我们】 收听渠道：苹果｜小宇宙 海外用户：Apple Podcast｜Spotify｜Google Podcast｜Amazon Music 联系我们：podcast@sv101.netSpecial Guest: Dan Romero.

And the owner wants you to “steal” his template. This week, rapid custom manufacturer SendCutSend reached a valuation of $1.01 billion after a $110 million investment from Sequoia, Paradigm, and Patrick and John Collison—the guys who co-founded Stripe.The Reno, Nevada-based company is using the funds to launch a five-year plan to strengthen its American industrial base, which includes a $1 billion commitment to creating new U.S. manufacturing jobs and to domestically produced materials.The company also earmarked more than $250 million to expand existing facilities and establish new manufacturing hubs throughout the country. By merging software-first logic with high-speed domestic production, SendCutSend provides laser cutting, CNC machining, and finishing services with instant-buy access. The company wants to be America's "anything factory," delivering parts in as little as 24 hours.SendCutSend has spent the last eight years working on developing a model that allows users to get an instant quote and quickly begin production.The company said it has been largely bootstrapped until now, primarily funded by $6 million from friends and family. Company founder Jim Belosic believes the time is right to accept investment to meet the speed and volume requirements of a rapidly reindustrializing American economy.#Manufacturing #MadeInAmerica #SendCutSend #Automation #CNC #LaserCutting #IndustrialNews #ManufacturingNow #Reindustrialization #AmericanManufacturing #FactoryTech #ManufacturingIndustry #Startups #IndustrialAutomation #Aerospace #DefenseManufacturing #Robotics #SupplyChain #DataCenters #Innovation

In this message we walk through Romans 13 and talk about how God transforms our everyday lives

Send us Fan MailWhy are chronic illness rates continuing to rise despite advancements in medicine and technology?In this episode of the Never Been Sicker podcast, Michael Rubino sits down with Dr. Phil Straw to discuss the growing disconnect between symptom management and true root-cause healing.Dr. Straw also shares how neuropathy can impact everything from balance and sleep to bladder control and overall quality of life — and why addressing the root cause matters more than masking symptoms.If you've been struggling with unexplained symptoms, chronic inflammation, fatigue, tingling, balance issues, or simply feel like something is being overlooked, this conversation is for you.Timestamps00:00 — Why America Has “Never Been Sicker”02:20 — The “Pill for Every Ill” Problem04:00 — Mold Exposure & Autoimmune Conditions06:00 — Why Band-Aid Solutions Aren't Working08:20 — The Body's Ability to Heal10:00 — How Mold Exposure Became Part of the Conversation13:00 — Anxiety, Depression & Environmental Triggers16:00 — Why Modern Healthcare Isn't Working18:30 — Energy Efficiency vs Human Health21:20 — What Neuropathy Actually Is26:00 — Why Patient Education Matters29:00 — Insurance Companies & Broken Healthcare33:00 — Why Root Cause Medicine Requires Mindset Shifts35:30 — The Biggest Root Causes Behind Chronic Illness37:00 — “Your Genes Are Not Your Destiny”39:00 — The Ozempic Conversation40:45 — Final Thoughts & Takeaways-----------------------------------------------------------------------------------------------

Yann LeCun, Turing Award winner and former Chief AI Scientist at Meta, joins Jacob Effron. The conversation centers on Yann's contrarian thesis that LLMs are a dead-end on the path to human-level intelligence, despite being useful products — because they can't predict the consequences of their actions, can't plan, and fundamentally can't model the messy, high-dimensional real world. He unpacks his alternative architecture, JEPA (Joint Embedding Predictive Architecture), which learns abstract representations rather than generating pixel-level predictions, and explains why this approach is essential for robotics, industrial applications, and any system that needs to operate beyond the substrate of language. Yann also reveals the real story behind his departure from Meta (he had zero technical influence on Llama, contrary to public narrative), the genesis of his Tapestry project for sovereign open-source AI, why he believes LLMs are intrinsically unsafe, where he diverges from his fellow Turing laureates Hinton and Bengio, and why he predicts the industry will recognize the paradigm shift by early 2027. Throughout, he offers candid reflections on the tension between research and product at major labs, and why he intentionally headquartered AMI Labs in Paris with zero Silicon Valley VC money.   (0:00) Introduction  (01:45) Why LLMs Aren't the Path to Intelligence  (07:51) AMI and World Models  (12:07) The JEPA Architecture Explained  (15:55) Problems with Robotics Models Today  (20:37) Silicon Valley Herd Behavior  (28:18) Tapestry: Sovereign AI for the Rest of the World  (35:49) OpenAI Is the Next Sun Microsystems  (40:51) Why Yann's Views Diverged from Hinton & Bengio  (44:32) LLMs Are Intrinsically Unsafe  (58:00) Why Yann Left Meta  (1:00:26) Reflections on FAIR  (1:12:11) Advice for PhD Students   LeWorldModel Paper: https://arxiv.org/abs/2603.19312   With your host:  @jacobeffron  - Partner at Redpoint

In this message we walk through Romans 13 and talk about how God transforms our everyday lives

What if the reason you feel confused or uncertain about your decisions isn't because you're off track, but because you're trying to force clarity before it's time? In this episode, Nicole unpacks one of the most important lessons for emotional authorities in Human Design: emotions are always moving, and your perspective moves with them. She explores why emotional highs and lows can completely change the way you experience your business, relationships, creativity, and decisions, and why reacting too quickly during emotional shifts often creates more confusion instead of clarity. Through examples from a recent Human Design mini mastermind, Nicole breaks down the difference between intellectually understanding Human Design and actually integrating it into your life. She shares how many people mistake temporary emotional states for permanent truth and explains why waiting is not about delaying your life, but about giving yourself space to see clearly. This episode also introduces a simple but powerful mantra that can completely change the way Emotional Authorities move through uncertainty: "Nothing needs to be decided right now." If you've ever felt pressure to figure everything out immediately, questioned yourself because your emotions changed overnight, or struggled to trust your process when momentum fades, this conversation will help you approach your emotional wave in a completely different way. Listen now!   Learn more about your Human Design and get your full chart for free at https://www.nicolelaino.com/chart   To download the FREE 2027 Shift Guide DM "2027" to Nicole on Instagram instagram.com/nicolelainoofficial or go to nicolelaino.com/2027    Do register for the FREE 2027 Change: Leadership in the Paradigm of the Sleeping Phoenix Workshop DM Nicole "LEADERSHIP" on Instagram instagram.com/nicolelainoofficial or go to nicolelaino.com/leadership   Be sure to visit nicolelaino.com/podcastlinks for all of the current links to events, freebies, and more!    If you enjoyed this week's episode, I'd so appreciate you doing a few things for me:  Please subscribe to the podcast on Apple Podcasts, Spotify, or wherever you listen! Rate and review the podcast on Apple Podcasts.  Tag me @nicolelainoofficial on your IG stories with a story of you listening to the podcast and I'll make sure to share your post!  Interested in learning more about working with me? Click here to learn more about how we can work together.   

Patellar Luxation Reimagined: Shifting the Treatment Paradigm with Dr. David DycusPatellar luxation is one of the most commonly diagnosed orthopedic conditions in dogs—but are we thinking about it all wrong?In this episode of the PetAbility Podcast, we revisit this familiar condition through a very different lens with veterinary orthopedic surgeon David Dycus, DVM, MS, CCRP, DACVS-SA. Rather than focusing on the basics of diagnosis and grading, Dr. Dycus shares emerging insights that challenge conventional thinking about what truly drives patellar instability and dysfunction - and the profound arthritic changes that this alignment mismatch may lead to over time -  by treating each case individually.Together, we discuss: What are the limitations of the traditional patellar luxation treatment model   Why eliminating grading of patellar luxation offers a broader perspectiveHow alignment of the proximal limb (femur) and distal limb (tibia) affects patellar stability and why 3D imaging via CT scan is key How biomechanics and functional movement are reshaping treatment   considerations How surgical decision-making is evolving through a patient-specific approach How the shift toward more non-traditional surgical corrections is resulting in   better short-term and long-term prognosis Why collaborative care, rehabilitation & conditioning are more vitally important for best outcomes The future of patellar luxation management in veterinary medicineThis episode is ideal for veterinarians, rehabilitation professionals, veterinary students, breeders, trainers, and dedicated pet owners interested in the future of canine orthopedic care. If you thought patellar luxation was “just a minor knee problem,” this conversation may completely change your perspective.Click for more information about Dr. Dycus and his practice, Fusion Veterinary Orthopedics. Follow Dr. Dycus on Instagram and Facebook.DisclaimerVitalVet.org, a platform for all things related to pet rehab - product information, education, and resources abound! MedcoVet (show sponsor)  Luma - advanced red-light therapy therapy that puts healing in the hands of the pet owner in the comfort of home! Use Promo Code PETPOD22  to receive discounts from our affiliates!Jope - science-backed supplements Ruff Ramp - a safe alternative to stairs Optimum Pet Vitality - education/coursework  Dr. Buzby's -Toe Grips to prevent slipping, Encore Mobility joint supplement, and Brain Boost cognitive supplement. Using this link donates 20% to PetAbility Calm & Cozy Cat Wrap - a must-have for anybody working with catsHedzUpPets Watercollars – save your dog from drowni...

In this episode, Tim Whitaker engages with Anna Clark Miller, a counselor and author of 'For God's Sake, Recovering from Religious Trauma,' shares her journey through high-control religion, the impact of spiritual abuse, and pathways to healing. Discover practical advice for navigating faith recovery, understanding empathy's role, and recognizing the influence of religious trauma on mental health. Learn more about Anna | Empathyparadigm.com Chapters 02:54 Understanding Spiritual Abuse 08:54 Navigating Trust and Community 12:03 The Role of Worship in Healing 18:02 Curiosity as a Tool for Recovery 21:07 Self-Compassion and Judgment 23:52 Conclusion and Resources ____________________________________________________ TNE Podcast hosts thought-provoking conversations at the intersection of faith, politics, and justice. We're part of the New Evangelical's 501c3 nonprofit that rejects Christian Nationalism and builds a better path forward, rooted in Jesus and centered on justice.  If ⁠⁠⁠⁠⁠⁠⁠⁠you'd like to support our work or get involved, visit our website: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠www.thenewevangelicals.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠  Follow Us On Instagram @thenewevangelicals  Subscribe On YouTube @thenewevangelicals This show is produced by Josh Gilbert Media | ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Joshgilbertmedia.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Learn more about your ad choices. Visit megaphone.fm/adchoices

Have you ever noticed that the harder you try to force momentum, the more stuck and drained you feel? In this episode, Nicole breaks down what it really means for Generators and Manifesting Generators to create momentum through the sacral response — and why so many people misunderstand what "following your energy" actually looks like in practice. She shares the subtle ways we disconnect from our bodies, overthink our next move, and accidentally drain the very energy we're trying to create. Nicole also explores the difference between fear and misalignment, and why many people assume they're "off path" when they're actually just caught in conditioning or mental pressure. Through relatable examples from content creation, business, and everyday life, she shows how presence becomes the key to unlocking clarity, creativity, and sustainable momentum. You'll also hear Nicole unpack why Human Design is meant to be integrated, not just intellectually understood. From sacral engagement to intuitive expression, this conversation highlights how understanding your design can help you stop forcing outcomes and start working with your natural energy in a way that feels lighter, more effective, and far more satisfying. Plus, Nicole shares insights about the energetic shifts leading into 2027 and why learning how to guide yourself and others differently is becoming more important than ever. If you've been feeling disconnected from the way you used to work, create, or lead, this episode may help you understand why.   Learn more about your Human Design and get your full chart for free at https://www.nicolelaino.com/chart   To download the FREE 2027 Shift Guide DM "2027" to Nicole on Instagram instagram.com/nicolelainoofficial or go to nicolelaino.com/2027    Do register for the FREE 2027 Change: Leadership in the Paradigm of the Sleeping Phoenix Workshop DM Nicole "LEADERSHIP" on Instagram instagram.com/nicolelainoofficial or go to nicolelaino.com/leadership   Be sure to visit nicolelaino.com/podcastlinks for all of the current links to events, freebies, and more!    If you enjoyed this week's episode, I'd so appreciate you doing a few things for me:  Please subscribe to the podcast on Apple Podcasts, Spotify, or wherever you listen! Rate and review the podcast on Apple Podcasts.  Tag me @nicolelainoofficial on your IG stories with a story of you listening to the podcast and I'll make sure to share your post!  Interested in learning more about working with me? Click here to learn more about how we can work together.   

Bitcoin Update: Bitcoin consolidates near $81K after failing to hold $83K resistance, supported by White House confirmation of an imminent crypto market structure bill markup.Institutional Momentum: BlackRock's IBIT saw $480M+ in inflows over 48 hours, while a major U.S. pension fund added another $310M to Bitcoin via ETFs.Regulatory Progress: The U.S. House is set to vote on the revised stablecoin bill next week with state chartering options included; Hong Kong approved two more licensed exchanges.Security Incident: A $19M flash-loan exploit hit a DeFi protocol on Base chain, the second major incident on the network in two weeks.Major Funding Round: AetherFi (AI-powered decentralized lending protocol) raised $120 million in a Series A led by a16z Crypto and Paradigm.Hot Presales: IONIX CHAIN raised $28 million and PEPEBOSS raised $19 million in the past 48 hours, showing strong retail interest in early-stage projects.Altcoin Watch: Galaxy Research and other analysts are highlighting five altcoins (LINK, KAS, SUI, NEAR, and TAO) with tight technical setups and concrete May catalysts that could lead the next leg up if Bitcoin holds above $81K.Sources:CoinDesk, Cointelegraph, Decrypt, The Block, Reuters, Fortune, Yahoo Finance, X trending data, CoinMarketCap & CoinGecko. Hosted on Acast. See acast.com/privacy for more information.

Law firms sell experience — but for decades, harnessing and operationalizing that experience has been a largely manual, chaotic process. In this episode, recorded live at the Legal Marketing Association annual conference in New Orleans, host Bob Ambrogi sits down with Jason Noble, president and chief of product strategy at Ikaun, to talk about how his company is changing that. Ikaun is a managed service and technology platform that helps law firms streamline the proposal and RFP response process — from capturing and organizing matter experience data to using AI to assemble and draft competitive pitches. Jason explains how the platform works, how the arrival of generative AI transformed what was previously possible, and why Ikaun positions itself as a managed service rather than a self-serve SaaS tool. Jason and Bob also get into the bigger picture of how law firms are responding to AI-driven changes in the competitive landscape, whether the billable hour can survive in an AI-augmented world, and whether the RFP process itself will look the same in the years ahead — or whether we're moving toward a future where agents are submitting and responding to proposals with minimal human involvement.   Thank You To Our Sponsors This episode of LawNext is generously made possible by our sponsors. We appreciate their support and hope you will check them out.   Paradigm, home to the practice management platforms PracticePanther, Bill4Time, MerusCase and LollyLaw; the e-payments platform Headnote; and the legal accounting software TrustBooks. Briefpoint, eliminating routine discovery response and request drafting tasks so you can focus on drafting what matters (or just make it home for dinner).   Chapters   (00:00) Introduction to ICON and Legal Tech Innovations (02:30) Jason Noble's Journey and Background (05:20) The Evolution of ICON and Its Focus (07:09) Experience Management in Legal Firms (10:30) Gathering Experience Data in Litigation (11:48) How ICON's Platform Works (14:05) The Impact of AI on Proposal Processes (18:07) Current Landscape of RFP Responses (20:31) Differentiating ICON from Competitors (22:45) Knowledge Management vs. Experience Management (24:01) Tailoring Solutions for Law Firms (25:49) Qualities of Successful Law Firms (27:24) Law Firms' Response to AI Integration (29:54) Pricing Strategies in RFP Responses (31:21) Competitive Landscape and AI's Influence (33:27) The Future of Billable Hours (35:50) The Future of RFPs and AI's Role (39:33) Client Satisfaction and Future Directions   If you enjoy listening to LawNext, please leave us a review wherever you listen to podcasts.  

Customer Experience isn't short of activity—it's short of new ideas that actually land. In this episode, Colin and Ryan dig into why genuinely fresh thinking in CX struggles to break through, how industries get stuck in "normal science," and why it feels like we're doing more measurement… without more progress. They explore what a real disruption looks like, the warning signs that a paradigm is reaching diminishing returns, and how leaders can break out of the loop. Best Quote  "When a paradigm hits its limits, the next move isn't 'do more.' It's think differently—and be willing to ruffle a few feathers." Colin Shaw: Key Takeaways Are we measuring more because we're improving—or because we don't know what else to do? If satisfaction is stagnating, what "accepted" CX beliefs might be holding us back? What would a real CX disruption look like—and are we brave enough to recognize it when it shows up? Why You Should Listen If you've felt like CX is turning into an echo chamber—same language, same frameworks, same playbook—this episode gives you a sharper lens on why that happens and what to do next. You'll hear how paradigm shifts actually work, the signals that the current model is running out of runway, and practical ways to find (and foster) ideas that can genuinely move the industry forward. Resources Mentioned Colin Shaw - https://www.linkedin.com/in/colinrjshaw/ Professor Ryan Hamilton - http://linkedin.com/in/ryan-hamilton-49b3321  ACSI National Customer Satisfaction (Q3 2025 press release): https://theacsi.org/news-and-resources/press-releases/2025/11/13/press-release-national-acsi-q3-2025/ PwC Global Workforce Hopes and Fears (psychological safety): https://www.pwc.com/gx/en/issues/workforce/hopes-and-fears.html About the Hosts: Colin Shaw is a LinkedIn 'Top Voice' with a massive 286,000 followers and 87,000 subscribers to his 'Why Customers Buy' newsletter. Shaw is named one of the world's 'Top 150 Business Influencers' by LinkedIn. His company, Beyond Philosophy LLC, has been selected four times by the Financial Times as a top management consultancy. Shaw is co-host of the top 1.5% podcast 'The Intuitive Customer'—with over 600,000 downloads—and author of eight best-sellers on customer experience. Shaw is a sought-after keynote speaker. Follow Colin on LinkedIn. Ryan Hamilton is a Professor of Marketing at Emory University's Goizueta Business School and co-author of 'The Intuitive Customer' book. An award-winning teacher and researcher in consumer psychology, he has been named one of Poets & Quants' "World's Best 40 B-School Profs Under 40." His research focuses on how brands, prices, and choice architecture influence shopper decision-making, and his findings have been published in top academic journals and covered by major media outlets like The New York Times and CNN. His work highlights how psychology can help firms better understand and serve their customers. Ryan has a new book launch in June 2025 called "The Growth Dilemma: Managing Your Brand When Different Customers Want Different Things" Harvard Business Press Follow Ryan on LinkedIn. Subscribe & Follow Apple Podcasts Spotify  

Welcome to OncLive On Air®! I'm your host today, Courtney Flaherty.OncLive On Air is a podcast from OncLive®, which provides oncology professionals with the resources and information they need to provide the best patient care. In both digital and print formats, OncLive covers every angle of oncology practice, from new technology to treatment advances to important regulatory decisions. In today's episode, Michael J. Pishvaian, MD, PhD, sat down to discuss the evolving role of biomarker-directed strategies in gastrointestinal (GI) oncology, as well as the importance of early comprehensive testing to identify molecular drivers and resistance mechanisms when approaching frontline treatment selection and sequencing. Pishvaian serves as director of the Gastrointestinal, Developmental Therapeutics, and Clinical Research Programs for the Johns Hopkins Kimmel Cancer Center in the National Capital Region.Pishvaian began the discussion by highlighting the shift from a disease-site-specific approach to a molecularly defined paradigm, noting that microsatellite instability–high status and NTRK fusions now dictate therapy regardless of tumor origin. He reviewed the transformational data from the phase 3 HERIZON-GE-01 trial (NCT04276493), positing that zanidatamab (Ziihera) could become the new standard of care for HER2-positive upper GI cancers due to unprecedented survival outcomes. He also emphasized the emergence of Claudin 18.2-directed therapies, noting that data from the phase 2 ILUSTRO study (NCT03505320) demonstrates remarkable progression-free survival when adding zolbetuximab (Vyloy) to mFOLFOX6 and nivolumab (Opdivo) for high-expressing subgroups.The conversation then shifted to colorectal cancer, where Dr. Pishvaian detailed how data from the phase 3 BREAKWATER trial (NCT03845036) has "locked in" a paradigm requiring frontline testing for BRAF V600E mutations to guide the use of encorafenib (Braftovi) plus cetuximab (Erbitux). He also discussed the "care revolution" in KRAS inhibition, spotlighting the significant survival benefits seen with daraxonrasib in pancreatic cancer and the potential for novel allele-specific inhibitors to combat disease resistance.Finally, Pishvaian addressed the practicalities of implementation, noting that testing rates in the community remain low. He advocated for prioritizing testing, including liquid biopsies and ctDNA, at the time of initial diagnosis to ensure no patient is left behind.This content is a production of OncLive; this OncLive On Air podcast episode is supported by funding, however, content is produced and independently developed by OncLive.

In today's fast-paced business environment, effective leadership is crucial for achieving sustainable business growth and organizational effectiveness. Mechanical leaders often create mechanical results, which can hinder a company's ability to adapt to a paradigm shift in business and ultimately limit its potential for long-term success. By adopting a living organization framework and focusing on human development in organizations, leaders can foster a corporate culture change that prioritizes heart-centered leadership, emotional intelligence, and servant leadership principles. This approach enables leaders to develop innovative leadership strategies that promote collective identity in teams, enhance team dynamics, and drive strategy execution. As a result, organizations can experience a significant transformation, leading to improved leadership maturity and a more human-centric approach to business. By embracing this new perspective, leaders can unlock their full potential and create a positive impact on their organizations, ultimately achieving remarkable results and driving sustainable growth. Discover how mechanical leaders can create mechanical results and learn how to break free from this cycle to achieve exceptional leadership transformation and organizational effectiveness.The discussion centers on the transformative paradigm introduced by Norman Wolfe, where organizations are reimagined not just as mechanical structures but as living, evolving entities. This change in perspective prompts a significant reevaluation of leadership methods, urging leaders to adopt a heart-centered approach that values human potential over the traditional focus on optimizing resources like machines. Wolfe points out that the current paradigm has created a disconnect between strategy execution and the overall development of people, resulting in a surprising statistic—the fact that roughly 70% of organizations stumble in their strategic efforts. As we explore the details of this living organization model, it becomes clear that an organization's success is closely tied to the collective maturity and relational dynamics of its members. Therefore, effective leadership depends on cultivating environments where collaboration and personal initiative flourish, ultimately increasing organizational resilience and flexibility in facing today's challenges.Takeaways:Leadership in contemporary organizations necessitates a paradigm shift from mechanistic approaches to recognizing organizations as living systems, emphasizing the importance of nurturing human development alongside business outcomes.Norman Wolfe's Living Organization framework posits that sustainable growth is intrinsically linked to the development of individuals within an organization, highlighting the necessity for leaders to cultivate maturity and capability among their teams.The persistent failure of 70% of organizations to effectively execute strategy stems from a prevalent paradigm trap that restricts innovative thinking, necessitating a reevaluation of traditional operational methodologies.To foster a culture of ownership and engagement, leaders must transition from simply directing tasks to facilitating collaborative contribution, thereby enhancing the collective identity of teams within the organizational ecosystem.The concept of 'heart-centered wisdom' emerges as a pivotal guiding principle, advocating for leaders to prioritize authentic connections and emotional intelligence in their interactions with team members.As organizations face escalating complexity and unpredictability in their environments, the Living Organization model offers a resilient framework that empowers adaptability and responsiveness to dynamic market conditions.Links referenced in this episode:quantumleaders.comthelivingorganization.comMentioned in this episode:My friend Dr. Noah St. John calls this 'the invisible brake.' He's giving our listeners a free Revenue Ceiling Audit to help you see what's REALLY holding you back. You'll also get a FREE 30-day membership to Noah Bot, giving you access to Dr. Noah's 30 years of experience to help you reach your next level. But hurry, because there are only 50 available this month. So if you're tired of being stuck at the same revenue level and want to finally break through, get your FREE Revenue Ceiling Audit at https://www.noahvault.com?aff=d28bf6c78150c7f09896297dfe1701c1cd191ac6fc9976779212cec5d38e94d6

In this message, Pastor Chad talks through Romans 12 and what it looks like to actually live in biblical community

Originally recorded at Science and Nonduality, 2021 Pat McCabe, also known as Woman Stands Shining, is a Diné elder, ceremonial prayer leader, and international speaker adopted into the Lakota spiritual way of life. In this conversation hosted by Lynn Murphy, Pat offers a profound invitation to examine the foundational assumptions of the modern world paradigm and consider what it might mean to live from a genuinely different understanding of what it is to be human. Drawing on teachings from her clan grandfather, her experience of intergenerational trauma and survival, and her deep inquiry into masculine and feminine principles, Pat maps the territory between the glittering world we are leaving and the green world we are entering. The conversation opens in ceremony and closes with a practice: a morning sunrise offering that anyone can begin today. Lynn Murphy is a strategic advisor for foundations and NGOs working in the geopolitical South. She was a senior fellow and program officer at the William and Flora Hewlett Foundation where she focused on international education and global development. She resigned as a ”conscientious objector” to neocolonial philanthropy. She holds an MA and PhD in international comparative education from Stanford University. She is also a certified Laban/Bartenieff movement analyst. This episode is released in celebration of SAND's new film featuring Pat McCabe, Little Singer, premiering online May 26-28, 2026, as part of the Eternal Song series. Timestamps 00:00:00 — Introduction 00:01:45 — Lynn Murphy introduces Pat McCabe: Diné nation, Lakota spiritual way, Defend the Sacred alliance 00:05:00 — Pat introduces herself through her clans — clan names as places on the earth, worlds more than this one 00:07:00 — Traveling through worlds: the flood, men and women, and the movement from the glittering world to the green world 00:15:00 — The two paradigms: indigenous versus modern world — "I am a human being, relative to all my relations" 00:34:00 — Trailer for Little Singer — premiering online May 26-28, 2026 — theeternalsong.org/littlesinger 00:35:00 — Masculine and feminine principles: power over versus power with, the sacred hoop, and right relations 00:52:00 — A practice for beginning: the morning sunrise offering and the teaching on consent, sovereignty, and honorable relationship with all beings Resources and Links Pat McCabe — Woman Stands Shining Website: patmccabe.net Little Singer — Eternal Song Series Online premiere: May 26-28, 2026 Three-day event with Diné voices Mentioned in the episode Robin Wall Kimmerer — Braiding Sweetgrass (plant sovereignty, honorable harvest) Lakota spiritual traditions — Seven Generations teaching Diné (Navajo) Nation — Long Walk history, Bosque Redondo concentration camp, 1860s Residential boarding school history — US government and church collaboration Masculine and feminine principles in economics and right relations — ongoing inquiry in Pat's work Episode artwork “Woman Stands Shining” by Namita Contact SAND podcast@scienceandnonduality.com Support the mission of SAND and the production of this podcast by becoming a SAND Member

In this episode of Paradigm Shifting Books, hosts Stephen and Britain Covey sit down with bestselling author Dan Coyle, whose books The Talent Code and The Culture Code have already reshaped how we think about individual growth and team dynamics. Now, with his latest book, Flourish, Dan takes an even bigger step, exploring not just how we perform or collaborate, but how we build truly meaningful lives and communities. At the heart of it all is a radical reframe: flourishing isn't something you achieve alone. It's mutual, shared, and rooted in connection.Stephen and Britain reflect on how Dan's ideas echo their grandfather's concept of the maturity continuum, the journey from dependence to independence to interdependence, and how Flourish makes the case that interdependence, not independence, is the real destination. Dan shares vivid stories from his research, including the miraculous survival of the 33 Chilean miners, the New England Patriots' Super Bowl run, and a $90 million deli ecosystem in Ann Arbor, to illustrate how questions, pauses, and shared vulnerability unlock something in people that answers and productivity never can. This episode is a must-listen for anyone who wants to move from self-improvement to shared flourishing in their teams, families, and everyday lives.What We Discuss[00:00] Introduction[02:09] What Does It Mean to Flourish? Redefining Success[04:28] The Backpack of Individualism and How to Put It Down[05:45] Task Attention vs. Relational Attention: The Toggle Switch in Your Brain[07:39] Why Questions Unite and Answers Drive People Apart[10:31] Life as Treasure Creation, Not a Treasure Hunt[11:11] The Four H Exercise and the New England Patriots[22:01] Lessons from the Chilean Miners[26:21] Embracing the Beautiful MessNotable Quotes[02:10] "The scientific definition of flourishing would be: joyful, meaningful, growth shared. And the piece that surprised me was that last word." – Dan Coyle[08:01] "The places that really end up flourishing are ones that are able to really dig into deep questions and create space for people to circle up and explore those questions together." – Dan Coyle[23:52] "Paradigm shifts only happen with questions. They never happen with answers." – Dan Coyle[27:36] "If you're gonna have a system that's alive, imperfection should be celebrated. If you're doing it all a hundred percent perfectly, you're not doing it right." – Dan CoyleResourcesParadigm Shifting BooksPodcastInstagram YouTube BookFlourish by Dan CoyleDan CoyleWebsiteFacebookLinkedInBooks: The Talent Code, The Culture CodeBritain CoveyLinkedIn InstagramStephen H. CoveyLinkedIn

“…what you need to know is this. And that is the difference between a conventional farmer and a sustainable farmer is that a conventional farmer grows plants and a sustainable farmer grows soil; and very simple in it's difference, and yet incredibly profound in how it takes you down two different paths, because, what are you doing if you're growing plants?”In this episode of Personalization Outbreak, Glenn Llopis sits down with Dr. Britt Yamamoto, author of The Soil of Leadership, to explore a powerful idea: great leadership is like sustainable farming. It is not about chasing quick wins, it is about cultivating the conditions for long-term growth.They unpack the difference between “growing plants” and “growing soil,” why trust cannot be forced, how burnout is a systems issue, and what leaders can do to rebuild healthier cultures through reflection, self-awareness, and sustainable leadership practices.----------------------------------------------------------------------------------------------------Video Content:   0:00 - Intro   03:44 - Leadership Starts with Soil, Not Strategy   16:09 - Reclaiming the Right Soil   20:17 - Why Most Workplaces Are Broken at the Root   27:23 - Leadership 3.0: The Shift Leaders Must Make Now   30:16 – The Soil of Leadership: Cultivating the Conditions for Transformation   33:13 - The Personalization of Leadership   38:44 - We Can't Practice What We Can't Imagine   41:22 – The Hyakusho Way: Japanese Wisdom for a Flourishing Life   43:26 - Rebuilding Trust Starts Within   45:36 - Shifting from Paradigm to Purpose   50:31 - Community First, Corporate Second   ----------------------------------------------------------------------------------------------------   

In this compelling fourth lecture of the series, Acharya das reframes well-being through the lens of timeless wisdom, drawing from sources like the Bhagavad Gita to reveal a powerful three-dimensional model: body, mind, and the often-overlooked spiritual self. With precision and clarity, the talk exposes a universal truth—no amount of success, relationships, or material gain can resolve the subtle but persistent sense of emptiness that many experience. This is not a personal failure or circumstantial issue; it is a signal pointing toward something deeper.The Bhagavad- gītā verse quoted in this talk:In this world, there is nothing so sublime and pure as transcendental knowledge. Such knowledge is the mature fruit of all mysticism. And one who has achieved this enjoys the self within himself in due course of time. - Bhagavad-gītā 4.38Such a liberated person is not attracted to material sense pleasure or external objects but is always in trance, enjoying the pleasure within. In this way the self-realized person enjoys unlimited happiness, for he concentrates on the Supreme. - Bhagavad-gītā 5.21One whose happiness is within, who is active within, who rejoices within and is illumined within, is actually the perfect mystic. He is liberated in the Supreme, and ultimately he attains the Supreme. - Bhagavad-gītā 5.24Chapters00:00:00 Introduction and Three-Dimensional Well-being Paradigm ‎ 00:02:22 The Universal Experience of Emptiness and Advertising Manipulation ‎ 00:04:38 Personal Counseling Example: Fear of Being Alone ‎ 00:06:44 Behavioral Patterns of Avoiding Emptiness ‎ 00:08:38 Life Clutter and Hidden Loneliness‎ 00:11:19 Emptiness as Spiritual Protection and Indication ‎ 00:13:18 Material Wealth and Relationship Status Don't Eliminate Emptiness ‎ 00:15:01 The Inadequacy of the Material World ‎ 00:16:37 A Woman's Honest Blog About Emptiness ‎ 00:23:47 Attraction to Beauty, Happiness, and Love ‎ 00:27:00 The Ice Cream Sundae Metaphor ‎ 00:28:52 Spiritual Malnourishment and the Fish Out of Water Metaphor ‎ 00:30:31 The Inward Journey and Purpose of Human Life ‎ 00:33:07 Bhagavad Gita Verses on Transcendental Knowledge ‎ 00:35:56 Liberation Through Spiritual Understanding ‎ 00:37:59 The Self-Realized Person's Experience ‎ 00:39:30 The Perfect Mystic and Spiritual Attainment ‎ 00:41:08 Two Simple Practices: Yoga Wisdom and Meditation ‎ 00:42:16 Spiritual Sound and Its Purifying Effects ‎ 00:44:15 The Signal of Inner Longing ‎ 00:45:41 The Futility of Material Investment ‎ 00:46:55 Invitation to Kirtan Practice ‎

Ian's done a bit of spring cleaning, suspension refreshing, and playlist stacking. And Dave? He snagged some car photos that he knows Ian is going to love. We love you!

Pastor Jon walks us through Romans 11 to find a clearer view of God's mercy

"Men with the muckrakes are often indispensable to the well-being of society; but only if they know when to stop raking the muck, and to look upward to the celestial crown above them, to the crown of worthy endeavor." ~ Theodore Roosevelt, April 14, 1906, speech "The Man with the Muck-Rake". This is the operational reality of the current information battle space.  #BardsFM_Morning #Muckraker #Peacemaker Bards Nation Health Store: www.bardsnationhealth.com MYPillow promo code: BARDS >> Go to https://www.mypillow.com/bards and use the promo code BARDS or... Call 1-800-975-2939.  EMPShield protect your vehicles and home. Promo code BARDS: Click here Treadlite Broadforks...best garden tool EVER. Promo code BARDS26: TreadliteBroadforks.com EnviroKlenz Air Purification, promo code BARDS to save 10%: www.enviroklenz.com Morning Intro Music Provided by Brian Kahanek: www.briankahanek.com Founders Bible 20% discount code: BARDS >>> TheFoundersBible.com Windblown Media 20% Discount with promo code BARDS: windblownmedia.com White Oak Pastures Grassfed Meats, Get $20 off any order $150 or more. Promo Code BARDS: www.whiteoakpastures.com/BARDS Mission Darkness Faraday Bags and RF Shielding. Promo code BARDS: Click here   If you wish to support this podcast directly you can donate here... DONATE: Click here Mailing Address: Xpedition Cafe, LLC Attn. Scott Kesterson 591 E Central Ave, #740 Sutherlin, OR  97479

Pastor Chad talks about our part in salvation through Romans 10