Podcasts about CSS

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

An AI assistant goes rogue and hacks a gym website, a $9k surprise Cloudflare bill lands in someone's inbox, and AI subscriptions start promising unlimited usage. Plus Meta's Muse Glimmer, Agent Plugins, Kimi K3 in Copilot, and a pile of CSS chaos. Show Notes 00:00 Welcome to Syntax! 02:30 Celld: self host distributed durable objects 07:57 $9k Cloudflare Bill 13:43 Ogygia - SSR islands for SvelteKit 18:49 Brought to you by Sentry.io 19:51 Standard Code - Unlimited Use AI Subscription 29:17 New Meta Model Muse Glimmer 36:12 AI Assistant Hacks Gym 46:49 This Week in AI 54:50 Prime Agent RLM harness 01:01:02 Agent Plugin Spec 01:04:08 Adam Wathan: A Token is a Token 01:07:39 New JS Runtime from Remix Creator 01:11:21 Lost phone found with Bluetooth meter 01:17:24 Center a div with browser sidebars 01:19:49 Flexwind froggy 01:21:55 Thanks for watching! Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

Show DescriptionHaving type two fun, email branding with BIMI, accessibility details in icons and favicons, using AI as a coding and maintenance partner, CSS @layer property, design systems, and the economics of fast AI hardware. Listen on WebsiteWatch on YouTubeLinks How and Why to Implement BIMI Selectors - BIMI Group You kinda want an orange favicon. – Chris Coyier Thinking Horizontally in CSS @layer AMD snaps up Toronto chip startup Taalas | Financial Post

Welcome to What Matters Now, a weekly podcast exploring key issues currently shaping Israel and the Jewish World, with host Amanda Borschel-Dan speaking with CEO of Community Security Service Richard Priem. While guarding his Dutch synagogue as a 17-year-old, Priem knew there were two places where Jews wouldn't experience antisemitism: Israel and the United States. Whereas in Europe, where Jews regularly must go through security checks and metal detectors before entering community events, he was sure the Jewish State and the Goldene Medina were different. That "age of security" for US Jewry changed around the time of the Pittsburgh Tree of Life shooting, he said. This is where his NGO steps in: Founded in 2007, the not-for-profit aims to empower Jewish volunteers and strengthen their communal security toolboxes to prevent attacks and de-escalate situations as they arise. As Priem, a former paratrooper in the IDF puts it, who better to preemptively ascertain something is amiss than the community regulars themselves? In this episode, we hear real-life examples of how CSS volunteers saved lives. Later, Priem lays out a hypothetical plan to secure Borschel-Dan's upcoming speaking gig in Chicago. We learn about the need for "digital hygiene" and how a force of thousands of volunteers -- and growing -- are allowing Jews to be loud and proud again. And so this week, we ask Richard Priem, what matters now. What Matters Now podcasts are available for download on Apple Podcasts, Spotify, YouTube, or wherever you get your podcasts. This episode was produced by Ari Schlacht.See omnystudio.com/listener for privacy information.

Welcome to What Matters Now, a weekly podcast exploring key issues currently shaping Israel and the Jewish World, with host Amanda Borschel-Dan speaking with CEO of Community Security Service Richard Priem. While guarding his Dutch synagogue as a 17-year-old, Priem knew there were two places where Jews wouldn't experience antisemitism: Israel and the United States. Whereas in Europe, where Jews regularly must go through security checks and metal detectors before entering community events, he was sure the Jewish State and the Goldene Medina were different. That "age of security" for US Jewry changed around the time of the Pittsburgh Tree of Life shooting, he said. This is where his NGO steps in: Founded in 2007, the not-for-profit aims to empower Jewish volunteers and strengthen their communal security toolboxes to prevent attacks and de-escalate situations as they arise. As Priem, a former paratrooper in the IDF puts it, who better to preemptively ascertain something is amiss than the community regulars themselves? In this episode, we hear real-life examples of how CSS volunteers saved lives. Later, Priem lays out a hypothetical plan to secure Borschel-Dan's upcoming speaking gig in Chicago. We learn about the need for "digital hygiene" and how a force of thousands of volunteers -- and growing -- are allowing Jews to be loud and proud again. And so this week, we ask Richard Priem, what matters now. What Matters Now podcasts are available for download on Apple Podcasts, Spotify, YouTube, or wherever you get your podcasts. This episode was produced by Ari Schlacht.See omnystudio.com/listener for privacy information.

In the tenth episode of "Under the Surface," Circling Seattle Sports' Seattle Torrent show/podcast, CSS founder and editor-in-chief Charles Hamaker is joined by Seattle Torrent goaltender Hannah Murphy! "Murph" reflects on her rookie year, the Torrent goaltender room last season, what her offseason has looked like, her excitement for the upcoming season, and more.

Former UMD and St. Scholastica defenseman Brenden Kotyk is back in Duluth, this time as the head coach for the CSS men. Hear about his playing career and his journey back to Duluth.See omnystudio.com/listener for privacy information.

Cloudflare is rolling out crypto wallets with claimable handles as identity, and a real React compiler finally landed for regular hooks-based code. Plus: OpenAI's pricing war, Vue Vapor benchmarks, GitHub's new npm malware scanning, and an active supply chain attack hitting 868 packages. Show Notes 00:00 Welcome to Syntax! 01:02 Shai Hulud is back! New Shai-Hulud announcement Attacked keyv packages 05:27 GitHub scans your npm packages for malware 06:42 Your agent has a wallet now Make your own Cloudflare wallet announcement blog post X402 payments 12:10 Yet another React compiler? Ripple.ts Inferno.js Dominic Gannaway's launch post Octane Native Script Reactivity + Rendering Benchmark 27:19 Scott switched his browser AGAIN! Dia Knock off extension 31:56 AI Mental health survey 32:29 OpenAI models are becoming cheaper? 38:49 GitHub stacked PRs finally arrived 41:48 AI video podcasts HeyGen launch post Hank Green's unhealthy AI usage 48:15 Brought to you by Sentry! 49:28 News from the TC39 meeting ECMAScript news Await dictionary TC39 Process 56:58 Qwen 3.8 01:02:31 Latest and greatest in CSS and UI libraries Foley.dev Morphicons Lucide Nucleo 8bit library CSS radar Impeccable Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

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

In the ninth episode of "Under the Surface," Circling Seattle Sports' Seattle Torrent show/podcast, CSS founder and editor-in-chief Charles Hamaker is joined by Seattle Torrent draft pick and defender Gracie Gilkyson! Gracie talks about her time at Yale, her improvement over her collegiate career, the Torrent blueline, her Kraken connections, and more!

Managing Atlassian as a Solo Admin can feel like a high-wire act, especially when your brain runs on hyperfocus. In this episode, Kythera Contreras shares how to turn Jira into the ultimate external brain for ADHD (for both work and personal projects) and how Atlassian Rovo Chat is helping write custom CSS to overhaul her artist website. From beating solo burnout to setting up dopamine-friendly Atlassian setups, Kythera drops actionable insights to help you tame the queue, streamline personal life organization, and get more done with AI.The Jira Life=====================================Having trouble keeping up with when we are live? Sign up for our Atlassian Community Group!https://ace.atlassian.com/the-jira-life/Or Follow us on LinkedIn! / the-jira-life Become a member on YouTube to get access to perks: / @thejiralife .Hosts:Alex "Dr. Jira" Ortiz / alexortiz89 / @apetechtechtutorials Rodney "The Jira Guy" Nissen / rgnissen https://thejiraguy.comSarah Wright / satwright Producer:"King Bob" Robert Wen / robert-wen-csm-spc6-a552051 Executive Producer: Lina OrtizMusic provided by Monstercat:=====================================Intro: Nitro Fun - Cheat Codes / monstercat Outro: Fractal - Atrium / monstercatinstinct

EU interior ministers close ranks behind Spain after the Ceuta migrant crisis. Then: Japan’s latest white paper on defense. Plus: we talk art with CSS singer Luisa Matsushita See omnystudio.com/listener for privacy information.

PHP Alive and Kicking – August 4, 2026 Hosts: Chris Miller (standing in solo while Mike is on holiday) Mike escaped to a beach so Chris hosts alone with special guest Derick Rethans. Expect date-time philosophy, PHP 8.6 goodies, Xdebug secrets, deprecation drama, and a heated debate about how to queue at a pub. From University Websites to Committing to PHP Derick traces his PHP origins back to his university days, building websites that needed database connectivity. ASP.NET was an option, but nobody wanted to pay for it — Linux was cool, and PHP was easy to start using. That combination hooked him early. His very first accepted contribution came from a practical need: everyone wanted centered Shockwave Flash films on their pages, back before CSS even existed. Centering meant knowing the width of a file, and while getimagesize() already existed (and still works today), it didn’t understand Flash. Derick added that support. From there he fell into bug triage, spending several years working through the issue tracker alongside Jani Taskinen (whose “Sniper” name still shows up in commit logs). For a long time it was just the two of them reproducing and fixing bugs — an important task that gets neglected easily, which is exactly how backlogs of a thousand issues and pull requests build up. The Eternal Problem of Date and Time Chris and Derick dig into why date-time bugs are so hard to triage: date algorithms are genuinely complicated, and it takes real time to figure out whether a report is a user’s mistake or an actual PHP bug. Crashes are easy to reproduce; subtle date arithmetic is not. The core philosophical question is “what does adding a month even mean?” If it’s January 31st and you add a month, PHP historically just bumps the month number, producing February 31st, which overflows to March 2nd or 3rd. But most people who add a month really just want the next month and don’t care about day counts — so “next month” is conceptually distinct from “add a month.” Derick has been brainstorming better interfaces so people can’t make these mistakes, though it’s a lot of work. They touch on Carbon as a unified interface people understand, but agree that making Carbon the language standard isn’t the right move. At the language level you need something that works for everybody and ideally doesn’t break existing code. What’s Coming in PHP 8.6 The first new time class is landing: a Duration object representing seconds and nanoseconds within a specific range, living in the Time namespace. It’s a trial run for new APIs and immediately useful — for example, passing a duration to sleep or to timeouts in the new polling API, rather than juggling raw integers. Another highlight is partial function application. With the pipe operator from 8.5, piping into anything that takes more than one argument meant wrapping it in a closure (and extra parentheses because of how the parser works). Partials let you pre-fill some arguments so the resulting callable accepts just one — perfect for pipelines. There’s also TLS session resumption support for streams, which lets OpenSSL shortcut the expensive session setup on repeated TLS connections. Bigger stream-layer work by Jakub Zelenka of the PHP Foundation is underway too, but that’s a huge job on old code and won’t make 8.6 — Chris and Derick both note the pain of keeping a year-and-a-half-long project in sync with the master branch. Xdebug in 8.6 and the Xdebug Cloud Xdebug’s recent headline feature (shipped with 8.5) is native path mapping, which lets you configure remote-to-local path mappings inside Xdebug itself instead of your IDE — handy when your code runs in Docker or on a dev machine. Feedback since release is driving quality-of-life improvements. For 8.6, relatively little is broken, though a change to how PHP reports line numbers needs untangling so debugging stops on the correct lines. Derick also has a new code-coverage implementation that gives better, more correct results at roughly a 10% speed cost. He’d rather ship correct output than fast output — and points out that PHPCov may be quicker but skips path and branch coverage entirely. The pair discuss how branch coverage doubles your test count at every branching point, and how Xdebug has a hard limit (around 64K) to avoid running out of memory on pathological code. Finally, Chris asks about Xdebug Cloud — a paid service that enables debugging where networking otherwise wouldn’t, such as remote teams sharing a single development machine (an SSH tunnel only lets one person listen on the debug port). It’s £15/month or £150/year for an individual, priced similarly to Packagist’s private packages, and helps fund Derick’s ongoing Xdebug work. He plans to do more marketing about it this year. Deprecations, Consensus, and Two-Thirds Votes Every year PHP collects a big list of deprecations — around 20 to 25 this cycle — voted on separately. Derick is more reluctant than most to approve them, arguing many offer no clear user benefit. His examples: deprecating metaphone() (whose suggested Composer replacement ironically relies on the internal function) and the dechunk filter (which can’t really be removed because HTTP streams use it internally). The list() deprecation is another sore point — Chris uses it, and the vote is tied 21–21 with one abstention, so it won’t pass under the two-thirds rule. Derick reminds everyone that “yes” needs to be twice “no.” Returning from a finally block is another candidate that makes little sense to use but hurts nothing to keep. Chris and Derick reflect on how voting was originally meant to confirm consensus reached on the mailing list, not to be the decision itself. A 50%+1 result isn’t consensus; two-thirds is the compromise, even if true 75–80% agreement would be ideal. Joe notes many deprecations are groundwork to reserve keywords for future RFCs — which raises the perennial question of how you measure real-world usage across Composer’s dependency chains. Infrastructure, the Website, and the Next Generation The PHP infrastructure has been converted to an Ansible-based repository over the last year and a half (largely by Derick, with help from Joe), replacing a wild mix of individually maintained servers — one was still running FreeBSD 4.3. They’ve also migrated to a new CDN, which brought surprises: a default one-month cache, ignoring the query string in cache keys, and even dark/light mode being an organization-wide setting rather than per-user. On the website side, everything currently lives in a single root directory of 1999-vintage code, and there’s a long-pending patch to restructure it. The PHP Foundation’s ambassadors program — with speaking, marketing, and research streams — aims to make the very techy php.net homepage speak to CTOs and newcomers about who uses PHP and why it’s a thriving project (only 31-ish years old, versus C’s 60). The conversation closes on caretakers and the next generation of contributors. Triage, they stress, doesn’t require deep internals knowledge — just reading reports to see if they still make sense is hugely valuable. Security and infrastructure access necessarily stay gatekept for trust reasons, and both agree a bus factor of one (or even two) isn’t good enough. Chris admits he’s struggling to name people who are both nice and know infra. Links from the show: Join us live in Discord — discord.phparch.com Watch live on YouTube — youtube.com/phparch PHP Tek Conference 2027 — Call for Papers now open PHP Arch Swag Store — store.phparch.com Xdebug — and Xdebug Cloud for shared debugging Magazine discount code ALIVE3 — three free months on an annual digital subscription Host: Chris Miller X: @ccmiller2018 Mastodon: @miller@phpc.social Bluesky: @ccmiller2018.bsky.social PHPArch.me: @miller Mike Page Mastodon: @MikePageDev@phpc.social PHPArch.me: @mikepagedev Streams: Youtube Channel Twitch Connect & Hire PHP Architect Website Twitter/X Mastodon Hire PHP Developers Looking to hire PHP developers? Email support@phparch.com – the team is available for consulting, infrastructure work, Ansible playbooks, and code review. Partner This podcast is made a little better thanks to our partners Displace Infrastructure Management, Simplified Automate Kubernetes deployments across any cloud provider or bare metal with a single command. Deploy, manage, and scale your infrastructure with ease. https://displace.tech/ OurCVEs Your security posture, on autopilot with OurCVEs CodeRabbit Cut code review time & bugs in half instantly with CodeRabbit. PHP Architect Consulting Your PHP codebase deserves a partner, not a contractor PHP Architect provides long-term technical partnerships for organizations that need senior-level PHP expertise that you can depend on. https://www.phparch.com/consulting/ Music Provided by Epidemic Sound https://www.epidemicsound.com/ Join Us Live Next Week Youtube Channel Got feedback? Join us on Discord at discord.phparch.com The post PHP Alive and Kicking 2026.08.04 appeared first on PHP Architect.

In the eighth episode of "Under the Surface," Circling Seattle Sports' Seattle Torrent show/podcast, CSS founder and editor-in-chief Charles Hamaker is joined by Seattle Torrent draft pick and forward Emerson Jarvis! Jarvis talks about her indigenous roots, her time at Quinnipiac, her strong senior season, the Torrent "trinket exchange," and more.

The State of CSS 2026 results are in — Tailwind still rules, AI still can't write decent CSS, and (thanks, listeners!) we made the resources list. CodePen ships its biggest update in years with CodePen 2.0, and a new library called Octane pitches "React's programming model, compiled" — hooks and Suspense with no VDOM and no dependency arrays.Timestamps0:00 - Intro3:05 - State of CSS 2026 survey20:01 - CodePen 2.032:55 - Octane JS framework38:37 - State of Devs survey 202639:30 - LinkedIn adds a "Seems like AI slop" button42:54 - TanStack rebrand, and a new charting library45:38 - GitHub stacked pull requests52:13 - Opus 554:27 - What's Making Us HappyNewsPaige: State of CSS 2026 surveyJack: Octane JS frameworkTJ: CodePen 2.0Lightning NewsState of Devs survey 2026LinkedIn adds a "Seems like AI slop" buttonGitHub adds stacked pull requestsTanStack rebrand & a new charting libraryAnthropic's Claude Opus 5 modelWhat's Making Us HappyPaige: His & Hers miniseriesJack: The Vampire Lestat miniseriesTJ: Orbit Traveling Tractor Water SprinklerThanks as always to our sponsor, the Blue Collar Coder channel on YouTube. Join us in our Discord, explore our website and reach us via email, or talk to us on X, Bluesky, or YouTube.Front-End Fire websiteBlue Collar Coder on YouTubeBlue Collar Coder on DiscordReach out via emailTweet at us on X @front_end_fireFollow us on Bluesky @front-end-fire.comSubscribe to our YouTube channel @Front-EndFirePodcast

In deze 100ste aflevering kijken we samen met gast Erik terug op de ontwikkelingen van Figma, browsers, CSS, apps en de verandering van de rol als UX Designer in de afgelopen 6 jaar. Daarnaast nemen we deze aflevering op in hartje Groningen in het Forum. Uiteraard geven we jullie nog weer praktische, leuke en handige tips! 01:52 - Terugblik op Figma 15:12 - Terugblik op browserontwikkeling 25:45 - Terugblik Technieken, tools en apps die het niet hebben gered 33:24 - Terugblik op Cloud gaming 43:26 - Terugblik op AI 48:00 - AI in games 53:25 - Terug op toegankelikheid 01:06:29 - Erik heeft een eigen LP laten maken 01:18:50 - Terugblik op home automation 01:30:59 - Terugblik op de rol van de UX designer 01:44:50 - Terugblik op alle footers 01:49:35 - Million Dollar Secret Seizoen 2 - https://www.netflix.com/nl-en/title/81731670 01:51:00 - AEG Vx8.2 stofzuiger 01:55:49 - TV Serie: Unit 13 - https://youtube.com/playlist?list=PLoNJZg83zwjF8CI_VmY2D5BBMg607OF48 01:59:22 - Barcado interactieve gametafel - https://www.barcado.nl/ 02:04:12 - Virtuele thuisaccu voor Homeassistant - https://github.com/hif2k1/battery_sim 02:09:41 - Obsidian notes

Ricky from The Wurst is back and he brought a new friend! Alec does Branding/Marketing professionally but is a Mixologist certified with CSS and a WSET level 2 Award in his spare time. He also has a newsletter that you can find HERE and his IG HERE

In the first episode of Circling Seattle Sports' weekly UW men's basketball show, "The Husky men's hoops show," Roundtable Sports reporter Teren Kowatsch joins CSS founder and editor-in-chief Charles Hamaker to discuss the team's losses from the 2025-26 roster, the additions made from the United States, the international players that Washington acquired, the two coaching staff hires that the Huskies made, and more.

In the tenth episode of Circling Seattle Sports' weekly UW women's basketball show, "The Husky women's hoops show," Roundtable Sports reporter Teren Kowatsch joins CSS founder and editor-in-chief Charles Hamaker to discuss the team's losses from their 2025-26 roster, the transfer portal additions made, the coaching staff hires Tina Langley made, and more.

In the seventh episode of "Under the Surface," Circling Seattle Sports' Seattle Torrent show/podcast, CSS founder and editor-in-chief Charles Hamaker is joined by Seattle Torrent second-round draft pick and defender Sydney Morrow! Morrow discusses her teammate Abbey Murphy, her hockey upbringing, her college teammates that will be joining her, the Torrent blueline, the Torrent "trinket exchange," and more.

Bentornati e bentornate su Azure Italia Podcast, il podcast in italiano su Microsoft Azure!Per non perderti nessun nuovo episodio clicca sul tasto FOLLOW del tuo player

In this Tax Tuesday episode, Anderson Advisors' Barley Bowler, CPA, and Eliot Thomas, Esq., answer listener questions covering entity structuring, real estate tax planning, investing, and charitable giving strategies. They explain when it makes sense to form an LLC or S Corporation for a real estate flipping business and whether new investors should wait until after closing their first deal. They also discuss how profits earned inside an LLC trading stocks and stock options are taxed, and whether leaving funds in a brokerage account changes the tax treatment. Barley and Eliot break down whether a cost segregation study makes sense for a long-held commercial property undergoing significant capital improvements, and how that decision compares to selling the property, completing a 1031 exchange, and performing a cost segregation study on replacement assets. They also explore tax-efficient charitable giving strategies, including ways to contribute appreciated assets or funds designated for charity while minimizing capital gains taxes. Tune in for practical guidance on these tax-saving strategies and more! Submit your tax question to taxtuesday@andersonadvisors.com Resources Claim Your FREE 45-minute Strategy Session to receive business planning tips and asset protection.

In the sixth episode of "Under the Surface," Circling Seattle Sports' Seattle Torrent show/podcast, CSS founder and editor-in-chief Charles Hamaker is joined by Seattle Torrent general manager Meghan Turner! Turner speaks on the team's inaugural season, the challenges of the expansion process, a new head coach, the entry draft class, and more.

Everyone selling in Europe has heard the pitch: use a third-party CSS and get a "20% discount" on your Google Shopping bids. Mike Ryan and Chris finally settle what that number actually means — and it's not a discount at all. They break down the real math behind Google Shopping Europe's mandatory margin, whether a multi-CSS strategy still makes sense in 2026 (spoiler: it doesn't), and why the fear of "bidding against yourself" across multiple CSS partners is a myth Google has gone out of its way to debunk.Then: a lesson for every advertiser, EU or not. If bid is the only real differentiator between a PMax shopping ad and a Standard Shopping ad serving the identical product, what happens when you run both at once? Mike shares fresh CPC data across shopping-only, hybrid, and PMax-only accounts suggesting the answer is: your account gets hotter. Whether or not you technically "bid against yourself," running overlapping campaign types may be quietly inflating your CPCs — and Google's new Channel Diagnostics report might be a tacit admission of exactly that.In this episode:• Myth #1: the "20% discount" claim — it's purchasing power, not a discount• The real math: how Google Shopping Europe's mandatory margin actually hits your bid• Do you still need a third-party CSS in 2026? (Yes — here's why)• Myth #2: does a multi-CSS strategy still make sense, or is it a "last-mover penalty"?• Myth #3: are you bidding against yourself with multiple CSS partners?• The bigger lesson: what happens when bid is the only ad rank differentiator?• Fresh CPC data: shopping-only vs. hybrid vs. PMax-only accounts• Google's new Channel Diagnostics report for PMax — a tacit admission?• The verdict: hybrid PMax + Shopping setups can work, but only with a real strategyGrowing Ecommerce is brought to you by smec (Smarter Ecommerce). Learn more: https://www.smarter-ecommerce.com

Send a message to InsidetheSquareSquarespace keeps absorbing the things designers used to hand-code.So when a feature ships that replaces code already sitting on a live client site, do you rip it out or leave it alone?In this episode I'm sharing how I decided if the code should stay or go.I also cover the customizations I have no intention of giving up, and the small branded details I call Disneyfying a website.Full show notes: insidethesquare.co/podcast/9400:00 — Squarespace added the feature. Do you remove your custom code?01:21 — The first question: how many pages does this code affect?01:36 — Hiding the header and footer on a Squarespace landing page02:15 — Two columns of products on mobile: remove this code and use the setting02:59 — Uploading a custom font to Squarespace instead of coding it03:55 — Button hover effects: when to keep your CSS and when to use the editor05:27 — Mobile menu customizations that still need custom code07:58 — The rule: sitewide stays in code, one-offs go nativeSupport the showThe term "Squarespace" is a trademark of Squarespace, Inc. This content is not affiliated with Squarespace, Inc.  For a transcript of this episode, along with the links to any resources mentioned, visit insidethesquare.co/podcast

Hay un debate que lleva tiempo flotando en toda la comunidad del desarrollo web, y en la de WordPress en particular: ¿tiene sentido seguir apostando por una plataforma tradicional cuando una IA es capaz de generar páginas enteras, con código personalizado e interfaces, en cuestión de segundos? Es una sensación perfectamente comprensible. Cuando ves lo que la inteligencia artificial puede hacer al vuelo, es natural preguntarse qué espacio le queda a WordPress. Pero, bajo mi punto de vista, el valor de WordPress no ha desaparecido: simplemente ha cambiado de lugar. En lugar de competir contra la IA, WordPress se está consolidando como el motor de ejecución y la base de datos sobre la que esa misma inteligencia artificial opera. Propiedad y soberanía de los datos La gran diferencia entre las soluciones no-code basadas en IA (o las plataformas SaaS empaquetadas que te alquilan su infraestructura) y WordPress es el control total. Con WordPress, la base de datos, los usuarios, los pedidos y los contenidos son 100% tuyos o de tu cliente. No hay locking. Ese concepto que antes se aplicaba a ciertos temas cerrados hoy lo trasladamos a la IA: no dependes de cambios drásticos en los precios de las APIs de empresas como ChatGPT o Claude, ni del cierre repentino de un servicio. La soberanía digital es un activo cada vez más crítico. Hay empresas que despidieron a mucha gente pensando que la IA lo haría todo, y muchas han terminado quebrando por eso. La IA necesita un backend confiable La inteligencia artificial es extraordinaria generando código y diseñando interfaces al vuelo, pero necesita una estructura sólida detrás para funcionar en el mundo real: la lógica de negocio, la persistencia, la gestión de usuarios y roles, las pasarelas de pago, las suscripciones y los flujos complejos. Un ejemplo real: la web de vozcaster.com la desarrollé entera con IA. Registré el dominio, la alojé en Cloudflare y le pedí a la IA que me creara un HTML estático muy mono, con colores bonitos y una tabla de precios dinámica con su selector anual. Todo rápido y precioso. Pero cuando llega el momento de la verdad —los usuarios, la seguridad, la gestión de suscripciones—, esa tabla enlaza a potencia.pro, donde todo lo gestiona WordPress mediante un plugin. La IA te resuelve la parte estática; la lógica de negocio y la persistencia en condiciones te las da una plataforma madura. Infraestructura lista para usar En lugar de construir desde cero un sistema de autenticación, una base de datos y un panel de administración para cada proyecto generado por IA, WordPress te ofrece toda esa arquitectura probada en batalla de forma nativa. Además, WordPress ya no es el simple generador de plantillas HTML o el gestor de blogs de antaño. Hoy cuenta con: APIs robustas gracias a su REST API y a soluciones como GraphQL. Un funcionamiento excelente como CMS headless, donde la IA alimenta los datos mientras la capa de presentación se gestiona externamente. Integración nativa con agentes de IA gracias al protocolo MCP, que permite conectar un sitio WordPress con modelos de inteligencia artificial para generar contenido, automatizar soporte o procesar datos de forma mucho más sencilla, precisamente por la madurez de la plataforma. Los flecos y los casos de borde Crear un prototipo visual con IA lleva minutos. Pero resolver los flecos finales —el cumplimiento del RGPD, las integraciones con ERP locales, la facturación compleja, los flujos de trabajo específicos— sigue requiriendo un sistema maduro. El repositorio de plugins de WordPress aporta esa flexibilidad para cubrir ese 1% de necesidades complejas que una herramienta automática suele pasar por alto. Es curioso: la IA arranca a toda velocidad, pero al llegar a cierto punto se frena, porque necesita hacer cosas que WordPress ya resuelve de forma simple por estar tan implementado. En una carrera de fondo, WordPress se come a la IA. Pasa igual que con los constructores visuales: Elementor es maravilloso y rapidísimo para la primera versión de una web presencial de cliente, pero cuando quieres implementar cosas más complejas a veces te toca irte a temas como GeneratePress. Son esos casos de borde que WordPress tiene más que superados. El rol del profesional no desaparece: se transforma Es como el agricultor que pasa del arado al tractor: sabe lo mismo, pero lo hace más rápido. El trabajo pesado ya no es picar CSS ni maquetar desde cero. El valor del profesional con experiencia en WordPress ha migrado hacia: La arquitectura de la información y la estrategia. El criterio técnico y la seguridad: saber evaluar si el código generado por la IA es seguro, optimizado y mantenible. La capacidad de conectar el ecosistema de WordPress con flujos de IA para aportar valor real, no solo un sitio estático. Otro ejemplo propio: he desarrollado un bot de Telegram que se conecta con WordPress para publicar capítulos de podcast (de hecho, este capítulo lo estoy publicando con ese sistema porque no tenía ganas de editar). Si yo no tuviera el criterio adquirido a lo largo de más de 15 años, no podría usar la IA de forma eficiente. Sé dónde está la identificación de usuario, cómo se gestiona una suscripción, dónde están los datos, y conozco a fondo plugins como PowerPress. Ese conocimiento profundo es el que me permite establecer la arquitectura y la estrategia adecuadas. No cualquiera puede desarrollar así. En resumen La IA ha democratizado la creación de webs sencillas: cualquiera puede pedirle una página que le diga lo guapo y lo alto que es, y quedará preciosa. Pero, precisamente por eso, las arquitecturas abiertas y extensibles como WordPress se han vuelto aún más valiosas como núcleo de proyectos digitales complejos: gestión de bases de datos, arquitectura, estrategia y capa de negocio. Cuando mezclamos ambos mundos —lo que ya conocemos de WordPress con la inteligencia artificial— aparecen cosas maravillosas. Así que no, la IA no nos va a quitar el trabajo: nos facilita avanzar de forma eficiente. Pero hay que usarla con criterio, y ese criterio es justamente lo que los desarrolladores del mundo WordPress hemos acumulado durante años. La IA sin criterio no sirve de nada. 🤖 El contenido de este post ha sido generado automáticamente con inteligencia artificial a partir de la transcripción del audio. Puede contener errores o imprecisiones. 🎙️ Publicado con VozCaster, el bot de Telegram que convierte tu voz en un episodio de podcast publicado. Pruébalo gratis. ¿Te ha gustado el episodio? Si quieres que sigamos experimentando con bots, protocolos y empanadillas polacas, no olvides suscribirte y dejarnos tu valoración. ¡Nos escuchamos en el próximo capítulo! Métodos de contacto Enviadnos vuestras preguntas al grupo de Telegram. Apuntaos al canal de Youtube del podcast https://www.youtube.com/potenciapro Si nos queréis decir algo directamente lo podéis hacer a @potenciapro , @materron, @mpc, o en el grupo de Telegram Y si eres muy muy muy fan del podcast Echa un vistazo a cómo nos puedes ayudar en https://potencia.pro/se-prosperoso/

Today we are talking about Supporting Open Source, Acquia, and The Acquia Fair Trade Initiative with guest James Sims. We'll also cover Image Effects as our module of the week. For show notes visit: https://www.talkingDrupal.com/562 Topics Fair Trade Initiative Explained How the Program Started Why Fair Trade Matters Adoption and Open Framework Agency and Freelancer Benefits Partner Funded Giving Who Can Be Makers Tracking Participation Tax Deduction Questions Community Shaped Program Money Counts Too Early Challenges Timeline And Launch Sustainability Built In How To Get Involved Defining Success Origins Of Fair Trade Resources Acquia Fair Trade Initiative Taste of chicago Giordanos Lou's pizza Five For The Future Image Convolution Playground Guests James Sims - rcjmselp85 Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Avi Schwab - froboy.org froboy MOTW Correspondent Avi Schwab - froboy.org froboy Brief description: Have you ever gone to edit an image style in Drupal, looked at the list of filters, and said "give me more! I want more!". Have you said "I'd like to mirror, filter, and convolute an image in Drupal - all at the same time". If so, you're in luck. Let me introduce you to our module of the week: Module name/project name: Image Effects Brief history How old: Created by Drupal user mondrake of Italy on 17 September 2015. It's also the successor to the ImageCache Actions module, which was created all the way back in 2008. Versions available: It has a 4.0.0 version available with Drupal 10 and 11 support, and a 5.0.0 version for Drupal 11.3 and above. Maintainership Actively maintained Security coverage Test coverage Documentation It has a full README with details about the available image styles and whether they are supported by the GD or ImageMagick PHP libraries. Number of open issues: 35 open issues, 3 of which are bugs against the current branch. (The current branch has only been out a few months, and many of the open issues against prior branches seem to still be relevant.) Usage stats: 35,196 sites report using this module, with most still on the 3.x or 4.x branches. (its predecessor, ImageCache Actions, still has over 25,000 active installs) Module features and usage The module is pulled in just like any other, with composer require and then enable via drush or the UI. Once it's installed there is a very basic settings page, but most folks won't use much on there. The power of Image Effects comes when you go to Config > Media > Image Styles and then edit an Image Style. Once Image Effects is enabled, you'll see over two dozen additional effects in the list. These effects range from simple to complex. Interestingly, many of the effects that were so amazing 15 years ago are now doable with CSS. Still, there are some incredibly powerful filters. Side note: I'd strongly recommend Aubrey Sambor's recent talk from Drupal Camp Asheville, "You Don't Need JS for That", and her prior talk "Color in CSS" to learn a ton of things you didn't know about CSS effects. The basics like Color Shift, Contrast, Mirror, Rotate, and more are there if you'd like to do these natively. More advanced filters like Sharpen, Blur, and Convolute let you make more complex modifications to images. "Convolution" is the process of applying n-dimensional matrixes to images to create effects such as blurring, sharpening, and edge detection. Try it out on https://anna.engineering/Image-Convolution-Playground/src/ Lastly, you can create advanced image styles with ImageMagick arguments, create Text overlays using the power of Drupal tokens, or even develop your own Image Effects guided by the incredibly detailed DEVELOPING.md file included with the module.

 PHP Podcast – July 16, 2026 Hosts: Joe Ferguson, Sara Golemon, and Holly Schilling Joe hosts with Sarah and Holly while running on no sleep. The PHP Tech 2027 CFP opens, a fake PHP 9 pitch appears, we crown Holly the accidental main character of internals, and everyone agrees dark mode flashing white is a war crime. PHP Tech 2027 CFP Is Open (And Yes, the Year Is Right This Time) The big news kicking off the show is that the PHP Tech CFP for 2027 is live and open. You can find it over at Sessionize under php-tech-2027, and unlike a certain demo from the previous week, the date on it is actually correct. There was a brief moment where it displayed 2007, but the team fixed that rather quickly, so credit where credit is due. The crew marveled at the fact that we are somehow less than six months out from 2027, which spiraled into a conversation about kids getting learner’s permits, full beards showing up on children who were toddlers just yesterday, and whether anyone’s offspring might actually submit a talk. Helldivers came up. Freedom was spread. And there was a gentle suggestion that SoCalKid and their newly engaged fiancé should be sent the CFP URL immediately. Meanwhile, PHP Tech 2026 videos are rolling out on PHP Tech TV. There are currently 37 available with more still processing thanks to some technical and room issues at the event. Several talks are completely free, including Joe’s talk on modernizing DevOps, Kaylin’s “Modernize Your Old School Endpoints with HTMX,” and both of Ben Ramsey’s talks. Working Groups, Discord, and the People Who Actually Care The conversation turned to the internals process and Ben Ramsey’s working group proposal on the internals mailing list, which the crew encouraged everyone to actually read. The idea of giving working groups some autonomy and even decision-making power drew broad agreement as a way to produce more fully-fleshed RFCs rather than one person’s implementation of a giant feature. A recurring point of confusion is the reference to “Discord conversations” in RFCs. There is no official PHP.net Discord, but phpc.chat will get you to the Discord (and previously the bridged IRC). The PHP Internals channel is where a lot of discussion happens, though far from the only place, and there are also the PHP Foundation and new Foundation Ambassadors channels. Big appreciation went out to the moderators keeping that Discord spam-free and troll-free, with a special shout to Tiffany, who is an absolute machine at helping people, pointing them in the right direction, and posting top-tier cat pictures in the pet flexing channel. The recurring theme: decisions are made by the people who show up. Silence is acquiescence, and if you have issues, speak up. Holly famously just showed up in internals one day, started talking, and they let her stay. This Week in Internals and the Co-Scientist Show Joe wanted to highlight Artisan Build’s YouTube channel, specifically their “This Week in Internals” videos. They are fantastic recaps of what’s happening in the internals world, complete with a very light sprinkling of extremely dry comedic timing that lands perfectly. The videos break down email threads and RFCs into easily digestible summaries of what people are arguing over, then poke a little fun at the sillier arguments. A weekly recap drops regularly and it’s consistently great content for anyone curious about internals. The crew was also impressed by the host’s ability to nail every name pronunciation on what seems like the first try, which spiraled into Holly’s confession that she has a hard memory limit on names learned after kindergarten. Anyone new is simply “out of bounds.” Holly’s Fake PHP 9 Pitch: Structs, Modules, and Surfaces Holly walked through a blog post on eventuallywrong.com featuring a fake PHP 9 pitch full of flagship features she’s prototyped. It kicked off with extensions, which she discovered didn’t exist while trying to build the Longhorn app in native PHP, landing her at the top of that internals video. Next came structs, which started as an attempt to build tuples (turns out full structs were easier). They’re Swift-style value types with strong typing, and after some grumbling at Larry, she reworked things to support interfaces and traits, leaning into composition over inheritance. Modules got the PHP-style treatment: a simple module definition, a public interface declaration, and a new `internal` visibility level that lets members be accessed within the same module. No autoloader modifications required, and reflection remains the escape hatch as always. Finally, surfaces — a keyword that adds a perpendicular-to-visibility scope. A method can belong to a surface, and callers simply declare they want to use that surface of the class. Holly performance-tested it: no impact if unused, minimal impact if used. She also spent a good chunk of the show against friend classes, arguing they’re leaky, unrestricted, and if you’re going to hand out full access to your privates, you shouldn’t have marked them private in the first place. Release Management, Version Stats, and Upgrade Paths Holly is a first-time PHP 8.6 release manager alongside Matteo Beccati, with veteran Daniel Scherzer (also on 8.5) rounding out the team. She stepped down from RM in a prior election because others wanted the work — a reminder that people stepping up in open source is a rarity worth celebrating. Release management, she noted, is less a social job and more about moving data at the right time and signing things. The July 2026 PHP version stats got a thumbs up. Looking at the trends, 8.5 is clearly on the rise, 8.4 climbing slightly, 8.3 starting to trend down, and 8.2 falling harder — exactly the curve you want, with the vast majority sitting inside the support window. Joe shared that upgrading apps from PHP 7 to 8.3/8.4/8.5 has been a much easier lift than the older 7.x hops, thanks to a more consistent release cadence and better deprecation guidance. Holly pushed back on the idea that 5.6-to-7 was ever hard, while Joe pointed out the real pain came from jumping ancient 5.0/5.1 codebases straight to 7 back before Claude existed. There was also a very in-depth debugging tangent about an opcache build flag no longer being needed on 8.5. Accessibility, Dark Mode Crimes, and the JetBrains Survey The JetBrains State of PHP survey is open, and everyone should go take it — there’s even a chance to win one of five vouchers. This led to a discussion about whether JetBrains usage is being decimated by AI tooling, with Holly living almost entirely in the terminal with Claude Code these days while Joe remains loyal to PHPStorm and PyCharm. Sarah, who is going blind and is not joking about it, kicked off a passionate segment on accessibility. Test your apps with a screen reader. Respect font scaling and contrast (F0F0F0 text on white is a genuine crime). Respect the OS toggles for reduced motion, because autistic users and others depend on them and apps routinely ignore them. The crew then united around dark mode etiquette: the only reasonable default is system-selected, and the white flash between two dark-mode pages is caused by JavaScript-based theme switching instead of sane CSS selectors. It is, universally agreed, the worst. The episode closed on eye-tracking privacy (Apple Vision Pro good, Oculus terrifying), heat maps, and a laptop-camera-covering tangent that got appropriately unhinged before Joe called it on that bombshell. Links from the show: PHP Tech 2027 CFP — Now open on Sessionize eventuallywrong.com — Holly’s fake PHP 9 pitch phpc.chat — Get to the PHP Discord store.phparch.com — Now with socks Hosts: Joe Ferguson X: @shocm Mastodon: @joepferguson@social.social PHPArch.me: @svpernova09 Sara Golemon Mastodon: @pollita@phpc.social Holly Schilling Mastodon: @TheCodeLorax@tech.lgbt Streams: Youtube Channel Twitch Connect & Hire PHP Architect Website Twitter/X Mastodon Hire PHP Developers Looking to hire PHP developers? Email support@phparch.com – Joe and the team are available for consulting, infrastructure work, Ansible playbooks, and code review. Partner This podcast is made a little better thanks to our partners PHP Architect Consulting Your PHP codebase deserves a partner, not a contractor PHP Architect provides long-term technical partnerships for organizations that need senior-level PHP expertise that you can depend on https://www.phparch.com/consulting/ Displace Infrastructure Management, Simplified Automate Kubernetes deployments across any cloud provider or bare metal with a single command. Deploy, manage, and scale your infrastructure with ease. https://displace.tech/ OurCVEs Your security posture, on autopilot with OurCVEs CodeRabbit Cut code review time & bugs in half instantly with CodeRabbit. Music Provided by Epidemic Sound https://www.epidemicsound.com/ Join Us Live Next Week Youtube Channel Got feedback? Join us on Discord at discord.phparch.com The post The PHP Podcast 2026.07.16 appeared first on PHP Architect.

Intracerebral hemorrhage carries high morbidity and mortality, but growing evidence highlights meaningful opportunities for prevention, risk reduction, and long-term recovery. This episode covers key strategies, including blood pressure management, interpretation of neuroimaging markers, and individualized decisions around antithrombotic therapy. It also emphasizes the prolonged recovery timeline and the importance of a holistic, patient-centered approach to improving outcomes. In this episode, Casey S. Albin, MD, FAAN, speaks with Wendy C. Ziai, MD, and Vishank A. Shah, MD, coauthors of the article "Intracerebral Hemorrhage" in the Continuum® June 2026 Cerebrovascular Disease issue. Dr. Albin is a Continuum® Audio interviewer, associate editor of media engagement, and an assistant professor of neurology and neurosurgery at Emory University School of Medicine in Atlanta, Georgia. Dr. Ziai is a professor of neurology and critical care medicine at Johns Hopkins University School of Medicine in Baltimore, Maryland. Dr. Shah is an assistant professor of neurology and critical care medicine at Johns Hopkins University School of Medicine in Baltimore, Maryland. Additional Resources Read the article: Intracerebral Hemorrhage Subscribe to Continuum®: shop.lww.com/Continuum Earn CME (available only to AAN members): continpub.com/AudioCME Continuum® Aloud (verbatim audio-book style recordings of articles available only to Continuum® subscribers): continpub.com/Aloud More about the American Academy of Neurology: aan.com Social Media facebook.com/continuumcme @ContinuumAAN Host: @caseyalbin Guest: @VishankShah3 Full episode transcript available here Dr Albin: A patient has suffered an intracerebral hemorrhage. They're taken to the neuro ICU, and they fortunately survive. But the journey does not end there. In fact, in some ways, the journey has just begun. Join us today as we unpack holistic care for ICH patients.  Dr Jones: This is Dr. Lyell Jones, Editor-in-Chief of Continuum. Thank you for listening to Continuum Audio. Be sure to visit the links in the episode notes for information about earning CME, subscribing to the journal, and exclusive access to interviews not featured on the podcast.  Dr Albin: Hello to our audience. This is Dr. Casey Albin. Today, I'm interviewing Dr. Wendy Ziai and Dr. Vishank Shah about their article on intracerebral hemorrhage. This article appears in the April 2026 Continuum issue on cerebrovascular disease. Welcome to the podcast. I am so delighted that both of you are joining. To begin, let's just do a brief introduction of who you are and, and a little bit of how you got interested in the topic.  Dr Ziai: Hi, I'm Wendy Ziai. Thank you for having me on this podcast. I am a professor of neurology at Johns Hopkins. I am a neurointensivist, and I think I got primarily interested in this topic through clinical trials that I have been a part of since my fellowship days.  Dr Shah: Hi, everyone. I'm, uh, Vishank Shah. I am also, uh, very thankful for being invited to be a part of this podcast. I'm also a neurointensivist at Hopkins and the fellowship program director here for neurocritical care, and I'm interested in recovery after ICH, and that's why I'm a part of this work.  Dr Albin: Welcome to you both. It is such a treat for me to get to interview fellow neurointensivist, particularly those who have such a wealth of experience. So, I am delighted to dive into this. All right. So, to set the stage for our audience, intracerebral hemorrhage has long been approached with pessimism. But your article really highlights that there are meaningful advantages in prevention and risk stratification and long-term recovery for these patients. Though you both are neurointensivist, this article really emphasizes primary prevention and the holistic long-term care for the survivors. And so, to begin, Dr. Shah, can you just lay out a little bit for our listeners the scope of intracerebral hemorrhage and its community impact?  Dr Shah: Yeah. So, you know, ICH is the second most common type of stroke. There are more than three million new cases of ICH globally each year, and it accounts for thirty percent of all stroke types, but it is the one that has the highest mortality, with more than forty to fifty percent of the patients dying in the first thirty days, and then continued long-term impact on both functional as well as outcomes, as well as survivorship after the early period. And it also disproportionately impacts lower socioeconomic, and then minority races like Blacks, Asians, as well as Hispanic ethnicity. And so, there's a lot of work that needs to be done to reduce the burden of this disease.  Dr Albin: Absolutely. I mean, these can really be devastating for families, and I really am appreciative of your highlighting that there's a lot of disparities, and there's a lot of work to be done to really increase equity to these patients. I think a lot of this goes into really the AAN's focus on brain health and trying to improve some of what we're doing to maintain brain health. And I really wanted to kind of drill down on this because for ICH, there's a lot that can be done upfront as we think about how do we counsel patients who may walk into the office about strategies to prevent ever becoming an intracerebral hemorrhage patient. So, Dr. Shah, can you walk us through a little bit about what neurologists in the community need to be doing to make sure that no one ends up with us in the neurointensive care unit?  Dr Shah: Yeah, sure. So, I think, you know, one of the most important risk factors is, of course, hypertension and long-standing uncontrolled hypertension. And so really recognizing the need for early onset screening with regular blood pressure monitoring at a very early age, particularly in the races that I discussed earlier. And then I think another big part, obesity, metabolic syndrome, and type two diabetes. And I think there's a lot of interesting new work that with the GLP-1 agonist, you know, in a large multicenter cohort studies showing that patients receiving these had a significantly lower reduction risk of ICH. And so, this might be a really important part that, you know, clinicians need to start increasingly recognizing and using in their practice. And then, of course, other risk factors that are common include smoking, diet high in sodium, exposure to air pollution, both indoor as well as outdoor. And so, mitigating all of these risk factors can also reduce the burden of ICH.  Dr Albin: Absolutely. And I really want to highlight that hypertension plays such an important role and that we as neurointensivist, as community neurologists, really need to be creative about ways that we can help people meet those blood pressure target and meeting people in the community where they are, making sure that they're not suffering from side effects from their medication that would prevent them from sticking with it long term. Dr. Ziai, anything else to add about what we can do in the community?  Dr Ziai: So, we really want to emphasize, even in the acute phase, that patients moving forward need to have targeted interventions to reduce blood pressure, smoking, enhance their physical activity, have a diet that is high in fruits and vegetables and low in alcohol and salt, and then promoting weight loss, of course.  Dr Albin: And Dr. Ziai, I'm gonna ask you a little bit about one of the things that maybe not all of our listeners have heard about is this APOE2, APOE4 genetic risk for intracerebral hemorrhage. What's going on there and, and should clinicians be testing for that? Dr Ziai: That's a great question, and it is not one that we currently test people for at least acute ICH presentation. APOE2 and A4- E4 alleles, these give patients a two to three times higher risk of ICH by increasing cerebral amyloid deposition. And if you happen to have APOE2 carrier ship status, then along with other risk factors like white matter disease and vascular risk factors, these predict the onset of new microbleeds even during very short follow-up periods of about two years. And as we know, having cerebral microbleeds are associated with an increased risk of all strokes, ischemic and ICH, but they are one of many MRI markers of small vessel disease, which along with cortical superficial siderosis, does significantly increase future ICH risk. And so even in people who've never had an ICH, if they happen to have an MRI, it may be reasonable to look at the MRI and incorporate this burden of small vessel disease, and especially these hemorrhagic markers into, uh, decision-making about interventions.  Dr Albin: That's a really excellent point. And so, I think that your article did a really beautiful job of thinking holistically about the patient, incorporating clinical markers of their risk for having ICH, but also those radiographic markers. I'm just gonna ask you to summarize those again one more time because not everyone will be familiar with these. So, when you're looking at an MRI, what are the things that you're particularly clued in on that would increase the patient's risk of future ICH?  Dr Ziai: In the past, what we're looking for really is markers of cerebral amyloid angiopathy, which significantly increase a person's risk for lobar hemorrhage in particular. And so, we have a set of criteria called the Boston Criteria, and there's a new version of these, version 2.0. And these, um, incorporate a number of imaging markers that provide a very high sensitivity and specificity to diagnose CAA after an ICH. But even if someone's never had an ICH, and they evaluate that risk-benefit ratio for different cardiovascular prevention strategies. And so, the markers that we're specifically interested in are, of course, microbleeds. But not just having microbleeds, but are they lobar or are they deep? Lobar having a higher risk for lobar ICH. How many microbleeds are there? Is it greater than five, or is it just one or two? Also, cortical superficial siderosis is a marker, a hemorrhagic marker, that does portend a significant increased risk of recurrent ICH, along with having a lobar ICH. And now we have these new markers, which are the white matter hyperintensity multi spot pattern, which requires these hyperintensities on flare imaging in the subcortical area, having greater than at least ten of these multi spots, and also having enlarged perivascular spaces in the centrum semiovale, and having at least twenty of those. And finally, white matter hyperintensities, which can be measured with the physica score or just by visualizing them. We can look at white matter hyperintensities as well as being a measure of small vessel disease.  Dr Albin: Got it. And so just to summarize, we're looking for small vessel disease markers because that puts our patients at higher risk of ongoing future bleeds. And then we're also looking for markers of particularly small vessel disease that's caused by cerebral amyloid angiopathy, which again, because it's having that protein deposition, that puts the patient at risk of those leptomeningeal very small vessels, putting the patient at risk of lobar ICH. Just confirming I've summarized this all correctly.  Dr Ziai: Yes. That was perfect.  Dr Albin: Amazing. Dr. Shah, I'm gonna go back to you. Let's say we have a patient. Let's say this is a sixty-five-year-old man who comes in and they want follow-up and they're... And you're trying to think about they've had an ICH in the past, and they are also at risk for ischemic disease. Let's say they, they have hypertension, they've had a smoking history. They have some risk for ischemic events. And you're trying to think about how do you balance those. Let's say the patient needs to be on aspirin but does have some of those high-risk features on their MRI. Is there any guidance on how we think through preventing them from having a recurrent bleed if they're a high-risk patient, also preventing them from having an ischemic event, which they might be at high risk for as well?  Dr Shah: Yes. So, I think, you know, the first step is of course trying to understand what was the type of bleed. I think that has a very important role, like you mentioned. If it's a lobar hemorrhage versus a deep hemorrhage, the risk of recurrent ICH and ischemic events is very variable. So lobar hemorrhages, there's obviously a higher risk of recurrent hemorrhage events, whereas deep hemorrhage is actually at or behaves sort of like small vessel ischemic strokes and have a higher risk of recurrent arterial ischemic events. So that distinction in itself can help you gauge which patients would be safe and would benefit from these therapies. To begin, and of course, looking for some of these markers on MRI that were mentioned by Dr. Ziai for recurrence of hemorrhage risk. In terms of antiplatelet, the, there is a lot more data now to guide treatment, and we have the RESTART as well as the ESTART trial that showed that starting an, a single antiplatelet after intracerebral hemorrhage did not increase the risk of hemorrhage recurrence. They were very variable in the timing when aspirin was started, and so that remains still a question about what is the safest time point to start aspirin. For example, in the ESTART trial, they started them very early, within the first three days, whereas in  the RESTART it was all the way up to two months after the hemorrhage. And so... But in general, the risk of recurrent ICH was very low with a single antiplatelet agent. And so, if it's needed for ischemic prevention, it's relatively safe broadly across all types of hemorrhages.  Dr Ziai: Yeah. I would just mention that there was also a subgroup analysis of the RESTART trial using MRI. And so, this more than likely included patients with CAA, since 40% of the hemorrhages were lobar in that study, and therefore seeing that there was no increased risk of recurrent ICH in RESTART, it is thought that putting patients back on their antiplatelet therapy is safe.  Dr Albin: That's a really huge takeaway pearl for our listeners, that regardless of whether it's a lobar bleed or a deep bleed, if there is a strong indication, you know, this is not just, oh, because someone gave them aspirin 81, but truly that there is a reason that they need to be on a single antiplatelet agent, it probably benefits them to be on that agent, and there's good data that there's not a huge increase in risk. Summarizing all of that?  Dr Ziai: Great.  Dr Albin: Now, things are gonna get a little bit tricky here, because what if the patient, what if they need to be on dual antiplatelet therapy? Or what if they need to be on anticoagulation? Dr. Ziai, I'll, I'll throw that to you. How do you tackle that patient population?  Dr Ziai: Yeah, the safety of dual antiplatelet therapy hasn't really been studied in patients who've had a prior ICH. Although, in people who've had previous strokes, putting them on dual antiplatelets doesn't seem to increase the risk of ICH, but it does increase extracranial hemorrhage. And so there may be other reasons not to put patients on dual antiplatelet agents. Patients who have cancer and also cardiovascular or cerebrovascular disease, putting them on dual antiplatelet therapy does seem to increase the risk for intracranial hemorrhage. So, I think there is enough of a bias against DAPT therapy in patients who have had an ICH that we would not recommend DAPT for patients with a prior ICH.  Dr Albin: Absolutely. And, and then what about, let's say they have atrial fibrillation, and you know that they have a high CHA2DS2-VASc score, and they are at very high risk of ischemic events, but they've also had a prior intracerebral hemorrhage. Walk us through a little bit, how should we approach that patient? Dr. Ziai, I'm gonna start with you again.  Dr Ziai: Sure. So again, looking at the MRI, which all patients with ICH should have nowadays. If patients do have these hemorrhagic findings, a lobar ICH, evidence of CSS, cortical superficial siderosis, especially if it's disseminated, and also lobar microbleeds, especially if there are greater than five, if they're multiple, then anticoagulation should really be avoided in those patients.  Dr Albin: Absolutely. So, I'm really hearing that when we have a patient with ICH, it is just critically important that we understand is this a hypertensive bleed or is this a lobar bleed that is probably related to cerebral amyloid angiopathy? And getting to that distinction is going to play a major role in our deciding whether or not the patient can be on DAPT or can be on anticoagulation. And then what are some of the strategies for patients that you're referring them to if they really cannot tolerate being on anticoagulation, but they have atrial fibrillation, and they do need some sort of ischemic stroke prevention?  Dr Shah: There's still a lot of controversy, even in non-lobar hemorrhages, about resuming anticoagulation and when that would be safe. HAF trial, there was a reduction in ischemic stroke recurrence, uh, but a significantly higher increase in hemorrhage recurrences. I think that trial included both deep and lobar hemorrhages. So, we still need more data, and I think the ASPIRE trial and maybe a meta-analysis would answer that eventually. But in the meantime, if a, specifically for lobar hemorrhages, which are, uh, thought to be CAA related, if they, uh, and the patient has AFib, you know, where anticoagulation would be contraindicated, a watchman device or, you know, AFib ablation may be some of the other strategies that can be looked into for those patients specifically.  Dr Albin: Right. I think that's a really important point to emphasize, that we don't just don't give up and say, "Oh, you're not a candidate for anticoagulation," but we really reach out to our cardiovascular friends and say, "Hey, what other procedures can you offer that will minimize the risk of recurrence?" You know, we don't want them to have an ischemic event, but we also know long-term that there would be a real risk of anticoagulation. Just reminder to our listeners that there are new procedures, and our cardiology colleagues are always doing new trials and new devices, and so we should really leverage their expertise here. I am in the final minutes gonna just switch gears a little bit from talking about sort of the nitty-gritty of secondary ischemic prevention and secondary hemorrhagic stroke prevention and thinking about there has been this degree of pessimism around ICH patients, and that, you know, they have a much more severe outcome than our patients with ischemic strokes. I think that that is probably a myth that we need to do some debunking around, and I think maybe we need to reframe in terms of thinking about just the trajectory. So, Dr. Shah, walk us through a little bit about what we can expect about the recovery trajectory in ICH compared to those patients who have an ischemic stroke. Dr Shah: Yes. From some newer data and studies, it is becoming clear that recovery after ICH is much slower than we expect. In general, for ischemic stroke, recovery is measured within the first few weeks to up to 90 days. But in ICH, we now know that patients can keep recovering all the way up to six months and even beyond. In general, from just a, a study of heart recovery that occurs after ischemic stroke, there's a steep recovery in the first seven days, and then sort of after that, patients still continue to recover, but it, it starts plateauing where up to 90 days. Whereas with ICH, there is not much recovery in the first 7 to 30 days, but after that, there is a recovery that occurs significantly between day 30 and day 180, and then some patients continue to recover all the way up to one year. The more severe the hemorrhage, the slower the recovery, but there's still some evidence to suggest that even severe hemorrhage patients can recover all the way up to one year out and beyond. This is, of course, in terms of functional recovery.  Dr Albin: I think that's a really important point for our audience. Many of the listeners are residents, they're fellows, they're seeing these patients in the hospital, and they may not see a whole lot of improvement over even 30 days. But to keep in mind that just because the patient has not had a dramatic recovery within that first month that they may be in the ICU and then on the floor does not mean that that patient will never have recovery, and that we reset our expectations that recovery is possible, it's just gonna be slower. And I think that that's not only important for the healthcare team to take in mind, but also for patients and their families to know there is hope here. It's just gonna be slower. Dr. Ziai, looking ahead, what developments in this are you most excited about that you think will move the needle for care for the long-term outcomes and the prevention for these patients? What's ahead in, in ICH?  Dr Ziai: Yeah, I think the research that's going on is very exciting at the moment. We just saw the presentation at the World Stroke Organization conference in the fall of the TRIDENT trial, Triple therapy prevention of Recurrent intracerebral Disease events, meaning strokes. And these investigators found that a single pill, a fixed dose of three blood pressure-lowering agents actually was successful in significantly reducing the risk of recurrent stroke in patients who have had a history of ICH and have just normal or low-grade hypertension. So rather than having patients on multiple antihypertensive agents, it may be possible to have them on a single pill, and may dramatically reduce their stroke risk. So that's exciting. There is also a trial ongoing, ASPIRING, testing whether antiplatelet monotherapy after 24 hours only can reduce the risk of all serious vascular events in ICH survivors. So very early antiplatelets. The SATURN trial, we didn't talk about statins yet, but it is comparing continuation versus discontinuation of statin therapy in ICH patients. And then we have ongoing epidemiological studies that are really needed to understand this interaction between the cardiovascular prevention strategies, the antithrombotic use, the blood pressure targets, and these high-risk neuroimaging markers for ICH. And I think that's gonna be key, personalizing the interventions for these patients.  Dr Albin: So, I love that. And what I'm hearing is that it's really important to think about the personalized approach as well as how do we simplify things. We know that blood pressure control is critically important to the primary and secondary prevention of ICH, but we have to make it easy for patients to do so. Dr. Shah, I want to end with kind of understanding, you know, this was an unusual topic for neurointensivists to talk about. This was really about prevention. It was about long-term survivorship. It was about not what's happening in the neuro ICU. How did you guys get interested in sort of that aspect of care?  Dr Shah: Yeah, so that's a great question. Dr. Ziai has been my mentor since I was in fellowship, so now about eight years that I've been working with her, and this was a project that I started in fellowship with under her mentorship, looking at long-term recovery in ICH patients, and specifically severe patients. Happy that work has received a lot of recognition. It was published in JAMA Neurology. We looked at patients with severe intracerebral and intraventricular hemorrhage, those that survived with an mRS of four and five at day 30, and what happened to them over the course of the year. There was really not much data on recovery after ICH. And we were very surprised to see that up to 40% of patients that were an mRS of four and five, so really, really severely disabled at day 30, recovered to an mRS of zero to three by one year. About one-third of that group that recovered actually achieved functional independence with an mRS of zero to two, which was very surprising, really breaking the myths around the pessimism with ICH. We found that a lot of the baseline comorbidities like diabetes, white matter disease, as well as what happens to them during the acute hospitalization, were adding all of that information to the severity of the hemorrhage significantly improved our ability to predict long-term recovery after ICH. And so that's kind of how we got interested in this work, looking at how factors in the care that we provide in the ICU, as well as what the patients come in with, how all of that could be modified to promote recovery in these patients that are often been forgotten.  Dr Albin: I think that there's one takeaway to our listeners is that this is really a place where there's a lot of hope for recovery, and that the nihilism that has really surrounded ICH is a thing of the past, and we have to move forward with thinking about how do we proactively impact the recovery and counsel the patients and give them hope. Because just as your research shows, there really is the ability that they can attain that functional independence, which is absolutely astounding. It's really amazing. Again, today I've been interviewing Dr. Wendy Ziai and Dr. Vishank Shah about their article on intracerebral hemorrhage. This article appears in the April 2026 Continuum issue on cerebrovascular disease. Please be sure to check out Continuum Audio episodes from this and other issues. Please go and check out. They have a wonderful article with lots of tables and figures, so much data. And again, thank you to our listeners for joining us today. Thank you, Dr. Ziai and Dr. Shah.  Dr Ziai: Thanks very much.  Dr Shah: Thank you.   Dr Monteith: This is Dr. Teshamae Monteith, Associate Editor of Continuum Audio. If you've enjoyed this episode, you'll love the journal, which is full of in-depth and clinically relevant information important for neurology practitioners. Use the link in the episode notes to learn more and subscribe. AAN members, you can get CME for listening to this interview by completing the evaluation at continpub.com/audioCME. Thank you for listening to Continuum Audio.

Today we are talking about Content, syndication, and Synchronization between Drupal Sites with guest Thiemo Müller. We'll also cover Drupal core 11.4 as our module of the week. For show notes visit: https://www.talkingDrupal.com/560 Topics Origins and Use Cases Hub Model and Flexibility Media Sync and Governance Composable Pages Challenge Governance With Blocks Canvas And Recipes Real Time Syndication Scaling To Thousands GEO And AEO Explained GEO Audits And Loops ContentSync Recommendations Permissions And Drupal 11 AIM Assess Improve Monitor Boosting Drupal AI Presence Ecosystem Alignment Signals Recency And Messaging Tips Resources Content Sync Content Sync A-I-M Content Sync Drupal Module Deprecated extensions meta issue GEO Generative engine optimization Semrush Peec ai Otterly ai Profound Guests Thiemo Müller - content-sync.io thiemo Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Ashraf Abed - drupito.com ashrafabed MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Are you excited for a feature release of Drupal core that delivers even more performance acceleration, a modernized developer experience, and a slew of administrator and editor improvements? Drupal core 11.4 delivers all that and more Module name/project name: Drupal core 11.4 Brief history How old: created on July 1 2026 by catch of Tag1 Changes Performance improvements When Drupal 11.3 was released, we talked about what a massive performance jump it represented, the biggest improvement in a decade. 11.4 has done it again! Database queries are reduced by half, across a range of requests due to optimizations in how entity fields are loaded. Overall, that represents a nearly ⅔ improvement for database and cache lookups on a cold cache compared to Drupal 11.0 or 10.6 Entity listing queries have also been refactored to use fewer table joins, reducing slow queries. Additionally, the link field introduces a resolvable_uri property and token, which returns a ready-to-use front-end link (like /#main-content) right out of the API instead of raw internal URIs, which will be a huge benefit for anyone using Drupal for decoupled and JSON:API-based use cases Applying recipes in Drupal 11.4 is significantly faster, reportedly twice as fast, and that includes installing Drupal CMS Drupal now supports Brotli compression, which should yield 15-25% better compression of CSS and JS assets Security Drupal 11.4 offers a new password hashing algorithm, argon2id, that will become the default in Drupal 12 later this year Also, the drupal/core-recommended package no longer strictly locks minor versions for critical dependencies like Guzzle, Twig, or Symfony Polyfills, making it easier to immediately receive important security updates Drupal's default robots.txt now blocks well-behaved search crawlers from indexing search queries, helping to solve a potential source of traffic overload on sites using faceted search Developer experience There's been a significant shift towards the adoption of PHP Attributes in recent Drupal releases, and 11.4 is no exception You can now define application routes directly within your PHP controller and form classes using the Symfony #[Route] attribute. This drastically reduces the need to jump back and forth into *.routing.yml files The new #[Bundle] attribute allows developers to define bundle classes directly, eliminating the need to write old-school entity_type_info or entity_type_info_alter hook implementations. All core .theme and .theme-settings.php files have been moved entirely to PHP classes. Support for legacy .theme files will be dropped in Drupal 13. Furthermore, dozens of core .module files have been fully converted into clean PHP classes Front controllers now leverage the symfony/runtime component to isolate bootstrapping logic from request handling, preparing the Drupal core architecture for advanced environments like FrankenPHP, known for its blazing-fast performance, among other features Drupal 11.4 introduces a native, extensible command-line tool (./vendor/bin/dr) built in partnership with Drush maintainers. This kicks off a transitional period where Drush commands will gradually be migrated to the core native binary Also, the new HttpKernelUiHelperTrait for kernel tests lets developers make mock HTTP requests and assertions without running the full Drupal site installer. This allows many traditional browser tests to be rewritten as much faster kernel tests Editor experience Drupal 11.4 includes the new Default Admin theme, a version of the popular Gin admin theme, now in core The Navigation module is now enabled by default, replacing the legacy toolbar CKEditor once again has a fullscreen button available without a contrib add-on, allowing editors to fully immerse themselves in a WYSIWYG element's content, great for working on long-format pieces Deprecations The initial 11.4.0 release actually removed a number of core recipes. They were since restored in an 11.4.1 release, but they are deprecated and will be removed from Drupal 12 Also on their way out are a number of modules, including Ban, Contact, Field Layout, History, Migrate Drupal and its UI, Search, Settings Tray, Shortcut, Telephone, Toolbar, and a flag module called layout_builder_expose_all_field_blocks. For themes, Claro, Stable 9, and Olivero are all deprecated, and will be moved from core. We'll include the meta issue about these deprecation in the show notes, and if any of these are important to you, it's worth tracking where they are on the path of moving to contrib

En este episodio de Atareao con Linux nos vamos a remangar para hablar de una de esas tecnologías que, una vez las dominas, te cambian la vida por completo: el Web Scraping asistido por Inteligencia Artificial.Seguro que te ha pasado alguna vez. Quieres comprar un producto concreto, como unas zapatillas de running (yo las cambio cada 800 kilómetros y es un goteo constante), o quieres extraer todas las recetas de cocina de una web para montarte tu propio planificador semanal. Lo ideal sería que estas páginas tuvieran una API pública para descargar la información de forma limpia. Pero la cruda realidad es que casi ninguna te lo pone fácil. Ahí es donde entra el scraping: la técnica de extraer la información directamente de la página web.En este episodio te cuento por qué el scraping clásico (ese que utiliza Beautiful Soup en Python y depende de identificar las etiquetas HTML y las clases CSS) tiene los días contados para tareas complejas. Basta con que un desarrollador cambie el diseño de la web para que tu script se rompa por completo. Además, con la llegada de las webs dinámicas, los tests A/B y los sistemas anti-bloqueo como Cloudflare, mantener un scraper tradicional es un auténtico dolor de muelas.La gran alternativa: Inteligencia Artificial en local¿Y si en lugar de pelearnos con el código fuente dejamos que un modelo de lenguaje (LLM) entienda la página exactamente igual que lo haría un humano? Un LLM comprende perfectamente qué es un "precio" o el "nombre de un producto", sin importar cómo esté maquetada la web ni el idioma en el que esté escrita. Y lo mejor de todo: ¡lo podemos hacer 100% gratis en local usando Ollama!Te detallo mis pruebas ejecutando modelos en mi Slimbook One utilizando únicamente la CPU (¡sin gastar un céntimo en nubes ni necesitar tarjetas gráficas carísimas!). Hablaremos de cómo rinden modelos como Llama 3.2, Qwen, Mistral y DeepSeek R1, y cuál es el punto de equilibrio perfecto para no eternizarnos esperando la respuesta.También te desvelo mi fórmula secreta para procesar la información. No podemos enviarle 2 Megabytes de HTML ruidoso a la IA. Te explico los 5 pasos que utilizo en Python para eliminar la basura (scripts, estilos, navegación) y reducir el HTML hasta en un 93%, permitiendo que el modelo extraiga los datos en segundos y nos devuelva un JSON estructurado impecable.Por último, vemos cómo montar un auténtico vigilante de ofertas automatizado en segundo plano. Un sistema que compare los precios de varias tiendas en paralelo.Capítulos del episodio:00:00:00 Introducción al Web Scraping con Inteligencia Artificial00:01:22 ¿Para qué sirve extraer datos? Ejemplos prácticos00:02:42 El gran talón de Aquiles del scraping tradicional00:04:31 La revolución de la IA: Entender la web sin saber HTML00:07:36 Los problemas habituales: Selectores rotos y webs dinámicas00:10:00 Cómo un modelo de lenguaje (LLM) procesa la información00:13:17 Cuándo elegir scraping clásico vs. scraping con IA00:15:28 Comparación de costes: Enfoque clásico, IA local e IA en la nube00:17:19 ¿Qué modelos usar? Pruebas con Llama, Qwen, Mistral y DeepSeek00:18:19 Detrás de escena: Mi script de Python y la limpieza del HTML00:21:05 Creando el prompt perfecto para extraer un JSON estructurado00:24:34 Ejemplo real: Comparativa paralela entre tiendas00:28:38 Diseñando un vigilante de ofertas automatizado (24/7)00:30:17 Casos de uso prácticos y mejoras para evitar bloqueos00:32:02 Cierre y detalles del próximo tutorial de scrapingMás información y enlaces en las notas del episodio

7/8/26Episode SummaryThe episode explains that a store's background color drives a subconscious snap judgment about a brand within about 50 milliseconds — before a visitor reads a single word — and that in 2026, Shopify stores are increasingly moving away from the long-standing default of pure white backgrounds.Why white is losing its grip. Pure white is clean, fast-loading, readable, and required by Amazon and Google Shopping — but it's become commoditized (making independent brands look like marketplace dropshippers) and causes eye strain on today's bright screens. The replacement trend is "elevated neutrals" — off-whites, warm creams, soft grays.Dark mode's advantages. Dark backgrounds create a "theater effect" that makes products pop, reduce eye fatigue for nighttime browsing, and save meaningful OLED battery life — but the episode warns against pure black (#000000), which causes black smearing and halation; deep charcoal like #121212 with softened text is the pro move.Brand-color backgrounds. High risk, high reward — Tiffany blue builds recognition and emotional immersion, but simultaneous contrast can distort how products look and drive returns.The recommended playbook. A hybrid approach: neutral backgrounds on collection grids where shoppers compare products, atmospheric color on product pages, delivered adaptively via the prefers-color-scheme CSS media query — with every change validated against WCAG 4.5:1 contrast requirements and A/B tested with an eye out for the novelty effect.Show LinksSabi Juice - https://sabijuice.com/Bixby Chocolate - https://bixbychocolate.com/Emerson Knives - https://www.emersonknives.com/Scorpion Percussion - https://scorpionpercussion.com/Authentic Vintage Posters - https://www.authenticvintageposters.com/Hexclad - https://hexclad.com/Google Battery Life Stat - https://wpswings.com/blog/dark-mode-in-ecommerce/WAVE Evaluation Tool - https://chromewebstore.google.com/detail/wave-evaluation-tool/Video & Transcripthttps://jadepuma.com/blogs/the-shopify-solutions-podcast/episode-189-why-shopify-stores-are-ditching-white-backgrounds 

Topics covered in this episode: Free-threaded Python: past, present, and future django-admin-site-search Qwen 3.6 27B is the sweet spot for local development A large batch of PEPs are finalized Extras Joke Watch on YouTube Show Intro Sponsored by us! Support our work through: Our courses at Talk Python Consulting from Six Feet Up Connect with the hosts Michael: Mastodon / BlueSky / X / LinkedIn Calvin: Mastodon / BlueSky / X / LinkedIn Show: Mastodon / BlueSky / X Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Tuesday at 7am PT. Older video versions available there too. Finally, if you want an artisanal, hand-crafted digest of every week of the show notes in email form? Add your name and email to our friends of the show list, we'll never share it. Calvin #1: Free-threaded Python: past, present, and future The GIL has prevented true multi-threaded parallelism in CPython since the beginning — multiple past attempts to remove it failed on performance grounds Sam Gross at Meta finally solved it; his work became PEP 703 and ships as free-threaded CPython today Python 3.13 was experimental with 20–40% single-threaded slowdown; 3.14 brought that to 0–10% Python 3.15 (October 2026) delivers a unified ABI — one extension binary works on both GIL and free-threaded builds Already >50% of the top PyPI binary wheels support free threading Wouters predicts free-threaded becomes the default between 3.16–3.20 (2027–2031), with the GIL eventually disappearing next decade Michael #2: django-admin-site-search via Adam Parkin A global/site search modal for the Django admin, by Ahmed Aljawahiry. Hit cmd+k anywhere in the admin and you get a command-palette-style search window, kind of like the one in VS Code. It doesn't just search one model's list page. It searches your entire site in one box: App labels Model labels and field attributes Actual model instances (your data) Two ways to search the instances: model_char_fields (the default): runs an __icontains across every CharField (and subclasses) on the model. Zero config, works out of the box. admin_search_fields: defers to each ModelAdmin's existing get_search_results(), so it respects the search_fields you've already set up. The part I like: it's permission-aware out of the box. Users only see results for the apps and models they actually have view permission on, so you're not leaking anything through search. Results appear as you type, with throttling/debouncing so you're not hammering the server on every keystroke, and it's full keyboard nav: cmd+k to open, up/down to move, enter to go. It's responsive, does dark and light mode, and it pulls Django's built-in admin CSS variables so it just matches whatever admin theme you're running. Under the hood it's Alpine.js, but bundled into static so there's no external CDN dependency. Setup is about what you'd expect: pip install django-admin-site-search, add it to INSTALLED_APPS, mix the AdminSiteSearchView into your AdminSite, and drop a few template includes into base_site.html. Supports Python 3.8 through 3.14 and Django 3.2 through 6.0, MIT licensed, and everything is overridable if you want to skip certain models, add TextField matching, etc. Calvin #3: Qwen 3.6 27B is the sweet spot for local development Qwen 3.6 27B is being called the first local model that genuinely competes as a general-purpose intelligence — benchmarks put it at roughly mid-2025 frontier level (comparable to GPT-5 / Claude Sonnet 4.5) Runs locally via llama.cpp; on an M5 MacBook Max with 8-bit quantization + multi-token prediction, it hits ~32 tokens/sec using ~42GB RAM 4-bit quantization gets it under 18GB, runnable on 32GB devices; Nvidia RTX cards run it even faster The dense 27B is recommended over the faster MoE 35B A3B — author prefers higher quality output over raw speed Privacy and reliability are the pitch: fine-tunable, can't be taken down, suitable for sensitive/proprietary data Author sees this as a stepping stone — frontier open-weight models like GLM 5.2 are now locally runnable with company-grade hardware, and smarter-still local models are coming Michael #4: A large batch of PEPs are finalized A bunch of PEPs went from accepted to final. 668, 687, 691, 699, 701, 703, 728, 770, 773, 829 But this wasn't them making their way into CPython. It's an admin sorta thing. (Thanks PyCoders) See the commit. Extras Calvin: More fun bling for your terminal this time - https://charm.land/ Michael: Follow up from pls, What the pls? Thanks Pito. Joke: BEMoji A production-grade utility and component framework built entirely on emoji class names via Jeff Triplett

Show DescriptionWhat to do when you have more ideas than time, getting new musical gear, nerding out and getting excited about things, the state of conferences in 2026, Cursor being bought, and Dave's got a minimum viable design system idea. Listen on WebsiteWatch on YouTubeLinks FFConf Figma Config 2026 SpaceX locks in $60 billion Cursor deal Google Antigravity Devon: An open-source pair programmer Introducing Composer 2 @function CSS at-rule A tale of two browsers Google's Prompt API SponsorsNotionWrite custom tools for Notion Agents that generate assets, query live data, and hit any API. Listen for incoming webhooks from any app, then run workflows with Notion Agents, pages, databases, and external APIs. All of this, on a hosted runtime. Workers are isolated sandboxes managed by Notion, so the code behind your syncs, tools, and workflows runs on our infra instead of your servers.

Today we are talking about Marketing, AI, and Drupal with guest Paul Johnson. We'll also cover Curated Colors as our module of the week. For show notes visit: https://www.talkingDrupal.com/559 Topics Paul's Current Projects Enterprise AI Summit Details Marketing the AI Initiative Partnering on Event Booths Drupal's Outside Perception What's Working Now Growing the Marketing Team How to Contribute Outside In Storytelling Case Study Examples AI Initiative Impact Roadmap and Launch Planning Finding New Adopters Where Pros Research Conference Pitch Story Local Event Playbook Funnel and Webinars Industry Guides and Demos SEO and AI Search Why Agents Avoid Drupal High Leverage Contributions Measuring AI Mentions Vibe Coders to Governance Fixing Misconceptions Resources Drupal AI Initiative home page Slack #ai-initiative-marketing Enterprise AI Summit Rotterdam AI Dev Summit Rotterdam Drupal AI TV We've curated a selection of the best presentations, workshops and demonstrations freely available to provide a practical way to stay informed about the latest innovations in Drupal AI. Drupal AI Webinars playlist Demos Ryan Whitcombe 1xINTERNET S1xSignals free AIO GEO assessment All things open World cancer day Guests Paul Johnson - pdjohnson Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Scott Falconer - managing-ai.com scott-falconer MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Have you ever wanted to allow editors on your Drupal site to choose styling from a brand-approved color palette? There's a module for that. Module name/project name: Curated Colors Brief history How old: created in Apr 2026 by Kyle Einecker (ctrladel) of True Summit Versions available: 1.0.0 which works with Drupal 10.3, 11, and 12 Maintainership Actively maintained Security coverage Test coverage Documentation - in-depth README Number of open issues: 2 open issues, neither of which are bugs Usage stats: 27 sites Module features and usage Curated Colors enforces brand consistency by replacing generic color text inputs or wide-open color pickers with a curated, visual swatch popover containing only pre-approved, named options It streamlines rebranding by storing abstract keys (such as brand-primary) instead of raw hex values (e.g., #0678be) in the database. That means updating a brand color in the future only requires a CSS or configuration change rather than a massive data migration Curated Colors is also extensible beyond colors. It functions as a generic visual variant selector. Site builders can repurpose it to let editors pick card layouts, button styles (like primary, outline, or danger), hero text alignments, or icon themes Editors can pick from neatly organized groups with human-readable labels and see a live preview swatch of their selection before saving Palettes are managed as exportable Drupal configuration. Each entry maps a machine key to a label, administrative hex preview, and optional custom CSS The module provides a curated_color field type and an accompanying swatch-based popover widget that can be restricted to specific palette groups. It also features a native curated_color_picker Form API element and integrates with the Canvas module via SDC annotations The field exposes properties like value, hex, style, and css, making it simple to output selections as classes, inline styles, or raw codes in Twig templates Finally, Curated Colors includes an example submodule providing a working SDC component and sample palette templates so you can see exactly how it's meant to be used

If you are a manager, a lead engineer, or anyone growing into more responsibility, this throwback episode is built for you. We keep hearing the same question, now louder than ever: "Why can't this go faster?" AI and agentic coding have made the literal coding step dramatically cheaper, so product leaders reasonably expect the whole pipeline to speed up. But it hasn't—and in today's short, focused episode I explore why. The answer isn't new at all. It's the theory of constraints, and it has everything to do with friction you may not be looking at. Speed Isn't the Story—Friction Is: When a fast component gets introduced into the pipeline, the instinct is to celebrate the velocity. But pay attention to what comes after. The real question is what keeps work from naturally flowing faster, and that lives in the friction, not the energy you're pouring in upfront. The Universal Bottleneck: I rarely claim universal truths on this show, but here's one: anything that looks like a pipeline will have a bottleneck. If you're not paying attention to it, it doesn't matter how fast every other step gets. Faster coding just exposes where the constraint really sits. The Two Places Friction Shows Up: For teams fully adopting agentic coding, the bottlenecks cluster in two spots—requirements gathering at the front, and verification, validation, and testing at the back. Rushed requirements upstream create even more painful rework downstream. Why Agents Punish Vague Specs: Human engineers fill in gaps by being close to the work. Agents fill in gaps too, but sometimes incorrectly. If your requirements aren't detailed, the agent guesses, and you pay for it in review. Spend more time in the planning phase, not less. The Foundation You Build On: Agents glob extra code onto a weak structure—unnecessary models, redundant endpoints, patterns that don't fit. A code base organized with clear conventions, good documentation in your CLAUDE.md or AGENTS.md, and dependable patterns lets the agent discover and extend rather than guess and hope. Specification and Validation Are Bookends: Good requirements translate directly into good tests. Acceptance criteria on one end, changes in the middle, validation on the other end—directly connected. Poor specification sitting on a poor structure guarantees poor execution and poor validation. Reframing Your Objections: Think scope creep is the problem? That's a requirements issue. Think you lack the talent? That's a foundation issue—because the engineer's job now is to cultivate the foundation so generated code enriches it instead of toppling it. This is not a new problem. We asked it of the internet, of web frameworks, of CSS. Now it's time to apply the same principles to agentic velocity: look at your requirements, your foundation, and your validation. Somewhere in those three is your bottleneck. I guarantee it.

TGB is in Italy and the girls have decided to adopt the CSS lifestyle, cigs, surf and sex...WICKED SWEET!!! Sarahs from far and wide tell the girls about their most chaotic girls' trip memories. Safe to say, don't fall in love on holiday...you might get robbed. One Sarah writes in about her Brian who has a hot date with HMP, and another Sarah can't get Brian out of her head...but is he still involved with his ex?New episodes every Wednesday! Email us your dilemma at hello@thegirlsbathroom.comFollow us on instagram @thegirlsbathroomJoin us on Patreon for an extra ep every week!! https://www.patreon.com/TheGirlsBathroom Hosted on Acast. See acast.com/privacy for more information.

The 25th episode of Circling Seattle Sports' weekly Seattle Kraken show, Keeping up with the Seattle Kraken, sees RJ of Emerald City Hockey and Darren of Sound of Hockey join CSS founder and editor-in-chief Charles Hamaker to discuss the news of the team trading for forward Mackie Samoskevich from the Florida Panthers and re-signing forward Bobby McMann to a six-year deal.

JDK 26 optimise la JVM dans ses moindres recoins, le SDK Java d'Agent2Agent passe en 1.0, Micronaut 5 est là. Côté terrain, un retour d'expérience après 40 jours à coder avec 100 % d'IA : génie ou junior, Alzheimer numérique et dette technique invisible. Pendant ce temps, GitLab restructure, Microsoft suspend ses licences Claude Code, et un développeur injecte un prompt destructeur dans sa lib JUnit. La révolution IA a un coût et les boites commencent à s'en rendre compte. Enregistré le 12 juin 2026 Téléchargement de l'épisode LesCastCodeurs-Episode-341.mp3 ou en vidéo sur YouTube. News Langages Les améliorations de performance dans le JDK 26 https://inside.java/2026/06/09/jdk-26-performance-improvements/ Côté bibliothèques, l'API LazyConstant (anciennement StableValue) fait son entrée en prévisualisation pour permettre une initialisation paresseuse, sécurisée pour les threads et optimisée par le mécanisme de constant-folding de la JVM. L'extraction de chaînes de caractères via MemorySegment::getString a été revue pour réduire considérablement les allocations intermédiaires et les copies en mémoire off-heap, accélérant fortement les traitements sur les chemins critiques (hot paths). La méthode générée automatiquement hashCode() pour les classes de type record a été optimisée par la JVM pour atteindre un niveau de performance équivalent à une implémentation écrite manuellement. Le ramasse-miettes G1 bénéficie du JEP 522 qui redessine sa table de cartes (card-table) afin de réduire les coûts de synchronisation des barrières d'écriture, offrant un gain de débit de 5 % à 15 % sur les applications manipulant énormément de références d'objets. Grâce au JEP 516 (Project Leyden), le cache d'objets Ahead-of-Time (AOT) adopte un format de flux agnostique, ce qui lui permet d'être compatible avec n'importe quel Garbage Collector, y compris le ramasse-miettes à très faible latence ZGC. Le démarrage de la JVM s'accélère par défaut lorsqu'aucune taille de tas n'est configurée, car HotSpot n'applique plus de pourcentage initial (InitialRAMPercentage) mais démarre directement avec la taille minimale (MinHeapSize) pour éviter d'allouer des métadonnées inutiles. Les threads virtuels gagnent en robustesse en étant désormais capables de céder la main (yield) pendant les phases d'initialisation des classes, éliminant ainsi le risque de famine des threads porteurs (carrier threads). Le compilateur C2 JIT améliore son modèle de coût pour la vectorisation des boucles (SIMD) et se montre maintenant capable de compiler et d'optimiser des méthodes dotées de listes de paramètres extrêmement longues. Librairies Release candidate du A2A Java SDK supportant versions 0.3 et 1.0 en même temps https://medium.com/google-cloud/a2a-java-sdk-1-0-0-cr1-released-f0c651ec9139 Dernière étape avant la GA : Toutes les fonctionnalités prévues pour la version 1.0 sont finalisées. Migration simplifiée depuis la Beta1. Compatibilité v0.3 : Ajout d'une couche de compatibilité permettant aux agents v1.0 de communiquer avec les systèmes v0.3 (via JSON-RPC, gRPC ou REST). Support natif pour Android (nouvel AndroidHttpClient). Uniformisation des clients HTTP pour garantir une cohérence entre les versions. Nouveau parseur SSE (Server-Sent Events) conforme aux spécifications. Ça y est, le SDK Java de l'Agent 2 Agent Protocol est sorti en version 1.0 finale ! (avec compatibilité v0.3 et v1.0) https://medium.com/google-cloud/a2a-java-sdk-1-0-0-final-released-10c05b6aee34 Lancement officiel : Sortie de A2A Java SDK 1.0.0.Final, la première version stable (GA) du protocole Agent2Agent. Objectif du protocole : Standard ouvert (Linux Foundation) permettant aux agents IA de communiquer, déléguer des tâches et collaborer, indépendamment du langage ou du framework. Interopérabilité : Introduction de l'Integration Test Kit (ITK) pour valider la compatibilité entre les SDK (Java, Python, TypeScript, etc.). Transports supportés : Support complet et équivalent pour JSON-RPC, gRPC et HTTP+JSON/REST. Alignement total avec la spécification A2A 1.0.0. Passage aux Java records pour l'immutabilité et moins de code répétitif. Architecture interne basée sur un MainEventBus pour garantir la persistance et éviter les conditions de concurrence. Intégration d'OpenTelemetry pour le suivi et la surveillance. Support d'Android et compatibilité descendante avec la version 0.3. Installation : Gestion des dépendances via Maven BOM (org.a2aproject.sdk). Sortie de Micronaut 5.0 https://micronaut.io/2026/05/20/micronaut-framework-5-0-0-released/ Lancement majeur : Disponibilité générale de Micronaut 5, incluant une refonte de plus de 70 modules et la plateforme BOM. Baselines techniques : Support de Java 25, Groovy 5, Kotlin 2.3 et GraalVM 25.0.3. Optimisations internes : Amélioration significative des performances au démarrage et réduction de la surcharge à l'exécution via une refonte du conteneur IoC et du traitement à la compilation. Architecture HTTP : Support stable de HTTP/3, nouvelle API de formulaires (multipart) et annotations de nullabilité (JSpecify) pour une meilleure interopérabilité Kotlin/IDE. Configuration : Nouveau système d'importation de configuration (remplaçant le Bootstrap Configuration) et validateur de schéma JSON intégré. Fiabilité : Nouvelles API programmatiques pour les politiques de retry et circuit breaker. Sécurité & Outils : Mise à jour majeure des dépendances (Jackson 3, Ktor 3), rafraîchissement du Panneau de contrôle et diagnostics AOT améliorés. Écosystème : Mises à jour complètes pour les bases de données (Data, SQL, R2DBC, MongoDB, Redis), le cloud (AWS, Azure, GCP, OCI) et les tests (JUnit 6, Testcontainers 2.0). Évolutions notables : Intégration HTMX dans Micronaut Views, retrait du support RxJava 2 et migration de divers processeurs d'annotations vers des modules dédiés. Comment rajouter un agent IA dans une app Android, avec le tout nouveau framework ADK pour Kotlin https://glaforge.dev/posts/2026/05/21/wiring-adk-kotlin-agents-in-an-android-application/ Guillaume a participé au développement et au lancement du nouveau runtime ADK pour Kotlin et Android https://developers.googleblog.com/adk-kotlin-android-building-ai-agents/ Tutoriel sur comment intégrer un agent ADK dans une app Dépendances : Ajout du noyau ADK (google-adk-kotlin-core) et du processeur KSP dans build.gradle.kts. Sécurité API : Utilisation de local.properties pour stocker la clé API Gemini et l'exposer via BuildConfig afin d'éviter le hardcoding. Définition de l'agent : Création d'un objet LlmAgent configuré avec le modèle Gemini, des instructions spécifiques et des outils (ex: GoogleSearchTool). Utilisation de InMemoryRunner pour gérer automatiquement le contexte et l'historique de la session. Implémentation de runAsync avec StreamingMode.SSE pour un retour en temps réel dans l'interface. Threading : Exécution des requêtes réseau sur Dispatchers.IO et mise à jour de l'état de l'interface utilisateur sur Dispatchers.Main. Comment développer et hoster des agents IA sur la plateforme d'agents managés de DeepMind https://glaforge.dev/posts/2026/05/21/managed-agents-with-the-gemini-interactions-java-sdk/ L'équipe DeepMind de Google a lancé une plateforme d'agents managés sur son API Gemini Interactions https://blog.google/innovation-and-ai/technology/developers-tools/managed-agents-gemini-api/ Guillaume a implémenté un SDK Java pour utiliser cette API Gemini Interactions, qui donne entre autre accès à tous les modèles mais aussi à cette plateforme managée d'agents IA Agents managés : Permet d'exécuter des agents autonomes qui raisonnent, planifient et exécutent du code dans des environnements isolés (sandboxes), sans gestion d'infrastructure par le développeur. Environnement distant : Utilise des espaces de travail Linux éphémères dans le cloud via le paramètre remote, permettant l'accès réseau et la persistance des fichiers sur plusieurs appels. Agents prédéfinis : Accès immédiat à des agents spécialisés comme deep-research-pro (recherche multi-étapes) ou antigravity (tâches de codage généralistes). Agents personnalisés : Possibilité de configurer ses propres agents avec des instructions système dédiées, des outils spécifiques (exécution de code, recherche Google) et des règles réseau (egress) personnalisées. Architecture basée sur les étapes (Steps) : Utilise une structure de données typée (Step, Content) pour suivre le raisonnement de l'agent, ses appels de fonctions et ses résultats en temps réel. Outils et Schémas : Inclut des utilitaires pour générer des schémas JSON complexes via une interface fluide (DSL), par réflexion Java ou par parsing JSON. Streaming réactif : Support natif des événements en temps réel (SSE) pour suivre la progression de l'agent et recevoir les deltas de contenu au fur et à mesure de la génération. Flexibilité : Fournit un gestionnaire de routage (InteractionsHandler) pour créer facilement des serveurs proxy ou des backends intermédiaires traitant les interactions Gemini. Spring Boot 4.1 https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-4.1-Release-Notes Support natif pour Spring gRPC permettant de créer et tester facilement des applications clientes et serveurs basées sur Netty ou des Servlets via HTTP/2 Introduction du lazy fetching pour les connexions JDBC via la propriété spring.datasource.connection-fetch=lazy afin de ne prendre une connexion du pool que lorsqu'un Statement est réellement exécuté Amélioration de l'auto-configuration de Jackson permettant de définir globalement les contraintes de lecture/écriture pour les formats JSON, XML et CBOR via des propriétés de configuration Sécurisation des clients HTTP bloquants et réactifs face aux attaques SSRF grâce à l'introduction d'un InetAddressFilter bloquant les requêtes sortantes vers des adresses spécifiques Améliorations majeures autour d'OpenTelemetry avec le support complet des variables d'environnement OTel, la possibilité de désactiver le SDK via une propriété globale et l'ajout du support SSL sur les exporters OTLP Ajout de l'auto-configuration pour l'utilisation de Spring Batch avec MongoDB incluant un nouveau starter dédié spring-boot-batch-data-mongo Auto-configuration des endpoints @RedisListener sans nécessiter la déclaration manuelle d'un RedisMessageListenerContainer Dépréciation du support de Apache Derby (projet arrêté), suppression définitive du mode layertools du JAR et réintroduction du support de Spock 2.4 (avec Groovy 5) Upgrade des dépendances majeures de l'écosystème avec notamment Spring Framework 7.0.8, Spring Security 7.1.0 et Micrometer 1.17.0 Outillage Vous êtes plutôt endive ou chicorée ? La librairie Chicory qui permet d'exécuter du code WASM à partir de son application Java est forkée et rejointe la Bytecode Alliance pour continuer son développement https://bytecodealliance.org/articles/endive-and-the-next-chapter-of-webassembly-on-the-jvm Annonce d'Endive : Nouveau projet hébergé par la Bytecode Alliance ; fork de Chicory (moteur WebAssembly pur Java, sans dépendance native). ​Objectif principal : Permettre aux développeurs Java d'intégrer, charger et déployer des modules Wasm nativement via les workflows Java habituels. ​Compilateur "Redline" : Intégration à venir de Redline (basé sur Cranelift) pour compiler le Wasm en code machine natif ; performances comparables à Rust/Wasmtime. ​Zéro dépendance (Java 25+) : Grâce à l'API standard Foreign Function & Memory (Project Panama), l'exécution à vitesse native se fait sans composants externes. ​Modèle de Composants (Component Model) : Support futur prévu pour consommer des composants (Rust, Go, JS, etc.) via des interfaces typées et sécurisées directement dans la JVM. ​Prochaines étapes : Fusion de Redline, conformité stricte aux specs Wasm (dont WasmGC) et amélioration du support WASI. Un visualisateur de sessions de travail avec Antigravity https://glaforge.dev/posts/2026/06/11/antigravity-brain-visualizer/ Un projet open source construit avec Micronaut, LangChain4j et GraalVM pour analyser les sessions de travail avec l'outil de développement agentique Antigravity (de Google) Analyse toutes les étapes, les requêtes utilisateur, les outils utilisés, les erreurs rencontrées, les réponses du modèle Gemini fait une analyse pour comprendre les moments clés de cette session de travail Outil buildé avec l'aide d'Antigravity lui-même SBX-Kits : des environnements de développement simplifiés pour les débutants (et les autres) https://k33g.org/20260501-sbx-kits.html Philippe Charrière (:whale: ) présente SBX-Kits (Sandbox Kits), une initiative personnelle visant à simplifier radicalement la mise en place d'environnements de développement pour les débutants, en éliminant la complexité d'installation des outils traditionnels. Chaque "kit" est une archive prête à l'emploi contenant un outil de développement spécifique (comme un langage, un framework ou une base de données) configuré pour s'exécuter de manière isolée et portable. La philosophie du projet repose sur le principe de "zéro configuration" et "zéro dépendance globale", permettant de tester une technologie ou de commencer à coder immédiatement sans polluer son système d'exploitation. L'approche technique s'appuie sur des scripts légers et des binaires portables pré-packagés, offrant une alternative plus simple et moins gourmande en ressources que les conteneurs Docker ou les configurations d'IDE complexes pour l'apprentissage. L'objectif à terme est de proposer un catalogue de kits couvrant les technologies courantes (JavaScript, Python, petites bases de données) pour faciliter les ateliers de programmation et le prototypage rapide. De nombreux kits sont disponibles sur https://github.com/docker/sbx-kits-contrib ghui: une interface utilisateur en ligne de commande (TUI) interactive pour GitHub https://github.com/kitlangton/ghui ghui est un outil en ligne de commande (TUI) écrit en Rust qui fournit une interface visuelle, interactive et rapide directement dans le terminal pour interagir avec GitHub. Il permet de gérer ses pull requests, ses issues et ses notifications sans avoir à ouvrir son navigateur web ou à taper de longues commandes avec la CLI officielle de GitHub. L'outil propose une navigation fluide au clavier, des raccourcis efficaces, et permet de réaliser des actions courantes comme valider une PR, ajouter des commentaires, attribuer des reviewers ou inspecter les logs des GitHub Actions. Conçu pour être extrêmement réactif, ghui s'intègre naturellement dans le flux de travail des développeurs adeptes du terminal et du mode "sans souris". Sortie de Homebrew 6.0.0 https://brew.sh/2026/06/11/homebrew-6.0.0/ Introduction du mécanisme de sécurité Tap Trust : comme les dépôts tiers (taps) peuvent exécuter du code Ruby arbitraire non sandboxé sur la machine, Homebrew demande désormais une confiance explicite de l'utilisateur avant d'évaluer ou d'exécuter leur code. L'API JSON interne devient le choix par défaut, offrant un système plus léger et beaucoup plus rapide pour les développeurs. Sécurisation renforcée de l'environnement avec l'implémentation du sandboxing sur Linux. Évolution des comportements par défaut basés sur un sondage utilisateur : le mode "ask" est activé par défaut pour les développeurs, affichant un résumé des dépendances et une demande de confirmation avant toute action de brew install ou brew upgrade. Améliorations notables des performances globales, notamment un boost de ~30 % sur la vitesse de la commande brew leaves et la parallélisation de la récupération des bottles (binaires) lors des mises à jour. Ajout du support initial pour la prochaine version d'Apple, macOS 27 (Golden Gate). Multiples optimisations pour brew bundle, incluant une gestion plus sécurisée des installations de paquets npm. Méthodologies Retour d'expérience très détaillé et 100% humain sur 40 jours avec une équipe 100% AI hormis le superviseur https://www.linkedin.com/pulse/jai-vir%C3%A9-mon-%C3%A9quipe-de-dev-pour-une-100-ia-pendant-40-luc-bonnin-jlgjf/ Voici le résumé en bullet points : Expérimentation de 40 jours : remplacer une équipe de dev par 100% IA agentique (Cursor) sur un vrai projet en production (playthatsheet.com, 200k lignes de code legacy) Chiffres bruts : 2,3 milliards de tokens consommés, 1 477 prompts, 260 564 lignes ajoutées (+145%), 59% du code final produit par l'IA ROI vertigineux à court terme : 9 mois de travail humain livrés en 40 jours, coût total 260$ d'abonnement + 15 jours de supervision, ROI x18 Profil psy de l'IA : Alzheimer (oublis de contexte), schizophrène (change de méthodo), ado de 12 ans (refait les mêmes erreurs), oscille entre génie et junior sans prévenir Effet iceberg : la dette technique ne disparaît pas, elle se camoufle et s'accélère ; hallucinations = bombes à retardement détectables uniquement par relecture humaine ligne par ligne Paradoxe du bateau de Thésée : perte de paternité et de maîtrise fine du code, baisse de l'autonomie du dev humain qui valide sans avoir construit Arnaque du "monkey money" : consommation de tokens opaque, non corrélée à la complexité (écart de 350% sur des prompts identiques), facturation imprévisible donc impossible à budgéter Syndrome du bazooka : les devs utilisent l'IA même pour changer une couleur CSS, atrophie progressive des compétences et coût écologique délirant Risque stratégique : dépendance irréversible aux vendeurs de tokens (Nvidia, Anthropic, OpenAI), business non rentable qui devra augmenter ses prix Conseil final : approche Pareto, garder 20% du temps en code "fait main", nommer un responsable stratégie IA, l'humain senior reste irremplaçable pour superviser Une libraries de test JUnit cache un prompt qui demande aux coding agents d'effacer les tests https://arstechnica.com/security/2026/05/fed-up-with-vibe-coders-dev-sneaks-data-nuking-prompt-injection-into-their-code/ Agacé par les « vibe coders », un développeur introduit une injection de prompt destructrice dans son code Le développeur de jqwik (un moteur de tests pour JUnit 5) a volontairement inséré une injection de prompt dans la version 1.10.0 de sa bibliothèque Java pour saboter le travail des agents d'IA. L'instruction injectée via la sortie standard (stdout) ordonne textuellement aux LLM d'ignorer les consignes précédentes et de supprimer l'intégralité du code et des tests jqwik du projet. Pour dissimuler cette action aux yeux des développeurs humains, le mainteneur a utilisé des séquences d'échappement ANSI qui effacent la ligne d'injection dans les émulateurs de terminaux interactifs. La modification a été découverte par un utilisateur qui a pointé du doigt les risques majeurs et disproportionnés pour les machines des utilisateurs, bien que certains outils comme Claude d'Anthropic aient détecté et bloqué la consigne malveillante. Face aux critiques de la communauté et aux accusations de comportement infantile ou potentiellement illégal, le développeur a mis à jour ses notes de version pour documenter explicitement son opposition à l'usage de son outil par des IA, avant de refuser tout commentaire supplémentaire sur conseil de son avocat. La réalité du rôle de Principal Engineer https://leaddev.com/career-development/reality-being-principal-engineer Le passage au rôle de Principal Engineer marque une transition majeure où les compétences techniques ne suffisent plus, l'impact se mesurant désormais à travers l'influence, la stratégie et la capacité à aligner la technique avec les objectifs business. Contrairement aux attentes, le quotidien est souvent marqué par une forme d'isolement, car le poste se situe à l'intersection de la direction (qui attend des solutions) et des équipes techniques (qui attendent des directives), sans appartenance directe à un groupe précis. Le rôle exige d'accepter une grande part d'ambiguïté et l'absence de retours immédiats, les projets et les décisions stratégiques mettant parfois des mois ou des années à porter leurs fruits. La gestion du temps devient un défi critique, nécessitant de savoir naviguer entre les sollicitations constantes, la présence en réunion et le besoin de préserver des moments de réflexion approfondie pour concevoir des visions à long terme. La réussite à ce niveau repose sur le développement de compétences humaines pointues (soft skills), notamment la négociation, la communication vulgarisée auprès des profils non techniques, et la capacité à faire grandir les autres ingénieurs par le mentorat. Sécurité Une attaque de la chaîne d'approvisionnement npm utilise binding.gyp pour compromettre des dizaines de paquets https://cybersecuritynews.com/binding-gyp-supply-chain-attack-compromises-dozens-of-npm-packages/ Une nouvelle variante du ver auto-propageable "Shai-Hulud", baptisée "Miasma", cible l'écosystème npm (et PyPI sous le nom de "Hades") en dissimulant son exécution dans le fichier binding.gyp au lieu des scripts classiques preinstall ou postinstall. La technique, surnommée "Phantom Gyp", exploite le fait que npm lance automatiquement node-gyp rebuild dès qu'un fichier binding.gyp est présent à la racine d'un paquet pour compiler des modules natifs C/C++, exécutant ainsi le code malveillant dès la commande npm install. L'attaque contourne la plupart des outils de sécurité traditionnels car l'injection s'appuie sur l'évaluation récursive de commandes (via la syntaxe ) ou directement sur la fonction eval() de Python sous-jacente à GYP, cachée sous n'importe quelle clé du fichier. Le script malveillant télécharge un runtime alternatif (Bun) pour échapper aux détections comportementales de Node.js, puis moissonne les identifiants et secrets des développeurs et des environnements CI/CD (npm, GitHub, AWS, GCP, Azure, Kubernetes, HashiCorp Vault). Plus de 57 paquets npm (dont le SDK serveur de Vapi ou des outils liés à l'IA) et des dizaines de paquets PyPI ont été infectés via des comptes de mainteneurs compromis, le ver republiant automatiquement de nouvelles versions vérolées en utilisant les jetons volés. Loi, société et organisation Restructuration chez Gitlab https://about.gitlab.com/blog/gitlab-act-2/ GitLab entame une restructuration majeure pour s'adapter à l'ère de l'intelligence artificielle agentique, incluant une réduction d'effectifs planifiée de manière transparente et ouverte. L'entreprise prévoit de réduire de 30 % le nombre de pays où elle maintient de petites équipes, d'aplatir sa hiérarchie en supprimant jusqu'à trois niveaux de gestion, et de réorganiser la R&D en une soixantaine d'équipes plus petites et autonomes. Les processus internes vont être revus en intégrant des agents d'IA pour automatiser les revues, les approbations et les passages de relais afin d'accélérer le rythme de travail. La stratégie repose sur la conviction que le logiciel sera bientôt écrit par des machines et dirigé par des humains, ce qui va multiplier la demande de logiciels et transformer le rôle des ingénieurs vers la résolution de problèmes complexes. Sur le plan technique, GitLab reconstruit son infrastructure sous-jacente (notamment Git) pour supporter la charge massive générée par les agents d'IA, tout en misant sur l'orchestration du cycle de vie, la centralisation du contexte des données et une gouvernance intégrée. Le modèle économique évolue vers un système hybride combinant les abonnements classiques et une tarification à la consommation pour le travail effectué par les agents d'IA. Un LLM local sur un mac pourrait coûter plus cher en électricité qu'un modèle hébergé sur OpenRouter dans le cloud https://www.williamangel.net/blog/2026/05/17/offline-llm-energy-use.html Conclusion : L'inférence locale sur Mac M5 Max est 3x plus chère et 2x plus lente que le cloud (OpenRouter). Électricité : Négligeable (~0,02 $/heure pour 50-100W). Matériel (Le vrai coût) : Achat du Mac à 4 299 $; l'amortissement sur 3 à 5 ans plombe la rentabilité horaire. Coût au million de tokens (Gemma 4 31b) : Mac M5 Max : 0,40 à4, 79 (pour 10-40 tokens/s). OpenRouter : 0,38 à0, 50 (pour 60-70 tokens/s). Verdict pro : Le temps humain perdu à cause de la lenteur locale coûte infiniment plus cher que les tokens cloud. Privilégier les API (Anthropic, OpenRouter). Ai didn't kill your junior pipeline https://andrewmurphy.io/blog/ai-didnt-kill-your-junior-pipeline-you-did L'IA n'a pas tué le recrutement des juniors, les entreprises l'ont fait elles-mêmes, par effet de mode. Sans juniors, pas de futurs seniors : on retire l'échelle qui nous a tous fait monter. Tout le monde pêche dans le même bassin de seniors sans le réapprovisionner, pénurie garantie dans 3-5 ans. Une équipe 100% senior + IA est fragile : un départ et tout le savoir tacite s'évapore. Les juniors posent les "pourquoi ?" qui révèlent les bugs et processus absurdes ; l'IA, elle, exécute sans questionner. Les seniors s'atrophient aussi en déléguant leur réflexion à l'IA, pince à double effet sur les compétences. Dépendre des outils IA, c'est sous-traiter sa stratégie talents à des fournisseurs dont les prix vont tripler. Solution : redéfinir le rôle junior (revue de code IA + mentorat), pas le supprimer. Les rapports internes de Microsoft révèlent la crise des coûts de l'IA : les agents coûtent plus cher que les employés humains https://fortune.com/2026/05/22/microsoft-ai-cost-problem-tokens-agents/ Des données et rapports internes chez Microsoft et d'autres géants de la tech ébranlent la promesse de rentabilité de l'IA, révélant que le déploiement d'agents autonomes à l'échelle de l'entreprise revient souvent plus cher que de payer des humains pour le même travail. Le modèle de tarification à l'usage (basé sur les tokens) se heurte à la nature même des architectures agentiques : contrairement à un simple chatbot, un agent boucle, enchaîne les appels d'outils, crée des sous-agents et auto-évalue son code, ce qui multiplie la consommation de tokens par un facteur de 5 à 30, voire jusqu'à 1 000 fois pour des tâches de programmation complexes. L'impact financier sur les budgets de calcul cloud est immédiat ; par exemple, Uber a entièrement épuisé l'intégralité de son budget annuel 2026 dédié au codage par IA en l'espace de seulement quatre mois. Face à cette explosion des coûts, des retours en arrière drastiques sont observés : Microsoft a ainsi commencé à suspendre une grande partie de ses licences internes Claude Code pour rediriger d'urgence ses milliers de développeurs vers sa propre solution moins onéreuse, GitHub Copilot CLI. Les directeurs techniques (CTO) et acheteurs de solutions logicielles qui ont signé des contrats pluriannuels basés sur des projections de réduction de masse salariale se retrouvent pris au piège, les gains réels de productivité ne parvenant pas à compenser les factures d'infrastructure exorbitantes. Conférences La liste des conférences provenant de Developers Conferences Agenda/List par Aurélie Vache et contributeurs : 11-12 juin 2026 : DevQuest Niort - Niort (France) 11-12 juin 2026 : DevLille 2026 - Lille (France) 12 juin 2026 : Tech F'Est 2026 - Nancy (France) 15 juin 2026 : Jupyter Workshops: Demystifying MyST Markdown in Education - Orsay (France) 16 juin 2026 : Mobilis In Mobile 2026 - Nantes (France) 17-19 juin 2026 : Devoxx Poland - Krakow (Poland) 17-20 juin 2026 : VivaTech - Paris (France) 18 juin 2026 : Tech'Work - Lyon (France) 22-26 juin 2026 : Galaxy Community Conference - Clermont-Ferrand (France) 23-24 juin 2026 : MWCP 2026 - Paris (France) 24-25 juin 2026 : Agi'Lille 2026 - Lille (France) 24-26 juin 2026 : BreizhCamp 2026 - Rennes (France) 26-27 juin 2026 : LeHACK - Paris (France) 27 juin 2026 : Asynconf - Paris (France) 2 juillet 2026 : Azur Tech Summer 2026 - Valbonne (France) 2 juillet 2026 : MCP Connect Travel Edition - Paris (France) 2-3 juillet 2026 : Sunny Tech - Montpellier (France) 3 juillet 2026 : Agile Lyon 2026 - Lyon (France) 6-8 juillet 2026 : Riviera Dev - Sophia Antipolis (France) 28-30 août 2026 : State of the Map - Champs-sur-Marne (France) 4 septembre 2026 : JUG Summer Camp 2026 - La Rochelle (France) 10-11 septembre 2026 : Nantes Craft - Nantes (France) 17 septembre 2026 : dotAI - Paris (France) 17-18 septembre 2026 : API Platform Conference 2026 - Lille (France) 18 septembre 2026 : WordCamp Bretagne - Rennes (France) 18 septembre 2026 : dotJS - Paris (France) 18 septembre 2026 : WordCamp Bretagne - Rennes (France) 22 septembre 2026 : Salon Data 2026 - Nantes (France) 22-23 septembre 2026 : Agile en Seine & IA 2026 - Paris (France) 24 septembre 2026 : OWASP AppSec Days France 2026 - Paris (France) 24 septembre 2026 : PlatformCon Paris - Paris (France) 24 septembre 2026 : React Native Connection 2026 - Paris (France) 24-26 septembre 2026 : Paris Web 2026 - Paris (France) 25 septembre 2026 : SAP Inside Track Paris 2026 - Paris (France) 28-29 septembre 2026 : 4th Tech Summit on AI & Robotics - Paris (France) & Online 1 octobre 2026 : WAX 2026 - Marseille (France) 1-2 octobre 2026 : Volcamp - Clermont-Ferrand (France) 2 octobre 2026 : DevFest Perros-Guirec 2026 - Perros-Guirec (France) 5-9 octobre 2026 : Devoxx Belgium - Antwerp (Belgium) 8-9 octobre 2026 : Forum PHP 2026 - Marne-la-Vallée (France) 12 octobre 2026 : Dev With AI - Paris (France) 22-23 octobre 2026 : Agile Tour Bordeaux 2026 - Bordeaux (France) 26 octobre 2026 : Agile Tour Montpellier - Montpellier (France) 27-29 octobre 2026 : Directions EMEA 2026 - Paris (France) 29-30 octobre 2026 : BDX I/O 2026 - Bordeaux (France) 29-30 octobre 2026 : Agile Tour Nantais 2026 - Nantes (France) 29 octobre 2026-1 novembre 2026 : Pycon FR - Biarritz (France) 30 octobre 2026 : Cloud Nord 2026 - Lille (France) 4-5 novembre 2026 : Devoxx Morocco - Casablanca (Morocco) 14-15 novembre 2026 : Capitole du Libre - Toulouse (France) 19 novembre 2026 : DevFest Toulouse 2026 - Toulouse (France) 19 novembre 2026 : Agile Laval 2026 - Laval (France) 19 novembre 2026 : OVHcloud Summit - Paris (France) 19 novembre 2026 : Codeurs en Seine - Rouen (France) 27 novembre 2026 : DevFest Paris 2026 - Paris (France) 1-3 décembre 2026 : Apidays Paris - Paris (France) 2-3 décembre 2026 : Cloud Native AI Summit Europe - Paris (France) 4 décembre 2026 : DevFest Lyon 2026 - Lyon (France) 4 décembre 2026 : DevFest Dijon 2026 - Dijon (France) 9-10 décembre 2026 : OpenSource Expérience - Paris (France) 9-10 décembre 2026 : DevOps REX - Paris (France) 10 décembre 2026 : KCD Provence - Aix-en-Provence (France) 7-9 avril 2027 : Devoxx France 2027 - Paris (France) 3 juin 2027 : Cloud Native Days France 2027 - Paris (France) Nous contacter Pour réagir à cet épisode, venez discuter sur le groupe Google https://groups.google.com/group/lescastcodeurs Contactez-nous via X/twitter https://twitter.com/lescastcodeurs ou Bluesky https://bsky.app/profile/lescastcodeurs.com Faire un crowdcast ou une crowdquestion Soutenez Les Cast Codeurs sur Patreon https://www.patreon.com/LesCastCodeurs Tous les épisodes et toutes les infos sur https://lescastcodeurs.com/

O paulistano Fábio passou a infância achando que seria desenhista, até que uma apresentação na escola despertou seu interesse por engenharia e o levou à Poli-USP. Lá, começou pensando em engenharia ambiental, passou pela elétrica e acabou escolhendo computação, área com a qual já tinha algum contato por meio dos pais e das primeiras experiências com HTML e CSS.Depois de quase dez anos trabalhando no Brasil, uma oportunidade na Amazon abriu as portas para o Japão, onde ele também pôde encurtar a distância de um relacionamento que havia começado em Taiwan. Mais tarde, em busca de projetos com maior impacto, mudou-se para Seattle, nos Estados Unidos, antes de deixar a empresa, tirar um período sabático e se estabelecer em Taiwan.Neste episódio, Fábio detalha essa trajetória, e comenta as diferenças culturais entre todos esses países e o Brasil, além das particularidades de se morar na terra onde mal se tem férias.Fabrício Carraro, o seu viajante poliglotaFabio Gusukuma, Engenheiro de Software na Stripe em Taipei, TaiwanLinks:LinkedIn fo FabioTechGuide.sh, um mapeamento das principais tecnologias demandadas pelo mercado para diferentes carreiras, com nossas sugestões e opiniões.#7DaysOfCode: Coloque em prática os seus conhecimentos de programação em desafios diários e gratuitos. Acesse https://7daysofcode.io/Ouvintes do podcast Dev Sem Fronteiras têm 10% de desconto em todos os planos da Alura Língua. Basta ir a https://www.aluralingua.com.br/promocao/devsemfronteiras/e começar a aprender inglês e espanhol hoje mesmo! Produção e conteúdo:Alura Língua Cursos online de Idiomas – https://www.aluralingua.com.br/Alura Cursos online de Tecnologia – https://www.alura.com.br/Edição e sonorização: Rede Gigahertz de Podcasts

Show DescriptionHow do you estimate how long a task or project is going to take? Is it easier or more difficult with AI's help? Were web components a mistake? What do we think about Cloudflare's EmDash now? And are lifetime offers a good or bad thing in the dev community? Listen on WebsiteLinks Keyframes, Cash, and CodePen w/ Shaw - Whiskey Web and Whatnot Meeting Design - For Managers, Makers, and Ever :host CSS pseudo-class - CSS | MDN Introducing EmDash WP Migrate SponsorsMacroMacro is a tool to cut through the noise - It's a workspace built for engineers; One place for all your emails, tasks, team chat, and documents. Sign up at Macro.com and get $100 of your subscriptions using code SHOPTALK100

It’s Old School Kingfish Shootout Saturday! Capt. Kirk was doing OSR with his son, and Capt. Kevin was busy vying for the big money, so Jeff brought in Tru Luvin’ Fishing’s Domenic Paniccia and Rick Hall to fill the chairs and have some fun. Coverage began with the one and only Paul Dozier, who gave everyone the complete rundown on the tournament, and continued throughout the morning with calls from a bunch of Old School anglers – Harley Bryan from CSS, Dave Edwards, Capt. Chris Stevens, “Mullethead” Paul, and more. Here’s the bonus: not only will you hear reports about how they’re doing, but you’ll be able to pick up a lot of tips – you might need to listen to this one with a notepad. The Old School was the headline for this episode, as expected, but when you have Rick Hall in the house, you gotta talk hunting, too. So if you need a little hunting fix, you have that in this one as well. Here's your L.V. Hiers Inc gear tip of the week: Don't get caught without gas! Bring a 5 gallon gas can just in case! In fact, get yourself a few of these Flo-Fast gas cans…and according to Jeff, you have to get the pump, too! Here's your Ring Power Cat tip of the week! Kingfish season means trolling. The Dave Workman Jr. Pro Series Duster rigs are really helpful at times to engage in a reactionary strike! Here’s your KirbyCo Builders’ Cooking Tip of the Week: Captain Kirk wants to try making his own butter! Click here to find out how to do it yourself! Facebook

Most people think selling software means building an app. It doesn't. A static HTML, CSS, and JS file solves real problems for local businesses, costs nothing to build with Claude's free tier, and sells for $200 a pop with the right framing. This episode walks through the whole process — what kinds of businesses buy this, what you actually hand them, and how to price and pitch it without a portfolio or a product page.

Introducing Russell Aaron I didn't learn WordPress at a fancy college or career academy. I graduated from the University of YouTube. My internship was the Las Vegas WordPress Meetup and WordCamp Vegas. The rest I learned building mortgage company platforms, working for casinos, inside managed WordPress hosts, and at some of the best WordPress development and support shops on the planet. Show Notes For more on Russell, check out his website: https://russellenvy.com Transcript: Topher DeRosia: All right. Here we go. Hey folks. Russell Aaron: And three, two, one. Topher DeRosia: Hey folks. Welcome to Hallway Chats. I’m Topher, and I’m here with Russell Aaron. I assume I pronounced that right, because it’s not that hard, but you never know. Russell Aaron: You know, so many people call me Aaron. They’ll tag me and they go, “Thanks, Aaron.” And I’m like, “You know, it’s Russell, but it’s cool.” Topher DeRosia: Yeah, nice. All right. Well, I saw a post on LinkedIn the other day from you talking about podcasts having the same people on episodes all the time. I thought, “Oh, I gotta have that guy on my podcast.” Because then you can’t go on any other ever again, because then you’ll be that guy. Russell Aaron: Maybe. Topher DeRosia: So, I snooped a little. You live much closer to me than I expected. Have we met? Did we meet at a WordCamp? Russell Aaron: I think we met at WordCamp Ann Arbor one year. Topher DeRosia: Oh, okay. I went to a whole bunch of those. Russell Aaron: Yeah. I think I spoke 2018, something like that. Topher DeRosia: Yeah. I was probably there. Russell Aaron: Yeah. Topher DeRosia: All right. So tell me where you live, what you do, all that kind of stuff. Russell Aaron: I currently reside in Indianapolis, Indiana, and I am just freelancing as of right now. You know, I live in a pretty small town where it’s kind of old school WordPress, if you will. Anyone who is worth their salt keys will remember a day when websites were not responsive or a business has a cousin of a friend of a brother who builds websites and, “Hey, he’s working on it,” and three years later, there’s still no new website. I kind of live in a town where I’m kind of getting back to my grassroots, where I stay up late at night with my insomnia, and I will roll up to a business and I will say, “Your new website can look like this today. If you pay me this much money, I will install it today, and this is your new website.” And it’s got your updated menu, and it’s responsive, and it works on mobile, and we can connect it to AppPresser and make it an app and stuff like that. So I’m kind of reliving the glory days of what I remember WordPress to be. Topher DeRosia: I’m also freelancing right now, sort of by choice, sort of not by choice. Somebody I’m married to would rather I had regular pay and insurance. Russell Aaron: Heard that. Topher DeRosia: Are you in the same boat, or did you do this on purpose? Russell Aaron: I did this on purpose. I was not working for the man, but I was working with some people. I’m over the tiny little granular things that somebody can fire you over. Like they’re watching if your mouse moves or they’re watching if you haven’t logged in. There’s just no more trust, I feel like, in so many cases. And so I know that I can do things better on my own, and I’m going to. Topher DeRosia: I have to admit, I love the freelance life. It is pretty special. Russell Aaron: Right. It’s almost like… what’s that movie? The 40-Year-Old Virgin, where they are making a website and they’re like, “Hey, Spider-Man 3’s on in five minutes. Let’s go watch it.” Like they totally ignore their job and they just go watch this movie now. It’s kind of like that. Topher DeRosia: Yeah. Yeah. For me, it’s doing stuff with my wife. She has a day job, but it has kind of chaotic hours and not specific days of the week. And so I work when she does, which sometimes is Saturday and Sunday, and then I just don’t on Tuesday and Thursday. That’s pretty great. Russell Aaron: I’m kind of in the same boat. My wife has a wonderful job, and she is with a great group, and she does global advocacy. I mean, she just deals with people that are happy with the product, and she keeps them happy. She does lots of stuff like that. I’m kind of the same thing, where their company is now starting to get into AI, and they have so many questions, and I’m over here building things with AI and doing things like that. So I’m not exactly consulting, but my ideas are going into their company through my wife. Topher DeRosia: My wife works at a grocery store, and they have a cash machine they use in the back office that runs Linux. Russell Aaron: Oh, wow Topher DeRosia: And the IT guys had to come in and do some work on it, and she saw the screen and she’s like, “Oh, is that Linux?” And I’m like, “Who are you, and what do you know?” Super nerd. So what’s your company name? Do you have one, or is it just WP Pro Support? Russell Aaron: WP Pro Support. Topher DeRosia: WP Pro Support. Okay. Do you concentrate more on support, or do you build more? Russell Aaron: I have been doing support since 2011. I formed my very first support company, and I launched it the same day that Shane Sanderson launched Maintainn. My buddy, who you might know, John Hawkins, I was at the Vegas WordPress Meetup Group, and I had the idea in Vegas WordPress Meetup Group where there’s 70 people sitting right here behind me and they all want help. And I was like, “How do I do this?” So I built my first thing where I gave everybody free-for-life support, and they were my test group, if you will. And they helped me work out my bugs and tickets, and they helped me work out how I actually operate and do stuff like that. Then when I launched it, literally that day, John goes, “Wait, have you seen this?” And we had no idea about each other, but we literally launched them the same day. Fast forward three years down the road, I ended up working for Maintainn when it was owned by WebDevStudios. But everything I’ve done in WordPress has been support, whether I’ve worked for a mortgage company, a casino in Vegas, hosting with Liquid Web, doing stuff with NerdPress or AppPresser. Everything I’ve done is support. That’s really where my passion is because I remember what it’s like being a first timer. I think that there is a huge market potential here of people are always going to be new. I don’t care who you are. There’s always somebody new walking in the door, and there has to be a person who will sit down and say, “Come here, I’ll hold your hand.” And I am that person. I always try to look at WordPress from that lens is if a new person is looking at this today, are they going to be happy? Are they going to be confused? And I go from there. So currently today I’m transitioning away from support as we know it, where you write a ticket and then somebody on the other end is like, “Hey, I fixed your site,” or whatever. And I’m transitioning to a new product that I’m working on. So I’m going to be getting away from traditional support, but I’m still going to be doing things in the support space, if that makes sense. Topher DeRosia: Yeah, that makes sense. When I first got into WordPress, it was 2010, and custom post types were brand new. Russell Aaron: Right? Topher DeRosia: And I was out of my element with WordPress. I did not know what I was doing, but I did know PHP, and no one else knew post types yet. So when it comes to that, I was on an equal footing, and that was my way in. That was my leverage. I made a lot of money in the early days just building custom post types. Russell Aaron: Custom post types and single-posttype.php or whatever. Yeah. Topher DeRosia: So I was a competent PHP guy who didn’t know WordPress. And I feel like we’re in kind of the same transition space right now with AI, where we have tons of competent WordPressers who don’t really know AI yet. I think there’s a great space for that, teaching our friends, teaching everybody we’ve known for 10 years in WordPress. You know what I mean? Russell Aaron: I do. That’s one of the things that I really love about WordPress is that… let’s take the new 7.0 that just came out, I think it re-leveled the playing field. Before this came out, there were people that were ahead of others when it comes to patterns or blocks or the command palette and stuff like that. But now I think with this, we’re back to an even playing field because every… I mean, not exactly. There’s still some people who know AI a lot better than others, but you’re always five minutes ahead of somebody and five minutes behind somebody else. Topher DeRosia: Oh, yeah. Russell Aaron: But I do think that with 7.0, a new level playing field has come out. And now is the time to start learning, or you got to wait until 7.1 comes out where that new level playing field comes out. But that’s what I love about WordPress is that it continues to happen. Like you said, CPTs. I still love CPTs. I think they’re one of my favorite things. I look at all of these features, you know, page builders, another time when the playing field was leveled again. Now you learn page builders and then shortcodes and then this and then that. I think that’s the one gift that WordPress keeps giving is that you might be out of date six months from now, but then 7.1 comes out and you’re caught right back up. Topher DeRosia: Right. Yeah. And while you’re five minutes ahead, you quick do a WordCamp talk. Russell Aaron: Yes. Yeah. Topher DeRosia: For that long, you know more than other people, right? Russell Aaron: At least it’s on video, right? Topher DeRosia: Right. I was an expert for a minute and a half. Russell Aaron: That was my 15 minutes of fame. Topher DeRosia: What is your WordCamp life like these days? When was the last one you went to? Russell Aaron: The last one I went to was in Vegas, 2018. It was at the Plaza Hotel, which I worked at. When John was putting that together, in Vegas we had a wonderful space, and it was called The Innevation Center, and it was at a data facility called Switch. And they donated so much to us, and we are so grateful to them. And then they kind of had a change in their policy where they weren’t doing things, and then they overpriced how much it would cost to hold events and stuff like that. I was working at a hotel, and so we had this giant convention space, if you will. And so because I was able to pull some strings, we got a great, great discount, all food paid for. I mean, all of it. So that was my last WordCamp. The after party was on top of a pool deck, and there was pickleball courts, and there was a pool, and there was an open bar. I mean, it was rad. That was my last one. I have kids now. My kids are seven and eight and so my WordPress travels have slowed. No, I’m sorry. I take it back. WordCamp US last year was my last one, where we went scorched earth. That’s what I call it. I call it WordCamp scorched earth. Topher DeRosia: I was there for that one. I used to go to a lot every year. Go to- Russell Aaron: Five, six? Topher DeRosia: Five and 10. But since COVID, I think maybe just US every year. It’s weird to just go to one. Russell Aaron: It is. And just US, it’s almost like we used to have what I used to call regional events, where I lived in Vegas, I would hit up WordCamp Orange County, then I’d hit up San Diego, then we’d hit up LA, and then we’d make our way up to Portland, and then maybe if San Francisco did one, and then Phoenix. I did all my regional stuff. And then every once in a while I would venture… I mean, I love WordCamp Minneapolis. Love the people up there. Love so much about that event. Used to do that a lot. What’s the one in Ohio that I used to go to? Topher DeRosia: In the teens, there were five in Ohio. And being in Michigan, I used to just cruise down there. Russell Aaron: It’s a three-hour, three-and-a-half-hour drive, huh? Topher DeRosia: Yeah. Russell Aaron: About that. Yeah. Topher DeRosia: At the time, I was working for a company that was paying me to go to WordCamps. I had to make the case for each one, but it was a really simple case for all the Ohio ones because I didn’t need a plane ticket. I just drive over there. It’s like five in Ohio. There was Ann Arbor, there was Detroit, there was Grand Rapids, there was Chicago. I mean, there was almost 10 WordCamps within a three-hour drive of me. Russell Aaron: That’s beautiful. Topher DeRosia: It’s just not there anymore. Russell Aaron: I was very fortunate to work for companies like WebDevStudios, where I could tell them, “Hey, I got into WordCamp Minneapolis. I’m going to speak there.” And because I’m speaking there, they would reimburse me X amount of dollars for something, and then they would sponsor the WordCamp, and then they would make a thing out of it. I mean, I was very fortunate in being able to do that. Then I worked with a really great company called NerdPress, and they are a fantastic group of people that do the same thing. And then I ventured out into different straits, and it was very much different. I’ll say that much. Topher DeRosia: Yeah. Those are good times. Russell Aaron: It’s almost like… the way that I put it is it’s like we all graduated. We all did our four years of college, we all graduated, and now we went to our temp jobs or we went to our internships. Like the band broke up. Topher DeRosia: Yep. Yeah, it is a lot like that. I have seen generations of WordPressers. There was all the crew before 2010 that were downloading zip files and hacking themes to even get them to run. Then there was after 2010, and custom post types were new and stuff. And then there’s the whole Gutenberg generation that never experienced all that crazy theme stuff. Russell Aaron: I mean, you tell people that child themes were so new that people didn’t even grasp the concept of a child theme, and today it’s so baked in. It’s not even something that people think about. It’s just you install this and the child theme, and it’s a thing. But I remember writing those by hand. Topher DeRosia: Yeah. No kidding. Then to a certain extent, not even having child themes anymore because nothing is stored on the file system. Russell Aaron: I love it. I love it. In my very first WordCamp talk in Vegas 2012, I made a prediction that everything was powered by the theme. Everything used to… I mean, that’s as far as I go back is every template was the same. It was left column, right sidebar, header, and every page, whether you liked it or not, looked like a blog post. And it wasn’t full-width, responsive. I remember a lot of that. And then corporate themes came out, and then cupcake themes came out, then lawn company themes came out, and then the rise of Envato and stuff like that. That’s a good name for a band, The Rise of Envato. Topher DeRosia: I’d go see them. Russell Aaron: But all that stuff comes out. And then you look at it now and it’s like, that seems so far away. I still remember the day that I learned about child themes, and I’ve never forgotten that. And I think, coming back full circle, that’s why I stay in this beginner support space because I’m kind of keeping that nostalgia around, I guess. Topher DeRosia: Yeah. There’s a lot of joy in watching people’s eyes light up when they get it. Russell Aaron: That’s the best part is just telling people what’s possible. When they’re frustrated with something and you go, “Oh, hey, Gravity Forms can do that.” And they’re like, “Wait, what?” And I’m like, “Yeah.” And they can also do… And I just start naming stuff. And I show all 50 extensions that they have and they’re just like, “Wait, what?” And I’m like, “Yeah.” I’m like, “This starts getting radical when you’re into it.” Topher DeRosia: There’s something I miss from old WordPress that I don’t see in modern WordPress. It might not be a thing. And that is dramatic new styling with a theme the instant you install it. My wife is not a computer person and does not care about computers. She loves design stuff. There was a time we used Winamp. Russell Aaron: Wow. Topher DeRosia: And she loved getting skins for Winamp. And she would download 30 in a day and try them all out. And then when I set her up for the blog the first time and showed her the theme repo on .org, this is in 2011, she would literally spend a day just downloading theme after theme after theme. Russell Aaron: Same way. Topher DeRosia: And you just install it and poof, your site looks amazingly different. These days, I mean, you install something like Kadence or GeneratePress or Ollie or any of them, really, and it’s kind of a blank canvas. Russell Aaron: It’s very minimalist. It’s very minimalist. Topher DeRosia: I miss the ability to say, “I feel like making a change today,” and two minutes later, your site looks completely different because you’re using… Russell Aaron: Couldn’t agree more. Couldn’t agree more. I mean, I look back at old pictures from when I would host the meetup group in Vegas, and there’s pictures of me talking, and then on the screen behind me is my old site, and it was this old layout. I bought the theme from Envato because I was just fascinated with it. It was everything that I wanted it to look like. But same thing is now when you change your theme from this one to that one, that dark grunge kind of thing is gone, and now you’ve got this bootstrap-looking thing or whatever. I agree with you. I think that comes from my days of being in MySpace. That’s how I got started with all this. So you could change your MySpace template like that, and I think that’s where it comes from, at least for me. Topher DeRosia: I haven’t even looked into it. Can you make a Gutenberg-based blog theme that has a very striking look and just release it? And then, I don’t know, just release a whole bunch of them like in the old days? Theme shops had 35 themes for sale, and they all looked different because they were all totally different themes. Russell Aaron: I remember there was a day on Envato where it was the same theme, it was just rebranded. So it was like theme name 1.0, and it was called Atlas. And then it’s the same theme but in orange, and now it’s 1.2, and it’s called Dungeon or something. And then we have 1.3 again. Same theme, same framework, but each version was named something different. It made that developer look like they had five different products instead of just one over and over. Now you look at something like a page builder, and it’s like, “We’ve got 500 different templates in one thing.” I can’t do that. I think that’s too much for me. Topher DeRosia: It’s like the days of the CSS Zen Garden. Russell Aaron: Right. Topher DeRosia: HTML is the same, CSS changes. Before I used WordPress, I built my own blog system. Russell Aaron: Oh, wow. Topher DeRosia: It never got super advanced, but I used it for 10 years. One of the things you can do in your HTML is register alternate stylesheets. It’s the same tag, it’s just an alternate word in there. And then in Firefox, at least, you can go under “view Page Style”, and they would all be listed there, and you can just choose different themes. I figured out the JavaScript, even though I didn’t know JavaScript. I figured out the JavaScript to make a little dropdown box in my sidebar so my visitors could say, “Oh, I want to change my theme here.” I never figured out how to do that in WordPress because everything was so tied to style.css. I didn’t know how to make a different one be the main one. But that’s something else I miss in WordPress is the ability to just so dramatically and dynamically change your design because your content is structured so well. Russell Aaron: You know, not only that, but I really liked the websites where there was a demo, and then it gave you a basic username. The username was demo, the password was demo. But then the one thing I never figured out was how every 24 hours the site would just reset. So somebody can go in there and they could do whatever they wanted to do. They could create their own pages. They could create their own blog posts. And for 24 hours, there was a page called Russell’s Awesome. But then after 24 hours, it would just reset. I always thought that was so cool, but I could never figure out how to do that. Topher DeRosia: Oh, yeah. And everybody was editing all at the same time, within that 24-hour period. Russell Aaron: I have since restructured my website. I use the block theme from WebDevStudios. I kind of feel like that’s where I got my education from. I was somebody who kind of dabbled around in WordPress, and then when I went to go work with them for three years, they had a set of standards that I couldn’t even fathom to begin with. But then as we built things and I saw how their machine works, how their business revolves, I was like, “You know, for me, this is the way that I like to do things, is the way that they like to do things.” And so my new website… I mean, not new website, but it’s my new theme, I actually had AI build it for me. I had Claude. I was using… It’s by ThemeIsle. Neve. I was using Neve, one of my favorite themes. Love them. So I was using that, and then my site was kind of all over the place. It was an “I’ll teach you how to do this”. That’s kind of the main focus of my site is I will jump on a call with you, and whatever questions you have, I’ll sit here for five hours with you if you want. I will teach you and until you get it. But then I also had this section about band names that were just… earlier when we were talking about the rise of Envato, you know, like I would have a section on my blog where you could create a new band name and then I had all these random blog posts. And so my website was kind of like this potluck, if you will, just like this random stuff. And I was like, you know, I want to be doing something else. I think my website needs to change. And I have those old blog posts still, but they’re hidden. So now with my new theme, I had AI look at my old site and say, this is what I think we should do. I picked out some colors and over like five days, I had it build me five different HTML pages, like completely different, you know? And then I started giving AI and I said like, “Okay, I want to look like this.” And then I was like, well, okay, I like this and I like this, but I also like this from this other site.” So I started feeding it information and like when the HTML came out, I had 12 different templates. I had my blog posts, I had my archive, but I had everything built in HTML. And the cool thing about the WDS block theme is that it serves everything as an HTML page. So I literally just took AI and said, “Take these HTML pages, bake them into how this theme does it,” and bam, my site came up. I had it done in maybe two days. Topher DeRosia: Wow. Russell Aaron: And then after that, I had it take all of those HTML pages and create me patterns. So now I can go in, and when I go into my full site editor, I can go to patterns, I have all my homepage patterns, my blog patterns, I sliced everything up, and they’re all WordPress native blocks. So I can literally go in and change the coloring on any page I want instead of having to edit the HTML or anything. And now that I have that, I feel this sense of freedom where I’m not worrying about an update coming tomorrow, if my update is gonna break or I don’t have to read a changelog that is not specific anymore. I can’t stress how much I love not having to read changelogs or the lack of changelogs. I mean, I’m fully happy with how things have come out. And over time, I’m gonna keep fine-tuning it, but I’m pretty much where I’m at right now. With all of this new technology that’s come out, I’ve really kind of found my love again for WordPress. I was kind of in a slump where I just wasn’t really doing anything. Now I take my son and we’ll drive down to Louisville, Kentucky. He rides BMX. So while he’s racing, I will literally have Claude Code open on my computer and I will log into the Claude app on my phone and I can keep sitting there having the same conversation. So this new thing that I’m building, I can still do it while I’m sitting there watching him race or while I’m doing something else. I was just like, this is fantastic. And then my wife will drive home and I’ll just sit there and I talk into my phone, I literally put the microphone on and I’ll be like, “You know, I don’t like that. And here’s my thoughts about this.” And you know, my phone dictates all of that and then I send it to my computer through the app and it just keeps spinning things up. Then by the time I get home, I have a new version that I can demo or I have a new version that I can test. I mean, I am just so fascinated by it. Topher DeRosia: That’s cool. Were we at WebDev at the same time? Russel Aaron: I don’t think so. Topher DeRosia: I was there just over three years ago. Russel Aaron: I was there 2015 through 2018. Topher DeRosia: Oh, yeah. I came much later. I was only there for like two months. Russell Aaron: Oh, wow. Sometimes that’s the way it goes. Topher DeRosia: Yeah. They were gonna get a big contract that hired a bunch of people and two months later didn’t get the contract and let us all go. Russell Aaron: As much as I hate that, that also taught me that the people that do great work or the people that show up every day and are putting in more than they’re getting out, those are usually the people that stay in companies like that. That really changed my work ethic. I used to be somebody who wanted to be not lazy, but I didn’t wanna be pressed for time or having to go, go, go and having to be on all the time. Now, I’m the opposite. Now, I’m like, now that I’ve done that, I kind of earn for that stretch for a little bit. I mean, you were just saying that how you’ve transitioned to where you are. I was watching a Barstool Sports interview with a guy who runs a pizza shop in… it’s either New Jersey or New York. The guy’s only open Wednesday, Thursday, Friday, Saturday. And he’s only open nine to six or something like that. And he built that business… well, it’s been in his family for like 60 years or something. He has one of the last original pizza ovens ever. But anyways, the point is, is that he lives at the pizza place, that’s where his entire life is, but he built the business around his life. I’m doing the same thing where if I wanna literally go jump on my bike right now and go for a two-mile ride, I’m gonna go do that. And I don’t have to feel like, hey, you’re not logged in and we’re not tracking your mouse. Like what’s happening? How come you’re not on Slack? You know what I mean? I’m not tied down to that. And I can’t stress that enough of like, that is where I wanna be. Topher DeRosia: Yeah. Yeah, it is a good life. We are at about the time to wrap it up. Okay. So I’m gonna do that. Where do you hang out online? Russel Aaron: Where do I hang out online? Topher DeRosia: Are you in any common WordPress Slacks? Russel Aaron: I’m on the main WordPress Slack sometimes. I tend to watch more than I do involve anymore. A long time ago, I used to be very vocal and I used to be not afraid to walk in to a room guns blazing. With the big cultural shift that happened in WordPress, I tend to just sit back now and be more self-reserved. So I post on my website, russellenvy.com. I’m on LinkedIn. I’ve been utilizing Reddit a lot too. I think for me, Reddit is a place where I kind of disagree with the fact that you can hide behind a pseudonym, but I do like the brutal honesty that people will have because they are hiding behind something and they will say, dude, this flat out sucks. Or they’ll be like, Hey, this is great, but it would be cool if, or somebody can be like, “Hey, that already exists. You’re not doing anything new.” I do like that. Because it kind of not puts me in my place, but it shows me either how connected or disconnected I am to what I think I’m doing. And so Reddit is a very great place. I mean, everything is russellenvy.com except for Twitter or X, whatever you want to call it. Topher DeRosia: All right, cool. Russel Aaron: Where do you hang out at? Topher DeRosia: I am in probably 40 slacks, but the vast majority of them, I don’t look at. I’m there so that someone can ping me. I’m in a couple of slacks in India. Okay. I’m in the WordPress Italian community Slack. Russel Aaron: That’s interesting. Topher DeRosia: Post status make, of course there’s a hero press Slack. I have my own company Slack, my local meetup has a Slack. There’s just a lot of them. I wouldn’t say I’m super active on any of them. I just occasionally interact with somebody. I use my own company Slack to invite my clients in when we talk there. Russel Aaron: Right. Do you find yourself reading things more than, you know… from the outsider looking in, I post a lot and it looks like I post a lot… I mean, especially on LinkedIn, but I’m always consuming more than I’m posting. Do you find yourself doing that? Like where you’re… maybe not keeping up with the trades anymore, but like, you know… I used to read maybe 1,500 blog posts a week and then… what was that service where you could like save…? I used to have a service where you could save articles and then that way, late at night, I would just read, you know, maybe 10 or 15 of them a night. But now I look at things like Reddit where I see… I just look at somebody who’s going on there and asking for help. Again, it’s a standard WordPress person that, hey, I’m new to this, I don’t know how, and I’m looking at it and I’m just like, how can we make that better? That’s kind of where I’m at these days. Topher DeRosia: I don’t read a whole lot in Slack. It really is for my convenience. I’m pretty active with my RSS reader. I follow a lot of stuff. Russell Aaron: Oh, wow. Topher DeRosia: Because I don’t wanna go chase it all down all over the internet. So, you know, there’s that. I’m on LinkedIn a fair amount, Facebook a little bit. I’m on Mastodon and Blue Sky mostly just to post stuff. It’s funny, I have more followers… No, let me say it this way. Mastodon, I have the fewest followers, but the most engagement from those followers. Russell Aaron: Isn’t that interesting? Topher DeRosia: Yeah, I’ll post something and I’ll get some favorites or reposts or whatever. Blue Sky, I get almost nothing at all, despite the fact that I have like a thousand followers there. Russell Aaron: But Blue Sky is a community that is fast-moving. I almost compare it to anything Meta has, which is you can post today right now and in three minutes you’re 785 posts down. That’s what I really love about Reddit is that I posted something about this AI team that I’m building that I give away for free on GitHub, and so for like five days, I was the number two post on that subreddit. And the volume that I saw from that. I mean, Reddit really loves human writing. If you go in there, you post something that somewhat seemingly might suggest that you had AI do anything with it, they will just downvote it. But if you write original and you write from the heart and stuff, like your stuff skyrockets there. I’ve learned a lot from Reddit because of that. Topher DeRosia: That’s really cool. Russell Aaron: It’s interesting. Topher DeRosia: Yeah. All right, well, thanks for chatting with me. Russell Aaron: Thank you for the time. Topher DeRosia: And now you can’t be on anybody else’s podcast. Russell Aaron: I’m actually starting my own, sir. Topher DeRosia: Are you? All right. Russell Aaron: I have, like you said, the reason why we started this is because you saw something from me that says, “I’m tired of the indie circuit,” if you will. I put out a LinkedIn post, I don’t know, maybe a month ago at this point and I asked people if they wanted to be on a show. So I have WP Roundtable. I got that from Kyle Mahler, a person who I love in WordPress more than I can express. One of the best people on the planet, I feel like. I was thinking about starting that up again, because we don’t have WP Watercooler anymore. We don’t have anything like that. That’s kind of where I got my start from. But again, I also identify that that’s kind of the problem is that every Monday or Friday I was on a show and I was one of the people that you would see constantly. And so I was sitting there thinking and I was like, what doesn’t the space have? What kind of show do I wanna watch? Because I don’t watch shows when they come out, do you? Topher DeRosia: No. Russell Aaron: I always watch them maybe four weeks down the road at like 2:30 in the morning when I have nothing going on. And by that point, the information is almost stale. I mean, the way that anything works these days. And there’s a few that I might watch maybe within 48 hours of coming out, but at this point, there is something… a new idea that myself and… the guy’s actually an automatician. And so it’s actually kind of interesting because we don’t wanna say anything that would put him in a position to where he’s saying something bad about the company he works for, but I’m also the person where I get to say something to the person who works at Automattic to maybe incite some change. So we are working on something like that, but it’s not going to be an interview show. It is not going to be something where you tune it out or you put it on a 2.5 playback speed just to get through it. You know what I mean? And that’s really what the emphasis of my post was about is that so many of the interviews go that way. Topher DeRosia: Yeah. Are you familiar with wppodcasts.com? Russell Aaron: Yes. Topher DeRosia: Okay, good. So when you get it started up, submit it there. Russell Aaron: That’s a place. I’m very fascinated by Gary Vaynerchuk. Are you familiar with Gary V? Topher DeRosia: No. Russell Aaron: I watch something Gary V every day. That guy makes me feel like I’m lazy every single day, but he is also one of the people that says like, “Hey, you’re 40, you’re still just a baby.” A lot of people feel like I should be two kids, a house, marriage, this, that, and because I’m not, I’m behind the ball. And he’s one person that’s like, “Listen, you’re still a kid.” And he’s like, “You’re 40, I’m 40, and you have 10 years until you’re 50.” And even then you’re still so young to where you can generate something again and from 50 to 60, you can now do. That kind of mentality really moved me around. Why I bring that up is, I’m trying not to post on the same places that everybody else is. I wanna find that new venture. Substack is a great one. And they also have a way to release podcast episodes through them. So they can actually be your entire engine. So like you don’t have to host them on different places and stuff like that. So I’m looking for different plays like that. Topher DeRosia: All right, cool. Well, I look forward to hearing about it when it comes out. I’m sure you’ll post on LinkedIn. Russell Aaron: Yes, yeah. Topher DeRosia: All right. All right then, well, I will maybe find you on Slack or Reddit or someplace. Russell Aaron: Slack, Reddit, LinkedIn. Either way, please keep in touch. First of all, it’s great to see somebody familiar in the space. It’s great. I mean, just talking about the old days, I could sit here and do it forever. Topher DeRosia: All right, I’ll see ya. Russell Aaron: Have a good one. Topher DeRosia: All right, so that was the end of the podcast. If you could send me a headshot. And yep, that’s the one. Cool. And any links you want in the liner notes. Russell Aaron: Cool. Topher DeRosia: And two or three sentences about you and what you do and whatnot. Russell Aaron: Cool. I noticed that you… are you trying to revive Hallway Chats? Or is it something that when you just find something interesting, you’re like, hey, I’ll go do that. Topher DeRosia: That’s it right there. Russell Aaron: Okay. Sure, sure. Topher DeRosia: There was a time when it was a weekly podcast and now it’s a whenever I feel like it podcast. Russell Aaron: I love it. I think that’s the biggest reason why I’m trying to do something different is I really dislike watching a podcast. The first thing they do is they come on and they go, “Hey, welcome to WP whatever. Hey, sorry we didn’t post this week. I was bit…” If you are gonna say you’re gonna post every Wednesday at one, that’s on you. But I do not like when things start off with an apology. Like just get to it. Because I’m not watching it Wednesday at one. I mean, unless you’re Joe Rogan, or unless you are somebody who has a huge following that people will watch you live because it’s important. Otherwise, it’s just consumable stuff, you know? Topher DeRosia: Yeah. For years, I posted it Heropress weekly on Wednesday without fail. I would ignore my family to go get it done. Then I was talking to Morton Rand Hendrickson. You know him? Russell Aaron: Uh-huh. Topher DeRosia: Yeah, he’s a huge fan of Heropress. And I said to him, “Do you read every week?” He’s like, “Oh no, not at all.” He’s like, “Oh, I thought you really liked it.” And he said, “Oh, I love it. But I don’t have time to read every week.” Every few months I’ll get depressed about the WordPress community and I’ll go read 10 essays. And then one time I was at WordCamp Ann Arbor, probably the same one you were at and Josepha came to me and said that… she was kind of a sounding board for employees that come to her and said, “Listen, I’ve been working support all day and people suck and I’m depressed and I hate life.” And she would just listen for a while and then at the end they would say, “Okay, I’m gonna go read a bunch of Heropress and I’ll feel better.” And it really changed my perspective of what I was making. I wasn’t making a weekly publication. I was making an archive, a collection to be used as a tool, a library. Russell Aaron: I’m gonna say this poorly, but it’s almost like you are creating a support help hotline where it’s like, if you’re on the verge of blowing up your website, please call this number. We’ll talk you down from it. It’s almost like you’re building that. Topher DeRosia: That’s funny. Russell Aaron: That’s interesting. And then now you’re just selective about it or you’re so far- Topher DeRosia: I’m less aggressive about finding essayists and less insistent that they get it to me by a certain time. Like I would find somebody and say, listen, I need it by Sunday on this date. And they were like, “Okay.” And that worked for a while. Russell Aaron: Oh, before, before. Okay. Topher DeRosia: Yeah. But now I’ll find somebody… No, I don’t go looking as often. Russell Aaron: You’ll maybe find something that somebody wrote and you’ll be like, “Hey, are you interested in doing this?” Topher DeRosia: Yes. And I don’t find people as often. I used to find my people on Twitter and I’m not on there anymore. Russell Aaron: Like by personal choice? Topher DeRosia: Yeah. Russell Aaron: Okay. Topher DeRosia: I just left Twitter. Russell Aaron: Oh, wow. You feel like your life improved? Topher DeRosia: Yes and no. Russell Aaron: Okay. Topher DeRosia: I feel the loss of what Twitter was. And it’s not there anymore. It’s just gone. Russell Aaron: Especially around WordCamp and stuff like that. That used to have to be the place that you’d be on, you know? Topher DeRosia: The Twitter I loved doesn’t exist anymore. And so, yeah, I feel that loss. Russell Aaron: I need a t-shirt that says that. Topher DeRosia: Yeah. Wow. I’m in the process of making a printable store. Printable? Printful. Printful store. Russell Aaron: Cool. Topher DeRosia: With Woo, to make a video with. I need to make a bunch of products. Maybe I’ll make one of those. Russell Aaron: It’s interesting. Wow. You just flat-out left X. Do you feel like with Heropress, it was… and again, this is why I made that post, is that people almost see it like they can make the rounds. And it’s like, well, I haven’t gone there yet. And so they’re gonna submit something to you because they’re gonna get some press out of it. And it’s not so much what’s best for your brand or it’s not best for your website. They just see it as, well, I’m gonna get some exposure there. Do you feel like it used to be that? Topher DeRosia: No. I’ve gotten maybe two or three submissions ever like that. And a couple of them, I was able to say, “No, that’s not what we’re about. It’s this other thing, what Heropress is actually about.” And they’re like, “Oh, well, okay, that’d be great.” And they do that. And maybe one or two people have said, “I built this great company and everyone should come use my company.” Like, no, not so much. Russell Aaron: Interesting. Topher DeRosia: And that’s the end of it. Russell Aaron: I remember back in, I wanna say like 2013, people used to call each other out and be like, why are you giving the same speech at WordCamp Miami, WordCamp Minneapolis, WordCamp San Diego. And that’s kind of where I was at with that same LinkedIn post. It’s like, I really, really enjoy watching Matt Cromwell’s show, but the guy that he just had on also was on Jonathan Denwood and was also on this one. It was also on, I was like, I’ve already seen this. Maybe I get three more percent information that wasn’t in that last, or because Matt knows a little bit more about personal stuff in WordPress or building a business, he might have some more insight there, but it’s like, I’ve already heard this and I’m kind of already over it. And that’s kind of where I was at is you don’t have to just say, I’m gonna do this one and that’s it. But it’s almost like, you’re making yourself not… what’s the word. Not credible because you’re going around and saying the same thing and it’s just, you’re not doing anything different than a blog post could have done. Topher DeRosia: You know what I mean? I don’t feel too bad about repeating WordCamp talks because, especially at small camps, because a lot of people are just gonna go to their local camp and never go to another one. And unless they cruise.tv, they’re not gonna see it. I struggle a little bit with podcasts because I’ve been asked a lot over the last 10 years to come on a podcast and talk about the story of WordPress. And it’s the same story every time, you know? And so, I’ll try to mix it up a little bit, give different information that I’ve never given before, that sort of thing. But it is something I think about and struggle with a little bit. Russell Aaron: What do you struggle with about it? Topher DeRosia: I don’t wanna just say the same thing over and over again. You know, I don’t want people to go, oh, Topher’s on another podcast episode. Oh, I’ve heard this story. I don’t need to be on this episode. Fortunately, it’s been around long enough that I can give a brief synopsis of the beginning and talk about stuff that’s happened in the last couple of years. Russell Aaron: Right. Topher DeRosia: Which is gonna be really different from the podcast episode I was on in 2020. Russell Aaron: You know? Right. Topher DeRosia: It’s an interesting dilemma when you have one story to tell and everybody wants you to tell it. How do you deal with that? Russell Aaron: Well, I’ve noticed that too. It is like, you know, I’ll watch [Insert Famous Name Here], and they have a podcast, and they’re interviewing, again, [Insert Famous Name Here], and that person was also just on That Famous Name and That Famous Name. I actually saw somebody, it’s like almost a year ago, and they were just like, “Do you want me just to say this so your show has this speech in it or are you genuinely asking me?” Because, you know, like you want this story so you can post it on your social media. But I’ve already given that story 15 different times because they wanted it for their own, you know? And it’s almost going that way where I kind of respect it in a way because you don’t want to post other people’s content. But I also feel like I’m tired of saying the same shit over and over again. It’s interesting, man. Topher DeRosia: Yeah, that’s a dilemma. Russell Aaron: So you’re just like kicking back and… are you building something for you that you think is gonna scale or are you trying to get away from WordPress? That’s kind of where I’m at right now. Topher DeRosia: Yes and no. I have always wanted to… I’ve always been better with people than code. I’m a life coach. Russell Aaron: Yeah. I did not know that about you. Topher DeRosia: I love talking to the client more than coding. I love helping people learn things. And so those skills could be anywhere in WordPress, but also could be anywhere outside of WordPress. So I’m looking for those jobs and they are not out there. Russell Aaron: Right. Topher DeRosia: So here we are. Russell Aaron: I’m to the point now where my son, he’s eight, but he races BMX, like actual bikes and stuff. And so there’s a college here in Indianapolis and it’s one of the best cycling schools in the country. And there’s like five Olympians that practice every Tuesday and Thursday and they’re right in our back door. These are people that have a great social following, but they don’t post very well. They have a brand name, but they don’t have a website. So I’m noticing that every new space that I go into, it’s kind of like I get to jump back into WordPress again, where it’s like, hey, I just built a website for this BMX track in Louisville, Kentucky. It’s one of the best tracks in the country by everybody that has ever raced in a sport, they all vote that it’s one of the best, but they don’t have a website period. I just went through this where they have a guy, he’s their treasurer and he’s like, “Well, I’m an AI software guy.” And I’m like, “Well, how come you don’t have a website?” And he’s like, “Well…” And I’m like, “Listen, I submitted a new version of a we… literally, I uploaded it to my Russell website or to my Russell Envy site and I just put it in a sub-folder and I was like, “Your website could look like this today.” I was like, “For free. I don’t want anything from you. No free anything.” I was like, “I want to donate this to you because I want to grow the sport.” And the guy’s like, “I wanted to build it and React.” And I’m like, “Well, why didn’t you?” And the guy’s like, “Uh.” And I’m like, “I have free hosting for life from WPEngine.” And I was like, “I won’t charge you guys ever. I will host a site. I have free with AppPresser. I’ll build you guys an app where you guys can send push notifications.” And the guy’s like, “Well, I want to have a lot of control and say over it.” And I was just like, “All right, you know what?” And then I built my own. Now I own a domain all about their BMX track and now they’re calling me going, “We should have went with you.” I’m to the point now where I’m nice. And then it’s just like, “Dude, I’m 10,000 miles over you and I’m going to go this way.” Liquid Web did that to me. Liquid Web brought me in and they were like, “We’re going to…” I was supposed to be the OG stellar WP. They brought me in, I was hiring all my friends and I was bringing in people and we were building something. And then they called me and they were like, “Well, you can either be a level two support person or you could just not work here.” And I was like, “Well, I don’t work here anymore.” And they were like, “Well, wait, hang on.” And I literally hit “click” and I have never logged on since. Topher DeRosia: That’s funny. Russell Aaron: I’m in that same boat where, you know, I don’t have to work for you. You know what I mean? Like, fuck, I’m 40. I should be doing something on my own anyway. I kind of wish I had… what was WP 101? Sean did that for all those years. I wish I would have done that. Or every week, I should have had some YouTube about talking about something and maybe I could have monetized that, but I’m not behind the ball. I let the ball slip is what I feel like. Topher DeRosia: It’s not too late to start. I picked that up when Sean, quit and I’ve got a YouTube channel with a bunch of stuff on it. I published one today. Russell Aaron: Oh wow. It’s just interesting things that you think about, or is it like educational, like tutorials? Topher DeRosia: It’s educational tutorials, but stuff that I find interesting. Like today I made a desktop wallpaper for WordCamp Europe. Russell Aaron: Nice. Topher DeRosia: And I did it by going to their webpage in my browser and using the console to hack the HTML and CSS until it looked like a screen, a wallpaper. Russell Aaron: That’s fucking cool. Topher DeRosia: So I published it right before I’d started talking to you, like minutes before that. And it has three views. Russell Aaron: Woohoo. Topher DeRosia: But a couple of weeks ago I did one called fun and games in the terminal. And it’s how to play Tetris in the terminal and how to make a choo-choo train go across your screen when you type LS wrong. And it has 784 views right now. Russell Aaron: That’s awesome. Topher DeRosia: I did one on how to brighten a photo. I did a series. I’m working on a series called Topher learns how, or I talk to people who know how to do things that I really should know how to do, but don’t. I talked to Scott Kingsley Clark about pods, which has been around forever, but I’ve never used. I talked to Donata about Termageddon, because I know it’s important, but I have stayed away because I don’t understand and it’s scary. Russell Aaron: Termageddon. I’ve never heard that. Topher DeRosia: Oh. You know the little cookie consent things, privacy policies and whatnot? Russell Aaron: Yeah. Topher DeRosia: So when you sign up with term again, you pay a surprisingly low monthly fee and they have a human get on the phone with you and talk through your requirements of where you live, your legal stuff. Like, are you in Europe? Are you in California? Where are you? Where are your customers, your viewers? Then you drop in a short code for your privacy code and for the cookies and they keep them up to date based on how the laws change. So you don’t have to pay attention to, Oh, did California make some crazy new law about cookies? What do I need to do to update my site? It’s really, really great. So I did an interview with her. Russell Aaron: $12 a month or $119 a year. Topher DeRosia: Yeah. Russell Aaron: What is the point of having a privacy policy if you don’t pay extra for limiting your liability? Wow. That’s amazing. Topher DeRosia: It is. Russell Aaron: That’s someone just thinking outside the box. Topher DeRosia: Yeah. I have a couple of videos where I was given an account at a hosting company that I’ve never used and videoed logging in for the first time and getting to a website. Russell Aaron: Oh, wow. Just from first login to setting everything up to now you have something production. Wow. Topher DeRosia: Yeah. Specifically not reading the docs. Russell Aaron: Oh, just trying to brute force your way through it. Topher DeRosia: Yeah. Russell Aaron: That’s smart, dude. Topher DeRosia: It’s partly about… well, they may have wonderful docs. It may be super easy to do if you read all the docs. I don’t want to read the docs. Russell Aaron: Me neither. Topher DeRosia: Clickety clickety click, I have a website. So I did GreenGeeks. I did honesthosting.io. I did X cloud. So that’s the kind of stuff I’m doing. Russell Aaron: That’s interesting. That is something that, that Gary V talks about a lot is that it used to have to be where you are this WordPress brand and you do just this and all your videos could only be about that. Anytime you stepped outside the box, people were like, “Why am I watching this?” And today now we’re to finally to where my website would probably actually thrive is it’s so random. It’s just something out of my head and one thing can skyrocket and it’s like hitting the jackpot, you know? That’s interesting. Topher DeRosia: Another thing I did is I made a site called topher.how and because I realized I had never really made stuff in my own channel. I’ve been blogging for decades, making videos, WinningWP. I have over a hundred videos on WinningWP. Russell Aaron: WinningWP? Topher DeRosia: Yeah. Russell Aaron: Did you start that when Charlie Sheen started doing Winning? Topher DeRosia: No, no, no, no. But I was thinking, boy, I’d love to have all this stuff on my own website, but I don’t want to go find it all and copy paste posts. And then I realized nearly every place I’ve ever made content has RSS for their authors. Russell Aaron: Yeah. Topher DeRosia: And so I found the sites, found my author RSS feed and started piping them into WP all import. And now topher.how has all my content from the last 15 years on a dozen different sites, doesn’t more than a dozen different sites, all my videos, all my posts, everything on wordpress.tv, all that stuff. So it’s kind of a portfolio. Yeah, so you can go to topher.how and see all my stuff. Russell Aaron: That was actually one thing that I was really proud of was that my entire WordPress journey is documented on somebody else’s project. So, like you go to WPwatercooler and my resume, what is great about it is that it is not me who can edit those videos, it is not me who can master them. Those words are there. Those words are me. You want to know my qualifications in WordPress, there’s all my shit. For me, I was like, “That’s actually pretty sick. You know what I mean?” Topher DeRosia: Yeah. Russell Aaron: Wow. Topher.how. Oh, dude, do you know who Jeffrey Zinn is? Topher DeRosia: No. Russell Aaron: Oh God. Him and Brandon Dove they have Pixel Jar. Have you ever heard of Pixel Jar? Topher DeRosia: Maybe. Russell Aaron: They’re big West coasters. I’ll tell you that much. He just wrote me, “He literally just said, dude, how do you find the time to write so much on LinkedIn? I enjoy all your stuff, but mostly I’m blown away by the volume.” Topher DeRosia: Nice. Russell Aaron: I’m going to write him back and just tell him the truth. But you know, it’s all thought man. Interesting. Topher, I’ve had a lot of fun. Am I taking up your time? Topher DeRosia: I should get back to work. Russell Aaron: All right, sir. Have a good one. Topher DeRosia: All right. I’ll see ya. Russell Aaron: Bye. Topher DeRosia: Bye.

This week, Bart and I recorded the second half of Programming By Stealth installment 184. The first half covered the SASS basics, and in this half, we get to learn through a worked example how to write in SASS, which compiles to regular old CSS. He created a little web page with some wise and humorous quotes from notable people in history, and used everything we learned in the first half to style the page. As I told Bart at the end, it's great that he teaches us the foundation of these tools, but it's equally great to have a worked example where we can see theory in action, and reference these examples in the future. You can find Bart's fabulous tutorial shownotes for both Part A and Part B at pbs.bartificer.net. If you want to jump right to the spot in the notes were Part B starts, go to this direct link pbs.bartificer.net/...)

Wes and Scott talk about the foundational decisions that make AI-assisted coding actually work—database schemas, validation, routing, CSS structure, and more. They explore why consistency matters more than specific tools, and how a little upfront planning can keep agents from turning your codebase into chaos. Show Notes 00:00 Welcome to Syntax! 03:19 Planning your database schema before AI touches it 06:08 Picking a validation strategy that won't drift 07:18 Mapping your routing structure and auth flow 08:48 Brought to you by Sentry.io 10:52 Locking in your CSS methodology and UI framework 13:31 Choosing how your client and server communicate 15:03 Creating a folder structure agents can follow 16:16 Don't be afraid to switch up your AI setup later Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

Scott and Wes chat all things agent skills for web developers, sharing their favorites for everything from CSS animations and HTML generation to logo extraction, marketing copy, and video creation. Whether you're just getting started with AI-powered development or looking to level up your workflow, this episode is packed with practical skills you can put to use today. Show Notes 00:00 Welcome to Syntax! 01:33 Hot Tip Skill 05:55 CSS Motion Systems 08:17 Agent Browser Skill 09:30 HTML Skill 12:01 Extract Logos Skill 13:34 Dex Task Skill 14:50 Remotion and Hyper Frames Skills Syntax Episode 550 with Remotion 16:22 Discussion on AI and Design Skills 18:50 Marketing Skills and Copywriting 23:01 Final Thoughts and Resources 24:10 Brought to you by Sentry.io Sentry Skills Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

In this potluck episode of Syntax, Wes and Scott answer your questions about LLM usage-based pricing, security risks from malicious code in interviews, staying current in a fast-moving dev landscape, a new CSS linter, managing Node environments and tooling without losing your mind, and more! Show Notes 00:00 Welcome to Syntax! 01:17 Copilot's new usage-based pricing and the end of cheap AI Model multipliers for annual Copilot Pro and Copilot Pro+ subscribers 08:53 Why Syntax dropped clever ad transitions 10:33 Debugging issues on the Syntax website with Sentry 12:51 Brought to you by Sentry.io 13:01 Getting hacked through a fake recruiter and malicious repos Adib Hanna's hacking story scammer.md DeskPad 17:57 How to catch up after stepping away from dev 25:10 React components vs native browser APIs 32:41 New CSS linting tools and Project Wallace updates csskit 36:06 How to interview developers in the age of AI 41:21 Managing Node, package managers, and dev environments 46:59 Sick picks + shameless plugs Sick Picks Scott: ZEISS Lens Care KeyboardCleanTool Wes: Amaran Halo 100x Shameless Plugs Syntax YouTube Channel Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

Scott and Wes break down what makes CSS truly manageable—from preventing style leaks and embracing fluid layouts to choosing the right methodology, whether that's utility CSS, component-scoped styles, or CSS modules. They also dive into practical tips like leveraging CSS variables, layers, scoping, and tooling to keep your stylesheets clean and scalable. Show Notes 00:00 Welcome to Syntax! 01:31 Understanding CSS Manageability 01:44 This CSS doesn't leak to other parts of website. 03:41 This CSS is easy to maintain. 05:54 This CSS is reusable. 06:10 Global Solutions Instead of Local Solutions. 07:12 Flexibility and Adaptability in CSS 09:36 Fluid Typography and Responsive Design fluid-type 12:09 Variables and Consistency in CSS 13:40 Brought to you by Sentry.io. 14:14 Values vs Variables. Project Wallace. 18:19 Choosing the Right CSS Methodology 18:48 Utility CSS and Atomic CSS 22:35 Exploring StyleX and Other Approaches Syntax Ep 650. 25:14 Panda CSS. 25:37 Component Scoped CSS: A Preferred Approach 29:08 The Evolution of CSS Modules 34:03 Global CSS: Best Practices Josh Comeau's CSS Reset. Scott's Graffiti UI. 38:22 Harnessing CSS Variables 41:33 Understanding CSS Layers 43:52 The Power of CSS Scoping 46:16 Enforcing CSS Standards with Tools Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads

Scott and Wes dig into a huge batch of community-submitted projects, from JSON tools and CSS editors to AI agents, view transitions, and everything in between. It's a rapid-fire showcase of what developers have been building, including picks like Arrow JS, Sugar High, Drift, and a whole lot more. Show Notes 00:00 Welcome to Syntax! Wes' Bluesky Post Wes' X Post 01:20 JSON-Alexander. 02:43 FFF - Fastest File Search. 04:44 View Transitions Toolkit. 08:06 Agentation and Svelte Agentation. 11:21 CSS Studio. 13:12 Peon Ping 14:26 Peekdown. 16:03 Dex. 20:22 Content Copilot. 22:16 Opencode Sentry Monitor. pi-sentry-monitor. 24:56 Arrow JS. 29:20 Comark. 33:19 Silly Software Club. 34:05 Sugar High. 36:04 Drift. 37:19 Fallow. 41:20 Edit Mind. 44:46 Clint. 47:18 Honorable mentions. 47:21 Artemisapp. 49:53 Open Screen. 50:14 CanvidHQ. 52:02 Proxybox Zero. Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott: X Instagram Tiktok LinkedIn Threads Randy: X Instagram YouTube Threads