Podcasts about All Hands

All Hands to Braces (Ben Pease) - June 7, 2026 by Bethany Covenant Church

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

Will Sofrin is a lifelong sailor and the author of the book "USCGC Eagle: The Legacy of America's Tall Ship." The book tells the story of a German naval training ship seized at the end of World War II and transformed into the U.S. Coast Guard's flagship, training generations of officers. Rather than a conventional history, it is told through firsthand accounts from those who sailed her, with each chapter capturing a different decade of the ship's life, from her dramatic 1946 delivery to America, to Cold War voyages behind the Iron Curtain, to surviving a near-loss in a hurricane. He is also the author of the book "All Hands on Deck," a  memoir about sailing the tall ship Rose 5,000 miles from Rhode Island to California so she could become HMS Surprise in the feature film Master and Commander. We talk about sailing a J-70, his book all hands on deck, sailing a tall ship, what all the crew did, maneuvering a tall ship, sails on a tall ship, climbing the mast of a tall ship, tall-ship sailors of old, the book "Two Years Before the Mast," sailing the tall ship Rose from Rhode Island to California for the movie Master and Commander, chain of command on a tall ship, a force 12 storm, going aloft in the storm, freeclimbing rigs, crew dynamics on Rose, sailing upwind in a tall ship, the motion of the boat, ballast on a tall ship, the ship's carpenter, the daily routine, tools, varnishing exterior teak on a sailboat - tips and best practice, his new book "USCG Eagle: The Legacy of America's Tall Ship," Will's dream boat, and more.  Photos and links are on the podcast shownotes page Support the show on Patreon  

On this episode of All Hands on Tech, we sit down with Jonathan Feindel, Partner and Director of Consulting and Business Engineering at CGI. With a strong and growing presence in Halifax, CGI is helping organizations across sectors tackle complex challenges and evolve how they operate through technology.Jonathan shares a behind-the-scenes look at the role consulting plays across industries, what might surprise people about the work, and how teams are solving real-world problems every day. They also dive into one of the biggest challenges facing the industry: talent. From co-op programs to community initiatives, Jonathan talks about why building the tech talent pipeline is critical—and the role companies can play in supporting the next generation.Produced by Unbound Media

On this episode of All Hands on Tech, we sit down with Jennifer Hutton, Vice President of Information, Technology & Risk and Chief Privacy Officer at Steele Auto Group. From its roots as a single Halifax dealership to a multi-region operation with more than 60 locations, Steele Auto's growth story is powered by more tech than you might expect—and Jennifer is right at the centre of it.With over 20 years of experience spanning technology, privacy, and enterprise risk, Jennifer shares a behind-the-scenes look at how tech enables scale in the automotive industry, how leaders balance innovation with responsibility, and what it means to build resilient, adaptable teams in the face of constant change. She also shares her career journey into executive leadership, her perspective on navigating underrepresentation in tech, and what the view looks like from the C-suite.Produced by Unbound Media

Produced by Joseph Cottrell, Wayne Hall, Ken Fuller and Jeffrey Crecelius Kevin is back! He and Mark bang on at length about the recent Oliver Wakeman concert with his band at Worcester, the remastered and expanded From A Page album and the first single from the new Yes album, Aurora. My thanks to everyone who has wished me well, including Brian Breen, Chris Berry and Gary Betts and his wife and most importantly Mark, who has kept the wheels turning at YMP Towers brilliantly. There are also some thoughts from Daniel and Amanda about the new From A Page, especially the inclusion of the song, Aliens and do check out the show notes for a video of our own Geoff Bailie discussing the new Yes single with his Prog Report compatriots. How was the Oliver Wakeman band? What's new about the expanded From A Page? What do we think of the new Yes single? The back entrance to the venue Front entrance Merchandise stall being set up The view from the soundboard Oliver's keyboard rig Drums ready to rock Oliver sighted before the show Oliver in preparation mode Hayley Griffiths Oliver entertaining with stories A raconteur - chip off the old block The set list l-r Scott Higham, Dan Nelson, Oliver Day, Hayley Griffiths, Oliver Wakeman and Arthur Wakeman Oliver signing items for fans https://youtu.be/AlUnYB3u7Nw?si=mpDtpFLwt68hcHgq YES announce 24th studio album  ‘Aurora'; launch video for title track  10th April 2026: YES, who is Steve Howe, Geoff Downes, Jon Davison, Billy Sherwood & Jay Schellen, are proud to announce their 24th studio album ‘Aurora' will be released on the 12th June 2026 via InsideOutMusic/Sony Music.  As Howe explains: “Making this record was joyful, a chance to play, explore and give everything to the music. It's always been about collaboration, somebody can write a song, but until everybody puts their contribution in it isn't really a Yes song. We're not trying to echo the past; we're carrying the spirit of Yes forward and turning it into something new”. The band are also launching the first single from the album, and you can watch the beautiful animated video for the title track, created by Matt Hutchings (Greg Lake, Oasis, Iron Maiden),  here: https://youtu.be/ETEGJTM6plw ‘Aurora' will be available as a Limited Deluxe 180g Light Green 2LP+2CD+Blu-ray Artbook & Poster, as well as a Ltd Deluxe 2CD+Blu-ray Artbook, both featuring the stunning artwork of Roger Dean and Freya Dean, as well as a bonus disc of instrumentals, and a blu-ray featuring Dolby Atmos, 5.1 Surround Sound & 24bit stereo mixes (by Curtis Schwartz). The album is also available as a Gatefold 180g 2LP + LP-booklet, Special Edition CD Digipak & as Digital Album.  Pre-order now here: https://yes-band.lnk.to/Aurora The track listing is as follows: 1. Aurora 07:27 2. Turnaround Situation 05:50 3. Love Lies Dreaming 06:24 4. Countermovement 13:48 5. Ariadne 06:18 6. All Hands on Deck 03:04 7. Outside the Box 04:20 8. Emotional Intelligence 03:30 9. Jambustin' (Bonus Track) 04:24 10. Watching the River Roll (Bonus Track) 04:42 When Yes first began sketching out ideas for what would become ‘Aurora', the process was loose and exploratory. There was no preconceived concept at the start, just a collection of musical fragments that gradually began to find one another and take form. Among these early sketches was a piece titled “Aurora,” and it quickly became clear that the name carried certain gravity. It suggested light, emergence, and a sense of vastness, qualities that resonated deeply with the band. Jon Davison remembers how “the title immediately resonated with Steve Howe and sparked visual inspiration for artist Roger Dean, setting a conceptual tone that would guide the project.” Work on ‘Aurora' began almost as soon as the ‘Classic Tales of Yes' tour ended in 2024. The idea of a new album surfaced quickly and with the label's encouragement, the band had the time to develop material organically. Rather than gathering in a single studio for months, they embraced a modern workflow; ideas were born in home studios, shaped independently, and then woven together through constant collaboration. Downes and Howe often acted as the central creative axis, with Howe, as producer, serving as the point through which all ideas eventually flowed. Across ‘Aurora', each track carries its own character. Some echo the classic Yes approach, others push into new territory, but together they form a cohesive whole that honours the band's heritage while embracing forward motion. With their 24th studio album, Yes demonstrate not just longevity, but a sustained curiosity, a desire to keep exploring, keep refining and keep discovering their capacity to create.    YES is: Steve Howe Geoff Downe Jon Davison Billy Sherwood Jay Schellen YES ONLINE: www.yesworld.com   www.facebook.com/yestheband   www.x.com/yesofficial www.youtube.com/user/yesofficial   www.instagram.com/yesofficial   INSIDEOUTMUSIC ONLINE: www.insideoutmusic.com www.youtube.com/InsideOutMusicTV www.facebook.com/InsideOutMusic www.instagram.com/insideoutmusic/ https://insideoutmusic.bandcamp.com https://youtu.be/ETEGJTM6plw?si=5W21K63dk8qY2qTU Barry Plummer 2026 Calendar is still available! ORDER HERE Apply £11.00 off with the promo code wh4y4pk3 Enrich your Prog year with iconic images of Yes in the 1970s, taken by the legendary rock photographer, Barry Plummer. Enjoy 12 beautiful colour and black and white photographs of Yes in the studio and live, capturing the essence of the world's greatest progressive rock band. With this limited-edition calendar on your wall throughout 2026, you'll agree that Barry Plummer is, indeed, the Master of Images! (A flat shipping fee will be added at checkout depending on your location.) ORDER HERE Yes - The Tormato Story & Tales from Topographic Oceans - Yes Album Listening Guide Available now! YesMusicBooks.com YMP Patrons: Producers: Joseph Cottrell Wayne Hall Ken Fuller Jeffrey Crecelius Patrons: Aaron SteelmanLindAl Dell'AngeloLobate ScarpBarry GorskyMark BaggsBill WhittakerMark James LangBob MartilottaMark SlaterBrian HarrisMartin KjellbergBrian SullivanMichael HanderhanChris BandiniMichael O'ConnorCraig EstenesMiguel FalcãoDave OwenPaul HailesDavidPaul TomeiDavid HeydenRachel HadawayDavid PannellRobert NasirDavid WatkinsonRobert VandiverDeclan LogueRonnie NeeleyDemScott ColomboDoug CurranSimon BarrowFergus CubbageStephen LambeFred BarringerSteve DillGary BettsSteve LuziettiGeoff BailieSteve PerryGeoffrey MasonSteve RodeGuy DeRomeSteve ScottHenrik AntonssonSteven RoehrHogne Bø PettersenTerence SadlerTodd DudleyThomas DeVriesJohn CowanJohn ThomsonJohn HoldenJohn ViolaJamie McQuinnTim StannardDouglas Caldwell Become a Patron!

For this episode of All Hands on Tech, we're celebrating 30 years of impact with an organization that's been helping shape the future of tech in Nova Scotia and beyond.We're joined by Alex Fenton, Executive Director of SuperNOVA — a Dalhousie University initiative dedicated to engaging youth in STEM, innovation and technology education across Atlantic Canada. For three decades, SuperNOVA has been working directly with students, educators and communities to build confidence, spark curiosity and create pathways into tech.From hands-on learning in AI and computer science to reaching rural and underrepresented communities, SuperNOVA offers a unique, on-the-ground perspective of how tech education is evolving — and why early, inclusive exposure is more important than ever.Produced by Unbound Media

In this episode of All Hands on Tech, we're joined by Ingrid Deon, founder of word-craft, an award-winning social media marketing agency specializing in organic social media strategy and content for consumer goods brands.word-craft is known for helping brands find their voice and tell stories that resonate in a digital world where content is everywhere and AI tools are rapidly reshaping how we communicate online.Ingrid returns to the podcast to explore a topic that feels more relevant than ever: authenticity in the age of AI. We discuss how brands can maintain a genuine voice while using AI tools, why storytelling is becoming increasingly valuable in tech and business, and what building trust with audiences looks like in an era of automated content.Produced by Unbound Media

In this episode of All Hands on Tech, we're joined by Samuel Oladimeji, cofounder of Halifax-based consulting firm Vedesi.Vedesi provides change management, branding, IT consulting and web development services, and is also the creator of Dwelleroo — a digital property management platform designed specifically for Atlantic Canadian property managers. Inspired by a personal family experience, Dwelleroo has grown into a comprehensive solution that helps property managers market units, screen tenants, manage maintenance requests and track rent payments all in one place.Sam shares the story behind building software rooted in real-world challenges, what it's like growing a tech company in Halifax, and the journey from consulting to launching a product of your own.Produced by Unbound Media

Acts 19:1-10 - This message recaps the final week of the All Hands on Deck series, using Acts 19 where Paul finds disciples in Ephesus, equips them with the fullness of the gospel, and builds a movement that spreads the Word throughout Asia in two years. It challenges believers to know the church's mission and to live out their faith with intentional disciple-making, not just religious attendance.

This Sunday in Made For This (Week 5: “All Hands on Deck”), we'll dig into Nehemiah 3 and discover why what looks like “just a list of names” is actually a blueprint for how God builds big things: organized work, shared ownership, and every person contributing. We'll be challenged to lead with a servant heart, bring our passion to the mission, and find our place in the work God is doing—because you were never meant to do it alone.

Continuing in Nehemiah, this sermon emphasizes how God accomplishes His work through the collective participation of His people rather than through individual leaders alone. God gives His people both an identity and an assignment, demonstrating that when believers are united in mission, God can accomplish incredible things. The rebuilding of Jerusalem's wall serves as a metaphor for church building today, showing that spiritual fruitfulness comes from God working through His people collectively. The sermon challenges the church to move from a “cruise ship mentality” (consumer-focused) to a “battleship mentality” (mission-focused), emphasizing that every member has a place in God's work regardless of their profession, past, or perceived qualifications.Main Points:God gives His people an identity – The wall provided security, which made Israel's identity as God's people possible. Through Christ, we are adopted as God's children with permanent belonging.Your believed identity determines your lived reality – What you believe about yourself shapes what you do. When we believe we are deeply loved by God, we can deeply love others.God works through His people – The wall was built with an “all-hands-on-deck” mentality. Everyone from perfumers to rulers to daughters participated.The church needs a battleship mentality, not a cruise ship mentality – We're called to ask, “Where can I serve?” rather than “How will this meet my needs?”Scripture Referenced:Nehemiah 3 (main passage); Psalm 127:1; Romans 8:15-16; Leviticus 26:11-12; 2 Timothy 2:3-4Community Group Guide:Begin with PrayerBegin by thanking God for bringing your group together and ask the Holy Spirit to guide your discussion and reveal how He wants to work through each person present.Discussion Questions:Part 1: Understanding Identity (Read Romans 8:15-16)How does understanding your identity as an adopted child of God, able to call Him ‘Abba Father,' change the way you approach daily challenges and relationships?The sermon stated: “Your believed identity determines your lived reality.” Where do you see this principle playing out in your own life? Are there areas where you struggle to believe what God says is true about you?Part 2: All-Hands-on-Deck Mentality (Read Nehemiah 3:8,12 and 3:5)What encourages you about seeing a perfumer and a ruler's daughters working on the wall? What excuses might they have made to avoid this work?In Nehemiah 3:5 the nobles “would not stoop” to do the work. Is there any area of need you've noticed where you've thought, “That's not the kind of work I want to do”? What would it look like to have a different attitude?Part 3: Grounding in Humility (Read 2 Timothy 2:3-4)Be honest: Do you tend more toward a “cruise ship mentality” (consumer mindset) or a “battleship mentality” (mission-focused)? What evidence supports your answer?The sermon mentioned that God often calls us to be faithful “right where we are” before calling us elsewhere. What does faithfulness look like in your current season—in your home, neighborhood, workplace, or church?What barriers (time, fear, insecurity, busyness) keep you from finding your place at the wall? How can this group help you overcome those barriers?Personal Reflection and Practical ApplicationPray daily: Use the phrase “Abba Father” in your prayer time this week, letting the reality of your adoption sink deeply into your heart as you cry out to the One who has called you His own.Encourage: Take time to acknowledge and encourage those you know who are being “faithful right where they are” within the church or our broader community.Identify: If you are currently serving, thank you! Spend some time praying and journaling through all the ways God has been at work in you and through you as you've faithfully stewarded your time and talents. Give Him thanks and ask Him to help you press on. If you are not currently serving, prayerfully ask God where He might desire to use you and take the next faithful step.Worship Setlist:There is a Savior; Cornerstone; Such an Awesome God; Worthy of it All; No Other King

Hebrews 10:24-25 - This message is part of our series called All Hands on Deck. This series will walk us through the culture of Crosswinds by focusing on our seven culture points. message emphasizes that encouragement is vital to the mission of the church—it is an intentional, Spirit-led practice that builds others up, spurs them toward love and good works, and aligns the church as a unified crew on mission for Jesus

The crew is back and covering everything from government shutdown rumors to backlash about the bump serum. Damo gives his two-week review of Charles Johnson's “The Bump Serum,” and the team unveils their “Don't Come to the All Hands” lists. The hosts catch up on life since the last episode and recognize Veterans Day before diving into the latest news on USS Nimitz and the questions surrounding extended deployments—including whether Sailors should get liberty back after standing holiday duty. They discuss the sudden retirement of another 3-Star General, the rumor that 168 commissaries may be closing, and Damo introduces a new segment: “Win for the Week.” The guys also react to the passing of former Vice President Dick Cheney, debate whether MCPON Honea received his due flowers, and unpack retired FLTCM Paul Kingsbury's launch of the National Chief Petty Officer Association. Other topics include counseling Sailors over social media conduct, Damon's Hero of the Week—Staff Sergeant Jared C. Monti, Aaron's perspective on Warrior Ethos, and celebrating five years of Permission to Speak Freely. Damo shows love for Damon and Aaron's picks in the No Limit vs. Cash Money Verzuz, reflects on a couple of movies he watched, and reacts to someone asking whether he uses ChatGPT. The topics and more are covered in this episode.         Do you have a “Do Better” that you want us to review on a future episode? Reach out at ptsfpodcast@gmail.com       Picks of the Week:   The Culture Code (Daniel Coyle) -  https://danielcoyle.com/the-culture-code/       Stay connected with the PTSF Podcast: https://linktr.ee/Ptsfpodcast       PTSF Theme Music: Produced by Lim0

Before you build slides, get crystal clear on who you're speaking to and why you're speaking at all. From internal All-Hands to industry chambers and benkyōkai study groups in Japan, the purpose drives the structure, the tone, and the proof you choose.  What's the real purpose of a business presentation? Your presentation exists to create a specific outcome for a specific audience—choose the outcome first. Whether you need to inform, convince, persuade to action, or entertain enough to keep attention, the purpose becomes your design brief. In 2025's attention-scarce workplace—Tokyo to Sydney to New York—audiences bring "Era of Cynicism" energy, so clarity of intent is non-negotiable. Choose the one primary verb your talk must deliver (inform/convince/persuade/entertain) and align evidence, tone, and timing to that verb for executives, SMEs, and multinationals alike. Use decision criteria (see checklist below) before you touch PowerPoint or Keynote.  Do now: Write "The purpose of this talk is to ___ for ___ by ___." Tape it above your keyboard. How do I define my audience before I write a single slide? Profile the room first; the content follows. Map role seniority (board/C-suite vs. managers), cultural context (Japan vs. US/Europe norms), and decision horizon (today vs. next quarter). In Japan, executives prefer evidence chains and respect for hierarchy; in US tech startups, crisp bottom lines and next steps often win. For internal Town Halls, keep jargon minimal and tie metrics to team impact; for external industry forums, cite research, case studies, and trend lines from recognisable entities (Dale Carnegie, Toyota, Rakuten). Once you know the level, you can calibrate depth, vocabulary, and the "so what" that matters to them. Skip this step and you'll either drown them in detail or sound vague.  Do now: Write three bullets: "They care about…," "They already know…," "They must decide…". Inform, convince, persuade, or entertain—how do I choose? Pick one dominant mode and let the others support it. Inform for internal/industry updates rich in stats, expert opinion, and research (think "Top Five Trends 2025" with case studies). Limit the "data dump"—gold in the main talk, silver/bronze in Q&A. Convince/Impress when credibility is on the line; your delivery quality now represents the whole organisation. Persuade/Inspire when behaviour must change—leaders need this most. Entertain doesn't mean stand-up; it means energy, story beats, and occasional humour you've tested. Across APAC, Europe, and the US, the balance shifts by culture and sector (B2B vs. consumer), but the discipline—one primary purpose—does not.  Do now: Circle the mode that matches your outcome; design every section to serve it. How do I stop the "data dump" and choose the right evidence? Curate like a prosecutor: fewer exhibits, stronger case. Open with a bold answer, then prove it with 2–3 high-leverage data points (trend, benchmark, case). Anchor time ("post-pandemic," "as of 2025") and entities (Nikkei index moves, METI guidance, EU AI Act, industry frameworks) to help AI search and humans connect dots. Keep detailed tables for the appendix or Q&A; in the main flow, show only what advances your single purpose. This approach works for multinationals reporting quarterly KPIs and for SMEs pitching a new budget. Variant phrases (metrics, numbers, stats, proof, evidence) boost retrievability without breaking flow.  Do now: Delete one slide for every two you keep—then rehearse the proof path out loud. How do leaders actually inspire action in 2025? Pair delivery excellence with relevance—then make the ask unmistakable. Inspiration is practical when urgency, consequence, and agency meet. Churchill's seven-word charge—"Never, ever ever ever ever give up"—worked because context (1941 Europe), clarity, and cadence aligned; your 2025 equivalent might be "Ship it safely this sprint" or "Call every lapsed client this week." In Japan's post-2023 labour reforms, tie actions to work-style realities; in US/Europe, link to quarterly OKRs and risk controls. Leaders at firms like Toyota and Rakuten model the ask, specify the first step, and remove friction. Finish with a one-page action checklist and a deadline.  Do now: State the concrete next action, owner, and timebox—then say it again at the close. What's the right design order—openings first or last? Design the closes first (Close #1 and Close #2), build the body, then craft the opening last. The close is the destination; design it before you chart the route. Create two closes: the "time-rich" version and a "compressed" version in case you run short. Build the body to earn those closes with evidence and examples. Only then write your opening—short, audience-hooked, and purpose-aligned. This reverse-engineering avoids rambling intros and ensures your opener previews exactly what you'll deliver. It's a proven workflow for internal All-Hands, marketing spend reviews, and external keynotes alike.  Do now: Write Close #1 and Close #2 in full sentences before touching the first slide. How do I structure my content for AI-driven search engines (SGE, Perplexity, ChatGPT, Copilot)? Lead with answer-first headings, dense entities, and time anchors in each section. Use conversational query subheads ("How do I…?"), open with a bold one-to-two-sentence answer, then a tight paragraph with comparisons (Japan vs. US/Europe), sectors (B2B vs. consumer), and named organisations. End with a mini-summary or "Do now." Keep sections 120–150 words. Add synonyms (metrics/numbers/KPIs) and timeframe tags ("as of 2025"). This GEO pattern boosts retrievability while staying human. Use it for transcripts, blogs, and Do now: Convert your next talk into six answer-first sections using this exact template. Quick checklist (decision criteria) Audience level, culture, and decision horizon defined Single dominant purpose chosen Gold evidence only in-flow; silver/bronze parked for Q&A Two closes drafted; opening written last Clear call-to-action with owner + deadline Conclusion Choose your purpose, curate your proof, and architect your flow backwards from the close. Do that, and you'll inform, convince, and—when needed—inspire action, whether you're presenting in Tokyo, Sydney, or Seattle.    Dr. Greg Story, Ph.D. in Japanese Decision-Making, is President of Dale Carnegie Tokyo Training and Adjunct Professor at Griffith University. He is a two-time winner of the Dale Carnegie "One Carnegie Award" (2018, 2021) and recipient of the Griffith University Business School Outstanding Alumnus Award (2012). A Dale Carnegie Master Trainer, Greg delivers globally across leadership, communication, sales, and presentation programs. He is the author of best-sellers Japan Business Mastery, Japan Sales Mastery, and Japan Presentations Mastery, plus Japan Leadership Mastery and How to Stop Wasting Money on Training; Japanese editions include ザ営業, プレゼンの達人, and 現代版「人を動かす」リーダー. He publishes daily insights and hosts multiple podcasts and YouTube shows for executives succeeding in Japan. 

All Hands on Deck - Pastor Josh Pate by Eastgate Church

David Nothacker, Co-Founder und CEO von sennder, erklärt dir die Herausforderungen beim Aufbau einer effizienten Organisationsstruktur mit 1.000 Mitarbeitern. Er teilt Einblicke in das 13-Level-System, erklärt die Bedeutung regelmäßiger Performance Reviews und warum klare Strategiekommunikation entscheidend ist. Was du lernst: Wie sennder mit 13 Hierarchie-Leveln effizient arbeitet Warum Performance Reviews zweimal jährlich durchgeführt werden Die Bedeutung von regelmäßiger Strategiekommunikation durch All-Hands, Summer Camps und Roadshows ALLES ZU UNICORN BAKERY: https://stan.store/fabiantausch Mehr zu David: LinkedIn: https://www.linkedin.com/in/david-nothacker/  sennder: https://www.sennder.com/de   Join our Founder Tactics Newsletter: 2x die Woche bekommst du die Taktiken der besten Gründer der Welt direkt ins Postfach: https://www.tactics.unicornbakery.de/ 

Leadership is rapidly evolving as artificial intelligence becomes deeply integrated into how organizations operate and make decisions. In a world where volatility, uncertainty, complexity, and ambiguity are the norm, leaders are being challenged to not only understand the role of AI—but also to harness it in ways that enhance what makes leadership truly human. This episode dives into why leaders can no longer afford to treat AI as a separate technical domain, but rather as a strategic partner that augments decision making, stretches creativity, and humanizes leadership itself. As generative AI rapidly advances, the question is not whether leaders should use these tools, but how to do so thoughtfully, ethically, and effectively. This conversation explores how leaders can remain at the center, leverage augmentation, and make deliberate choices that will define competitive advantage and organizational health in the next decade. The episode also emphasizes the necessity of skepticism, risk awareness, and the cultivation of skills—like “human calming”—that will set exceptional leaders apart in an AI-rich world. Timestamped Overview [00:05:27] Introduction to AI and Leadership: Exploring why AI is now essential to leadership development and future success.[00:07:00] The Human Core of Leadership: Discussing the enduring need for human-centered leadership—augmented, not replaced, by technology.[00:08:34] Evolution of Leadership Skills: How classic leadership skills stand the test of time, but require a generative AI lens.[00:09:34] Rethinking “Cyborg Leadership”: Moving beyond science fiction to practical digital augmentation for leaders.[00:11:46] Developing the 10 AI-Augmented Leadership Skills: Why these skills matter and the unique place of “human calming.”[00:15:06] The Role of Human Calming: Centering leaders' intention and composure in an AI-driven world.[00:17:36] The Value of Skepticism: Why questioning, challenging, and stretching assumptions is vital in adopting new technology.[00:19:17] Embracing vs. Rejecting AI: Strategies for experimenting, learning, and building organizational trust with emerging tools.[00:24:00] Facing Risks and Unknowns: Assessing current and future risks—including cyber threats and over-focusing on efficiency.[00:30:03] Effectiveness vs. Efficiency: Shifting the leadership focus toward innovation, not just automation.[00:34:03] All Hands on Deck: Why AI is a human and organizational story—not just a technical one.[00:35:12] Future-Back Thinking: Blending human and machine, and why leaders must choose to play and prototype.[00:39:44] Managing the Noise: How scalable foresight and intentional augmentation can help leaders cut through information overload.[00:43:35] Practical Takeaways: Real-life examples of how leaders can use AI tools to augment creativity and effectiveness.[00:46:22] Embracing Skeptical Foresight: Encouraging leaders to challenge assumptions and stretch their strategic thinking.[00:50:02] Don't Get Discouraged: The learning curve of AI and the importance of hands-on experimentation. For the complete show notes be sure to check out our website: https://leaddontboss.com/357

One of the main things needed to achieve net zero that is to transform how we produce and consume energy. In this podcast, CEOs of three very different companies on the front lines of the energy transition around the world assess where the energy transition is now, and what the future may look like. Speakers: Christian Bruch, CEO, Siemens Energy Andrés Gluski, CEO, AES Corporation Lei Zhang, CEO, Envision Group Co-host: Charles Bourgault manager, electricity industry, World Economic Forum Episode page with transcript: https://www.weforum.org/podcasts/radio-davos/episodes/energy-transition-electrification-siemens-aes-envision Related podcasts: Climate science is clearer than ever. How should companies respond? Getting sustainable, secure and equitable power to the people - how's the global energy transition going? Energy Transition: Amping Up or Powering Down? All Hands on Deck for the Energy Transition Check out all our podcasts on wef.ch/podcasts: YouTube: - https://www.youtube.com/@wef/podcasts Radio Davos - subscribe: https://pod.link/1504682164 Meet the Leader - subscribe: https://pod.link/1534915560 Agenda Dialogues - subscribe: https://pod.link/1574956552 Join the World Economic Forum Podcast Club: https://www.facebook.com/groups/wefpodcastclub

We're kicking off a brand-new sermon collection called Love Island—because sometimes the most toxic thing in your life isn't who you love, but how you've earned to love. In this Welcome Home Sunday message, Pastor Ernest Grant, II opens the All Hands on Deck! collection with a powerful word titled, “It's Giving… Toxic.” Preaching from Judges 16, Pastor Ernest walks through the story of Samson and Delilah—not as a romantic cautionary tale, but as a mirror for our modern relationships.

This week Pastor Ernest Grant II preached a life-changing message from 1 Corinthians 15 in our All Hands on Deck collection. He reminded us that the church doesn't run on personalities, programs, or polish—the power that fuels the church is the gospel. Without it, we drift. With it, lives are changed, hope is restored, and eternity is rewritten.

In this kickoff message from our All Hands on Deck collection, Pastor Ernest Grant, II challenges us to move beyond cruise-ship Christianity and embrace our calling as soldiers on mission. Preaching from 2 Thessalonians 3:1–5, this sermon reminds us that the gospel doesn't move forward through comfort, but through conviction, obedience, and prayer. The mission is urgent, the resistance is real, and eternity is at stake. It's time to suit up, show up, and take our place. The mission is clear—it's all hands on deck.

Send us a textRomas and Ducharme will be sailing together for the first time in 8 years. ALL HANDS!2 ALs 1 Pod is a comedy podcast hosted by stand-up comedians Al Ducharme and Al Romas. Originally titled Talking Dicks Comedy Podcast, the show is a spinoff from their web series The Two Dicks, which features two inept 1950s detectives. The podcast blends observational humor, personal anecdotes, and satirical commentary, often revisiting classic episodes from their archives. With over 345 episodes, it offers a mix of new content and “vault” episodes, providing listeners with a variety of comedic material.  You can listen to 2 ALs 1 Pod on platforms like Spotify, Apple Podcasts, and Buzzsprout. For additional content, including video episodes and behind-the-scenes material, visit their Patreon page. https:/patreon.com/2als1podhttps://www.instagram.com/thetalkingdickscomedypodcast/https://twitter.com/DicksTwohttps://www.facebook.com/thetwodickshttps://www.facebook.com/The-Talking-Dicks-Comedy-Podcast-107101331446404Support the show

A fifth developer beta is out for iPhone, iPad, and Mac, while the new iPhone 17 launch date has leaked, and Apple tells its staff it's serious about AI, on the AppleInsider Podcast.Contact your hosts:@williamgallagher_ on Threads@WGallagher on TwitterWilliam's 58keys on YouTubeWilliam Gallagher on email@hillithreads on Threads@Hillitech on TwitterWes on BlueskyWes Hilliard on emailSponsored by:Oracle: Try Oracle Cloud Infrastructure for free at oracle.com/appleinsiderLinks from the Show:New in iOS 26 beta 5: Camera and Mail toggles, Apple Watch display leak, moremacOS 26 says goodbye to the classic hard drive iconApple has sold 3 billion iPhones since 2007All hands on deck: Tim Cook, Craig Federighi address Apple employees on AI, SiriSiri may get Chat GPT-like search powers driven by a new Apple teamGoogle mocks Apple's AI delays while standing in a graveyard of late and abandoned productsThis time, the iPhone 17 Air battery may have actually been leakediPhone 17 launch date may have been leaked by German wireless carriersApple's existing U.S. manufacturing partners main beneficiaries of new $100B investmentApple's $100 billion investment has almost nothing to do with US iPhone manufacturingApple CEO Tim Cook gifts President Trump gold & glass commemorative plaqueApple exempt from 100% semiconductor tariffs, thanks to its $100B U.S. investmentMade-in-America iPhone not happening anytime soon & Trump seems okay with thatWokyis M5 dock review: Mac Plus looks, M4 Mac mini performanceSupport the show:Support the show on Patreon or Apple Podcasts to get ad-free episodes every week, access to our private Discord channel, and early release of the show! We would also appreciate a 5-star rating and review in Apple PodcastsMore AppleInsider podcastsTune in to our HomeKit Insider podcast covering the latest news, products, apps and everything HomeKit related. Subscribe in Apple Podcasts, Overcast, or just search for HomeKit Insider wherever you get your podcasts.Subscribe and listen to our AppleInsider Daily podcast for the latest Apple news Monday through Friday. You can find it on Apple Podcasts, Overcast, or anywhere you listen to podcasts.Those interested in sponsoring the show can reach out to us at: advertising@appleinsider.com (00:00) - Intro (00:27) - Beta 5 (24:56) - All-Hands meeting (32:37) - Siri Answers (40:50) - Perplexity (51:19) - iPhone 17 launch date (58:49) - Plaque (01:04:51) - Controversy Corner (01:13:19) - Wokyis M5 ★ Support this podcast on Patreon ★

In this episode of All Hands on Decks, AndyR and Boomguy discuss decks that have a musical theme. We dive deep into the songs, the decks, and the cards that make them great!  Here are the decks from the Episode: Justice Silk - https://marvelcdb.com/decklist/view/49727/you-only-get-one-shot-1.0 Spider-Woman - https://marvelcdb.com/decklist/view/47957/spider-woman-tick-tick-boom-1.0 Justice Magik - https://marvelcdb.com/decklist/view/45319/the-sound-of-silence-1.0 Leadership Jubilee - https://marvelcdb.com/decklist/view/45309/jump-around-1.0 'Pool Falcon - https://marvelcdb.com/decklist/view/51168/the-bird-is-the-word-1.0 Aggression Iceman - https://marvelcdb.com/decklist/view/43106/do-you-wanna-build-a-snowman-1.0 Protection Magneto - https://marvelcdb.com/decklist/view/46262/magneto-come-together-right-now-magnetically-1.0 Leadership Ironheart - https://marvelcdb.com/decklist/view/40125/the-beasty-boys-hit-a-stroke-of-genius-1.0 Chapters 00:00 Introduction to Deck Building and Marvel Champions 02:56 Exploring Card Utility and Misunderstood Cards 05:35 Thematic Decks: Musical Inspirations in Marvel Champions 11:42 Deck Showcase: Jump Around - A Jubilee Leadership Deck 17:45 Deck Showcase: Come Together - A Magneto Protection Deck 23:36 Deck Showcase: Tic Tic Boom - A Spider-Woman Aggression Deck 25:42 Iceman's Aggression Deck: Do You Want to Build a Snowman? 33:05 The Sound of Silence: A Justice Magic Deck 40:26 Hit a Stroke of Genius: Leadership with Ironheart 44:00 Deck Strategies and Card Synergies 46:04 Deck Publishing and Community Engagement 48:04 Exploring New Decks and Game Mechanics 54:02 Surprise Deck Reveal and Player Insights 01:02:34 Closing Thoughts and Future Themes

David Nothacker, Co-Founder und CEO von sennder, erklärt dir die Herausforderungen beim Aufbau einer effizienten Organisationsstruktur mit 1.000 Mitarbeitern. Er teilt Einblicke in das 13-Level-System, erklärt die Bedeutung regelmäßiger Performance Reviews und warum klare Strategiekommunikation entscheidend ist. Was du lernst: Wie sennder mit 13 Hierarchie-Leveln effizient arbeitet Warum Performance Reviews zweimal jährlich durchgeführt werden Die Bedeutung von regelmäßiger Strategiekommunikation durch All-Hands, Summer Camps und Roadshows ALLES ZU UNICORN BAKERY: https://zez.am/unicornbakery  Mehr zu David: LinkedIn: https://www.linkedin.com/in/david-nothacker/  sennder: https://www.sennder.com/de   Join our Founder Tactics Newsletter: 2x die Woche bekommst du die Taktiken der besten Gründer der Welt direkt ins Postfach: https://www.tactics.unicornbakery.de/

Today's broadcast is C1E96 for Theme Thursday, June 26th, 2025 (happy 27th "dating" anniversary to my dear wife, St. Jodee). Today's theme is a collection of music from games in my own personal Steam Library – planned, curated, produced, and distributed entirely on/from the Steam Deck (SteamOS desktop mode)! A collection dominated by music from indie games from the 2010's and 2020's and peppered with music from bigger-named games from the 1990's and 2000's and contains not one, but TWO chill zones, which collectively account for almost half of the mixtape runtime! Special thanks to Professor Tom from Shujin Acadamy VGM Club podcast for helping me settle on episode title. Other candidate titles I'd been considering included "Gimme Steam" (which was the working title), "Steam Punk", and "All Hands on Deck". Lastly, this is our debut episode on Terra Player!    SKIP STRAIGHT TO THE MUSIC TIMESTAMP: 00:07:22     Tracklist:     Track# - Track - Game (System is always presumed to be PC for this episode) - Composer(s) - Timestamp     A1) Intro - 00:00:00     01) Main Theme - Mr. Run and Jump - Fat Bard and/or Andrew P. Masson - 00:07:22     02) Blackout City - Bit Trip Runner - Petrified Productions - 00:09:24     03) Solace Tomorrow - ExZodiac - Ben Hickling - 00:12:44     04) Starry Sky - Toree 3D - Nash Music Library - 00:15:51     05) Southisland 2 - Fantavision 202 X - Soichi Terada - 00:18:07     06) Shame (aka “The Shameful Last Minute”) - EDGE - Romain Gauthier - 00:21:16     07) Syreen Theme - Star Control III - Andrew M. Frazier - 00:24:23     08) Analog Control Loop - Formula Retro Racing - John Williams - 00:27:14     09) UFO 50 - UFO 50 - Eirik Suhrke - 00:29:17     10) Hinterwald Dungeon Explore - Dungeons of Hinterberg - David Zahradnicek, and/or Markus Zahradnicek - 00:32:01     11) Control - Cloundpunk - Harry Critchley - 00:35:18     12) Blast Pit 1 - Black Mesa - Joel Nielsen - 00:37:29     13) The Nomai - The Outer Wilds - Andrew Prahlow - 00:39:14     14) Dream Town - Fallout 2 - Mark Morgan - 00:43:01     15) Earth - Lords of Magic - Keith Zizza - 00:46:12     16) grip - qomp - Britt Brady - 00:50:14     17) Returning the Flavour - Olli Olli World - Potatohead People - 00:52:45     18) Portabellahead - Crypt of the Necrodancer - Danny Baronowsky - 00:55:43     19) Delirious Acting - Pseudoregalia - potatoTero - 00:58:29     20) Relentless - Gunborg - Cato Hoeben - 01:00:27     21) Kurodabushi - Koi Koi Japan Hanafuda - Unknown - 01:03:21     22) Security Bridge - System Shock Classic - Greg LoPiccolo and/or Tim Ries - 01:04:50     23) Battle - Caveblazers - Paul Zimmerman - 01:08:02     24) Salt and Sepulcher - The Mummy Demastered - monomer - 01:09:55     25) Main Theme - Blade Assault - Planetboom and/or Creative Factory - 01:12:10     26) Main Theme - Fury Unleashed - Adam Skorupa and/or Krzysztof Wierzynkiewicz - 01:15:08     27) Witness Prevention Program - Killing Floor - Zynthetic - 01:17:21     28) The Audience Chamber - Elder Scrolls Arena - Eric Heberling - 01:20:08     29) Trademeet - Baldur's Gate II - Michael Hoenig - 01:21:46     30) Wayward Dreamers - Dreams of Aether - flashy goodness - 01:22:39     31) Save Room - Gato Roboto - Britt Brady - 01:25:30     32) Equanimity - Lucid9 - Breezee - 01:27:14     33) Pillar Gardens - In Other Waters - Amos Roddy - 01:31:40     34) Completely Safe - Deliver Us Mars - Sander Van Zanten - 01:36:02     35) Karst Pass - Even the Ocean - Melos Han-Tani - 01:39:34     36) Title Screen - Cubot - Kevin MacLeod - 01:44:33     37) Splash of Color - Flower - Vincent Diamante - 01:49:45     38) Beast Road - Touhou Mystia's Izakaya - Hannari and/or Can Shi - 01:58:56     39) Pra Me Lembrar Amanha - Before I Forget - Dave Tucker - 02:02:31     40) Candy Store Crush - Donut Dodo - Sean Bialo - 02:05:04     41) Toastopia - Pikuniku - Calem Bowen - 02:07:22     42) April Mountains - Lovely Planet 2: April Skies - Calem Bowen - 02:10:17     43) Clouds - Nidhogg - Daedalus - 02:12:47     44) Home - Retrowave - Resonance - 02:15:20     45) Battle Theme - Void Invaders - kingdaro - 02:18:43     B1) Outro - 02:21:58     Music Block Runtime: 02:14:43 / Total Episode Runtime: 02:34:01    Our Intro and Outro Music is Funky Radio, from Jet Grind Radio on the Sega Dreamcast, composed by BB Rights.    Produced using a nearly equal mix of Audacity and Ardour in SteamOS desktop mode on the Steam Deck! Recorded with a Shure SM7B XLR dynamic microphone on a RØDE PSA1+ boom arm through a Cloudlifter and a Focusrite 4i4 XLR-to-USB interface!    If you aren't already a listener of Shujin Acadamy VGM Club, please go show the good professor some love, and tell him St. John sent ya! You can find Shujin Acadamy on Terra Player, Instagram, Threads, Bluesky, Facebook, Mastodon, Podbean, or on your podcatcher of choice. Here's a link to his show on Terra Player and on Podbean:    https://terraplayer.com/shows/shujin-academy-vgm-club    https://shujinacademyvgmclub.podbean.com/    Speaking of Terra Player, we are now a member podcast as well. You can find us there at  https://terraplayer.com/shows/nerd-noise-radio. Also, check out their outstanding collection of other podcasts and radio stations at https://terraplayer.com/! From now on, when sharing episodes of Nerd Noise Radio, I will most likely use the Terra Player link rather than the Podbean link like I have been using.    You can also find all of our audio episodes on https://archive.org/details/@nerd_noise_radio as well as the occasional additional release only available there, such as remixes of previous releases and other content.    Our YouTube Channel, for the time being is in dormancy, but will be returning with content, hopefully, in 2022. Meanwhile, all the old stuff is still there, and can be found here:     https://www.youtube.com/user/NerdNoiseRadio    Occasional blogs and sometimes expanded show notes can be found here:    nerdnoiseradio.blogspot.com.    Nerd Noise Radio is also a member of the VGM Podcast Fans community at     https://www.facebook.com/groups/VGMPodcastFans/    We are also a member of Podcasters of Des Moines at https://www.facebook.com/groups/1782895868426870/    Or, if you wish to connect with us directly, we have two groups of our own:     Nerd Noise Radio - Easy Mode: https://www.facebook.com/groups/276843385859797/ for sharing tracks, video game news, or just general videogame fandom.    Nerd Noise Radio - Expert Mode: https://www.facebook.com/groups/381475162016534/ for going deep into video game sound hardware, composer info, and/or music theory.    Or you can reach us by e-mail at nerd.noise.radio@gmail.com    You can also follow us on Threads at https://www.threads.net/@nerdnoiseradio , Instagram at https://www.instagram.com/nerdnoiseradio?igsh=MWF4NjBpdGVxazUxYw== , Mastodon at https://universeodon.com/@NerdNoiseRadio , and BlueSky at  And we are also now on TuneIn, Pandora, iHeartRadio, Vurbl, Amazon Music and Audible!     But frankly, probably the absolute best way you can connect with us is on our new Discord Channel: "Nerd Noise Radio – Channel D", which includes various sub-channels for all sorts of different types of connection and conversation:     https://discord.gg/GUWdaXUw    Thanks for listening! Join us again in July for C1E97 (Channel 1, Episode 97): the Super Metroid soundtrack, part of a collaboration with Shujin Academy VGM Club, The Messenger Presents: A VGM Journey, and any other shows which wish to join us in lieu of an official Masters of VGM event this year - Delicious VGM on "Noise from the Hearts of Nerds"! And wherever you are - Fly the N!    Cheers! 

The IRS Rule That Could Save Your Early Retirement (No, Seriously)Burned out? Laid off? Can't sit through one more “All Hands” meeting where Todd from Accounting performs a spoken word about synergy? Honey, maybe it's time to retire early—even if you didn't plan to.This week on Queer Money®, we're spilling the retirement tea

In this episode of All Hands on Decks, Boomguy and Andyr discuss their experiences at the recent Marvel Champions con, focusing on the evolving trends in deck building, the impact of new cards, and the dynamics of multiplayer gameplay. They explore the noticeable decline in player side schemes, the underrepresentation of certain heroes like Nick Fury and Maria Hill, and the importance of damage output in multiplayer settings. The conversation also touches on the absence of team up cards and how players are adapting their strategies to enhance deck consistency and effectiveness. In this episode, the hosts delve into various Marvel Champions decks showcased at a recent convention, highlighting innovative strategies and community engagement. They discuss the clever use of Enhanced Awareness in resource management, the effectiveness of the Nightcrawler Injustice deck, and the unique playstyle of the Wildcard Iron Man deck. The conversation also explores a Colossus defense deck that emphasizes protection and the excitement of discovering new archetypes like alter ego only decks. The hosts celebrate the creativity of the community and encourage players to share their unique deck builds. Here are the decks we discussed: Phoenix Leadership (SDx) https://marvelcdb.com/decklist/view/49481/phoenix-soul-queens-are-here-to-slay-your-side-schemes-1.0 Nick Aggression (LazyTitan) https://marvelcdb.com/decklist/view/49689/overkill-em-1.0 Scarlet Witch Basic (Astrodar) https://marvelcdb.com/decklist/view/49375/witch-doctor-1.0 Nova Leadership (TheDailyStrugle) https://marvelcdb.com/decklist/view/48382/sam-s-lan-party-1.0 Justice Ms. Marvel - Spike https://marvelcdb.com/decklist/view/48069/3-4-player-burst-thwart-unthreatened-team-is-a-happy-team-1.0 Justice Tony Stark - Johnny https://marvelcdb.com/decklist/view/49445/tony-stark-director-of-s-h-i-e-l-d-1.0 Colossus Protection - Johnny https://marvelcdb.com/decklist/view/49334/nyet-1.0 Gambit Protection - Timmy https://marvelcdb.com/decklist/view/49305/fortune-favors-the-shy-coh25-3.0 Ghost-Spider Leadership - Johnny https://marvelcdb.com/decklist/view/44333/started-my-own-band-with-a-few-old-friends-you-want-in-1.0   Chapters 00:00 Post-Con Reflections and Deck Trends 02:53 Player Side Schemes: A Shift in Strategy 05:49 The Role of Allies: Nick Fury and Maria Hill 08:56 Deck Consistency and Gameplay Dynamics 11:46 The Evolution of Deck Building: Beyond Aspects 14:49 Team Up Cards: Missed Opportunities 17:45 Support Decks and Command Team Strategies 20:49 Voltron Strategies and Standout Decks 28:20 Deck Consistency and Trends 30:14 The Importance of Damage in Multiplayer 35:53 Underrepresented Heroes at the Con 39:01 Innovative Deck Strategies 48:22 The Alter Ego Iron Man Deck 55:33 Colossus: A Defense Deck for the Table 59:48 Deck Building Insights 01:00:15 Exploring Other Players' Decks 01:01:11 The Basic Witch Deck Breakdown 01:04:04 Overkillem: A Damage-Focused Deck 01:08:23 The Shy Deck: A New Legend Emerges 01:13:42 Nova Leadership: Ally Heavy Strategy 01:18:32 Ms. Marvel Justice: Thwarting Everything

Hi, and welcome to The Long View. I'm Dan Lefkovitz, strategist for Morningstar Indexes. Our guest this week is Arunma Oteh, currently of the University of Oxford Saïd Business School. Arunma is a former treasurer of the World Bank and also served in various leadership roles in the African Development Bank. In 2010, she became Director General of Nigeria Securities and Exchange Commission, and she led that apex regulator for several years following the global financial crisis. She writes about the experience in the recently published book All Hands on Deck: Unleash Prosperity Through World Class Capital Markets. Arunma is a graduate of the University of Nigeria, UNN Nsukka, and Harvard Business School.BackgroundBioAll Hands on Deck: Unleash Prosperity Through World Class Capital MarketsNigeria's “Iron Lady”“Nigeria's Iron Lady Takes on Fraudsters,” by Caroline Duffield, bbc.com, July 1, 2010.“Changing the World One Bond at a Time,” Rita Stankeviciute and Kathleen Manahan, worldbank.org, July 18, 2018.“Nigeria SEC Boss, Arunma Oteh, Fights Back,” YouTube video, March 15, 2012.OtherSecurities and Exchange Commission, NigeriaNigerian Exchange Group NGXFMDQ Group“A Tale of 2 Exchanges: As FMDQ Thrives NGX Plays Catch Up,” by Bala Augie, moneycentral.com, Oct. 2, 2021.

All Hands on Dick, oops we mean deck! Between Brandon’s balls, Steve’s coxswain, and Dick’s big boat…this episode goes from nautical to naughty real fast! Aside from the usual adultery and drama, Tori talks about the cast member with major ALPHA energy, and Jennie reveals the former co-star who wore a Winnie the Pooh onesie to work. Plus, the roommate who is done with Dick (Harrison) once and for all! Don’t say we didn't warn you!See omnystudio.com/listener for privacy information.

Vibe coding, agentic workflows, and AI-assisted pull requests? In this episode, Daniel and Chris chat with Robert Brennan and Graham Neubig of All Hands AI about how AI is transforming software development—from senior engineer productivity to open source agents that address GitHub issues. They dive into trust, tooling, collaboration, and what it means to build software in the era of AI agents. Whether you're coding from your laptop or your phone on a morning walk, the future is hands-free (and All Hands).Featuring:Robert Brennan – LinkedIn, XGraham Neubig – LinkedIn, XChris Benson – Website, GitHub, LinkedIn, XDaniel Whitenack – Website, GitHub, XLinks:All HandsAll Hands on GitHubAll Hands on Hugging Face 

What if the real reason your team isn't thriving isn't them—it's you? In this episode, Ashok sits down with Sel Watts, founder of Wattsnext and a trusted advisor to growth-stage executives, to talk about the blind spots that derail team performance. Sel shares why leaders often overengineer HR systems while neglecting the basic needs of their people—and why getting back to the fundamentals starts with brutal self-honesty. They explore why traditional job descriptions are outdated, how to rethink role clarity using "outcome profiles," and why consistency beats charisma when it comes to leadership. Sel also shares candid stories from the field—including one about a CEO who had zero emotional intelligence but ran a surprisingly stable company—and explains how tools like behavioral profiling can be powerful when used correctly (and not just shelved after a team offsite). Inside the episode Why leadership starts with self-awareness, not structure The “outcome profile” approach to defining roles clearly How to tell if someone's actually underperforming—or just misaligned What happens when leaders care more about process than people The surprising upsides of being consistent, even if you're not "warm" Why behavioral profiling tools are often wasted One-on-ones, All Hands, and rituals that only work when leaders believe in them Rethinking hiring decisions by starting with the org chart, not the title The cost of skipping reflection before replacing a team member A real-world example of a team where mutual accountability actually works   Mentioned in this episode Wattsnextpx - https://www.wattsnextpx.com Extended DISC - https://www.extendeddisc.org/ AcuMax - https://www.acumaxindex.com/ Myers-Briggs - https://www.themyersbriggs.com/en-US/Products-and-Services/Myers-Briggs Predictive Index - https://www.predictiveindex.com/ Entrepreneurs' Organisation (EO) - https://eonetwork.org/ Unlock the full potential of your product team with Integral's player coaches, experts in lean, human-centered design. Visit integral.io/convergence for a free Product Success Lab workshop to gain clarity and confidence in tackling any product design or engineering challenge. Subscribe to the Convergence podcast wherever you get podcasts including video episodes to get updated on the other crucial conversations that we'll post on YouTube at youtube.com/@convergencefmpodcast Learn something? Give us a 5 star review and like the podcast on YouTube. It's how we grow.   Follow the Pod Linkedin: https://www.linkedin.com/company/convergence-podcast/ X: https://twitter.com/podconvergence Instagram: @podconvergence

In this episode of Alter Everything, we talk with Ian Barkin and Tom Davenport, authors of 'All Hands On Tech: The AI-Powered Citizen Revolution.' They discuss their motivations for writing the book, the emerging role of citizen developers, and the democratization of data science and AI. Themes include the evolution of low-code/no-code tools, the importance of governance in deploying AI, and future implications of generative AI in citizen development. Listeners are encouraged to register for the Alteryx Inspire 2025 conference and can access free chapters of the book via the show's website.Panelists:Tom Davenport, Distinguished Professor @ Babson College - LinkedInIan Barkin, Founding Partner @ 2BVentures - LinkedInMegan Bowers, Sr. Content Manager @ Alteryx - @MeganBowers, LinkedInShow notes: Two FREE chapters of All Hands on Tech: The AI-Powered Citizen RevolutionAll Hands on Tech: The AI-Powered Citizen Revolution Full BookInspire breakout session catalog Interested in sharing your feedback with the Alter Everything team? Take our feedback survey here!This episode was produced by Megan Bowers, Mike Cusic, and Matt Rotundo. Special thanks to Andy Uttley for the theme music and Mike Cusic for the for our album artwork.

All Hands on Deck. Punk Rock Factory guitar nerds, silly sausages and viral TikTok stars, Peej Edwards and Ryan Steadman, are our guests on Episode 330 of Sappenin' Podcast! Your algorithms favourite covers band, invited us into their studio, to unleash exclusive secrets on their Disney vs Emo structure, industry loopholes and why this isn't just some gimmick. In this conversation, Peej and Steadman open up on their unique formula of transforming film soundtracks, pop anthems and the most random hits of yesteryear, internet backlash vs building a community, how this project started, coming from individual backgrounds in South Wales 2000's metal bands, helping families bound over music, live show madness, finding the original Milky Way kid, having the ultimate praise from Bowling For Soup, Papa Roach and B*Witched, weird magazine posters, scene jealousy, embracing their meme attitude, the best TV themes, Moana mosh pits, calling out The Rock and more! Turn it up and join Sean and Morgan to find out Sappenin' this week!Follow us on Social Media:Twitter: @sappeninpodInstagram: @sappeninpodSpecial thank you to our Sappenin' Podcast Patreons:Join the Sappenin' Podcast Community: Patreon.com/Sappenin.Kylie Wheeler, Janelle Caston, Paul Hirschfield, Tony Michael, Scarlet Charlton, Dilly Grimwood, Mitch Perry, Nathan Crawshaw, Molly Molloy, James Bowerbank, Amee Louise, Kat Bessant, Kieran Lewis, Alexandra Pemblington, Jonathan Gutierrez, Jenni Robinson, Stuart McNaught, Jenni Munster, Louis Cook, Carl Pendlebury, James Mcnaught, Martina McManus, Jason Heredia, John&Emma, Danny Eaton, RahRah James, Sian Foynes, Evan, Ollie Amesbury, Dan Peregreen, Emily Perry, Kalila Keane, Adam Parslow, Josh Crisp, Vicki Henshaw, Laura Russell, Fraser Cummings, Sophie Ansell, Kyle Smith, Connor Lewins, Billy Hunter, Harry Radford, George Evans, Em Evans Roberts, Thomas O'Neill, Sinead O'Halloran, Kael Braham, Jade Austin, Charlie Wood, Aurora Winchester, Jordan Harris, James Page, Georgie Hopkinson, Helen Anyetta, John Wilson, Lisa Sullivan, Ayla Emo, Kelly Young, Jennifer Dean, Tj Ambler-Shattock, Chaz Howkins, Michael Snowden, Justine Baddeley, David Winchurch, Jim Farrell, Scott Evans, Andrew Simpson, Shaun Croucher, Lewis Sluman, Ellie Gowers, Luke Wardle, Grazyna McGroarty, Nathan Matheson, Matt Roberts, Joshua Lewis, Erin Howard,, Chris Harris, Lucy Neill, Amy Thomas, Jessie Hellier, Stevie Burke, Robert Pike, Anthony Matthews, Samantha Neville, Sarah Maher, Owen Davies, Bethan Downing, Jessica Tiernan, Danielle Oldershaw, Samantha Bowen, Ruby Price, Jule Ferl, Alice Wood, Billy Parmiter, Emma Musgrave, Rhian Friggens, Hannah Kenyon, Patrick Floyd, Hayley Taylor, Loz Sanchez, Cerys Andrews, Dan Johnson, Eva B, Emma Barber, Helen Macbeth, Melissa Mercury, Joshua Ryan, Cate Stevenson, Emily Moorhouse, Jacob Turner, Madeleine Inez, Robert Byrne, Christopher Goldring, Chris Lincoln, Beth Gayler, Lesley Dargie-Walker, Sabina Grosch, Tom Hylands, Andrew Keech, Kerry Beckett, Leanne Gerrard, Ieuan Wheeler, Hannah Rachael, Gemma Graham, Andy Wastell, Jay Smith, Nuala Clark, Liam Connolly, Lavender Martin, Lloyd Pinder, Ghostly Grimoire, Amy Hogg.Diolch and Thank You x Get bonus content on Patreon Hosted on Acast. See acast.com/privacy for more information.

Get featured on the show by leaving us a Voice Mail: https://bit.ly/MIPVM FULL SHOW NOTES https://www.microsoftinnovationpodcast.com/665 Stevie Sims shares his journey from chemical plant operator to lead Power Platform developer at Shell, demonstrating how business expertise combined with low-code tools can transform organizations.TAKEAWAYS• Started career in operations, climbing towers and turning valves before discovering Excel• Hurricane Ida became a pivotal moment when he built a Power BI dashboard to manage recovery• Transitioned from citizen developer to fusion team member building complex apps and automations• Believes companies should encourage operational experts to upskill with technical tools• Emphasizes the importance of business knowledge when developing technical solutions• Advocates for "ring-fencing" talented citizen developers for focused development periods• Prevents duplicate development efforts through idea triage and solution sharing• Featured in new book "All Hands on Tech: AI-Powered Citizen Developer Revolution"Check out "All Hands on Tech" by Ian Barkin and Tom Davenport, featuring Steve's story and other inspiring examples from the low-code no-code space.This year we're adding a new show to our line up - The AI Advantage. We'll discuss the skills you need to thrive in an AI-enabled world. DynamicsMinds is a world-class event in Slovenia that brings together Microsoft product managers, industry leaders, and dedicated users to explore the latest in Microsoft Dynamics 365, the Power Platform, and Copilot.Early bird tickets are on sale now and listeners of the Microsoft Innovation Podcast get 10% off with the code MIPVIP144bff https://www.dynamicsminds.com/register/?voucher=MIPVIP144bff Accelerate your Microsoft career with the 90 Day Mentoring Challenge We've helped 1,300+ people across 70+ countries establish successful careers in the Microsoft Power Platform and Dynamics 365 ecosystem.Benefit from expert guidance, a supportive community, and a clear career roadmap. A lot can change in 90 days, get started today!Support the showIf you want to get in touch with me, you can message me here on Linkedin.Thanks for listening

Today on BOLD STEPS, Pastor Mark Jobe reveals what happens when persistent faith meets creative problem-solving. We’re continuing our series called All Hands on Deck with a powerful lesson about persistence and creative faith. It's a story about four friends who were so determined to get their paralyzed companion to Jesus, that they wouldn't take no for an answer … even when a crowd of religious leaders stood in their way. What happened next would not only change their friend's life forever but also teaches us an unforgettable lesson about what it means to truly bring others into God's presence. Bold Step Gift: Building Love In Blended FamiliesBecome a Bold Partner: http://moodyradio.org/donateto/boldsteps/partnersSee omnystudio.com/listener for privacy information.

Today on BOLD STEPS, Pastor Mark Jobe has a wakeup call for believers, to be on the lookout for God’s movement. We’re beginning a new short series about a really powerful subject … joining the movement of God. There are special moments in our lives when God makes it clear that it's time to move … time to act. In Scripture there's this powerful concept called "kairos" – it's a Greek word that describes a specific moment in time when God is doing something unique. It's not just another day on the calendar ... it's a divine appointment. And it calls for All Hands on Deck. Bold Step Gift: Building Love In Blended FamiliesBecome a Bold Partner: http://moodyradio.org/donateto/boldsteps/partnersSee omnystudio.com/listener for privacy information.

The guys sit down and have a chat about the busy winter, and anything else that comes to mind...Music Credit: Rev Theory

In this episode of All Hands on Decks, Boomguy and Andy R discuss two decks from Marvel CDB, focusing on a Domino leadership deck and a Friendly Neighborhood Spider-Man deck. They explore the mechanics, strategies, and potential improvements for each deck, emphasizing the importance of deck themes and player experience. We also highlight the fun and complexity of deck building in Marvel CDB, while also teasing future episodes where they will build their own decks together. How come I'm the only one popping my posse up in here: https://marvelcdb.com/decklist/view/45547/how-come-i-m-the-only-one-popping-my-posse-up-in-here-1.0 Friendly Neighborhood Spider-Man: https://marvelcdb.com/decklist/view/45545/friendly-neighborhood-spider-man-1.0 Chapters 00:00 Introduction and Deck Themes 04:49 Reviewing the Domino Leadership Deck 12:58 Exploring the Friendly Neighborhood Spider-Man Deck 27:02 Conclusion and Future Deck Building Plans

Wed, 29 Jan 2025 18:00:00 GMT http://relay.fm/clockwise/590 http://relay.fm/clockwise/590 All Hands on Face 590 Dan Moren and Mikah Sargent The how often we use our non-default smartphone cameras, the tech or techniques we use to stay focused at work, where we buy and read ebooks and whether supporting indie bookstores appeals to us, and our least favorite thing to troubleshoot. The how often we use our non-default smartphone cameras, the tech or techniques we use to stay focused at work, where we buy and read ebooks and whether supporting indie bookstores appeals to us, and our least favorite thing to troubleshoot. clean 1799 The how often we use our non-default smartphone cameras, the tech or techniques we use to stay focused at work, where we buy and read ebooks and whether supporting indie bookstores appeals to us, and our least favorite thing to troubleshoot. This episode of Clockwise is sponsored by: Vitally: A new era for customer success productivity. Get a free pair of AirPods Pro when you book a qualified meeting. Guest Starring: mb bischoff and Jason Howell Links and Show Notes: Support Clockwise with a Relay FM Membership

In this episode of All Hands on Decks, Boomguy and Andyr delve into the world of deck building in Marvel Champions with Reddit-submitted decks. They explore the Chitinous Wasp deck, discussing its strategies and card choices, before moving on to the Ant in the Pool deck, which emphasizes resource management and Pool synergy. We also discuss the limitations of the 'Pool aspect in deck-building and the challenges it presents. Chitinous Wasp: https://marvelcdb.com/decklist/view/44949/chitinous-wasp-1.0 Ant in the Pool: https://marvelcdb.com/decklist/view/45051/ant-in-the-pool-1.0 Chapters 00:00 Introduction to Deck Building and Community Engagement 03:01 Exploring the Chitinous Wasp Deck 11:53 Analyzing the Ant-Man Deck 23:58 Discussion on Pool Limitations and Deck Strategies 31:54 Conclusion and Final Thoughts

TVC 674.3: Pat Boone talks to Ed about working with Shirley Jones in April Love, with Ann-Margret in State Fair, and with Barbara Eden in All Hands on Deck. Pat can currently be seen in Reagan and Miracle in the Valley, both of which are available now for viewing on demand through Amazon Prime, while Pat's latest movies, Our Crossroads and The American Miracle, are both scheduled for release later in 2025.

In this episode of All Hands on Deck, Boomguy and Andyr discuss the Impede card, its effectiveness, and its place in various deck archetypes. They break down two specific decks featuring Ms. Marvel, exploring their strategies and synergies. The conversation also touches on the importance of deck building for new players and the potential for collaborative gameplay videos in the future. Here is the Impede deck that started this conversation: https://marvelcdb.com/decklist/view/45086/doctor-icelove-3.0 Andy's Deck: https://marvelcdb.com/decklist/view/41703/ms-marvel-thwarts-and-all-1.0 Boomguy's Deck: https://marvelcdb.com/decklist/view/36600/n00b-support-system-1.0 This deck is meant to work together with this deck: https://marvelcdb.com/decklist/view/36599/learning-to-crawl-1.0 Chapters 00:00 Introduction and Overview of Impede 02:03 Deep Dive into Impede's Effectiveness 05:03 Deck Breakdown: Ms. Marvel Thwarts and All 07:59 Deck Breakdown: Noob Support System 10:55 Comparative Analysis of Decks 14:08 Final Thoughts and Future Plans  

All Hands on Decks is a series featuring Andyr that discusses community decks that we think deserve to be seen. We will discuss the decks, and categorize them into the Johnny-Timmy-Spike archetypes so that others can find decks they might enjoy, depending on the type of player they are.  Link to Spike, Johnny, and Timmy: https://magic.wizards.com/en/news/making-magic/timmy-johnny-and-spike-2013-12-03 In this episode of the our mini-series, Boomguy and Andy explore two unique decks in the Marvel Champions game. The first deck, 'Drax Tank and Spank with Mantis Sidekick Healer,' focuses on utilizing Drax's strengths alongside Mantis as a sidekick healer. The second deck, 'Wasp and Ant-Man with a Great Equalizer,' aims to enhance Wasp's capabilities by leveraging Ant-Man's potential through various attachments and strategies. The hosts discuss the strengths and weaknesses of each deck, categorize them based on player archetypes, and share insights on deck building and gameplay strategies. Drank "Tank and Spank" with Mantis Sidekick Healer: https://marvelcdb.com/decklist/view/38888/drax-tank-and-spank-with-mantis-sidekick-healer-1.0 Wasp and Ant-Man with a Great Equalizer (fixed): https://marvelcdb.com/decklist/view/44671/wasp-and-ant-man-with-a-great-equalizer-fixed-1.0 Chapters 00:00 Introduction 02:08 Exploring Drax Tank and Spank Deck 09:45 Reviewing Wasp and Ant-Man Deck 25:59 Conclusion and Future Deck Suggestions

In episode 103, Camille breaks down her time in North Carolina and her volunteer work with the organization "All Hands and All Hearts" in the recovery efforts from Hurricane Helene that she started back in October. Six states were hit by this hurricane, with North Carolina being one of, if not the, hardest hit. Unexpectedly hard hit. If you are a new listener to Camille's podcasts, this is a big story, and you may want to start at the beginning with episodes 101 and 102 for more background and what led Camille to wanting to do this. If you are a returning guest, while it has taken a little longer for this episode to happen, you will not be disappointed by the wait. It's exciting, emotional, informative, and so relatable. This is a mostly freeform episode, and Camille will be sharing her most valuable insights, key points, tips, resources, experiences, and how remote work fits in. During this time, she got sick, did a lot of physical labor, met great people, formed friendships, and she even has a surprise to reveal. So, kick back, relax, and listen to what turned out to be a lifechanging experience for our Camille Attell.Here is Camille's direct link for All Hands and All Hearts, the organization she will be working with, and she talks about in this episode. All donations will go directly to them. Please feel free to share.https://give.allhandsandhearts.org/camilleClick here to read the show notes for this episode:https://www.camilleattell.com/blog/101You can also take her FREE training at:www.camilleattell.com/remote-trainingIf you want to learn more about how to leverage your digital products or service visit:www.camilleattell.com/remoteworkschool Connect with Camille on Instagram: @camille.attellConnect with Camille on Linkedin: Camille Attell, MARead more about the RV and Remote Work Lifestyle at https://www.morethanawheelin.com/

All Hands on Decks is a series featuring Andyr that discusses community decks that we think deserve to be seen. We will discuss the decks, and categorize them into the Johnny-Timmy-Spike archetypes so that others can find decks they might enjoy, depending on the type of player they are.  Link to Spike, Johnny, and Timmy: https://magic.wizards.com/en/news/making-magic/timmy-johnny-and-spike-2013-12-03 In this episode of All Hands on Decks, Boomguy and Andyr explore community decks centered around the leadership ally Beta Ray Bill. They discuss various deck-building strategies, player archetypes, and analyze specific decks, including one from The Masked Hero and another featuring Valkyrie. The conversation emphasizes the importance of community engagement and the creativity of deck builders, encouraging listeners to share their own decks and thoughts. Going Down Swinging: https://marvelcdb.com/decklist/view/44216/going-down-swinging-1.0 Valkyrie's Black Knight: https://marvelcdb.com/decklist/view/42221/valkyrie-s-black-knight-1.0 Chapters 00:00 Introduction to the series 03:07 Deck Building Themes and Player Archetypes 09:46 Exploring the Beta Ray Bill Deck 16:40 Valkyrie Deck Analysis 28:53 Community Engagement and Closing Thoughts    

Join hosts Ed Voccola (Rick and Morty, Bless The Harts) and Chris Cullari (Blumhouse, The Aviary) for a wild trip through the world of what scares them.  This week, the Hose Boys kick off Season Five by dialing the clocks back almost a quarter century to the night of Dec. 31st, 1999. Y2K was on everyone's lips. Society was going to collapse at the stroke of midnight. How did we manage to survive? And how long until the next digital disaster? Don't love every word we say? Ok, weirdo. Here's some "chapters" to find what you DO love: 00:00:00 - Intro 00:02:07 - Housekeeping 00:06:17 - 5-Star Review Corner 00:10:40 - We're Talking Y2K 00:15:32 - Y2K basics 00:22:15 - HelloFresh 00:23:52 - How the Problem Started 00:34:39 - Y2K Etymology and linguistics 00:40:29 - Y2K in Pop Culture 00:44:24 - BetterHelp 00:46:05 - Y2K in Pop Culture Continued 00:59:40 - All Hands on Deck 01:03:24 - After Midnight 01:10:24 - The Fix 01:17:17 - Mini Y2Ks and AI 01:26:52 - The Fear Tier NOTE: Ads out of our control may affect chapter timing. Visit this episode's show notes for links and references. And the show notes for every episode can now be found on our website. Want even more out of SATT? You can SUPPORT THE SHOW and grab yourself ad-free episodes, a welcome button, and more by joining SATT PREMIUM.

Yankee Stadium fans ejected for prying ball from Mookie Betts' glove. 3 arrested for series of violent ‘follow-away' robberies across Southern California. Among the newest dating events in L.A. is All Hands-on Deck, a live matchmaking party where people pitch their single friends to an audience with a four-minute slide deck presentation. LA Voting.

In this episode, we dive into “Watermarkisms;” the phrases and sayings that help shape the culture at Watermark Community Church. John McGee and Ashley Lawrence unpack the importance of the words we choose, how they influence your team, and create a culture of ownership.Watermark's Owners ManualPopular Phrases We Say Around Watermark:1. Ride Along2. Think Like an Owner3. Last 2%/ 24-Hour Rule/ Widen the Circle4. Preach, Pray, or Die5. Faithfulness of the Leader, Faithfulness of the Team6. Farkle/ That's a Way to Lose!/ High-Risk High-Reward7. Find the One8. How's Your Ministry?9. Stay in the Ring With Me10. All Hands on Deck11. The Most Important 100 are the Next 100Bonus: Knock Your Socks Off