Podcasts about HTML

The Geeks return with a brand-new Grumpy Old Geeks Wiki containing 21,577 static HTML pages, because apparently the appropriate response to having a massive podcast archive is to build an even more massive searchable monument to it. From there, things get considerably less wholesome as they dig into TikTok's settlement with Alabama, AI companies promising safeguards while simultaneously unleashing increasingly autonomous agents, and an OpenAI agent that apparently decided that “I can't access this” meant “perhaps I should hack it.” Government websites, a university digital library, and other targets apparently became irresistible once the normal route to the information stopped working. The Geeks contemplate the exciting future of digital interns who don't understand that the Computer Fraud and Abuse Act is, in fact, not a suggestion.The AI-agent discussion rolls into Meta's Muse, OpenAI's new agent tools, security boundaries, and the increasingly familiar problem of giving software enough permissions to accomplish a task and then discovering it has developed its own interpretation of “accomplish.” The episode also tackles Utah's attempt to apply age verification requirements to VPN users, New York's legal fight with prediction markets, Meta expanding Instagram into schools, and the continuing saga of AI-generated music and copyright. Then there's Automatic's corporate drama involving Matt Mullenweg, vibe coding, and the increasingly compelling argument that if you can build a website in a few hours, maybe spending years arguing about WordPress is no longer the best use of anyone's time.Finally, the Geeks move on to the technological disasters that really matter: Plex changing the Apple TV skip controls unless you pay for premium, a Samsung software update that managed to turn some AI refrigerators into very expensive food-warming cabinets, and Toy Story 5 proving once again that Hollywood has never met a perfectly good ending it couldn't monetize. There's also a trio of soccer documentaries, including Italia 90, Angel City, and Game and Glory; a discussion of the Strange New Worlds finale “Tomorrow's Enterprise”; and Meta's new lightweight VR glasses. Because nothing says “we have learned absolutely nothing” quite like putting more software between you and your refrigerator.Sponsors:DeleteMe - Get 20% off your DeleteMe plan when you go to JoinDeleteMe.com/GOG and use promo code GOG at checkout.Private Internet Access - Go to GOG.Show/vpn and sign up today. For a limited time only, you can get OUR favorite VPN for as little as $2.03 a month.SetApp - With a single monthly subscription you get 240+ apps for your Mac. Go to SetApp and get started today!!!1Password - Get a great deal on the only password manager recommended by Grumpy Old Geeks! gog.show/1passwordShow notes at https://gog.show/765Watch on YouTube at https://youtu.be/meLT-1PRbpASHOW NOTESThe Grumpy Old Geeks WikiTikTok reaches first state settlement over teen safety claims, agrees to user limitsLawyers in Alabama's TikTok settlement set to earn $14 millionBill Gates says it's 'completely irresponsible' for AI to not have safeguardsOpenAI's agent hacked into an Australian government websiteOpenAI's agents targeted and infiltrated US government websitesOpenAI Gets Sued Over the Hugging Face HackWith Dots, OpenAI Wants You to Stop Being Afraid of Its AI AgentsTrump's New America.gov Chatbot Seems to Drop Acid When You Tell It to Play MinecraftNVIDIA Launches Open Agent Safety Platform to Secure Agents From Testing to DeploymentHere's why OpenAI is absent from Nvidia's industry-wide effort to end rogue AI agentsFederal Judge Blocks Utah's VPN CrackdownNew York continues to fight prediction markets with a lawsuit against PolymarketExpanding Instagram's School Partnership Program to Help Teens Stay InformedAutomattic has a new board after failed attempt to put CEO on leaveThe problem with smart appliances: some of Samsung's AI fridges have shut down and lost their cool after a bad update was accidentally pushed to themToy Story 5Italia 90Angel CityGame and GloryStar Trek Strange New Worlds S04E10 Tomorrows EnterpriseThe DiplomatCan Imax, Dolby and New VR Glasses Help Meta Reboot Its Immersive Entertainment Ambitions?Peter Byrne, Singer From '80s Synth-Pop Duo Naked Eyes, Dies at 74See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

We are excited to have Anthropic share their latest AI x Finance work at AI Engineer New York, coming up in 2 weeks!In case you've been under a rock, here's a non-exhaustive list of what Anthropic has been shipping since closing the largest fundraise of all time in May at $47B ARR:* June: Launched Claude Tag and Sonnet 5 and Fable 5* July: Opus 5, /checkup. crossed $65B ARR* Last month: Fable/Mythos 5.1, and EFS (upcoming pod)* IPO target $2T, end 2026 ARR estimated $100B* Cowork/chat merged before did* Claude Mods* Dario endorses the same Pacing the Frontier message cosigned by all labs* Last week: Opus 5.5, Plugins portal, Cloud Sessions/Claude Projects* Today: Sonnet 5.5!Today's episode should catch you up, with Thariq Shihipar, the explainer-king of Anthropic, who we last caught up on Fable launch day with The Field Guide to Fable:The Future of Mutable SoftwarePay special attention to Claude Mods (especially the cheatsheet):In general this is also the inverse of the other viral tweet from Thariq:Cloud Brain, Local HandsAnd give a try to Claude Projects:The “hands” terminology is not just an analogy for the local/cloud paradigm that is being built up at frontier coding agent companies like Cognition, but is ALSO particularly relevant to the safety systems discussions that we'll be discussing with Anthropic in an upcoming episode as they prepare to pace to frontier with responsible AI deployment.For those who want Thariq's writing tips we teased at the start of the pod, watch the full video here:From the rapid rise of Claude Code to a future where agents can rewrite their own harnesses, collaborate across teams, and operate across cloud and local environments, the way we build software is changing extraordinarily fast. In this episode, Anthropic's Thariq Shihipar joins swyx and Vibhu to unpack how power users are actually working with Claude Code today, why prompting remains a high-skill discipline, and where Anthropic thinks the agent harness is headed next.We go deep on Claude Code's evolving interface: Ask User Question and elicitation, artifacts as persistent generative interfaces, Claude Tag for multiplayer agent workflows, Projects, model effort, implementation notes, and the new Claude Mods system for customizing the harness itself. Thariq explains why Claude.md may eventually disappear, why the smartest model could also become the cheapest model for many tasks, and why mutable software could become a new paradigm for how applications are built and customized.The conversation then turns to agent security and Anthropic's “Pacing the Frontier” argument. Thariq walks through recent incidents where agents discovered unexpected ways to communicate, exploit infrastructure, reverse-engineer benchmark scorers, and chain vulnerabilities together. We discuss sandboxing, prompt injection, autonomous agents, interpretability, constitutional classifiers, probes, fallbacks, Auto Mode, and why securing increasingly capable agents may become one of the defining engineering problems of the next few years.We discuss:* Why agentic coding went from controversial to the default in less than a year* Why prompting is still one of the highest-leverage skills for working with Claude Code* How expert users build a mental model of Claude and what it can reliably one-shot* Why discovering your “unknown unknowns” matters more as agents become more capable* Artifacts as persistent, generative interfaces between humans and agents* How Claude could split into a cloud-based “brain,” local or remote “hands,” and dynamic interfaces* Claude Tag, Projects, and multiplayer agents and how collaborative agent workflows could evolve* Why spending more time on the initial prompt can dramatically reduce wasted agent work* When to use low, medium, high, or max effort for different engineering tasks* Why frontier models may eventually outperform smaller models on both intelligence and token efficiency* Why implementation notes can expose decisions the model considered but chose not to make* Why Claude.md may eventually disappear — and why starting without one can sometimes be better* Claude Mods: customizing the execution loop, UI, subagents, routing, and behavior of Claude Code* Model routers, forked agents, and supervisor agents that automatically improve agent workflows* Why Claude Mods may be an early preview of “mutable software”* The bitter lesson of harness engineering and why agent architectures go out of date so quickly* How Claude Tag is becoming an organizational harness for multiplayer work* Why giving agents access to company data creates an enormous new security surface* The Exploit-Bench incident where agents discovered ways to communicate and collaborate* Why agents hacked Hugging Face for scorer code rather than benchmark answers* How agents chained sandbox and infrastructure vulnerabilities in unexpected ways* Why increasingly capable agents make traditional security assumptions harder to maintain* The argument behind Anthropic's “Pacing the Frontier” proposal* Why software engineers are increasingly doing two jobs: engineering and keeping up with AI* Constitutional classifiers, probes, and fallbacks and what interpretability looks like in production* How Auto Mode checks whether an agent's actions actually match the user's permissions* Why Thariq can see serious AI risks while still having a relatively low p(doom)Thariq Shihipar* X: https://x.com/trq212* LinkedIn: https://www.linkedin.com/in/thariqshihiparTimestamps00:00:00 Introduction00:04:12 Ask User Question and the Future of Agent Interfaces00:08:29 Artifacts, Projects, and Multiplayer Agents00:15:37 Prompting as the Core Claude Code Skill00:21:52 Context, Effort, and Smarter Model Usage00:28:10 Is Claude.md Going Away?00:32:49 Claude Mods: Customizing the Claude Code Harness00:36:35 Model Routing and the Rise of Mutable Software00:44:40 The Bitter Lesson of Harness Engineering00:50:49 Claude Tag as an Organizational Harness00:55:59 Pacing the Frontier and Autonomous Agent Security00:58:22 Agents Hack Hugging Face for the Scorer01:05:34 What Happens When Agents Need More Compute?01:10:32 AI Coding Is Changing Faster Than Engineers Can Keep Up01:17:17 Probes, Fallbacks, Interpretability, and Auto Mode01:28:32 AI Risk, p(doom), and Closing ThoughtsTranscriptIntroduction: Life at Anthropic and the Pace of ChangeSwyx [00:00:00]: We're here in the studio with our friend Thariq from Anthropic, and I guess generally the Claude Code, I-- there's, there's so much, merging of boundaries and you've been so on top of everything since you joined Anthropic. You have been early to Claude Code itself, but then also, and you've told that story in other podcasts, and you've also been talking about seeing like an agent. Most recently you did the top AIE World Tour talk, Field Guide to Fable, which obviously you guys launched Fable, so that was-- that's cheating. And mostly you most recently also launching Claude Tag, and we're also gonna be talking about Pacing the Frontier. There's a lot going on in Anthropic. I guess top of the question is, what's it like being at Anthropic when there's so much going on?Thariq Shihipar [00:00:48]: I think that It is, like. I think you can get whiplash sometimes. I think, like, going. When I joined Anthropic, I joined because of Claude Code. Like Claude Code had just come out and I was like, “This is so good.” And Opus 4 to me was like just, I could not imagine, like, how good it was? And that was, like, a real moment for me. But I was, like, trying to convince, like, my startup friends to use agentic coding, and they're like, “Oh, no, like, our engineers don't think it's good enough,” or something. And I was like, “That's insane.” and now you, like, fast-forward, 12 months, less, and, like, it's just like, yeah, the default way that everyone codes, right? And I think that, like, just having to go from, like, selling it to, like, now, teaching people how to be. make the most use of it and be more efficient and things like that is just like a big, like big change. And, yeah, I think, like, it's just hard to stay on top of everything as a human? Like, I think things happen so fast and likeSwyx [00:01:51]: You just throw more agents at it.Thariq Shihipar [00:01:52]: Yeah, like that's like the agentic stuff scales much better than the, like, human stuff where it's like, oh, like, there are three things happening right now and, like, they're all emergencies and, like, how do you, like, respond to it? Yeah.Teaching People to Use Claude CodeVibhu [00:02:05]: What do you split your time on? You do a lot of technical writing, engineering work.Thariq Shihipar [00:02:10]: Yeah, so I think that, like, when I joined the Claude Code team, I wanted to teach people how to use Claude Code and I think that, like, that has been something that, like, I thought, like, maybe I would spend a little bit of time on it or, like, I'd, like, do. I was spending some time on the agent SDK first, and I wasn't exactly sure, like, how the bitter lesson would go, when it comes to, like, harnesses, right? Like, I think sometimes we were like, “Oh, like, what's after Claude Code?”? And so initially I was like, I just wanna teach people how to use Claude Code and make it easier to use Claude Code. And I think that has just, like, as the harnesses have gotten better and better, that's like the dominant problem now is, like, how do you use the agents, right? Like, it's like such a high skill expression thing. So I do that and then I do engineering work. I give talks, but I think, like, when I'm doing engineering work, my goal is to take that feedback that we get from users and also, like, then be able to talk about, like, hey, how to use Claude Code to do engineering. So there's like a good loop there. Yeah.Swyx [00:03:07]: Yeah. I'll-- For listeners, we'll attach, the talk that you did with Sarah for the Dev Writers, meetupThariq Shihipar [00:03:13]: Oh, yeahSwyx [00:03:13]: Which we talked a little bit about, well, first you do the work and then you talk about the work.Thariq Shihipar [00:03:16]: Right.Swyx [00:03:16]: Something like that.Thariq Shihipar [00:03:17]: Yeah.Swyx [00:03:17]: It's sow and reap orThariq Shihipar [00:03:19]: Yeah, reap and. Sow and reap.Swyx [00:03:21]: Something like that. Something like that. Yeah, so, and then just to preview a little bit, we are gonna talk about the evolution of the harness. It has come a long way from just being a CLI. We're gonna talk about, Claude Mods, which is starting to leak today, because you couldn't keep it secret.Thariq Shihipar [00:03:36]: Yeah. yeah.Swyx [00:03:39]: Yeah, there's, there's a lot, there. I think you started off with, like, adding ask user question tool, which people love and hate.Thariq Shihipar [00:03:48]: Yeah.Swyx [00:03:48]: Like, I thought it was, like, very innovative, and then now I have, like, my own version. You have your Interview Me version.Thariq Shihipar [00:03:55]: Yeah.Swyx [00:03:56]: And, yeah, everyone just has, like, their own stuff. And, like, it no longer matters ‘cause now you're supposed to, write prompts that create other prompts and loops and all these things.Ask User Question and Human-Agent InteractionThariq Shihipar [00:04:05]: Sure, yeah.Swyx [00:04:06]: So what's the state of the art, today? Like, what are people. what are you, like, telling people to do today?Thariq Shihipar [00:04:12]: Yeah, ask user question was the first time that the model was good at elicitation. I think this was, like, an emergent behavior that I, like, wanted to see if the models could do. I have, like a human-computer interaction background, so I, like, did that in undergrad and grad school. And so this was like. I think it's like human-agent interaction to me, like, trying to figure out, like, how can the agent communicate with you and extract, the requirements, right? I think that, like, one of the things about, like, that's difficult as Claude Code has gone broader and broader is that everyone has, like, their own way of using it, and it's very hard to, like, change the default behavior. So for example, like, if someone asks Claude Code to do something,Thariq Shihipar [00:04:59]: Sometimes they just want them to do the work, ‘cause they're, like, maybe a very good prompter, and sometimes they want. like, are not good at prompting? And you need. like, the agent needs to, like, clarify? And so that's, like, a good split. Like, and the ask you the question tool like, splits along that side where, like, are-- do you feel like you're good enough to instruct the agent as it is, or is the agent able to, like. does the agent need to, like, pull out more requirements and, like, collaborate with you more and really understand your preferences?Thariq Shihipar [00:05:27]: I, on the whole, believe that pretty much everyone is more on the latter than the former, that they, like, have more ambiguity and they know less than they want, than they, like, think they know about the problem. but, like, it's like a interface design problem to make that easy? And so, like, if you're designing a problem, like, or if you're going through a problem, like, things like what's the schema or, like, what's the call stack and things like that are really important. like, the details in the design are important. Ideally, you want to figure out some of these, like, hard problems ahead of time before starting implementation. And yeah, that's why they call, like, unknowns, right? And so I think that this will forever be, like, a skill in agentic coding is, like, figuring out your unknowns. So, like, because even if the model is, like, super intelligent- It, like, needs to know what you want? And, like, you have preferences. like, you need to like, pull the, pull that out. and so that's, like, I think how I'm, what I'm pushing. the question then is, like, how does the agent interact with you? And I think that has been HTML, has been, like, the big way of doing that. And we've recently added artifacts, right? And artifacts, I think we've done a bad job of, like, or, like, I've done a bad job of, like, explaining how to use them fully. We have a lot of property capabilities. They have a database associated with them? And so every artifact can store and write persistent data. They can, like, feed back into Claude? And so, like, one thing that, like, people are not doing yet that I'm trying to, like, encourage is, like, this idea of a dashboard artifact. So you have, like, Claude working on a project long-term. Maybe it's like a kanban or something. it can store that kanban data in its database. Multiple Claudes can access that data via, like, the artifact MCP, and, like, that artifact can, like, talk to those Claudes as well. And so, like, the. We're building the primitives for you to be able to have this, like, generative interface via artifacts that will, like, let you surface more of that rich detail from the agents. And I think that, like, almost everything with agents right now is, like, this problem of, like, you think what you want, but you don't really know what you want, and, like, the agents need a lot of detail, and collaborating with them in the loop is really important. And so artifacts are, like, the, like, way that we're trying to evolve there. But there's a lot of work to do because it's so much more complicated than, like, a multiple-choice question? there's a lot more, like, detail in terms of, like, diagrams and code snippets and schemas or, like, whatever it is for that problem. But, like, artifacts is, like, the mo-more AGI-pilled way of, like, doing ask user question. So yeah.Artifacts as the Interface to the HarnessSwyx [00:08:15]: I think one thing that's unclear to me about these, the artifact stuff is, like, what feedback should go in through the artifact and what feedback should go through a Claude, a chat? Because the more AGI-pilled one is to just feed everything to the Claude.Thariq Shihipar [00:08:29]: I think the more AGI-pilled one is to go through the artifact. Like, and I think that, like, we imagine in the limit, I think that artifacts will be your interface into the harness? You can, like, comment on this, like, live, like, document of your plan, of the work. you can see maybe, like, multiple agents and different agents are doing this, and that artifact is built for the current work that you're doing, right? And so, like, each one has, like, slightly different. I think we're still, like, getting there from, like, an infrastructure perspective. But yeah, I think, like, on-the-fly interface for your harness is probably where things are headed.Vibhu [00:09:03]: Is there a version of it that's an abstraction from CLI or chat and you. Because right now, a lot of it is, okay, you're interfacing with Claude Code, you're having HTML given back for a mockup. It's pretty rich. There's diagrams. Artifacts are ways to connect these together. Why not just do everything that way?Separating Brain, Hands, and Surface UIThariq Shihipar [00:09:22]: Then it becomes, like, separating out, like, where is the inference happening? Where is the intelligence happening? Where is the work happening? like, I think this is like, difference between, like, or, like, some of the distinction between local and cloud, right? And so, I think right now, if you use Claude Code, it's, like, local and, like, you can spin off remote control, for example, to get some cloud behavior, or you can spin off Claude Code in the cloud, right? We're moving towards a place where instead of Claudes, like, you message a local Claude, it starts a session locally and it executes, to more like you have a Claude that you message that's in the cloud that's running. it can run, like, local, or, like, cloud sessions. This is how Claude Tag works. But, like, over time, we'll add, like, local hands as well. And so, like, local hands will be the ability for that agent to access your computer if it's online, and be able to, like, work there. And so it can spin off many different subagents. It can, like, commu- those subagents can communicate with each other, and that's where the artifact comes in to display all of that work. So you can imagine, like, the. You're separating out these things. So there's, like, the surface UI display that's an artifact and hosted somewhere and has a database and everything. There is the inference intelligence, right, that's happening on the cloud, and you don't have to worry about shutting off your computer or whatever, right? and then there's the, like, hands. Like, and it can be local, it can be in, like, a remote sandbox or wherever you need your work to be done. That's like unpackaging, like, the Claude Code experience right now where, like, right now it all happens in one place, right? So.Multiplayer Agents, Claude Tag, and ProjectsVibhu [00:11:00]: How do you see, like, the multiplayer side of that? So say teams want to work in this way. Right now it's very individual, but how do you see the future of multiplayer? Like, right now, I guess there's Claude Tag, which is a version, but.Thariq Shihipar [00:11:12]: We're launching projects. And so projects is the, like, this abstraction that's like Claude Tag, but on our Claude products, right? So you can message it and, like, it will do the Claude Tag-like stuff, like spinning off subagents. So We think with multiplayer. Like, Claude Tag is, like, a little bit more native multiplayer because it's just, like, in your Slack and the permissions are all figured out and stuff like that. But I do think multiplayer is, like, an important part of the story and, like, that will need to get tied together more. Like, you can imagine how complicated it gets when you're like, oh, you have hands, but now you have other hands in other people's computers too, and, like, you need to, like, permission them or, like, you have, like, your MCP and someone else's MCP, and how do you figure out how to use them, right? It gets, like, quite complicated. And Claude Tag does a good job of, like, sanding down all of these issues, right? So that, like, when you have, yeah, Google Docs, how does it access Google Docs, right? Like, it accesses through the shared Claude MCP, or it can access through your local credentials as well if it doesn't have access. But yeah, I think Claude Tag is our multiplayer, product, and it's really useful for these, like, things that are inherently multiplayer. Like, okay, like on-call, for example, incidents are inherently multiplayer. You want to tag Claude, you want multiple people to log in, you want it to be able to find context. I think whenever I'm, like, working on something and I want, like, privacy or security or, like, I want other people to review it's really nice to, like. I'll have a channel per project and I'll, like, at legal, for example, be like, “Hey, like, I want to ship this. Can you, like.” Like, here's. Like Claude knows everything, just chat with it. And that way legal gets precise answers, on like what exactly is shipping into the code, and I don't need to be in the loop, right? So I think like multiplayer is getting like more and more like, yeah, everyone can participate with Claude. I think Claude Tag is like that product and like projects will start off single player and will like, expand.Swyx [00:13:14]: I think there's a question about like maybe dual questions about identity and the unit of isolation.Identity, Permissions, and IsolationThariq Shihipar [00:13:20]: Yeah.Swyx [00:13:20]: Claude Tag, you specifically chose to make it its own identityThariq Shihipar [00:13:26]: Yes.Swyx [00:13:26]: Which is like, a controversial choice. There's, there's other ways to do it.Thariq Shihipar [00:13:30]: Yeah.Swyx [00:13:30]: Claude Projects probably it sounds like, if it's anything like ChatGPT Projects, it is, the isolation is that artifacts, that cloud instance, everyone's collaborating on this. It'll. It sounds like, it should be like if you're, if you're collaborating with legal on a thing, like that channel should be a project, right? Like it's not yetThariq Shihipar [00:13:50]: Yes.Swyx [00:13:50]: But it. that's the natural next step.Thariq Shihipar [00:13:53]: Yeah, like I think in Claude Tag, it's effectively. Like Claude Tag, you have to do your own arrangement. And so Claude Tag, yeah, each channel is like you can name it as you want, and I nameSwyx [00:14:04]: Yeah.Thariq Shihipar [00:14:04]: Like each featureSwyx [00:14:06]: Yeah.Thariq Shihipar [00:14:07]: As a channel.Swyx [00:14:07]: And, but I think like there is some trans- like it's unclear when there is transference, because let's say it is. if you have a coworkerThariq Shihipar [00:14:14]: Yeah.Swyx [00:14:14]: Who is tagging on all these things, yes, there is transferThariq Shihipar [00:14:16]: Yeah.Swyx [00:14:16]: Because it's the same person. but with Claude, it's unclear if it's like necessarily like, well, no, you don't know any of. you don't know about the other stuff. You should only use this stuff.Thariq Shihipar [00:14:25]: It's like the tip of the iceberg meme, right, where you can like. This is what we spend so much time onSwyx [00:14:31]: Yeah.Thariq Shihipar [00:14:31]: Is like there is like infinite surface area of like, okay, you want Claudes to. Not infinite, but like there's like surface area, a lot of like, surface area to figure out of like permissions and visibility and like how can you let Claude operate as well as you can, as safely as you can? And obviously, this is very important to us because like security for our code base is very important. And so we've put a lot of time into this. Yeah, there's so many like edge cases you can figure out where it's like, oh, like, yeah, this Claude in this channel has different permissions, but it can message another channel, and can't it exfiltrate data that way? Or like can you like. What if it uses your MCP and then messages someone else? Like there's like so much, and we've like really put a lot of work into sanding it down.Swyx [00:15:14]: Yeah. Lots of work. okay. Fable?Fable and the Meta-Skill of PromptingVibhu [00:15:18]: Fable, you wrote two good articles. you've written many good articlesThariq Shihipar [00:15:22]: Yeah.Vibhu [00:15:22]: But on, Field Guide to Fable, Building Claude Code. I'm curious from what you've seen, is there any common patterns that you see in like top users at Anthropic externally? Like what are best practices for getting the most out of Claude Code?Thariq Shihipar [00:15:37]: The like meta skill I say is like prompting is like very important? And like that. Like I think this is like not trivial to say because I think a lot of people are like, “Oh, prompting doesn't matter. It's just like I can just say a sentence and Claude will do it.” And I think prompting is really this like, this. It's like public speaking, like, or writing or something, and for a specific audience, and that audience is Claude. And you need to like build a mental model of Claude and how it thinks and how it works, right? And so that's like the most important skill in working with Claude Code is like having this mental model, right, of Claude and like what it can do well, what it can one-shot, what it can't. And so many people when you see prompting, they're just like, they're short prompts, but they have such a good mental model of Claude and of like the code base and things like that like it's effortless? But it's like high skill ceiling. So like that work of like, spending a lot of time prompting and building mental models of how, and intuition for how the agents work is really important. And then I think like the next thing is like the unknown stuff we talked about earlier, where it's like being able to find out like your, what you don't know or what you haven't written down, learning about like different things. I think as Claude can do more and more things, the likelihood of you doing something out of distribution for you and like you have low domain knowledge on is very high? And the more you can like learn the vocabulary to be able to prompt Claude, it becomes really important. And so like I think the most important unknowns are the unknown unknowns, where you're like, I just like don't even know that this exists, right? Yeah, exactly. I think that's like a illustration of like the map and the territory, right, where you're like, “Okay, this is my prompt,” and the territory is like the actual like work that the agent needs to do, right? And if you are like very precise, you can give more precise things, right? So like for example, in design, I'm not very precise. I'm not a designer, so I say like, “Give me like eight different mock-ups.” But if I was a designer, maybe I'd be like, “Oh, hey, here are some reference sites.” Like, “I want this type of font and this type of like look to it, and here's like a few different components to like visualize. Here's a Figma MC board to bring in,” like. And so you can just be so much more precise with that language. And if you're not a designer, you just need to like try and learn the language or learn the unknown unknowns. And this is true of like everything, I think. Like the more, like you can work with Claude to learn like how things work, the better your prompting will be. I think another good example of this is like game design, like where a lot of people are like, “Oh, like I can vibe code a game now.” And they're like, “It's not fun.” And like it's just like the thing about game design is like every one of these choices has like a lot ofTaste, Domain Knowledge, and Learning the VocabularySwyx [00:18:25]: Variations.Thariq Shihipar [00:18:25]: A lot of like craft to them. So it's like, oh, okay, like when you're making a flying game, the feel of the plane and the like, way it responds to your controls has a lot of like. Like, a game designer would spend like days on that. Do? and likeSwyx [00:18:44]: To me, that's what taste is, right?Swyx [00:18:45]: Like it is like from the possible space of one thousand mathematically valid answersThariq Shihipar [00:18:49]: Yeah.Swyx [00:18:49]: Here's the one that is the humans will like.Thariq Shihipar [00:18:51]: Yes. Yeah.Thariq Shihipar [00:18:52]: I think with taste, I'm like torn on this word ‘cause I think you're right, but everyone has different definitions, and it sounds kind, sounds like low skill or like elitist almost, where you're like, oh, like there are certain people with taste?Swyx [00:19:06]: It's like taste is what I call taste.Thariq Shihipar [00:19:07]: Yeah, exactly.Swyx [00:19:08]: And it's like these guys don't have taste.Thariq Shihipar [00:19:09]: Yeah, exactly. Oh, like an engineer doesn't have taste. Like I, the like founder, have taste.Thariq Shihipar [00:19:14]: ? And I think that's not true. Like I think like the engineers have a lot of taste for these particular like problems? And I think everyone has taste for particular problems. I think like Jason Liu, like say like in order to, yeah, have taste, you have to eat?Thariq Shihipar [00:19:32]: And I really like that, where it's like, okay, you have to like do a lot of things. You have to like iterate and figure out what you want, what you like, and, like build that like domainSwyx [00:19:41]: YesThariq Shihipar [00:19:41]: Domain vocabulary. And then when you're prompting, you're like synthesizing all of that for a product.Swyx [00:19:46]: Isn't it annoying when someone else says it better than you?Swyx [00:19:48]: It's just like, f**k, I have to quote this guy forever.Vibhu [00:19:51]: Having to quote Jason Liu forever.Vibhu [00:19:53]: He's gonna love this.Thariq Shihipar [00:19:55]: So I get prompts, more than that.Vibhu [00:19:57]: And sometimes it's not even that. Sometimes it's just intuitive, right? Like you don't realize you even want something till a model puts it out, and you're like, “Oh, this just feels immediately better,” right?Voice Prompting and Information DensityThariq Shihipar [00:20:07]: Yeah, exactly.Swyx [00:20:09]: One thing I go back and forth on is I feel like the way I prompt half the time, let's say I use voice.Swyx [00:20:16]: Did I say voice? Other people have voice. that is the opposite. That is just like me rambling for like two minutes Pressing down the function key and then let go, and then like hopefully it figures it out. And oftentimes it does.Thariq Shihipar [00:20:26]: Yeah.Swyx [00:20:26]: But it's not as thoughtful as like a structured prompt with like Well-run communication as though it's a PRD or a memo. Is that in line with how people do this? There's like bimodal prompting where there's some prompts where you spend a lot of time upfront and other prompts you just dash it off?Thariq Shihipar [00:20:43]: I don't think the voice is necessarily low. Like I think it's like more like how much information is in the prompt. like the model can. Like you can and like add some sentencesSwyx [00:20:53]: RightThariq Shihipar [00:20:53]: And be like, “Oh, like I changed my mind,” like in the middle of the prompt, and it will be able to follow that perfectly? So I think the like actual format of the text is less important, but then like the ability to. Like how much information is in it, right? And I think for voice, a lot of times, going back to like human-agent interaction and like for a lot of people, it's just way easier to talk than to like type? and I. If that gets more information out of you, like that's better.Vibhu [00:21:21]: At some level, it feels like just giving the model as much contextThariq Shihipar [00:21:24]: YesVibhu [00:21:24]: Over prompting before you kick off is a best practice. I don't know. A lot of the times, like when I was first trying out Fable, I spend a solid 30 minutes like really crafting a long prompt. This, I think, is a response of models running for longer and longer, right? It's still a little difficult to nudge them as they're in like, in the loop, but I just like intuitively spend more time kicking off that first prompt and working with it a lot.Spend More Upfront, Iterate LessThariq Shihipar [00:21:52]: My personal opinion is that if I was a software engineer, if I was like, just running my own startup, for example, I think I would mostly fit, stick to a max 20x? like maybe verification and so code review are like separate things. But I think like what I see a lot of times is people hit rate limits when they're doing this like, oh, like it did a lot of work and you're like, “Oh, I don't like this.” Like, “Can you like undo this and redo it?” And then you're like iterating on this like thing that the model could have done if you had like spent more upfront time or given it better context? And instead it's like you're like, “Nope, don't like that design. Try this.” Or like, “You messed this up,” or something like that. And then that just eats up so much more of like, your usage. And so that's like, I think maybe like a key like tip both for like efficiency as well, right? And yeah, I think like context, and not just like context on like what the goal is good, right? Like are you building a prototype or is it like a production thing? Like where can you spend compute or when, where can you not spend compute? Like I think you have to give the model permission or like not permission to do things sometimes where, like it doesn't know intuitively how much you want to spend on this task, right? And you can use effort for this. So I did-- I'm working on a blog post about that where it's like, if you want. For like we see that effort scales with the complexity of the task. So for security, effort gets like way more results. Like high effort versus like low effort gets, like changes the evals a lot. But for software engineering, it doesn't change it a huge amount because effort is mostly spent on the verification and the like edge case testing and things like that. And so like being able to like give the model that guidance of like, “Hey, this problem is something that I think I want you to spend a lot of time verifying and edge case testing,”?Effort, Model Choice, and VerificationVibhu [00:23:43]: How about model in the mix? So, there's Opus and Fable with effort.Thariq Shihipar [00:23:47]: Yeah.Vibhu [00:23:48]: There's also Haiku in there.Thariq Shihipar [00:23:49]: Yeah. It's not quite true yet, but it's very close where I think the frontier models will be Pareto dominant over like almost everything. like maybe. And sometimes I think Opus might be Pareto dominant. Do? Like I think depending on like how things, like shake out if it's like a newer version of Opus. But I think that like increasingly it's just going to be like the smart model is going to be able to like do the simple task for less tokens than the like the other models because of verification. With verification, in the limit, your model doesn't need to verify, right? If it's a perfect model, it just does the work once and it's like, okay, like you, I did it? And increasingly with Fable, I'm like, I'm like, “Dude, you don't need to spin up Chromium and screenshot all of these things.” Like I see it. Like you did it, right? And so a lot of the. At higher effort, you spend more of those tokens verifying. But if you're working on simpler problems, and a lot of software engineering is like well, like in Fable, like low and medium stability, it can spend less tokens verifying. And as the models get smarter and smarter, they will just be able to like, “All right, done.”? Like, I can run the lint for sanity's sake, but, like, I, like, know it lints? Like, you don't even need to do that. And that will be so much more token efficient than, like, the smaller models. Yeah.Swyx [00:25:15]: Is there a good, practice on our side that we can use to see if we're using too much effort? Like, I freakingThariq Shihipar [00:25:23]: YeahSwyx [00:25:23]: Hate wasting time on that stuff.Thariq Shihipar [00:25:24]: Yeah. I know what you mean. I think, like, so in this blog post, my rough distribution is, like, code review and security should be, like, high or max and, like, software engineeringSwyx [00:25:37]: You said recommend mix settings per domain.Thariq Shihipar [00:25:37]: Yeah. I think, like, if you're doing, like, UI or something like that, like low and medium, I think is you're building, like, an API and you want to make sure, like, you cover enough edge cases? And so I think building, like I said, that mental model of, like, how things work across these distributions is, like, yeah, part of the job.Implementation Notes and Decision LogsVibhu [00:25:56]: This is more intuition-driven or eval? Because I'm guessing this would change as you go.Swyx [00:26:00]: He has evals.Thariq Shihipar [00:26:01]: Yeah. So what I did in the blog post is I go over all of the terminal bench evals. So there are, like, 70 problems and I'm show that, like, okay, like, in the security problems it does more. and then I also, like, look at some of the transcripts just in terms of, like, how-- what does it answer, what does it forget or something. And a lot of times, this is another prompting tip I have, is, like, asking it to make decision notes or implementation notes because, in every eval problem that it faces, it thinks about the correct solution, and decides not to do it. it's like, oh, like, here is the answer. What if I did this? And then it's like, oh, probably not? and then keeps going. And this is, like, the majority of the failures, at, like, a higher max level. It's very rare that the model just doesn't know how to do something. If you just have these implementation notes, then you can review and you can be like, “Oh, I want you to do this thing that you didn't do.” The models are getting better at surfacing that overall. Like, I see in the transcripts of Fable 5.1, like, when it does this output, it will call out its decision-making as well. but making this more explicit in the harness is better. And now we're, allowing ways of you modifying the harness so you can, like, add someVibhu [00:27:23]: Ooh.Thariq Shihipar [00:27:24]: Calculate with there. Yeah.Swyx [00:27:25]: Yeah. So I do wanna call out two things that you mentioned that I think exist outside of prompting. One is like, let's, let's call it the prompt that is so important that it shouldn't be in a prompt. It is in Claude.md or Agents.mdThariq Shihipar [00:27:38]: YeahSwyx [00:27:38]: Which is like goals, right? Like your situation, your goals, the things that you want, the thing. and then second of all is the decision log or the experiment log or whatever log of traces that you might want to survive the current session to do those things. Those are, like, externalities that there's no standard. There's no-- It's not like skills. It's not like MCP. There's no standard. It's, it's just like it's a markdown file. first of all, is that right? Is Claude.md going away? You have a documented dislike of, Agents.md, but you're gonna do it?Claude.md, Agents.md, and Model-Specific InstructionsThariq Shihipar [00:28:10]: Yeah. Okay. So Agents.md, yeah, like, we're, we're gonna do it. I think it's just, like, different models are very different from each other? But I realize that it's, like, such a pain to, like, maintain different ones? And yeah, like, as the models get better and better, the floor of how they accomplish the simpler task is better. And so I do think in the limit, Claude.md goes away, and maybe not even, like, that far. Like, I think, like, I think that right now it might be better to start a new project without a Claude.md.Swyx [00:28:44]: Yes.Thariq Shihipar [00:28:44]: I think that, like, maybe if you see very repeated failure modes, you add them to your Claude.md. The really tough thing is that this changes per model. And so, like, if you've added a bunch of failure modes or, like evenSwyx [00:28:57]: So you need Fable MD, you need Opus MD.Thariq Shihipar [00:28:59]: Or well, even Fable 5.1 versus Fable 5.Swyx [00:29:03]: Yeah.Thariq Shihipar [00:29:03]: Like, it is annoying. Like, I'm not like,Swyx [00:29:05]: YeahThariq Shihipar [00:29:05]: Like, we don't, like, do this on purpose? It's just, like, how the models work, right? And so, like, maybe, like, Fable 5 had this, like, failure mode that Fable 5.1 doesn't. And if you keep this context, this running log of a bunch of different failure modes, they will probably over constrain Claude? And so this is like. we just added evals plugins for skills.Swyx [00:29:28]: Yeah.Thariq Shihipar [00:29:29]: And so now you can eval if a skill is better. I think Daisy on our team did this. And so, yeah, this is like we're trying to work on this. We know it's, like, you still have to spend tokens on it and, like, it's not, it's not perfect, but it's, like, we're trying to help out with this problem.Swyx [00:29:44]: And so, and as far as prompting goes, the one tip I wanna offer is, something I have told people a lot is sufficiently advanced prompting is indistinguishable from sufficiently advanced executive communication. So I've referred to-- This is an executive comms workshop from Heavybit that is the best I've ever seen in my career. And they teach this thing called the SCQA model. Just Google it. It's a, it's a thing. Like, people have done prompting for decades. It's just called executive communication. It's like when one person has to communicate to thousands of people down the org chart, this is what you do. so situation, complication, question and answer, is how you write the memo. but obviously sometimes you don't have the answer, but you can at least list out the SC and Q, and then they have some examples in there. So just leaving breadcrumbs for people if they want to explore.Underrated Prompting Patterns and ELI5Vibhu [00:30:31]: Before we move on, I wanna ask you, any other underrated tips, ways people could get a lot of value from Claude Code that they're not using?Thariq Shihipar [00:30:41]: Yeah, I think a lot of them are in the, this unknowns, like, doc. Like, I give a bunch of example prompts, like, using it for brainstorming, using it to quiz you after. we added this, like, explain it like I'm five skill which is a very short prompt. And it doesn't even say explain it like I'm five. It's like the key word of this prompt is big pictures, few words. like, that's like the main thing. And it is shockingly good? Like, you, like, I think I tweeted about this and it's like /eli5, and, like, you can install it as a plug-in. But yeah, it's, like, way better at just cutting through the BS and being like, yeah, exactly right here. So the diagrams are, like, quite clear. I think one of the things that is true with artifacts is, like, they put too much text in and people are not reading the artifacts? And so, like, this simplifies it a lot more. And, yeah, this came out of, like, just people at Anthropic, like, going through very complicated incidents and being like, “What is happening?”? So, this one I think is great, yeah.Swyx [00:31:47]: My version of this is the, it's like test your understanding. Give you a few choices and then, like, if you get it wrong, you have a mismatch between what you think is happening versus what's happening.Thariq Shihipar [00:31:58]: Yeah. I think this is one of those things that everyone loves talking about, and then very few people really do. Like, I thinkSwyx [00:32:05]: Really helpful.Thariq Shihipar [00:32:07]: Yeah. But most people just don't want to get quizzed about something? Unfortunately, I think this is one of the, like, things that we need to, like.Swyx [00:32:16]: What's the opposite of ask you the question or ask you the question before the thing?Thariq Shihipar [00:32:19]: Yeah.Swyx [00:32:19]: This is after the thing.Thariq Shihipar [00:32:20]: Exactly. Yeah.Vibhu [00:32:21]: It's a good way to stay grounded of, like, do you even know what you're doing, right? The worst case is when people send you slop and they haven't understood what they're asking for or what the output is, and it's like, “Dude, I don't wanna read this. Do you even know what it is?” So, you make it a rule for yourself that before you send stuff, you should at least know what's implemented.Claude Mods: Customizing the HarnessThariq Shihipar [00:32:41]: Yes, but so you could make this a mod and you could build your own mod to, like, make sure you test it. So yeah, you can do that.Swyx [00:32:49]: All right. Let's get right into it. What is Claude Mod, and what is this diagram showing?Thariq Shihipar [00:32:54]: Yeah. Okay, so Claude Mods is you can customize the entire Claude Code harness, and we're going to. If you have requests, we will, like, let you, like, please let us know. We'll add more and more. This works for CLI, it works for desktop. maybe it will work for Claude Tag in the future. I don't know. Like, we're trying to make this very extensible. You can see this reference sheet. I don't want people to get overwhelmed by it? At a high level, you can customize both the execution of the harness, and the UI of the harness. And so, like, you say on that Tetris example from Boris, that's like customizing the UI, right? Like showing, like, Tetris in the game.Thariq Shihipar [00:33:35]: But, like, let's say that you wanted to do this thing where you had. you tested your assumptions or, like, tested your understanding after every project, right? What you would do is you would ask Claude to make this plug-in. It would spin a classifier after every prompt. And so, like, at the end of each turn, you would spin off a sub-agent or, like, a forked agent. A forked agent is, like, maintains the prompt cache, right? So it's like a, like one of those unintuitive things where you can fork and do, like, a little request, and it'll be very cheap because the entire prompt cache is, like, done. And so you can be like, “Has this task been completed?” likeSwyx [00:34:18]: This is how you do BTW and all those.Thariq Shihipar [00:34:20]: Yeah. The underlying forked agent, yes. But so you can, in the f-fork sub-agent, you can say, like, “Has this task been completed? If so, return true.” And then in your hook, or in your, like, plug-in mod, or sorry, like, in the sub-agent probably, you would say, like, “If true, give me a quiz.” give me questions and answers, and then, like, in a JSON format, and then you'd parse it, and then you display above the prompt input, this list of questions, right? And so this is something that's, like, slightly token-intensive because, like, you have to do it after every end of the assistant turn. But it's, like, a lightweight classification, and then you can, like, get this quiz, and then you'll see, like, Claude will always do it for you. You don't need to remember to do it. There are lots of these, like, tips that we've talked about, right, where it's like, oh, implementation notes. You can also add a tool for implementation notes now. And so, like, this tool that I'm adding is, like, register, like, I think assumption is what I'm calling it, but, like, maybe I'll change it around. And this is a mod. And so, like, you give it a register assumption tool, and then it will keep a list. It'll. Every time it does it'll keep a, like, add to the list, and then at the end it will display those assumptions? Another mod I'm working on is a model router. And so, like, internal, like, Claude model routing, right? So it's. This is, I want to say the reason we don't do model routing by default is, like, it's a hard problem? And likeForked Agents, Assumption Tracking, and Model RoutingSwyx [00:35:51]: You will get it wrong.Thariq Shihipar [00:35:52]: Yeah, you, like, yeah, you will, like, accidentally use, like, Fable for a hard problem or Sonnet forSwyx [00:35:57]: Yeah, if you have auto approve, but you don't have auto mode.Thariq Shihipar [00:36:01]: Well, you will have auto. Like, you don't have, like, auto routing or something.Vibhu [00:36:04]: You don't have auto mode for model picker.Thariq Shihipar [00:36:06]: Yeah, exactly. SoVibhu [00:36:07]: I'm getting the rough question of, like, how much do you open this up and how much do people have to think about this? Like, when you talk about prompt caching and building a router, it seems like you could easily build a mod that routes per query, and I'm just killing my plan very fast, right? I guess my question is more so, like, what is, like, a product talk like this look like, right? Who is it for? Is it for power users? Is it everyone should be able to go throughSwyx [00:36:33]: Oh, definitely power users, right?Thariq Shihipar [00:36:35]: Yeah, I think it is power users, but, like, the nature of Claude Code is that so many people are power users? Because it's easy to share things, like you can. Like, one person can make a good model router thing that doesn't break prompt cache all the time, and then you can, like, compose them. Another cool thing about the plug-ins is that they can hook into and compose with each other. And so I have, like, a mod that will, like, create a mode selector at the top, and any plug-ins can register to be a mode. And so, like, the auto router can be a mode, right? Or, like, you can have a mode that's, like, artifact mode, where it's like it primarily talks to you in artifacts. like, you can toggle between plan mode? And so, like, you can create more and more of these modes. But the ability to create modes is in it itself a mod? And so there's a lot of richness here, but we do want to make it fairly easy. We want to be-- make it so that you can just, like, install someone else's. You can ta-- you can chat with Claude and, we'll, like, make sure that it understands the nuances of things like prompt caching and stuff, so it can, like, warn you. This is, like, not extremely complicated behavior for Claude, I think, but we should have just a good skill on how to make mods. and yeah, we'll see how we go. But I do think that this is, like, a preview of, like, mutable software, and, like, how, like, generative software, just like you can customize safely. If enabled, you could customize any piece of software. And I think that more and more apps ideally do something like this?Power Users, Modes, and Mutable SoftwareSwyx [00:38:13]: And by the way, you, we have, you have another cool tweet about how, there's the infinite money button, which is like make your SaaS, consumable by agents. I think mutable software is interesting and, other people have also tried to do it. I think the hurdle comes when you can do everything, then people, users get, tend to get confused. So usually the stuff that works is just like one opinionated flow. This is in the side of less opinionation. It's just like, well, more power to power users. And I think probably unlocked by AI, where, like, you can just prompt for whatever the thing is.Thariq Shihipar [00:38:47]: Yeah, or there can be a skill that gives the opinions?Mods vs. Hooks vs. ArtifactsSwyx [00:38:50]: Yeah.Thariq Shihipar [00:38:50]: And then, yeah.Swyx [00:38:51]: So knowing a little bit about, like, TypeScript and build systems and all these things, the closest-- I'm very curious that the team who worked on this, if, I don't know how close you were to them, if they drew any inspiration from build systems like Babel, Webpack, all these, like, old school things. Because it sounds very similar, like the plug-in ecosystem of those things where they can compose with each other.Thariq Shihipar [00:39:11]: Yeah, I'm not deep in the technical details, but I do know it was a collaboration with someone on the Bun team and someone on the Claude Code team.Swyx [00:39:17]: Yeah, it's a build system mecca.Thariq Shihipar [00:39:19]: Yeah. Exactly. It's, it's very exciting. But yeah, like, agents can just do this very complicated like, extensibility into your software now. And so, yeah, like, another reason to, like. If you run a startup, like, you can just prompt Claude and be like, “Hey, like, could we make an extension system? Like, what would that look like?”?Swyx [00:39:37]: Yeah.Swyx [00:39:38]: And I just really wonder, like, you had hooks in the past and plug-ins, all these things. So what specifically will mods be able to do that those things could not do?Thariq Shihipar [00:39:47]: Internally, we were originally calling this function hooks. And so, like, that's, like, gives you a little bit of an idea where, like, hooks register a, like an event to happen and then, like, a script to call. And this inside of the, like, TypeScript runtime is running things. And so, like, you get some benefits of just, like, it has a bunch of things in the Scope with, like, for example, like how many turns is in this conversation, right? Like, how many tokens have been used? Like, et cetera. Like, what are the messages? Things like that. So it has a bunch of messages that can be used. And then it's just, like, a lot more hooks. So we have, like, or a lot of, lot more, like, things you can register on. And then you can do because of the. because it's all happening in process, you can, spawn sub-agents, with four contests and contexts and stuff. And, like, that will return. You can parse the results of those. You can use structured output to like, return them. and then you can modify the UI, which you can never do in hooks. So, yeah.Swyx [00:40:50]: Yeah. Yeah. So modify UI, this is why you showed the Tetris example. Does it also ex-extend to artifacts? I assume it does.Thariq Shihipar [00:40:57]: You-- Like, artifacts are like a different way of customizing it. like, you can definitely. One of the mods I'm working on is, like, this dashboard mod, which will, like, prompt Claude to maintain a dashboard, that's an artifact. But they're like, slightly orthogonal, or not orthogonal. They compose with each other in different ways. Like, mods are, like, a little bit more, like, in your Claude Code harness, changing the agent loop? And, like, the UI is, like, an added benefit. and then artifacts are just like you want to, see things at a high level, very inter- highly interactive. like, the affordances can be a lot bigger than, like a TUI or even in our desktop.Next Steps, Supervisors, and Persistent GuidanceVibhu [00:41:40]: I'm guessing you'll have a good blog post on the differences, because right now you can also, make a loop that outputs to an artifact that's an interactive dashboard, but you can also do it with a mod. There's just some thinking about making a hacking on a harness when we don't know much about the harness, right?Thariq Shihipar [00:42:00]: Well, something I'm excited about with mods is, like, there's so much things with Claude Code that you just have to remember? You're like, “Oh, like, let me do this, and then let me call the dashboard skill that does the loop,” and things like that. And, or like, “Let me test my assumptions afterwards.” And I think, like, if you do all of these things using these little classifiers and stuff, and you're like, “These are the things I care about. This is what I want to do,” you can, like. You don't have to remember as much. One more, like, mod I'm working on is a next steps mod thatSwyx [00:42:28]: I have-- I was gonna say, I have a next step skill. I always run next steps.Thariq Shihipar [00:42:32]: And does it have access to your skills? Like, this is one of those things where I'm like.Swyx [00:42:37]: I think so.Thariq Shihipar [00:42:38]: Okay. Yeah, probablyVibhu [00:42:39]: Do skills need specific access toThariq Shihipar [00:42:41]: Well, I think there'sSwyx [00:42:41]: Don't they always haveThariq Shihipar [00:42:42]: I think there's, like, specific prompting, I guess, to, like, know your skills. Like I think Claude forgets them sometimes throughout, like, the thing. But anyways, the idea of, like, yeah, next steps that also are like, “Oh, hey, this has happened. Use the explain skill to explain to you what happened because this seems, like, quite complex,”? Or, like, yeah, “Use your unknown skill. It looks like you are, like, asking the model to, like, iterate on these small changes. It seems like you could prompt better.” like, “What if you did this?” Right? So, I think, yeah, like spending more compute there. Yeah.Swyx [00:43:20]: And it should always come out as multiple choice. we have, I haveVibhu [00:43:23]: We have his skill.Swyx [00:43:24]: My next step skill is like this.Thariq Shihipar [00:43:26]: Okay, perfect. Yeah.Swyx [00:43:27]: You can steal it.Thariq Shihipar [00:43:28]: Yeah.Swyx [00:43:29]: Like, but like, for me, it's all-- I think models really always need to be reminded, what are you trying to do here?Thariq Shihipar [00:43:35]: Yeah.Swyx [00:43:35]: Look at the whole transcript and go like, oh, was this original goal? Did your solution solve it? Were you lazy? If you're lazy, maybe there's a reason. Maybe you needed approval from me. Maybe you needed, there's two things you wanna suggest. So it's, it's a little bit like the modification of the ask user question or interview me skill. so it's next steps.Thariq Shihipar [00:43:55]: Yeah, exactly. And again, the benefit of doing it with mods is you can do it as a fork sub-agent, and so it doesn't remain in the context afterwards. So you have this, like, idea of like, okay, the model is doing its execution and you have this almost like supervisor, like, that is like making sure that you can do like the next steps well. So yeah.Swyx [00:44:15]: Yes. I do have two panels and like I often try to have a supervisor thing, keep the high-level context and then the implementationThariq Shihipar [00:44:21]: YeahSwyx [00:44:22]: Detail in another agent.Vibhu [00:44:23]: I feel like a lot of this abstracts away as models change? The, like, half an hour ago you said bitter lesson of harness engineeringThe Bitter Lesson of Harness EngineeringThariq Shihipar [00:44:31]: YeahVibhu [00:44:31]: And we're on the other extreme right now, I feel.Swyx [00:44:33]: Well, so yeah, exactly. If everything's customizable, what is Claude Code, right?Thariq Shihipar [00:44:37]: Yeah.Swyx [00:44:37]: And which I talked to you about last night.Thariq Shihipar [00:44:40]: Yeah, I think that this is. I think the bitter lesson is unintuitive? In terms of like. Also, like we're misusing a little bit of the bitter lesson here where it's like, it's more about like scaling and compute and stuff. But like, I think there is something where it's just like. I think I use it as an approximation here to say that harnesses go out of date very quickly? And like how, but how they change is unintuitive? And so like the big obvious example is like from chat to like agents where you had to give them entirely new tools, right? But like, I think this new version of like, oh, it can modify its own harness, right? This is like, an own harness loop is like a way of using its capabilities, right? Or like it can build an artifact. And like, I think the way I think about it is like the models have more and more intelligence, and they're like so much more intelligent now than like the average software engineering task. Like, you look at the like terminal bench ones and they're like solve like the Jacobian conjecture. Not really, but like, it's like they're, they're quite complex. Like, I would not have been able to do this really as a software engineer.Swyx [00:45:42]: And you said TB4 or TB2?Thariq Shihipar [00:45:43]: TB3. TB3.Swyx [00:45:44]: TB3.Thariq Shihipar [00:45:44]: Yeah. They're quite complex, but the goal is still to deliver user value, right? And like you said, there's like this infinite space of things to do. And so the ways like you spend compute are to keep the user in the loop and make sure that like you're getting to the right decision in the end of the day and like the right output. And artifacts and mods are this way of like spending that intelligence. and I think that's like, yeah, the next step. And so, yeah, I think Claude Code is like, has the core things of agent loop which are, have gotten more complicated. It's like, it needs a sandbox to operate safely. It needs auto mode to like make sure like the permissionsVibhu [00:46:21]: Approvals.Thariq Shihipar [00:46:21]: Yeah, approvals. it needs computer use and MCPs and like all of these like ways of accessing your data, and it needs web search and web fetch. And like, so the-- as the models can do more and more, the core harness has to be like quite complex and very secure. But then like how you interact with it can change quite a lot.Vibhu [00:46:42]: What other harness engineering best practices have you, from the Claude Code team itself? I feel like, there was a phase of plan mode, which is not as used. We now have auto mode. at a point you cut the majority of the system prompt, you got rid of examples. What other best practices are there for harness engineering?Core Harness Primitives and Managed AgentsThariq Shihipar [00:47:02]: I think there is like a forking path where at some point, eventually, yes, the model will just be able to like vibe code the exact version of Claude Code, even describing all this complexity that I've talked about, right? Like auto mode and computer use and stuff. Eventually, the models will just be able to do that in one shot. But I think they can one shot simpler harnesses? And so like, I think some people. Sometimes you don't need this full, like if you don't need computer use or like all this like more complicated stuff. I think before we, you had to use things like the agent SDK, which was like Claude Code wrapped, in order to like. And I would, like suggest people do that because there was so much complexity into building a harness. And now as that's got more abstracted, we have like, Claude managed agents, which lets you have that complexity, but still like, right, like a very bare bones like harness that's scoped to your task. Yeah, I think there's like this barbell effect where like for like very complex, for like coding task and like these like complex things, you should use our harness. And then for like a lot of like simpler or like, more domain-specific things, you can build your own harness because Claude has gotten better at building harnesses, and we have these harness primitives like managed agents. So yeah.Swyx [00:48:18]: Yeah. Is there a general progression? Let's say chapter one was ultra code dynamic workflows, then chapter two was cloud mods. Where is this going?Swyx [00:48:29]: Where you're, you're, you can customize the thing on demand.Thariq Shihipar [00:48:36]: Yeah. I do think that like this evolution of projects and like artifacts and splitting out like brain and hands and, surfaces is like where things are going more. And like, I think it's like not all quite there. partially it's like a, it's just like more token expensive? And like, I think likeProjects, Local Hands, and Cloud-to-Local HandoffsSwyx [00:48:59]: Why would projects be more token expensive? I understand mods would be slightly more token expensive. No, not something I'm worried about.Thariq Shihipar [00:49:06]: Yeah.Swyx [00:49:06]: But whatThariq Shihipar [00:49:07]: You're asking Claude to do. It's like creating loops. Like you're asking Claude to do more work for you. And so like it's managing the sub-agents and reviewing it, versus where you would be doing that work normally. And so that's like gonna be a little bit more intensive, like. Outputting to an artifact is gonna be a little bit more token-intensive than, like, outputting normally. I don't think it's too much more, but like, it's like combining all of these together well, like I think we're, we're still working on like local hands and things like that, I think is like, yeah, where things are headed, yeah.Swyx [00:49:37]: Yeah. Claude and local is, handoff is very interesting. I was thinking about this as reverse cloud remote.Thariq Shihipar [00:49:44]: Yeah.Swyx [00:49:45]: Because it's like remote, it's you're handing off to cloud, but here the cloud is handing off to local, right?Thariq Shihipar [00:49:49]: Yeah, exactly. Yeah, remote control is also another way of doing it. And I do want to say this is like how I think about it and like what the things that I'm most excited about this, but like there are, just like lots of different ways to work with Claude. Like some people use remote control a lot, some people use Claude Code on the web a lot. Obviously, like at Anthropic, we use Claude Tag a lot, and like what's great about Claude Tag is we set up all this stuff for our own execution. And I do think if you're an enterprise, that's still the best way to go. but if you're like an individual, Projects is this way of like, getting some of that like niceness of Tag, which has like that like supervising agent and yeah, adding artifacts and stuff, but like without having that whole like admin setup. And so there will be many ways to use Claude, I think. I think it's probably not just one like single.Claude Tag as an Organizational HarnessSwyx [00:50:36]: You had the multiplayer thing here. Let's, let's just check in on Claude Tag. it's been about two-plus months. Lots of, public, adoption and trying it out.Thariq Shihipar [00:50:45]: Yeah.Swyx [00:50:45]: What's new? What's, what have you found since the launch?Thariq Shihipar [00:50:49]: Like, Claude Tag is how we useSwyx [00:50:51]: It's like 80% of your

Getting started with Claude Code and agentic AI doesn't require a technical background, as Henry Lopez and applied AI specialist Colin Rhoades explain the shift from AI chatbots to AI agents that complete tasks for your small business. Show Notes Page: https://www.thehowofbusiness.com/622-claude-code-agentic-ai/ You don't need a technical background, or to have ever written a line of code, to get started with agentic AI. Henry Lopez is joined again by his son-in-law Colin Rhoades, a corporate AI and data analytics specialist, for a primer on the shift from AI chatbots to AI agents that can actually get work done for your small business. Most business owners have tried ChatGPT, Claude Chat, or Gemini by now, and those tools are genuinely useful.  But there's a newer, less familiar layer: Agentic AI, tools that don't just answer a question but go do the work to implement it. Understanding the difference, and knowing how to take the first step, matters right now, because the businesses that start experimenting are the ones that will get the leverage first. Colin's analogy captures the shift well: chatbot AI is like having a very smart consultant or research assistant at your fingertips, while agentic AI is more like giving that consultant a desk, access to your tools, and an assignment to go do. An AI chat gives you answers. Agentic AI gets things done. The clearest example in the episode is Henry's daughter Makena's business, Final Curtain Finishing, a needlepoint finishing service with a Shopify ecommerce site. Native Shopify isn't built for configured products, so the site needed custom HTML code. Makena has no coding background, but using ChatGPT and then Claude Code, she generated that code herself with plain English instructions. This was work that otherwise would have cost thousands of dollars in outside development. Now that Claude Code is connected directly to her Shopify account through a connector, it can read the site's configuration and make changes on its own based on her instructions. That connection is the real unlock: Agentic AI plugged into or connected to your systems (a CRM, email, a Shopify store, QuickBooks) can do its own lookups and extracts instead of you exporting reports and pasting screenshots into a chat window. Colin saw this firsthand the first week he connected Claude Code to his company's CRM: the manual process of finding a report, exporting it, and cleaning the data disappeared, and he could go straight to deciding what the data meant. But getting started doesn't mean diving in blind. Henry and Colin both stress starting with controlled access and a human in the loop, the same way you'd onboard a new employee, and expanding autonomy only as trust builds. As Colin put it, "the goal isn't AI can do everything, it's having an AI that you can trust to do one defined task well." And getting started is simpler than it sounds: pick one repetitive task you already understand, document it (even just by speaking it into Claude), and teach the AI that one process first. This episode is hosted by Henry Lopez. The How of Business podcast focuses on helping you start, run, grow and exit your small business. The How of Business is a top-rated podcast for small business owners and entrepreneurs. Find the best podcast, small business coaching, resources and trusted service partners for small business owners and entrepreneurs at our website https://TheHowOfBusiness.com

A change to Microsoft 365 so big that Microsoft dropped the 365 and changed to Microsoft Copilot, in more places that one. The super-app is was announced, combining Chat, Cowork, Code, and Autopilot. Daniel and Darrell still managed to find some significant updates that didn't involve Copilot this week. HTML support in SharePoint and changes to Planner meeting plans. 0:00 Welcome Message title and number 2:49 Microsoft OneDrive: New pay-as-you-go storage billing option - MC1477185 7:25 Microsoft Copilot: New ways to work across Microsoft Copilot and Microsoft 365 - MC1479277 17:13 Microsoft 365 Copilot: Updates to the Researcher experience - MC1476269 24:14 Spell check before sending emails in new Outlook - MC1479509 27:16 SharePoint: HTML pages - MC1479517 33:01 Microsoft Planner: Meeting-created plans will expire after 180 days of inactivity - MC1479508

DHH took the Rails World stage to announce that he and Basecamp are no longer writing code by hand, wouldn't necessarily recommend Rails for a new app, and are going all in on native. That kicks off this week's big question: in an era of agentic coding, do frameworks still matter? We also dig into Safari 27's WebKit release, which is packed with a Safari MCP for agents, customizable selects, the HTML model element, and a pile of CSS improvements. In Lightning News, GitHub Copilot's runtime moved to Rust, and OpenAI's agents hacked an Australian government Medicare portal.Timestamps0:00 - Intro2:36 - DHH's Rails World Keynote12:28 - Do frameworks matter anymore?19:50 - Safari 27 WebKit updates37:32 - GitHub Copilot's runtime migrated to Rust39:23 - OpenAI agents hacked an Australian government website44:30 - What's making us happyNewsPaige: Safari 27 WebKit updatesJack: Do frameworks matter anymore?TJ: DHH's Rails World KeynoteLightning NewsGitHub Copilot's runtime migrated to RustOpenAI agents hacked an Australian government websiteWhat's Making Us HappyPaige: Star Trek: Strange New Worlds TV seriesJack: Learning Blackbird on guitarTJ: Ted Lasso TV seriesThanks as always to our sponsor, the Blue Collar Coder channel on YouTube. Join us in our Discord, explore our website and reach us via email, or talk to us on X, Bluesky, or YouTube.Front-End Fire websiteBlue Collar Coder on YouTubeBlue Collar Coder on DiscordReach out via emailTweet at us on X @front_end_fireFollow us on Bluesky @front-end-fire.comSubscribe to our YouTube channel @Front-EndFirePodcast

In this episode of the Master.dev podcast, Dustin Tower, VP of Learning, sits down with Leah Thompson, DevRel and community engineer at Laravel and Twitch streamer (LeahTCodes), to talk about developer relations, learning in public, and how community can launch a tech career.Leah shares her non-traditional path into software: from a pure mathematics degree and a stint teaching high school math, to the free 100Devs bootcamp, to her first job as an HTML email developer. She explains how a free Laracon US ticket and a message to Taylor Otwell led to a job at Laravel just months later. Along the way, she talks about why teaching is the fastest way to learn, how streaming prepares you for conference speaking, and why being authentic is the key to building an audience.Leah also digs into the Laravel stack (React, Inertia, Laravel, and Tailwind), why Laravel's opinionated structure works so well with AI coding agents, how Laravel Boost helps close the context gap for models, and her advice for beginners learning to code in the age of AI.If you're interested in Laravel, developer relations, conference speaking, learning in public, AI-assisted development, or breaking into tech without a traditional CS degree, this conversation is full of practical insight and encouragement.#Laravel, #DevRel, #Inertia, #AI, #WebDevelopment, #LearnInPublic, #PodcastCheck out Leah's Master.dev Course: https://master.dev/courses/laravel/?utm_source=youtube&utm_medium=home_link&utm_campaign=leah-podcastFind Master.dev Online:Twitter: https://twitter.com/MasterDotDevLinkedIn: https://www.linkedin.com/company/masterdotdev/Facebook: https://www.facebook.com/masterdotdevInstagram: https://instagram.com/FrontendMastersAbout Us: Master AI & Full Stack Development with in-depth, modern engineering courses. Our 300+ high-quality courses and 24 curated learning paths will guide you from mid-level to senior developer, frontend to backend, and everything between. Start your path to mastery today: https://master.dev/?utm_source=youtube&utm_medium=home_link&utm_campaign=leah-podcast

Se hai mai sviluppato un prodotto digitale, saprai che la differenza tra un buon prodotto e un prodotto venduto è spesso la comunicazione. Ma cosa succede quando devi scrivere manuali utente, tag per immagini e pagine web promozionali per un software complesso? È qui che l'Intelligenza Artificiale si trasforma da semplice assistente a vera e propria macchina produttiva di contenuti.In questo episodio di Tecno Pillz, Alex Raccuglia porta il pubblico attraverso un viaggio incredibile: come ha utilizzato prompt avanzati, visione artificiale e modelli LLM per automatizzare ogni aspetto del marketing e della documentazione delle sue applicazioni. Scopri come passare da un semplice screenshot a una pagina web ottimizzata per ogni singolo dispositivo, sfruttando il potere nascosto del codice e dell'AI. Se possiedi un prodotto e senti che la comunicazione è il tuo collo di bottiglia, questa puntata è la tua mappa per l'autoproduzione di contenuti di livello mondiale.

The Fork In Your Ear Ep#222 "Ionic The Hedgehog" - Podcast Show Notes & Summary 9-26-26 Tim and Nate spend the first ten minutes fighting a Discord refresh, a hiss they blame on forced suppression, and a Windows accessibility crosshair that PowerToys cannot kill. Then the ring lands on Life: first day of fall floods Tim's plugged gutters, a USPS driver does an Austin Powers turn in his driveway because Washington will not let carriers reverse more than a foot, and Nate trades a Mustang insurance bill for a 2019 Hyundai Ioniq they immediately name Ionic the Hedgehog. Dream Nate gets a tattoo without telling Mrs. Foo. Amazon cargo e-bikes with fake pedals unload patio furniture in Burbank heat. Games dump after the last episode posted — Diablo 5, StarCraft Dominion, more No Man's Sky, Famitsu wishlists, Kojima's canceled Metal Gear-shaped "Fizzint," Bungie saying "we're listening" again, and Xbox shoving Halo under an Activision Call of Duty team while Halo Studios shrinks to "community support." Tim's HTML RTS playtest is up to 0.58 with dumber-AI rehab. Tech is iPhone Duo vs Z Fold 8 and a missing telephoto that keeps Tim off the fold. Entertainment is Lanterns going feral, Mayday being exactly Ryan Reynolds, Paramount-Warner getting waved through, Darkwing Duck coming back without Jim Cummings, Kara's Spaceballs DVD, and a Reddit stranger who archived Wizard's Rule episodes 0–40. Get forked.   Detailed Show Notes  

Earlier this month, world model company Runway introduced GWM Worlds 2, a research preview that “turns high-fidelity video and audio generation into real-time interactive simulation.” Runway calls this an “autoregressive diffusion” model; with autoregressive describing how it generates over time.One new feature in particular caught our eye: WorldPrompt, a proposed input format for specifying a generated world and the actions within it. It allows you to fix some aspects of a simulated environment — including the first frame — and then create a series of timestamped events. The events, or actions, can even be prompted in real-time.To understand the implications of WorldPrompt, we spoke to Kamil Sindi, Runway's CTO, and Robin Kahlow, its Principal Research Scientist for generative video and multimodal AI. We also have exclusive comments from Anastasis Germanidis, co-founder & co-CEO of Runway, courtesy of a podcast swyx and Vibhu did with him.Who's building real-time interactive world models?First, some context about world models that can generate interactive video and audio in real-time.Runway is reportedly valued at $5.3 billion, based on its most recent fund raise of $315 million in February. Its first release, GWM Worlds, was launched last December.Alongside Runway, there are several other notable projects in this domain: Google DeepMind's Genie 3 (which also generates at 720p and 24 fps), Odyssey-2 Pro, and World Labs' RTFM (Real-Time Frame Model). We've summarized their differences in the following table:Given the complexity and massive latency demands of real-time video and audio generation (which we'll get into below), all of the projects listed above have limitations. For instance, Google notes that Genie 3 “can currently support a few minutes of continuous interaction, rather than extended hours.”But as our interviews with Runway show, real progress is being made.The central idea of WorldPromptWorldPrompt, a new feature in GWM Worlds 2, helps differentiate Runway from its competition. You can think of it as a control layer for characters, cameras and the environment. As Kahlow put it, it's a way to “control all the different subjects in the world” — similar to a computer game.“Like, if there's an NPC [Non-Player Character] somewhere, the NPC might walk up to you and say something. So you could achieve the same thing with this kind of model, where you can have very detailed control over everything in the scene.”As the name suggests, WorldPrompt is a prompting mechanism — not a programming language. So, unlike virtual world games like Minecraft or Roblox, GWM Worlds 2 doesn't offer scripting capabilities or the ability to control state. But there's a power to that, as Sindi pointed out.“You can create promptable worlds on-demand with video and audio in sync, across all these different domains and environments. That's not a distant-future hypothetical thing,” he said.But there are also limitations to prompting a world model. We asked how reliably the model would follow an instruction to create, for example, a law of gravity or a certain ability in a character?“Yeah, so it's a research preview,” Kahlow replied. “So it's not perfect, of course, and there are still flaws. It really depends on how difficult the action is. I would say movement works quite reliably.”Sindi added that more training plus scaling the data and models is resulting in “better following.”How a video model becomes a real-time runtimeDespite the current limitations of GWM Worlds 2 — especially if you compare it to pre-designed and scriptable worlds like Minecraft or Roblox — the true promise of world models like Runway is that they'll eventually lead to fully self-generated, real-time games and experiences. Which is an extremely hard engineering problem, as Kahlow reminded us.“There are two challenges. One is making the model not generate a whole clip at once. So instead, you want it to generate frame by frame while you're looking at it. And the other challenge is actually making the generation fast, so you can play it in real time.”GWM Worlds 2 offers real-time interactive worlds streamed in continuous 720p video at 24 frames per second (fps) and audio at 48,000 Hz.Runway achieved this firstly by taking its foundational audio-video generation model and fine-tuning it to the new WorldPrompt format, so the model can follow that. It then post-trains the model to generate autoregressively.“And after that, we work on making it real-time through distillation methods,” Kahlow added.Co-CEO Anastasis Germanidis offered more technical details in our podcast with him. He told us that the process starts from “bidirectional diffusion that basically generates an entire video at once and [makes] it autoregressive.” This allows the model to “generate one frame or a few frames at a time.”Germanidis described two possible forms of distillation in order to make it real-time: distilling a larger model into a smaller one or reducing its diffusion steps. As a general example, he said a model might go from around 50 denoising steps to four, with some quality loss but potentially comparable results.The challenges of real-time generationGermanidis admitted that there were issues with how it generates real-time interactive video.“The biggest challenge with autoregressive models is error accumulation,” he said. “You're feeding generated frames back into the model to generate the next frames, and if there are any small errors, they accumulate over time.”Sindi told us there are also challenges dealing with “infinite generations” of content.“There's all these challenges around what context to keep, what to discard that's not important. And so there's all these optimizations we have to think about, so we're not blowing up our GPU memory.”Another current limitation is long-term memory. “The model does not have perfect memory,” Kahlow said. “That's still an open research problem.”Causality and correctnessWhile performance is the primary challenge for Runway at this time, its world model also has to produce plausible consequences when a user takes different actions.Germanidis used the example of simulating football; he pointed out that online video training data contains more successful goals than failed goal attempts, so a video model might render the first more convincingly.“If I take this action versus this action, you want it to generate equally realistic outcomes,” he told us. “That's, I think, the big gap between video models and world models: that idea of counterfactual generation.”Sindi told us that evaluation gets harder the more complex interactions get.“If you have this multi-prompt, multi-character, multi-scene [environment], how do you really understand what was causal and what was not?”To try and solve that, Runway has some automated verifiable tests. But since GWM Worlds 2 is a research preview, Kahlow noted that doing tests yourself is also advisable — “trying out your model to see what doesn't work is really important.”More than gaming — there are agent use cases tooGaming is the obvious use case for what Runway is building, but there are others. Kahlow mentioned robotics — for example using a simulated environment to test how a robot works.Another, more intriguing, use case is to use it to test agents at scale.“Having thousands of simulated environments is much less challenging if you have a suitable model like GWM Worlds,” Kahlow said.But how does an agent know what's changed in the world — is there a structured state that it can read, or is it just the generated video and audio that it's consuming and understanding?“So there's no structured state here,” Kahlow replied. “It's just observing the same thing you might observe in real life, just [in this case] from cameras.”Sindi noted that GWM Worlds can also be used for “synthetic data generation for agents.”Finally, Germanidis suggested there's potential to use these world models alongside reasoning models.“You're maybe using some reasoning [for] planning of the scene, and then you're passing it into the diffusion head that's actually generating the pixels.”Anastasis Germanidis* LinkedIn: https://www.linkedin.com/in/agermanidis/* X: https://x.com/agermanidisTimestamps00:00:00 Introduction00:05:17 Runway's Origins and the Bet on Generative Video00:12:23 The Stable Diffusion Story00:18:44 Gen-2, Controllability, and the Weekend Hack00:23:02 From Video Generation to World Models00:28:03 Learning From the World, Not Just Language00:35:04 Sora, Runway's Existential Crisis, and Gen-300:39:39 Why Real-Time Video Is Inevitable00:43:06 Interface World Models: Software Without Code00:50:25 The Fully Neural Operating System00:55:11 World Models for Robotics01:02:32 Robot Policies and World Action Models01:07:47 The Lucid Dream Test01:11:41 Video Agents and Omni Models01:23:12 Artists, AI, and Creative Workflows01:27:14 Physical AI and the Future of World ModelsTranscriptIntroduction: Runway, Creative AI, and the Early ThesisSwyx [00:00:00]: Okay, we're here with, Anastassios from Runway, with, me and Vibhu in the studio. Welcome.Anastasis [00:00:08]: Good to be here.Swyx [00:00:09]: Congrats on all your success and progress with Runway. You're opening offices all over the world. Did you envision this when you first started out?Anastasis [00:00:16]: Not quite. I think even when we started, we had this idea that, It was more a matter of when, not if, we were seeing the early generative models of 2016, 2017, and just extrapolating, assuming, we resolution, quality increases predictably over time. There's gonna be a point where most of content will be generated, and that was maybe the initial thesis of Runway was we will need, as a result of those generative models, rethink how creative tools are made. and as we built out the research behind, our generative models, it then became clear that they were useful far beyond that as well.Anastasis' Background: Art, Simulation, and Machine LearningSwyx [00:00:57]: And it is more obvious now with, like, the real-world stuff and the world models that we'll talk about later. I'm just kinda curious how you go from a background in, like, Zocdoc and, computer vision into Runway. Like, take us back to that early conversations with Chris and, whoever else is on your founding team.Anastasis [00:01:14]: I was always splitting through those two worlds. One was the I had my own art practice. I was making a lot of interactive art, I think for a long time. and then on the other side, I was working in startups, and I was working as a ML engineer, as a backend engineer at different companies. I've always been interested in, coding and computation, and especially interested in simulation and brought it back into my early artwork as well. And at the same time, I was interested inSwyx [00:01:43]: The personal site has a few, right?Anastasis [00:01:44]: Yeah.Swyx [00:01:45]: Is there one that we should pull up? Just in case there's something that's like. I just like to go down memory lane.Anastasis [00:01:50]: Yeah.Swyx [00:01:50]: Okay, what is this?Anastasis [00:01:51]: So this was, a project that I made, I think back in 2015, where I built this software that would give, voice instructions to people in a gallery space. So it would coordinate interactions between people. And so it will first give you an identity, like you're an, architect, you're 30 years old, and, you like sports. and then it would match you with another person, and you have this completely generated interaction. language models were not quite there at the time, and so it was it was a mix of some templates and some, like, some Markov chain-generated text, and it would just completely simulate these small talk conversations between, everyone in the gallery space. so was always very fascinated on the one hand with, generative models and, like, the early machine learning work that was being at that time. But at the same time, there was this separate thread of simulation and what it means. Like, what can we learn about humans by creating those very simple models of their interactions and their behavior?Early Generative Art: pix2pix, GANs, and Uncanny ValleyVibhu [00:02:56]: Did you generate the prompts or, the 30-year-old, whatever? Was it you generating them? How'd you, how'd youAnastasis [00:03:03]: Exactly. So the program would just generate- those, from. Yeah, a lot of it would be Mad Libs style of justVibhu [00:03:10]: YesAnastasis [00:03:10]: You have lists of different professions, lists of different,Vibhu [00:03:14]: HobbiesAnastasis [00:03:15]: Personality types, lists of different, ages, things like that. And then it would just combine those things together. And then maybe the next project we go is, Uncanny Valley, Uncanny Road, which wasSwyx [00:03:27]: GansAnastasis [00:03:27]: One of the first projects that, we built with, one of my two co-founders, Chris. This was taking, pix2pixHD, which was one of the early image-to-image models that NVIDIA released back in 2016 or 2017. and it was a model that would take a semantic map of a scene and then generate a photorealistic, let's call it, output. very early days, so it was not very high-fidelity outputs, but it w I think was the first image-generation model that could generate at 1K resolution. And it was all trained on self-driving datasets. So the semantic categories it would support were only, things you would encounter on the road. So it would be pedestrians, traffic signs,Vibhu [00:04:16]: StoplightsAnastasis [00:04:17]: Bikes, stoplights. And so that was one of our first indications that we built this and people were making all this, like, very surreal imagery of, yeah, a million plus a million pedestrians or a million traffic signs or, like, gigantic humans. And it was a indication that you could take a model that was trained on this very boring dataset, essentially, of, like, not that many interesting things happen when you're on the road, and then you can repurpose it and go very out of distribution and make something that was artistically compelling. And that was It's a summary of the thesis of Runway in some ways, that you can take the same generative models, and if you look at them from another direction, if you build interesting tools around them and you give them to artists, they're gonna do things that you don't expect.Vibhu [00:05:02]: Very cool. I like the, UX of it. You're just given an empty canvas, try whatever, do whatever. And then the other one, like, you see everyone with wired headphones? Like, that's, that's a sign that it's, it's veryAnastasis [00:05:16]: The AppleVibhu [00:05:17]: YeahAnastasis [00:05:17]: Apple, your version.Vibhu [00:05:17]: Original ads. Yeah. Take us to today. You've been doing this for seven years at Runway. How have we got to this? Like, how do we go from driving simulator data to all this? And you cover the whole stack of generative media?From Creative Tools to a Research LabAnastasis [00:05:33]: Interestingly, we're almost back in, we're, we're full circle. We're, we're now applying our models and beyond creative tools into real-world scenarios. But it was a, it was a long journey. It was very early on we realized the first version of Runway was a way to easily use the, all the open source model of the day, things like pix2pix to. and give them to artists. That was the initial idea, is those models are too difficult to use if you're not a machine learning engineer. Like, what happens when you give them to artists? Very quickly, we realized we needed to build a research org, inside of Runway, and that happened maybe on year one. And, a lot of the mandate there was. The image-generation models of the time, the video generation models of the time, or there were barely any video generations all the time, but they were not quite there where they could be productionized and brought into tools that would be part of creative workflows. so we need to push the frontier of the research. And so maybe the first four years of Runway, research was almost happening on the background until there was a moment in 2022, with latent diffusion, with, DALL-E 2, where, there was that step function change, and you guys maybe remember around the time.Swyx [00:06:49]: I started in this space because of latent diffusion and Stable Diffusion.Anastasis [00:06:54]: Yeah.Swyx [00:06:54]: Because I was like, “Wow, this is not only, like, feasible, it is doable on consumer hardware.”Anastasis [00:07:01]: Exactly, yeah.Vibhu [00:07:01]: I think the delta is also huge. Like, I learned pix2pix. Like, this was intro to ML, the TensorFlow, like, Jupyter, Google Colab notebooks were like this, and then you have a sudden step function change, with diffusion and whatnot. Any other ones since that. Like, there were clear examples of what early diffusion were to get to here. Any other changes in key technology research?Green Screen, Rotoscoping, and Early RunwayAnastasis [00:07:26]: Between, 2018 when we started and 2022?Vibhu [00:07:29]: Yeah.Anastasis [00:07:29]: So one of the early work that we did in Runway was solving segmentation, image and video segmentation. It was a very important problem because most VFX involves essentially separatingSwyx [00:07:42]: RotoscopeAnastasis [00:07:42]: Subjects. Yeah, rotoscoping. Extremely manual process. Nobody enjoys doing that. and so a lot of the early days of Runway was building this tool. It was called Green Screen, and it was for a long time the main thing that people were using Runway for. It ended up being used in, Everything Everywhere All at Once and a bunch of other high-visibility films and series. But that was essentially, Runway for a long time was a post-production tool until latent diffusion and generat- Gen-1, Gen-2, happened.Swyx [00:08:12]: Cool. let's, let's go past that moment. You've come a long way. Then you started releasing your own models. Maybe describe that journey as well.Scaling Video Models and the Bet on 1,000 A100sAnastasis [00:08:20]: Yeah, so we go to the other point, yeah, in mid-2022 when it became clear that we're doing research at a fairly small scale of compute, and it became clear that, like, scaling laws would apply to, image and video gen in the same way that we're applying to language generation. So we made a big bet, and I think at so at the time, we signed this deal to build a cluster of a thousand A100s, which at the time we were a Series B startup. That was a almost, slightly irrational decision maybe, but we really believed that if we trained a video model at a large scale, we would get, like, a great model at the end. And at the time, the goal or we set the goal around fall of 2022 of what is, what does the latent diffusion, Stable Diffusion moment look like for video? And at the time, the best model of the time was called CogVideo. it was one of the early video models. It was very 256 by 256 resolution, very not very high quality. and so we decided we're gonna build out this cluster, and we're gonna just invest in, like, in building out our own video model. it became clear as we're training Gen-1 that it was difficult to get to fully. we wanted to build text-to-video, but it became clear to us that an easier starting point would be to start from video to video. Because when you have a stronger conditioning, it's, it's an easier problem to restylize an existing video versus generate the video from scratch. And so we released Gen-1 first back in, it was January of, 2023. Yeah.Vibhu [00:10:04]: It's just a fun visual podcast, honestly. Like, if we can see February 2023, what was the state of stuff?Gen-1: Video-to-Video and Depth ConditioningAnastasis [00:10:10]: It's so interesting ‘cause at the time when you see those results, you think this is so incredible, and this is like, it's almost like image generation or video generation is solved. And then you look back a few years after, and it's like, it's It's just like you get used to the results very quickly, with those models. But at the time when we started seeing those results, it was, it felt quite incredible, and the level of, like, quality that you could get. And, so the Gen-1 was a depth-conditioned video model, so it would turn. it would take a input video, it would predict. it would it would first convert it into the depth map, and then we would generate, pixels with a latent diffusion model.Swyx [00:11:01]: Yeah, very effective.Vibhu [00:11:02]: Yeah. I didn't realize how distracting the blog post would be. Sorry.Anastasis [00:11:05]: Yeah, but, one of my favorite examples of on those, on Gen-1 was both, if you go up to mode three or mode two, there was this storyboard use case where people would makeVibhu [00:11:18]: OohAnastasis [00:11:18]: WouldVibhu [00:11:20]: You can mess around with theAnastasis [00:11:20]: Make a city out of books or out of boxes, and then they would shoot a video with their phone and then translate it into a photo-photorealistic output. There was all these ways in which those models were starting to be used for storyboarding and also for really. and then if you go to mode four, like, of taking untextured 3D scenes and then turning them into photorealistic output. So we saw a lot of use cases early on where people that were familiar, were power VFX editors would just take a blender, render, and then they would get translated in with Gen-1 or create a scene in Unity and then take a capture a video of it and then translate into, restylize it. So I still think video to video is powerful. I think we had a recent video-to-video model as well, and it's one of my favorite ways of using those models is essentially using them to use ground truth video as, like, the initial inspiration and then translate into different styles or different outputs.Stable Diffusion, Stability AI, and Open SourceSwyx [00:12:23]: But I think we're gonna go into, like, the rest of Runway and catch people up to speed today. I did wanna cover the, let's call it the Stable Diffusion controversy, or, what happened with Stability AI, whatever. I think there was a two sides of the story. I think there's part of that is a normal thing of, like, people, join and leave companies, but what is the, retrospective now that, there's been some years behind it?Anastasis [00:12:49]: Yeah, it's a very, it's a very long story to go into. I think it wouldSwyx [00:12:53]: Which I remember you wrote a really long post about.Anastasis [00:12:56]: We would probably cover the whole hour to go into it in more detail. But, essentially, there was the latent diffusion paper that came in, I think that was at the end of, 2021. And then Patrick Esser, who was one of the researchers behind, latent diffusion, and he worked at Runway at the time, he built latent diffusion in collaboration with Robin Rumbach and a few other folks back, in the in, CompVis, which was, a labSwyx [00:13:26]: Like a research group, yeah.Anastasis [00:13:27]: And, after releasing the early latent diffusion model, they, essentially they were. the goal was to keep working on versions of the model, scale it up, incorporate new data, incorporate new tasks. And Stable Diffusion was the same model, but trained on more compute, and then with a few more tricks, like a classifier-free guidance paper came at some point, I think in the early 2022. And thatSwyx [00:13:52]: Which, like, was a big prompting improvement.Anastasis [00:13:55]: Yeah.Swyx [00:13:55]:?Anastasis [00:13:56]: That improved results. it was trained on better data, so like, the esthetic subset of LAION, but it was effectively, the same underlying architecture. And there was that big training run, that, happened on Stability's cluster. Stability financed that run. And looking back at that story, I think it was the work to build and train that model was done. It was a, it was a research project. It was done as part of, like, continuation of the latent diffusion work. It then, I think it the model became very successful, and it, I think there were the. And I think as a result of its success, other companies tried to, figure out the commercialization path for it. But for us, it was very important that we try to, we make sure that we. It was meant to be an open source research project, and so the we decided that we should continue releasing versions of it, since that was the original goal of Stable Diffusion, and that led to releasing Stable Diffusion 1.5. There was maybe a day of, a bit of, miscommunication there, but ultimately that was resolved very quickly within hours. so yeah, there wasSwyx [00:15:12]: OkayAnastasis [00:15:12]: Not a niceSwyx [00:15:13]: I just wanted to. you have toAnastasis [00:15:15]: Yeah.Swyx [00:15:15]: You're one of the main players in that journey, and so it's nice to hear from the source of, like, what happened. Yeah.Anastasis [00:15:22]: Yeah. I think it's all, it's all in the past nowSwyx [00:15:26]: YeahAnastasis [00:15:26]: I would say. and, like, both companies, Stability took its own path, Runway took its own path.Swyx [00:15:32]: Yeah. There's still. James Cameron is backing the new Stability, whatever they're doing with the Hollywood studios.Anastasis [00:15:38]: Right.Swyx [00:15:38]: I don't know what they are doing. I think one thing that impresses me, and I'm happy to move on, is that back in the that time, let's say, like 2021, 2022, there was this community of people that you were involved in that was researching all this stuff, right? And, like, from everyone I talked to who was active then, it seemed like it was fairly obvious that somebody would do the hero training run that would produce Stable Diffusion. So, like, I guess the question is, like, you had the you were you had made investments. You were you had the foresight. Is it accurate to say, like, that is reflective of, like, what people were thinking at the time? Or was it still very much like, “Well, we'll use it as, like, a post-production tool or something. I don't know.”? Like, where in the sentiment were we that maybe you can think back to, like, what the community was like back then?The Early Creative AI CommunityAnastasis [00:16:28]: I reminisce and I think very fondly those early years, from like 2018 to 2022, because it was a very small community that, as you said, were very convinced that this was gonna be a big thing. And at the time, anyone who. Because it was such a small circle and, everyone who would, like, be part of that circle and, like, make projects with it would, immediately get, go viral. so likeSwyx [00:16:55]: And you didn't know who they are, right? They're just some name on a, GitHub or Hugging Face somewhere.Anastasis [00:16:59]: Exactly, yeah. So I remember one of the first big viral moments of creative AI was, there was the neural style transfer paperSwyx [00:17:09]: HuhAnastasis [00:17:09]: ThatSwyx [00:17:10]: Something dreaming?Anastasis [00:17:11]: I think it was called neural style transfer.Swyx [00:17:14]: Okay.Anastasis [00:17:14]: There was also Deep Dream, the puppy sliceSwyx [00:17:16]: YesAnastasis [00:17:16]: Which was, also really cool. but, yeah, there was this project that, Jim Kogan, who was an early advisor of Runway and one of those,Swyx [00:17:25]: Marketing guysAnastasis [00:17:26]: Big, creative AI, folks, he literally just, like, showed a video of himself taking the New York Subway and going over the Williamsburg Bridge and then stylized it with, I think in the style of Van Gogh or, like, one, painter. And that was. Like, at the time, that was, like, so cool and it went viral and it was completely revelation to people that you could do this with generative models. And that was only, it was less than. It was maybe 10 years ago. So just, like, as an indication of, like, how quickly things have gone.Vibhu [00:18:02]: It's pretty crazy. Like, even since then, you've got people at every level of the stack. You've got devs, creatives, artists, hobbyists. You've got everyone using it. And for people that tried stuff early, they'll remember how hard it was to use regular diffusion, right? Like, nowadays, you can use your favorite ChatGPT image gen or whatever, give a sentence, get a beautiful output. But diffusion was like, the whole ultra HD, 4K, high resolution. Like, prompting these things was very different. anything you learned on the tooling side, like from the offerings you guys have now, so like creatives, devs, you really took the. Research and brought it to everyone to use. anything interesting there to share?From Gen-2 to Controllable Video GenerationAnastasis [00:18:44]: We had to build the entire model serving infrastructure for video diffusion models. There was nothing else, already, like, because we had Gen-2 was the first text-to-video model, I think, out in the market. So many things that we learn over time. I think the I think the biggest one was, like, we. it was very clear early on that text-to-video was not gonna be the answer. Like, you. Like, people wanted a lot more control than that, and so we invested in, like, control building on top of those models very quickly. how do you use the camera trajectory as control? How do you use an initial input frame as control? So that was a very early learning for us. With text-to-video was, like Gen-2 was an amazing, step function improvement in the quality of video models, but it was used much more in an exploratory way because there was nothing to ground it to. There was no reference that you could bring into it. There was no. You couldn't really control the camera motion. You couldn't control the object motion. And so the first year, in 2023, was really all about what are all the interesting ways in which we can condition those models? And it was a lot of just post-training rounds on top of the base model to figure out, like, what, -- how do people wanna control them? And so there was, like, this quick succession of the we it was called Motion Brush, which was you could, like, you could draw arrows and dictate where things should move in the scene.Vibhu [00:20:09]: That's so cool.Anastasis [00:20:09]: There was camera control that was you could just describe, like, how you want the camera to move in the scene. And because we work with filmmakers from the most of the history of Runway, we immediately got this feedback and got this, decided that this was worth investing in. And so control ability became a big theme, I think, very early on as we were building, as we were building those models. Something fun that I haven't really talked about too much was just how Gen-2 came to be out of Gen-1. So it was a bit strange because we announced Gen-2 two months after Gen-1 andHow Gen-2 Came From a Weekend HackVibhu [00:20:43]: We're accelerating.Anastasis [00:20:44]: It was before Gen-1 was even generally available. But Gen-1 was a depth-to-video model, so it would take a depth map and it would convert it into RGB. and we couldn't get, text or image-to-video to work directly, and that's why we started from depth to video. but, and we had discussions of like, okay, we need to spend the next six months investing in text-to-video, maybe increasing the compute scale or the model scale, like train a larger model. And I had this weekend project idea, which was, what if I take a model that, starts from text input and converts to depth maps and then use Gen-1 to convert the depth maps Into RGB?Vibhu [00:21:29]: It would probably work.Anastasis [00:21:30]: And so Gen-2 was that.Vibhu [00:21:32]: Oh. The hackathon pipeline.Swyx [00:21:35]: The weekend hackathon pipeline.Anastasis [00:21:36]: Yeah.Vibhu [00:21:37]: But it looks good.Anastasis [00:21:38]: And it worked pretty well. there were if you, with the knowledge that it has this, like, two-stage pipeline, you can tell in some cases that the structure of the video looks a bit off because you had to generate the depth first before you go into the output video. But it worked and it allowed us to bring this to our, to users very quickly. But it's now it's interesting because, like, people are coming back to this almost two-stage approach. Like, if you look at the Reve text-to-image model that came a few months ago, it had this planner model that would generate bounding boxes before it fed that into the diffusion transformer.Swyx [00:22:19]: Yeah, Ideogram also the same day.Anastasis [00:22:22]: Yeah.Swyx [00:22:22]: I remember that was very strange that both of them came out the same day with the same exact innovation.Anastasis [00:22:26]: It's a small community, I think.Swyx [00:22:28]: I'm like, this is like, this is completely coincidental, right?Anastasis [00:22:32]: People talk. So yeah, there's, there's definitely something into this approach. And, now, like every single like, video generation model in production uses a complex prompt completion pipeline under the hood. I think that's no secret that there is. ThatSwyx [00:22:48]: Humans are terrible at prompting.Prompt Rewriting, Camera Control, and the Seed of World ModelsVibhu [00:22:51]: I think across the board.Anastasis [00:22:51]: Yes.Vibhu [00:22:52]: But yeah, I think like the original Sora one blog post even told you that what happens after your input is rewriting your prompt. It's much more descriptive about what you would want.Anastasis [00:23:02]: Exactly. I, And there was the DALL-E 3 paper beforehand that, was the first public, description of the fact that synthetic captions and really detailed captions work really well. And then Sora built on that. Yeah, so it was 2023. We were releasing all these updates to Gen-2, like the camera control, Motion Brush. And there was something very interesting about camera control because it was the first time that you felt that instead of, like, you were creating video, you were creating a short video, you were navigating inside the world. And I think camera control was maybe the seed of some of the ideas that we had around world models and really opening up that research direction. We realized, it was this era and this series of, Gen-1 and Gen-2 models really proved to ourselves, yeah, this is theSwyx [00:23:56]: Cool.Anastasis [00:23:57]: So this is not the original camera control. This was the updated camera control on top of Gen-3. But yeah, I think it made those models usable to filmmakers, I would say. The so camera control was very popular. And so we realized, there is one way of seeing those models, which is, you're just as content creation machines, and there is the other way, which is you're. As you're predicting video in order to predict video well, you need to simulate the world in an increasing and increasing capacity. And if scaling laws apply on video, just like they apply on language models, then as we scale the compute that we put into those models, then they're gonna be able to simulate physics, they're gonna be able to simulate human actions and dynamics increasingly well and predictably well. That was the thesis about around our efforts on world models, and we spin up this research group to just focus on the world models and how do we turn the video generation models that we're building into something broader and something that would be useful beyond, also content creation as well.Swyx [00:25:04]: And that was roughly when?Anastasis [00:25:06]: Yeah, so that was inSwyx [00:25:06]: OhAnastasis [00:25:07]: In late 2023.Vibhu [00:25:08]: Interesting. like, I think, a lot of people have been saying a lot of video gen model companies have all pivoted to world models these days, but like, 2023, you're posting it. oneWorld Models: From Video Generation to SimulationSwyx [00:25:21]: It's, it's debatable whether it's a pivot.Vibhu [00:25:23]: Yeah.Swyx [00:25:23]: Like, arguablyVibhu [00:25:24]: YeahSwyx [00:25:24]: That's what you always had to do anyway, right?Anastasis [00:25:26]: It's in a way an expansionVibhu [00:25:28]: YeahAnastasis [00:25:28]: Of the applicationsVibhu [00:25:29]: YeahAnastasis [00:25:29]: Of the models as they become more capable.Vibhu [00:25:31]: The early signs, it seems like the original models you guy had, guys had, people would say it's very not bitter lesson pilled, right? You're adding, rewriting prompts, you're having all these one-off things, but that's just the state of the tech as it was versus the future of as you said, you can scale it up as, we can scale up to world models.Anastasis [00:25:50]: Yeah. So it just became. And if you looked at the outputs of Gen-2Vibhu [00:25:56]: YeahAnastasis [00:25:56]: It was not. I think it was not obvious to people that this would scale to become a general simulator of the world. Like, you had very limited movement, you had, very low fidelity or low resolution, like obvious mistakes in human anatomy, like all kinds of limitations. But it was just, the idea was that's just GPT-two, and GPT-two, it can barely generate, like, coherent sentences. Similar, Gen-2 can barely create coherent video, but if you scale it up, you're gonna. There is no reason why it shouldn't work in a way. It's, And I think that was. That's, that's always the mindset of Runway is like this extrapolation of, like, if, like, even when we started in 2018 and you looked at the results of the day, you need to look more at the trend of, like, where we were in 2018 versus when we were at the, when the first GAN came out in twenty, four 2014 or twenty, fifteen. And, you started from, like, thirty-two by thirty-two images of faces, and then by the time in 2018, you could generate, street images at the 1K resolution. And it was the same with world models, very early signs of something much bigger.Swyx [00:27:08]: Yeah. I was gonna say, like, it's diffusing into focus. Like, if you look at our visible output from year to year, it looks like a diffusion process itself.Anastasis [00:27:17]: Yeah.Vibhu [00:27:17]: Especially watching the early, like, old blog posts, you can really see the choppiness, the details.Anastasis [00:27:24]: Yeah. Like human civilization starting from random noise and thenVibhu [00:27:27]: YeahAnastasis [00:27:27]: Denoising intoSwyx [00:27:28]: Yeah. Just run it a hundred years.Anastasis [00:27:30]: Civilization.Swyx [00:27:30]: Yeah.Vibhu [00:27:31]: That's how you're on track, you're still noising, right?Swyx [00:27:34]: Yeah. I like the way that you guys phrased it when you, announced it in June, which is, oh, that you had a video essay. “The human mind is no longer the center of AI. Our world is.” Right? Which is, let's, let's call it the past five years of LLM-based AI is very much like trying to emulate human preferences and human speech. But now that's, like, mostly solved. I think that's, like, some of the context of your essay, which you also wrote around the time. And now it's like the focus is on modeling the world accurately.Scaling Laws for Video and Why Predicting Pixels MattersAnastasis [00:28:03]: Exactly, yeah. So the way we see it is, there is that, initial mission statement of DeepMind, which is, solve intelligence and then use it to solve everything else. But I think it's starting from everything else, could be valuable of, like, starting from. there is just so much complexity, and detail in the world that in order to. That it's, it's hard to learn directly from just human descriptions of the world. Like, we're assuming that, like, language models learn from everything that humans have written about the world, like our own understanding as of, the twenty twenties. And there is just so much that we don't know and so much that's not captured by existing text, about both the low level dynamics of the world, like we're not describing in detail. if I tell you to describe, like, how do you tie your shoes, that's a very difficult thing to describe in words, but it's very obvious thing to demonstrate. And so I think there's been. And there's, more of X paradox, like we're constantly underestimating all the complexity that goes into very, like, things that we do subconsciously as humans, and we don't even necessarily always have the words to describe them. And so in my mind, the simulating the world and simulating, physics, simulating the dynamics of the world has always been underestimated, compared to, we place too much emphasis on the things that are easy to talk about. but there is just all this complexity and richness of the world that if we just try and train directly on that observational data instead of training on how people describe the world, we would learn something new that we wouldn't otherwise know.Swyx [00:29:54]: You think that the present architectural paradigm is fine? You don't need, like, another layer, like JEPA, like another famous, New York AI leader would say?Anastasis [00:30:05]: We're a very pragmatic research lab. If, we have evidence that an approach works better than the approach that we're taking, then we have no qualms to taking it. We just have seen no indication that video prediction itself doesn't scale. And even if you look now, not just our work, but the work of others, you're seeing in robotics some of the most promising work, starts from video prediction models, and then you adapt them to also the action models, for example. so there is very little evidence that you need something else and that your time is better spent on a novel architectural change compared to improving data and improving the, and scaling the current approach. And so, We don't have any indication that. the, there is that counterargument that I think there was a tweet by Yann LeCun a few days ago that, understanding the dynamics of the world is very different than, generating, cute videos.Swyx [00:31:05]: And your answer is no, they're the same thing.Anastasis [00:31:07]: Yeah, they're the same thing.Swyx [00:31:08]: My cat videos are the same as understanding physics.Anastasis [00:31:11]: Right, because if you wanna generate. video models can cheat and, like, they could you could give, like, successive dif shots of the scene in a way that doesn't require you to simulate difficult physics. There is like, all these different ways in which you can hide the deficiencies of the model, and it's important not to be too tricked by the performance of the current video models. It's easy to, cherry-pick examples and think that video models are further advanced than they are. So there is a lot more work that we need to do to improve those models. But in my mind, very similar to language, and, like, we've. you go from barely coherent sentences to something that, could hold a conversation with a human to something that could can operate autonomously for a day and, like, create entire code bases. And the main difference, there is some architecture improvements along the way, but the main thing is scale. And so it's the same bet for video, and we have no indications that this is saturating. Like, we have benchmarks that we use for measuring the physics of those models, and we see those predictably improve as we scale those models. So there is. If you want to Google up, Physics-IQ, is one of those benchmarks that measures how well does the model perform at solid mechanics or fluid dynamics or optics.Vibhu [00:32:32]: I'm curious if you've seen any emergence, any scaling law around this.Swyx [00:32:37]: Yeah, he's saying there is a scaling law, right?Anastasis [00:32:39]: Exactly.Vibhu [00:32:40]: Yeah,Anastasis [00:32:40]: So the way those models, those benchmarks work is you. the researchers have gone and, like, captured, a few videos that are representative of different physical phenomena, and then you can take the first frame and then pass it through an image-to-video model and then generate a rollout that shows what should happen next. So you have, a ball hanging from the ceiling, and then you use that as input, and then you the model predicts how the ball should fall on the ground. and this measures. we have an intuitive understanding of physics. I know, you can imagine what will happen next if I drop this bottle. So it's measuring that same intuitive physics understanding of those models, and we've measured that at different model scales, and we see, and compute scales, and we see that the score on physics IQ predictably improves. There's other, tricks and techniques that you can make to improve the score even further, but even scale alone helps, in the model learning better physics.Swyx [00:33:40]: My main sympathy with Yann LeCun is the, Plato's cave allegory, right? Like, you're, you're, like, learning on the output of a thing, not the internal process of a thing, and it's very noisy. And, if only you could observe the internals of a thing. It's hard to observe the internals of a human mind, but you can very much observe, or at least we have a whole branch of science and physics that we're ignoring on how to model Physics and movement and, gravity and, other interactions. and we're just, like, throwing away all of that and just saying just scale data, which is very much the lesson of unsupervised learning, but it feels wrong. that's the main idea.Anastasis [00:34:21]: I think the history of machine learning is, at large, it feels wrong.Swyx [00:34:25]: Yeah. It's a bitter lesson, right? Yeah. It's, it's, it's the simple answer to that.Vibhu [00:34:29]: I guess, how much can you scale? So, like, even on, let's say, the video generation side, like, there's one side of video understanding. Video generation, are we still gonna have tools where it's like, I wanna generate two hours, twenty hours? there's a infra way to do it in batches and stitch it together, but, like, do we just keep scaling? Do we just continue long generation consistency, all that at scale? And, like, tying it into where we're at now from we looked at Runway two to four point fiveGen-3, Sora, and Runway's Scaling InflectionAnastasis [00:34:58]: Yeah.Vibhu [00:34:58]: Like, technically, what advancements have we made to today, and then where do you see things still going?Anastasis [00:35:04]: So part of the answer is definitely scale. and that was. We learned that lesson in a big way for with Gen-3. So Gen-3 was the model we released the year after, like in 2024. That was a few months after Sora was released. so yeah, there's an interesting story of that came to be as well. Gen-3 for us was, the first time that we really needed to build. we had to learn all the lessons that the language model world learned in two in three years in the span of a few months. one of the biggest changes of Sora was using diffusion transformers instead of convnets. So a lot of the early, latent diffusion models were all, convnets for the diffusion model part. And the diffusion transformer paper came at some point in 2023, and it showed scaling laws for image, diffusion transformers. And we realized at that point that we needed to invest in infrastructure for model parallelism, for really scaling training to larger than, a few billion parameter models. And we spent maybe the, most of the fall of 2023 building out our infrastructure for distributed training. And we had a lot of false starts and a lot of failure in trying to scale, image and video diffusion transformers. And at that point, February 2024, Sora comes out, and the results areAnastasis [00:36:35]: Very much superior to what Gen-2 could produce. There were a lot of, a lot of chatter on Twitter about Runway. Runway's done. like, there is no way Runway will catch up. And if you remember, also OpenAI in the early twenty-It felt very, like it's aSwyx [00:36:56]: To the moonAnastasis [00:36:57]: It's a formidable opponent now, but at that point, it, they were on the top of their game. nobody could even get close to them. There was maybe Gemini was just the first version of Gemini had just released. So when OpenAI came with Sora and it was such a big jump of like quality, it gave me, there was like an existential crisis for a few hours. But that, I think the amazing thing about Runway and like I think the, we've been around eight years now, which is almost we're dinosaur in AI, and we had to like, we had there was a lot of those moments we had to learn, adapt very quickly and build out skill set in the team that we didn't have. And so, if you ask anyone what is their favorite time at Runway that was there during that time, it was that push in like three months to get to a model better than Sora. and it, we scaled 10x the model scale, the model size and the, compute that we were training on. we figured out model parallelism. We had zero expertise in that. And then we came out with Gen-3 during that summer. So that was a big turning point, I think, for the company where the research org grew very quickly, and we really started pursuing this vision of the general world model, in earnest, I think after Gen-3 was out.Swyx [00:38:12]: Yeah. that's the amazing thing about building when you're building. There's no stack to. You have to invent everything yourself. You have to be completely full stack. Now I think like there are inference specialists like Fal or whatever that can help with like, model serving, and I think you guys work with them as well. but yeah, like it's, it. But at the time, it was just. It's very interesting to think about what you do when Sora comes out and people are questioning whether your company should still exist.Distillation, Turbo Models, and Real-Time VideoAnastasis [00:38:41]: Yeah. And yeah, there was no, there was no VLM of diffusion models. Like, we had to build the whole model serving infrastructure and make things efficient. And a few months after we released Gen-3, we released the Turbo version, which I think was the first step-distilled model in production.Swyx [00:38:56]: That was a whole trend that we covered as well. Yeah.Anastasis [00:38:59]: So that allowed us, to serve those models at the larger scale, ‘cause I think the first version of Gen-3 was quite, expensive to serve.Swyx [00:39:09]: I think the whole like trend in like consistency models, Lightning and, Turbo and all these things somehow didn't really stick around. I don't know if you have any reflections on this. Because at the time, I was like, “Well, everything should start with a distilled model first, and then you can upscale,” right? It. your bigger models just turn into fancy upscalers, but like you should always draft with a smaller model and faster model, right? Because you can get it so quickly, like near real-time.Anastasis [00:39:39]: Yeah. I would not be so sure to say that didn't stick around. I think that, it's, it's likely to. that there is a lot of step-distilled models that are actively used in production. there is still a gap in quality compared to the, non-distilled model. but in my mind, we're still. there is a two to three year offset from language models. So the things that, So it's just a matter of time before there is better distillation techniques. we use. Right now we have a real-time model core character that I think is the largest deployment of real-time video models, that's a step-distilled model, and it's actively being used. It's a very specific use case compared to a general video model. So this is aSwyx [00:40:27]: Very cool, by the way.Anastasis [00:40:27]: This is avatars stuff, right?Swyx [00:40:28]: Consistency, character.Anastasis [00:40:30]: Yeah. So this is a talking avatar, model. we were able to. we optimized the hell out of it, and it generates at 24 FPS, and it's a, it's a step-distilled autoregressive video model. So if we look at our world model direction, a big component of it is starting from the bidirectional diffusion that generates entire video at once and making autoregressive shows. So you generate one frame or a few frames at a time. so there's a lot that goes into that pipeline of getting to a real-time model. It's first you need to make it into a causal autoregressive model, and then you just turn it into. You need to do some additional step distillation to get it to be real-time. and I think that part is just starting. I'll be very surprised if we're, two years from now, we don't primarily use real-time models. To me, real-time video generation is just inevitable that, it has much better user experience, it's much cheaper to serve, and, the quality gap between the base model and the real-time model is only gonna close as we figure out better, distillation techniques. And we made a lot of progress there internally on maintaining the quality of the base model when we distill them.Swyx [00:41:49]: How much of this is transferable? So is it the same base model? Like if you're doing diffusion across the whole sequence and you're converting it to step autoregressive distillation, is this like distillation where you still need to train both, you can use the same base and converter? What's that process like to go from regular model to something that's real-time on a technical level?Anastasis [00:42:11]: So the nice thing about diffusion models is you have, two axes of distillation. So there is the. You can distill to a smaller model, which resembles what you do in LLMs, or you can distill in terms of taking less steps, less diffusion steps. So you could take a model that generates in fifty steps and generate in four steps and get to, You have some performance, degradation, but very often you get comparable outputs. So you can even take the large frontier model and distill it with step distillation and get to a real-time performance, and that's what we've seen. So, depending on the use case, in some cases we might also serve with a smaller model, but in a lot of use cases, we just use theSwyx [00:42:56]: Step distillationAnastasis [00:42:56]: The frontier model, and we're able to make it work in real-time.Swyx [00:42:59]: I think this might be a good time to cut over to his laptop to show off some of the real-time stuff that you're doing.Interface World Models and Neural SoftwareAnastasis [00:43:06]: This is one of the research updates that we did recently. so we've been working and f in getting our general world models to, different applications. one of them that we think is very compelling is using general world models as essentially, an interface, a universal interface to software. This is a version of our world model that's called an interface world model. and the idea is that it essentially, replaces, the, front end of a software application. It renders the pixels directly of an interface and is trained to predict what happens next as a result of, a click or another interaction you have with the interface. So this is all pixels. it's there is no HTML, CSS, React that's powering this interface. This is directly at the output of our real-time, video generation model, and it takes clicks directly as input.Swyx [00:44:09]: And drags, click and drag.Anastasis [00:44:12]: Right. So it supportsSwyx [00:44:13]: Ooh.Anastasis [00:44:14]: Yeah, clicks. It supports drags. it also supports scrolling. and the amazing thing about this is that you can effectively describe in the prompt how you want different elements, like what do you want the behavior of different elements to be. So it's almost you're you can turn, an interface from, markup language description of, like, an HTML interface, and instead you can just describe the interface. if I press this button, I expect this to happen. If I press this button, this should happen. And it's useful, we believe, both for prototyping, for, like, just testing, like, what different interactions would feel like. you can also add audio to it. So it's a video audio generation model. So you get you essentially can describe both what the visual outcome should be of your click and also what the if there is a sound effect that comes out of it. So we believe that's gonna be a much more flexible way of building software. Just render. It just, in why generate the code that generates the pixels? Just generate the pixels directly.Anastasis [00:45:18]: It's the end-to-end philosophy applying applied to front ends.Anastasis [00:45:25]: So we think there is a few interesting use case. So you can build creative tools on top of it.Anastasis [00:45:32]: We think that, for any use case that involves a lot of exploration or, like, educational use case where you wanna learn about a new concept and you want some visualization and like, and open-ended exploration, we think those this is a very powerful, approach. you can imagine new forms of, design, industrial design software that could emerge as a result of those models. And this is all, generated in real-time as well. So, you can build a lot of interesting camera transitions and forms of interaction that are very difficult to build otherwise. And one way in which we evaluate this is what if you try to generate the same interface with Claude by just, prompting Claude, “Here's an image reference of my interface that I made in Figma or that I created somewhere else. create this particular interaction,” which in this case it's, drag that object, upwards. and beyond it being slower, it's also very difficult to capture some interactions by just fully, with just LLMs. So we think that this is likely to be the way that a lot of the future, like, software in the future will be created. and one of the additional benefits is personalization might be a lot easier done with those models. Like, you can essentially try out different prompts based on who is visiting the interface. You can, more easily, prompt engineer the interface to have larger size, text for more accessibility reasons, or you can make this or, like, if you have a particular aesthetic preferences. So we're very excited about this approach. It's early days, and I think we'll need to, make it more cost-effective as well to serve those models ‘cause, running a real-time video model versus just purely rendering HTML, there's -- the computational needs are much higher. but we do see a lot of potential in this approach to building front-end interfaces.Swyx [00:47:47]: So we covered this similar thing with Flipbook before with our, Ethan Hara episode with Groq, video. And yeah, I think it's very engaging visually. I think it's maybe very good for education, but it's it does sound expensive. I think there's an upper bound to how expensive it will be, though, right? Like, the inference cost will go down over time. You'll figure out ways to optimize it. Effectively, when it pauses, you don't you're not receiving human input. You don't have to generate anything, right? So.Anastasis [00:48:14]: Yeah, you could also. Like, in this case, you have ambient motion, so there is parts of the screen that might. if you're let's say you wanna, visit Paris and then you get this interface that allows you to explore.Swyx [00:48:29]: People walking. Yeah.Anastasis [00:48:29]: You have people walking or, like, things happening. But, it's, it's a no Yeah, it makes it more expensive because you need to run the model all the time. Maybe you have some looping mechanism so you don't need to do that. But all those things, I think, is stuff we'll need to figure out.Toward a Fully Neural Operating SystemSwyx [00:48:44]: Yeah.Anastasis [00:48:44]: I think our first consideration is let's make this clearly find some use cases where it's clearly a much more compelling interaction compared to traditional interfaces. And then it's a matter of time before it becomes more cost-effective to serve.Swyx [00:48:58]: Yeah. When it comes to the people walking, I think the approach that makes the most sense to me is Nick.Anastasis [00:49:04]: Nick.Swyx [00:49:04]: Oh, God. I keep messing up their name. With Chris Manning and Fanny Yan. I don't know if you've come across them, where they. Mapped to some game engine. I think it's Unity or something, or Godot. And they you can script some NPC behavior behind that and train on that. Whereas here, you can really imagine whatever you want. Like, that is a UI, right? Like, and it feels, like, more tractable, I guess, to, create a world model of software that is interactable because we have many of examples of that, and you can, do your fancy RL environment stuff on that than it is scaling up to embodied and real-world physical use cases. But this is a nice first step.Vibhu [00:49:43]: Or, there's the opposite of you have, like, one B models, three 50 million parameter language models. It just gets so small that they're just predicting, like, fishes moving.Swyx [00:49:53]: Small models are now 120 B, so.Vibhu [00:49:57]: Ultra mini on device.Vibhu [00:49:58]: But, no, I think it, like, it puts it into perspective, at least the car one for me, like, the applications, right? The amount of work to do that, sure, you only make one model year car per year, but applying this, it's also a cost-saving to have to manually make all this, right? So it opens up a lot of possibilities, too. I'm curious if you extend this out two, three years, so where do you see things going even further?Anastasis [00:50:25]: Effectively, the end game of something like interface world models is you have, a fully neural operating system. So I think, Andrej Karpathy has written about that quite a while back. But it's, You, I think to me it's, it's a bit, it's a bit odd that, we have, for example, with an interaction with an LLM of today, you have this LLM that can talk to you about anything. It can You can take the conversation in any direction. You can It's very general, so it can solve all those different tasks, but you interact with it through a very rigid interface. And so to me, it's just a matter of time before the interface itself becomes learnable and becomes, part of the whole loop of, like, you're not just delivering. You're delivering an application end-to-end, and that means you're delivering the language model, but you're also delivering the render and the pixels and that's also a learnable component. And the concept of applications might not necessarily. I think we'll need to figure out new abstractions for software. the concept of application comes from this idea that you need, separate code bases to describe, to, for, to power each individual, tool and each individual application. But you might think of something a lot more unified if you're. if you have, a video model that's generating the interface as you go. so it can take context from an LLM and allow you to combine different functionalities that traditionally would live in different applications. So it's a, it's a way to solve, software end-to-end, effectively. We also see this as a powerful way to train computer use agents as well. so this is, one way to see this as. And in general, with world models, there is those two directions. One is world models for humans and world models forSwyx [00:52:24]: AgentsAnastasis [00:52:24]: To train agents.Swyx [00:52:25]: Yeah.Anastasis [00:52:25]: And so for every new work of, world models that we do, we have this both uses become possible. So this is a powerful synthetic data generator for training computer use models. It could become, a live, RL environment that you could use to do online RL with a computer use agent, and you can get wide diversity of different interactions, kinds of interfaces, just generated on the fly that, to improve the how robust the, your agent, becomes. So that's the same also with the world models that we're working on for a robotics use case as well.Long Context, Error Accumulation, and Autoregressive VideoSwyx [00:53:02]: Is there a research breakthrough that you're Waiting for that would unlock the next set of use cases that you really wanna pursue?Anastasis [00:53:10]: Long context is a very important one, so being able to maintain consistency for long periods of time, and that depends on the use case. So for our characters model, for example, or for the interface world model, it's easier to maintain long sessions of interaction. If you go into more open-ended worlds that you navigate and you take arbitrary actions in, we, like, there is more the context at which you can and duration which you can generate becomes limited much more quickly.Swyx [00:53:40]: Yeah.Anastasis [00:53:40]: So we see more degradation and error accumulation happening. so the biggest challenge with autoregressive models is error accumulation, is you're feeding generative frames back into the model to generate the next The next frames. And if there is any small errors, they accumulate over time. That's not a new problem. It's a problem that LLMs also have, and we've seen the ability to generate now really long outputs. So it's a solved problem, but it's definitely still a challenge.Swyx [00:54:08]: Yeah. And what is the state of the art? so for Grok, it would be like 10 to 20 seconds of context going in there for video.Anastasis [00:54:16]: With our characters models, we're able to generate up to 30 minutes of video autoregressively.Swyx [00:54:21]: Yeah. But that's just for the avatars.Anastasis [00:54:24]: Yeah. So if we look at, GWM Worlds, which is more our open-ended world exploration model, it's, it's on the order of a few minutes, which is Yeah, soSwyx [00:54:35]: Probably enough for people because you have to cut to the next scene anyway, right?Anastasis [00:54:40]: Yeah, it's not, it's not the ideal game experience if you have to restart every few minutes. So I think. But, I think it's. Yeah, for certain kinds of game experiences, you can work around it.

Hey, it's Alex

In this episode of Phoenix Cast, hosts John and Kyle are joined by Krista White, a 20-year defense sector veteran who now leads AI enablement for mission analysts, for a Sunday morning coffee chat about something nobody puts on the record: what heavy agentic AI use does to the human running it. Kyle describes hitting a cognitive wall after four hours of managing a fleet of agents, John lays out his commander's intent approach of forcing the AI to bring him HTML decision briefs so decisions stay off his plate, and Krista names the fatigue, the fear of better options, and the moment it starts to look like addiction. The three compare notes on subscription tiers as accidental work-life balance, the “$100 bills everywhere” trap, and why the folks still resistant to AI mostly just need someone to sit down next to them. Then they take it to the watch floor: if an operator has limitless tokens, how many hours into a 12 to 16 hour shift can we still expect good decisions? If you have ever felt your brain turn to mush after an afternoon with the agents, this one is for you.LinksVibe Coding (Gene Kim and Steve Yegge, IT Revolution):https://itrevolution.com/product/vibe-coding-book/The AI Vampire (Steve Yegge on AI fatigue and naps):https://steve-yegge.medium.com/the-ai-vampire-eda6e4f07163Conway's Law:https://en.wikipedia.org/wiki/Conway%27s_lawGenAI.mil:https://genai.milClaude Code:https://claude.com/product/claude-codeOpenAI Codex:https://openai.com/codex/Google Antigravity:https://antigravity.googleOpenCode:https://opencode.aiPhoenix Cast - Every Marine an AI Rifleman:https://open.spotify.com/episode/3vRBJMgTBQNnp0uebmkzEu

HTML - Groovestone Chronicles III by MedellinStyle

For most of the past 20 years, I have thought of myself first and foremost as a podcaster when it comes to content creation. Recently, I was working on a project that caused me to go back through hundreds of blog posts I wrote between 2004 and 2014. I converted the entire archive into HTML, Markdown and even an EPUB that I can now read on my Kindle. As I started looking through all of that old writing, I realized something I had almost forgotten. Before I was a podcaster, I was a writer. In fact, before I recorded my first podcast episode in December 2005, I had already spent years writing online. At one point, I was even working toward becoming a published author. Podcasting changed everything for me because it allowed me to communicate ideas in a fraction of the time it took me to write and polish a long-form article. Eventually, audio became my primary creative medium and I mostly left long-form writing behind. Today, the economics of writing have changed for me. With the tools I now have available, especially the way I use ChatGPT as part of my creative process, I can take an idea that might once have required six or eight hours of writing and editing and turn it into something I'm proud to publish in one or two hours. At the same time, I recognize that my written content currently has the potential to reach significantly more people through my email list, LinkedIn, Facebook and Substack than I'm reaching through my audio podcasts alone. All of this contributed to my recent decision to step away from my commitment to producing The Cliff Ravenscraft Show and Podcast Answer Man every single week. I'm returning to what I call "inspired content only." My commitment is simple. There will be at least one new episode of each show every calendar month. Beyond that, I may publish two episodes, five episodes or considerably more whenever there is something I genuinely feel inspired to share. In this episode, I talk through that decision, my rediscovery of myself as a writer, my thoughts about written, audio and video content, and why I'm becoming much more intentional about where I invest my creative energy. I also share a few things happening in my world right now, including my upcoming trip to VidSummit, some of what I've been doing with ChatGPT automations, and a story about how a cracked PLAUD Note Pro turned into three brand new devices. That final story became an example of something I think about constantly in my own life and in my coaching. When I encounter an undesirable circumstance, eventually I want to get beyond my reaction to the problem and ask a different question. What is my desired outcome? Once I know that, I can start looking for the options that might move me toward it. Relevant Links Next Level Mastermind: Momentum: https://www.cliffravenscraft.com/momentum Substack: https://cliffravenscraft.substack.com LinkedIn Newsletter: The Entrepreneur's Journey : https://www.linkedin.com/newsletters/the-entrepreneur's-journey-7275950143143604225 PLAUD Note Pro Affiliate Link: http://plaudus.sjv.io/en2jd6 Affiliate disclosure: If you purchase a PLAUD product through my affiliate link, I may receive a commission.

The Reddit Hoax That Bled into Reality... or a Masterclass in Espionage?In 2009, an elderly  @reddit   user named "Milo" passed away. When internet sleuths dug into his seemingly boring image-hosting website, they uncovered a hidden HTML message board coordinating logistics, international flights, and massive cash payouts. Weeks later, a Hamas military commander was assassinated in a Duba hotel room—and the timeline perfectly matched the hidden code.Was Lake City Quiet Pills an elaborate Alternate Reality Game, or a digital dead drop used by Mossad to coordinate an international hit squad in plain sight?Join us as we tear into one of the most enduring, complex, and dangerous mysteries of the early internet. From burner phones and cloned passports to the "Milo" persona and the chilling final message posted on the board, The Soul Trap breaks down the timeline of the ultimate digital ghost story.Hit Subscribe to support the investigation and drop your theories in the comments—was Milo a troll or a handler?#LakeCityQuietPills #internetmysteries  #truecrimecommunity  #TheSoulTrap #DigitalDeadDrop #UnsolvedMysteries #cyberespionage   #redditmysteries  #ConspiracyTheorySupport the show

Mel Huang Buntine on how computers started entering our homes, and the beige box of a machine that changed her own life.Personal computers are so ubiquitous now, it's hard to imagine a time when computers were inaccessible to everyday people.For decades, computers were the size of rooms, and they were used for specialist tasks like processing large data sets for researchers, or sending men to the moon.But by the 1980s computers had become smaller and more affordable, and people started bringing them into their homes.From this point on, how everyday people interacted with technology changed forever.Mel Huang Buntine is a designer and technologist who was gifted her first computer as a tween in 1990s Melbourne.Mel lived in a multigenerational home with her mother, her grandparents and her great-grandmother, all of whom had escaped the Cambodian genocide as refugees.They couldn't understand why Mel was obsessed with this machine, but it completely opened up Mel's world and changed her life.Now with anxiety growing around AI, surveillance and mega tech companies, Mel is trying to get people to understand the history of computers and how they work.She hopes this will give back to people a sense of agency over machines, rather than feeling powerless to the opacity of algorithms and large language models.Radical Computing is exhibiting at the National Communication Museum in Melbourne from 19 September 2026, until 21February 2027.This episode of Conversations was produced by Meggie Morris. Executive Producer is Nicola Harrison.It explores technology, artificial intelligence, Facebook, Instagram, social media, coding, making a website, HTML, CSS, PS5, playstation, games console, computer games, desktop games, Apple iOs 27, Mac, Macbook, Mac versus PC, IBM, Commodore 64, Steam Frame, iPhone, smartphone, dumb phone, Steve Jobs, Jack Tramiel, computer race, home appliances, toy market, super computers, science and technology, future of computers, techno optimist, tech subculture, Demoscene, hackers, jailbreak phone, crack software, pirated software, Dario Amodei, Sam Altman, ChatGPT, Claude, Anthropic, Zuckerberg.To binge even more great episodes of the Conversations podcast with Richard Fidler and Sarah Kanowski go the ABC listen app (Australia) or wherever you get your podcasts. There you'll find hundreds of the best thought-provoking interviews with authors, writers, artists, politicians, psychologists, musicians, and celebrities.

Send us Fan MailFrazier welcomes Michael McAlister as a co-host on the Mortgage AI Podcast and explains the transition from The MLO Project to focus on AI. They discuss the difference between “AI agents” (a tool that automates specific tasks) and “agentic AI” (an approach where AI is embedded with autonomy across business functions). Miguel describes moving beyond prompt-based assistants to workflows where AI monitors stages, reviews files, drafts communications, and updates systems, which requires standardized inputs, documented rules, and oversight similar to managing employees. He shares using scheduled routines that run early daily and email HTML reports for ad management, pipeline signals, and weekly newsletter drafting with approval. They note tools change rapidly, urging focus on business outcomes over chasing tools. Rapid fire: underhyped tools Fathom and Aila; overhyped GPT Work; most annoying AI talk is “build your own” piecemeal tools.00:00 Welcome Back Maestro01:31 Why This Podcast Exists02:42 Agents Versus Agentic05:29 From Tasks To Workflows11:18 Managing AI Employees13:39 Routines And Reports18:54 Tool Overload Reality21:14 Think Business Not Tools27:54 GrokBot Setup And Cost29:19 Rapid Fire AI Takes32:21 Final Thoughts And OutroPresented by: DIFRNT CoachingFounding Sponsor: MortgageConBroker Sponsor: Summit LendingFriends of the Program: Empower LO

On Feedback Friday we usually review other brands' emails. This time we put our own SaaS onboarding emails up for review.Together we look at five onboarding emails inside the RGE Studio builder and talk through what each one is for, when it sends, and what we'd change.Chapters00:00 Intro02:28 Email 1: Your ESP wasn't built for this16:32 Email 2: Power up your dream team23:20 Email 3: Getting your email into SFMC29:15 Email 4: Your trial is ending38:15 Email 5: A hate letter to Outlook43:59 OutroKelsey Yen: https://www.linkedin.com/in/kelsey-yen/Build your own really good emailsAll five emails in this episode were built in RGE Studio, the drag-and-drop builder inside Really Good Emails. Save inspiration from the library, build your own version, then export the HTML or connect your ESP. Free to sign up at https://reallygoodemails.com/studioWant feedback on your emails? Submit them at https://reallygoodemails.com and they could end up on a future Feedback Friday.Follow @reallygoodemails on IG, drop a comment with your take, and subscribe for new episodes.

Tony Whatley didn't start with investors, connections, or some perfectly mapped-out entrepreneurial journey. He was working three jobs, buried in debt, raising a kid, and building his first online business with $350 and a book on HTML. That side hustle eventually became a massive automotive community he sold for millions. In this episode, Tony and Eric get into what actually separates people who talk about building something from the ones who fucking do it. They break down the different stages of entrepreneurship, how to build a company with an eventual exit in mind, why Tony believes he left a million dollars on the table during his first sale, and what a 130 MPH crash taught him about impact, purpose, and how he wanted to be remembered. And maybe the biggest lesson: the people you're afraid will judge you probably won't even be at your funeral. Stop building your life around their opinions.

What happens when users stop clicking through many screens and simply tell the application what they want?In this episode of the Angular Master Podcast, Manfred Steyer explains Agentic UI and how it may change the way we build Angular applications. We discuss how an AI agent can understand user goals, work with application state, and select the right UI components.We also explain the roles of MCP, AG-UI, and A2UI, and how these technologies can work together in a modern Angular architecture.Can AI decide what appears on the screen? Should it generate HTML and Angular code directly, or should it choose from a trusted set of components? Who owns the application state, and what happens when the agent makes a mistake?We also discuss security, human confirmation, design systems, routing, forms, and what an AI-ready Angular architecture should look like.

Chapters00:00 Introducción al Agentic Commerce y la nueva forma de comprar05:30 De buscar en Google a comprar con agentes de IA12:30 El impacto de la IA en tráfico, conversión y decisiones de compra18:30 Cómo optimizar páginas de producto para ser recomendado por la IA25:00 Reseñas, autoridad y comunidades como señales de confianza32:30 Qué puedes controlar, influenciar y adaptar en Agentic Commerce39:00 Shopify, Universal Catalog Protocol y la importancia de un catálogo limpio48:00 Knowledge Base, datos de marca y los pilares de la visibilidad01:01:30 HTML vs. JavaScript: cómo asegurarte de que los agentes puedan leer tu contenido01:08:00 Calidad y consistencia de la información de tus productos01:17:00 Descripciones, atributos y metafields para dar más contexto a la IA01:29:00 Errores comunes, herramientas y próximos pasosKey topicsQué es Agentic Commerce y cómo está cambiando el e-commerceCómo los consumidores utilizan IA para descubrir y comparar productosCómo optimizar páginas de producto para agentes de IAImportancia de títulos, descripciones, atributos, metafields y alt textCómo estructurar y mantener consistente la información del catálogoEl rol de las reseñas, Reddit y otras fuentes de autoridadShopify, Universal Catalog Protocol y Knowledge BaseDiferencias entre contenido renderizado en HTML y JavaScriptCómo preparar tu tienda para ser entendida y recomendada por la IAErrores comunes que pueden limitar la visibilidad de tus productos¿Quieres preparar tu e-commerce para la nueva era del Agentic Commerce? Agenda una consulta con ED Digital. Recursos mencionados en este episodio:Email: ed@ed-digital.comTeléfono: +1 (787) -449-2219Website: ed-digital.com

Episode Summary:Will and Brandt try to get through a whole episode without saying the two letters. What's your over-under on how far they got? Along the way: Will's new NDI camera rig, Apple's ten-thousand-dollar Mac Minis and a rumored rack-mount server, why local hosting keeps swinging back to the cloud, and Brandt's morning brief that grew from a chat message into a checkbox web page.Discussions Include:• Will's NDI camera overhaul, from a $200 encoder box to auto-tracking PTZ gimbals that occasionally zoom out on their own• Apple's $10K Mac Mini configurations, the rumored rack-mount Mac server, and model companies ordering them by the thousand• The expansion-and-contraction cycle of local versus cloud, from self-hosted email servers to running your own models• Buzz, Block's "Slack for agents," and why one master agent isn't enough once you're running several at once• Brandt's daily brief evolving from a chat message into a full HTML page with checkboxesQuotable Quotes (Should you choose to share):     "It's refreshing to talk about something that's technology based that doesn't have two letters in it." - Brandt Krueger     "Whenever I get frustrated with something in software, I now ask myself: can I just build it?" - Will Curran     "It would back up, go full speed to the point where it would pop a wheelie, and then ram itself into your furniture at full speed." - Brandt Krueger     "AI has definitely made us more organized and more productive. But then why do people feel as burnt out as they did when we didn't have this technology?" - Will CurranThing of the Episode (TOTE):     Brandt: Roborock QV 35A - https://us.roborock.com/products/roborock-qv-35a     Will: Cronometer - https://cronometer.com

This episode of the DevCast looks at how JavaScript, HTML, JSON, Web Viewers, and AI can work together to build more flexible and dynamic FileMaker solutions. A few of our devs walk us through real-world examples, like a multi-image upload and rotation tool and a dynamic dining room and table management interface.The conversation strides into a bigger question: How much do you really need to understand when AI is writing the code for you? Our devs discuss finding the right balance between letting AI handle the heavy lifting and understanding enough of what's happening under the hood to build, test, troubleshoot, and maintain a reliable solution.Multi-Image Upload Blog Pt. 1: https://www.portagebay.com/blog/multi-image-uploading-with-gallery-and-rotation-free-demo/Multi-Image Upload Blog Pt. 2: https://www.portagebay.com/blog/using-webviewers-to-add-functionality-for-field-technicians/

Côté IA : MCP devient stateless, Claude watermarke ses textes, GPT-6 Astra défie Claude Fable, et une étude JetBrains confirme Claude Code en tête des agents de code. Côté JVM : JDK 27 généralise G1, Kotlin 2.4 stabilise les context parameters, une API JSON arrive dans le JDK, et Quarkus comme Micronaut enchaînent les versions. En bonus, trois pannes IA simultanées et un câble débranché chez Google Cloud. Enregistré le 11 septembre 2026 Téléchargement de l'épisode LesCastCodeurs-Episode-343.mp3 ou en vidéo sur YouTube. News Langages Les Types Algébriques de Données (ADTs) en Java rockthejvm.com/articles/algebraic-data-types-in-java Le problème : L'approche classique (champs nullables, hiérarchies de classes ouvertes) crée des états invalides et des erreurs à l'exécution (comme le NullPointerException). Types Produits (ET logique) : Implémentés en Java avec les Records. Ils regroupent plusieurs champs de manière immuable et concise. Types Sommes (OU logique) : Implémentés avec les Sealed Interfaces. Elles définissent un ensemble strictement fermé de sous-types connus à la compilation. ADTs (Types Algébriques) : La combinaison des Sealed Interfaces et des Records. Ils garantissent que les états invalides sont impossibles à représenter dans le code. Pattern Matching : L'extraction des données se fait via des expressions switch exhaustives, supprimant le besoin de casts manuels et obligeant le développeur à traiter tous les cas possibles. Généralisation : Ce modèle est idéal pour créer des types comme Result, forçant le traitement explicite et sécurisé des succès et des erreurs typées. Pourquoi "Algébrique" ? Parce que les types sont combinés mathématiquement (Produits = multiplication, Sommes = addition) pour limiter strictement le nombre d'états possibles d'une donnée. JDK 27 : fonctionnalités et calendrier de sortie openjdk.org/projects/jdk/27 infoworld.com/article/4202901/jdk-27-the-new-features-of-java-27.html JDK 27 est la prochaine version majeure de Java, une version non-LTS avec seulement 6 mois de support, qui succède à JDK 26. La disponibilité générale est prévue pour le 15 septembre 2026, avec des release candidates les 6 et 20 août 2026. Le périmètre est désormais figé (feature freeze) avec neuf JEP au programme. Le ramasse-miettes G1 devient le collecteur par défaut dans tous les environnements, et plus seulement en mode serveur. Ajout d'un support de la cryptographie post-quantique pour TLS 1.3, via des échanges de clés hybrides combinant algorithmes classiques et résistants au quantique. Finalisation de l'API PEM pour encoder et décoder clés, certificats et listes de révocation au format PEM. L'API Vector poursuit son incubation pour la douzième fois, permettant d'exprimer des calculs vectoriels compilés en instructions CPU optimisées. Les en-têtes d'objets compacts, introduits en JDK 24, sont désormais activés par défaut et réduisent l'empreinte mémoire du tas. Plusieurs previews sont reconduites : constantes paresseuses (3e preview), types primitifs dans les patterns (5e preview) et concurrence structurée (7e preview). Ajout d'une fonctionnalité de rédaction in-process pour JFR, afin de masquer les données sensibles dans les enregistrements de profiling. Kotlin 2.4 : nouveautés du langage et outillage kotlinlang.org/docs/whatsnew24.html Kotlin est un langage moderne, multiplateforme (JVM, Android, iOS, JavaScript, Wasm) développé par JetBrains, souvent utilisé comme alternative à Java. Les context parameters passent en stable : ils permettent de fournir des dépendances implicites à une fonction sans les déclarer en paramètre explicite, un peu comme une injection de dépendances. Les collection literals arrivent en expérimental : on peut écrire une liste avec des crochets, comme en Python, par exemple val fruits = ["pomme", "banane"]. L'API UUID de la bibliothèque standard devient stable, pour générer et manipuler des identifiants uniques nativement. Nouvelles fonctions utilitaires comme isSorted() pour vérifier si une collection est déjà triée. Support de Java 26 côté JVM et alignement automatique des versions Java et Kotlin dans les projets Maven. Kotlin/Native, la compilation vers du code natif iOS et macOS, active par défaut un nouveau ramasse-miettes plus rapide et améliore l'export vers Swift. Kotlin/Wasm, la compilation vers WebAssembly pour faire tourner du Kotlin dans le navigateur, rend la compilation incrémentale stable. Kotlin/JS permet désormais d'exporter des value classes vers JavaScript et TypeScript. Le compilateur K1, l'ancienne génération, n'est plus supporté : seul le nouveau compilateur K2 reste disponible. JEP 540 : une API JSON simple intégrée au JDK (incubation) openjdk.org/jeps/540 Le JDK ne propose aujourd'hui aucune API JSON native, obligeant à dépendre de bibliothèques externes comme Jackson, Gson ou Jakarta JSON pour parser ou générer du JSON. Cette JEP remplace la JEP 198 de 2014 et cible JDK 28 avec le nouveau module incubateur jdk.incubator.json. L'objectif est de couvrir les besoins simples d'extraction de données sans binding de données ni API de streaming, en laissant ces cas avancés aux bibliothèques existantes. L'API s'articule autour de l'interface scellée JsonValue avec six sous-types : JsonString, JsonNumber, JsonBoolean, JsonNull, JsonObject et JsonArray. Le parsing est strict et conforme à RFC 8259 : pas de virgules finales, pas de commentaires, et les noms de membres dupliqués provoquent une erreur. Donc pas de JSON5 La navigation se fait via get et tryGet, et la conversion vers des types Java via asInt, asLong, asDouble, asString, asMap ou asList. En cas d'erreur, une JsonValueException précise le chemin exact dans le document et sa position en ligne et colonne. Le pattern matching sur les sous-types de JsonValue permet de gérer proprement l'évolution du format d'un document JSON dans le temps. La génération se fait via toString pour une sortie compacte ou Json.toDisplayString pour une sortie indentée et lisible. À terme, le JDK pourrait utiliser cette API en interne, par exemple pour remplacer les fichiers de configuration au format property par du JSON. Autres nouvelles du JDK openjdk.org/jeps/535 openjdk.org/jeps/541 le mode generationel pour Shenandoah est prévu par défaut et deprécue le non générationel en 28 fini le support de Java sur Apple Intel GraalVM 25.2 : références compressées et Graal Script Agent medium.com/graalvm/… GraalVM est une machine virtuelle polyglotte d'Oracle offrant compilation JIT avancée et compilation en image native pour accélérer les applications Java et d'autres langages. Cette version 25.2 fait partie du train de releases innovation qui livre les nouveautés plus vite, pendant que GraalVM 25.0 reste la version stable recevant les correctifs de sécurité critiques. Nouveauté phare, le Graal Script Agent transforme des demandes en langage naturel en plugins sandboxés exécutés localement, en JavaScript ou Python, avec un accès restreint aux APIs de l'application. Les références compressées sont désormais activées par défaut dans Native Image sur les systèmes 64 bits, remplaçant les adresses complètes par des valeurs 32 bits relatives au tas. Cette optimisation réduit de 39% la consommation mémoire RSS d'une application Micronaut connectée à Oracle Database, comparée à la version 25.0. Contrepartie de cette optimisation, le tas géré est désormais plafonné à 32 Go. Le garbage collector G1 est maintenant disponible sur toutes les plateformes, y compris Windows, via l'option –gc=G1. G1 apporte de meilleures performances, une latence réduite et un démarrage plus rapide, avec des images natives plus petites grâce à l'optimisation guidée par profil. Le Vector API de Java est activé par défaut pour exploiter les instructions SIMD, utile pour le machine learning et le traitement de données. Bonne intégration avec l'écosystème via Micronaut 5.1, Quarkus et WebAssembly. Shopify arrête React Native pour ses applis mobiles iOS et Android et repasse à du natif avec Swift et Kotlin shopify.engineering/back-to-native Les progrès majeurs des LLM (IA) réduisent drastiquement le coût du développement sur deux plateformes distinctes. Les bénéfices du natif pur restent supérieurs, moins de couches d'abstractions, de dépenfances externes, et plus rapide pour adopter les dernières fonctionnalités des OS Les bibliothèques open-source (Skia, FlashList, Restyle) évoluent : Skia sera forkée par William Candillon, FlashList cherche un nouveau repreneur, Restyle sera archivée fin 2026. Migration des applications (Shop, Shopify, etc.) réalisée en mode "greenfield" (reconstruction totale) assistée par IA. Utilisation du système "Helix" pour un développement itératif et contrôlé par des agents IA. Découplage de la logique métier et de l'interface via une CLI pour accélérer les tests et éviter les lenteurs des simulateurs. L'application Shop a été entièrement reconstruite en natif en 12 semaines ; les autres suivront. Librairies LangChain4j CDI est une extension CDI qui intègre LangChain4j avec CDI de Jakarta EE langchain4j.github.io/langchain4j-cdi LangChain4j CDI : Extension intégrant LangChain4j à Jakarta EE et MicroProfile. Services IA : Injection et gestion de cycle de vie via @RegisterAIService. Orchestration d'agents : 11 topologies d'agents configurables par annotations. Serveur MCP : Conversion de beans CDI en serveurs Model Context Protocol. Fonctionnalités d'entreprise : Configuration externe, tolérance aux pannes et observabilité OpenTelemetry. Installation Maven : Deux extensions disponibles selon l'environnement (build-time pour Quarkus/Helidon, portable pour WildFly/GlassFish/Liberty). Prérequis techniques : Java 17+, Jakarta EE 10, MicroProfile 6.1. Quarkus 3.36, 3.37 et 3.38 : trois releases avant Quarkus 4 quarkus.io/blog/quarkus-3-38-released quarkus.io/blog/quarkus-3-37-released quarkus.io/blog/quarkus-3-36-released Quarkus est un framework Java cloud natif optimisé pour GraalVM et HotSpot, conçu pour les microservices et les environnements conteneurisés. En 3.38 (29 juillet), l'équipe allège les nouveautés pour se concentrer sur Quarkus 4, la communauté atteint 1213 contributeurs. 3.38 introduit l'éviction basée sur le poids mémoire pour le cache Caffeine de second niveau d'Hibernate, en plus de l'éviction par comptage. 3.38 apporte l'extension Quarkus HTTP Problem qui implémente la RFC 9457 pour mapper les exceptions en réponses application/problem+json, intégrée à OpenAPI. 3.37 (24 juin) ajoute l'extension expérimentale quarkus jlink pour générer des images runtime JDK sur mesure et réduire la taille des conteneurs. 3.37 active par défaut la sérialisation Jackson sans réflexion pour de meilleures performances. et 3.39 lesdesactivent et les rement en opt-in 3.37 introduit dans REST Client RestMultiResponse pour lire codes de statut et en-têtes sur des réponses REST en streaming, avec passage à Hibernate ORM 7.4 qui exige PostgreSQL 14 minimum. 3.36 (27 mai) propose Quarkus Signals en expérimental, un système de communication typée entre composants inspiré des events CDI et de l'EventBus Vert.x. 3.36 embarque des SBOM applicatifs exposés via /.well-known/sbom, y compris en image native selon la spécification GraalVM. 3.36 ajoute l'authentification OIDC via JWT SPIFFE, facilitant l'identité de charge de travail en environnement zero trust. Micronaut Framework 5.1.0 : injection de dépendances, IA et sécurité renforcées github.com/micronaut-projects/micronaut-platform/…/v5.1.0 Micronaut est un framework JVM pour microservices et applications cloud-natives, avec injection de dépendances à la compilation et démarrage rapide. Introduction d'Open DI 1.0.0, une implémentation CDI Lite s'appuyant sur l'infrastructure d'injection de dépendances de Micronaut. Côté données, support officiel de SQLite et intégration MyBatis, avec ETags basés sur les valeurs pour le verrouillage optimiste. En sécurité, arrivée d'un module OWASP HTML Sanitizer, délégation d'authentification @RunAs et résolution de locale via OIDC. Côté IA, LangChain4j ajoute le support Chroma, la mémorisation de chat Oracle et l'authentification Google injectée pour Vertex AI, avec passage du MCP en version 2.0.0. Mises à jour majeures des dépendances : Spring Boot 4.1.0, Jetty 12.1.10, Tomcat 11.0.23, OpenTelemetry 1.64.0 et Kubernetes Java Client 27.0.0. SSL activé par défaut par service pour les clients HTTP Infrastructure Ça coûte combien de faire tourner un LLM local sur son Apple Silicon ? towardsdatascience.com/how-much-does-a-local-llm-actually-cost-to-run-i-measured-every-watt-on-apple-silicon Coût électrique des LLM locaux sur Mac Apple Silicon Un modèle 120B (MoE) coûte 5x à 10x moins cher qu'un modèle 27B (Dense). Le coût dépend du débit (tokens/seconde), pas du nombre de paramètres. Modèle dense –> Charge 100% des poids par token = lent et très énergivore. MoE (Mixture of Experts) –> N'active qu'une fraction des poids = rapide et économe. Conclusion : Pour réduire la facture électrique, choisir des modèles MoE quantifiés (haut débit). Kubernetes 1.36 (Haru) : sécurité renforcée et alignement IA infoq.com/news/2026/05/kubernetes-1-36-released Kubernetes est la plateforme open source de référence pour l'orchestration de conteneurs, portée par la CNCF. La version 1.36 nommée Haru apporte 70 améliorations : 18 passent stables, 25 en bêta et 25 en alpha, avec 106 entreprises et 491 contributeurs. Les user namespaces passent en disponibilité générale, isolant le root du conteneur de celui de l'hôte. Les Mutating Admission Policies passent en GA, remplaçant les webhooks par des règles CEL natives plus performantes. L'autorisation de l'API kubelet devient plus fine, remplaçant le droit trop large nodes/proxy. Le labeling SELinux des volumes utilise désormais mount -o context, accélérant le démarrage des pods. Plusieurs avancées ciblent les charges IA : gang scheduling en bêta, préemption consciente des groupes de pods, et allocation dynamique de ressources activée par défaut pour le partage fin des GPU. Le redimensionnement vertical des pods en place passe en bêta et activé par défaut, ajustant CPU et mémoire sans redémarrage. Suppression du plugin gitRepo, source de risque de sécurité, et du mode IPVS de kube-proxy, tous deux dépréciés de longue date. Avec la sortie de 1.36, la version 1.34 devient la plus ancienne branche encore supportée et entre en maintenance, ne recevant plus que des correctifs critiques avant sa fin de support. Terraform vs OpenTofu en 2026 : la divergence est actée ecorpit.hashnode.dev/terraform-vs-opentofu-in-2026-the-fork-has-diverged-so-which-do-you-standardize-on env0.com/insights/opentofu-in-2026-what-the-terraform-fork-became-after-three-years-of-independence Terraform est l'outil historique d'Infrastructure as Code de HashiCorp, OpenTofu en est le fork open source lancé après le changement de licence. HashiCorp est passé de la licence MPL 2.0 a la BUSL 1.1 en aout 2023, ce qui a poussé une partie de la communauté a créer OpenTofu sous la Linux Foundation. IBM a racheté HashiCorp pour 6,4 milliards de dollars, finalisé en février 2025, tandis qu'OpenTofu rejoignait le CNCF comme projet sandbox en avril 2025. OpenTofu prend de l'avance sur des fonctionnalités inédites : chiffrement du state côté client depuis la v1.7, valeurs éphémères qui gardent les secrets hors du state depuis la v1.11, et prevent_destroy dynamique en v1.12 (mai 2026). Terraform garde l'avantage sur l'orchestration managée avec Terraform Stacks, désormais en disponibilité générale, sans équivalent natif côté OpenTofu. Le coût diverge fortement : HCP Terraform facture jusqu'à 0,99 dollar par ressource gérée et par mois, alors qu'OpenTofu reste une CLI gratuite couplée au backend de son choix. Fidelity Investments a migré plus de 2000 applications et 50000 fichiers d'état vers OpenTofu, la complexité venant surtout de l'écosystème (CI/CD, gouvernance) plutôt que du binaire lui-même. OpenTofu reste compatible avec les configurations Terraform jusqu'a la version 1.6.x, mais les versions Terraform plus récentes n'offrent plus aucune garantie de compatibilité. Pour les secteurs régulés, le chiffrement natif du state par OpenTofu et sa gouvernance ouverte sont des arguments forts face aux exigences de protection des données. La recommandation qui ressort des deux articles : partir sur OpenTofu pour les projets neufs et rester sur Terraform si l'on est déjà investi dans HCP Terraform et ses fonctionnalités de gouvernance. OTel est à la peine ? matduggan.com/otel-isnt-going-well-and-i-made-a-spreadsheet-about-it Le développement d'OTel est un peu au point mort Périmètre démesuré : Volonté de supporter un nombre gigantesque de langages, bibliothèques et frameworks. Pénurie critique de mainteneurs : Les données montrent une hyper-concentration du travail ; de nombreux SDK (comme PHP ou Ruby) dépendent d'une ou deux personnes seulement. Stabilité paralysante : La règle interdisant toute modification d'une fonctionnalité déclarée « stable » crée une peur de valider les nouveautés, entraînant des mois de débats. Solutions proposées par l'auteur : Créer un niveau « Bêta » temporaire (ex: 12 mois) entre les statuts « Expérimental » et « Stable ». Faire preuve de transparence sur les différences de qualité/maintenance entre les langages (ne pas mettre Go et Ruby sur le même plan). Communiquer activement sur le besoin urgent de nouveaux mainteneurs. Assouplir la politique de stabilité en acceptant des breaking changes bien documentés. Honeycomb transforme son infrastructure Kafka honeycomb.io/blog/transforming-how-we-run-kafka-honeycomb Honeycomb est une plateforme d'observabilité dont Kafka est le coeur du pipeline d'ingestion, traitant des millions d'événements par seconde. L'entreprise a migré de Confluent Platform auto-hébergée vers Apache Kafka 4.1.1 en mode KRaft. Le nouveau cluster tourne sur AWS EKS avec Strimzi comme couche d'orchestration Kubernetes. Motivation principale : la récupération après remplacement de broker était passée de 8-12h à 48-72h avec l'ancienne stack. Confluent imposait aussi sa solution propriétaire de Tiered Storage, impossible à corriger en interne. Un incident de décembre 2025 ayant vidé un cluster a révélé une fenêtre d'opportunité pour migrer. La migration s'est faite progressivement sur six clusters, de dogfood jusqu'à la production. Les producteurs sont basculés avant les consommateurs, avec une courte fenêtre de downtime assumée entre les deux. Le stockage utilise des NVMe en instance store plutôt que de l'EBS pour minimiser la latence. interessant de voir une société reprendre en main sa compétence et de voir les contraintes de certaines fonctionalités propriétaires Cloud AWS us-west-2 : panne réseau régionale et effet domino chez les fournisseurs SaaS blog.incidenthub.cloud/aws-us-west-2-outage-jul-24-2026 AWS us-west-2 (Oregon) est une région cloud majeure hébergeant de nombreux services et fournisseurs SaaS. Le 24 juillet 2026, une panne matérielle réseau a coupé la connectivité entre la région et le Seattle Metro pendant environ 20 minutes. Particularité notable, seule la couche de connectivité externe a été touchée, le trafic interne à la région a continué de fonctionner normalement. Après la réparation matérielle, une phase distincte de reconvergence des routes a de nouveau causé une connectivité intermittente pendant plusieurs dizaines de minutes. Les clients Direct Connect via EqSe2 ont subi une coupure bien plus longue que le reste, 1h17 au total. Neuf incidents chez sept fournisseurs ont cité explicitement AWS comme cause, dont SendGrid, SparkPost et NinjaOne. Fait marquant, les temps de rétablissement des fournisseurs tiers ont largement dépassé la durée de la panne AWS elle même. NinjaOne a mis 9h29 à se rétablir totalement, avec 150000 appareils tentant de se reconnecter simultanément freinés par des mécanismes de backoff et jitter. SparkPost a mis 6h45 à absorber l'arriéré de courriels accumulé pendant la coupure, avec encore 80 à 90 minutes de retard des heures plus tard. L'article recommande d'identifier ses dépendances en us-west-2 et de prévoir capacité et bascule, l'effet différé pouvant durer bien plus longtemps que l'incident initial. Rapport Cloudflare Radar sur les perturbations Internet au Q2 2026 blog.cloudflare.com/fr-fr/q2-2026-internet-disruption-summary Cloudflare Radar est la plateforme qui analyse en temps réel le trafic mondial pour détecter pannes, coupures et censures Internet. l'instabilité est le nouveau normal Le super-typhon Sinlaku a fait chuter le trafic de près de 80% à Guam les 13 et 14 avril. Deux séismes de magnitude 7,5 ont fortement dégradé la connectivité au Venezuela le 24 juin. Une coupure électrique a provoqué cinq heures de perturbation en Tanzanie le 27 juin. En Iran, la connectivité s'est stabilisée à 59% du niveau normal après 88 jours de coupure. Le Soudan a imposé dix coupures programmées pendant les examens nationaux mi-avril. L'Irak a coupé Internet à trois reprises pour lutter contre la fraude aux examens. Des frappes de drones ont endommagé la région AWS me-central-1 aux Émirats arabes unis. Un renouvellement de clés DNSSEC a rendu les sites .de inaccessibles en Allemagne le 5 mai. Une rupture de câble sous-marin a fait chuter le trafic de 60% à Sainte-Lucie fin juin. l'instabilité est le nouveau normal Un ingénieur Google débranche une zone entière de Google Cloud https://www.theregister.com/off-prem/2026/09/04/google-engineer-unplugged-every-fiber-they-could-see-and-surprise-took-down-a-chunk-of-the-g-cloud/5294418 Google Cloud est la plateforme d'infrastructure cloud de Google, organisée en régions et zones de disponibilité comme us-central1. Le 1er septembre 2026, un ingénieur a débranché par erreur des câbles fibre optique lors d'une opération de maintenance matérielle routinière dans la zone us-central1-b. En 13 minutes, il a déconnecté 100 % des chemins de fibre optique de tous les équipements de cette portion de la zone. Les machines virtuelles hébergées dans la zone touchée sont devenues injoignables, avec une perte de paquets élevée. Le taux de chute du trafic réseau pour les ressources concernées a atteint 100 %. L'incident a duré 4 heures et 11 minutes, de 7h41 à 11h52 heure du Pacifique. Google a détecté l'anomalie, reroute le trafic, identifié les liaisons optiques débranchées puis rebranché physiquement les fibres avant le retour à la normale. Les post-mortems d'incident cloud sont un classique du podcast, mais l'erreur humaine sur du câblage physique chez un hyperscaler mérite une minute d'antenne. ChatGPT, Claude et Grok en panne presque simultanément le 3 septembre theregister.com/ai-and-ml/…/5294322 ChatGPT, Claude et Grok sont les assistants IA et coding agents désormais utilisés au quotidien par de nombreux développeurs. xAI loue ses datacenters à un certains nombre de fournisseurs de cloud et d'IA. ils ont fait tombé ses concurrents :slightly_smiling_face: Arreter là Le 3 septembre 2026, les trois services sont tombés en panne quasiment en même temps. ChatGPT a connu une panne de 7h43 à 8h17 PT, soit environ 34 minutes, due à une erreur de routage rendant ChatGPT et Codex indisponibles. Claude a subi une panne partielle de 3 heures et 6 minutes touchant Claude.ai, Claude Code, Claude Cowork et l'API Claude, résolue à 16h16 UTC. xAI a commencé à enquêter sur les problèmes de Grok dès 6h30 PT, puis SpaceX a confirmé une panne de son centre de calcul de Memphis. La coïncidence des trois pannes a fait suspecter un fournisseur commun à l'origine du problème. Pour les développeurs devenus dépendants de ces coding agents, l'épisode illustre le risque d'un point de défaillance unique xAI loue ses datacenters à un certains nombre de fournisseurs de cloud et d'IA. Web Nouveautés CSS 2026 : mixins, masonry natif et animations pilotées par le scroll modern-css.com/whats-new-in-css-2026 animation-timeline: scroll() et view() atteignent le baseline cross-browser, Firefox et Safari ayant livré le support complet. Plus besoin de préfixes ni de librairie JS. @starting-style devient cross-browser : animations d'entrée depuis display: none sans hack de timing JS. Firefox 147 amène l'anchor positioning au baseline, plus les view transition types et la Navigation API. Les menus contextuels via popover CSS arrivent aussi. Data et Intelligence Artificielle Guillaume a porté le SDK Python d'Antigravity en Java… en utilisant Antigravity lui même comme assistant ! glaforge.dev/posts/…/the-unofficial-antigravity-sdk-for-java SDK Java non officiel pour Antigravity, rétro-ingénierie du SDK Python pour exploiter un binaire Go sous-jacent. Cas d'usage : pipelines CI/CD, applications d'entreprise (Spring Boot), outils internes, surveillance en arrière-plan, interfaces personnalisées. Gestion des ressources : implémente AutoCloseable(try-with-resources) pour lancer et fermer proprement le processus Go. Exécution de code Java personnalisé : exposition de méthodes Java comme outils IA via les annotations @Toolet@Param. Streaming et programmation réactive : prise en charge des CompletableFuture, des callbacks (chatStream), et deFlow.Publisher. Fonctionnalités avancées : persistance de session, protocole MCP, politiques de sécurité, entrées multimodales, et sorties structurées mappées sur des records Java. Le SDK Java pour le protocol Agent2Agent sort sa version 1.2.0 medium.com/google-cloud/a2a-java-sdk-1-2-0-final-released… Prise en charge de la spécification A2A 1.0. Sécurité renforcée : Vérification stricte des autorisations de lecture sur les tâches référencées et implémentation d'une logique de blocage par défaut (fail-closed). Intégration facilitée : Support du câblage programmatique des autorisations pour les environnements non-CDI (comme Spring). Contrôle des flux : Ajout du Task Stream Lifecycle Hook pour surveiller et gérer le cycle de vie des abonnements aux flux d'événements. Stabilité des données : Immutabilité stricte imposée sur les enregistrements de spécifications pour empêcher toute modification accidentelle. Documentation : Lancement d'une documentation web multi-versions et d'un Javadoc agrégé pour tous les modules. Corrections de bugs : Résolution de problèmes liés à la synchronisation des tâches, aux réponses de streaming et aux conditions de concurrence HTTP. Breaking changes : Nécessite une migration suite à la modification de certaines méthodes d'autorisation, la réorganisation de packages et le renommage de l'état TaskState.UNRECOGNIZED en TaskState.TASK_STATE_UNSPECIFIED. Article sur le blog de JetBrains : blog.jetbrains.com/idea/2026/08/intellij-idea-goes-lsp pas trop de temps Langchain4j continue sa progression github.com/langchain4j/langchain4j/…/1.18.0 github.com/langchain4j/langchain4j/…/1.19.0 github.com/langchain4j/langchain4j/…/1.17.0 Introduction du pattern Debate pour lancer des sous agents dans rechercehnt et entrent dans un debat critique sur une decision avant qu'un juge decide (1.17) compensation d'action d'un outil avec @ReverseTool (1.17) Ajout du pattern Belief-Desire-Intention (1.18): belief est l'état du monde cru, desire est la liste des objectifs, intention est le plan pour avancer un ou plusieurs objectif Support d'un systeme crash resilient dans l'approche Human in the loop avec des checkpoints nestés (1.18) Support Open AI TextToSpeech (1.18) Support de Mistral batch chat (1.18) support MCP client 2026-07-28 (1.19) Anthromic batch chat et Google thinking mode (1.19) Embabel atteint 1.0 GA github.com/embabel/embabel-agent/…/v1.0.0 embabel d'eloigne de Spring AI ne s'appuie que sur Spring (notamment tool calling) nettoyage des explorations autour du pattern GOAL avant a 1.0 ajout observabilite (dont le cout) les approches de retry solidifiées et d'autres choses toujours basées sur la description de goals typés et des dependences entre eux via les types MCP 2026-07-28 : le protocole devient stateless blog.modelcontextprotocol.io/posts/2026-07-28 MCP (Model Context Protocol) est le protocole standard permettant aux LLM et agents IA de communiquer avec des outils, ressources et serveurs externes. Cette version marque le plus gros changement depuis le lancement du MCP distant il y a 18 mois. Le protocole passe d'un modèle bidirectionnel avec état à un modèle stateless en requête/réponse. Suppression de la poignée de main initialize/initialized et du header Mcp-Session-Id, chaque requête devient autoportante. N'importe quelle requête peut désormais être routée vers n'importe quelle instance de serveur derrière un load balancer classique, sans stockage partagé. Introduction des Multi Round-Trip Requests (MRTR) pour remplacer les requêtes initiées par le serveur, via un resultType input_required et des inputResponses. Nouveaux headers Mcp-Method et Mcp-Name pour permettre aux gateways de router et autoriser sans parser le JSON. Les résultats de tools, prompts et resources deviennent cacheables grâce aux paramètres ttlMs et cacheScope. Renforcement sécurité avec la validation d'issuer RFC 9207 pour éviter les attaques de confusion entre serveurs d'autorisation, et transition de DCR vers CIMD. Roots, Sampling et Logging sont dépréciés avec douze mois de support garanti, tout comme le transport legacy HTTP+SSE. Un site qui référence les skills pour la JVM (framework, langage, build…) jvmskills.com Frameworks : Spring, Quarkus, Jakarta EE, Reactor, Camel Java : bonne pratiques, conventions, guides de mise à jour à niveau LTS, API spécifiques (streams, optionals, logs…) Bases de données : ORM, validation, modélisation PostgreSQL, vectorielle avec pgvector Tests et qualité : TDD, mutation testing, debogage avec JDB Workflows dev et archi : commits git, domain modeling Outils et diagnostics JVM : JFR, Jstall, JSpecify Une skill n'est pas une librairie https://devx.writizzy.blog/p/un-skill-nest-pas-une-lib Les skills sont des éléments de configuration en prose pour agents IA comme Claude, distribués via des marketplaces à la manière de librairies logicielles. Frédéric Camblor critique cette analogie car partager un skill n'est pas la même chose que le mutualiser durablement. Écrire un skill prend 30 minutes mais l'adopter ailleurs coûte cher en appropriation et en maintenance. Forker un skill s'avère souvent plus efficace que de chercher à converger vers une version commune. Contrairement au code, les régressions d'un skill ne sont pas détectables automatiquement. Un skill peut se dégrader silencieusement sur plusieurs cas d'usage en corrigeant un autre. Les skills vieillissent vite car les modèles progressent et intègrent naturellement certaines bonnes pratiques. Le skill-creator d'Anthropic permet d'évaluer un skill via des jeux de cas et des mesures de variance. L'auteur distingue quatre sphères de partage : personnelle, équipe, outil et marketplace. Il propose un cycle partage puis appropriation puis duplication puis divergence plutôt qu'une installation collective figée. Les modèles Anthropic introduisent un filigrane (watermark) dans les textes qu'ils génèrent https://www.anthropic.com/news/claude-text-watermark Claude est l'assistant IA d'Anthropic, et le watermarking est une technique permettant de marquer discrètement un contenu généré par IA pour en tracer l'origine. Anthropic annonce que les futurs modèles Claude intégreront un filigrane numérique invisible dans le texte généré. Le principe exploite les choix de mots équivalents que le modèle fait naturellement, en les orientant via une clé cryptographique plutôt qu'un tirage aléatoire. Le texte produit reste indiscernable à l'œil nu, sans caractères cachés, sans ralentissement ni coût supplémentaire. Seule la personne possédant la clé correspondante peut détecter la présence du filigrane. Le filigrane est plus fiable sur les textes longs et créatifs, moins sur du texte factuel, du code ou après une édition manuelle poussée. Il ne prouve pas qu'un texte est écrit par IA, ni n'identifie l'auteur ou la conversation d'origine, il donne seulement une probabilité d'implication de Claude. Une API de détection est proposée en accès restreint aux régulateurs, forces de l'ordre, médias et vérificateurs de faits. Pour les fichiers non textuels comme les images ou les PDF, Anthropic s'appuie sur le standard C2PA. Cette initiative s'inscrit dans le Code de Pratique de l'UE sur la transparence des contenus IA, signé par Anthropic et environ 190 autres acteurs, en lien avec la loi européenne sur l'IA. GPT-6 Astra, le nouveau modèle d'OpenAI face à Claude Fable 5.1 https://openai.com/index/gpt-6-astra/ GPT-6 Astra est le nouveau modèle phare d'OpenAI, annoncé le 3 septembre 2026 comme le plus intelligent et le plus aligné de l'entreprise. Le modèle arrive deux jours après Claude Fable 5.1, à un tarif affiché comparable, dans une course accélérée aux modèles de code et de raisonnement. Astra revendique 98 % sur FrontierMath Tier 4, 99,9 % sur ARC-AGI-3 et 100 % sur ExploitBench. Fenêtre de contexte d'environ 1,05 million de tokens. Tarification API, 10 dollars par million de tokens en entrée, 50 dollars en sortie, et 1 dollar par million pour les tokens en cache. Au-delà de 272 000 tokens en entrée, toute la requête est facturée au double sur l'entrée et une fois et demie sur la sortie. Astra est le premier modèle d'OpenAI à franchir le seuil interne critique en cybersécurité. La version publique refuse les tâches offensives avancées comme générer des preuves de concept d'exploits. Le déploiement est progressif, les entreprises du programme de cybersécurité Daybreak d'OpenAI y accèdent en premier, avant ChatGPT Plus, Pro, Business, Enterprise, l'API et AWS. Même logique de diffusion contrôlée que chez Anthropic avec Mythos 5.1 : deux jours d'écart, deux modèles de tête, et la même question de savoir qui accède en premier aux capacités les plus sensibles. Outillage JetBrains s'est lancé dans les LSP (Language Server Protocol) avec une extension IntelliJ pour VS Code et assimilés marketplace.visualstudio.com/items?itemName=JetBrains.intellij-s… Nouveau produit : Lancement de l'extension Java & Kotlin by IntelliJ IDEA pour les éditeurs basés sur VS Code (incluant Cursor). Technologie : Utilisation du standard LSP (Language Server Protocol). Objectif : S'adapter au développement piloté par les agents IA, qui nécessite des fonctionnalités IDE légères et standardisées. Fonctionnalités clés : Support des projets Java, Kotlin et mixtes. Débogage (DAP). Complétion intelligente, navigation et analyse de code. Refactoring. Prise en charge de Maven, Gradle et Bazel. Disponibilité : Téléchargeable via le Visual Studio Marketplace et l'Open VSX registry. Licence / Prix : Gratuit durant la phase de preview (évaluation renouvelable de 30 jours). Nécessitera un abonnement IntelliJ IDEA Ultimate après la preview. (Note : Le LSP purement Kotlin reste gratuit et open-source). Avenir : Développement en cours pour optimiser les flux de travail avec les agents IA en ligne de commande (ex: Claude Code, Codex) afin de réduire la consommation de tokens. Après son acquisition par SpaceX, Cursor perd l'accès aux modèles OpenAI https://openai.com/index/our-decision-on-cursor-following-its-acquisition-by-spacex/ decision difficile mais Elon ment comme un arracheur de dent (et c'est un competiteur donc bon ça nous arrange) David Pilato a créé un thème spéciale pour les gens pour les devrel, ou qui font des talks à droite à gauche, pour le moteur Hugo https://david.pilato.fr/posts/2026-09-07-hugo-theme-devrel/ hugo-theme-devrel, thème Hugo (MIT) pour Developer Advocates et conférenciers, fonctionnant comme un module superposé au thème Dream. Gestion des conférences (cartes Leaflet), présentations (PDF, YouTube, co-auteurs), vues dédiées (archives, sujets récurrents, vidéos) et recherche Pagefind. Chaque intervention est un page bundle YAML structuré comme une base de données relationnelle compilée par Hugo. Architecture Airbnb refond son authentification en architecture server-driven, 60 % de code en moins https://www.infoq.com/news/2026/09/airbnb-server-driven-login/ Airbnb a restructuré son authentification autour d'un modèle en deux phases, identification du compte (email, téléphone ou connexion sociale) puis choix du challenge d'authentification décidé côté serveur selon le contexte utilisateur. Ce qui est interessant c'est que choisir la method d'authentification est côté serveur et adaptative, comme si c'était une révolution Arreter là Un moteur de politique serveur sélectionne la méthode d'authentification optimale avec des solutions de repli, permettant des adaptations régionales comme l'OTP WhatsApp au Brésil ou des fournisseurs d'identité locaux en Corée du Sud sans nouvelle version client. Un Challenge Picker propose des méthodes alternatives classées par probabilité de succès en cas d'échec. Résultat chiffré, 60 % de code d'authentification en moins et 100 Ko de moins sur le bundle client web. Méthodologies Les nouvelles règles d'ingénierie du contexte pour les modèles Claude 5 x.com/trq212/status/2080710971228918066 Partage par Thariq des apprentissages sur l'ingénierie du contexte et le prompt engineering pour les nouveaux modèles Claude 5 (comme Claude Opus 5 et Claude Fable 5) utilisés dans Claude Code. Évolution majeure vers le dés-empirement (unhobbling) : plus de 80 % du prompt système de Claude Code a pu être supprimé sans perte sur les évaluations de code, les modèles récents faisant preuve d'un bien meilleur jugement contextuel. Passage des règles strictes au jugement : au lieu d'interdire les commentaires ou d'imposer des contraintes lourdes, les modèles s'adaptent désormais au code environnant et font appel à leur propre discernement. Remplacement des exemples par la conception d'interfaces : fournir des exemples figés restreint l'exploration du modèle, d'où l'importance de concevoir des outils et des fichiers plus expressifs. Adoption de la divulgation progressive (progressive disclosure) : chargement dynamique du contexte (via des compétences ou des outils à chargement différé comme ToolSearch) pour éviter de saturer la fenêtre de contexte avec des instructions fixes. Utilisation d'une mémoire automatique et de références riches (artefacts HTML, suites de tests, fonctions de référence) plutôt que de fichiers CLAUDE.md pléthoriques ou de consignes répétitives. Recommandation pour les fichiers CLAUDE.md et les Skills : les garder légers, se concentrer sur les pièges spécifiques (gotchas) du dépôt, et structurer les guides sous forme d'arborescences modulaires pour ne charger que le nécessaire. Niveau d'adoption des agents IA de codage selon une étude de JetBrains blog.jetbrains.com/research/2026/08/ai-coding-agent-adoption-2026 Adoption massive : 90 % des développeurs professionnels utilisent des agents d'IA de codage au moins une fois par semaine, et 68 % quotidiennement. Claude Code domine : Il devient le nouveau leader du marché avec 39 % d'adoption mondiale (47 % aux États-Unis), détrônant largement ses concurrents. Déclin de GitHub Copilot : L'ancien leader perd de sa superbe, passant de 29 % à 21 % d'adoption, bien qu'il conserve une très forte notoriété (79 %). Percée de Codex : Sa croissance est fulgurante, son taux d'adoption ayant été multiplié par 5 en quelques mois (de 3 % à 16 %). Recul de Cursor : L'outil connaît une légère baisse, passant de 18 % à 12 % d'adoption, principalement due à une forte chute sur le marché chinois. Écosystème diversifié : JetBrains AI atteint 9 % d'adoption. Des alternatives comme OpenCode (7 %) et Google Antigravity (6 %, mais très populaire en Inde à 15 %) continuent de s'implanter. L'IA a cassé les hypothèses de la CI… ou pas https://stack72.dev/ai-broke-the-assumptions-behind-ci/ Paul Stack (ex-Pulumi) explique que l'intégration continue a toujours mêlé deux rôles distincts, exécuter la vérification du code et coordonner les fusions. avec les agents, la pression sur la CI augmente, car ils ne testent pas end to end tout le temps ils ont maintenant des workflows qui verifient tests, lint, revue d'agent etc dans un env local isolé donc c'est pre PR push Il propose de séparer vérification (exécution), attestations structurées (hash de commit, checksums SHA256) et CI, réduite à la validation et à la coordination des fusions. Sa thèse, les agents IA peuvent désormais vérifier tout le code localement avant même l'ouverture d'une pull request, ce qui bouleverse cet équilibre. l'attestation vient ensuite et la CI est une étape de vérification (attestation de commit et de tests et si branche a bougé, repart à l'execution) Martin Fowler, qui a repéré l'article dans ses Fragments du 1er septembre 2026, réplique que la vraie CI a toujours exigé une vérification locale avant de pousser le code. ca demande une chaine d'attestation forte quid de garder les metriques historique de CI Sécurité France Passoire: une analyse sur les différents vols de données des services publics de ces dernières mois https://www.cybernetica.fr/piratage-des-impots-comment-en-est-on-arrive-la/ Analyse du piratage massif de la DGFiP et d'autres administrations françaises en 2026, révélateur de failles systémiques de cybersécurité de l'État. Intrusion détectée fin juin à la DGFiP, mais l'exfiltration de 678 000 entrées fiscales n'a été découverte qu'en août lors de leur mise en vente. Données volées : noms, revenu fiscal de référence, taux de prélèvement, adresse, téléphone. Une seconde attaque du même pirate a visé le cadastre fin juillet, exposant plus de 2 millions de personnes. L'Éducation nationale a aussi été piratée fin juillet, données de tous les agents depuis 2001 exposées. Cause principale : modèle de sécurité fondé sur le périmètre physique plutôt que sur le zero trust, sans contrôle après authentification. Le télétravail post Covid a étendu les accès distants sans reconstruire les modèles de confiance. Aucun système de détection d'exfiltration n'existait, la fuite n'a été révélée que par le pirate lui-même. La transposition de la directive NIS2 est bloquée en France depuis septembre 2025, la CJUE a condamné le pays à des astreintes. L'article souligne un désengagement croissant des Etats-Unis en matière de cybersécurité internationale et une dépendance technologique accrue de la France. Loi, société et organisation Ce que l'IA change vraiment au métier de manager shapeandship.ai/p/ce-que-lia-change-vraiment-au-metier-de-manager Retour d'expérience et analyse par Mathilde Rigabert sur l'impact réel de l'IA générative dans le quotidien d'un Engineering Manager. L'IA excelle pour automatiser la reconstitution factuelle de l'activité (lecture de PRs, commits, reviews) nécessaire aux 1:1 et entretiens annuels, mais elle offre une vision uniquement quantitative et nécessite d'être croisée avec des notes de terrain. L'IA rend le maintien de la qualité et des standards plus difficile : selon une étude Faros AI sur 22 000 développeurs, les PRs mergées sans aucune revue ont augmenté de 31 %, fragilisant la compréhension commune apportée par le pairing et les revues de code. Le temps gagné par l'IA ne permet pas d'augmenter massivement le span of control (seulement 2 ou 3 personnes de plus), car l'IA compresse la collecte d'informations mais pas les conversations humaines complexes ou l'accompagnement du changement. Les compétences d'orchestration et de gestion de sujets multiples acquises par les managers facilitent leur transition vers le pilotage de plusieurs agents IA en contribution individuelle. Le piège actuel réside dans l'accumulation des casquettes (manager, tech lead, product owner, contributeur, pompier), conduisant à l'épuisement et au délaissement du travail de fond sur l'organisation et l'humain. Le temps libéré par l'IA doit être réinvesti dans le travail invisible qui fait tenir le système (suivi des actions de rétro, analyse de métriques, coaching), que personne ne réclame à court terme mais dont l'absence fragilise les équipes à long terme. Je regrette d'avoir migré vers Codeberg xn–gckvb8fzb.com/i-regret-migrating-to-codeberg L'auteur explique pourquoi il regrette d'avoir quitté GitHub pour Codeberg, à la suite des récentes modifications des conditions d'utilisation (ToS) de la plateforme. Codeberg a interdit les projets principalement générés par des LLM ainsi que les projets liés aux cryptomonnaies via des propositions de l'Assembly 2026, au motif qu'ils nuisent à sa réputation. blog.codeberg.org/protecting-our-floss-commons-from… Critique de l'argument de Codeberg sur l'absence de communauté des vibe coders, en rappelant que la majorité des logiciels libres (FOSS) sont créés par des développeurs solos sans communauté au sens romancé du terme. Ironie soulignée concernant la posture de Codeberg et Forgejo, qui a hérité de la communauté de Gitea après un hard fork avant de faire la leçon aux développeurs individuels. Alerte sur le risque de censure idéologique : interdire des catégories entières plutôt que de traiter les abus réels ou la consommation d'infrastructure crée un précédent dangereux pour une forge qui se veut libre. Proposition de solutions alternatives pour gérer l'impact des LLM et de la crypto : déclaration obligatoire via des cases à cocher, hébergement sur des tiers d'infrastructure spécifiques payants ou sous quotas, et disclaimers automatiques. Décision de l'auteur de quitter Codeberg pour mettre en place son propre serveur Git personnel afin d'éviter la dépendance à une plateforme qui modifie ses règles de manière unilatérale. Cloud souverain : Airbus choisit Scaleway pour l'hébergement de ses applications critiques https://www.usine-digitale.fr/aeronautique-spatial/airbus/cloud-souverain-airbus-choisit-scaleway-pour-lhebergement-de-ses-applications-critiques.OHBVBMSZIJELNOKN6G5F6B7NSI.html Scaleway est le cloud provider français filiale du groupe Iliad, positionné comme alternative souveraine aux hyperscalers américains. Airbus a lancé un appel d'offres de six mois consultant une cinquantaine d'acteurs dont OVHcloud, Thales, Google S3NS et Microsoft Bleu. Scaleway a été retenu pour héberger les applications critiques liées à la conception d'aéronefs, l'ingénierie, la production industrielle et les opérations. Le contrat prévoit la migration d'environ 70 applications d'ici 2028, puis jusqu'à 900 applications sur 5 à 6 ans. Le montant du contrat n'a pas été communiqué. Scaleway revendique zéro actionnaire, zéro employé et zéro filiale hors Union européenne pour garantir une protection contre les lois extraterritoriales. Damien Lucas, PDG de Scaleway, évoque une immunité complète face aux évolutions politiques et législatives externes. La plateforme doit aussi accélérer les usages d'intelligence artificielle d'Airbus, avec les modèles de Mistral AI déjà déployés chez Scaleway. Catherine Jestin, responsable numérique d'Airbus, souligne que cette intégration accélère la démarche IA du groupe. Ce choix ne remet pas en cause la stratégie multicloud d'Airbus, Scaleway venant compléter les fournisseurs existants pour les charges nécessitant le plus haut niveau de gouvernance et de résilience. Debian adopte une résolution sur l'usage responsable de l'IA générative lwn.net/Articles/1091231 La discussion sur l'usage des LLM dans Debian s'est tenue du 23 juillet au 13 août 2026, suivie d'un vote du 15 au 28 août 2026. 1045 développeurs Debian étaient éligibles à voter, avec un quorum de 48,49 votes largement dépassé par les huit options en lice. Les options allaient d'une interdiction stricte des contributions générées par LLM inscrite dans le contrat social à une acceptation encadrée des contributions IA. L'option gagnante au classement Condorcet est Responsible Use of Generative AI, devant Allow AI-Assisted Contributions with conditions et A cautious approach to generative AI. Le texte adopté n'interdit ni n'encourage l'usage d'outils d'IA générative dans le développement de Debian. Il exige que toute contribution, quels que soient les outils utilisés pour la produire, respecte les mêmes standards de qualité, correction, maintenabilité et conformité légale. Les contributeurs doivent comprendre, relire, tester et si besoin modifier la production assistée par IA avant de l'intégrer à Debian. Les informations sensibles du projet ne doivent pas être transmises à des fournisseurs d'IA non fiables, et la divulgation de l'usage de l'IA est encouragée sans être obligatoire. Le détail du vote et le texte complet de la résolution sont disponibles sur la page officielle [debian.org/vote/2026/vote_002](https://www.debian.org/vote/2026/vote_002). Contraste direct avec l'OpenJDK, qui a publié une politique interdisant le code généré par LLM (épisode 340), et avec l'auteur de jqwik qui a piégé sa librairie contre les agents. Conférences Nous contacter Pour réagir à cet épisode, venez discuter sur le groupe Google https://groups.google.com/group/lescastcodeurs Contactez-nous via X/twitter https://twitter.com/lescastcodeurs ou Bluesky https://bsky.app/profile/lescastcodeurs.com Faire un crowdcast ou une crowdquestion Soutenez Les Cast Codeurs sur Patreon https://www.patreon.com/LesCastCodeurs Tous les épisodes et toutes les infos sur https://lescastcodeurs.com/

Twenty fourth Sunday of Ordinary Time - "Jesus speaks of forgiveness and then gives a parable to express why we should be grateful and generous."

The Fork In Your Ear Ep#221 "Author, Podcaster, Game Designer" - Podcast Show Notes & Summary 9-12-26   Quick Summary  Tim walks in barely held together and introduces himself as author, podcaster, and game designer — because he just dropped a playable HTML prototype of his Color Clash-inspired dual-grid RTS into the Fork Discord. The ring actually lands on Life first: Nate's kids demand VR mid-show, California is an air fryer, lane-splitters want six inches of courtesy, and both households are eating unexpected bills. Then the game firehose opens — Sony tells a courtroom that reasonable consumers know they don't own digital games, Xbox Cloud gets a 15-hour Ultimate cap, Nintendo dumps a Zelda 40th and a second Direct in two days, Ocarina of Time remake looks like a stop-motion maquette, Metroid Ravenous is metal as hell, and Kojima's canceled Sony IP is now an Xbox game. Entertainment is Coyote vs. Acme beating Warner Bros. at its own gag, Chad Powers season two sneaking back from the dead, Spider-Noir winning Emmys then getting canceled, and Nick Offerman as Big the Cat. Tech is Mac Studio M5 Max sticker shock, Apple's September event, the iPhone Duo foldable, and John Ternus's first week as CEO. Classic four-and-a-half-hour Fork: family chaos, Sony fumbles, Nintendo cooking, and Tim finally putting a game on the table.   Detailed Show Notes  

Este es el primer episodio de una serie de cuatro que voy a dedicar a herramientas que he implementado y que uso en mi día a día. Las cuatro comparten stack: Rust en el backend y React con TypeScript en el frontend. Y la primera es, sin duda, una de las que más me facilitan la vida: Popuplatrs.¿Te suena el ritual de publicar un artículo y tener que abrir Telegram, luego Mastodon, luego X, luego LinkedIn, luego Bluesky, y encima personalizar el texto para cada plataforma? Pues eso es exactamente lo que Popuplatrs elimina de tu día a día. Le das uno o varios feeds RSS, Atom o YouTube, y él se encarga de leer las novedades y publicarlas automáticamente en las redes que le configures. Con plantillas personalizables, programación de horarios, reintentos automáticos y un panel web desde el que controlarlo todo.En este episodio te cuento por qué me decidí a crear esta herramienta, qué alternativas existen (Buffer, Hootsuite, IFTTT, Zapier) y por qué ninguna me convencía al ser SaaS o no estar pensadas para funcionar a partir de feeds. También te explico la arquitectura técnica: Rust con Axum, SQLite en modo WAL, autenticación OIDC con Pocket ID, y un sistema de plantillas con MiniJinja que te permite personalizar el mensaje para cada red social.Popuplatrs soporta hasta nueve publicadores diferentes: Telegram, X (Twitter), Mastodon, Bluesky, LinkedIn, Threads, Discord, Matrix y OpenObserve para logging. Cada uno con su propia configuración de autenticación y límites de caracteres. Por ejemplo, en Bluesky publica respetando el límite de 300 caracteres, en X primero lanza el título y luego un reply con el enlace para aprovechar mejor el espacio, y en Discord usa webhooks que se configuran en segundos.El sistema de plantillas es una de las partes que más me gustan. Usa MiniJinja, un motor compatible con Jinja2, y te permite definir plantillas distintas para cada plataforma. Puedes truncar el texto a un número de caracteres, limitar las palabras, eliminar HTML, y combinar el título con la descripción como más te convenga. Todo desde el panel web, sin tocar código.Y por supuesto, te cuento cómo tenerlo corriendo en tu servidor en cinco minutos con Docker. Porque si algo me gusta es que las herramientas sean fáciles de desplegar.Capítulos:0:00 - Introducción: el problema de publicar en redes sociales1:45 - Alternativas existentes y sus limitaciones3:00 - Qué es Popuplatrs: origen, nombre y características principales4:15 - Arquitectura técnica: Rust, Axum, SQLite y Pocket ID5:45 - Fuentes soportadas: RSS, Atom y YouTube7:00 - Publicadores: hasta nueve plataformas sociales8:30 - Panel web: dashboard, logs y republicación de errores10:30 - Programación, reintentos y control anti-spam12:00 - Motor de plantillas y personalización por plataforma13:30 - Despliegue con Docker Compose, Pocket ID y despedidaMás información y enlaces en las notas del episodio

The most important EdTech skill might not be knowing which tool to use. It might be knowing when technology can actually help.New apps, platforms, and AI tools will always compete for your attention. Trying to keep up with all of them isn't realistic—and it isn't necessary. What educators need is a way to recognize opportunities, think critically about technology, and decide whether a tool will actually make learning or work better.That's the idea behind the Anytime EdTech Mindset.In Episode 270, Chris Nesi introduces a practical framework built around seven ideas: Ask, Notice, Your Learners First, Try, Iterate, Make Meaning, and Evolve.This isn't about using more technology. It's about using technology with purpose.Whether you're facing a classroom challenge, looking to improve a workflow, considering a new AI tool, or simply wondering if there's a better way to do something, this episode gives you a framework you can return to anytime.Because you don't need to know every tool.You need a better way to think when a new tool, challenge, or opportunity comes your way.You'll LearnHow to stop chasing every new EdTech tool and focus on real problems instead.Why anytime does not mean all the time when it comes to technology.How to identify what you're actually trying to accomplish before searching for a tool.Why observation matters before trying to solve a classroom or workflow problem.How to put learners—not features or trends—at the center of technology decisions.Why starting small can make trying new technology less intimidating.How to learn from imperfect first attempts instead of abandoning an idea too quickly.How to determine whether technology actually improved learning or simply added technology.When to keep, change, or abandon a tool or approach.How the ANYTIME framework can help you approach future EdTech challenges with confidence.EdTech RecommendationTeacher Hive — teacherhive.appBring the app you've built with AI. Teacher Hive gives it a home.Browse hundreds of apps made by teachers, or add your own. Paste the HTML from ChatGPT, Claude, or Gemini, or drop in a link, and Teacher Hive makes it easy to use with a class, keep for yourself, or share with other teachers.Bee There by Tony Vincent — apphive.us/thereA QR code scanner for classrooms. Reads the screen from across the room and opens links automatically. Show the code again for anyone who missed it. No ads, nothing collected.

David McFall joins Andrew Pla to talk about practical PowerShell, mentorship, automation, and why you do not need to be a PowerShell expert to get serious value from it. David shares how he uses PowerShell across Active Directory, Entra, Microsoft 365, Microsoft Graph, and PDQ, including real-world examples like device posture reporting, identifying hardware gaps, and automating project management. They also dig into learning with AI, knowing when a simple script is enough, the importance of testing before production, and why helping the people around you grow can make everyone's job easier. Key Takeaways: · PowerShell does not have to be complicated to be useful. David approaches PowerShell as a working sysadmin who wants to automate repetitive tasks, reuse existing tools, and solve real problems rather than build everything from scratch. · AI can accelerate learning, but it should not replace understanding. David uses AI to better understand PowerShell concepts and Microsoft Graph, while emphasizing the importance of reviewing, testing, and understanding scripts before putting them into production. · Sharing knowledge makes the whole team stronger. David views himself as a mentor rather than simply a manager. Helping junior team members develop their skills gives them more opportunities while also creating a team that can share responsibility instead of relying on one person who knows everything. Guest Bio: David McFall is an IT infrastructure and operations leader with experience across enterprise cloud platforms, cybersecurity, system administration, Microsoft Defender, Azure, incident response, and automation. Based in Metro Detroit, David combines hands-on technical work with a strong focus on mentoring IT professionals and sharing what he has learned throughout his career. Resource links: ImportExcel (create Excel reports without Excel installed) https://github.com/dfinke/ImportExcel PSWriteHTML (build interactive HTML reports from PowerShell) https://github.com/EvotecIT/PSWriteHTML BurntToast (Windows toast notifications from PowerShell) https://github.com/Windos/BurntToast Maester (automated Microsoft 365 security posture testing) https://maester.dev The PowerShell Podcast on YouTube: https://youtu.be/36VN6K-oE8w

AI is already reading your emails before your subscribers do, and if you're not writing for it, your message might not make it to the inbox at all. Jay breaks down "live text," the actual HTML text in your email that AI tools like Gmail summaries and Microsoft Copilot scan to build inbox previews and rewrite preheaders. Copilot alone just hit 30 million paid users, up 10 million in a single month, so this isn't a niche problem. Jay's rule: the first 150 characters of your email need to carry your most important, most specific information (webinar details, offer terms, whatever the ask is) because that's the window AI summaries pull from. Images and JPEGs don't count, and alt text doesn't count as live text either, no matter what you've been told. He predicts that within six months, half of all preheaders will be AI generated instead of whatever Marketers actually wrote. Daniel adds that the preheader isn't dead, it's just unreliable now. His fix: write your opening body copy so it echoes what you'd want the preheader to say, so if AI does pull from it, the message still lands the way you intended. He also flags that this isn't just an email problem. The same summarization behavior is starting to show up in text messages, and Marketers need to start thinking about how their SMS gets condensed too. The bigger idea: the prettiest, most designed email templates are losing right now. If AI can't read the words inside your design, it doesn't matter how good it looks. Email Marketing is quietly reverting to a text-first format, closer to how it worked 10 to 15 years ago. If you want your emails to survive the next wave of inbox AI, this is the episode for you. Follow Jay: LinkedIn: https://www.linkedin.com/in/schwedelson/ Podcast: Do This, Not That Follow Daniel: YouTube: https://www.youtube.com/@themarketingmillennials/featured Twitter: https://www.twitter.com/Dmurr68 LinkedIn: https://www.linkedin.com/in/daniel-murray-marketing Sign up for The Marketing Millennials newsletter:https://themarketingmillennials.com/ Daniel is a Workweek friend, working to produce amazing podcasts. To find out more, visit:https://workweek.com/

This week, Chris, Andrew, and David dig into a packed mix of Rails news, developer tooling, and the increasingly complicated role AI is playing in everyday coding. They talk about Herb making its way into Rails, the realities of Rails upgrades and stacked PRs, new approaches to Git hosting and object storage, and how Rails is being evaluated in the age of AI agents. They also get into improvements coming to Action Text, Podia's approach to “flavored” Markdown, the never-ending frustrations of HTML email, and why tools like ArchSpec and Rubydex could become especially useful as more code is generated by LLMs. Hit download now to hear more!LinksChris Oliver XAndrew Mason BlueskyDavid Hill LinkedInJudoscale- Remote Ruby listener giftRails World-Sept 23-24, 2026, Austin, TXAdd Herb as an HTML -aware ERB implementation #58552 (GitHub pull request)turbopufferAgents on Rails: The LLM Benchmark Project (Rails Foundation)Agents on Rails : The First Benchmark ReportTiptapArchSpecRubydexHoneybadgerHoneybadger is an application health monitoring tool built by developers for developers.JudoscaleMake your deployments bulletproof with autoscaling that just works.Disclaimer: This post contains affiliate links. If you make a purchase, I may receive a commission at no extra cost to you.Chris Oliver X/TwitterAndrew Mason X/TwitterJason Charnes X/Twitter

כניסתם של כלי AI כמו קלוד-קוד וקרסר הביאה איתן אפשרויות והזדמנוית בלתי נגמרות, אבל הולידה גם סט חדש של אתגרים ובעיות. במאנדיי עובדים החלו לבנות באופן עצמאי ערימות של דשבורדים מקומיים בקבצי HTML סטטים - ללא סנכרון בזמן אמת, ללא הרשאות אבטחה ומשילות, וללא אפשרות לשתף מידע בצורה מסודרת. כדי לפתור את הפער הזה ארגון ה-BI של החברה הקים את Big Brain Studio, אייג׳נט שמאפשר לכל עובד ועובדת לבנות אפליקציות ודשבורדים דינמיים על הקוד והתשתיות הפנימיות של החברה. בפרק השבוע רוני הרניב מדברת עם דורון נחמני, Senior Product Manager בביג בריין וניר סמילגה, Data viz manager במאנדיי על המשמעות של דמוקרטיזציה של פיתוח תוכנה, איך קפצנו מפיתוח כמות של 1,500 דשבורדים שעוזרים לעובדים להציג דאטה לאורך חמש שנים - למעל 2,000 דשבורים בכמה חודשים בודדים, ומה ההזדמנויות והאתגרים שזה מביא איתו. האזינו לפרק על קרמר שהזכרנו בשיחה - 348: דמוקרטיזציה של דאטה – איך בנינו אייג׳נט שמנגיש מידע לכל עובד בחברה See omnystudio.com/listener for privacy information.

Episode SummaryIn this episode, Pete and Tyler compare a decade of print publisher stories, starting with a recent closure that came down to debt from an old acquisition, not readers.They walk through three publishers who each handled the print decision differently: Brew Your Own and Winemaker, Track & Field News, and My Villager. Then they get into the fix that matters most once print goes away, the registration wall, and why your print archive belongs on the web as real HTML, not a flipbook.What You'll LearnOne or two local newspapers close in the US every week. The closure Pete and Tyler discuss this episode came down to debt from an old acquisition, not a lack of readers.Public notices (probate filings, court orders, anything states mandate be published) are why a lot of small papers still print. Qualifying takes twelve straight months of print publication, and the rules differ by state.The New York Times' circulation is about 4% print today. That 4% is loyal and pays well for it, which is a big part of why the print edition still makes sense.Print isn't winning new subscribers anywhere Pete and Tyler have seen. It retains an aging base while digital is where the growth happens.Design-driven, lean-back magazines (fishing, boating, hobbyist niches) can make print the actual product. Transactional, lean-in news content generally can't.Brew Your Own and Winemaker went cold turkey on print and rebuilt their readership within a year.Track & Field News dropped print for nine months, lost half its older readers who wouldn't log in, then relaunched print-on-demand at close to five times the original price.My Villager flipped its free weekly in Saint Paul to paid print and paid digital and grew from there.The registration wall converts 2x to 7x more email signups than a standard newsletter opt-in (3.2 to 6.7% versus 0.9%, across nine publishers on the same tool).Get your print archive onto the web as real HTML articles, not flipbooks. Modern Drummer doubled its site traffic in a year just by publishing one new issue and one archive issue online each month.Resources MentionedLeaky Paywall: publisher's AI survival guide, referenced for the registration wall and email growth numbersPublisher's AI Survival Guide: the free 65-page guide Pete mentions on the show, pops up on the Leaky Paywall homepageReissue: turns print PDF archives into web-ready WordPress postsReal 3D Flipbook: the WordPress plugin Pete and Tyler recommend for digital flipbook editions

In this episode of the Master.dev podcast, Dustin Tauer sits down with Katia Gil Guzman, a developer experience engineer at OpenAI, to talk about her path from learning C and HTML as a kid to building software at Microsoft, founding her own SaaS startup, and working at the intersection of AI, developer tools, and creativity.Katia shares how early curiosity shaped her career, what she learned from working with early users of Azure Cognitive Services and mixed reality, and why the best products often come from your own expertise and passions. She also talks about the value of building for specific users you understand deeply — whether that means a niche industry, a dev tool, or something entirely different.If you're interested in software engineering, startups, developer tools, AI, or have a creator mindset, this conversation is packed with practical insight and inspiration.#OpenAI #DeveloperExperience #SoftwareEngineering #Startups #AI #DeveloperTools #PodcastCheck out Katia's Master.dev Course: https://master.dev/courses/codex/?utm_source=youtube&utm_medium=home_link&utm_campaign=katia-podcastFind Master.dev Online:Twitter: https://twitter.com/MasterDotDevLinkedIn: https://www.linkedin.com/company/masterdotdev/Facebook: https://www.facebook.com/masterdotdevInstagram: https://instagram.com/FrontendMastersAbout Us: Master AI & Full Stack Development with in-depth, modern engineering courses. Our 300+ high-quality courses and 24 curated learning paths will guide you from mid-level to senior developer, frontend to backend, and everything between. Start your path to mastery today: https://master.dev/?utm_source=youtube&utm_medium=home_link&utm_campaign=katia-podcast

Show DescriptionThe realities of A/B testing, the future of specialized hosting in the AI era, microphone and camera permissions on the web, tricks for working with HTML email, and hyping Midnight Vinyl Club and How Many Dudes? Listen on WebsiteWatch on YouTubeLinks 8 New CSS, JS and HTML Features You Should Know - Syntax #1033 Mermaid | Diagramming and charting tool What Is AI Coding Doing To Us? - YouTube Midnight Vinyl Club MJML - The Responsive Email Framework AT Protocol How Many Dudes? | Download and Play!

Welcome solo and group practice owners! We are Liath Dalton and Evan Dumas, your co-hosts of Group Practice Tech. In our latest episode, we share a HIPAA-friendly way for therapy practice owners to get useful information about how their websites are performing, via Google Search Console. We discuss: What Google Search Console can tell you about your website The crucial differences between Google Analytics and Google Search Console Why Search Console is permissible for therapy practice websites Caveats and what to consider when configuring Search Console Listen here: https://personcenteredtech.com/group/podcast/ For more, visit our website. Resources for Listeners PCT Resources Podcast: Episode 625: Google Analytics for Therapy Practice Websites—The HIPAA Risks Explained — The companion episode explaining why Google Analytics is not appropriate for therapy-practice websites and how individually identifiable website activity can become protected health information. PCT CE course: Marketing in Mental Health: The Legal and Ethical Do's and Don'ts You Need to Know — This 3 legal-ethical CE credit hour on-demand training, presented by therapist and HIPAA attorney Eric Ström, JD, PhD, LMHC, unpacks the legal and ethical standards that apply to marketing in mental health practice, with particular attention to HIPAA marketing requirements, Business Associate Agreements (BAAs), authorizations/ROIs, advertising, referrals, reviews, and endorsements. PCT's Google Workspace Configuration Help Center — Includes step-by-step, video-based guidance for securing, configuring and leveraging Google Workspace appropriately for a therapy practice Group Practice Care Premium — Includes weekly live and recorded Group Practice Office Hours, including a monthly session with therapist and attorney Eric Ström, JD, PhD, LMHC; the Device Security Suite; the Remote Workspace Security Suite; and additional direct support and consultation resources. HIPAA Risk Analysis & Risk Mitigation Planning Service for Mental Health Practices — Care for your practice using our supportive, shame-free risk analysis and mitigation planning service. You'll have your Risk Analysis performed by a PCT consultant using a tool built specifically for mental health practices, along with a mitigation checklist to help you reduce identified risks. PCT's Comprehensive HIPAA Security Compliance Program bundles: For Group Practices For Solo Practitioners Comprehensive HIPAA Security Policies & Procedures Forms and logs for documenting the implementation and maintenance of Policies & Procedures Device & Workspace Security Suites Direct support and consultation from the PCT team and therapist-attorney Eric Ström, JD, PhD, LMHC HIPAA Risk Analysis & Risk Mitigation Planning service and tool HIPAA Security & Privacy Ethics training Resources Google Search Console — Google's free tool for understanding how a public website performs in Google Search, including the search terms that result in a website appearing, impressions, clicks, search position, indexing issues, and website-health information. Google Search Console Performance Report: Dimensions and Data Groupings — Google's explanation of the search-query, page, country, and device information available through Search Console. It also explains that some queries are omitted from reports to protect searcher privacy. Google Search Console: Verify Your Site Ownership — Google's instructions for verifying ownership through methods such as a DNS record or HTML file or tag. Google Analytics and Google Tag Manager are optional verification methods and do not need to be enabled to use Search Console. Google Search Console: Managing Owners, Users, and Permissions — Guidance for limiting Search Console access and periodically reviewing who has owner- or user-level access to a practice's website data. Google Search Console: Remove Information From Your Website From Google Search — Google's guidance for keeping sensitive, authenticated, or otherwise inappropriate pages out of search results and removing pages that have already been indexed.

HTML and Markdown are back in the spotlight, and AI is a big reason why. In this episode of Sync Up, hosts Stephen Rice and Arvind Mishra sit down with Dorine Rassaian (OneDrive Sr. Product Manager) and Nicole Woon (SharePoint Sr. Product Manager) to explore how AI-generated content is driving renewed interest in HTML and Markdown files across Microsoft 365. Learn how organizations are using HTML dashboards, newsletters, reports, presentations, and interactive experiences generated with AI, and how OneDrive and SharePoint are evolving to make these files easier to view, edit, collaborate on, and share. The conversation covers: ✅ Why HTML and Markdown are experiencing a resurgence ✅ How AI tools like Copilot generate HTML and Markdown content ✅ New OneDrive experiences for HTML and Markdown files ✅ WYSIWYG editing, inline text editing, and anchor comments ✅ Human-to-agent collaboration and the future of AI-powered work ✅ HTML-powered SharePoint pages and intranet experiences ✅ Real-world examples, dashboards, presentations, newsletters, and more   Whether you're a developer, IT professional, SharePoint administrator, or simply curious about how AI is changing the way we create and communicate, this episode offers a look at the future of content creation in Microsoft 365. Guests

Nico & Kevo kick off a whole new era of HTML coverage, returning to the superhero stories that they love by covering LANTERNS! But first, the two watch the movie that came way before the show – GREEN LANTERN (2011) starring Ryan Reynolds, Blake Lively, Angela Bassett, & more! The film itself is a mess of ideas and struggles to hit it's mark, but the HTML Guys find the good in it and get ready for their coverage of LANTERNS! Watch along with Green Lantern (2011) – don't miss it all on a new HTML / X Is For Show! X IS FOR SHOW is a talk show for your favorite media, the same way THE OFFICE was a documentary about a paper company. Every week, THE ACTION PACK gathers to discuss a wide range of entertainment media and news, from film & TV to comics to gaming, music, and beyond. Led by NICO (@NicoAction) and TK (@TKAccidental) with producer KEVO (@KevoReally), as well as a variety of friends and special guests, these LIVE discussions are not to be missed - so be sure to tune in and join us for all the fun!

Scott and Wes run through eight new CSS, JS, and HTML features landing in browsers; including the relative alpha() color function, the progress() function for calculating values between units, Promise.allKeyed(), and native camera and microphone elements. They also get into an upgraded attr(), shrink-to-fit containers, and text-box-trim for finally killing that annoying extra space above your text. Show Notes 00:00 Welcome to Syntax! Wes's Demo Site 00:22 CSS Alpha() Relative Color Function Google Groups 02:25 Brought to you by Sentry.io 02:48 CSS CSS Progress() Function: Calculate Values Between Units 05:09 Promise.allKeyed(): Object-Based Promise Resolution 06:55 Camera and Microphone HTML Elements 09:24 Advanced CSS Attr() Function: Props for CSS 11:25 CSS Sibling-Index() and Sibling-Count() Functions 13:56 CSS Shrink-to-Fit Container 15:36 CSS Text-Box-Trim and Text-Box-Edge Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

In 2020, a gastroenterologist in Glasgow did the math on his new research study and came up with 30,000 samples, arriving over two years from three cities and a dozen hospitals. He asked around about how researchers keep track of that. The answer was Microsoft Excel. Shaun Chuah had written some HTML by hand in Notepad back in high school and that was about the whole of his programming experience, so he opened the Django tutorial and started reading. Six years later that app is Foundry120, holding 10 terabytes of clinical and genomics data with an agentic AI running on top of it. Episode sponsors Sentry Error Monitoring, Code talkpython26 Talk Python Courses Talk Python Courses Links from the show Guest Shaun Chuah: github.com Up and Running with Rust Course: talkpython.fm Foundry120: www.foundry120.com Designing Data Intensive Applications: www.oreilly.com Microsoft Foundry: ai.azure.com ChatIBD: www.chatibd.com Blog: shaunchuah.github.io @drshaunchuah: x.com github.com/shaunchuah: github.com Watch this episode on YouTube: youtube.com Episode #560 deep-dive: talkpython.fm/560 Episode transcripts: talkpython.fm Theme Song: Developer Rap

*Please note that this episode is best viewed on YouTube as we did some screen sharing during our conversation*That being said... On this week's episode of JAMXP we're taking a trip straight back to the days of fun profile backgrounds, music playlists, bulletins, HTML, and the almighty Top 8, because MySpace is making a comeback! Jess and Chris are diving into all the nostalgia, memories, and chaos that made MySpace such an iconic part of our internet lives. So, dust off your HTML skills, pick your Top 8, and let's get into it!

Send us Fan MailAI is speeding up digital forensics, but speed without control is how good labs get burned. We dig into a safer way to work: use AI-assisted coding to generate a repeatable process, then test it against a real corpus of known extractions so results stay deterministic, verifiable, and defensible. If you've ever felt your LLM results “drift” from run to run, this mindset shift is the difference between a helpful assistant and a hidden liability. We also get practical with what's new across the community: a free macOS timestamp utility, Android intrusion logs (and how to extract and parse them when a user has opted in), and a deep look at Apple Unified Logs and log archives as an underrated iOS forensics goldmine. The big takeaway on logs is interpretation: one scary-looking line is not a conclusion. You have to read the surrounding sequence of events to avoid false narratives, and we talk about how newer workflows can process log archives directly from extractions without requiring a Mac. From there we move into evidence sources that often decide cases: iOS Health database artifacts, LevelDB and IndexedDB for browser forensics, and a standout BitLocker improvement that can auto-unlock secondary encrypted volumes when keys are preserved in a system image. Finally, we walk through reporting at scale with LAVA, the LEAPPs viewer that adds conversation views, analytics, tagging, notes, and LAVA subset exports for massive chats that would otherwise choke HTML reports. If this helped you rethink your workflow or gave you a new artifact to chase, subscribe, share the episode with your lab, and leave a review so more examiners can find it. What tool or artifact do you want us to test next?Notes:Timestamped - https://thebinaryhick.blog/2026/08/16/timestamped/Brett Shavers Blog Posts - http://linkedin.com/pulse/let-ai-run-your-case-make-you-stupid-brett-shavers-vproc/Android Logical Extractor - https://github.com/prosch88/ALEXTim Korver Blog Posts - https://www.linkedin.com/in/tim-korver/recent-activity/articles/SANS DFIR Summit & Training - https://www.sans.org/cyber-security-training-events/digital-forensics-summit-2026MSAB Digital Summit - https://www.msab.com/msab-mobile-forensics-digital-summit-2027/Cellebrite 101 - https://community.cellebrite.com/s/101HEART Metadata Forensics - https://github.com/MetadataForensics/HEART_by_Metadata_ForensicsArsenal - https://arsenalrecon.com/productsLEAPPs & LAVA - leapps.org

Vic Levitin is a serial founder who built companies in Israel for two decades before fleeing the war with his young family to the island of Koh Samui, Thailand. His first SaaS company, CrazyLister, grew out of his own e-commerce business where he needed a simple way for eBay sellers to build professional listings without knowing HTML. CrazyLister raised about $700K, then a similar second round, and grew to nearly $2M ARR before stalling. Today it runs profitably at roughly $1M ARR. Vic later spent four years co-founding Diptera.ai, a deep-tech venture using a larval-stage breakthrough to suppress malaria-carrying mosquitoes, now backed by the Gates Foundation. From Thailand, Vic now runs an AI-powered venture studio built on one rule: no code gets written until he proves he can generate demand. He partners with domain experts and influencers who already own trusting audiences, which is a model that took his AI-influencer platform to $90K MRR in 18 months, now extending to smaller niches like dog trainers. Key Takeaways Distribution First: Prove you can generate demand and revenue before a single line of code is written. Repeat vs. First: First-time founders obsess about product; repeat founders obsess about distribution. Partner for Reach: Bring on experts and influencers who already own a trusting audience. Micro-Niches Win: AI makes it viable to build dedicated apps for tiny verticals like dog trainers. Time to Money: Chase the fastest path to the first $100 in MRR to make everything real. Quote from Vic Levitin, Founder of CrazyLister "My technical co-founder Yair could build anything, even before AI came along. But we have an agreement, and it's a simple one. "He doesn't write a single line of code — whether from his own brain or with AI — before I prove to both of us that I can generate demand and revenue for whatever we're building. "That agreement formed the way we build now. We're a venture studio, and we solve distribution first by partnering with domain experts who already have trusting audiences." Links Vic Levitin on LinkedIn Crazy Lister on LinkedIn Crazy Lister website Diptera.ai (prior venture) Podcast Sponsor – Vista Point Advisors This podcast is sponsored by Vista Point Advisors, a leading investment bank for founder-led software, AI, and internet companies. Vista Point works exclusively on the sell side, providing unconflicted M&A and capital raising advice to help founders maximize business value, evaluate their options, and realize ideal outcomes.   The Practical Founders Podcast Tune into the Practical Founders Podcast for weekly in-depth interviews with founders who have built valuable software companies without big funding. Subscribe to the Practical Founders Podcast using your favorite podcast app or view on our YouTube channel. Get the weekly Practical Founders newsletter and podcast updates at practicalfounders.com. Practical Founders CEO Peer Groups Be part of a committed and confidential group of practical founders creating valuable software companies without big VC funding.  A Practical Founders Peer Group is a committed and confidential group of founders/CEOs who want to help you succeed on your terms. Each Practical Founders Peer Group is personally curated and moderated by Greg Head.

This episode gave me the opportunity to review the summer's episodes and I noticed some of them naturally grouped into 3 different categories - what LLMs want, the computational constraints of models and why we should want to lessen our computational cost for them, and the proof that 1:1 parity of HTML to Rendered DOM is the gateway to reliable citation.Mentioned in the show:VizzEx plugin is in the Wordpress Plugin Directory⁠https://wordpress.org/plugins/vizzex/⁠AI doesn't work like Google. Even Google doesn't anymore.⁠https://vizzex.ai/ai-visibility-mastery/⁠Symmetry vs Asymmetry Single Variable Testhttps://www.youtube.com/watch?v=TkPi-J54bowTest #2 - Is passing Symmetry alone without schema sufficient? https://www.youtube.com/watch?v=YUkwfboMpiQLast week's episode:⁠ ⁠https://www.pandora.com/podcast/confessions-of-an-seo-r/symptom-chasing-vs-single-variable-testing-deconstructing-the-semrush-chatgpt-study/PE:1325321344Registration is open for the next cohort of the AI Visibility Mastery 12-month course. We are committed to the success of our members.⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://vizzex.ai/ai-visibility-mastery/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Wordpress registration⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ HubSpot registration⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Symmetry Gate⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ - check the "cost" of your content for AI models to extract informationSubscribe to Confessions of an SEO™ wherever you get your podcasts. Your subscribing and download sends the message that you appreciate what is being shared and helping others find Confessions of an SEO™An easy place to leave a review ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.podchaser.com/podcasts/confessions-of-an-seo-1973881⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠You can find me on⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Carolyn Holzman⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ - Linkedin⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠American Way Media⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Google Directly⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠AmericanWayMedia.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Consulting AgencyNeed Help With an Issue? - reach out Text me here - 512-222-3132Music from Uppbeathttps://uppbeat.io/t/doug-organ/fugue-stateLicense code: HESHAZ4ZOAUMWTUA

Topics covered in this episode: Claude Code /insights Post-quantum crypto lands in Python MCP goes stateless — and FastMCP gets renamed inshellisense - IDE style command line auto complete Extras Joke Watch on YouTube About the show Sponsored by Xweather Xweather combines enterprise-grade weather intelligence with agent-ready APIs, natural language capabilities, and an MCP server so your agents can adapt workflows, automate responses, and make better decisions based on real-world conditions. Michael will tell you more about them later in the show. Get started for free at pythonbytes.fm/xweather Connect with the hosts Michael: Mastodon / BlueSky / X / LinkedIn Calvin: Mastodon / BlueSky / X / LinkedIn Show: Mastodon / BlueSky / X Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Tuesday at 7am PT. Older video versions available there too. Finally, if you want an artisanal digest of every week of the show notes in email form? Add your name and email to our friends of the show list, we'll never share it. Michael #1: Claude Code /insights Michael's Insights: michael-kennedy-claude-code-insights-2026-08-09.html Be careful sharing these outputs, they include details references to your projects, errors, security findings, etc. ;) /insights reads your last 30 days of local session transcripts and hands back an interactive HTML report on how you actually work. One command, zero setup: type /insights in a session, or run claude -p "/insights" from the shell for a non-interactive version that just prints the path Reads what's already on disk: pulls session logs from ~/.claude/projects/, skipping agent sub-sessions and anything under 2 messages or 1 minute Project areas: clusters your sessions into themes like "CLI Tooling" or "Documentation" with session counts Friction analysis: categorizes where things went wrong by root cause - and quotes your own prompts back at you Interaction style: tells you whether you're a delegator or a micromanager, plus which workflows are worth doubling down on Actually actionable: suggests concrete CLAUDE.md additions and Claude Code features you're not using The catch: Haiku does the per-session classification, so the first run takes several minutes; results cache to ~/.claude/usage-data/facets/ and the report lands at ~/.claude/usage-data/report.html Calvin #2: Post-quantum crypto lands in Python pyca/cryptography 48 ships ML-KEM (key establishment) and ML-DSA (signatures) — NIST's post-quantum standards, now one pip install away. Big deal because it's the 11th most-downloaded package on PyPI (~1.2B downloads/month) and sits under Ansible, Certbot, Airflow, and paramiko. No PQ there, no PQ anywhere in Python. Trail of Bits did the work (Rust bindings, cross-backend API, tests, AWS-LC backend support), funded by the Sovereign Tech Agency. Timing tracks a June 22 White House order setting federal deadlines: PQ key establishment by end of 2030, PQ signatures by end of 2031. Not a drop-in swap — the wire sizes explode. ML-DSA-65 signatures are 3,309 bytes vs Ed25519's 64; ML-KEM-768 public keys are 1,184 bytes vs X25519's 32. Hardcoded field sizes and length prefixes will bite. API looks like the existing asymmetric primitives, except ML-KEM is encapsulate/decapsulate rather than a Diffie-Hellman exchange. SLH-DSA (the hash-based conservative backstop) is still in progress. The primitives are here, but protocols haven't caught up — so you won't be running post-quantum Certbot this week. Sponsor: Xweather You're using agents that can write code, summarize documents, and automate workflows. But they're missing one thing: awareness of the world around them. This is where today's sponsor, Xweather comes in. Xweather combines enterprise-grade weather intelligence with agent-ready APIs, natural language capabilities, and an MCP server built for tools like Claude, Codex, Copilot, and modern IDEs – so your agents can adapt workflows, automate responses, and make better decisions based on real-world conditions. Backed by Vaisala, whose instruments fly on NASA missions to Mars, Xweather delivers trusted data and unique insights that go beyond conditions to actual impact – from real-time lightning strikes to road surface forecasts. Start with 15,000 free API calls each month and pay only for what you use as you grow. Xweather is your full weather stack, for developers by developers. Start building for free today at pythonbytes.fm/xweather. The link is in your podcast player's show notes and on the episode page. Thanks so much to Xweather for supporting Python Bytes. Calvin #3: MCP goes stateless — and FastMCP gets renamed From Philipp Acsany over at Real Python The 2026-07-28 spec landed July 28 and the Python SDK shipped 2.0.0 the same day. Biggest rewrite since MCP launched, and it's breaking on purpose. Context for scale: the Tier 1 SDKs are pulling close to half a billion downloads a month, with TypeScript and Python each past a billion total. The headline is the stateless core. The initialize/initialized handshake and the Mcp-Session-Id header are both retired — protocol version, client identity, and capabilities now ride in _meta on every request, with an optional server/discover RPC if a client wants capabilities up front. Any request can land on any instance behind plain round-robin, no shared storage. Server-initiated calls are the hard part of the migration. Sampling, elicitation, and roots/list no longer call back to the client; instead the server returns resultType: "input_required" and the client retries with inputResponses attached. Multi Round-Trip Requests, MRTR. Also: Mcp-Method and Mcp-Name are now required headers so gateways route on headers instead of cracking JSON bodies, and missing-resource errors move to standard 32602. Deprecation sweep with an actual policy behind it — Roots, Sampling, Logging, and the legacy HTTP+SSE transport all deprecated with a twelve-month minimum offramp. Tasks graduated out of the experimental core into a real extension, which is what the formalized extensions framework was for. MCP Apps is now an official extension too, so a tool call can return sandboxed interactive HTML. Auth picked up RFC 9207 issuer validation, issuer-bound credentials, and a shift from DCR toward CIMD. Python SDK 2.0 is where it gets personal: FastMCP is now MCPServer, no alias, no shim. McpError → MCPError. Wire types went snake_case (is_error, input_schema) and moved to a standalone mcp_types package, with mcp.types kept as a permanent alias. One Client object replaces the old transport + ClientSession + initialize() stack. httpx became httpx2. Sync handlers run on worker threads now, so asyncio.get_running_loop() raises inside them. The good news: one MCPServer serves both protocol eras, so 2025-era clients keep working with nothing to configure, and a Resolve(fn) parameter lets one tool body cover MRTR and the old path. 1.x is maintenance-and-security-fixes only — pin mcp>=1.28,

#363: Three waves of the web, and you are late for the third one. The 90s were about getting a browser to render your page at all. The early 2000s were about SEO, or as Darin puts it, sell me all the ads ready. Now it is agent ready, and Cloudflare built a scoreboard for it at [isitagentready.com](https://isitagentready.com/). The devopsparadox.com site scored about 70 out of 100 and then went down when Cloudflare added new checks. Run yours. You will be sad. Viktor thinks the framing is slightly off, though, and the correction is the good part. Optimizing for agents that browse your site is aiming at the wrong thing, because most requests never touch your server. Agent asks the model, model answers, agent shows you. So the target is not the crawler, it is the training data - and if the model does go looking, the question becomes whether you are the first answer or one of the five sites it was told to go analyze. Same game as Google. Different index. It is not Google index anymore, it is model training now. Then the practical part. Five things Cloudflare scores you on: discoverability, content, bot access control, API, Auth, MCP & Skill Discovery, and Commerce. Content accessibility is where most of you are losing, because agents want Markdown and you are serving them a pile of HTML tags to strip. Both DOP and Viktor's site are Hugo, so the Markdown is already sitting on disk next to the HTML - serve one or the other based on what the request asks for. Almost no effort. If you are still shipping a JavaScript-rendered site, Darin says it is game over, and humans do not like those either. On the blocking side, both of them are baffled by the same thing: if you do not want agents reading it, do not publish it. robots.txt is a suggestion at best. If you really want to block, actually block. The API argument is the one that will annoy people. Viktor says CLIs and MCP servers are both auto-generated from a schema, so the real work is having a good API, and most companies do not. But who your audience is decides the wrapper - developers already have Bash, so give them a CLI and get out of the way. Everyone else needs MCP, because Viktor's mom is not installing your binary. And somewhere in the middle of all this Darin asks whether documentation should live in the code now more than ever, and Viktor says no, less than ever - he wants it separate so he can review it, because agents made everything cheap to produce and review is now the only thing standing between him and 5,000 features a day. Also: WordPress should be the last thing you consider, not the first.   YouTube channel: https://youtube.com/devopsparadox   Review the podcast on Apple Podcasts: https://www.devopsparadox.com/review-podcast/   Slack: https://www.devopsparadox.com/slack/   Connect with us at: https://www.devopsparadox.com/contact/

Show DescriptionWe tackle a listener question about why junior front-end devs are expected to know so much beyond HTML and CSS, then get into Dave's real-world fix swapping old WebKit line-clamp hacks for the new CSS line-clamp property and the subtle bugs that kind of truncation work can cause. They also debate whether AI tools like Claude or Copilot deserve co-author credit on commits, gripe about agent-only coding workflows that skip linting and hide what's actually happening, and wrap up looking at new platform features like the navigation API and a proposed CSS-based routing approach using @route and @view-transition. Listen on WebsiteWatch on YouTubeSponsorsNotionWrite custom tools for Notion Agents that generate assets, query live data, and hit any API. Listen for incoming webhooks from any app, then run workflows with Notion Agents, pages, databases, and external APIs. All of this, on a hosted runtime. Workers are isolated sandboxes managed by Notion, so the code behind your syncs, tools, and workflows runs on our infra instead of your servers.

Some people start their morning with coffee. We start ours by arguing about what the word "standby" actually means before immediately spiraling into ancient social media trauma. Seems healthy.This daily comedy show welcomes comedian Bobby Jaycox back into the studio, and from there the rails completely disappear. One minute we're talking about his stand-up shows, the next we're debating whether MySpace deserves another shot at world domination. Would you bring back your Top 8? Would Tom still be your first friend? More importantly... what embarrassing song was automatically blasting from your profile the second someone visited?Naturally, that conversation leads us into the greatest collection of forgotten internet memories imaginable. MySpace profile songs, HTML backgrounds, awkward teenage decisions, and the horrifying realization that some of those old photos may still exist somewhere in the digital universe waiting to ruin careers.As if nostalgia wasn't enough, Lauren somehow gets roped into doing a Chewbacca impression... and then convinces everyone else to try one too. The results are exactly as dignified as you'd expect from grown adults with microphones.Elsewhere in today's chaos...• Bobby shares stories about Nikki Glaser helping promote his comedy shows.• The crew debates whether listening to music should be a solo experience.• Rafe revisits one of the most questionable MySpace profile songs ever selected by a human being.• Moon explains why MySpace worked in the first place—and why bringing it back might be impossible.• Clone conspiracies somehow become a serious topic for several minutes.• Lauren runs through the latest celebrity news, music headlines, TV updates and entertainment gossip during Crap on Celebrities.• Ted Lasso returns.• American Horror Story gets its Avengers-style crossover season.• Eminem auctions off sneakers.• Demi Lovato shuts down clone theories... which naturally only fuels more clone theories around the room.• The gang ranks classic summer songs while simultaneously roasting Kenny Chesney, LFO, Brian Wilson, and basically everyone else.It's another episode where one conversation accidentally creates six more conversations, nobody stays on topic for long, and somehow that's exactly how we like it.Whether you're here for comedy, weird news, pop culture commentary, celebrity gossip, or simply listening to adults argue over extinct social media platforms, you've found your people.Thanks for making The Rizzuto Show part of your day and hanging out with us for another ridiculous ride. This daily comedy show exists because of listeners like you who continue to embrace the nonsense right alongside us.Follow The Rizzuto Show → https://linktr.ee/rizzshow for more from your favorite daily comedy show.Connect with The Rizzuto Show Comedy Podcast online → https://1057thepoint.com/RizzShow.Hear The Rizz Show daily on the radio at 105.7 The Point | Hubbard Radio in St. Louis, MO.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

From camel rides to West Nile mosquitoes, somehow end up roasting Panera's move to Boston, and still find time to debate whether minivans are secretly awesome... congratulations, you've found today's episode.The crew kicks things off with one of the weirdest conversations you'll hear all week after camel videos completely derail the morning. From there it's straight into Missouri mosquito season, West Nile warnings, heat indexes trying to melt highways, and why everyone suddenly feels like checking every birdbath in the neighborhood.Then comes the biggest local story of the day: Panera officially announcing plans to move its headquarters from the St. Louis area to Boston. The gang reacts the only way they know how—with sarcastic conspiracy theories, fake boardroom jargon, Boston jokes, memories of St. Louis Bread Co., questionable bathroom reviews, and plenty of mourning for another hometown company heading east. Somehow the conversation also includes Matt Damon, Ben Affleck, bread bowls, hospital food, and the mysterious career path of CEO Paul Carbone.The chaos doesn't stop there.There's a wild retail theft story where social media becomes the criminals' biggest enemy, stories about detention, paddlings, school punishments that absolutely wouldn't fly today, and enough embarrassing childhood memories to keep therapists employed for years.Later, the crew unexpectedly becomes the biggest supporters of minivans you've ever heard. Sliding doors, cup holders, family road trips, captain's chairs, Toyota Siennas... suddenly everyone's wondering if they judged minivans way too harshly growing up.Of course, no episode would be complete without random tangents about neighborhood cats, weird internet nostalgia, ridiculous listener texts, and the kind of conversations that somehow only happen on The Rizzuto Show.Some people start their morning with coffee. We start ours by arguing about what the word "standby" actually means before immediately spiraling into ancient social media trauma. Seems healthy.This daily comedy show welcomes comedian Bobby Jaycox back into the studio, and from there the rails completely disappear. One minute we're talking about his stand-up shows, the next we're debating whether MySpace deserves another shot at world domination. Would you bring back your Top 8? Would Tom still be your first friend? More importantly... what embarrassing song was automatically blasting from your profile the second someone visited?Naturally, that conversation leads us into the greatest collection of forgotten internet memories imaginable. MySpace profile songs, HTML backgrounds, awkward teenage decisions, and the horrifying realization that some of those old photos may still exist somewhere in the digital universe waiting to ruin careers.As if nostalgia wasn't enough, Lauren somehow gets roped into doing a Chewbacca impression... and then convinces everyone else to try one too. The results are exactly as dignified as you'd expect from grown adults with microphones.Elsewhere in today's chaos...• Bobby shares stories about Nikki Glaser helping promote his comedy shows.• The crew debates whether listening to music should be a solo experience.• Rafe revisits one of the most questionable MySpace profile songs ever selected by a human being.• Moon explains why MySpace worked in the first place—and why bringing it back might be impossible.• Clone conspiracies somehow become a serious topic for several minutes.• Lauren runs through the latest celebrity news, music headlines, TV updates and entertainment gossip during Crap on Celebrities.• Ted Lasso returns.• American Horror Story gets its Avengers-style crossover season.• Eminem auctions off sneakers.• Demi Lovato shuts down clone theories... which naturally only fuels more clone theories around the room.• The gang ranks classic summer songs while simultaneously roasting Kenny Chesney, LFO, Brian Wilson, and basically everyone else.It's another episode where one conversation accidentally creates six more conversations, nobody stays on topic for long, and somehow that's exactly how we like it.Then Mike McKenna from Macadoodles walks into the studio carrying what might be the greatest gift Rafe has ever received: a full-size cardboard cutout of Willie Nelson. Naturally, that leads to conversations about THC drinks, sleep gummies, hemp regulations, getting way too high in Vegas, and why older adults are becoming the biggest fans of Willie Nelson's cannabis beverages.The crew also answers listener emails that somehow become full-blown debates. Is it weird to say hi to the spouses of radio personalities when you see them in public? Does gray hair actually make people more attractive? Should you ever dye it? Why do brothers care if their sister goes gray? The opinions are... surprisingly passionate.Then comes one of the biggest debates of the episode.A listener witnesses someone bringing a dog into a pizza restaurant... then placing the dog ON THE TABLE. The crew is completely split over what's acceptable, what's disgusting, where the line should be, and somehow babies, dirty diapers, dog hair, patios, and pizza all become part of the same conversation.Meanwhile Bobby prepares for his upcoming appearance at the Gathering of the Juggalos, everyone wonders what kind of chaos that comedy show will become, and Rafe volunteers to road trip despite claiming he's only doing it to pay off student loans.It's another completely unfiltered episode filled with ridiculous conversations, listener emails, celebrity randomness, weird news, and exactly the kind of nonsense you've come to expect from The Rizzuto Show.Follow The Rizzuto Show → https://linktr.ee/rizzshow for more from your favorite daily comedy show.Connect with The Rizzuto Show Comedy Podcast online → https://1057thepoint.com/RizzShow.Hear The Rizz Show daily on the radio at 105.7 The Point | Hubbard Radio in St. Louis, MO.Mosquitoes in Desoto Test Positive for West Nile VirusExtreme heat buckles road on Highway K in O'FallonPanera to move headquarters from St. Louis to BostonMillennials are trying to make minivans cool again‘Millennials assemble': Myspace could be making a comebackSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Some mornings you wake up expecting another normal daily comedy show.Then the building catches everyone's attention with a fire alarm, Rizz refuses to evacuate because apparently radio hosts go down with the ship, and somehow the conversation spirals into MySpace, CDs making a comeback, William Shatner becoming a metal frontman at 95, and why nobody under 25 knows who Hole is anymore.Just another Tuesday.This episode starts with excitement surrounding the upcoming Super Troopers 3 as the Broken Lizard crew prepares to visit the studio, giving everyone an excuse to geek out over one of the greatest comedy franchises ever made. Before they arrive, the crew jumps into Crap on Celebrities, where nostalgia absolutely takes over.Could MySpace actually deserve more respect than it gets? Turns out the platform helped launch artists like Taylor Swift, Katy Perry, Adele, and even Dane Cook before social media became the attention economy we know today. That naturally leads into everyone's embarrassing MySpace memories, Top 8 drama, party bulletins, and the strange realization that we all willingly learned HTML just to put terrible music on our profiles.Speaking of things nobody expected to return...CDs are suddenly making a comeback. Yes... actual compact discs. The crew debates whether anyone even owns a CD player anymore, whether physical media still matters, and whether younger generations are rediscovering something older fans never completely gave up on. It's part nostalgia, part technology debate, and part excuse for Moon to become the resident audio nerd.Then things somehow become even stranger.William Shatner is officially performing heavy metal songs at Riot Fest... at ninety-five years old.The conversation somehow makes perfect sense.Elsewhere in celebrity news:• The Batman Part II gets delayed again.• A new Rocky movie about Sylvester Stallone fighting to play himself looks surprisingly incredible.• Paris Jackson earns praise for covering Blind Melon's "No Rain."• Alec Baldwin accidentally makes another tribute about... Alec Baldwin.• The Grateful Dead release a massive 20-CD collection because apparently CDs aren't dead after all.• Hole returns to social media, prompting an entire debate over whether younger music fans even know who Courtney Love's band was.Along the way, the crew shares ridiculous observations, roasts each other relentlessly, argues over music, remembers forgotten internet history, and proves once again why no topic stays on the rails for very long.That's exactly why this daily comedy show continues to be the easiest way to stay caught up on celebrity news, weird stories, pop culture, and conversations that somehow go from MySpace coding to William Shatner screaming heavy metal in less than ten minutes.If you enjoy sarcastic humor, entertainment news, nostalgic pop culture rabbit holes, and a group of friends who rarely let facts get in the way of a good joke, this episode has everything you need from your favorite daily comedy show.Follow The Rizzuto Show → https://linktr.ee/rizzshow for more from your favorite daily comedy show.Connect with The Rizzuto Show Comedy Podcast online → https://1057thepoint.com/RizzShowHear The Rizz Show daily on the radio at 105.7 The Point | Hubbard Radio in St. Louis, MO.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.