Podcasts about MVC

En este nonagésimo quinto episodio del ¡Bipartidismo Strikes Back! (una producción del #PodcastLaTrinchera), Christian Sobrino y Luis Balbino discuten los ataques recientes del PIP y el MVC contra el PNP y el PPD, el contra ataque de Luisito Herrero contra Manuel Natal, la visita de la Delegación PNP a la oficina del Comisionado Residente, lo más reciente en las primarias demócratas en la Ciudad de Nueva York, la presencia militar en Roosevelt Roads, municipios cobrando arbitrios a contratistas de la reconstrucción federal y mucho más.Este episodio es presentado a ustedes por:- San Juan Lincoln, donde encontrarán una exclusiva colección de vehículos de lujo diseñados para satisfacer todas sus expectativas. Allí descubrirán la presencia imponente de la Navigator, la elegancia dinámica de la Aviator, la sofisticación refinada de la Corsair y el diseño moderno de la Nautilus. Pueden visitarlos en la Avenida Kennedy en San Juan para explorar lo que una SUV de lujo debe ser. Su equipo está listo para ofrecerles una experiencia inigualable. Para más información u orientación, llamen al 787-331-5023.- La Tigre,  el primer destino en Puerto Rico para encontrar una progresiva selección de moda Italiana, orientada a una nueva generación de profesionales que reconocen que una imagen bien curada puede aportar a nuestro progreso profesional. Detrás de La Tigre, se encuentra un selecto grupo de expertos en moda y estilo personal, que te ayudarán a elaborar una imagen con opciones de ropa a la medida y al detal de origen Italiano para él, y colecciones europeas para ella. Visiten la boutique de La Tigre ubicada en Ciudadela en Santurce o síganlos en Instagram en @shoplatigre.Por favor suscribirse a La Trinchera con Christian Sobrino en su plataforma favorita de podcasts y compartan este episodio con sus amistades.Para contactar a Christian Sobrino y #PodcastLaTrinchera, nada mejor que mediante las siguientes plataformas:Facebook: @PodcastLaTrincheraTwitter: @zobrinovichInstagram: zobrinovichTikTok: @podcastlatrincheraYouTube: @PodcastLaTrinchera

In this special episode, Dylan is joined by Teresa Serrenho, Gerald Rots, and Filip D'havé to explore something many people feel when they move here: Portugal's incredible sense of community.After one of the worst storms in Portugal's history caused major damage across the Leiria region, locals and internationals came together to help those in urgent need. Teresa shares how Associação MVC quickly stepped in to support affected families. Gerald and Filip explain why the local expat community has also joined this cause.From life on the Silver Coast to Portuguese culture, resilience, community spirit, and the upcoming charity fundraising concert in Caldas da Rainha on May 23, this episode shows the real heart of Portugal.SUPPORT THIS EVENT:GET TICKETS OR DONATEEVENT ON FACEBOOKGET IN CONTACTABOUT PORTUGAL THE SIMPLE LIFE PODCAST:"Portugal - The simple life”, an insider's perspective to Portugal.We already know about Portugal's fantastic weather, food and people. In this podcast, we go deeper to meet the people who make this country so wonderful.Dylan, who has made his life in Portugal, shares an insider's perspective on what makes Portugal the unique, beautiful and fantastic country it is. Join him and his guests weekly as they shed light on the lifestyle that makes Portugal so appealing.   Don't forget to subscribe to our Podcast to receive more stories about living and moving to Portugal!   SPONSOR:Portugal Realty, a Leisure Launch group company, sponsors this episode. 

On this episode of the Dubuque Area Sports Podcast, Coach Maneman sits down with Dubuque Senior Head Coach Tyler Saeugling to preview the 2026 Rams baseball season.Coach Saeugling looks back on an 18-19 season that saw the Rams finish 7th on the Mississippi side of the MVC at 11-17. The conversation dives into the key moments from last year, the returning award winners and starters, players ready to step into bigger roles, and the pitchers who could help lead Senior this season.They also discuss younger players to keep an eye on, the biggest strengths of this year's team, areas that still need improvement, and what Dubuque Senior fans can expect from the Rams in 2026. If you want a closer look at a team battling in one of the toughest baseball conferences around, this is an episode you will not want to miss.

This week, Rivka and Frank are joined by the third leg of the MVC team: editor John. Together, they discuss Father Hood, the 1993 Patrick Swayze comedy-action thrille (not to be confused with Kevin Hart's Fatherhood). Buried beneath the film's utterly unhinged plot, the trio uncover the politics of its era, including the decade's fascination with the “deadbeat dad turns out to have a heart of gold” trope.   

Coach Maneman is joined by Wahlert Catholic head softball coach Tyler Lang to preview the Golden Eagles' 2026 season on the Dubuque Area Sports Podcast. After a tremendous 37-8 season, an MVC championship with a 24-4 conference record, and a run all the way to the state championship game, Wahlert Catholic heads into the new season with high expectations once again. Coach Lang reflects on the biggest moments from last year, discusses returning award winners and starters, highlights players ready for bigger roles, breaks down the pitching staff, and shares what it will take for the Golden Eagles to make another deep run. It's a fun and informative look at Wahlert Catholic softball and what fans can expect in 2026.

On this episode of the Dubuque Area Sports Podcast, Coach Maneman is joined by Wahlert Catholic Head Coach Kory Tuescher to preview the 2026 Golden Eagles baseball season.Wahlert is coming off a tremendous 38-7 overall record, a 23-5 mark in the MVC, a conference championship, and a run all the way to the state championship game. Coach Tuescher looks back on the key moments that defined last season, talks about the returning award winners and starters, and shares which players are ready to step into larger roles after the loss of an outstanding senior class.The conversation also breaks down the Golden Eagles' pitching staff, highlights younger players to keep an eye on, and discusses the biggest strengths and areas for improvement for this year's team. If you want a closer look at one of the premier baseball programs in the area and what it will take for Wahlert to make another deep postseason run, this is an episode you will not want to miss.

PODCAST LAS NOTICIAS CON CALLE DE 8 DE ABRIL DE 2026 - Petróleo colapsa de 114 a 91, pero vuelve a subir a 94 - Oilprice.com Siguen los casos de sífilis en el embarazo, casi siempre demostración de un país de extrema pobreza - Primera Hora China presionó a Irán para aceptar acuerdo de tregua - AP Presidente de Ecuador quiere que ejército de USA entre y les ayude a pelear contra narcos tras brutales asesinatos de gangas - Bloomberg Demócratas tienen moméntum en elecciones, pero Trump y republicanos tienen más de 7 veces más dinero que los demócratas - Axios Kany García lanza canción con Juan Luis Guerra Proponen que te llegue alerta a los celulares cuando vayas a zona de alto oleaje - Primera HoraÍndice de calor hoy se trepa a 100 grados - WAPA.TV Departamento de Justicia apoya cambios propuestos por Rivera Schatz al sistema judicial - El Nuevo Día Según el FEI ellos hacen un gran trabajo y tienen tremendo récord metiendo presos a corruptos - El Nuevo Día Dicen que NO a mostrar el rostro de Anthonieska en juicio en su contra - El Nuevo Día Se pierde el café de PR, buscan traer 2 mil, arrancan con 823 recolectores de café extranjeros  - El Nuevo Día UPR a Paro por 2 horas Fiscalía federal presentará oferta a miembro MVC acusado de pornografía infantil - El Vocero Costo de la luz y agua, inflación y costo de vida le pasan a la criminalidad como preocupación principal de la humanidad - El Vocero Va a tardar meses el mercado del jetfuel en normalizarse - OilPriceHungría la elección más vista en el mundo - FTSenadores ausentes en medio de vista para escoger sistema judicial de PR - Noticel Muere arrollado y desmembrado peatón en la PR 30 de Juncos Trump amenaza con aranceles a cualquier país que le venda armas a Irán. Asegura 50% sin excepciones - Truth Social Israel acepta tregua con Irán, pero no con Líbano y sigue esa guerra - Bloomberg MAGA Media abandona a Trump por guerra de Irán - Axios Pronostícan bajada de precio de gasolina bien rápida, el diesel es el principal problema - AAA Si estás pagando por tu celular, lo mínimo es que te dé valor de verdad. Por eso, T-Mobile es la mejor red móvil en Puerto Rico. Y no es solo velocidad, es todo lo que viene con ella. Tienes streaming incluido de Netflix, Hulu, Apple TV+, hotspot ilimitado, y conexión con internet y textos ilimitados en más de 215 destinos sin costo adicional. Además, con el Magenta Pass en el app T-Life, accedes a beneficios reales como experiencias exclusivas, filas más rápidas y muchoo más. Si te vas a conectar, conéctate bien con T-Mobile.#TMobile#incluyeauspicio 

We're proud to release this ahead of Ryan's keynote at AIE Europe. Hit the bell, get notified when it is live! Attendees: come prepped for Ryan's AMA with Vibhu after.Move over, context engineering. Now it's time for Harness engineering and the age of the token billionaires.Ryan Lopopolo of OpenAI is leading that charge, recently publishing a lengthy essay on Harness Eng that has become the talk of the town:In it, Ryan peeled back the curtains on how the recently announced OpenAI Frontier team have become OpenAI's top Codex users, running a >1m LOC codebase with 0 human written code and, crucially for the Dark Factory fans, no human REVIEWED code before merge. Ryan is admirably evangelical about this, calling it borderline “negligent” if you aren't using >1B tokens a day (roughly $2-3k/day in token spend based on market rates and caching assumptions):Over the past five months, they ran an extreme experiment: building and shipping an internal beta product with zero manually written code. Through the experiment, they adopted a different model of engineering work: when the agent failed, instead of prompting it better or to “try harder,” the team would look at “what capability, context, or structure is missing?”The result was Symphony, “a ghost library” and reference Elixir implementation (by Alex Kotliarskyi) that sets up a massive system of Codex agents all extensively prompted with the specificity of a proper PRD spec, but without full implementation:The future starts taking shape as one where coding agents stop being copilots and start becoming real teammates anyone can use and Codex is doubling down on that mission with their Superbowl messaging of “you can just build things”.Across Codex, internal observability stacks, and the multi-agent orchestration system his team calls Symphony, Ryan has been pushing what happens when you optimize an entire codebase, workflow, and organization around agent legibility instead of human habit.We sat down with Ryan to dig into how OpenAI's internal teams actually use Codex, why the real bottleneck in AI-native software development is now human attention rather than tokens, how fast build loops, observability, specs, and skills let agents operate autonomously, why software increasingly needs to be written for the model as much as for the engineer, and how Frontier points toward a future where agents can safely do economically valuable work across the enterprise.We discuss:* Ryan's background from Snowflake, Brex, Stripe, and Citadel to OpenAI Frontier Product Exploration, where he works on new product development for deploying agents safely at enterprise scale* The origin of “harness engineering” and the constraint that kicked off the whole experiment: Ryan deliberately refused to write code himself so the agent had to do the job end to end* Building an internal product over five months with zero lines of human-written code, more than a million lines in the repo, and thousands of PRs across multiple Codex model generations* Why early Codex was painfully slow at first, and how the team learned to decompose tasks, build better primitives, and gradually turn the agent into a much faster engineer than any individual human* The obsession with fast build times: why one minute became the upper bound for the inner loop, and how the team repeatedly retooled the build system to keep agents productive* Why humans became the bottleneck, and how Ryan's team shifted from reviewing code directly to building systems, observability, and context that let agents review, fix, and merge work autonomously* Skills, docs, tests, markdown trackers, and quality scores as ways of encoding engineering taste and non-functional requirements directly into context the agent can use* The shift from predefined scaffolds to reasoning-model-led workflows, where the harness becomes the box and the model chooses how to proceed* Symphony, OpenAI's internal Elixir-based orchestration layer for spinning up, supervising, reworking, and coordinating large numbers of coding agents across tickets and repos* Why code is increasingly disposable, why worktrees and merge conflicts matter less when agents can resolve them, and what it really means to fully delegate the PR lifecycle* “Ghost libraries”, spec-driven software, and the idea that a coding agent can reproduce complex systems from a high-fidelity specification rather than shared source code* The broader future of Frontier: safely deploying observable, governable agents into enterprises, and building the collaboration, security, and control layers needed for real-world agentic workRyan Lopopolo* X: https://x.com/_lopopolo* Linkedin: https://www.linkedin.com/in/ryanlopopolo/* Website: https://hyperbo.la/contact/Timestamps00:00:00 Introduction: Harness Engineering and OpenAI Frontier00:02:20 Ryan's background and the “no human-written code” experiment00:08:48 Humans as the bottleneck: systems thinking, observability, and agent workflows00:12:24 Skills, scaffolds, and encoding engineering taste into context00:17:17 What humans still do, what agents already own, and why software must be agent-legible00:24:27 Delegating the PR lifecycle: worktrees, merge conflicts, and non-functional requirements00:31:57 Spec-driven software, “ghost libraries,” and the path to Symphony00:35:20 Symphony: orchestrating large numbers of coding agents00:43:42 Skill distillation, self-improving workflows, and team-wide learning00:50:04 CLI design, policy layers, and building token-efficient tools for agents00:59:43 What current models still struggle with: zero-to-one products and gnarly refactors01:02:05 Frontier's vision for enterprise AI deployment01:08:15 Culture, humor, and teaching agents how the company works01:12:29 Harness vs. training, Codex model progress, and “you can just do things”01:15:09 Bellevue, hiring, and OpenAI's expansion beyond San FranciscoTranscriptRyan Lopopolo: I do think that there is an interesting space to explore here with Codex, the harness, as part of building AI products, right? There's a ton of momentum around getting the models to be good at coding. We've seen big leaps in like the task complexity with each incremental model release where if you can figure out how to collapse a product that you're trying to.Build a user journey that you're trying to solve into code. It's pretty natural to use the Codex Harness to solve that problem for you. It's done all the wiring and lets you just communicate in prompts. To let the model cook, you have to step back, right? Like you need to take a systems thinking mindset to things and constantly be asking, where is the Asian making mistakes?Where am I spending my time? How can I not spend that time going forward? And then build confidence in the automation that I'm putting in place. So I have solved this part of the SDLC.swyx: [00:01:00] All right.[00:01:03] Meet Ryan swyx: We're in the studio with Ryan from OpenAI. Welcome.Ryan Lopopolo: Hi,swyx: Thanks for visiting San Francisco and thanks for spending some time with us.Ryan Lopopolo: Yeah, thank you. I'm super excited to be here.swyx: You wrote a blockbuster article on harness engineering. It's probably going to be the defining piece of this emerging discipline, huh?Ryan Lopopolo: Thank you. It is it's been fun to feel like we've defined the discourse in some sense.swyx: Let's contextualize a little bit, this first podcast you've ever done. Yes. And thank you for spending with us. What is, where is this coming from? What team are you in all that jazz?Ryan Lopopolo: Sure, sure.Ryan Lopopolo: I work on Frontier Product Exploration, new product development in the space of OpenAI Frontier, which is our enterprise platform for deploying agents safely at scale, with good governance in any business. And. The role of VMI team has been to figure out novel ways to deploy our models into package and products that we can sell as solutions to enterprises.swyx: And you have a background, I'll just squeeze it in there. Snowflake, brick, [00:02:00] stripe, citadel.Ryan Lopopolo: Yes. Yes. Same. Any kind of customerswyx: entire life. Yes. The exact kind of customer that you want to,Vibhu: so I'll say, I was actually, I didn't expect the background when I looked at your Twitter, I'm seeing the opposite.Stuff like this. So you've got the mindset of like full send AI, coding stuff about slop, like buckling in your laptop on your Waymo's. Yes. And then I look at your profile, I'm like, oh, you're just like, you're in the other end too. Oh, perfect. Makes perfect.Ryan Lopopolo: I it's quite fun to be AI maximalist if you're gonna live that persona.Open eye is the place to do it. And it'sswyx: token is what you say.Ryan Lopopolo: Yeah. Certainly helps that we have no rate limits internally. And I can go, like you said, full send at this stay.swyx: Yeah. Yeah. So the Frontier, and you're a special team within O Frontier.Ryan Lopopolo: We had been given some space to cook, which has been super, super exciting.[00:02:47] Zero Code ExperimentRyan Lopopolo: And this is why I started with kind of a out there constraint to not write any of the code myself. I was figuring if we're trying to make agents that can be deployed into end to enterprises, they should be [00:03:00] able to do all the things that I do. And having worked with these coding models, these coding harnesses over 6, 7, 8 months, I do feel like the models are there enough, the harnesses are there enough where they're isomorphic to me in capability and the ability to do the job.So starting with this constraint of I can't write the code meant that the only way I could do my job was to get the agent to do my job.Vibhu: And like a, just a bit of background before that. This is basically the article. So what you guys did is five months of working on an internal tool, zero lines of code over a mi, a million lines of code in the total code base.You say it was cenex, more like it was cenex faster than you would've. If you had done it by end. SoRyan Lopopolo: yeah, thatVibhu: was the mindset going into this, right?Ryan Lopopolo: That's right.[00:03:46] Model Upgrades LessonsRyan Lopopolo: Started with some of the very first versions of Codex CLI, with the Codex Mini model, which was obviously much less capable than the ones we have today.Which was also a very good constraint, right? Quite a visceral feeling to ask the [00:04:00] model to build you a product feature. And it just not being able to assemble the pieces together.Which kind of defined one of the mindsets we had for going into this, which is whenever the model just cannot, you always pop open at the task, double click into it, and build smaller building blocks that then you can reassemble into the broader objective.And it was quite painful to do this. Honestly, the first month and a half was. 10 times slower than I would be. But because we paid that cost, we ended up getting to something much more productive than any one engineer could be because we built the tools, the assembly station for the agent to do the whole thing.[00:04:43] Model Generations, Build Systems & Background ShellsRyan Lopopolo: But yeah, so onward to G BT 5, 5, 1, 5, 2, 5, 3, 5 4. To go through all these model generations and see their kind of corks and different working styles also meant we had to adapt the code base to change things up when the model was revved. [00:05:00] One interesting thing here is five two, the Codex harness at the time did not have background shells in it, which means we were able to rely on blocking scripts to perform long horizon work.But with five, three and background shells, it became less patient, less willing to block. So we had to retool the entire build system to complete in under a minute and. This is not a thing I would expect to be able to do in a code base where people have opinions. But because the only goal was to make the Asian productive over the course of a week, we went from a bespoke make file build to Basil, to turbo to nx and just left it there because builds were fast at that point.swyx: Interesting. Talk more about Turbo TenX. That's interesting ‘cause that's the other direction that other people have been doing.Ryan Lopopolo: Ultimately I have. Not a lot of experience with actual frontend repo architecture.swyx: You're talking that Jessica built the sky. So I'm like, I know the NX team. I know Turbo from Jared [00:06:00] Palmer.And I'm like, yeah, that's an interesting comparison.[00:06:02] One Minute Build LoopRyan Lopopolo: The hill we were climbing right, was make it fast.swyx: Is there a micro front end involved? Is it how how complex reactRyan Lopopolo: electron base single app sort of thingswyx: And must be under a minute. That's an interesting limitation. I'm actually not super familiar with the background shelf stuff.Probably was talked about in the fight three release.Ryan Lopopolo: BA basically means that codex is able to spawn commands in the background and then go continue to work while it waits for them to finish. So it can spawn an expensive build and then continue reviewing the code, for example.swyx: Yeah.Ryan Lopopolo: And this helps it be more time efficient for the user invoking the harness.swyx: And I guess and just to really nail this, like what does one minute matter? Like why not five, okay, good. We want no. WeRyan Lopopolo: want the inner loop to be as fast as possible. Okay. One minute was just a nice round number and we were able to hit it.swyx: And if it doesn't complete, it kills it or some something,Ryan Lopopolo: No.We just take that as a signal that we need to stop what we're doing, double click, decompose a build graph a bit to get us to high back under so that we [00:07:00] can able the agent continue to operate.swyx: It's almost like you're, it's like a ratchet. It's like you're forcing build time discipline, because if you don't, it'll just grow and grow.That's right. And you mentioned that my current, like the software I work on currently is at 12 minutes. It sucks.Ryan Lopopolo: This has been my experience with platform teams in the past, where you have an envelope of acceptable build times and you let it go up to breach and then you spend two, three weeks to bring it back down to the lower end of the average low bed stop.But because tokens are so cheap Yeah. And we're so insanely parallel with the model, we can just constantly be gardening this thing to make sure that we maintain these in variants, which means. There's way less dispersion in the code and the SDLC, which means we can simplify in a way and rely on a lot more in variance as we write the software.[00:07:45] Observability, Traces & Local Dev StackVibhu: Lovely.[00:07:46] Humans Are BottleneckVibhu: You mentioned in your article, like humans became the bottleneck, right? You kicked off as a team of three people. You're putting out a million line of code, like 1500 prs, basically. What's the mindset there? So as much as code is disposable, you're doing a lot of review. A lot [00:08:00] of the article talks about how you wanna rephrase everything is prompting everything, is what the agent can't see.It's kind of garbage, right? You shouldn't have it in there. So what's like the high level of how you went about building it, and then how you address okay, humans are just PR review. Like how is human in the loop for this?Ryan Lopopolo: We've moved beyond even the humans reviewing the code as well.[00:08:19] Human Review, PR Automation & Agent Code ReviewRyan Lopopolo: Most of the human review is post merge at this point.But post, post merge, that's not even reviewed. That's justswyx: Oh, let's just make ourselves happy by YouRyan Lopopolo: haven't used fundamentally. The model is trivially paralyzable, right? As many GPUs and tokens as I am willing to spend, I can have capacity to work with my hood base.The only fundamentally scarce thing is the synchronous human attention of my team. There's only so many hours in the day we have to eat lunch. I would like to sleep, although it's quite difficult to, stop poking the machine because it makes me want to feed it. You have to step back, right?Like you need to take a systems thinking mindset to things and [00:09:00] constantly be asking where is the agent making mistakes? Where am I spending my time? How can I not spend that time going forward? And then build confidence in the automation that I'm putting in place. So I have solved this part of the SDLC, and usually what that has looked like is like we started needing to pay very close attention to the code because the agent did not have the right building blocks to produce.Modular software that decomposed appropriately that was reliable and observable and actually accrued a working front end in these things, right?[00:09:35] Observability First SetupRyan Lopopolo: So in order to not spend all of our time sitting in front of a terminal at most, doing one or two things at a time, invested in giving the model that observability, which is that that graph in the post here.swyx: Yeah. Let's walk through this traces and which existed firstRyan Lopopolo: we started with just the app and the whole rest of it. From vector through to all these login metrics, APIs was, I dunno, half an [00:10:00] afternoon of my time. We have intentionally chosen very high level fast developer tools. There's a ton of great stuff out there now.We use me a bunch, which makes it trivial to pull down all these go written Victoria Stack binaries in our local development. Tiny little bit of python glue to spin all these up. And off you go. One neat thing here is we have tried to invert things as much as possible, which is instead of setting up an environment to spawn the coding agent into, instead we spawn the coding agent, like that's the entry point.It's just Codex. And then we give Codex via skills and scripts the ability to boot the stack if it chooses to, and then tell it how to set some end variables. So the app and local Devrel points at this stack that it has chosen to spin up. And this I think is like the fundamental difference between reasoning models and the four ones and four ohs of the past, where these models could not think so you had to put them in [00:11:00] boxes with a predefined set of state transitions.Whereas here we have the model, the harness be the whole box. And give it a bunch of options for how to proceed with enough context for it to make intelligent choices. SoVibhu: sales, so like a lot of that is around scaffolding, right? Yes. Previous agents, you would define a scaffold. It would operate in that.Lube, try again. That's pivoted off from when we've had reasoning models. They're seeming to perform better when you don't have a scaffold, right? That's right.[00:11:28] Docs Skills GuardrailsVibhu: And you go into like niches here too, like your SPEC MD and like having a very short agent MG Agent md.swyx: Yes. Yes.Vibhu: Yeah. So you even lay out what it is here, but I likeswyx: the table contents.Vibhu: Yeah.swyx: Like stuff like this, it really helps guide people because everyone's trying to do this.Ryan Lopopolo: This structure also makes it super cheap to put new content into the repository to steer both the humans and the agents.swyx: You, you reinvented skills, right?Vibhu: One big agents andswyx: skills from first princip holdsRyan Lopopolo: all skills did not exist when we started doing this.Vibhu: You have a short [00:12:00] one 100 line overall table of contents and then you have little skills, right? Core beliefs, MD tech tracker. Yeah. Yeah. The scale is overRyan Lopopolo: The tech jet tracker and the quality score are pretty interesting because this is basically a tiny little scaffold, like a markdown table, which is a hook for Codex to review all the business logic that we have defined in the app, assess how it matches all these documented guardrails and propose follow up work for itself.Before beads and all these ticketing systems, we were just tracking follow up work as notes in a markdown file, which, we could spa an agent on Aron to burn down. There's this really neat thing that like the models fundamentally crave text. So a lot of what we have done here is figure out ways to inject textswyx: intoRyan Lopopolo: the system right when we get a page, because we're missing a timeout, for example.I can just add Codex in Slack on that page and say, I'm gonna fix this by adding a timeout. Please update our reliability documentation. To require that all network calls have [00:13:00] timeouts. So I have not only made a point in time fix, but also like durably encoded this process knowledge around what good looks like.swyx: Yeah.Ryan Lopopolo: And we give that to the root coding agent as it goes and does the thing. But you can also use that to distill tests out of, or a code review agent, which is pointed at the same things to narrow the acceptable universe of the code that's produced.swyx: I think one of the concerns I have with that kind of stuff is you think you're making the right call by making, it's persisted for all time across everything.Yes. But then you didn't think about the exceptions that you need to make, right? And that you have to roll it back.Vibhu: Part of it isswyx: also sometimes it can follow your s instructions too.Vibhu: It's somewhat a skill, right? So it determines when it uses the tools, right? Like it's not like it'll run outta every call.It'll determine when it wants to check quality score, right?Ryan Lopopolo: Yeah. And we do in the prompts we give these agents, allow them to push back,[00:13:51] Agent Code Review RulesRyan Lopopolo: When we first started adding code review agents to the pr, it would be Codex, CLI. Locally writes the change, pushes up a PR on [00:14:00] those PR synchronizations of review agent fires.It posts a comment. We instruct Codex that it has to at least acknowledge and respond to that feedback. And initially the Codex driving the code author was willing to be bullied by the PR reviewer, which meant you could end up in a situation where things were not converging. So yeah, we had to,swyx: he's just a thrash.Ryan Lopopolo: We had to add more optionality to the prompts on both of these things, right? The reviewer agents were instructed to bias toward merging the thing to not surface anything greater than a P two in priority. We didn't really define P two, but we gave it, youswyx: did define P two.Ryan Lopopolo: We gave it a framework within which to score its outputswyx: and then greater than P zero is worse, right?Yes. P two is very good.Ryan Lopopolo: P zero is you will mute the code place ifswyx: you merch thisRyan Lopopolo: thing, right?swyx: Yeah.Ryan Lopopolo: But also on the code authoring agent side, we also gave it the flexibility to either defer or push back against review feedback, right? This happens all the time, right? Like I happen to notice something and leave a code review, [00:15:00] which.Could blow up the scope by a factor of two. I usually don't mean for that to be addressed Exactly. In the moment. It's more of an FYI file it to the backlog, pick it up in the next fix it week sort of thing. And without the context that this is permissible, the coding agents are gonna bias toward what they do, which is following instructions.swyx: Yeah.[00:15:19] Autonomous Merging Flowswyx: I do wanted to check in on a couple things, right? Sure. All the coding review agent, it can merge autonomously. I think that's something that a lot of people aren't comfortable with. And you have a list here of how much agents do they do Product code and tests, CI configuration and release tooling, internal Devrel tools, documentation eval, harness review, comments, scripts that manage the repository itself, production dashboard definition files, like everything.Yes. And so they're just all churning at the same time, is there like a record that, that any human on the team pulls to stop everythingRyan Lopopolo: Because we are building a native application here. We're not doing continuous deploy. So there's still a human in the loop for cutting the release branch.I see. We require a blessed [00:16:00] human approved smoke test of the app before we promote it to distribution, these sort of things.swyx: So you're working on the app, you're not building like infrastructure where you have like nines of reliability, that kinda stuff?Ryan Lopopolo: That's correct. That's correct. Okay. And also like full recognition here that all of this activity took in a completely greenfield repository.There's. Should be no script that this applies generally toswyx: this is a production thing, you're gonna shipRyan Lopopolo: toswyx: customers. Of course. Yeah, of course. So this is realVibhu: And like one of the things there is, you mentioned you started this as a repo from scratch. The onboarding first month or so was pretty, it was like working backwards, right?Yeah. And then you had to work with the system and now you're at that point where you know, you're very autonomous. I'm curious like, okay, so what, how human in the loop is it? So what are the bottlenecks that you wish you could still automate? And part of that is also like, where do you see the model trajectory improving and offloading more human in the loop?We just got 5.4. It's a really good,Ryan Lopopolo: fantastic model, by the way.Vibhu: Yeah. Yeah. It's the first one that's merged. Top tier coding. So it's codex level coding and reasoning. So general reasoning both in one model. SoRyan Lopopolo: andVibhu: computer [00:17:00] use vision.Ryan Lopopolo: Now we now with five four, I can just have Codex write the blog post, whereas for this one I had to balance between chat.swyx: Oh, I need to, I might be out of a job. Oh my God.Ryan Lopopolo: Oh,swyx: I know. You just gave me an idea for a completely AI newsletter that five four could do. Yeah, I get it Now.Ryan Lopopolo: This sort of thing is just one example of closing the loop, right? Like the dashboard thing you mentioned. We have Codex authoring the Js ON, for the Grafana dashboards and publishing them and also responding to the pages, which means when it gets the page, it knows exactly which dashboards are defined and what alerts.What alert was triggered by which exact log in the code base. ‘cause all of this stuff is collated together.swyx: It has to own everything.Yes. Yeah. Yeah.Ryan Lopopolo: And it means that if we have an outage that did not result in a page. It has the existing set of dashboards available to it. It has the existing set of metrics and logs and can figure out where the gaps in the dashboard are or [00:18:00] in the underlying metrics and fix them in one go.In the same way, you would have a full stack engineer be able to drive a feature from the backend all the way to the front end.Vibhu: So it, it seems like a lot of the work you guys had to do was you as a small team are fully working for a way that the model wants the software to be written. It's like less human legible for better. Code legibility, agent legibility. How do you think that affects broader teams? So one at OpenAI, do liaison, like this is how software should be written. Like I can imagine, say you join a new team with this methodology, this mindset there's ways that, teams do code review, teams write code, like teams are structured and a lot of it is for human legibility.So should we all swap? Like how does this play back one broader into OpenAI and then like broader into the software engineering, right? Is it like teams that pick this up will it's pretty drastic, right? You have to make a pretty big switch. Should they just full send Yeah.Ryan Lopopolo: The mindset is very much that I'm removed from the process, right? I can't really have deep code level opinions about [00:19:00] things. It's as if I'm. Group tech leading a 500 person organization.Vibhu: Yeah.Ryan Lopopolo: Like it's not appropriate for me to be in the weeds on every pr. This is why that post merge code review thing is like a good analog here, right?Like I have some representative sample of the code as it is written, and I have to use that to infer what the teams are struggling with, where they could use help, where they're already moving quickly and I can pivot my focus elsewhere.Vibhu: Yeah.Ryan Lopopolo: So I don't really have too many opinions around the code as it is written.I do, however, have a command based class, which is used to have repeatable chunks of business logic that comes with tracing and metrics and observability for free. And the thing to focus on is not how that business logic is structured, but that it uses this primitive ‘cause I know that's gonna give leverage by default.Vibhu: Yeah.Ryan Lopopolo: Yeah, back to that sort of systems stinking,Vibhu: and you have part of that in your blog post, enforcing architecture and ta taste how you set boundaries for what's used. There's also a section on redefining [00:20:00] engineering and stuff, but yeah, it's just, it's interesting to hear,Ryan Lopopolo: and as the models have gotten better, they have gotten better at proposing these abstractions to unblock themselves, which again, lets me move higher and higher up the stack to look deeper into the future on what ultimately blocked the team from shipping.swyx: Yeah. You mentioned so you, this is primarily a, it is like a 1 million line of code base electron app. But it manages its own services as well, so it's like a backend for front end type thing.Ryan Lopopolo: We do have a backend in there, but that's hosted in the cloud.Yeah. This sort of structure is actually within the separate main and render processesWithin theswyx: electric.That's just how electronic works.Ryan Lopopolo: Yeah, of course. So have also treated like. MVC style decomposition with the same level of rigor, which has been very fun.swyx: I have a fun pun. This is a tangent, NVC is model view controller. Any sort of full stack web Devrel knows that.But my AI native version of this is Model view Claw, the clause the harness.Ryan Lopopolo: That's right. That's right. I do think that there is an interesting space to [00:21:00] explore here with Codex, the harness as part of building AI products, right? There's a ton of momentum around getting the models to be good at coding.We've seen big leaps in like the task complexity with each incremental model release where if you can figure out how to collapse a product that you're trying to build, a user journey that you're trying to solve into code, it's pretty natural to use the Codex Harness to solve that problem for you. It's done all the wiring and lets you just communicate and prompts to let the model cook.Yeah. It's been very fun. And there's also a very engineering legible way of increasing capabil. It's fantastic, right? Yeah. Just give you, just give the model scripts, the same scripts you would already build for yourself.swyx: Yeah.Yeah. So for listeners, this is Ryan saying that software engineering or coding against will eat knowledge work like the non-coding parts that you would normally think.Oh, you have to build a separate agent for it. No, start a coding agent and go out from there. Which open Claw has like it's pie Underhood.Ryan Lopopolo: [00:22:00] Yes.Vibhu: Basically define your task in code. Everything is a codingswyx: agent by the way. Since I brought it up, it's probably the only place we bring it up. Is any open claw usage from you?Any?Ryan Lopopolo: No. No. Not for me. I don't have any spare Mac Minis rattling around my house.swyx: You can afford it? No. I just, I'm curious if it's changed anything in opening eye yet, but it's probably early days. And then the other, the other thing I, I wanna pull on here is like you mentioned ticketing systems and you mentioned prs and I'm wondering if both those things have to go away or be reinvented for this kind of coding.So the git itself and is like very hostile to multi-agent.Ryan Lopopolo: Yeah. We make very heavy use of work trees.swyx: But like even then, like I just did a, dropped a podcast yesterday with Cursors saying, and they said they're getting rid of work trees ‘cause it still has too many merge conflicts.It's still un too un unintuitive. But go ahead.Ryan Lopopolo: The models are really great at resolving merge conflicts. Yeah. And to get to a state where I'm not synchronously in the loop in my terminal, I almost don't care that there are mergeswyx: with disposable.[00:23:00] Yeah.Ryan Lopopolo: We invoke a dollar land skill and that coaches codex to push the PR Wait for human and agent reviewers Wait for CI to be green.Fix the flakes if there are any merged upstream. If the PR comes into conflict, wait for everything to pass. Put it in the merge queue. Deal with flakes until it's in Maine. End. This is what it means to delegate fully, right? This is in a, very large model re probably a significant tax on humans to get PRS merged, but the agent is more than capable of doing this and I really don't have to think about it other than keep my laptop open.swyx: Yeah. I used to be much more of a control freak, but now I'm like, yeah, actually you could do a better job of this than me. Yeah. With the right context. Yes.[00:23:47] Encoding Requirementsswyx: Anything else in harness in general? Just this piece, I just wanna make sure we,Ryan Lopopolo: I think one thing that I maybe didn't make super clear in the article that I heard on Twitter as an interesting, that's respond [00:24:00]swyx: to them.What's the chatter and then what's your response?Ryan Lopopolo: Ultimately, all the things that we have encoded in docs and tests and review agents and all these things are ways to put all the non-functional requirements of building high scale, high quality, reliable software into a space that prompt injects the agent.We either write it down as docs, we add links where the error messages tell how to do the right thing. So the whole meta of the thing is to basically tease out of the heads of all the engineers on my team, what they think good looks like, what they would do by default, or what they would coach a new hire on the team to do to get things to merch.And that's why we pay attention to all the mistakes, mistakes that the agent makes, right? This is code being written that is misaligned with some as yet not written down, non-functional requirement.swyx: Sorry, what? Did the online people misunderstand orRyan Lopopolo: No,swyx: whatyouRyan Lopopolo: responded to? Somebody just literally said that.I was like, oh yeah,swyx: okay,Ryan Lopopolo: This is the [00:25:00] thing. This is what I've been doing. Oh, youswyx: agree? Yeah. I see. Interesting.Ryan Lopopolo: One other neat thing, which I did totally did not expect is folks were just. Taking the link to the article and giving it to pi or Codex and say, make my repo this,Vibhu: you achi a whole recursion.Ryan Lopopolo: And it was wildly effective. Really? It was wildly effective. NoVibhu: way. It just actually is something I tried with five, four yesterday. I didn't have time. Last time I was like out speaking of something, and this is one of my things, I was like, okay, I have this article. Can we just scaffold out what it would be like to run this?And I, I did it first as that and then I was like, okay, let me take another little side repo and say okay, if I was to fully automate this like this because I haven't written a line of code, it'sRyan Lopopolo: like over full, setVibhu: it right. The side thing I'm doing of voice. TTS I'm just like, slobbing out, whatever.It's nothing production. I'm like, how would I make this like this? And it's actually like a really good way. It's like a good way to learn what could be changed, what could be like, it's just a good analyzing, right? You give it all the codes, you give it all the context, you give it the article and it walks you through it very well.That's right. That's right.[00:25:57] Inlining Dependencies[00:25:57] Dependencies Going Away & Brett Taylor's Responseswyx: I guess one more thing before we go to Symphony is I wanted to cover [00:26:00] Brett Taylor's response. We had him on the show. He is your chairman, which is wild. Yeah. That he's reading your articles as well and like getting engaged in it. He says software dependencies are going away.Basically they can just be like vendored. Yes. Response.Ryan Lopopolo: Aswyx: hundred percent. A hundred percent agree. You still pro qr, you still pay Datadog. You still pay Temporal. Thank you.Ryan Lopopolo: Yep. The level of complexity of the dependencies that we can internalize is, I would say low, medium right now. Just based on model capability.What does the,swyx: what is medium?Ryan Lopopolo: I would say like a. A couple thousand line dependency is a thing that we could in-house No problem. Call in an afternoon of time. One neat thing about it is like probably most of that code you don't even need. Like by in-house and abstraction, you can strip away all the generic parts of it and only focus on what you need to enable the specific thing.Yes. You're building,swyx: I've been calling this the end of b******t plugins.Ryan Lopopolo: Yeah.swyx: Because there's so much when I published an open source thing, I want to accept everything, be liberal. I want to accept, this is post's law, but that means there's so much bloat. Yes. There's so much overhead.Ryan Lopopolo: One other neat thing about [00:27:00] this too is when we deploy Codex Security on the repo, it is able to deeply review and change. The internalized dependencies in a much lower friction way than it would be to like, push patches upstream, wait for them to be released, pull them down, make sure that's compatible with all the transitive I have in my repo and things like that.So it's also much lower friction to internalize some of these things if code is free. ‘cause the tokens are cheap sort of thing.swyx: Yeah. Yeah. I think like the only argument I have against this is basically scale testing, which obviously the larger pieces of software like Linux, MySQL, he calls up even the Datadog and Temporals and then maybe security testing where Yes.Classically, I think, is it linis tos, it said security open source is the best disinfectant.Ryan Lopopolo: Many eyes.swyx: Many eyes. And if inline your dependencies and code them up, you're gonna have to relearn mistakes from other people that Yep.Ryan Lopopolo: Yep. And to internalize that dependency, you're back to zero and you have to start.Reassembling all those bits and pieces to Yeah. Have [00:28:00] high confidence in the code as it is written. Yeah.Vibhu: Even part of the first intro of this, you basically mentioned like everything was written by codex, including internal tooling, right? So internal tooling, like when you're visualizing what's going on it's writing it for itself.swyx: Yeah. I'm built internal tools way I now, and like I just show them off and they're like, how long did you spend? And I didn't spend any time. I just prompted it,Ryan Lopopolo: very funny story here.swyx: Yeah, go ahead.Ryan Lopopolo: We had deployed our app to the first dozen users internally had some performance issues, so we asked them to export a trace for us get a tar ball, gave it to our on-call engineer, and he did a fantastic job of working with Codex to build this beautiful local Devrel tool, next JS app, the drag and drop the tar ball in, and it visualizes the entire trace.It's fantastic. Took an afternoon, but none of this was necessary. Because you could just spin up codex and give it the tar ball and ask the same thing and get the response immediately. So in a way, optimizing for human [00:29:00] legibility of that debugging process was wrong. It kept him in the loop unnecessarily when instead he could have just like Codex cooked for five minutes and gotten this same.swyx: Yeah, you verify your instincts here of this is how we used to do it. Or this is how I would have used to solve it.Ryan Lopopolo: Yeah. In this local observability stack. Like sure, you can de deploy Yeager to visualize the traces, but I wouldn't expect to be looking at the traces in the first place because I'm not gonna write the code to fix them.swyx: Yeah. So basically there needs to be like this kind of house stack and owning the whole loop. I think that is very well established. And it sounds like you might be like sharing more about that in the future, right?Ryan Lopopolo: Yeah. I think we're excited to do[00:29:36] Ghost Libraries Specs[00:29:36] Ghost Libraries & Distributing Software as SpecsRyan Lopopolo: We're gonna talk about Symphony in a little bit, but like the way we distribute it as a spec, which I think folks are calling Ghost Libraries on Twitter.This is like a such a cool name. It does mean it becomes much cheaper to share software with the world, right? You define a spec, how you could build your own specifying as much as is required for a coding agent to reassemble it [00:30:00] locally. The flow here is very cool. Like we have taken. All the scaffolding that has existed in our proprietary repo spun up a new one.Ask Codex with our repo as a reference. Write the spec. We tell it. Spin up a team ox spawn a disconnected codex to implement the spec. Wait for it to be done. Spawn another codex and another team ox to review the spec com or review the implementation compared to upstream and update the spec so it diverges less.And then you just loop over and over Ralph style until you get a spec that is with high fidelity able to reproduce the system as it is. It's fantastic.Vibhu: And you're basically, you're not really adding any of your human bias in there, right? That's correct. A lot of times people write a spec and be like, okay, I think it should be done this way, and you'll riff on something.And it's no, the agent could have just handled it like you're still scaffolding in a sense, right? I want it done this way. It can determine its spec better.swyx: That's right. That's right. Part of me it, I'm, I've been working a lot on evals recently, and part of me is wondering if [00:31:00] an agent can produce a spec that it cannot solve.Is it always capable of things that he can imagine or can you imagine things that it is impossible to do?Ryan Lopopolo: I think with Symphony, we, there's like this there's this axis where you have things that are easier, hard, or established or new, right? And I think things that are hard and new is still something that the models need humans.Yeah. Drive.swyx: Yeah. Yeah.Ryan Lopopolo: But I think those other quadrants are largely salt. Given the right scaffold and the right thing that's gonna drive the agent to completion,swyx: it's crazy that it solved,Ryan Lopopolo: but it means that the humans, the ones with limited time and attention get to work on the hardest stuff, like the problems where it's pure white space out in front. Or like the deepest refactorings where you don't know what the proper shape of the interfaces are. And this is where I wanna spend my time. ‘cause it lets me set up for the next level of scale.swyx: Yeah. Yeah. Amazing. Let's introduce Symphony.I think we've been mentioning it every now and then. Elixir. Interesting option.Ryan Lopopolo: Yeah.swyx: Yeah. I'm not,Ryan Lopopolo: again, like the [00:32:00] elixir manifestation here is just a derivative. Is it a modelswyx: chosen? Yeah.Ryan Lopopolo: Yeah. Yeah. And it chose that because the process supervision and the gen servers are super amenable to the type of process orchestration that we're doing here.You are essentially spinning up little Damons for every task that is in execution and driving it to completion, which. Means the mall gets a ton of stuff for free by using Elixir and the Beam.swyx: I had to go do a crash course in Beam and Elixir, and I think most people are not operating at that scale of concurrency where you need that.But it is a good mental model for Resum ability and all those things. And these are things I care about. But tell me the story, the origin story of Symphony. What do you use it for? Is this, how did it form maybe any abandoned paths that you didn't take?[00:32:46] Terminal Free Orchestration[00:32:46] Symphony: Removing Humans from the LoopRyan Lopopolo: At the end of December we were at about three and a half PRS per engineer per day.This was before five two came out in the beginning of January. Everyone gets back from holiday with five two and no other work [00:33:00] on the repository. We were up in the five to 10 PRS per day per engineer. And I don't know about y'all, but like it's very taxing to constantly be switching like that. Like I was pretty tapped out at the end of the day, again, where are the humans spending their time? They're spending their time context switching between all these active tmox pains to drive the agent forward.swyx: Yeah. No way. Yeah.Ryan Lopopolo: So let's again, build something to remove ourselves from the loop. And this is what frantic sprinted adapt here to find a way to remove the need for the human to sit in front of their terminal.So a lot of experimentation with Devrel boxes and, automatically spinning up agents, like it seems like a fantastic end state here, where my life is beach. I open live twice a day and say yes no to these things. Yeah. And this is again, a super, super interesting framing for how the work is done.Because I become more latency and sensitive. I have [00:34:00] way less attachment to the code as it is written. Like I've had close to zero investment in the actual authorship experience. So if it's garbage. I can just throw it away and not care too much about it. In Symphony, there's this like rework state where once the PR is proposed and it's escalated to the human for review, it should be a cheap review.It is either mergeable or it is not. And if it's not, you move it to rework. The elixir service will completely trash the entire work tree NPR and start it again from scratch. Okay. And this is that opportunity again to say, why was it trash right? What did the agent do that wasswyx: bad. Yeah.Ryan Lopopolo: Fix that before moving the ticket toswyx: endRyan Lopopolo: of progress again.swyx: Yeah. Why is this not in codex app? I guess this, you guys are ahead of Codex app,Ryan Lopopolo: yeah, so the way the team has been working is basically to be as AI pilled as possible and spread ahead. And a lot of the things we have worked on have fallen out [00:35:00] into a lot of the products that we have.Like we were in deep consultation with the Codex team to. Have the Codex app be a thing that exists, right? To have skills be a thing that Codex is able to use. So we didn't have to roll our own to put automations into the product. So all of our automatic refactoring agents didn't have to be these hand rolled control loops.It has been really fantastic to be, in a way, un anchored to the product development of Frontier and Codex and just very quickly try to figure out what works and then later find the scalable thing that can be deployed widely. It's been a very fun way to operate. It's certainly chaotic. I have lost track very often of what the actual state of the code looks like.‘cause I'm not in the loop. There was. One point where we had wired playwright directly up to the Electron app. With MCPM CCPs, I'm pretty bearish on because the harness forcibly injects all those tokens in the [00:36:00] context, and I don't really get a say over it. They mess with auto compaction. The agent can forget how to use the tool.There's probably only what three calls in playwright that I actually ever want to use. So I pay the cost for a ton of things. Somebody vibed a local Damon that boots playwright and exposes a tiny little shim CLI to drive it. And I had zero idea that this had occurred because to me, I run Codex and it's able to, it's oh, it's better.Yeah. Like no knowledge of this at all. Uhhuh.[00:36:30] Multi Human ChaosRyan Lopopolo: So we have had like in human space to spend a lot of time doing synchronous knowledge sharing. We have a daily standup that's 45 minutes long because we almost have to. Fan out the understanding of the current state.swyx: Yeah, I was gonna say this is good for a single human multi-agent, but multi human, multi-agent is a whole like po like explosion of stuff.Ryan Lopopolo: Yeah. And that this is fundamentally why we have such a rigid, like 10,000 [00:37:00] engineer level architecture in the app because we have to find ways to carve up the space so people are not trampling on each other.swyx: Sorry, I don't get the 10,000 thing. Did I miss that?Ryan Lopopolo: The structure of the repository is like 500 NPM packages.It's like architecture to the excess for what you would consider, I think normal for a seven person team. But if every person is actually like 10 to 50. Then the like numbers on being super, super deep into decomposition and sharding and like proper interface boundaries make a lot more sense.swyx: Yeah. To me, that's why I talked about Microfund ends and I, an anex is from that world, but Cool. It is just coming back to, to, to this I dunno if you have other, thoughts on. Orchestrating so much work coin going through this. Is this enough? Is this like any aha moments?Vibhu: It'll be interesting to see like where, okay, so right now you pick linear as your issue tracker, right?swyx: Or it's like a is it actually linear? This is actually linear.[00:37:55] Linear vs Slack WorkflowVibhu: Oh, that's linear. It's linear.swyx: Oh I never looked atVibhu: video. The demo video I had to download to [00:38:00] run.swyx: So I, because I'm a Slack maxie, but Yeah, linear. Linear is also really good. Yes,Ryan Lopopolo: we do make a good use of Slack. We we fire off codex to do all these lotion, elasticity, fix ups, the things that like sync that knowledge into the repository.It's super cheap. Yeah.swyx: Yeah.Ryan Lopopolo: Just do it in Codex.swyx: My biggest plug is OpenAI needs to build Slack. You need to own Slack. Build yours. Turn this into Slack.Ryan Lopopolo: I did read about it. Youswyx: did?Ryan Lopopolo: Yeah.[00:38:25] Collaboration Tools for AgentsRyan Lopopolo: I would say that if we think that we want these agents to do economically valuable work, which is like this is the mission, right?We want AI to be deployed widely, to do economically valuable work, then we need to find ways for them to naturally collaborate with humans, which means collaboration tooling, I think, is an interesting space to explore.swyx: Yeah, totally. Yeah. GitHub, slack, linear.Vibhu: Yeah, that was my thing. Okay, where do we see right now Codex has started Codex Model, then CLI, now there's an app, app can let me shoot off multiple Codex is in parallel, but there's no great team collaboration for Codex.And it [00:39:00] seems like your team had some say into what comes out, right? So you talked to ‘em, codex kind of was a thing. From there, if you guys are on the bound, what stuff that like, you might not focus on, but what do you expect other people to be building, right? So people that are like five x 50 Xing.Should you build stuff that's like very niche for your workflow, for your team? Should it be more general so other people can adopt? Is there a niche there? ‘Cause part of it is just okay, is everything just internal tooling? Do we have everything our own way? Like the way our team operates has our own ways that we like to communicate or is there a broader way to do it?Is it something like a issue tracker? Just thoughts if you wanna riff on that.[00:39:35] Standardizing Skills and CodeRyan Lopopolo: I think TBD we have not figured this out in a general way. I do think that there is leverage to be had in making the code and the processes as much the same as possible. If you think that code is context, code is prompts, it's better from the agent behavior perspective to be able to look in a package in directory X, Y, Z, and it not to have to page so [00:40:00] deeply into directory if you C, because they have the same structure, use the same language, they have the same patterns internally.And that same like leverage comes from aligning on a single set of skills that you're pouring every engineer's taste into to make sure that the agent is effective. So like in our code base, we have, I think, six skills. That's it. And if some part of the software development loop is not being covered, our first attempt is to encode it in one of the existing setup skills, which means that we can change the agent behavior.Yeah. More cheaply than changing the human driver behavior.swyx: Yeah.[00:40:39] Self Improvement via Logsswyx: Have you ever, have you experimented with agents changing their own behavior?Ryan Lopopolo: We do.swyx: Yeah. Or parent agent changing a subagents, behavior or something like that.Ryan Lopopolo: We have some bits for skill distillation. So for example, there's one neat thing you can do with Codex, which is just point it at its own session logs to ask it to tell you how you can use [00:41:00] the tool pedal better.swyx: It's like introspectionRyan Lopopolo: or ask it to do things. I useVibhu: this session better. What skills should Iswyx: high? I like the modification of, you can do, just do things to you can just ask agent to do things.Ryan Lopopolo: Yeah. You can just codex things. This is like a, this is like a silly emoji that we have, right? You can just codex things, you can just prompt things.It's really glorious future we live in, but okay, you can do that one-on-one. But we're actually slurping these up for the entire team into blob storage and. Running agent loops over them every day to figure out where as a team can we do better and how do we reflect that back into the repositories?Yes, though everybody benefits from everybody else's behavior for free. Same for like PR comments, right? These are all feedback. That means the code as written, deviated from what was good, a PR comment, a failed build. These are all signals that mean at some point the agent was missing context. We gotta figure out how toswyx: Yeah.Ryan Lopopolo: Slurp it up and put it back in the reboot.swyx: By the way, I do this exactly right. I used to, when I use cloud code for [00:42:00] knowledge work, cloud cowork is like a nice product, right? Yes. In I think you would agree. I always have it tell me what do I do better next time? And that's the meta programming reflection thing.So I almost think like you have six reflection extraction levels in symphony and almost like the zero of layer. So the six levels are PO policy, configuration, coordination, execution, integration, observability. We've talked about a couple of these, but the zero layer is like the, okay, are we working well?Can we improve how we work? Yes. Can I modify my own workflow without MD or something? I don't know.Ryan Lopopolo: Yeah, of course. Yeah, of course you can. Like this thing is also able to cut its own tickets ‘cause we give it full access.Yeah. Make it a ticket to have it cut. Tickets you can.Put in the ticket that you expect it to file as on follow up work,swyx: like Yeah. Self-modifying. Yeah.Ryan Lopopolo: Yeah.[00:42:44] Tool Access and CLI FirstRyan Lopopolo: Put, don't put the agent in a box. Give the agent full accessibility over it. Domain.swyx: I had a mental reaction when you said don't put the agent in a box. So I think you should put it in a box. Like it's just that you're giving the box everything it needs.Ryan Lopopolo: Yeah. Context and tools.swyx: But we're like, as developers, we're used to calling [00:43:00] out to different systems, but here you use the open source things like the Prometheus, whatever, and you run it locally so that you can have the full loop. I assume.Ryan Lopopolo: Yep.Vibhu: I think likeRyan Lopopolo: another, you wanna minimize cloud, cloud dependencies.Vibhu: You also want to make sure that you think about what the agent has access to. What does it see? Does it go back into the loop, like from the most basic sense of you let it see its own like calls, traces it can determine where it went wrong. But are you feeding that back in? So you know, just the most basic level of you wanna see exactly what's input output, like does the agent have access to.What is being outputted, right? It can self-improve a lot of these things. It's allRyan Lopopolo: text, right? My job is to figure out ways to funnel text from one agent to the other.swyx: It's so strange like way back at the start of this whole AI wave Andre was like, English is the hottest day programming language.It's here, it's just Yeah. The feature as well.Vibhu: A lot of, okay. Like a lot of software, a lot of stuff. There's a gui, it's made for the human. We're seeing the evolution of CLI for everything, right? All tools have CLIs. Your agents can use [00:44:00] them well, do we get good vision? Do we get good little sandboxes?Like right now? It's a really effective way, right? Models love to use tools. They love the best. They love to read through text. So slap a CLI let it go loose. That works for everything.Ryan Lopopolo: It does. Yeah. Yeah.[00:44:14] UI Perception and RasterizingRyan Lopopolo: We've also been adapting nont, textual things to that shape in order to improve model behavior in some ways, right?We want the agent to be able to see the UI agents do not perceive visually in the same way that we do. They don't see a red box, they see red box button, right? They see these things in latent space. So if we want, Hey, yeah, I do. We haveswyx: a ding if that goes off every time. Alien spaceRyan Lopopolo: ding.Anyway if we wanna actually make it see the layout, it's almost easier to rasterize that image to ask EOR and feed it in to the agent. Ha. And there's no reason you can't do both, right? To like further refine how the model perceives the object it's [00:45:00] manipulating.swyx: Cool. Could we, you wanna talk about a couple more of these layers that might bear more introspection or that you have personal passion for?[00:45:07] Coordination Layer with ElixirRyan Lopopolo: I will say that the coordination layer here was a really tricky piece to get right.swyx: Let's do it. Yep. I'm all about that. And this is Temporal core.Ryan Lopopolo: This is where when we turn the spec into Elixir, where like the model takes a shortcut, right? Like it's oh, I have all these primitives that I can make use of in this lovely runtime that has native process supervision.Which is I think, a neat way to have taken the spec and made it more choices achievable by making choices that naturally mapswyx: Yeah.Ryan Lopopolo: To the domain, right? In the same way that like you would prefer to have a TypeScript model repo if you are doing full stack web development, right? Because the ability to share types across the front end and backend reduces a lot of complexity.And becauseswyx: that's what graph kill used to be.Ryan Lopopolo: That's right. Andswyx: I don't know if it's still alive, butRyan Lopopolo: [00:46:00] no humans in the loop here. So like my own personal ability to write or not write elixir. Doesn't really have to bias us away from using the right tool for the job. It is just wild.swyx: Love it. I love it.Yeah. I wonder if any languages struggle more than others because of this? I feel like everyone has their own abstractions. That would make sense. But maybe it might be slower, it might be more faulty where like you'd have to just kick the server every now and then. I, I don't know. I think observability layer is really well understood.Integration layer, CP is dead. I think all these just like a really interesting hierarchy to travel up and down. It's common language for people working on the system to understandRyan Lopopolo: The policy stuff is really cool, right? Yeah. You don't really have to build a bunch of code to make sure the system wait for the, to passswyx: it's institutional knowledge.Ryan Lopopolo: Yeah. You just give it the G-H-C-L-I with some text that say CI has to pass. It makes the maintenance of these systems a lot easier.[00:46:57] Agent Friendly CLI Outputswyx: Do you think that CLI maintainers need to be [00:47:00] do anything special for agents or just as is? It's good because like I don't think when people made the G GitHub, CLI, they anticipated this happening.Ryan Lopopolo: That's correct. The GH CLI is fantastic. It's great super industry.swyx: Everyone go try GH repo create GH pull and then pull request number, right? GH HPR, like 1 53, whatever. And then it like pullsRyan Lopopolo: basically my only interaction with the GitHub web UI at this point is GH PR view dash web.Exactly. Glanceswyx: at the diffRyan Lopopolo: and be like Sure thing. Send it. Yeah. But the CLI are nice ‘cause they're super token efficient and they can be made more token efficient really easily. Like I'm sure you all have seen like I go to build Kite or Jenkins and I could just get this massive wall of build output.And in order to unblock the humans, your developer productivity team is almost certainly gonna write some code that parses the actual exception out of the build logs and sticks it in a sticky note at the top of the page. And you basically [00:48:00] want CLI to be structured in a similar way, right? You're gonna want to patch dash silent to prettier because the agent doesn't care that every file was already formatted.Just wants to know it's either formatted or not. So it can then go run a right command. Similarly, like in our PNPM distributed script runner, when we had one, when you do dash recursive, like it produces a absolute mountain of text. But all of that is for passing. Test suites. So we ended up wrapping all of this in another scriptswyx: to suppress the,Ryan Lopopolo: which you can vibe the channel only output the failing parts of the tests.swyx: You make a pipe errors versus the standard, standard out. I don't know. Okay. Whatever. Too much thinking have to do that. The CII used to maintain SCLI for my company and yeah, this is like core, very core to my heart. But you're vibing my job.Ryan Lopopolo: That's right.swyx: Cool. Any other things?This is a long spec. [00:49:00] I appreciate that. It's got a lot of strong opinions in here. Any other things that we should highlight? I think obviously you can spend the whole day going through some of these, but I do think that some of these have a lot of care or some of this you might wanna tell people, Hey, take this, but, make it your own.[00:49:15] Blueprint Spec and GuardrailsRyan Lopopolo: Fundamentally, software is made more flexible when it's able to adapt to the environment in which it is deployed, which means that things like linear or GitHub even are specified within the spec, but not required pieces of it. There's like a more platonic ideal of the thing that you could swap in like Jira or Bitbucket, for example.But being able to tightly specify things like the ID formats or how the Ralph Loop works for the individual agents. Basically means you can get up and running with a fully specified system quickly that you then evolve later on. I think we never intended for this to be a static spec that you can [00:50:00] never change.It's more like a blueprint to get something worth a starting point up and running.swyx: Yeah.Ryan Lopopolo: For you then to vibe later to your heart's content,swyx: you have like code and scripts in here where it's oh, I think this is a really good prompt. It's just a very long prompt.Ryan Lopopolo: Fundamentally, the agents are good at following instructions, so give them instructions.And it will, improve the reliability of the result. We, much like the way we use Symphony, we don't want folks to have to monitor the agent as it is vibing the system into existence. So being very opinionatedVery strict around what these success criteria are means that our deployment success rate goes up. Yeah. It means we don't have to get tickets on this thing.Vibhu: Think it all goes back to that like code to disposable, right? Like early on when you had CLI or you'd kick off a Codex run, it would take two hours. You would wanna monitor okay, I'm in the workflow of just using one.I don't want it to go down the wrong path. I'll cut it off and, just shoot off four, like that was my favorite thing of the Codex app, right? Yeah. Just Forex it like, [00:51:00] it's okay. One of them will probably be right, one of them might be better. Stop overthinking it. Like my first example was probably like deep research.When you put out deep research and I'd ask it something like, I asked it something about LLM, it thought it was legal something and spent an hour, came back with a report completely off the rails. And I was like, okay, I gotta monitor this thing a bit. No don't monitor it. Just you want to build it so it's that it, it goes the right way.And you don't wanna, you don't wanna sit there and babysit, right? You don't want to babysit your agentsRyan Lopopolo: with that deep research query that you made. Looking at the bad result, you probably figured out you needed to tweak your prompt Yeah. A bit, right? That's that guardrail that you fed back into the code base for the task, your prompt to further align the agent's execution.Same sort of concept supply there too.swyx: When you talk, how are the customers feelingRyan Lopopolo: for Symphony? I think we have none, right? This is a thing we have put out into theswyx: world. Symphony's internal, right? As long as you are happy, you are the customer. That'

ASP.NET Core continues to evolve in 2026! Carl and Richard talk to Daniel Roth about all the goodness in the ASP.NET Core space, including MVC, Razor, and Blazor! Daniel talks about the publicly visible ASP.NET Core Roadmap on GitHub - where you can support ideas, add your own, and debate implementations! The conversation dives into the focus on Blazor - MVC and Razor aren't going away anytime soon, or perhaps ever. Still, the energy is definitely on Blazor, and its potential to provide a great development experience that scales effectively and provides the features your applications need. And Daniel reminds us that the teams all work closely together, including the broader .NET and language teams, so new features are in the right place and available to everyone!

ASP.NET Core continues to evolve in 2026! Carl and Richard talk to Daniel Roth about all the goodness in the ASP.NET Core space, including MVC, Razor, and Blazor! Daniel talks about the publicly visible ASP.NET Core Roadmap on GitHub - where you can support ideas, add your own, and debate implementations! The conversation dives into the focus on Blazor - MVC and Razor aren't going away anytime soon, or perhaps ever. Still, the energy is definitely on Blazor, and its potential to provide a great development experience that scales effectively and provides the features your applications need. And Daniel reminds us that the teams all work closely together, including the broader .NET and language teams, so new features are in the right place and available to everyone!

"As Communities Unite through music, we can rebuild hope"Richard Allen returns to discuss the upcoming Silver Coast fundraiser... No one can fail to have been shocked by the images of the devastation that was left by a series of storms this winter. Weeks on, and as the rains ease, there are still families without a roof over their head, farmers without livestock, businesses without premises, and plenty still needing help. But non-profit organisation from Caldas da Rainha that has been assisting on the frontline will have its efforts boosted by a benefit concert this month being headlined by Portugal's number one Beatles tribute act.Musicians, volunteers, charities and businesses from across the local area will all have a part to play as internationally acclaimed group The Peakles take top billing at “Comunidades Unidas: TempestAID” on Sunday March 22nd near Óbidos. The Caldas based not-for-profit association Movimento Viver o Concelho (MVC) will distribute the funds raised by the event which is being co-partnered by the Associação Recreativa e Cultural Amigos de Capeleira e Navalha (ARCACEN). Concert co-ordinator Steve Poole explains “having seen the challenges faced by local organisations to get practical support mobilised in the worst affected towns and villages in the region, we saw an opportunity to help through one musical event that could make a real difference. The partnership between ARCACEN and MVC means that we have great facilities to hold an event to maximise raising funds that can be allocated quickly and transparently to where they continue to be needed the most”.MVC President Teresa Serrenho added “These storms were democratic. They didn't care for the size of the house or someone's ability to pay for repairs. They ripped through people's lives, landscapes and businesses, leaving many of them un-equipped and unable to move forward. In recent weeks we've been able to help people in practical ways for example, with construction contacts, materials and labour. These people are going to need our support for many months to come, and we are helping them to rebuild hope”.Communities Unite originated as a series of concerts in Óbidos in 2023 aimed at bringing the Portuguese and immigrant populations together through music. Co-founder and local musician Richard Allen has been reaching out to bands to perform at the gig in Capeleira and is thrilled that The Peakles are taking part: “The Peakles are the top Beatles tribute act in the country, they've toured internationally and now they're returning to Óbidos to headline a stage packed with other local talent like Voltar-N, The Four Horsemen and Jam Shack. It promises to not only be a sell-out event, but also an incredible day of music, community and generosity.”Comunidades Unidas: TempestAID takes place on Sunday 22nd March at the Associação Recreativa e Cultural Amigos da Capeleira e Navalha near Óbidos. Admission is five euros on the day.For more information search social media for Comunidades Unidas: TempestAID.For Interview opportunities with the concert organisers and MVC please whatsapp / email events@movimentoviveroconcelho.ptBecome a supporter of this podcast: https://www.spreaker.com/podcast/the-good-morning-portugal-podcast-with-carl-munson--2903992/support."The one you're thinking of is Good Morning Portugal! hosted by Carl Munson. It's an English-language live show/podcast aimed at expats (especially 50+ folks) settling into or loving life in Portugal. It's streamed live on YouTube weekdays around 8-9 AM (often with a cheerful Olá Bom Dia ALEGRIA! vibe), covering news, weather, culture, wellbeing, property tips, moving advice, and fun chats. Carl helps people buy, rent, or scout homes—contact him at +351 913 590 303 or carl@carlmunson.com if you need that. You can catch full episodes on YouTube (channel: Good Morning Portugal!), as a podcast on Spotify/Apple, and join the free Portugal Club community at theportugalclub.com for more support and connection. It's super positive, community-focused, and still going strong in 2026!" - Grok

Gros zoom sur les skills et leurs usages dans les coding agents, sur les benchmarks de stacks techniques MCP, mais aussi du Java 26-27, du HttpClient, du NodeJS, des scenarios nucléaires pilotés par l'IA, de la méthodologie, bref on ne s'ennuie pas ! Enregistré le 15 mars 2026 Téléchargement de l'épisode LesCastCodeurs-Episode-338.mp3 ou en vidéo sur YouTube. News Langages Bruno Borges a créé un site, inspiré d'un site récent qui montrait comment CSS avait évolué, qui illustre justement comment Java a bien évolué au fil du temps, et est devenu un langage encore plus élégant https://javaevolved.github.io/ Code simplifié: main() allégé, var, blocs de texte, API String enrichie. Pattern Matching: switch sur types, instanceof amélioré, record patterns. Données: Records, collections immuables faciles à créer, méthodes de listes. Concurrence: Threads virtuels, CompletableFuture, StructuredTaskScope, ScopedValue. Erreurs & Sécurité: NPE précis, catch multiples, Optional amélioré, filtres de désérialisation. I/O & Réseau: HttpClient moderne, E/S fichiers/console simplifiées, transferTo. Dates & Heures: API modernisée, précise, immutables et thread-safe. Langage: Interfaces sealed/private, import de modules, Math.clamp Streams: Nouveaux opérateurs (takeWhile, mapMulti, Gatherers, teeing). Outils & Perf: jshell, exécution simplifiée, jwebserver, AOT, JFR, optimisation mémoire. 10+ raisons de ne pas utiliser le HttpClient du JDK, avec un article très détaillé de Brice Dutheil https://blog.arkey.fr/2026/02/08/ten-reasons-to-not-use-jdk-httpclient/ JDK HttpClient: intégré, non-upgradable. OkHttp: plus lourd (dépendance Kotlin). TLS/SSL: JDK: SSLContext limité, vérif hôte globale, épinglage manuel, SSLParameters rigides. OkHttp: contrôle fin (SSLSocketFactory/TrustManager), vérif hôte/épinglage dédiés, ConnectionSpec structuré. Connexions: JDK: pas de repli, fabrique socket custom impossible (pas UDS/Named Pipes direct), pool limité (propriétés système, contrôle pauvre avant JDK 20/21). OkHttp: repli automatique, fabrique custom, pool granulaire. Réseau: JDK: résolveur DNS par défaut, Authenticator unique. OkHttp: résolveur DNS custom, authentificateurs séparés (proxy/serveur). Cycle Requêtes: JDK: pas d'intercepteurs ni API événements intégrés. OkHttp: addInterceptor, EventListener pour événements granulaires. Ressources: JDK: pas d'arrêt propre avant JDK 21. OkHttp: arrêt granulaire (pool, exécuteur, cache). Timeout: JDK: désactivé après en-têtes; le transfert du corps peut dépasser le timeout initial. JDK 26 et JDK 27 : ce qui nous attend — https://www.infoq.com/news/2026/02/java-26-so-far/ JDK 26 est une version non-LTS prévue le 17 mars 2026, avec 10 nouvelles fonctionnalités réparties en 5 catégories Le support HTTP/3 arrive enfin dans l'API HTTP Client standard de Java (JEP 517) La Structured Concurrency (projet Loom) en est à sa 6e preview, avec l'ajout d'une méthode onTimeout() sur StructuredTaskScope.Joiner Les Lazy Constants passent en 2e preview : des constantes initialisées à la demande, utiles pour optimiser le démarrage Le G1 GC gagne en performance via une réduction des synchronisations entre threads applicatifs et threads GC (JEP 522) Le cache d'objets AOT (JEP 516) est étendu pour fonctionner avec n'importe quel GC, y compris ZGC L'API Applet est définitivement supprimée (JEP 504), fermant une page historique de Java L'encodage PEM des objets cryptographiques continue sa preview avec support de chiffrement/déchiffrement de KeyPair Pour JDK 27 (septembre 2026), l'échange de clés post-quantique hybride pour TLS 1.3 est déjà ciblé (JEP 527) Project Valhalla progresse avec une preview des Value Classes : objets sans identité, à champs final uniquement Librairies Une étude de performance montre que Java est un super choix pour développer des serveurs MCP https://www.tmdevlab.com/mcp-server-performance-benchmark.html Comparaison de performances de serveurs MCP (Model Context Protocol) en Java, Go, Node.js, Python. Méthodologie: 3,9 millions requêtes, environnement Docker (1 cœur CPU, 1 Go RAM/serveur). Fiabilité: 0% d'erreurs pour toutes les implémentations. Tiers de performance: 1 (Haute): Go & Java (latence < 1ms, ~1600 requêtes/s). ▪︎ Go: Efficacité mémoire exceptionnelle (18 Mo vs 220 Mo pour Java). ▪︎ Java: Latence marginalement meilleure, mais 12x plus de mémoire. 2 (Moyenne): Node.js (latence ~10,7 ms, ~560 requêtes/s). Surcharge par instanciation. 3 (Faible): Python (latence ~26,5 ms, ~290 requêtes/s). Limité par GIL. Recommandations production: Go: Optimal forte charge, cloud-native, optimisation coûts. Java: Latence très basse critique, infrastructure Java existante. Node.js & Python: Adaptés charges modérées/faibles, développement/test. Node.js et Python peuvent être optimisés pour améliorer leurs performances en production. Et encore, en Java, le benchmark n'a pas utilisé GraalVM pour une compilation native, ce qui aurait donné des chiffres côté mémoire qui aurait concurrencé Go Qui a la meilleure perf entre Quarkus et Spring pour faire des serveurs MCP ? https://medium.com/@egekaraosmanoglu/spring-boot-vs-quarkus-which-java-runtime-wins-the-ai-mcp-tools-performance-battle-4da9d6a248d5 Quarkus JVM: Débit et latence les plus élevés (jusqu'à 16 381 req/s, 65% plus rapide que Spring Boot), surpasse Spring Boot même avec Apache Camel. Quarkus Native: Consommation mémoire la plus faible (118 MB), démarrage instantané, performance prédictible. Spring Boot MVC: Bonnes performances, écosystème mature, nécessite un "warm-up" important (jusqu'à 44% de gain). Spring Boot WebFlux: Légèrement meilleur débit et latence que MVC (~5%), mais plus de mémoire et complexité réactive. Coût architectural: MapStruct: Impact négligeable (< ±5%). Apache Camel: Réduction de débit de 8-21%, mais valeur ajoutée significative; Quarkus JVM + Camel reste > Spring Boot baseline. Protocole MCP: Sur Quarkus JVM (avec Camel), surpasse gRPC. Recommandations: Débit max: Quarkus JVM. Coût/Serverless: Quarkus Native. Intégration d'entreprise: Quarkus JVM + Camel + MapStruct. Meilleur choix Spring: Spring Boot WebFlux + MapStruct. Benchmark des stacks qui implémentent MCP https://www.tmdevlab.com/mcp-server-performance-benchmark-v2.html MCP (Model Context Protocol) est le protocole d'Anthropic pour connecter les LLMs à des outils et sources de données externes ; ce benchmark compare 15 implémentations serveur. 39,9 millions de requêtes traitées avec zéro erreur, sur des charges I/O réalistes (Redis + HTTP API) plutôt que des tâches CPU synthétiques. Rust atteint 4 845 RPS avec seulement 10,9 Mo de RAM ; Quarkus obtient 4 739 RPS avec la meilleure latence (4,04 ms en moyenne, 8,13 ms au P95). Go (3 616 RPS) et Spring MVC (3 540 RPS) constituent un second groupe solide. Node.js plafonne à 423 RPS ; Bun est 2,2x plus rapide sur un code identique (876 RPS) ; Python atteint 259 RPS avec 4 workers et uvloop. Découverte notable : un bug dans le SDK Rust rmcp v0.16 ajoutait ~40 ms de latence à toutes les réponses HTTP, limitant le débit à 1 283 RPS ; corrigé en v0.17 via la PR #683. Les images natives GraalVM réduisent la mémoire de 27 à 81 % mais dégradent le débit de 20 à 36 % ; Quarkus-native est l'exception avec 36 Mo RAM et 3 449 RPS. Spring MVC (bloquant) surpasse WebFlux (réactif) à 50 utilisateurs simultanés, rappelant que le modèle réactif n'est pas toujours gagnant. Recommandations : Rust ou Quarkus pour la production haute charge, Go pour le cloud-native, Bun plutôt que Node.js en JavaScript. Jakarta EE 12 Milestone 2 : données, cohérence et configuration https://www.infoq.com/articles/jakartaee-12-milestone-2/ Jakarta EE est la plateforme Java entreprise open-source, socle de frameworks comme Quarkus et Spring, qui standardise les APIs pour la persistance, les transactions, la sécurité, etc. Jakarta EE 12 adopte Java 21 comme baseline (avec support Java 25) et supprime définitivement le SecurityManager déprécié. La nouvelle spec Jakarta Query unifie JPQL (SQL/relationnel) et JDQL (NoSQL) en un seul langage avec deux profils : Core Language (portable) et Persistence Language (relationnel). Jakarta Data 1.1 introduit les requêtes dynamiques via une API fluente avec Restriction et l'annotation @Is pour des conditions plus expressives. Jakarta Data supporte désormais les repositories stateful, permettant la gestion du cycle de vie des entités (persist, merge, detach, refresh) comme en JPA classique. Jakarta NoSQL 1.1 intègre Jakarta Query via une nouvelle interface Query et supporte les projections avec des Java records. Jakarta Persistence 4.0 supporte SequencedCollection (Java 21) comme type de collection dans les entités. Une nouvelle spec Jakarta Agentic AI est en cours, visant des APIs vendor-neutral pour construire des agents IA sur les runtimes Jakarta EE, avec intégration prévue de LangChain4j et Spring AI. Cette release est encore un milestone (pas pour la prod) — l'adoption large dépendra de la maturité des outils (IDE, validation de requêtes, diagnostics). Nouveaux benchmarks Quarkus vs Spring Boot : performance complète et transparente https://quarkus.io/blog/new-benchmarks/ Quarkus est un framework Java optimisé pour les conteneurs, connu pour son faible usage mémoire et son démarrage rapide, concurrent principal de Spring Boot. Les anciens graphiques de performance sur quarkus.io étaient obsolètes, sans date, sans source, et ne montraient pas le débit (throughput). L'absence de données sur le throughput faisait croire à tort que Quarkus avait de mauvaises performances à ce niveau. Un nouveau benchmark open source a été créé, transparent et reproductible, disponible sur GitHub. Résultats : Quarkus gère 2,7x plus de transactions par seconde que Spring Boot, démarre 2,3x plus vite, avec deux fois moins de mémoire. Des experts Spring Boot externes ont contribué à rendre la comparaison plus équitable, notamment sur la configuration des pools de connexions. Les threads virtuels améliorent le débit d'environ 6000 tps supplémentaires pour tous les frameworks testés. Spring Boot 4 offre un meilleur débit que Spring Boot 3, mais au prix d'un démarrage plus lent et d'une empreinte mémoire plus élevée. En mode natif (GraalVM), le démarrage est ultra-rapide mais le throughput est divisé par deux, pour Quarkus comme pour Spring Boot. Le mode natif n'est recommandé que pour les applis démarrées/arrêtées très fréquemment ou à faible charge. Quarkus 3.32 : fondations pour la prochaine LTS https://quarkus.io/blog/quarkus-3-32-released/ Quarkus est un framework Java cloud-natif optimisé pour GraalVM et HotSpot, conçu pour les microservices et les environnements conteneurisés. Cette version marque le feature freeze pour la prochaine version LTS 3.33. Intégration de Project Leyden (AOT JVM) : le démarrage d'une application REST minimale passe de 370ms à 80ms. L'entraînement Leyden peut se déclencher au build ou via les tests d'intégration. Amélioration du graceful shutdown HTTP, avec des contributions de l'équipe Keycloak. Enregistrement automatique dans Consul via l'extension Stork pour la découverte de services. Nouvelles fonctionnalités de sécurité : DPoP nonce providers personnalisés, support de rich authorization pour OIDC. Possibilité de personnaliser l'ordre des mécanismes d'authentification et ajout de OIDCAuthenticationCompletionAction. Mise à jour du framework Google Cloud Functions en version 2.0, ainsi que Camel Quarkus et Quarkus CXF. Les utilisateurs sur LTS 3.27 sont encouragés à tester la migration vers 3.33 pour faire remonter des retours. NodeJS change sa cadence de releases https://nodejs.org/en/blog/announcements/evolving-the-nodejs-release-schedule Node.js est le runtime JavaScript côté serveur le plus utilisé, géré par la OpenJS Foundation avec un cycle de releases actif depuis la fusion avec io.js il y a dix ans. À partir de Node.js 27 (octobre 2026), le projet passe d'une release majeure tous les six mois à une seule par an. Chaque release deviendra LTS, supprimant la distinction entre versions paires (LTS) et impaires (non-LTS). Un nouveau canal Alpha est introduit, permettant les changements semver-major pendant la phase de test précoce. Les phases deviennent : Alpha (6 mois, oct. à mars), Current (6 mois, avr. à oct.), LTS (30 mois), puis EOL. La durée totale de support reste de 36 mois, identique au modèle actuel. La numérotation des versions s'aligne sur l'année calendaire de la release Current (ex : 27.0.0 en 2027). La version Alpha est signée, taguée et testée via CITGM, mais n'est pas destinée à la production. La motivation principale : les versions impaires étaient peu adoptées, la distinction pair/impair perturbait les débutants, et réduire les lignes de release parallèles allège la charge des bénévoles. Les auteurs de bibliothèques sont encouragés à intégrer les releases Alpha dans leur CI dès que possible pour détecter les régressions en amont. Web jQuery v4 est sorti https://www.infoq.com/news/2026/02/jquery-4-release/?utm_source=twitter&utm_medium=link&utm_campaign=calendar jQuery est une bibliothèque JavaScript historique qui simplifie la manipulation du DOM, la gestion des événements et les requêtes AJAX, encore très présente dans de nombreuses bases de code. Cette version majeure sort pour les 20 ans de la bibliothèque, après presque une décennie sans version majeure. Suppression du support d'Internet Explorer 10 et antérieur, Edge Legacy et les anciennes versions iOS/Android. IE11 reste encore supporté dans jQuery 4, mais sa suppression est prévue pour jQuery 5. Le code source migre d'AMD vers les ES modules, pour une meilleure compatibilité avec les outils de build modernes. Le bundler passe de RequireJS à Rollup. Suppression des fonctions dépréciées comme jQuery.isArray, jQuery.parseJSON et jQuery.trim, désormais disponibles nativement en JavaScript. Le fichier gzippé gagne plus de 3 000 octets ; le build slim descend à environ 19,5 ko. Ajout du support des Trusted Types pour faciliter la compatibilité avec les Content Security Policy strictes. jQuery reste pertinent pour la maintenance de bases de code existantes et les projets nécessitant une faible dépendance aux frameworks. La réactivité en frontend : concepts et approches https://www.sfeir.dev/front/quest-ce-que-la-reactivite-en-frontend/ Un article qui resume comment la reactivite est implementee en front web La réactivité en frontend désigne le mécanisme qui permet de mettre à jour automatiquement l'UI quand les données changent, sans manipulation directe du DOM. Sans réactivité, les développeurs doivent mettre à jour manuellement chaque élément de l'interface, ce qui est fastidieux et source d'erreurs. Le data binding unidirectionnel (React) distingue le flux de données des callbacks d'interaction utilisateur. Le data binding bidirectionnel (Angular) synchronise automatiquement données et UI dans les deux sens. Le Virtual DOM (React, Vue) compare une représentation en mémoire avec le DOM réel avant d'appliquer uniquement les changements nécessaires. Les observables via RxJS (Angular) permettent de gérer des flux de données asynchrones et des événements complexes. Les signaux (SolidJS, Angular récent, Svelte) offrent des mises à jour granulaires et de meilleures performances que les approches précédentes. Les signaux proposent une API plus simple que les observables tout en restant très performants. La réactivité abstrait la manipulation du DOM et permet aux développeurs de se concentrer sur l'état de l'application. Data et Intelligence Artificielle Gunnar Morling a annoncé la sortie de Hardwood, un nouveau parseur Java pour les fichiers Apache Parquet, grâce aux leçons apprises par le 1BRC challenge https://www.morling.dev/blog/hardwood-new-parser-for-apache-parquet/ Hardwood : Nouveau parseur Apache Parquet open-source (Java 21+). But : Dépasser parquet-java (dépendances lourdes, lecteur mono-threadé). Points clés : Dépendances minimes, pipeline de décodage multi-threadé. APIs : RowReader (ligne) et ColumnReader (colonne, haute perf.). Optimisations : Parallélisme pages, préchargement adaptatif, moins d'allocations. Développement : Assisté par IA (Claude Code), révision humaine. Futur : "Predicate push-down", compatibilité parquet-java, écriture, CLI, intégration Iceberg. Apicurio Registry passe AI-Native — https://www.apicur.io/blog/2026/02/05/apicurio-registry-ai-natural-evolution Apicurio Registry est un registre open-source de schemas (OpenAPI, AsyncAPI, Avro, Protobuf…) gérant versioning, validation et gouvernance des APIs. Le projet étend ses capacités pour devenir une plateforme native AI, en appliquant les mêmes principes de gouvernance aux agents IA. Support du protocole A2A (Agent-to-Agent) : les agents s'enregistrent via des "Agent Cards" et se découvrent mutuellement via des endpoints standardisés. Un serveur MCP intégré permet aux LLMs d'interagir directement avec le registre (découverte de schémas, validation, création). L'intégration avec Claude Desktop est déjà documentée, permettant de gérer les artefacts en langage naturel. Deux nouveaux types d'artefacts : PROMPT_TEMPLATE (templates de prompts versionnés avec variables) et MODEL_SCHEMA (validation des entrées/sorties des agents). Les SDKs Java (LangChain4j, Quarkus) et Python (LangChain, LlamaIndex) sont disponibles. Une démo multi-agents illustre le "context chaining" : chaque agent reçoit les sorties des agents précédents dans la pipeline. La roadmap prévoit : gestion du cycle de vie des agents, recherche sémantique, intégration dans les pipelines de déploiement. L'Histoire du Deep Learning : quand les machines ont commencé à apprendre https://blog.ippon.fr/2026/02/20/lhistoire-du-deep-learning-quand-les-machines-ont-commence-a-apprendre/ un article qui retrace les avancées clées du machine learning Le deep learning est un sous-domaine du ML basé sur des réseaux de neurones empilés en couches, aujourd'hui omniprésent dans la vision, le langage et la recommandation. Le Perceptron (1957) est le premier modèle formel d'apprentissage supervisé, mais il échoue sur des problèmes non linéaires comme le XOR : une limite structurelle, pas algorithmique. La rétropropagation du gradient (années 80) permet d'entraîner des réseaux multi-couches, mais souffre du problème de "vanishing gradient" qui bloque l'apprentissage en profondeur. L'essor du deep learning dans les années 2000 est autant une révolution matérielle qu'algorithmique : les GPU, conçus pour le jeu vidéo, se révèlent parfaitement adaptés aux calculs matriciels. AlexNet (2012) marque une rupture industrielle en démontrant qu'un CNN profond entraîné sur GPU surpasse largement les méthodes classiques en reconnaissance d'images. Les LSTM (1997) résolvent les problèmes de mémoire à long terme des RNN, mais leur nature séquentielle limite fortement la parallélisation. Les Transformers ("Attention Is All You Need", 2017) révolutionnent le domaine en remplaçant la récursion par un mécanisme d'attention parallélisable, adaptable aux GPU et TPU. L'IA générative introduit une rupture conceptuelle : les modèles apprennent la distribution des données pour en produire de nouveaux exemples, et non plus simplement classifier. Les LLM offrent un socle généraliste réutilisable pour de nombreuses tâches, là où l'IA prédictive nécessitait un modèle spécifique par problème. La question de l'AGI reste ouverte et très incertaine, mais l'IA devient déjà un "acteur logiciel" capable de raisonner et d'agir de manière autonome via les agents. Ca y est, Agent to Agent Protocol (A2A) est sorti en version 1.0 https://a2a-protocol.org/latest/announcing-1.0/ Prêt pour la prod Support multi-version ( multi-protocoles (gRPC, HTTP+JSON…) Multi-tenancy : un même endpoint peut supporter et exposer plusieurs agents distincts Agent Cards signées et vérifiables cryptographiquement pour vérifier l'identité des agents Flexibilité : les clients peuvent choisir de consommer les résultats par polling, streaming, ou également webhooks Outillage Le guide complet pour créer des skills pour vos agents, par Anthropic https://resources.anthropic.com/hubfs/The-Complete-Guide-to-Building-Skill-for-Claude.pdf Définition et structure : Les skills sont des dossiers contenant des instructions (fichier SKILL.md obligatoire) et des scripts qui enseignent aux agents comment exécuter des tâches spécifiques ou utiliser des outils MCP de manière fiable. Fonctionnement technique : Le système repose sur la "divulgation progressive" via un en-tête YAML critique, permettant à Claude de charger le contexte de la compétence uniquement lorsque la demande de l'utilisateur le nécessite. Cycle de vie : Le guide couvre toutes les étapes de développement, de la définition des cas d'usage (automatisation, création de documents) aux protocoles de test et de distribution. il couvre aussi comment tester (brievement) et des patterns communs Apprendre a utiliser les skills pour structurer son code ia https://philippart-s.github.io/blog/2026-02-18-anthropic-skills/ Les Skills Claude sont des packages d'instructions dans un dossier enseignant à Claude comment gérer des tâches spécifiques de façon cohérente. Un skill se compose au minimum d'un fichier SKILL.md avec un frontmatter YAML et des instructions en Markdown. Le frontmatter YAML impose deux champs obligatoires : name (en kebab-case) et description (max 1024 caractères expliquant quoi faire et quand le déclencher). Les skills fonctionnent de façon identique sur Claude.ai, Claude Code et l'API sans modification. Trois catégories principales : création de documents/assets, automatisation de workflows multi-étapes, et amélioration d'intégrations MCP. Les skills s'appuient sur le principe de divulgation progressive : frontmatter toujours chargé, corps du SKILL.md si pertinent, fichiers liés à la demande. Cinq patterns courants : orchestration séquentielle, coordination multi-MCP, raffinement itératif, sélection d'outils contextuelle, intelligence métier embarquée. Les tests doivent couvrir le déclenchement (90% des requêtes pertinentes), le fonctionnel et la comparaison avec la baseline sans skill. Pour la distribution, héberger sur GitHub avec un README séparé du dossier du skill (pas de README.md dans le dossier lui-même). Un skill-creator officiel permet de générer un premier SKILL.md en 15-30 minutes à partir d'une description en langage naturel. Les skills pour les agents, c'est une façon d'automatiser des tâches répétitives https://glaforge.dev/posts/2026/02/21/easily-build-a-local-mcp-server-in-java-with-a-skill-in-gemini-cli/ Construction facile de serveurs MCP Java locaux pour Gemini CLI et autres agents. Solution au code Java répétitif : JBang + LangChain4j + un "skill" utilisé par Gemini CLI. Idée clée : Une "skill" pour Gemini CLI automatise génération et installation des serveurs. La "skill" génère un fichier Java, le compile et l'enregistre dans les paramètres de Gemini CLI. Avantages : Élimine le boilerplate, enregistrement automatique, développement rapide. Conclusion : Les "skills" d'agent automatisent les tâches répétitives et systématisent l'expérimentation. Un SKILL.md par Julien Dubois pour permettre aux agents IA de créer des projets Spring en suivant les bonnes pratiques à la JHipster https://github.com/jdubois/dr-jskill/blob/main/SKILL.md Dr JSkill est une "Agent Skill" conçue pour aider les IA (GitHub Copilot CLI, Claude Code) à générer des applications Spring Boot 4.x selon les meilleures pratiques de Julien Dubois. Permet de créer des projets full-stack modernes utilisant Java 25, PostgreSQL et Docker, avec un choix de frameworks front-end (Vue.js par défaut, React, Angular ou Vanilla JS). Intègre des scripts Node.js multiplateformes pour automatiser la génération de projets via start.spring.io sans dépendances npm externes. Préconise des choix technologiques stricts : Maven uniquement, pas de Lombok, et utilisation de Hibernate ddl-auto pour la gestion du schéma (pas de Flyway/Liquibase). Supporte nativement la compilation GraalVM (images natives) pour des démarrages ultra-rapides (

Guest host Klem and Harvey discuss the 2026 NFHS Baseball Rules Changes. Kevin Weber will return in the near future.Kevin has been umpiring since his high school days, however, he's been working consistently in amateur baseball since 2006. His story is the tale of what umpire camps and perseverance can accomplish. Kevin demonstrates that the umpire camp route is an alternative to the professional umpire school path. His road to success has been through self-study, camps, and clinics, most notably Bruce Doane's camps. Kevin has attended the Doane February camp, 2-man advanced camp, and 3-man camp on multiple occasions. He also attended the CBUA 4-Man Invitation Clinic twice. Kevin has worked high school (MHSAA), JUCO (MCCAA), NAIA (WHAC/Crossroads), and NCAA Division I (MAC) (Horizon) (MVC), II (GLIAC), and III (MIAA) contests. He's also worked Big Ten Conference non-con games along with MAC and Horizon League series, and MVC non-con games. Kevin has worked the GLIAC NCAA DII Conference tournament and three NCAA Division III Regionals and one NCAA Division III Super Regional. Kevin has worked the NJCAA Division III, Region 12 Tournament, and the MIAA Tournament on multiple occasions. Additionally, Kevin has worked the MHSAA State Finals three times (2015, 2019, & 2023). He is always trying to hone his umpire skills to continue moving up the umpiring ladder. Kevin took on an assigner role, assigning varsity MHSAA baseball games for the West Michigan Umpire Association. He also assigns junior college baseball for the MCCAA. Additionally, Kevin assigns tournament and travel team games for the BATL/USSSA. He is happily married, has one daughter, and teaches high school Social Studies and English in Grand Rapids, Michigan.

Northern Iowa is going dancing again!

Tom Ackerman gives an in-depth update from the St. Louis Cardinals' spring training in Florida, highlighting the newly renovated facilities, early season player evaluations, and standout performances. He also touches on SLU's challenging basketball losses, the importance of the MVC tournament for NCAA bids, and updates on the Blues' rebuilding progress, offering context on team dynamics, injuries, and prospects. Hashtags: #TomAckerman #Cardinals #SpringTraining #SLUBasketball #MVCTournament #BluesRebuild #SportsUpdate #MLB #CollegeBasketball #NHL

Welcome to The Daily Juice Podcast presented by Hard Rock Bet, your source for daily sports betting picks, college basketball bets, UFC plays, and the best bets today. Each episode delivers quick analysis and actionable wagers across the biggest games on the board. Today’s Daily Juice picks include SEC college basketball, MVC action, and a UFC moneyline parlay, breaking down key matchups and totals bettors should watch. The Daily Juice gives bettors sharp insight, line movement discussion, and the top picks across college basketball, UFC, NBA, and more. Subscribe for daily betting picks, sports betting strategy, and best bets every day from the Daily Juice presented by Hard Rock Bet. Topics Covered: College Basketball Betting Picks SEC Basketball Picks Missouri Valley Conference Betting UFC Betting Picks Sports Betting Best Bets Today Make sure to subscribe and turn on notifications so you never miss the Daily Juice betting card. #SportsBetting #BestBets #CollegeBasketballPicks #UFCPicks #BettingPicks #DailyJuiceSee omnystudio.com/listener for privacy information.

Please consider supporting the show on Patreon! You can also click here to join the free Discord server or connect with the show on Bluesky and Instagram!"Legend tells of an ancient artifact that can grant a woman's wish..."Fighting Game February comes to a close with Skullgirls, the indie fighter—excuse me, the handdrawn indie fighter, put some respect where it's due—that takes inspiration from fighting games, comics, and old-school movies alike. Mikey Tabletop (0-2 Heroes Podcast) joins as co-host to talk about why this game deserves more love than it gets. Between the gorgeous animation, the attention paid to competitive mechanics, and a soundtrack that's closer to "good jazz" than most games get (you too, New Vegas, sorry), it's easy to gush over Skullgirls. It's not all pleasantries though, as this game has been in the spotlight many a time for reasons less than admirable. All of this and more, to bring February to a close. Hope you love the show today. Enjoy!Skullgirls Origins story modeSkullgirls canonical(ish) timelineInsaneintherain YouTube channelThank you for listening! Want to reach out to PPR? Send your questions, comments, and recommendations to pixelprojectradio@gmail.com! And as ever, any ratings and/or reviews left on your platform of choice are greatly appreciated!

Know what you call a group of Panthers? A claw.Know what we call our group of calls of the game for Panther Women's Basketball? Claw Calls of course.Hear game highlights plus post-game thoughts from Head Coach Tanya Warren, Ryley Goebel and Taryn Wharton.The UNI Panthers won their final two regular season MVC games. UNI beat Indiana State on the road 92-73, then returned home and secured a season finale win 65-58 over Drake. Jenna Twedt led five Panthers in double figures with 21 against Indiana State. Twedt kept her roll going the next game with another 20 point effort in the win over Drake. All UNI women's basketball games can be heard locally on 106.5 FM Corn Country and anywhere via the Varsity Network App.This is the Panther Point of View, your source for all things Panthers. Listen on:Apple PodcastsSpotifyAnd MORE! Follow UNI Athletics onXFacebookInstagramYouTube Follow the Voice of Panther Volleyball and WBB Chris Kleinhans-Schulz:XSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Know what you call a group of Panthers? A claw.Know what we call our group of calls of the game for Panther Women's Basketball? Claw Calls of course.Hear game highlights plus post-game thoughts from Head Coach Tanya Warren, Jenna Twedt and Maren Schmotzer.The UNI Panthers swept a pair of MVC home games over the past week. UNI beat Valpo 92-54 then followed it up with an 82-68 win over UIC. Four Panthers scored in double figures against the Beacons, led by Elise Jaeger with 16. Taryn Wharton paced the cats vs the Flames with 22 points, 3 assists and 3 rebounds. All UNI women's basketball games can be heard locally on 106.5 FM Corn Country and anywhere via the Varsity Network App.This is the Panther Point of View, your source for all things Panthers. Listen on:Apple PodcastsSpotifyAnd MORE! Follow UNI Athletics onXFacebookInstagramYouTube Follow the Voice of Panther Volleyball and WBB Chris Kleinhans-Schulz:XSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Know what you call a group of Panthers? A claw.Know what we call our group of calls of the game for Panther basketball? Claw Calls of course.Hear game highlights and postgame thoughts from HC Ben Jacobson and Trey CampbellThe UNI Panthers lost a one possession game to MVC rival Illinois State 71-69 on Wednesday night. Trey Campbell, Ben Schwieger and Will Hornseth all paced the Panthers with 13 points. UNI closes the regular season with a 2pm tip time at Drake.This is the Panther Point of View, your source for all things Panthers. Listen on:Apple PodcastsSpotifyAnd MORE! Follow UNI Athletics onXFacebookInstagramYouTube Follow the Voice of the Panthers JW Cox on:Instagram See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Know what you call a group of Panthers? A claw.Know what we call our group of calls of the game for Panther Women's Basketball? Claw Calls of course.Hear game highlights plus post-game thoughts from Head Coach Tanya Warren and Kaylynn Janes.The UNI Panthers split a pair of MVC games over the past week. UNI won on the road at Southern Illinois 77-48, then lost in overtime at Evansville 64-63. Jenna Twedt and Ryley Goebel both posted 20 point games in the win over SIU, then put up 18 and 23 respectively to lead the way in the loss vs Evansville. All UNI women's basketball games can be heard locally on 106.5 FM Corn Country and anywhere via the Varsity Network App.This is the Panther Point of View, your source for all things Panthers. Listen on:Apple PodcastsSpotifyAnd MORE! Follow UNI Athletics onXFacebookInstagramYouTube Follow the Voice of Panther Volleyball and WBB Chris Kleinhans-Schulz:XSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Know what you call a group of Panthers? A claw.Know what we call our group of calls of the game for Panther basketball? Claw Calls of course.Hear game highlights and postgame thoughts from HC Ben Jacobson and Tristan SmithThe UNI Panthers lost a hotly contested MVC matchup with SIU, 59-57 on Saturday night. Treu Campbell led the way for UNI with 16 points, Will Hornseth chipped in 14, and Tristan Smith had 8. The Panthers return to action in the McLeod Center Wednesday night at 6pm against Illinois State.This is the Panther Point of View, your source for all things Panthers. Listen on:Apple PodcastsSpotifyAnd MORE! Follow UNI Athletics onXFacebookInstagramYouTube Follow the Voice of the Panthers JW Cox on:Instagram See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Wichita State is recognizing three MVC champions during Saturday’s basketball game vs. Temple (5 p.m.). We chatted with two members from each team – Ed Southern and Steve Kalocinski from the 1976 Shockers, Ryan Martin and Kyle Wilson from 2006 and J.R. Simon and Evan Wessel from the 2016 team. Southern reveals that a chance … Continue reading "Roundhouse podcast with MVC champions – 1976, 2006, 2016"

1. Gobernadora niega amenazas del PNPpor bonos en la CEE2.  Arrancala reorganización del PNP más de un año después de las elecciones. El procesocomienza con los pueblos en los que no prevaleció la Palma en los pasadoscomicios3. Jueza federal concede restriccióntemporera y prohíbe el traslado de un inmigrante dominicano detenido en PuertoNuevo4. Familiares de Viqueira reclamanjusticia y piden que se investigue al juez5. Miles de abonados en el áreametropolitana permanecen sin el servicio de agua6. Que lo encierren y boten la llave:Fiscalía alega patrón de “grooming” de exmiembro de MVC contra menores7.  Muere lahistoriadora Ivonne Acosta Lespier, autora de “La Mordaza”8. Cerca de la mitad de todos losestadounidenses describen al presidente Trump como “corrupto”, “racista” y“cruel” en una nueva encuesta llena de advertencias para los republicanos enlas elecciones de medio termino 9. El Congreso de Perú destituye alpresidente interino José Jerí, en un nuevo episodio de la inestabilidadpolítica que atraviesa el país, que ha tenido siete jefes de Estado en losúltimos diez años. 10.            Hillary Clinton acusa al Dept. deJusticia de Trump de encubrir los archivos de Epstein 11.            Nigeria emite advertencia sobre elreclutamiento ilegal de sus ciudadanos para la guerra de Rusia en Ucrania Este es un programa independiente y sindicalizado. Esto significa que este programa se produce de manera independiente, pero se transmite de manera sindicalizada, o sea, por las emisoras y cadenas de radio que son más fuertes en sus respectivas regiones. También se transmite por sus plataformas digitales, aplicaciones para dispositivos móviles y redes sociales.  Estas emisoras de radio son:1.    Cadena WIAC - WYAC 930 AM Cabo Rojo- Mayagüez2.    Cadena WIAC – WISA 1390 AM Isabela3.    Cadena WIAC – WIAC 740 AM Área norte y zona metropolitana4.    WLRP 1460 AM Radio Raíces La voz del Pepino en San Sebastián5.    X61 – 610 AM en Patillas6.    X61 – 94.3 FM Patillas y todo el sureste7.    WPAB 550 AM - Ponce8.    ECO 93.1 FM – En todo Puerto Rico9.    WOQI 1020 AM – Radio Casa Pueblo desde Adjuntas 10. Mundo Latino PR.com, la emisora web de música tropical y comentario Una vez sale del aire, el programa queda grabado y está disponible en las plataformas de podcasts tales como Spotify, Soundcloud, Apple Podcasts, Google Podcasts y otras plataformas https://anchor.fm/sandrarodriguezcotto También nos pueden seguir en:REDES SOCIALES:  Facebook, X (Twitter), Instagram, Threads, LinkedIn, Tumblr, TikTok BLOG:  En Blanco y Negro con Sandra http://enblancoynegromedia.blogspot.com  SUSCRIPCIÓN: Substack, plataforma de suscripción de prensa independientehttps://substack.com/@sandrarodriguezcotto OTROS MEDIOS DIGITALES: ¡Ey! Boricua, Revista Seguros. Revista Crónicas y otrosEstas son algunas de las noticias que tenemos hoy En Blanco y Negro con Sandra. 

Bill Capaldo Joins Trent after Iowa State's big win over Houston, Bracket talk with Dave Ommen & a look at the MVC with Adam Emmenecker

Bill Capaldo Joins Trent after Iowa State's big win over Houston, Bracket talk with Dave Ommen & a look at the MVC with Adam Emmenecker

PODCAST LAS NOTICIAS CON CALLE DE 16 FEBRERO DE 2026 - Gobernadora no pidió a Hacienda investigar traqueteo de centro de inspección de la secretaria de Vivienda Pelosi empuja a Gavin Newsom para presidente - Axios No hay microchips en el mundo, Google, Open Ai, Tesla, Cisco, Amazon y otros anuncian que no hay suficientes - Bloomberg 2-3 tasas de café baja posibilidad de demencia tras estudio de 130 mil personas - Harvard Trump empuja plan de 5 billones para Gaza - Economist Jefe de la policía dice que necesita 3 mil policías - El Vocero El crimen de haber autorizado comida ultra procesada es bestial dice ex jefe de la FDA - CBS 60 Minutes Jadhiel Cedeño Gómez el candidato de MVC que desgració al partido con cargo de explotación sexual infantil - El Vocero   Mucha gente debe dinero, pero no llegan a 90 días de deudas dice informe de atraso hipotecario, carros - El Vocero Se quedaron con las ganas las instituciones sin fines de lucro tras quitarle 350 millones federales para energía renovable y darla a Gas Natural de la gobernadora- El Nuevo DíaPiden que para poder sancionar a abogados tengan que los querellantes tener legitimación activa - El Nuevo Día Pelea entre Miguel Romero y la AAA continúa, pero la AAA dice que es que ahora están arreglando cosas permanentemente - El Nuevo Día Bad Bunny se ofreció a pagar el seguro de Lindor y de Correa, confirman los dos - El Nuevo DíaJunta dice que no puede aprobar contrato de Power Expectations por energía temporera no es un contrato que se pueda confiar en los datos presentados - El Nuevo Día Nos quedamos otra vez sin SNAP - El Nuevo DíaProyectos contributivos siguen detenidos, aunque siguen anunciando - El Nuevo Día Bajan las bodas en 30%, pero la industria sigue trayendo gente de fuera a casarse en PR - El Nuevo Día3 millones más para Baños de Coamo a ver si ahora sí los arreglan - El Nuevo Día Wanda Vázquez logra nuevo break, Supremo le da tiempo - Primera Hora6 asesinatos en el weekend - Primera Hora Hay momentos en los que no necesitas solo respuestas sino tranquilidad y apoyo. En Universal Group combinamos tecnología avanzada con el Toque Humano que te da calma y te responde al instante. Universal: Auspiciador oficial del equipo de Puerto Rico en el World Baseball Classic.Incluye auspicio 

Esta semana fue oficialmente Ciary Week.Analizamos lo último que ocurrió al cierre de la semana con la Secretaria de la Vivienda Ciary Pérez Peña, la defensa pública de la gobernadora, el referido del DTOP a Justicia y las contradicciones en la narrativa oficial. Desmenuzamos la carta de multas al taller, quiénes estuvieron en la reunión de transacción que bajó la cantidad a $25,000 y cómo se reabrió el centro de inspección luego de ese encuentro.También hablamos del contrato de los centros y si ahí realmente está la raíz de todo este revolú.En el chit chat discutimos el arresto de un integrante de la juventud del MVC por pedofilia y lo que eso implica políticamente.Y sí… hablamos del hermano de Ciary, pero sólo en el Patreon.Descarga la canción de Ciary y otros éxitos de DJ San Ghibli en https://open.spotify.com/artist/501D5ir53CTV41z0NYjm94Esta semana fue oficialmente Ciary Week.Analizamos lo último que ocurrió al cierre de la semana con la Secretaria de la Vivienda Ciary Pérez Peña, la defensa pública de la gobernadora, el referido del DTOP a Justicia y las contradicciones en la narrativa oficial. Desmenuzamos la carta de multas al taller, quiénes estuvieron en la reunión de transacción que bajó la cantidad a $25,000 y cómo se reabrió el centro de inspección luego de ese encuentro.También hablamos del contrato de los centros y si ahí realmente está la raíz de todo este revolú.En el chit chat discutimos el arresto de un integrante de la juventud del MVC por pedofilia y lo que eso implica políticamente.Y sí… hablamos del hermano de Ciary, pero sólo en el Patreon.Descarga la canción de Ciary y otros éxitos de DJ San Ghibli en https://open.spotify.com/artist/501D5ir53CTV41z0NYjm94-

Murray St vs. Indiana St College Basketball Pick Prediction by Tony T. Murray St vs. Indiana St Profiles Murray St at Indiana St 7PM ET—Murray St has a mark of 18-8 on the year and 10-5 in the Missouri Valley with road wins against Valparaiso, Illinois Chicago, Evansville as well as Southern Illinois. Losses on the road came against Drake, Northern Iowa and Belmont. Indiana St is 10-15 with 3-11 in the MVC with home losses against Bradley, Evansville, Drake and Valparaiso. They won at home against Belmont and Illinois St.

Know what you call a group of Panthers? A claw.Know what we call our group of calls of the game for Panther Women's Basketball? Claw Calls of course.Hear game highlights plus post-game thoughts from Head Coach Tanya Warren and Kaylynn Janes.The UNI Panthers lost a pair of MVC games, on the road at Bradley and home against Belmont this past week. Ryley Goebel scored in double figures in both games, while Jenna Twedt put up 15 in game two against Belmont. All UNI women's basketball games can be heard locally on 106.5 FM Corn Country and anywhere via the Varsity Network App.This is the Panther Point of View, your source for all things Panthers. Listen on:Apple PodcastsSpotifyAnd MORE! Follow UNI Athletics onXFacebookInstagramYouTube Follow the Voice of Panther Volleyball and WBB Chris Kleinhans-Schulz:XSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Can Kansas win it all? Adam Emmenecker on the MVC & Derek Stevens, Owner of Circa on the Super Bowl & Circa Squares

Can Kansas win it all? Adam Emmenecker on the MVC & Derek Stevens, Owner of Circa on the Super Bowl & Circa Squares

Know what you call a group of Panthers? A claw.Know what we call our group of calls of the game for Panther Women's Basketball? Claw Calls of course.Hear game highlights plus post-game thoughts from Head Coach Tanya Warren, Abby Tuttle and Riley Goebel.The UNI Panthers split a pair of MVC games, losing at Illinois State, then bouncing back with a win at Drake. Riley Goebel paced the win vs Drake, posting a triple double, with 18 points, 14 rebounds and 10 blocks. All UNI women's basketball games can be heard locally on 106.5 FM Corn Country and anywhere via the Varsity Network App.This is the Panther Point of View, your source for all things Panthers. Listen on:Apple PodcastsSpotifyAnd MORE! Follow UNI Athletics onXFacebookInstagramYouTube Follow the Voice of Panther Volleyball and WBB Chris Kleinhans-Schulz:XSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Know what you call a group of Panthers? A claw.Know what we call our group of calls of the game for Panther basketball? Claw Calls of course.Hear game highlights and postgame thoughts from HC Ben Jacobson and Kyle Pock.The UNI Panthers Men's Basketball bounced back with a big win over the Evansville Purple Aces on Saturday, 71-55. UNI got a career high 21 points from Will Hornseth, a 12 point, 10 assist double double from Trey Campbell and a 10 point, 10 rebound double double from Ben Schwieger in the game. Panthers are back to even in MVC play with the win. Next up for UNI is a home game on Friday against Bradley at 7pm.This is the Panther Point of View, your source for all things Panthers. Listen on:Apple PodcastsSpotifyAnd MORE! Follow UNI Athletics onXFacebookInstagramYouTube Follow the Voice of the Panthers JW Cox on:Instagram See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Know what you call a group of Panthers? A claw.Know what we call our group of calls of the game for Panther Women's Basketball? Claw Calls of course.Hear game highlights plus post-game thoughts from Head Coach Tanya Warren, Jenna Twedt and Elise Jaeger.The UNI Panthers split a pair of home MVC games over the weekend, picking up a huge win over Murray State 89-74, then dropping a tight contest 68-65 vs Evansville. Up next, three straight on the road at Illinois State, Drake and Bradley. All UNI women's basketball games can be heard locally on 106.5 FM Corn Country and anywhere via the Varsity Network App.This is the Panther Point of View, your source for all things Panthers. Listen on:Apple PodcastsSpotifyAnd MORE! Follow UNI Athletics onXFacebookInstagramYouTube Follow the Voice of Panther Volleyball and WBB Chris Kleinhans-Schulz:XSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Baker and Vance discuss the Field of 68 best jobs rankings and the most recent conference game. Jeff Bidwell, play-by-play for the Murray State Racers, joins us to talk the hot start and the MVC as a whole. Banter & News (0:28)Power Rankings & Game Recaps(17:04)Jeff Bidwell (1:00:03)Game Picks (1:31:06)Come join us for Valley Hoops Pick'em Contest. Sign-up now! Link to Pick'em Contest: ⁠⁠⁠⁠⁠Valley Hoops Pick'em⁠⁠⁠

Our crew was dispatched to a high energy, rollover MVC with a patient ejection, which usually demands aggressive trauma protocols. But what happens when the patient is equipped with a HeartMate II, a Left Ventricular Assist Device (LVAD) that pumps blood for failing hearts. The irony is that this extremely sophisticated medical device that keeps our patient alive, also precludes our team from gathering regular vital signs, like a palpable pulse or traditional blood pressure measurements. How does the team manage a trauma resuscitation when the patient's circulation is a continuous flow rather than a beat? The trick is going to back to the basics of trauma care. Listen in and find out how this case unfurled.   Interested in obtaining CE credit for this episode? Visit OnlineAscend.com to learn more. Listeners can purchase individual episode credits or subscribe to the Critical Care Review Bundle and gain access to all episode CE Credits.    We are joined by:   Chelsea Putman, FP-C     Robert Steele, RN   Click here to download this episode today! As always thanks for listening and fly safe! Hawnwan Moy MD FACEP FAEMS John Wilmas MD FACEP FAEMS Nyssa Hattaway, BA, BSN, RN, CEN, CPEN, CFRN

Know what you call a group of Panthers? A claw.Know what we call our group of calls of the game for Panther basketball? Claw Calls of course.Hear game highlights and postgame thoughts from HC Ben Jacobson.The UNI Panthers Men's Basketball team dropped an MVC road game 59-54 to the Illinois State Redbirds on Wednesday night. Ben Schweiger led the way with 15 points and 4 rebounds while Will Hornseth chipped in 10 points and 7 rebounds. Next up the Panthers host Murray State on Saturday afternoon at 3pm.This is the Panther Point of View, your source for all things Panthers. Listen on:Apple PodcastsSpotifyAnd MORE! Follow UNI Athletics onXFacebookInstagramYouTube Follow the Voice of the Panthers JW Cox on:Instagram See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

PODCAST LAS NOTICIAS CON CALLE DE 20 ENERO DE 2026 - Trump amenaza 200% de tarifas a vinos de Francia - LeMonde Sigue violencia contra manifestantes en Irán - WSJHarán censo de personas sin casa en PR - Primera Hora Fiscalía federal decide retirar todo sobre John Blakeman y Frances Díaz sobre caso de Wanda Vázquez - Primera Hora Salen huyendo millonarios de California y se van a Texas tras propuesta de impuesto a millonarios de 5% - NYTTropas de Dinamarca van a Groenlandia, pero alemanes se van porque es demasiado frío - FTCae el valor de dólar y Wall St. Pierde billones tras confrontación por Groenlandia - FTTrump también quiere ahora la isla de Diego García que pertenece a Inglaterra tras UK decir que la daría a Mauritius - Truth Social Gobierno de PR dice que para el 2030 se iría la Junta - El Nuevo Día Santurce regresa al Bithorn para ver si terminan la serie - El Nuevo Día Aprueban medida para exgobernadores convictos pierdan escoltas - El Nuevo Día Oficialmente se acabó el caso contra Wanda Vázquez y cooperadores tmb tendrán archivo - El Vocero Olvin Valentín se va de MVC para el PPD - El Nuevo DíaLegisladores y gobernadora en España - El Nuevo Día Gregorio Matías contra ley de bolsas plásticas y ley de plástico de un solo uso - El Nuevo Día Baxter reduce operaciones en Guayama PR - Departamento del Trabajo Oro sube a 4,700 la onza - Bloomberg Carlos Beltrán al salón de la fama hoy Poner o no los 10 mandamientos en las escuelas llega al Quinto Circuito de Apelaciones en Texas - Economist Tapón bestial por accidente de camión que derramó diesel por casi un kilómetro - WUNOAumentarían más personas en el negociado de energía en proyecto de ley - El Vocero Evaluarán si querellas de Proyecto Dignidad contra anuncios de la gobernadora va o no - El Vocero Pedirán pena de muerte para CDobleta por asesinato de agente de la policía - El Vocero Pelea por hospital Wilma Vázquez si van para cierre total o no - El Vocero Japón empieza problema, su nota sube a sobre 4% por primera vez de la crisis global en 2007 - Bloomberg Empieza el año Fit y Saludable con Martin's BBQ Pide tu Combo Fit1/4 de pollo, tu vianda o verdura favorita con botella de agua Martin's BBQCocinando diariamente comida  saludable, fresca y sabrosa....mmmm esto si es criollo... Entregando con Uber Eats y Doordash Sabroso y Fit!Hoy Voy Pa Martins BBQAsado, Jugoso, Sabroso.Incluye auspicio 

Know what you call a group of Panthers? A claw.Know what we call our group of calls of the game for Panther basketball? Claw Calls of course.Hear game highlights and postgame thoughts from HC Ben Jacobson.The UNI Panthers Men's Basketball team dropped an MVC road game 54-44 to the Valparaiso Beacons on Saturday night. Ben Schweiger led the way with 10 points and 4 rebounds while will Hornseth chipped in 8 points and 8 rebounds. Next up the Panthers visit Illinois State on Wednesday night at 8pm.This is the Panther Point of View, your source for all things Panthers. Listen on:Apple PodcastsSpotifyAnd MORE! Follow UNI Athletics onXFacebookInstagramYouTube Follow the Voice of the Panthers JW Cox on:Instagram See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Baker and Vance discuss the most recent conference game. Vance discusses MVC officiating with the Coordinator of Officials Eddie Jackson.Banter (0:28)Power Rankings & Game Recaps(9:05)Eddie Jackson (47:09)Game Picks (1:46:35)Player of the Year Draft Update (1:52:27)Come join us for Valley Hoops Pick'em Contest. Sign-up now! Link to Pick'em Contest: ⁠⁠⁠⁠Valley Hoops Pick'em⁠⁠

Know what you call a group of Panthers? A claw.Know what we call our group of calls of the game for Panther basketball? Claw Calls of course.Hear game highlights and postgame thoughts from HC Ben Jacobson and Trey Campbell.The UNI Panthers Men's Basketball team dropped a home MVC contest 69-61 to the UIC Flames on Tuesday night. Trey Campbell scored a season high 21 points in the game. Next up, the Panthers travel to Valparaiso for a 2pm tip time on Saturday afternoon.This is the Panther Point of View, your source for all things Panthers. Listen on:Apple PodcastsSpotifyAnd MORE! Follow UNI Athletics onXFacebookInstagramYouTube Follow the Voice of the Panthers JW Cox on:Instagram See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Know what you call a group of Panthers? A claw.Know what we call our group of calls of the game for Panther Women's Basketball? Claw Calls of course.Hear game highlights plus post-game thoughts from Head Coach Tanya Warren and Ryley Goebel.The UNI Panthers suffered their first two MVC losses over the weekend at Murray State and Belmont. UNI is back home to continue conference play on Sunday at home against Bradley at 2pm. All UNI women's basketball games can be heard locally on 106.5 FM Corn Country and anywhere via the Varsity Network App.This is the Panther Point of View, your source for all things Panthers. Listen on:Apple PodcastsSpotifyAnd MORE! Follow UNI Athletics onXFacebookInstagramYouTube Follow the Voice of Panther Volleyball and WBB Chris Kleinhans-Schulz:XSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Iowa falls at Minnesota, Bears/Packers Playoff Matchup, Adam Emmenecker on the MVC & Mitch Holthus puts a bow on the Chiefs Season

On this episode of the Hometown Hoops Podcast, the Voice of the Murray State Racers, Jeff Bidwell, joins the show to preview Bulldogs vs. Racers and the beginning of MVC play.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

The Seahawks needed some clutch kicks, late game clock management and special teams prowess to pull ahead for the win and push their record to an impressive 11-3. We take a look at some of the critical moments, and standout performances. Nick Emmanwori's effort was on display again as he made some key tackles and provided a tribute to Kam Chancellor. The Seahawks had one key fourth down conversion in the game. Which player provided some key effort to help ensure Seattle was able to move into field goal range? Zach Charbonnet looked to be the best of the two backs on the field this week when running the ball, but what about his prowess in pass protection? Stay tuned through the INs and OUTs this week to find out which player won the coveted (and very real) MVC trophy. Join our  Sea Hawkers Podcast Pickem League - free prizes for weekly winners. Support the show Get in the Flock! Visit GetInTheFlock.com Or visit our website for other ways to support the show Subscribe via: Apple Podcasts | Spotify | Google Podcasts | YouTube | TuneIn | RSS Follow us on: Facebook | Twitter Listen on our free app for Android, iOS, Kindle or Windows Phone/PC Call or text: 253-235-9041 Find Sea Hawkers clubs around the world at SeaHawkers.org Music from the show by The 12 Train, download each track at ReverbNation  

The Seattle Seahawks kept the opposing offense out of the end zone for the second straight week. To celebrate, we're keying in on three plays by the Seattle defensive backs who helped to make it happen. From Josh Jobe protecting the sideline on an early third down to Nick Emmanwori navigating traffic for a TFL, we take a look back at the 37-9 victory. On the negative side, there were some issues with blocking. Charles Cross was nearly responsible for a safety, and a Robbie Ouzts hold contributed to a 3-and-out in the second quarter. Stay tuned to find out who Captain Destroy-O is and why he earned this week's MVC award! Join our Sea Hawkers Podcast Pickem League - free prizes for weekly winners. Support the show Get in the Flock! Visit GetInTheFlock.com Or visit our website for other ways to support the show Subscribe via: Apple Podcasts | Spotify | Google Podcasts | YouTube | TuneIn | RSS Follow us on: Facebook | Twitter Listen on our free app for Android, iOS, Kindle or Windows Phone/PC Call or text: 253-235-9041 Find Sea Hawkers clubs around the world at SeaHawkers.org Music from the show by The 12 Train, download each track at ReverbNation  

The Dubuque Area Sports Podcast sits down with Coach Wendell Eimers of the Dubuque Senior Rams for an in-depth look at one of the Mississippi Valley Conference's most exciting teams heading into the new season.Coming off a strong 17–7 campaign and a 3rd-place finish on the Mississippi side of the MVC, the Rams return their top three scorers — all seniors — while looking to fill the defensive gaps left by last year's standout stoppers.Coach Eimers breaks down the roster, including:Returning award winners and the leadership they bringReturning starters and key bench players stepping into bigger rolesPromising newcomers ready to make an impactHow the Rams plan to replace three elite defenders from last year's squadReflections on last season's growthWhat the outlook is for this year's senior-led teamA must-listen for Rams fans and MVC basketball followers — this episode brings energy, insight, and everything you need to know before Dubuque Senior hits the hardwood.

Growth tests the soul of every organization. As companies expand, consistency often replaces compassion—but CAVA proves you can scale without losing humanity. With 400 restaurants and 12,000 team members, CAVA has built a culture that's as grounded as it is consistent through a people framework rooted in heart, health, and humanity. In this episode, I sit down with Kelly Costanza, Chief People Officer of CAVA, to unpack exactly how they've done it—diving into their MVC framework (Mission, Values, and Competencies) that turns ideals into action. We explore their recognition systems like MVC Awards and Value Cards, the CCT Program that trains leaders as culture coaches, and Impact Plans that replace performance reviews with real-time growth. Kelly also shares how CAVA brings connection to life through the Love Button and Allies in Motion (AIM) programs, integrates culture across the employee lifecycle, and balances AI innovation with human warmth. This episode offers every CHRO a practical look at how to bring values to life, connect them to performance, and make culture come alive. ________________ Start your day with the world's top leaders by joining thousands of others at Great Leadership on Substack. Just enter your email: ⁠⁠https://greatleadership.substack.com/ Future-ready organizations are built, not hoped for. My latest book, -The 8 Laws of Employee Experience shows how. Preorder here: 8EXLaws.com

Hoy conversamos con Eva Prados, ex candidata al Distrito 3 de San Juan y actual Coordinadora General del Movimiento Victoria Ciudadana (MVC). Hablamos sobre su trayectoria política, las lecciones que ha aprendido tras dos campañas, su relación con el activismo, y cómo navega las tensiones entre la calle y la política partidista. También discutimos el estado actual del MVC, las críticas sobre su identidad ideológica y carisma, y el futuro de las alianzas con el PIP y otros movimientos. ¿Sigue creyendo en el proyecto original del MVC? ¿Cómo ve el panorama hacia 2028?Y, claro, respondimos varias de las preguntas enviadas por la comunidad del Patreon. Si fueras integrante de nuestro Patreon, hubieras escuchado este episodio ayer. Únete ahora en patreon.com/puestospalproblema! Presentado por