Podcasts about continual

What does it take to build economies that are truly inclusive—and built for long-term impact? In this episode of Develop This!, Dennis Fraise speaks with Philip Gaskin to explore his diverse career spanning the private sector, entrepreneurship, and community development—and how those experiences shape his approach to economic transformation today. Philip shares how lessons from the private sector can directly inform economic development strategy, especially when it comes to innovation, ecosystem building, and driving measurable community impact. The conversation also highlights the importance of addressing systemic barriers that limit access to capital and opportunity in underserved communities. A key focus is the role of economic developers as connectors—bridging policy, private sector insight, and community needs to build stronger, more resilient local economies.   The discussion also touches on Kansas City's evolving economic landscape and how regional ecosystems can serve as powerful models for inclusive growth and entrepreneurial support. Key Takeaways Private sector experience can strengthen economic development strategy Inclusive growth requires addressing access to capital and opportunity gaps Economic developers play a key role in policy and collaboration Strong ecosystems drive innovation and community transformation Kansas City offers a model for regional economic growth Continuous transformation is essential for long-term impact Key Topics Covered Private sector lessons for economic development Community and economic transformation Inclusive entrepreneurship and access to capital Role of economic developers in policy and collaboration Kansas City's ecosystem and growth model Sound Bites "Crazy times call for crazy organizations" "Communities need to embrace their potential" "Continual work on transforming communities"  

A common trap in the Christian life is the “graduation mindset”: I got baptized, received First Communion, got confirmed… I'm good. Joe Rockey and Father Boniface Hicks argue that this is not only false—it quietly starves your soul. This episode is a practical invitation and blueprint for continual conversion: ongoing reaffirmation with Jesus that turns faith from a box you checked into a life you live.Father lays out a simple foundation that makes growth sustainable: Sunday Mass, monthly confession, daily prayer (15 minutes to an hour), spiritual reading, and a dose of silence. Once those basics are in place, faith begins to “take on a life of its own.” You start pulling on a thread—an event, a parish opportunity, a lead—and it opens doors you didn't plan: Bible study, new friendships, new discoveries, deeper prayer, real formation. And God isn't passive in any of it—He attracts, invites, and prepares opportunities without manipulating your freedom.Joe adds what this looks like in real practice: don't stay a passive listener to Scripture. Put yourself in the scene. Notice the emotions that aren't written down. Ask what the apostles needed their readers to understand and why. That habit of deeper attention builds a stronger interior life—and even changes how you hear the homily at Mass. The call is simple: keep going deeper, because depth is what breaks the “I did this once, I'm done” illusion.Key IdeasThe “I'm done” mindset (post-sacraments) is spiritually costly; the antidote is ongoing conversion.A durable foundation: Sunday Mass + monthly confession + daily prayer + spiritual reading + silence.Growth often starts with a small “thread” (event/opportunity) that becomes a habit and opens unexpected doors.God draws without coercion: invitation, attraction, prepared opportunities—no manipulation.Go deeper in Scripture by entering the scene: emotions, relationships, motives—not just facts.Links & References (official/source only)Hallow (official):https://hallow.com/Bible in a Year (Ascension, official):https://ascensionpress.com/pages/bibleinayearCatechism in a Year (Ascension, official):https://ascensionpress.com/pages/catechisminayearJeff Cavins (official):https://www.jeffcavins.com/CTA: If this helped, please leave a review or share this episode with a friend.Questions or thoughts? Email FatherAndJoe@gmail.com .Tags (comma-separated)Father and Joe, Joe Rockey, Father Boniface Hicks, continual conversion, ongoing conversion, sacraments, baptism, first communion, confirmation, Sunday Mass, confession, monthly confession, daily prayer, spiritual reading, silence, Scripture, Bible study, catechism, formation, discipleship, Catholic life, parish life, retreat, pilgrimage, parish mission, Eucharistic adoration, holy hour, daily Mass, Hallow app, Bible in a Year, Catechism in a Year, Jeff Cavins, homily, spiritual growth, curiosity, habits, events to habits, freedom, God's invitation

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

A verse by verse study through the book of 1 John with Pastor Kevin Edwards of Calvary Chapel Clayton, NC. https://www.calvaryclayton.com

SHABBAT DAY LESSON — LEVITICUS 24Teachers: Kerry & Karen BattleWHAT WE COVERLeviticus 24 reveals the difference between maintained holiness and gradual covenant decay.This chapter is not merely about lamps, bread, punishment, or judicial law.The chapter exposes:continual covenant consciousnesscontinual maintenancecontinual remembrancethe weight of speechpublic corruptioninward decaydesensitization toward holinessequal justice before YahuahThe Continual Lamp and Maintained IlluminationLeviticus 24:1–4The lamp was commanded to burn continually before Yahuah.The oil had to remain pure.The priests were responsible for maintaining the light continually.This section reveals that holiness requires continual maintenance.The chapter exposes a terrifying reality:People rarely drift into darkness suddenly.Usually:maintenance weakens firstreverence weakens nextcompromise spreads quietlythen corruption manifests publiclyThe Holy Bread and Continual RemembranceLeviticus 24:5–9The bread remained continually before Yahuah as a memorial.This section teaches:continual remembrancecontinual dependencecovenant awarenessdisciplined orderThe chapter reveals that people often collapse because continual remembrance weakens over time.Familiarity slowly destroys reverence.What people stop honoring continually, they eventually begin treating casually.The Blasphemer and the Exposure of Inward CorruptionLeviticus 24:10–16The blasphemer did not begin with outward speech first.The mouth exposed corruption already forming inwardly.This section reveals:hardened dishonorpublic corruptioninward decayconflict exposing formationdesensitization toward holinessPressure exposed what had already been maintained secretly in the heart.The chapter teaches that public corruption is often the final visible stage of inward compromise long tolerated privately.Equal Justice and Covenant OrderLeviticus 24:17–23The same law applied equally.The same accountability applied equally.This section reveals:judicial consistencyrestrained justicecovenant orderequal standards before YahuahHoliness without justice becomes hypocrisy.Justice without holiness becomes brutality.WHY THIS MESSAGE MATTERSLeviticus 24 exposes how covenant decay develops gradually inside individuals and communities.The chapter teaches:what is continually maintained reveals what is truly honoredtolerated compromise reshapes consciencefamiliarity weakens reverenceneglected maintenance spreads darkness quietlyspeech eventually exposes inward formationcommunities decay collectively when corruption becomes normalizedThis chapter destroys emotional religion.Holiness is not occasional emotion.Holiness requires continual maintenance before Yahuah.SCRIPTURE REFERENCESLeviticus 24Leviticus 24:1–4Leviticus 24:5–9Leviticus 24:10–16Leviticus 24:17–23Exodus 27:20–21Psalm 119:105Proverbs 6:23Deuteronomy 8:11–14Matthew 12:34–37Matthew 12:31–32James 3Isaiah 5:201 Corinthians 5Galatians 6:7ABOUT AHAVA ~ LOVE ASSEMBLYWe teach the pure Word of Yahuah. No religion. No traditions. No compromise.Teaching is established by Scripture only: line upon line, precept upon precept, with covenant understanding rooted in the Hebrew thought-world of the text.SUPPORT THE WORK — GIVE VIA ZELLEZelle QR available at: ahavaloveministry.comZelle only.FINAL WORDHoliness rarely collapses suddenly.It usually decays gradually through:neglected maintenanceweakened remembrancetolerated compromisefamiliaritydesensitization toward holinessWhat is continually maintained reveals what is truly honored before Yahuah.FINAL HEART CHECKWhat are you continually maintaining?Has reverence become continual, or merely emotional?Have you slowly become desensitized toward holiness?What emerges from your mouth during pressure?What does your speech reveal has been growing inwardly for years?Are you preserving holiness collectively, or silently tolerating corruption?

There is a major sin issue Paul addresses in 1 Corinthians 5 and he tells the church, who is boasting about this particular sin, that this man should be banned from their assembly, he should be turned over to Satan, and they should not even eat a meal with this guy! Sin is serious and is not a toy to be played with! We are to repent of our sin, which means turn away from it, and we must die to sin (Romans 6). When we give our lives to Christ, the old man is buried and we come out of that water a new creation, filled with he Holy Spirit. He begins to transform our lives into he image of Christ...if we let him. Do not choose sin over righteousness!

This episode of Own Your Power explores the life-changing impact of continual personal growth, challenging listeners to break free from stagnation, fear, and comfort to unlock their true potential. It emphasizes that real fulfillment and happiness come from progress, not perfection, and that growth requires intentional action, pushing through discomfort, and redefining limiting beliefs. By focusing on self-improvement, embracing challenges, and committing to becoming a better version of yourself every day, you can create the freedom, success, and extraordinary life you truly desire. Own your power with this Success Tip.   For more about Rod and his real estate investing journey go to www.rodkhleif.com

Partakers of the Divine Nature2 Peter 1:1-11 Partakers of the Divine Nature: 2 Peter 2:1-11 Chris Moore Message Slides For the bulletin in PDF form, click here. Our Passive Role in Spiritual Growth (vv. 1-4) - Our Growth Begins with God's Initiative (vv. 1-3) - Our Growth Continues as we Hear & Believe (v. 4)Our Active Role in Spiritual Growth (vv. 5-11) - True Spiritual Growth is Comprehensive (vv. 5-7) - True Spiritual Growth is Continual (v. 8) - True Spiritual Growth is Essential (vv. 9-11)Discussion Questions1. Think about a time in your life when you experienced significant spiritual growth. What were some of the key elements that led to your growth?Our Passive Role in Spiritual Growth (2 Peter 1:1-4)2. What does it mean that God “has granted to us all things that pertain to life and godliness” (1:3)? Does this mean we don't need any outside resources like books or other people? How would you explain this?3. One way we grow and become “partakers of the divine nature” is by hearing and believing His “precious and very great promises” (1:4). What promises has God made that encourage you most? 4. What are some practical ways we can make sure we continue believing and trusting so we keep growing in Christ? Our Active Role in Spiritual Growth (2 Peter 1:5-11)5. Peter mentions eight characteristics in vv. 5-7. We are supposed to “make every effort” to grow in these areas. In which of these areas do you need to grow?6. In v.8 we learn we should be “increasing” in these eight areas and in our spiritual growth. Are you in a season of spiritual growth right now? If not, what next steps can you take?7. Do you tend to emphasize the active role or the passive role in your spiritual growth? Which aspect needs some extra attention right now? Pray for the Unreached: The Kapu in India The Kapu are a large Hindu community in southern India, historically known as farmers and protectors, with many still engaged in agriculture today. While some have moved into business, education, and leadership, many remain in rural areas with limited access to resources. Though the Bible and gospel tools are available, only a small percentage follow Christ. Pray for a growing movement of disciples among the Kapu, for hearts to be open to the gospel, and for both their spiritual and physical needs to be met.FinancesWeekly Budget 34,615Giving For 04/19 40,027Giving For 04/26 20,288YTD Budget 1,488,462Giving 1,796,478 OVER/(UNDER) 308,016 Fellowship Baby DedicationFellowship is grateful to partner with parents as they dedicate their children to the Lord. On Sunday, May 10, during both services, we will set aside a special time for families to dedicate their children before the Fellowship body. If you would like to participate, please email Lisa at lgerdes@fellowshipconway.org and include your preferred service time. The dedication will take place at the beginning of each service.New to Fellowship?We are so glad that you chose to worship with our Fellowship Family this morning. If you are joining us for the first time or have been checking us out for a few weeks, we are excited you are here and would love to meet you. Please fill out the “Connect Card” and bring it to the Connection Center in the Atrium, we would love to say “hi” and give you a gift. Fellowship Kids VBS - There's No Place Like Rome…That's why we want your kids to join us for an exciting Bible-times adventure with the Underground Church in ancient Rome! They will explore authentic Marketplace shops, visit the Apostle Paul (who's under house arrest), sneak to the cave where the Underground Church meets, take part in games, dance to lively Bible songs, and sample tasty tidbits as they discover more about the early church. Join us June 22-26, 9:00 am- 12:00 pm. This is for kids currently in Kindergarten through 4th grade. Register by May 24 at ffellowshipconway.org/register. FSM 2026 Fellowship GraduatesWe're excited to celebrate our 2026 high school seniors! If Fellowship Bible Church is your home, we'd love to honor you during our Sunday morning services on May 17 at fellowshipconway.org/register. Send five photos for the senior slideshow to Casey Goode at cgoode@fellowshipconway.org by May 1. Fellowship Women's Bible Study - Knowing GodJoin us for “Knowing God,” a 4 week study of The Trinity by Rebecca Carter & Heather Harrison. We'll meet Tuesday nights at 6:30pm, beginning June 2nd at Fellowship. Register at fellowshipconway.org/women. Text Shanna at 336-0332 to reserve free childcare by May 25th.Fellowship Kids Summer Volunteers We are wrapping up the school year and preparing to head into summer. We are continuing our three-year journey through the Bible, and we need your help to do so. Our children are ready to learn about and worship Jesus. We have a place for everyone...Nursery, classroom leaders, hall monitors, storytellers, and special needs buddies. The summer sessions are May 31 through August 9. Contact Heather today at hfulmer@fellowshipconway.org or Ashley at aoverstreet@fellowshipconway.orgMission fundraiser at StobysTHANK YOU FELLOWSHIP!!! With your support (and many, many pancakes made and eaten) we were able to raise around $2,500 towards our youth/college trip to the Czech Republic. We appreciate you and your generosity!Prayer During ServiceWe love to pray for one another. Our prayer team will have people at the front of the Auditorium under the signs Hope and Love to pray for you after the message. Please feel free to walk up to them for prayer or encouragement during the first worship song after the message.

2 Peter 2:9 TPTIf the Lord YAHWEH rescued Lot, he knows how to continually rescue the godly from their trials and to reserve the ungodly for punishment on the day of judgment.

God's people can close their day with thankful praise because the Lord has all along again provided for them in every way. Transition from Morning to Evening with Continual Praise for God's Provision Throughout Your Day.

Shintaro and David discuss Ken Gunji, a high-level Japanese judoka training at the dojo, and the massive impact he's had on the room. They dive into technical exchanges, differences in gripping systems, and how having an elite training partner elevates both coaching and learning.00:00 Intro to Ken Gunji00:10 Size, athleticism, and presence on the mat00:47 Role in Japan training trip and dojo connections01:11 Keio University and academic background02:20 Language differences: Japanese vs English communication02:50 Asahi Kasei career and All Japan Pro Tournament success04:05 Middle school All Japan wrestling champion04:36 How Gunji elevates the training environment05:13 High-level technical discussions and idea exchange06:31 Importance of having a true “judo sounding board”07:49 Translating high-level concepts into teaching08:42 Consistency of having a world-class athlete in the dojo09:27 Value of hands-on learning vs instructionals09:54 Differences in gripping systems (tight vs loose sleeve control)10:23 Timing-based entries vs control-based approaches10:50 Why certain techniques are hard to teach across styles11:40 Training drills: Ouchi gari finishing mechanics12:38 Gunji's transitions: cutback to Uchimata13:09 Importance of precise, actionable feedback13:54 Problems with vague coaching (“no kuzushi”)14:24 Importance of high-level training partners14:37 Uchimata timing and hop sequencing strategy15:05 Matching opponent movement to avoid counters15:34 Continual learning—even at elite levels15:48 Mutual learning between high-level athletes16:08 Training with Gunji at the dojo16:17 Outro

AI has been trained like software. But what if it should be grown like life? In this episode of Eye on AI, Craig Smith sits down with Sebastian Risi, professor and leading researcher in neuroevolution and artificial life, to explore a fundamentally different approach to building intelligence, one inspired by how nature evolves, grows, and adapts. Sebastian explains why traditional AI systems are limited by fixed architectures and one-time training, and how evolutionary algorithms can create systems that continuously learn, self-organize, and even grow their own neural structures over time. They dive into concepts like plastic neural networks that keep updating during their lifetime, AI systems that can recover from damage, and models that develop from a single "cell" into complex structures, similar to biological organisms. The conversation also explores how combining large language models with evolutionary search could unlock more creative and open-ended problem solving, from merging specialized models to building AI systems capable of generating and testing scientific ideas. If you want to understand where AI is headed beyond today's transformer models, and why the future may look more like living systems than software, this episode offers a clear and thought-provoking perspective. Subscribe for more conversations with the people building the future of AI and emerging technology. Stay Updated: Craig Smith on X: https://x.com/craigss Eye on A.I. on X: https://x.com/EyeOn_AI (00:00) Why copy nature's evolution for AI (01:20) What neuroevolution actually means (05:52) How evolutionary search replaces gradients (08:03) Plastic neural networks and continuous learning (11:53) Growing neural networks like living systems (18:08) Scaling challenges and limits of growth (23:16) Can evolving systems replace LLM training (27:28) Continual learning and model merging (30:27) Artificial life, self-repair, and resilience (35:10) AI scientists and evolution with LLMs

This week, we have tech editors Ronan Mc Laughlin and Josh Weinberg coming in from opposite ends of the world, both in dimly lit hotel rooms, and without their usual podcast recording equipment. It's only up from here!  In the first section, Dave Rome chats to Ronan about his previous day touring Pirelli. Then Dave reminds us of the real-world compromises that 1x shifting continues to battle. Also, you'll hear a rant, and Ronan has a Good Thing that many probably already own.  Next stop is Dave catching up with our US tech editor Josh Weinberg, who finds himself in Taiwan for the Taipei Cycle Show.  And finally, members of Escape Collective (who get access to everything we do at Escape Collective), can tune in for our popular Ask a Wrench segment, where Dave and pro mechanic Zach Edwards answer technical questions from members. Finally, the day has come for Geek Warning to be a motion picture. You'll now find episodes on YouTube, too.    Happy Geeking!    Time stamps:    4:40 - Touring Pirelli HQ  12:00 - Pirelli's new flagship race tyre 18:00 - Wolf Tooth's new flagship Mark Zero range 21:40 - The real world compromises of 1x shifting  34:00 - Content creation that has Dave ranting  40:20 - Ronan's Good Thing that you may already own - 44:45 - Taipei Cycle Show with Josh  52:00 - 32er manufacturing is brewing, 3D printing, and other trends 1:07:00 - Ask a Wrench (members only)  1:08:00 - Shimano brakes gone bad if not used  1:17:30 - Stuck tyre bead on rim. Solutions?  1:26:00 - Re-using old brake hoses during re-routing 

The Oil and Gas Continual Spike Explained full 447 Tue, 17 Mar 2026 13:23:08 +0000 iPI5lo1uDxh4NCSOoKpXv5LE6YKYpPYC emailnewsletter,news The Big K Morning Show emailnewsletter,news The Oil and Gas Continual Spike Explained The Big K Morning Show 2024 © 2021 Audacy, Inc. News False https://player.amperwavepodcasting.com?feed-link=ht

Got a question? Let us know!Step Ten: Ongoing InventoryThis week on Made for Mondays, Heather is joined by Jamey, Tyler, and RaChelle to talk about Step 10 — continuing to take personal inventory and promptly admitting when we're wrong. Before diving into the conversation, the group catches up about the weekend and reflects on the Bible Reading Challenge, continuing through Deuteronomy and Mark.Then the conversation turns to Sunday's message.SUNDAY DISHThe reaction to “taking inventory” When people hear the phrase take inventory, reactions vary. For some it sounds freeing and clarifying. For others it feels exhausting or intimidating. The group reflects on why honest self-examination can feel uncomfortable—even though it's meant to lead to freedom.The illusion of “arriving” Jamey pointed out that following Jesus doesn't make us sinless—it makes us forgiven. Yet many Christians quietly assume maturity means we should eventually stop struggling. That expectation can create pressure to hide our struggles instead of bringing them honestly before God and trusted community.“When,” not “if” Step 10 uses the phrase when we were wrong, not if. That small word reminds us that spiritual growth doesn't eliminate mistakes—it teaches us how to respond when they happen. Honest acknowledgment of failure doesn't lower the bar for holiness; it keeps us grounded in humility and grace.Living one day at a time Jamey shared the illustration of eating a lifetime's worth of food one day at a time. In the same way, spiritual growth becomes overwhelming when we try to think about the entire journey at once. Focusing on today helps us stay connected to Jesus in the present instead of discouraged by the past or anxious about the future.Honest community The group reflects on a story shared Sunday about an older man who openly admitted his ongoing struggles. Moments like that show the power of honesty in community. When people feel safe enough to tell the truth about their lives, it creates space for real growth without pretending we've already arrived.Practicing Step 10 Jamey described three ways to practice this step:Spot-check inventory — pausing in the moment when something feels offDaily inventory — reflecting on the day with GodPeriodic inventory — stepping back occasionally for deeper reflectionFor someone feeling overwhelmed, the best place to start may simply be a daily moment of reflection with God—asking where things went well, where we missed the mark, and where grace is needed.Final ReflectionRegularly admitting when we're wrong doesn't push us farther from Jesus—it keeps us close to Him. Honest reflection reminds us that growth isn't about perfection, but about continually returning to grace.Join Us SundayThat's all we have time for today, friends! Join us THIS Sunday at 9 and 10:45 AM as we continue taking the next step toward healing and freedom together. If you can't make it in person, watch on YouTube at 1 PM.These Steps may be challenging, but they're shaping something good.Remember: it works if you work it. Go be love, everybody—we'll see you next week!Stay Connected Website: https://believerschurch.org/ Bible Reading Plan: https://believerschurch.org/bible-reading-plan/ Believers Facebook: https://www.facebook.com/believerschurch.va/ Believers Instagram: https://www.instagram.com/believers_church/ Subscribe to The Outlet: https://believerschurch.us13.list-manage.com/subscribe?u=66f00f86238de86688d2480e6&id=729c3f381f

The Health Detective Podcast is entering a new chapter. In this transition episode, Michele Scarlet steps in as the new host and shares what listeners can expect moving forward. This podcast is dedicated to real health transformations; the kind that happen when we start asking deeper questions and looking beyond surface-level answers. Together, we'll explore the patterns behind chronic symptoms, investigate root causes, and continually evolve our understanding of functional health. Moving forward, you can expect conversations around: • Functional health transformations and case-based insights • The art of asking better questions in root cause medicine • Continual education and evolving clinical thinking • Interviews with practitioners pushing the boundaries of functional health • Occasional insights into the business side of health coaching and building a practice Because healing doesn't happen when we stop learning; it happens when we stay curious. If you're a practitioner, health coach, or someone passionate about understanding the body and uncovering real solutions, you're in the right place. Subscribe so you don't miss what's ahead. Until the next investigation… keep asking deeper questions.

Bex Moorhouse is Global Head of Strategy, Ops Excellence & Performance - Procurement & REWS at WPP where she is passionate about helping to prioritize employee experience and create environments where people thrive. Mike Petrusky asks Bex about her new role and her passion for cultivating such engaging environments where all employees feel seen, valued, and empowered. She believes that empathy and curiosity are crucial "power skills" for workplace professionals, enabling them to adapt, learn, and lead effectively in changing environments, so she shares that storytelling and clear communication are essential. Bex and Mike discuss how real estate and facility management teams often need to better articulate their value in business terms and focus less on justification and more on impact for end users. Continual adaptation, embracing new technologies, and focusing on both operational excellence and human experience will keep the FM profession relevant, so Mike and Bex offer the inspiration you will need to be a Workplace Innovator in your organization! Connect with Bex on LinkedIn: https://www.linkedin.com/in/bexmoorhouse/ Learn more about Bex's work: https://www.bexmoorhouse.com/ Find out more about WPP: https://www.wpp.com/en-us Watch the podcast on YouTube: https://www.youtube.com/playlist?list=PLSkmmkVFvM4H3pwnlU2AuqynuRDpvnh4J Discover free resources and explore past interviews at: https://eptura.com/discover-more/podcasts/workplace-innovator/ Learn more about Eptura™: https://eptura.com/ Connect with Mike on LinkedIn: https://www.linkedin.com/in/mikepetrusky/  

The readings for this homily: https://bible.usccb.org/bible/readings/030926.cfmFather Matthew Tomeny, MIC, opens with a memorable story from Venerable Archbishop Fulton Sheen, who once welcomed a drunk woman into Saint Patrick's Cathedral in New York City. Rather than turning her away, he offered her tea and promised not to ask her to go to confession — until she returned sober and ready to encounter God's mercy.Father Matthew connects this to the Scripture reading of Naaman the leper, who expected an extraordinary cure but was healed by the simple act of dipping seven times in the Jordan River. Salvation does not require grand quests or heroic feats. Instead, the Sacraments of the Church provide the ordinary means by which God cleanses our souls and restores our union with Him.Through Baptism, Jesus washes away our sins. Through the Sacrament of Reconciliation, He continues to cleanse us when we fall. And through the Eucharist, we express that communion in the most intimate way possible. Father Matthew emphasizes that holiness is intended for all people, regardless of their past. Just as Archbishop Sheen did not write off the drunk woman, neither should we write off anyone who struggles.Continual repentance—the virtue of penance—keeps our hearts aligned with God's will. When we are in order with God, trials lose their power to derail us. Take advantage of these simple ways to holiness and share that satisfaction with others. ★ Support this podcast ★

  I mentioned a number of resources that I would provide links for or include for your further study.  First, if you want to expand your study into the ideas of Unintentional sin and Intentional sin, please check out … Exodus 69 part 2 – https://lightofmenorah.podbean.com/e/exodus-69-part-2-exod-2920-37-ram-of-the-lord-sanctifies-head-and-heart-and-hands-and-ferret/ Yom Kippureem Episode 1 - https://lightofmenorah.podbean.com/e/fall-feasts-of-the-lord-yom-kippureem-episode-1-it-is-finished/ Episode 4 - https://lightofmenorah.podbean.com/e/yom-kippureem-episode-4-the-goat-and-the-lamb-john-539/ Genesis Lesson 70 - https://lightofmenorah.podbean.com/e/genesis-70-gen-2813-15-we-all-will-be-blessed/ See the chart below showing a little more detail as to the OLAT HATAMEED or the “Continual Burnt Offerings.”  The final blood sacrifice that completed the Covenant was the sacrifice of the Lamb of God “who takes away the sins of the world” and was offered between the sacrifices. Rev. Ferret - who is this guy?  (Ferret - on Tel el Safi or ancientGath Israel) What's his background?  Why should I listen to him?  Check his background at this link - click here for the teacher's background

The Philadelphia Flyers are having a tough season to say the least. As the team is still in their rebuild mode, we've seen some good hockey. We've also seen some not to good hockey. What might this team and front office do before the trade deadline? This week, Daniel Esche from BrotherlyPuck.com and the Brotherly Pod podcast joined us for a great discussion about this team as well as some Lehigh Valley Phantoms storylines as well.But first, the guys dove into how the Sixers are having major issues with rebounding - a theme that's not getting enough attention this season. (Approx. 5:00)From there, they got into how the Eagles should be handling certain aspects of the offseason. Should they truly try to acquire Maxx Crosby and what should the front office do about the tight end position?(Approx. 16:40)The guys then talked about the positive vibes stemming from Phillies Spring Training as Andrew Painter and Bryce Harper have been showing us some good stuff! (Approx. 28:10)What they threw down on the Table this week was a great and in-depth conversation with Daniel Esche from Brotherly Puck about this Flyers team. The team has been in a holding pattern. What could Danny Briere do at the trade deadline to truly help this team during the rebuild? Is Rick Tocchet the guy to coach this team to the next level? All of this and much more this week on the Table! (Approx. 36:35)SUBSCRIBE on YouTube: youtube.com/@thephiladelphiasportstableHead over to our website for all of our podcasts and more: philadelphiasportstable.comFollow us on Threads: @philadelphiasportstableFollow us on Twitter/X: @PhiladelphiaPSTFollow us on Instagram: @philadelphiasportstable.Follow us on Facebook: facebook.com/PhiladelphiaSportsTable

Support the show

Alisa is on fire with a message that's resonating with so many: understanding and finding peace with both food noise—the mental chatter around eating—and body noise—the persistent thoughts about how we look and show up in the world. In this episode, she breaks down why these inner messages exist, how they connect to deeper feelings of safety, and what it takes to respond with awareness, truth, and grace. What You'll Learn: What food noise really is: Persistent mental chatter about food that can feel overwhelming. Why it exists: Not all food noise is bad! Hunger is actually a gift—a signal from your body to nourish yourself. The 7 forms of hunger: From true, homeostatic hunger to emotional, social, environmental, habitual, survival, and reward hunger. Understanding which is which can help you respond with awareness rather than guilt. The connection to safety: Increased food noise often points to a deeper sense of insecurity or loss of safety. Body noise: Continual thoughts about our appearance and how we look, and why awareness is the first step in responding differently. Soul work: How sin and brokenness in our world have disrupted our connection to God, ourselves, and others, and why body and food struggles often show up the moment we feel "something is wrong" with our bodies. Hope in community: RW+ offers a space to explore, process, and grow together. Scripture Highlight: Genesis 3:9 reminds us that God seeks us even in our brokenness—and invites us into healing, not shame.

Alisa is on fire with a message that's resonating with so many: understanding and finding peace with both food noise—the mental chatter around eating—and body noise—the persistent thoughts about how we look and show up in the world. In this episode, she breaks down why these inner messages exist, how they connect to deeper feelings of safety, and what it takes to respond with awareness, truth, and grace. What You'll Learn: What food noise really is: Persistent mental chatter about food that can feel overwhelming. Why it exists: Not all food noise is bad! Hunger is actually a gift—a signal from your body to nourish yourself. The 7 forms of hunger: From true, homeostatic hunger to emotional, social, environmental, habitual, survival, and reward hunger. Understanding which is which can help you respond with awareness rather than guilt. The connection to safety: Increased food noise often points to a deeper sense of insecurity or loss of safety. Body noise: Continual thoughts about our appearance and how we look, and why awareness is the first step in responding differently. Soul work: How sin and brokenness in our world have disrupted our connection to God, ourselves, and others, and why body and food struggles often show up the moment we feel "something is wrong" with our bodies. Hope in community: RW+ offers a space to explore, process, and grow together. Scripture Highlight: Genesis 3:9 reminds us that God seeks us even in our brokenness—and invites us into healing, not shame.

#310 In this episode, Thom Plummer shares insights on how gym owners can build lasting businesses by focusing on purpose, continuous learning, and strategic planning. Discover how to avoid common pitfalls, develop emotional connections, and reinvent your approach every few years for lasting success and fulfillment. Main Topics Covered: The importance of starting with a clear life and business purpose Mastering core skills: sales, marketing, and finance Developing emotional ties through storytelling and communication The significance of strategic exit planning and long-term vision Reinventing your business approach every 3-5 years Trends shaping the future of gyms, including aging populations and AI impacts Personal character traits that foster ongoing growth and leadership Timestamps: 00:00 - Introduction and guest credibility 02:29 - Beginnings in the gym industry in 1977 04:13 - Lessons learned from past entrepreneurial ventures 07:15 - Mastering business fundamentals for gym owners 09:14 - Horizontal vs. vertical management in gyms 11:19 - The importance of daily sales and marketing discipline 13:21 - Planning your business with an end goal in mind 17:30 - The significance of understanding your exit strategy 20:39 - Trends: aging populations and classic gym models return 23:10 - The dangers of chasing other people's dreams 25:22 - The power of storytelling and emotional connection 27:05 - Developing communication skills for business growth 29:24 - The impact of reading and continual learning 32:37 - AI, data, and future trends in the fitness industry 35:52 - Reinventing the business every 3-5 years 39:00 - Personal stories of transformation and leadership 43:41 - Building genuine client relationships and community 47:36 - The value of personal integrity and serving others 51:22 - Continual self-education and pulling the thread of knowledge 54:08 - Resources and strategies for improving writing skills 58:23 - The importance of storytelling and human touch in marketing 61:00 - Final reflections on purposeful living and legacy Resources & Links: The Experience Economy by Pine & Gilmore Stage Not Age by Christina Roulstone Anne Handley's Writing Courses Gotham Writers Workshop SNHU Writing Programs Connect with Thom Plummer: Perform Better Speaker Schools Additional Highlights: Emphasizing that true progress comes from intentional story-driven communication. The necessity of planning the business's end game to align daily actions. Reinvention as key to staying relevant amidst changing industry trends. The importance of character traits like coachability, humility, and service. This episode underscores that long-term success in the gym industry hinges on purpose, strategic management, continual learning, and authentic human connection. Implement these principles to elevate your business and life.  

MESSAGE SUMMARY Learning to Trust God with the Desires of My Heart By Patricia Hudson, M.S. 1) Opening prayer and purpose of the message Patricia opens by thanking God for the day and asking Him to help her speak words that are “seeds”—words that will touch hearts and produce fruit in the lives of both in-person listeners and livestream viewers. Her prayer emphasizes that God's work is corporate and individual: He is speaking to the whole church, but also to each person's specific life, struggles, and calling. She thanks Dr. Bryan Hudson for the opportunity to minister, connecting her message to the church's yearlong focus: “Delight in the Lord, desires of the heart fulfilled.” She references an earlier teaching (Dec. 28) titled “Joy is Delight, Bent for God,” which becomes the foundation for how she develops Psalm 37:4. 2) Starting with the Day 4 devotional: Delight means “bent” With Pastor Hudson's permission, Patricia begins by reading the Day 4 devotional, “Delight in the Lord.” The devotional's key idea is that: God reshapes desires before He fulfills them. “Delight” biblically means to take pleasure in, to incline toward, or to bend. What we delight in is revealed by what pulls us, shapes us, motivates us, and “bends” us—either positively or negatively. This introduces a crucial lens for the entire sermon: delight is not a feeling only—it is a direction. Delight means your inner life is being shaped, inclined, and formed. She stresses that because “to delight is to be bent,” we must pay attention to our desires and discern whether they come from God or from something else. As we delight in the Lord—His character, presence, and promises—God forms us into a “shape” that pleases Him. 3) Relational, not transactional: God gives transformed desires Patricia repeats a major refrain: life with God is relational, not transactional. In other words, Psalm 37:4 is not a “deal” where people delight so God gives a wishlist. Instead: Delighting in God reshapes the heart. What God fulfills is not merely personal ambition, but desires that have been transformed by relationship with Him. She quotes Pastor Hudson's idea that what comes from being “bent” through relationship with God is being granted, bestowed, and entrusted with genuine heart desires. She also highlights another phrase: Jesus refines, aligns, and “calibrates” the heart, so what we increasingly desire reflects God's will. 4) The “bend” metaphor: transformation can be uncomfortable Patricia explains why “bend” matters to her: bending changes shape, and bending is not always comfortable. Depending on age, bending can be easier or harder, but the point is spiritual: Being bent toward God may not feel easy, and the shape we start with may not be the shape we end with, because God is bending us for His purposes. This becomes a pastoral encouragement: discomfort does not mean God is absent—it can mean God is shaping you. 5) The guiding questions: where do desires come from? Patricia invites the Holy Spirit to guide listeners through several reflective questions: What (or who) is the source of my desire? Are there desires of the soul (mind, will, emotions) and desires of the flesh? (Yes—but they are different.) Is “desire” the same as “desires of the heart”? Do desires of the heart come from God? Are heart desires only meant to bless me—or also to bless others? Her direction is clear: this teaching is not merely about getting what we want, but about understanding purpose. 6) Word study: “desires of the heart” as petition flowing from delight Patricia introduces a word study to emphasize that Psalm 37:4 is specific. She explains that the Hebrew term she's focusing on carries the sense of: a heartfelt plea, a request, a petition toward God. She says this word appears only twice in the Old Testament (Psalm 20:5 and Psalm 37:4), which for her underscores that the phrase is purposeful and weighty. Her takeaway: true desires of the heart become petitions God is willing to satisfy when they arise from delight in Him. So she urges people to watch how they use the word “desire”—because we can want many things, but “desires of the heart” in this sense are the kind that rise out of communion with God. 7) Continual desires: God isn't done with you One of her most encouraging points is that the “desires of the heart” concept implies something ongoing—not finished, continual. That excites her because it speaks directly to people who wonder, especially later in life, “Lord, is there still more?” Her answer is yes: as you continue delighting in the Lord, God continues shaping desires and giving zeal and passion to finish your race and fulfill purpose—regardless of age. 8) Abraham and Sarah: a case study in trust, waiting, and purpose Patricia then turns to Abraham and Sarah to show how this works in real life. She frames their story as a living example of learning to trust God with heart desires. a) Genesis 12 — Called to go without knowing God calls Abram to leave his country and go to a land God will show him. Patricia imagines the human reactions: “Where are we going? What are we going to do? Are you serious?” Yet Abram trusts God and goes—at 75 years old, emphasizing again that it is never too late for purpose. b) Genesis 15 — God promises an heir Abram voices concern: “What good are blessings if I have no son?” God responds with the promise of a son and descendants as numerous as the stars. Abram believes, and God counts it as righteousness. c) Genesis 16 — Sarah tries to “help God” Patricia highlights the emotional realism: Sarah is barren, years pass, hope fades, frustration grows. She calls it a picture of what people still do today: desperate people do desperate things. Sarah proposes Hagar as a workaround, and Ishmael is born. Patricia emphasizes that human solutions can create complications and conflict—because it wasn't God's plan. d) Genesis 17 — God reiterates: “I said what I said” This becomes one of Patricia's repeated phrases: God reaffirms His promise. He changes Abram and Sarai's names to Abraham and Sarah, and specifies that Sarah will bear the promised son Isaac. Her point: God has not changed the original promise, even though time passed and mistakes were made. e) Genesis 21 — Isaac is born after 25 years Isaac is born when Abraham is 100 and Sarah is 90—a 25-year wait from the initial promise. Patricia contrasts this with how impatient people can be: we pray today and struggle to wait even days. But she stresses: waiting is not empty time—something is happening in us. God is preparing people to carry what He promised. She states it plainly: circumstances don't change the promise, and delays don't cancel God's purpose when we remain delighted in Him. 9) Genesis 22 — The test: will you trust God with what you love most? After Isaac arrives—the heart's desire—God tests Abraham: offer Isaac. Patricia frames this as the ultimate picture of her theme: Will you obey God with the desire of your heart? Can you trust the Giver even with the gift? Abraham prepares to obey, declaring in faith that God will provide. God stops him and provides a ram. Then God reaffirms the covenant again: blessing, descendants, and worldwide impact through Abraham's offspring. Patricia's conclusion from this scene: Abraham learned trust over time, and the test revealed where his heart truly rested—in God, not merely the promise. 10) Bigger than personal blessing: prophetic purpose fulfilled in Christ Patricia then lifts the story to its larger meaning: Abraham's longing for an heir was not only personal—it was prophetic. Through Isaac's line comes Jesus Christ. God's promise that Abraham's seed would bless the nations finds fulfillment in Christ. She reads from Romans 4 to emphasize that Abraham's faith was recorded for our benefit, so believers today can trust that God keeps His promises and counts faith as righteousness through Christ. 11) Modern illustrations: “the this” and “the that,” and purpose that blesses others Patricia brings the message into contemporary life through two examples: a) Jan Mitchell's testimony (Jan. 18) She shares Jan's lesson: “You need the this to get to the that.” The journey (“the this”) may be uncomfortable, but it is often necessary for what God intends (“the that”). Patricia highlights the idea that if God gave some things immediately, they would bless only in the moment—but God's goal may be larger: overflow for the world, not just private relief. b) Ophelia Wellington and Freetown Village Patricia describes how a desire to teach African-American history grew into Freetown Village, reaching over one million people through programs. Her point: God can take a desire and unfold it into a life purpose that touches generations. There are “bumps, bends, drop-offs,” but purpose matures through perseverance and trust. 12) Closing invitation: partner with God, don't perform for God Patricia closes by returning to Pastor Hudson's framing: as we delight in Him, we will see the desires of our heart fulfilled. She calls the congregation to accept God's invitation: trust Him do good dwell in the land feed on His faithfulness delight in the Lord commit your way to Him And she clarifies: these are not fleshly works to earn something; we are laborers together with God.     

Olive Song from MiniMax shares how her team trains the M series frontier open-weight models using reinforcement learning, tight product feedback loops, and systematic environment perturbations. This crossover episode weaves together her AI Engineer Conference talk and an in-depth interview from the Inference podcast. Listeners will learn about interleaved thinking for long-horizon agentic tasks, fighting reward hacking, and why they moved RL training to FP32 precision. Olive also offers a candid look at debugging real-world LLM failures and how MiniMax uses AI agents to track the fast-moving AI landscape. Use the Granola Recipe Nathan relies on to identify blind spots across conversations, AI research, and decisions: https://bit.ly/granolablindspot LINKS: Conference Talk (AI Engineer, Dec 2025) – https://www.youtube.com/watch?v=lY1iFbDPRlwInterview (Turing Post, Jan 2026) – https://www.youtube.com/watch?v=GkUMqWeHn40 Sponsors: Claude: Claude is the AI collaborator that understands your entire workflow, from drafting and research to coding and complex problem-solving. Start tackling bigger problems with Claude and unlock Claude Pro's full capabilities at https://claude.ai/tcr Tasklet: Tasklet is an AI agent that automates your work 24/7; just describe what you want in plain English and it gets the job done. Try it for free and use code COGREV for 50% off your first month at https://tasklet.ai CHAPTERS: (00:00) About the Episode (04:15) Minimax M2 presentation (Part 1) (17:59) Sponsors: Claude | Tasklet (21:22) Minimax M2 presentation (Part 2) (21:26) Research life and culture (26:27) Alignment, safety and feedback (32:01) Long-horizon coding agents (35:57) Open models and evaluation (43:29) M2.2 and researcher goals (48:16) Continual learning and AGI (52:58) Closing musical summary (55:49) Outro PRODUCED BY: https://aipodcast.ing SOCIAL LINKS: Website: https://www.cognitiverevolution.ai Twitter (Podcast): https://x.com/cogrev_podcast Twitter (Nathan): https://x.com/labenz LinkedIn: https://linkedin.com/in/nathanlabenz/ Youtube: https://youtube.com/@CognitiveRevolutionPodcast Apple: https://podcasts.apple.com/de/podcast/the-cognitive-revolution-ai-builders-researchers-and/id1669813431 Spotify: https://open.spotify.com/show/6yHyok3M3BjqzR0VB5MSyk

In this Sunday message, Pastor Rich Whitter teaches from Hebrews 13:7–25, calling believers to a steady, enduring faith rooted in sound doctrine, faithful leadership, and unwavering devotion to Christ. The closing chapter of Hebrews reminds us that worship is not confined to a moment or a melody, but expressed through obedience, gratitude, perseverance, and lives that honor God daily.Hebrews 13 challenges us to remember those who lead us in faith, reject unstable teachings, endure hardship with confidence, and continually offer a sacrifice of praise to God through Jesus Christ.This message will encourage you to move beyond occasional worship and embrace a lifestyle of faithful, continual praise.Scripture: Hebrews 13:7–25Speaker: Pastor Rich WhitterLife Pointe ChurchSubscribe for more biblical teaching and Sunday messages from Life Pointe Church.

In this introspective episode of the Uncommon Wealth Podcast, host Phillip Ramsey addresses a compelling issue that many entrepreneurs face: the perils of anchoring one's identity solely in their business endeavors. Through reflective storytelling and practical insights, Ramsey unpacks the emotional and psychological challenges that can arise when deeply invested business leaders suddenly find themselves in a post-sale identity vacuum.Dive into a nuanced conversation about the intertwined nature of identity and entrepreneurship. Phillip Ramsey shares the compelling narrative of a former business owner who experienced a complete mental breakdown after selling his business. This episode delves into how this profound experience reveals the often-overlooked psychological stress related to business ownership and identity. Ramsey emphasizes the importance of acknowledging and addressing these issues early on, suggesting mindful consideration of one's identity beyond their business achievements. With expert analysis and real-life examples, Phillip provides a roadmap for aligning personal identity with broader life roles, such as being a parent, partner, or spiritual being, thus paving the way for a healthier, more balanced approach to business and life.Key Takeaways: Entrepreneurs often face identity crises post-business sale, highlighting the danger of tying identity solely to business roles. Business ownership, much like parenting, involves deep emotional investment, which can lead to identity issues when those roles change or end. Maintaining a multi-faceted identity is crucial for personal well-being; this includes identifying roles beyond being a business owner. Continual self-reflection and asking "Who am I?" can help build a comprehensive identity that is not reliant on external success or business status. Emphasizing personal roles, such as being a friend, family member, or spiritual individual, can offer stability and fulfillment beyond business achievements.Notable Quotes: "A lot of times business owners and people who are starting a business struggle with putting all of their identity in their business." "You pour yourself into a business as much as you do a child; when it's gone, you can feel lost, no matter your bank account balance." "When you think about your identity, try to think about something other than what your business is." "I want to have my identity rooted in something that can never be taken away."

I talk about how being emotionally accessible all the time is often mistaken for maturity or leadership, but taken too far it becomes a liability. When I'm always available to absorb other people's emotions, my own clarity and authority start to fade. Constant access doesn't build real connection, it trains people to depend on me while draining my energy and decision making. In this episode, I explain why boundaries around emotional access protect your presence and help you stay strong and focused. Show Notes: [02:25]#1 Constant access trains people to offload their emotional regulation onto you. [08:40]#2 Accessibility dilutes signal and presence.  [12:44]#3 Continual access creates emotional debt.  [15:36]Recap Next Steps: --- Power Presence is not taught. It is enforced. If you are operating in environments where hesitation costs money, authority, or leverage, the Power Presence Mastermind exists as a controlled setting for discipline, execution, and consequence-based decision-making. Details live here: http://PowerPresenceProtocol.com/Mastermind  This Masterclass is the public record of standards. Private enforcement happens elsewhere. All episodes and the complete archive: → WorkOnYourGamePodcast.com 

Reading edited and original versions of Bukowski poems before discussing AI and Ex Machina.

From the rising of the sun to its going down, the LORD's name is to be praised. Psalm 113:3From the rising of the sun to its setting, our God is worthy to be praised. He is worthy to be praised!Blessings,Presiding Elder Barbara HayesBe Still & Know

Nathan Lambert and Sebastian Raschka are machine learning researchers, engineers, and educators. Nathan is the post-training lead at the Allen Institute for AI (Ai2) and the author of The RLHF Book. Sebastian Raschka is the author of Build a Large Language Model (From Scratch) and Build a Reasoning Model (From Scratch). Thank you for listening ❤ Check out our sponsors: https://lexfridman.com/sponsors/ep490-sc See below for timestamps, transcript, and to give feedback, submit questions, contact Lex, etc. Transcript: https://lexfridman.com/ai-sota-2026-transcript CONTACT LEX: Feedback – give feedback to Lex: https://lexfridman.com/survey AMA – submit questions, videos or call-in: https://lexfridman.com/ama Hiring – join our team: https://lexfridman.com/hiring Other – other ways to get in touch: https://lexfridman.com/contact SPONSORS: To support this podcast, check out our sponsors & get discounts: Box: Intelligent content management platform. Go to https://box.com/ai Quo: Phone system (calls, texts, contacts) for businesses. Go to https://quo.com/lex UPLIFT Desk: Standing desks and office ergonomics. Go to https://upliftdesk.com/lex Fin: AI agent for customer service. Go to https://fin.ai/lex Shopify: Sell stuff online. Go to https://shopify.com/lex CodeRabbit: AI-powered code reviews. Go to https://coderabbit.ai/lex LMNT: Zero-sugar electrolyte drink mix. Go to https://drinkLMNT.com/lex Perplexity: AI-powered answer engine. Go to https://perplexity.ai/ OUTLINE: (00:00) – Introduction (01:39) – Sponsors, Comments, and Reflections (16:29) – China vs US: Who wins the AI race? (25:11) – ChatGPT vs Claude vs Gemini vs Grok: Who is winning? (36:11) – Best AI for coding (43:02) – Open Source vs Closed Source LLMs (54:41) – Transformers: Evolution of LLMs since 2019 (1:02:38) – AI Scaling Laws: Are they dead or still holding? (1:18:45) – How AI is trained: Pre-training, Mid-training, and Post-training (1:51:51) – Post-training explained: Exciting new research directions in LLMs (2:12:43) – Advice for beginners on how to get into AI development & research (2:35:36) – Work culture in AI (72+ hour weeks) (2:39:22) – Silicon Valley bubble (2:43:19) – Text diffusion models and other new research directions (2:49:01) – Tool use (2:53:17) – Continual learning (2:58:39) – Long context (3:04:54) – Robotics (3:14:04) – Timeline to AGI (3:21:20) – Will AI replace programmers? (3:39:51) – Is the dream of AGI dying? (3:46:40) – How AI will make money? (3:51:02) – Big acquisitions in 2026 (3:55:34) – Future of OpenAI, Anthropic, Google DeepMind, xAI, Meta (4:08:08) – Manhattan Project for AI (4:14:42) – Future of NVIDIA, GPUs, and AI compute clusters (4:22:48) – Future of human civilization

“Send Coach John a message”Found a great post that I got some good reflections on. It came from Reads with Ravi (@readswithravi) where this was shared from James Clear: “Embrace the fact that life is continual and look for ways to enjoy the daily practice.”  What was meant by this was a bit more in depth that helped me really connect to it.  “Work is endless. Exercise is endless. Parenting is endless. Same with marriage, writing, investing, creating, and more. You get to choose the parts of your life, but many of the important things in life cannot be “finished.”  Do not approach and endless game with a finite mindset. The objective is not to be done, but to settle into a daily lifestyle you can sustain and that allows you to make daily progress in the areas that matter.  Embrace the fact that life is continual and look for ways to enjoy the daily practice.”  I love the thought of things in life not ever being finished - other than our last day. I challenge myself to keep learning new things every day I have.  You know, something just came to mind was Mitch Albom with his friend and producer, Lisa Goich - their recent “Tuesday People Podcast” (listen to it HERE) was all about changing our perspective of living each day as if it's our last and start living it as it can be our “first” of doing different things. Rather than focus on things we might lose or never have again, it's a unique mindset shift that I think connects with this post, where we keep looking to continue things and not have things that are finished. Cool stuff if you ask me. Very motivating to start changing my perspective. Hope it is for you too.   Thanks for listening.  Please take a few moments to subscribe & share this with someone, also leave a 5 Star rating on Apple Podcasts and ITunes or other services where you find this show.  Find me on Facebook:  https://www.facebook.com/coachtoexpectsuccess/   on Twitter / “X”:  @coachtosuccess   and on Instagram at:  @coachjohndaly  - My YouTube Channel is at: Coach John Daly.   Email me at: CoachJohnDalyPodcast@gmail.com     You can also head on over to https://www.coachtoexpectsuccess.com/ and get in touch with me there on my homepage along with checking out my Top Book list too.  Other things there on my site are being worked on too.  Please let me know that you are reaching out to me from my podcast.  ** I would appreciate anyone to try clicking on the top of the show notes where it says "Send us a text" to leave a few thoughts / comments / questions.  It's a new feature that I'd like to see how it works. **

Sebastian Raschka joins the MAD Podcast for a deep, educational tour of what actually changed in LLMs in 2025 — and what matters heading into 2026.We start with the big architecture question: are transformers still the winning design, and what should we make of world models, small “recursive” reasoning models and text diffusion approaches? Then we get into the real story of the last 12 months: post-training and reasoning. Sebastian breaks down RLVR (reinforcement learning with verifiable rewards) and GRPO, why they pair so well, what makes them cheaper to scale than classic RLHF, and how they “unlock” reasoning already latent in base models.We also cover why “benchmaxxing” is warping evaluation, why Sebastian increasingly trusts real usage over benchmark scores, and why inference-time scaling and tool use may be the underappreciated drivers of progress. Finally, we zoom out: where moats live now (hint: private data), why more large companies may train models in-house, and why continual learning is still so hard.If you want the 2025–2026 LLM landscape explained like a masterclass — this is it.Sources:The State Of LLMs 2025: Progress, Problems, and Predictions - https://x.com/rasbt/status/2006015301717028989?s=20The Big LLM Architecture Comparison - https://magazine.sebastianraschka.com/p/the-big-llm-architecture-comparisonSebastian RaschkaWebsite - https://sebastianraschka.comBlog - https://magazine.sebastianraschka.comLinkedIn - https://www.linkedin.com/in/sebastianraschka/X/Twitter - https://x.com/rasbtFIRSTMARKWebsite - https://firstmark.comX/Twitter - https://twitter.com/FirstMarkCapMatt Turck (Managing Director)Blog - https://mattturck.comLinkedIn - https://www.linkedin.com/in/turck/X/Twitter - https://twitter.com/mattturck(00:00) - Intro (01:05) - Are the days of Transformers numbered?(14:05) - World models: what they are and why people care(06:01) - Small “recursive” reasoning models (ARC, iterative refinement)(09:45) - What is a diffusion model (for text)?(13:24) - Are we seeing real architecture breakthroughs — or just polishing?(14:04) - MoE + “efficiency tweaks” that actually move the needle(17:26) - “Pre-training isn't dead… it's just boring”(18:03) - 2025's headline shift: RLVR + GRPO (post-training for reasoning)(20:58) - Why RLHF is expensive (reward model + value model)(21:43) - Why GRPO makes RLVR cheaper and more scalable(24:54) - Process Reward Models (PRMs): why grading the steps is hard(28:20) - Can RLVR expand beyond math & coding?(30:27) - Why RL feels “finicky” at scale(32:34) - The practical “tips & tricks” that make GRPO more stable(35:29) - The meta-lesson of 2025: progress = lots of small improvements(38:41) - “Benchmaxxing”: why benchmarks are getting less trustworthy(43:10) - The other big lever: inference-time scaling(47:36) - Tool use: reducing hallucinations by calling external tools(49:57) - The “private data edge” + in-house model training(55:14) - Continual learning: why it's hard (and why it's not 2026)(59:28) - How Sebastian works: reading, coding, learning “from scratch”(01:04:55) - LLM burnout + how he uses models (without replacing himself)

WANTED: Developers and STEM experts! Get paid to create benchmarks and improve AI models. Sign up for Alignerr using our link: https://alignerr.com/?referral-source=briankeating One of the most powerful AI systems we've ever built is succeeding for reasons we still don't understand. And worse, they may succeed for reasons that might lock us into the wrong future for humanity. Today's guest is Anil Ananthaswamy, an award-winning science writer and one of the clearest thinkers on the mathematical foundations of machine learning. In this conversation, we're not just talking about new demos, incremental improvements, or updates on new models being released. We're asking even harder questions: Why does the mathematics of machine learning work at all? How do these models succeed when they suffer from problems like overparameterization and lack of training data? And are large language models revealing deep structure, or are they just producing very convincing illusions and causing us to face an increasingly AI-slop-driven future? KEY TAKEAWAYS 00:00 — Book explores why ML works through math 02:47 — Perceptron proof shows simple math guarantees learning 05:11 — Early AI failed due to single-layer limits 07:12 — Nonlinear limits caused the first AI winter 09:04 — Backpropagation revived neural networks 10:59 — GPUs + big data enabled deep learning 15:25 — AI success risks technological lock-in 17:30 — LLMs lack human-like learning and embodiment 22:57 — High-dimensional spaces power ML behavior 27:36 — Data saturation may slow future gains 31:11 — Continual learning is still missing in AI 33:46 — Neuromorphic chips promise energy efficiency 41:49 — Overparameterized models still generalize well 45:05 — SGD succeeds via randomness in complex landscapes 48:27 — Perceptrons remain the core of modern neural net - Additional resources: Anil's NEW Book "Why Machines Learn: The Elegant Math Behind Modern AI": https://www.amazon.com/Why-Machines-Learn-Elegant-Behind/dp/0593185749 Get My NEW Book: Focus Like a Nobel Prize Winner: https://www.amazon.com/dp/B0FN8DH6SX?ref_=pe_93986420_775043100 Please join my mailing list here

In this AMA-style episode, Nathan takes on listener questions about whether fine-tuning is really on the way out, what emergent misalignment and weird generalization results tell us, and how to think about continual learning. He talks candidly about how he's personally preparing for AGI—from career choices and investing to what resilience steps he has and hasn't taken. The discussion also covers timelines for job disruption, whether UBI becomes inevitable, how to talk to kids and “normal people” about AI, and which safety approaches are most neglected. Sponsors: Blitzy: Blitzy is the autonomous code generation platform that ingests millions of lines of code to accelerate enterprise software development by up to 5x with premium, spec-driven output. Schedule a strategy session with their AI solutions consultants at https://blitzy.com MongoDB: Tired of database limitations and architectures that break when you scale? MongoDB is the database built for developers, by developers—ACID compliant, enterprise-ready, and fluent in AI—so you can start building faster at https://mongodb.com/build Serval: Serval uses AI-powered automations to cut IT help desk tickets by more than 50%, freeing your team from repetitive tasks like password resets and onboarding. Book your free pilot and guarantee 50% help desk automation by week four at https://serval.com/cognitive Tasklet: Tasklet is an AI agent that automates your work 24/7; just describe what you want in plain English and it gets the job done. Try it for free and use code COGREV for 50% off your first month at https://tasklet.ai CHAPTERS: (00:00) Ernie cancer update (04:57) Is fine-tuning dead (Part 1) (12:31) Sponsors: Blitzy | MongoDB (14:57) Is fine-tuning dead (Part 2) (Part 1) (26:56) Sponsors: Serval | Tasklet (29:15) Is fine-tuning dead (Part 2) (Part 2) (29:16) Continual learning cautions (34:59) Talking to normal people (39:30) Personal risk preparation (49:59) Investing around AI safety (01:00:39) Early childhood AI literacy (01:08:55) Work disruption timelines (01:27:58) Nonprofits, need, and UBI (01:34:53) Benchmarks, AGI, and embodiment (01:47:30) AI tooling and platforms (01:57:01) Discourse norms and shaming (02:05:50) Location and safety funding (02:15:17) Turpentine deal and independence (02:24:19) Outro PRODUCED BY: https://aipodcast.ing

https://chusermedia.s3.amazonaws.com/343084912_83689_Continual_Renewal_.mp3 lbtrcsecretary@gmail.com Wed, 21 Jan 2026 00:00:00 MST Wed, 21 Jan 2026 00:00:00 MST Continual Renewal | Pastor DeGarmo | Wednesday Night Liberty Baptist Tabernacle No Continual Renewal | Pastor DeGarmo | Wednesday Night Liberty Baptist Tabernacle lbtrcsecretary@gmail.com

Continual discussion of how to create organic spiritual music in isolation or on the bandstand.

Medium & Messages With Host: #FFFCertifiedMedium Joe Perreta and Guest:FFFCertifiedMedium Connie Fusella Connie Fusella is a Certified Medium with Forever Family Foundation who has had spiritual awareness and experiences since she was a small child. In her early 20's, an allergic reaction to medication led to a near death experience which intensified her intuitive abilities. Continual self-improvement and training enabled her to develop into a credible Evidential Medium. Connie is the Author of 'You are Soul Beautiful: A Unique Perspective into the Soul's Quest for its Destiny.' Bringing You Evidence of An Afterlife Since 2004 Forever Family Foundation is a global 100%volunteer non-profit, non-sectarian organization that supports the premise that life does not end with physical death, furthers the understanding of Afterlife Science and survival of consciousness, and offers support to the bereaved. Among the active members of the organization and the executive board are scientists, researchers, medical doctors, philosophers and educators who have devoted substantial parts of their careers to the investigation of the survival hypothesis - an existence beyond this physical world.

Would you rather stand in the shadow of a house—or step inside where there's shelter and rest? Hebrews chapter 10 draws a sharp line between the shadow of the law and the solid reality of Jesus, and we walk that line with care, clarity, and hope. We unpack why repeated sacrifices could never cleanse the conscience, how Psalm 40 exposes the emptiness of going through the motions, and what it means that Jesus offered one sacrifice and then sat down because the work is finished.We trace a single thread of salvation from Abraham to today: not by keeping the law, not by rituals or badges of obedience, but by faith that God counts as righteousness. Along the way we explore “the good things to come”—Spirit-empowered obedience, joy in God's presence, a clear conscience, and the sure hope of a glorified body in a renewed creation. If you've ever felt the urge to earn your standing with God or drifted into performative religion, this chapter in Hebrews aims your heart back to the new covenant, where love fuels obedience and the Spirit writes God's law within.You'll hear why priests stood daily while Jesus sat down, why “once for all” changes the way we live on Monday, and how “perfected for all time” frees us from anxious striving. We also talk about community and accountability—moving beyond anonymous attendance toward relationships that shape real discipleship. Step out of the shadow. Step into the house. And let the finished work of Christ redefine your past, redirect your habits, and reframe your future.If this encouraged you, follow the show, share it with a friend who needs clarity on grace, and leave a review to help others find the conversation.Support the showThank you for listening!! Please give us a five-star rating to help your podcast provider's algorithm spread RTTB among their listeners. You can find free study and leader resources at the following link - Resource Page - Reasoning Through the Bible Please prayerfully consider supporting RTTB to help us to continue providing content and free resources. You can do that at this link - Support RTTB - Reasoning Through the Bible May God Bless you!! - Glenn and Steve

→ Watch on YouTube → Detailed Show Notes → Timestamps: (00:00) An overview of the The Old Testament.(04:27) Bryce breaks down the Old Testament into nine time periods.(09:41) Canonization and the creation of the Greek Septuagint. The authors of the New Testament quoted the Greek version of the Old Testament. The version that Jesus used is unknown.(13:01) The Old Testament is not one book written by a single author. It is an anthology of books written over centuries by individuals. Later authors sometimes rejected and edited earlier authors. Remnants remain that multiple Gods participated in the creation. The first word in Genesis invites us to consider the Grand Pre-mortal Council.(20:03) The creation accounts address why the world was created, not how. The purpose of the earth is to create eternal families.(33:17) Ancient cultures shared the creation story at their temples during the New Year. The time-honored principle of marriage and family are connected to the purposes of creation.(36:21) Chaos played a role in the formation of the earth. God transformed unorganized matter into something beautiful. The cosmology of the Bible invites modern readers to think about scripture differently.(41:18) The temple takes us to the creation and the creation takes us to the temple because each us back to God.(48:25) Moses 2 and 3 can be read as a single account. This is contrasted with the documentary hypothesis, where scholars believe Genesis 1 and 2 come from two different sources because of differences in the text.(54:21) Seven eternal lessons in the creation account invite us to find success during our time on earth. Finding balance between work and rest.(1:00:29) Seek spiritual things first, then temporal.(1:01:50) Cherubim and a flaming sword foiled Satan's plan and preserved the space between the trees. God protected our probationary estate. God knew from the very beginning that we would sin and need time to repent.(1:13:11) Satan's Plan B is to get us to take away our own or someone else's probationary state. Toxic perfectionism is addressed. Continual progression is what matters to God.(1:16:55) The river flowing out of Eden as a symbol for the division found in mortality. We must find ways to be unified.(1:23:08) Instead of focusing on what we are missing, our focus should be on all our blessings.(1:28:23) Pardes is an acronym to describe the ways of reading scripture: Peshat, remez, derash, and sod. The plain reading (peshat), allegorical or hidden reading (remez), the moral or imperative sense or application (derash), and the mystical, esoteric, or temple reading (sod).(1:30:13) The rib in Genesis 2.22 symbolizes partnership in marriage.(1:38:44) “Helper” or ʿēzer as found in Genesis 2.18 has often been misread and used to subjugate women. The term translated as “help meet” actually denotes the kind of powerful help that God gives. Eve's position next to Adam places both in a setting as having dominion over the whole earth. Eve is called “Zoe” in the LXX, the mother of all the living ones. There is no kingdom without Eve.(1:47:02) Fig leaves can represent covering our sins with bigger and bigger lies.(1:52:47) Garments are a piece of the temple that we wear to remind us of our connection to the Savior's atonement. → For more of Bryce Dunford’s podcast classes, click here. → Enroll in Institute → YouTube → Apple Podcasts → Spotify → Amazon Music → Facebook The post Ep 354 | Genesis 1-2; Moses 2-3; Abraham 4-5, Come Follow Me 2026 (January 12-18) appeared first on LDS Scripture Teachings.

This year-end live show features nine rapid-fire conversations to make sense of AI's 2025 and what might define 2026. PSA for AI builders: Interested in alignment, governance, or AI safety? Learn more about the MATS Summer 2026 Fellowship and submit your name to be notified when applications open: https://matsprogram.org/s26-tcr. Zvi Moshowitz maps the OpenAI–Anthropic–Google race, the denialism gap, and why his PDoom is still ~60–70%. Greg (ARC-AGI Prize), Eugenia Kuyda, Ali Behrouz, Logan Kirkpatrick, and Jungwon Hwang cover sample-efficient benchmarks and ARC-AGI 3, companions and human-flourishing metrics, continual-learning memory, Gemini 3 Flash for developers, and AI for scientific decisions. Sponsors: Gemini 3 in Google AI Studio: Gemini 3 in Google AI Studio lets you build fully functional apps from a simple description—no coding required. Start vibe coding your idea today at https://ai.studio/build MATS: MATS is a fully funded 12-week research program pairing rising talent with top mentors in AI alignment, interpretability, security, and governance. Apply for the next cohort at https://matsprogram.org/s26-tcr Framer: Framer is the all-in-one tool to design, iterate, and publish stunning websites with powerful AI features. Start creating for free and use code COGNITIVE to get one free month of Framer Pro at https://framer.com/design Shopify: Shopify powers millions of businesses worldwide, handling 10% of U.S. e-commerce. With hundreds of templates, AI tools for product descriptions, and seamless marketing campaign creation, it's like having a design studio and marketing team in one. Start your $1/month trial today at https://shopify.com/cognitive Tasklet: Tasklet is an AI agent that automates your work 24/7; just describe what you want in plain English and it gets the job done. Try it for free and use code COGREV for 50% off your first month at https://tasklet.ai CHAPTERS: (00:00) Sponsor: Gemini 3 in Google AI Studio (00:31) Live show experiment (02:26) Zvi: discourse and denial (13:28) Continual learning and doom (22:05) ArcAGI: what's missing (Part 1) (22:09) Sponsors: MATS | Framer (25:28) ArcAGI: what's missing (Part 2) (31:58) Scaffolds and tiny models (38:58) ArcAGI 3 game worlds (45:13) AI companions landscape (Part 1) (45:21) Sponsors: Shopify | Tasklet (48:29) AI companions landscape (Part 2) (58:14) Wabi apps and caution (01:08:16) Nested learning, layered memory (01:23:14) Gemini 3 Flash launch (01:34:09) RAG, agents, dev advice (01:42:20) Elicit speeds evidence synthesis (01:57:57) Outro PRODUCED BY: https://aipodcast.ing

Gemini 3 was a landmark frontier model launch in AI this year — but the story behind its performance isn't just about adding more compute. In this episode, I sit down with Sebastian Bourgeaud, a pre-training lead for Gemini 3 at Google DeepMind and co-author of the seminal RETRO paper. In his first-ever podcast interview, Sebastian takes us inside the lab mindset behind Google's most powerful model — what actually changed, and why the real work today is no longer “training a model,” but building a full system.We unpack the “secret recipe” idea — the notion that big leaps come from better pre-training and better post-training — and use it to explore a deeper shift in the industry: moving from an “infinite data” era to a data-limited regime, where curation, proxies, and measurement matter as much as web-scale volume. Sebastian explains why scaling laws aren't dead, but evolving, why evals have become one of the hardest and most underrated problems (including benchmark contamination), and why frontier research is increasingly a full-stack discipline that spans data, infrastructure, and engineering as much as algorithms.From the intuition behind Deep Think, to the rise (and risks) of synthetic data loops, to the future of long-context and retrieval, this is a technical deep dive into the physics of frontier AI. We also get into continual learning — what it would take for models to keep updating with new knowledge over time, whether via tools, expanding context, or new training paradigms — and what that implies for where foundation models are headed next. If you want a grounded view of pre-training in late 2025 beyond the marketing layer, this conversation is a blueprint.Google DeepMindWebsite - https://deepmind.googleX/Twitter - https://x.com/GoogleDeepMindSebastian BorgeaudLinkedIn - https://www.linkedin.com/in/sebastian-borgeaud-8648a5aa/X/Twitter - https://x.com/borgeaud_sFIRSTMARKWebsite - https://firstmark.comX/Twitter - https://twitter.com/FirstMarkCapMatt Turck (Managing Director)Blog - https://mattturck.comLinkedIn - https://www.linkedin.com/in/turck/X/Twitter - https://twitter.com/mattturck(00:00) – Cold intro: “We're ahead of schedule” + AI is now a system(00:58) – Oriol's “secret recipe”: better pre- + post-training(02:09) – Why AI progress still isn't slowing down(03:04) – Are models actually getting smarter?(04:36) – Two–three years out: what changes first?(06:34) – AI doing AI research: faster, not automated(07:45) – Frontier labs: same playbook or different bets?(10:19) – Post-transformers: will a disruption happen?(10:51) – DeepMind's advantage: research × engineering × infra(12:26) – What a Gemini 3 pre-training lead actually does(13:59) – From Europe to Cambridge to DeepMind(18:06) – Why he left RL for real-world data(20:05) – From Gopher to Chinchilla to RETRO (and why it matters)(20:28) – “Research taste”: integrate or slow everyone down(23:00) – Fixes vs moonshots: how they balance the pipeline(24:37) – Research vs product pressure (and org structure)(26:24) – Gemini 3 under the hood: MoE in plain English(28:30) – Native multimodality: the hidden costs(30:03) – Scaling laws aren't dead (but scale isn't everything)(33:07) – Synthetic data: powerful, dangerous(35:00) – Reasoning traces: what he can't say (and why)(37:18) – Long context + attention: what's next(38:40) – Retrieval vs RAG vs long context(41:49) – The real boss fight: evals (and contamination)(42:28) – Alignment: pre-training vs post-training(43:32) – Deep Think + agents + “vibe coding”(46:34) – Continual learning: updating models over time(49:35) – Advice for researchers + founders(53:35) – “No end in sight” for progress + closing

Drawing from Maslow's hierarchy of needs, this episode breaks down what it truly means to live with integrity, creativity, compassion and authenticity while freeing yourself from the opinions of others. It dives into acceptance, spontaneity, gratitude and purpose as essential practices for growth, emphasizing that self actualization is not a destination but a daily commitment to personal and spiritual evolution. By focusing inward, embracing empathy and maximizing your own potential, this conversation challenges you to live more fully, lead with compassion and show up each day as a better version of yourself. Own your power with this Success Tip.   For more about Rod and his real estate investing journey go to www.rodkhleif.com

Pastor Alan R. Knapp discusses the topic of "SEE: Living by Faith at the Edge of the Eschaton Part Thirteen: Our Continual “Amen”" in his series entitled "Hebrews 2020: We See Jesus" This is Increment 408 and it focuses on the following verses: 2 Corinthians 1:19-22, 5:18-21; Hebrews 11:11-12, 17-19

On a road trip to Montana one summer, we stopped at a rest area to stretch our legs. Inside one of the buildings was a young man who was singing a familiar praise song as he mopped the floor. Then he started singing the hymn, “It Is Well with My Soul.” I couldn’t resist. When he called out the phrase, “It is well,” I repeated it. When he sang, “with my soul,” I echoed the words. Together, we sang the last line: “It is well, it is well . . . with my soul!” He grinned, gave me a fist bump, and said, “Praise God.” When I got back to the car where my husband was waiting, he asked, “What’s with the big smile?” Think of the things for which we can praise God, such as His goodness, righteousness, compassion, promises, provision, and protection. And Psalm 145 is one of many psalms that urges us to continually praise Him. David wrote, “Every day I will praise you” (v. 2). Many people praise God by playing an instrument; others by reading or reciting Scripture; or by singing psalms, hymns, and spiritual songs (Colossians 3:16). Some express their praise through liturgical dance. But all genuine praise springs from hearts that are full of gratitude. Our spirits were designed to praise God. It’s because of His sacrificial love for us that we can say with confidence, “It is well with my soul!”