Podcasts about CSS

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.

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/

In deze aflevering hebben we het over de aankomende iOS release, bespreken we kort CSSDay 2026 en praat Rick je bij over de laatste HTML en CSS features die zijn besproken zoals CSS Grid lanes en Heading-offset. Michele legt uit waarom UX zichzelf terugverdient en geeft je wat quick wins. 01:00 - iOS 27 wordt eindelijk wel bruikbaar 07:30 - Heading offset voor het eenvoudig structureren van je headings - https://mastodon.social/@firefoxwebdevs/116680726980295049 11:10 - Border-radius: match-parent komt er wellicht aan 12:19 - Grid-lanes nu in Safari en je kunt er mee spelen op de playground - https://gridlanes.webkit.org/ 18:14 - Door middel van tekenen je Lovable app veranderen - https://x.com/emilfagerholm/status/2066536352259215805?s=20 22:10 - CSSDay Recap 27:50 - Adam Argyle's prop-for-that library - https://prop-for-that.netlify.app 30:00 - De ROI Van UX - https://www.smashingmagazine.com/2026/05/data-backed-truths-user-experience-roi/ 48:45 - Switchbot Lock Ultra (Referral, 10 euro korting) - https://eu.switch-bot.com?sca_ref=11404744.SnekIQLevZ&sca_crp=MzE4MTE0 53:30 - Obsidian notes app - https://obsidian.md

22/06/2026 - Verbum, a Palavra de Deus Meditação da Palavra do Senhor com o Pe. José Aguiar Nobre, CSS

In dieser SEOPRESSO Live Folge spricht Björn Darko mit Christiane „Chrissy“ Kunisch, SEO-Expertin und Mitgründerin von One Beyond Search, über Chrome DevTools als echte Wunderwaffe für SEOs. Chrissy zeigt hands-on, wie SEOs mit dem Elements Tab Inhalte live manipulieren, klickabhängige Elemente prüfen, interne Links im DOM validieren und mit XPath sowie CSS-Selektoren gezielt Informationen aus Seiten extrahieren können.Außerdem geht es tief in den Network Tab: von PageSpeed-Checks über Caching, Throttling und blockierte Requests bis hin zu einem spannenden Beispiel, wie sich bei ChatGPT über geladene JSON-Dateien Hinweise auf Query Fanout, Websuche und genutzte Quellen finden lassen. Im Application Tab erklärt Chrissy, warum Cookies auch für SEO relevant sein können – etwa wenn Google Sitemaps oder Seiteninhalte ohne Cookie-Akzeptanz nicht abrufen kann.Zum Abschluss sprechen Björn und Chrissy über ungenutzten JavaScript- und CSS-Code, Coverage Reports und die nächste Automatisierungsstufe: Chrome DevTools in Kombination mit MCP-Servern, Claude, Cursor oder anderen AI-Tools. Eine Folge für alle, die technische SEO-Analysen schneller, günstiger und smarter machen wollen. Chrome DevTools sind kostenlos, direkt im Browser verfügbar und bieten SEOs eine Art „Röntgenbrille“ für Webseiten.Im Elements Tab lassen sich Texte, CSS und HTML live verändern – ideal für schnelle Mockups und SEO-Empfehlungen.Klickabhängige Inhalte und interne Links können direkt im DOM geprüft werden, um zu sehen, ob Google sie überhaupt initial findet.XPath und CSS-Selektoren helfen dabei, gezielt Elemente wie Links, Bewertungen oder Custom-Elemente zu identifizieren und später in Crawling-Tools zu nutzen.Der Network Tab eignet sich für PageSpeed-, Caching-, Request- und Throttling-Checks.Cookies können SEO-Probleme verursachen, wenn wichtige Dateien wie XML-Sitemaps oder Seiteninhalte ohne Cookie-Akzeptanz nicht erreichbar sind.Der Coverage Report zeigt ungenutztes CSS und JavaScript und liefert Ansatzpunkte für Performance-Optimierung.MCP-Server für Chrome DevTools können Audits, PageSpeed-Vergleiche, Markup-Erstellung und technische Analysen teilweise automatisieren.Kapitelmarken00:00 Intro & Begrüßung01:03 Thema der Folge: Chrome DevTools als Zauberwaffe für SEOs03:05 Warum DevTools für SEOs so wertvoll sind05:29 Elements Tab: Texte, CSS und Elemente live verändern09:09 Klickabhängige Inhalte und Links im DOM prüfen14:07 XPath und CSS-Selektoren für SEO-Analysen18:10 Network Tab: ChatGPT, JSON-Files und Query Fanout24:21 PageSpeed-, Caching- und Throttling-Checks im Network Tab31:02 Application Tab: Cookies, Sitemaps und Googlebot-Probleme35:21 Ungenutzten CSS- und JavaScript-Code finden40:14 MCP-Server und AI-Automatisierung mit Chrome DevTools46:48 Wichtigster Tipp: einfach ausprobieren48:43 Outro mit Christiane Kunisch

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

React officially leaves the Meta building to live under the new React Foundation (and the React Compiler gets rewritten in Rust), Apple's WWDC unveils a stacked Safari 27 beta, and Chrome DevTools 149 levels up its AI features. A jam-packed week in front-end news.Timestamps 0:00 - Intro 1:27 - React is now officially owned by the React Foundation 3:07 - React Compiler is now in Rust 5:56 - Safari 27 beta 12:12 - DevTools 149 updates 23:46 - State of CSS survey 2026 27:54 - Fire Starter 32:15 - What's Making Us Happy NewsPaige: WebKit in Safari 27 betaJack: React is now owned by the React Foundation & React Compiler is now in RustTJ: DevTools 149 updatesLightning NewsState of CSS survey 2026 — go vote for us under your favorite web dev podcasts!Fire StarterAdvanced Perceptual Contrast AlgorithmWhat's Making Us HappyPaige: Blocks of focus timeJack: AI is saving money and time — Burn Baby BurnTJ: SportsThanks 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 website Blue Collar Coder on YouTube Blue Collar Coder on Discord Reach out via email Tweet at us on X @front_end_fire Follow us on Bluesky @front-end-fire.com Subscribe to our YouTube channel @Front-EndFirePodcast

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

Shopify performance specialist Izaac Barratt of Baseline Commerce joins Karl and Taylor for a deep dive into site speed optimization. The conversation covers the full spectrum from LCP and INP fundamentals to the real-world friction of app bloat, AI coding habits, and what actually moves the needle for conversion rates. A must-listen for any theme developer, app developer, or agency working with high-traffic Shopify stores.SponsorThe Support Heroes - https://www.thesupportheroes.com/?utm_source=liquid_weekly&utm_medium=podcast&utm_campaign=sponsorshipsSubscribe to Liquid WeeklyDon't miss out on expert insights and tips—subscribe to Liquid Weekly for more content like this: https://liquidweekly.com/Find Izaac Barratt OnlineLinkedIn: https://www.linkedin.com/in/izaac-barratt — where he posts performance tips, resources, and his ongoing series on the nine performance fix bucketsBaseline Commerce: baseline-commerce.com — Izaac's site speed optimization consultancyTimestamps01:23 – Intros; welcoming guest Izaac Barrett02:48 – Izaac's origin story: animation, Newgrounds, and e-commerce05:36 – What drew Izaac to performance optimization06:00 – First site speed project: 12 seconds to 2 seconds, conversion doubled10:00 – LCP fundamentals: above-the-fold prioritization and perception18:00 – Preloading, lazy loading, and how to get them wrong20:43 – Liquid's preload tag, sections_index, and reducing JavaScript dependency26:38 – Telling AI to prioritize HTML/Liquid and CSS over JavaScript31:01 – Async vs. defer vs. render-blocking scripts explained35:28 – Apps and performance: identifying problem apps, merchant conversations39:15 – Advice for app developers on loading strategy and user interaction cycles41:42 – INP (Interaction to Next Paint) explained: what it is and why it's hard to fix43:30 – Shopify/research report: 34ms of INP = 3.5% drop in CVR46:06 – How to debug INP: Chrome DevTools performance tab and CrUX data53:20 – Izaac's LinkedIn series: nine buckets of performance fixes56:17 – Dev Changelog1:02:44 – Picks of the WeekDev Changelog- Next-Generation Events — Developer Preview: https://shopify.dev/changelog- ⚠️ Expiring Offline Access Tokens Required for All Public Apps — January 1, 2027: https://shopify.dev/changelog- Shop Minis — March/April 2026 Update: https://shopify.dev/changelog- Customer Account UI — Feature Preview: https://shopify.dev/changelog- App Home as a UI Extension: https://shopify.dev/changelog- llms.txt / agents.md in Shopify Themes: https://shopify.dev/changelogPicks of the WeekKarl:The Dark Journey: The Tragedy of the Donner Party by Allan Eckert – A true history of the ill-fated 1846 wagon party, written by one of Karl's favorite frontier authors; dark but compelling, especially for history enthusiasts. https://www.amazon.com/Dark-Journey-Allan-W-Eckert/dp/1931672539Izaac: Page Speed Impact Estimator fastersite.ai – A tool for estimating the performance gains of removing specific scripts and assets before actually doing the work; great for benchmarking and scoping conversations with clients.Taylor:The Will of the Many by James Islington – A sci-fi novel recommended by Taylor's brother (a bookseller); follows a teenager hiding his royal lineage in a Roman Empire-style society that literally harvests people's will to gain power. Book two also out. https://www.goodreads.com/book/show/58416951-the-will-of-the-many

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.

✏️ Suscribirse https://www.youtube.com/watch?v=4ctXUc228nc Optimizar una web WordPress no va solo de activar un plugin de caché al final del proyecto. En este episodio 253 de Negocios y WordPress, la conversación gira alrededor de una idea mucho más útil: el rendimiento empieza en cómo construyes la web, en cuántas capas metes, en cómo mides, en qué recursos cargas y en si de verdad necesitas cada plugin, cada builder o cada script. Además, el episodio conecta ese enfoque con otra capa muy actual: la IA como apoyo para construir soluciones más directas, más limpias y menos dependientes de herramientas intermedias. Desde ahí salen dos temas que encajan muy bien entre sí: WPO para WordPress y una forma más madura de desarrollar con contexto, skills y conectores más potentes. WP Rocket como punto de partida para hablar de rendimiento real El episodio usa WP Rocket como puerta de entrada para aterrizar el tema del WPO en algo práctico y reconocible. La idea no es presentar la optimización como un ejercicio académico, sino como algo que afecta de forma directa a la usabilidad, al SEO, a la conversión y a la experiencia real del usuario. Una de las ideas que más se repiten es que herramientas como WP Rocket resultan útiles porque condensan muchas tareas habituales de rendimiento en una interfaz más simple: caché, retraso de scripts, optimización de carga y análisis de oportunidades sin obligarte a navegar por paneles mucho más técnicos desde el primer minuto. Eso no significa que el plugin lo resuelva todo por arte de magia. Lo que sí deja claro la conversación es que un buen plugin de rendimiento puede acelerar mucho el trabajo cuando detrás hay criterio técnico, especialmente en proyectos donde necesitas una mejora rápida, mantenible y comprensible también para otras personas del equipo o para el cliente. También aparece una idea interesante: el rendimiento no debe mirarse solo como “la web carga más rápido”, sino como una parte de la comunicación del sitio. Cuando una página carga mejor, distrae menos, es más clara y obliga a esconder menos cosas detrás de artificios innecesarios, normalmente también funciona mejor a nivel de negocio. El WPO empieza en el desarrollo, no en el parche final Uno de los mensajes más valiosos del episodio es que muchas webs llegan tarde a la optimización porque intentan arreglar al final decisiones malas que se tomaron al principio. Ahí entra una regla muy simple: no meter cosas que no hacen falta. La conversación insiste mucho en varios frentes: no añadir plugins por inercia no resolver con capas extra algo que puedes hacer de forma nativa no cargar recursos en páginas donde no se usan no diseñar primero una web pesada para intentar rescatarla después Ese criterio aplica a casi todo: sliders, mapas incrustados, formularios que cargan scripts en toda la web, animaciones que no aportan nada o builders que introducen más complejidad de la necesaria en proyectos sencillos. Aquí el episodio conecta muy bien rendimiento con estrategia. No se trata solo de “limpiar código”, sino de preguntarte si de verdad hace falta cada cosa que estás añadiendo. Muchas veces, una web mejora a la vez en velocidad, claridad y conversión simplemente porque elimina capas que nunca debieron estar ahí. También se recuerda algo muy útil para proyectos nuevos y para proyectos heredados: conviene medir mientras desarrollas. Si instalas un plugin importante, si metes WooCommerce, si añades una integración o si cambias una parte clave de la web, lo sensato es revisar ahí el impacto. Esperar al final para hacer una gran auditoría suele ser bastante peor que detectar los problemas por el camino. Caché, Time to First Byte, imágenes y recursos: el Pareto del rendimiento Cuando el episodio entra en la parte más técnica, el foco está en las mejoras que más impacto suelen dar con menos complicación. Y ahí el primer gran bloque es la caché. La explicación es muy clara: si puedes servir una página ya preparada en vez de obligar a WordPress a reconstruirla desde cero en cada visita, la respuesta mejora muchísimo. Por eso la caché de página sigue siendo uno de los pilares del WPO. A partir de ahí aparecen matices importantes, como las exclusiones necesarias en una tienda online o en páginas con partes dinámicas. Junto a eso, se comenta el Time to First Byte, la importancia de medirlo y de entender qué está tardando realmente antes de que el navegador empiece a recibir contenido. El episodio menciona explícitamente el uso de GTmetrix y, sobre todo, del apartado Waterfall para detectar recursos problemáticos y cuellos de botella con más criterio. Otro bloque clave es el de imágenes, vídeos y medios: lazy loading para no cargar lo que aún no se ve tamaños adecuados según el uso real de cada imagen compresión razonable evitar incrustados pesados cuando una alternativa más simple cumple mejor Aquí sale un ejemplo muy bueno: muchas veces no hace falta incrustar un mapa de Google o un slider entero si una dirección clicable o una solución más ligera resuelven mejor el objetivo. Reducir carga no es solo comprimir archivos, también es dejar de servir cosas que apenas aportan valor. Lo mismo ocurre con JavaScript y CSS. El episodio habla de diferir scripts, de evitar cargar recursos globales cuando solo se usan en una página concreta y de revisar con cuidado qué necesita estar disponible desde el primer momento y qué puede esperar. Esa parte enlaza con otro punto importante: no todo lo que la herramienta permite cargar debería cargarse siempre. Builders, DOM, base de datos y limpieza estructural Otra clave del episodio es que el rendimiento no depende solo del hosting o del plugin de caché, sino también de la estructura que arrastras. Y ahí entran el DOM, los builders, los metadatos, las consultas y la limpieza de base de datos. La conversación no plantea un ataque simplón a Elementor, Bricks o JetEngine. De hecho, se reconoce que las herramientas han mejorado y que muchas veces son útiles. Pero también se remarca que cada capa extra tiene un coste, y que ese coste puede notarse en HTML inflado, listados más pesados, más scripts, más estilos o una base de datos más desordenada. Se mencionan varios frentes donde conviene afinar: grids o loops duplicados que podrían resolverse mejor abuso de `postmeta`, repeaters o estructuras demasiado cargadas residuos que dejan plugins al desaparecer carga condicional de plugins para que no trabajen donde no deben fuentes mal servidas o con demasiadas variantes Ese bloque baja muy bien una idea importante: optimizar también es simplificar la arquitectura del proyecto. A veces el problema no está en una imagen grande o en una fuente mal cargada, sino en que la propia solución está pidiendo demasiado para hacer una tarea relativamente simple. Por eso el episodio insiste en revisar DOM, consultas, tablas, PHP y estructura general. Incluso cuando se habla de CDN, se deja claro que ayuda en contextos concretos, pero nunca sustituye las buenas decisiones de base. Primero simplificar, luego acelerar. IA, Auto Skills y NovaMira: menos dependencia de capas innecesarias La parte de IA no aparece como un tema separado, sino como una forma de reforzar el mismo principio de fondo: construir mejor con menos fricción. En ese contexto se habla de skills, de sistemas propios y de reutilizar conocimiento operativo en vez de empezar siempre desde cero. Uno de los ejemplos más claros es Auto Skills, que sirve para descubrir skills relacionadas con tu stack y con el tipo de proyecto que estás tocando. La reflexión que sale de ahí es útil: si ya existen procedimientos bien definidos para WordPress, performance o desarrollo, reutilizarlos puede ahorrarte muchísimo contexto y bastante improvisación. También aparece NovaMira como conexión MCP para WordPress, con acceso a PHP, WP-CLI, ficheros y operaciones más potentes dentro del proyecto. Lo interesante no es solo la herramienta concreta, sino lo que permite: resolver tareas que antes empujaban a meter plugins o builders cuando en realidad bastaba con una solución más directa a nivel de código y estructura. En esa misma línea, el episodio plantea que con IA se vuelve más factible construir: grids complejos sin depender de varios loops visuales sliders ligeros sin añadir plugins específicos filtros y pequeñas interacciones con una implementación más limpia procesos internos para revisar y documentar optimización La conclusión de ese bloque es bastante potente: si la IA te ayuda a crear soluciones más nativas y mejor pensadas, también puede ayudarte a mejorar el rendimiento, porque reduce la tentación de añadir otra capa para resolver cada necesidad. Además, entre las menciones laterales del episodio aparece WordPress.com Social como ejemplo de novedad del ecosistema y una reflexión útil sobre cómo algunas herramientas nuevas pueden encajar, pero sin perder nunca de vista el criterio principal: usar lo que aporta valor real y no lo que solo añade ruido. Cierre El episodio 253 deja una idea muy clara: el WPO para WordPress no es una fase final, sino una forma de pensar el desarrollo. Caché, Time to First Byte, imágenes, JavaScript, CSS, fuentes, builders, base de datos y CDN importan, sí, pero lo decisivo es cómo tomas decisiones antes de que todos esos problemas se acumulen. También deja otra lectura útil: la IA puede ser una aliada real del rendimiento cuando la usas para simplificar, documentar, medir y construir soluciones más directas, no cuando la conviertes en otra capa más de complejidad. Si trabajas con WordPress y quieres mejorar velocidad, claridad técnica y mantenibilidad, este episodio apunta bien el camino: menos inercia, más criterio, mejores mediciones y una arquitectura mucho más limpia desde el principio. Ese suele ser el verdadero atajo.

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

In this episode, Matt and Mike break down why traditional CSS learning often falls short - and what actually works instead. From building muscle memory and understanding layout behavior to avoiding common beginner mistakes like over-nesting and fighting the layout, this episode is all about practical, real-world CSS skills. We also explore hands-on learning scenarios like navbars, hero sections, blog layouts, and forms-plus a simple framework you can use to improve your CSS faster. And in the age of AI, we discuss why practical CSS knowledge is still essential for debugging and building production-ready designs. If you've ever felt stuck between “knowing CSS” and actually building with it, this episode is for you. Show Notes: https://www.htmlallthethings.com/podcast/you-know-css-so-why-cant-you-build-anything Use our Scrimba affiliate link (https://scrimba.com/?via=htmlallthethings) for a 20% discount!! Full details in show notes.

ChatGPT tiene desde el año pasado una funcionalidad llamada Product Search Discovery que permite mostrar un carrusel de productos cuando alguien hace una búsqueda de compra. Y no solo eso: con instant checkout se puede completar la compra sin salir de ChatGPT, comprando directamente en tu tienda de e-commerce. Requisitos para aparecer No tener bloqueado el bot oai-searchbot en el robots.txt Registrarse en el formulario de Product Search Discovery (búscalo en Google o en ChatGPT) Enviar el feed de productos — en WordPress/WooCommerce ya existe por defecto, no hay que hacer nada extra. Si tu tienda está en Astro u otro framework sin feed nativo, tendrás que generarlo a mano. Lo que hay. Cómo optimizarlo Schema markup: dile a la IA en HTML qué es cada cosa (nombre, precio, disponibilidad…). Plugins como Open Eye Product Fit generan y validan este esquema automáticamente. Títulos descriptivos: «Peluquín negro» no vende; «Peluquín negro rizado de pelo sintético ligero» le da contexto a la IA. Velocidad y técnica básica: hosting decente, imágenes en WebP, caché activa, diseño responsive. Nada nuevo, pero sigue siendo lo que marca la diferencia. Campos mínimos del schema para aparecer en ChatGPT ID del producto Nombre Descripción URL (con parámetro UTM para saber si viene de ChatGPT) Imagen Precio Moneda (importante si vendes en Polonia, que tiene zlotys, no euros — dato crucial para la WordCamp de Cracovia) Disponibilidad Recomendación: GitHub es obligatorio si trabajas con agentes de IA Said perdió una semana de trabajo porque su agente de codificación borró todo y luego dijo tranquilamente «yo no he sido». La solución es tan vieja como el software: control de versiones. Git + GitHub, y que el propio agente haga los commits en cada cambio. El truco extra: usa ficheros CLAUDE.md, agents.md o arquitectura.md en cada proyecto para definir las reglas del agente de forma permanente — qué convenciones seguir, cómo hacer commits, si el proyecto es WordPress… Así no tienes que repetírselo en cada conversación. Plugin del día: Design Set Go 65 bloques de Gutenberg construidos con bloques nativos de WordPress más un poco de CSS. Sin código propietario, sin sobrecarga, sin versión pro (con 65 bloques, ¿para qué?). Incluye slider, pestañas, secciones sticky y el bloque 50-50 que divide la pantalla en dos mitades. Los screenshots son GIFs animados para que veas cómo funciona antes de instalarlo, y tiene botón de Live Preview en Playground para probarlo sin tocar tu web. Una joya, y gratis. https://wordpress.org/plugins/designsetgo/ Próximamente WordCamp Kraków: 3 al 7 de junio. Miguel Ángel estará allí. Llevar ropa de verano o de invierno: por determinar (pendiente consulta con María). ¿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/

This month's "180 with Katie" highlights the many ways CSS staff and volunteers brought hope, dignity, and connection to the people we served throughout April. In 180 seconds, you'll hear about a Good Samaritan who helped one of our refugee clients, and how sharing meals with clients inside the new Hastings building is so special. This episode captures meaningful moments that reflect Hope in the Good Life.

5/13/26Episode SummaryIn Episode 185 of the Shopify Solutions Podcast, host Scott Austin of JadePuma explains why he's made the Enterprise theme by Clean Canvas his go-to starting point for client Shopify stores.His core argument is that themes are toolboxes, and rather than picking one based on a single feature, merchants should pick the theme with the deepest set of built-in tools — which means less reliance on paid apps, developers, or theme migrations down the road. Enterprise (priced at $400) wins on that measure, and Scott switched to it in 2025 after seven years on the Flex theme, which he felt had stopped keeping pace with Shopify.He gives Clean Canvas high marks as a developer: ten-plus years in the theme store, the team behind popular themes like Symmetry, Pipeline, and Taste, and a focus solely on theme development rather than custom client work. Reviews of Enterprise consistently praise its speed and Core Web Vitals performance, the breadth of features that replace third-party apps, its suitability for large catalogs, and the responsiveness of Clean Canvas's support team.After a brief explainer on Shopify theme structure (templates, sections, blocks, and CSS), Scott walks through Enterprise's feature categories: cart and checkout tools (slide-out cart, quick buy, in-store pickup), marketing and conversion features (cross-sells, countdown timers, popups, back-in-stock alerts), merchandising tools (product tabs, swatches, lookbooks, shoppable images), and product discovery features especially valuable for big catalogs (mega menus, predictive search, filtering, infinite scroll).He acknowledges Enterprise has gaps and built his own app — Enterprise Theme Sections — to add missing functionality and toggle off design choices like the Shop Pay promo and alternative checkout buttons.His bottom line: Enterprise is ideal for established brands with real catalogs and traffic, but overkill for brand-new low-volume stores, which should start with a free theme and migrate later.Show LinksEnterprise Theme - https://themes.shopify.com/themes/enterprise/presets/enterprise Enterprise Theme Sections app - https://apps.shopify.com/enterprise-theme-sections Video & Transcripthttps://jadepuma.com/blogs/the-shopify-solutions-podcast/episode-185-review-of-the-enterprise-theme-for-shopify-stores 

Eine Familie mit einem schwer autistischen Jungen beisst bei der CSS auf Granit. Die Krankenkasse sieht keinen Grund, die Mutter für ihren Pflegeaufwand zu entschädigen. +++ Weiteres Thema: Welche sind die bequemsten Campingmatten?

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

Thanks Pressable for supporting the show! Get your special hosting deal at https://pressable.com/wpminuteBecome a WP Minute Supporter & Slack member at https://thewpminute.com/supportOn this episode of The WP Minute+ podcast, Eric sits down with Jeffrey Zeldman, a pioneer in web design and co-founder of the Web Standards Project and A List Apart. They discuss his journey into web design, the challenges of early web development, the birth of web standards, and the evolution of CSS and accessibility. Jeffrey shares insights on the collaborative nature of the web and the importance of creating a more inclusive digital space. This is the first in a two-part series.Takeaways:Jeffrey initially disliked web design but grew to love it.The early web lacked standards, leading to chaotic development. Jeffrey's experience with the Batman Forever website is a prime example.Jeffrey played a key role in the Web Standards Project.The introduction of CSS revolutionized web design.Accessibility became a crucial focus in web development.Collaboration among developers was essential for the adoption of standards.The educational component of web design was lacking in the early days. The early web design community shared knowledge freely.The push for web standards was akin to the open-source movement.Important Links:Jeffrey Zeldman PresentsA List ApartThe Web Standards ProjectBatman Forever website: Web Design MuseumConnect with Jeffrey: Bluesky | LinkedInCSS Zen GardenThe WP Minute+ Podcast: thewpminute.com/subscribe ★ Support this podcast ★

In our most recent installment, Bart taught us how to use CSS "variables" (custom properties) to customize Bootstrap to make your pages not look like every other Bootstrap page on the Internet. He explained at the end that you can take all of this quite a bit further if you learn how to use SASS (Syntactically Awesome Style Sheets). SASS is a preprocessor for CSS, which means it creates "normal" CSS but allows you a lot more flexibility in how to create that CSS. For example, you can even create lists and maps and loop over them just like a proper programming language. We get SASS for free with Jekyll so why not take advantage of it? There's a lot to learn about SASS, so we broke this topic up into two parts, but even this first "half" is a mammoth episode. Nothing is a hard lift, but there's a lot to lift! You can find Bart's fabulous tutorial shownotes for both Part A and Part B and the audio podcast for Part A at pbs.bartificer.net. As Bart says at the very end, Part B comes with a "health warning" as it hasn't yet been proofread!

Google Chrome engineer Adam Argyle breaks down why AI is bad at frontend development and CSS in particular. From LLM training data problems to the fact that LLMs can't see, the issues run deep. But it's not all doom! Adam shares a game-changing technique for getting creative AI generated UI by asking for low probability outputs, introduces tools like Impeccable and V0 for AI assisted CSS editing, and dives into agentic loop engineering with auto research, an overnight AI workflow he uses to ship improvements while he sleeps. Links Website: https://nerdy.dev/ YouTube: https://www.youtube.com/channel/UCBGr3ZMcV5jke40_Wrv3fNA Twitter: twitter.com/argyleink Github: github.com/argyleink Linkedin: https://www.linkedin.com/in/adamargyle Resources Why AI sucks at frontend: https://nerdy.dev/why-ai-sucks-at-front-end We want to hear from you! How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend? Fill out our listener survey! https://t.co/oKVAEXipxu Let us know by sending an email to our producer, Elizabeth, at elizabeth.becz@logrocket.com, or tweet at us at PodRocketPod. Check out our newsletter! https://blog.logrocket.com/the-replay-newsletter/ Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form, and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understanding where your users are struggling by trying it for free at LogRocket.com. Try LogRocket for free today. ChaptersSpecial Guests: Adam Argyle and Jack Herrington.

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

Каждый день мы набираем тысячи символов — в мессенджерах, документах, таблицах — и почти никогда не задумываемся, что происходит на наших смартфонах и компьютерах в этот момент. Как текст превращается в понятный компьютеру код, почему иногда мы видим кракозябры при открытии текстового файла и зачем существует столько разных форматов. В новом выпуске пытаемся разобраться во всём этом вместе с Евгением Кругловым, руководителем сервиса Яндекс Документы и Яндекс Доски, и Николаем Ермошенковым, руководителем разработки Яндекс Документов.Разобрали, как компьютеры научились понимать текст — от перфокарт и ASCII до Unicode. Поговорили о том, как устроен собственный движок Документов Яндекс 360, как в нём работает совместное редактирование и что на самом деле происходит, когда два человека одновременно правят один абзац. И, конечно, обсудили AI: где он уже встроен в документы сегодня и каким будет редактор, когда агент станет полноценным соавтором.

In this episode, we travel to Auburn, Nebraska, to sit down with Dr. John Crotty, a longtime board member of Catholic Social Services of Southern Nebraska. With more than 20 years of involvement, John shares why his commitment to CSS has remained strong—and how he has witnessed lives changed through acts of compassion, care, and faith. Through personal insight, this conversation highlights the real impact of generosity and invites listeners to be part of that mission, especially during the Nebraska Catholic Day of Giving. Make your donation now at csshope.org/NCDG and it will be matched dollar for dollar!

In the 21st "Storm Postgame Report," CSS founder Charles Hamaker discusses the team's preseason victory over the Portland Fire at Climate Pledge Arena, including strong individual performances from Flau'jae Johnson, Zia Cooke, and Dominique Malonga.

Chris, Andrew, and David open with some classic confusion over what day it is then dive into Podia's gradual rollout of a major new app version, including how the team is handling migration, feature flags, dogfooding, and eventual cleanup. From there, the discussion turns to underrated Rails routing features like direct routes and resolve routes, a newly merged Rails query command, observability improvements through Hatchbox's AppSignal integration, and the ongoing pain of CSS build tooling in Rails apps. They also touch on conference season and their upcoming talks. Press download now to hear more! LinksJudoscale- Remote Ruby listener giftDirect RoutesInstance Public methods-direct (name, options = {}, &block)Instance Public methods-resolve (*args, &block)GitHub-Query command for read-only database queries #57156App Signal for HatchboxBlastoff Rails-June 11-12, 2026, Albuquerque, NMFrontend Masters Workshop-May 26, 2026-Getting Started with Rails (Chris Oliver)Toronto Tech Week- May 25-29, 2026HoneybadgerHoneybadger is an application health monitoring tool built by developers for developers.JudoscaleMake your deployments bulletproof with autoscaling that just works.Disclaimer: This post contains affiliate links. If you make a purchase, I may receive a commission at no extra cost to you.Chris Oliver X/TwitterAndrew Mason X/TwitterJason Charnes X/Twitter

This show has been flagged as Clean by the host. This show is about developing features for a web application. The technology used is ASP.Net WebForms , the programming language is Visual Basic .Net along with HTML and CSS and the development environment is Windows 11 running under a virtual machine in Linux, with Visual Studio and SQL Server as the database. Other tools used are Git , Github , Joplin and Dropbox , Google Gemini and a tool called Beyond Compare . ResourceRowControl.ascx.vb Public WriteOnly Property ResourceObject As Resource Set(obj As Resource) If obj IsNot Nothing Then HiddenResourceID.Value = CStr(obj.ResourceID) HiddenResourceTypeID.Value = CStr(obj.ResourceTypeID) Resource.Text = obj.ResourceName Type.Text = obj.ResourceTypeName Available.Checked = obj.ResourceAvailable End If End Set End Property Private Sub Available_CheckedChanged(sender As Object, e As EventArgs) Handles Available.CheckedChanged Dim objResource As New Resource With objResource .ResourceID = ResourceID .ResourceName = Resource.Text .ResourceTypeID = ResourceTypeID .ResourceAvailable = Available.Checked End With objResource.Add() End Sub ResourceRowControl.ascx Provide feedback on this episode.

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

In this episode of Hope in the Good Life, we welcome new board member Leslie Wiesler, who has already stepped into leadership as Board Secretary at Catholic Social Services of Southern Nebraska. Leslie shares what inspired her to get involved, the impact of her early experiences, and what has surprised her most about the depth and reach of CSS programs. Leslie offers a fresh perspective on how CSS serves all people with dignity and compassion.

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

Psalm 48:9-14, Deuteronomy 31:30-32:52, Luke 19:45-20:26. There are five main ways in which God guides us (the five CSs):- **C**ommanding **S**cripture (the Bible)- **C**ompelling **S**pirit (the Holy Spirit)- **C**ounsel of the **S**aints (the church)- **C**ommon **S**ense (reason)- **C**ircumstantial **S**igns (providence) In each of today's passages, we see first something general about the way in which God guides us, and then specific examples of each of these ‘five CSs'

Psalm 48:9-14, Deuteronomy 32:10-12, Luke 19:45-46, 20:1-25. There are five main ways in which God guides us (the five CSs):- **C**ommanding **S**cripture (the Bible)- **C**ompelling **S**pirit (the Holy Spirit)- **C**ounsel of the **S**aints (the church)- **C**ommon **S**ense (reason)- **C**ircumstantial **S**igns (providence) In each of today's passages, we see first something general about the way in which God guides us, and then specific examples of each of these ‘five CSs'

Psalm 48:9-14, Deuteronomy 32:10-12, Luke 19:45-46, 20:1-25. There are five main ways in which God guides us (the five CSs):- **C**ommanding **S**cripture (the Bible)- **C**ompelling **S**pirit (the Holy Spirit)- **C**ounsel of the **S**aints (the church)- **C**ommon **S**ense (reason)- **C**ircumstantial **S**igns (providence) In each of today's passages, we see first something general about the way in which God guides us, and then specific examples of each of these ‘five CSs'

Send us Fan MailBack in 2011, I remember personally waiting in line on Freret Street at the new hot dog closet that had just opened up. A line down the block. It was something to behold. Especially because it was only 6 years after Katrina. And Freret Street still looked like it. For real. But a few investors saw potential and the first sparks in the dark were made.        And before you knew it,  that street was bright and bustling again. It was and IS magical. Just driving down this street currently is so inspiring. And it started with just a handful of visionaries. One being, the owner of DAT DOG, Constantine Georges. Constantine sat down with me to talk about how it all happened. From a tiny hot dog closet to a total city dominator.  Mr. Georges has the personality and the vision to make it happen. All behind a concept of nostalgia.  Georges, a former federal prosecutor, olive oil purveyor breaks it all down and even offers some advice for others out there with an idea or concept. Persistence is key. ______Then later, we're celebrating April's Autism Acceptance month with local children's book author, mama & advocate; founder of Rare Blooms Foundation, Dana Garrett. After her daughter's diagnosis of CSS & Autism, Dana felt led to advocate for kids through writing and philanthropy. She self published a children's book series called “Alana & Wyatt's Adventures” highlighting nonverbal kids, their siblings & the different ways we all communicate. She established Rare Blooms Foundation in 2026 with the mission to support families raising neurodivergent children by hosting restorative retreats, enrichment and life skills workshops, caregiver gatherings, sibling programs and celebrations. This month  Dana will be joining our Kid's Book Club LIVE at Dat Dog on Freret Street! She will be reading her books and the kids will be having fun with activities and Hot Dogs! We are so grateful for brave parents like Dana that leads by example. I was taught one person can change the world. Dana Garrett is proof. Plus she looks like my OG crush- Daphnie from Scooby Doo. Just sayin. To find her books and to learn more about Dana's mission go to www.rarebloomsfoundation.orgThank you to our family of amazing sponsors! STATE FARM®   INSURANCE AGENT Leigh Ann Arcuri             https://ridewithla.com/Ochsner Children's HospitalWww.ochsner.orgRouses MarkersWww.rousesmarkets.comCafe Du Monde www.shop.cafedumonde.comNew Orleans Ice Cream CompanyWww.neworleansicecream.comERA TOP REALTY: Pamela Breaux plbreaux@gmail.comNew Orleans Tea Co.                                                 www.neworleansteacompany.comBottom of the Cup Tea Room                                                www.bottomofthecup.com

In this very fun installment of Programming By Stealth, @Bart B teaches us how to use CSS “variables”, which aren't actually variables (they're custom properties). These non-variables allow you to take advantage of Bootstrap to style web pages, but make the look and feel all your own. Bart outdid himself on the shownotes, the examples, and the challenge looks super fun. You can find Bart's fabulous tutorial shownotes and the audio podcast at pbs.bartificer.net. If you appreciate the work Bart puts into Programming by Stealth, consider supporting him through Patreon or Paypal by going to supporting him on Patreon..

Wes and Scott talk about the latest CSS and browser features, including the Grid Lines API for masonry layouts, HTML in Canvas, name-only container queries, CSS random, search-text styling, and more. Show Notes 00:00 Welcome to Syntax! 00:57 Grid Lines API for masonry-style layouts Introducing CSS Grid Lanes CSS Grid Lanes browser support 03:25 HTML in canvas and next-gen UI effects @jaffathecake @mattrothenberg 11:30 Name-only container queries for scoped styles Name-Only Containers: The Scoping We Needed 14:37 Brought to you by Sentry.io 15:34 Safari removes haptic feedback workaround 17:38 CSS random for dynamic values Rolling the Dice with CSS random() 18:49 Styling find-in-page with ::search-text 21:44 Sticky positioning now works in both axes @una 22:43 Multi-column CSS finally gets usable fixes Looking at New CSS Multi-Column Layout Wrapping Features 24:41 Border shape improvements and new design options @una MadCSS.com 27:09 Why MDN demos need to be better 28:24 Element-scoped view transitions for cleaner animations @bram.us 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

This episode of Remote Ruby opens with stories of exhaustion from a sleepless week. Then, Chris, Andrew, and David spend most of the episode unpacking two big themes: trust and governance in open source, and the growing mess of software security and AI-assisted development. They dig into the new Ruby Central write-up on the RubyGems/Bundler fracture and question whether it actually clarifies the path forward, then pivot into the Axios npm compromise, supply-chain risk, and how fragile modern package ecosystems can feel. Then, they go into a wide-ranging discussion on AI coding, bloated production apps, image-performance headaches, CSS/rendering quirks, and why teams may need to rethink APIs, CLIs, MCPs, and markdown-first docs as agent traffic keeps growing. Hit download now to hear more! LinksJudoscale- Remote Ruby listener giftRubyGems Fracture Incident Report Bundler has moved to the RubyGems organization (GitHub)Mitigating the Axios npm supply chain compromise (Microsoft Security blog) Garry Tan XThe Missing GitHub Status PageHoneybadgerHoneybadger is an application health monitoring tool built by developers for developers.JudoscaleMake your deployments bulletproof with autoscaling that just works.Disclaimer: This post contains affiliate links. If you make a purchase, I may receive a commission at no extra cost to you.Chris Oliver X/TwitterAndrew Mason X/TwitterJason Charnes X/Twitter

Miriam Suzanne joins the podcast to unpack the surprisingly deep world of CSS value resolution, the browser program running beneath every website. She explains how cascade and inheritance work together, why CSS custom properties introduce invalid at computed value time errors, and how CSS functions and mixins change the game. Plus: is Sass actually dead, or does it still solve real problems that the browser can't touch? Links Website: https://www.miriamsuzanne.com Mastodon: https://front-end.social/@mia Bluesky: https://bsky.app/profile/miriam.codes Github: https://github.com/mirisuzanne Codepen: https://codepen.io/miriamsuzanne Resources Is Sass Dead Yet? CSS Mixins and Functions - Miriam Suzanne - CSS Day 2025: https://www.youtube.com/watch?v=IIvqkkfmPYE When Variables Cascade with MIRIAM SUZANNE - SmashingConf New York 2025: https://www.youtube.com/watch?v=F-vopd4wMvI We want to hear from you! How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend? Fill out our listener survey! https://t.co/oKVAEXipxu Let us know by sending an email to our producer, Elizabeth, at elizabeth.becz@logrocket.com, or tweet at us at PodRocketPod. Check out our newsletter! https://blog.logrocket.com/the-replay-newsletter/ Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form, and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understanding where your users are struggling by trying it for free at LogRocket.com. Try LogRocket for free today. ChaptersSpecial Guest: Mia Suzanne.

In this potluck episode of Syntax, Wes and Scott answer your questions about AI struggles with CSS and design workflows, learning vs relying on AI, debugging web performance, beginner soldering setups, navigating AI-era job interviews, Figma dev mode, modern API choices, and more. Show Notes 00:00 Welcome to Syntax! 00:55 Why AI struggles with CSS and design workflows 10:50 How much AI should you use when learning to code? 18:41 Debugging performance: tools and team workflows Ep 585: Fundamentals × What Makes a Website Slow? Ep 874: Fast Apps - Easy Perf Wins Ep 897: Making Your App Feel Faster Than It Really Is Ep 972: These Things Make Your App Feel Like Crap on Mobile 23:52 Brought to you by Sentry.io 26:26 Beginner soldering setup and essential tools 29:54 Preparing for interviews without AI (while jobs require it) Brendan Falk on AI-native coding interviews 35:16 Thoughts on Figma dev mode and design workflows 39:20 Ice vs Thaw menu bar apps 40:27 Why AI isn't pushing us toward better APIs 44:54 Vibe rules, skills, and shipping docs for agents vibe-rules Optimizing Content for Agents 54:44 Sick Picks + Shameless Plugs Sick Picks Scott: Jury Duty Wes: USB Cable Tester 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

As we celebrate National Volunteer Month this April, CSS is taking time to honor our volunteers – people who truly bring “Hope in the Good Life” to those we serve. In this special episode, you'll hear how acts of service don't just change lives, but uplift the soul, deepen faith, and reveal what it truly means to be the hands and feet of Christ.

React made a lot of us feel powerful, then maintenance made a lot of us feel tired. Drew Bragg sits down with Delaney Gillilan, creator of Datastar, to argue for a different kind of “modern web” one that keeps the browser's strengths front and center and keeps your app logic where it belongs: on the server. If you've ever looked at your dependency graph and wondered how you got here, this conversation is a reset.We get concrete about what Datastar is and how it works: a tiny reactive framework built around HTML, data attributes, and signals, with a plugin system that stays out of the way. Delaney explains why most state should live on the backend, why duplicating validation and business rules in the client is wasted effort, and why hypermedia is still the simplest way to communicate what a user can do next. We also unpack the “send strings to the browser” philosophy and how that changes performance, complexity, and even team collaboration.Real-time is where it gets spicy. Delaney makes the case for Server-Sent Events (SSE) over WebSockets for many apps, leaning on normal HTTP semantics, built-in reconnects, and streaming compression to ship tiny DOM diffs efficiently. From there we talk CQRS as a mental model for command intent vs view updates, plus what this means for Ruby on Rails developers weighing Hotwire, Stimulus, and upgrades. We close with two bold companion projects: Rocket, which makes Web Components more declarative, and Stellar, a Tailwind alternative that uses parametric CSS variables for a modern design system workflow.If you enjoy deep technical takes on reactive UI, server-driven rendering, SSE, Rails, and modern CSS, subscribe, share the episode with a friend who's stuck in SPA fatigue, and leave a review with the part you disagreed with most.Send us some love.JudoscaleAutoscaling that actually works. Take control of your cloud hosting. HoneybadgerHoneybadger is an application health monitoring tool built by developers for developers.JudoscaleAutoscaling that actually works. Take control of your cloud hosting.Disclaimer: This post contains affiliate links. If you make a purchase, I may receive a commission at no extra cost to you.Support the show

Brad Baldridge breaks down how real estate investors and business owners can legally reduce college costs — using income control, asset positioning, and tax strategy.In this episode of RealDealChat, Jack Hoss sits down with Brad Baldridge, financial advisor and college planning specialist at Taming the High Cost of College, to unpack one of the most overlooked financial planning opportunities for real estate investors — using their assets and income control to dramatically reduce what they pay for their kids' college education.Brad covers:Why families come too late — and the ideal planning runway (sophomore year of high school)The difference between need-based aid and merit aid — and why elite private schools can actually be cheaper than you thinkWhy real estate investors and business owners have levers W-2 employees simply don't haveHow to use income control, bonus timing, and salary adjustments to improve your FAFSA positionWhy investment real estate must be reported as an asset (at net value, not gross) — and what that actually means for your aid calculationHow to shift income and assets to your student to unlock tax credits that phase out at higher income levelsReal case study: a teacher's family inherited $500K and still qualified for a full ride by repositioning assets correctlyReal case study: an engineering manager calculated that paying full price for NYU cost him 3 extra years of work — and decided that was fineWhy applying to five schools of the same type is one of the most common and costly mistakes families makeHow to vet a college financial advisor — and why most people don't know to ask about the CSS profile vs. FAFSABrad's take on AI: useful for research, not yet replacing expertise — and why the "AI will take all the jobs" panic is overblownNiching down: how becoming the college planning specialist transformed Brad's financial advisory practiceThis episode is for:Real estate investors who have kids approaching college ageBusiness owners who want to understand how income control affects financial aidAny parent who wants to stop leaving money on the table when paying for college

Show DescriptionAre we all going to vibe code our own bespoke apps now, can a canvas app be vibe coded, more geolocation API thoughts, CodePen v2's public beta is now out, and private pens explained. Listen on WebsiteWatch on YouTubeLinks March Mad CSS Scroll My Mac Setapp | Powerful apps for Mac & iOS Move tests to closed source repo · Issue #8082 · tldraw/tldraw Enterprising developer somehow writes an x86 CPU emulator in plain CSS — no Javascript, no WASM, just stylesheet computing Traditional Irish music on The Session CodePen Radio – CodePen

In this potluck episode, Wes and Scott answer your questions about popover navigation patterns, the Vibrate API on iOS, whether code quality still matters in the AI era, Wes's evolving Obsidian second-brain setup, where to start with modern full-stack JavaScript, and more! Show Notes 00:00 Welcome to Syntax! 01:02 Using display none with popover and hamburger navigation 03:37 Vercel on iOS and experimenting with the Vibrate API 05:47 Does code quality still matter in the AI age? 11:08 Wes' second brain update and Obsidian workflow QMD 19:57 Brought to you by Sentry.io 20:21 Supporting older browsers and missing out on modern web features 23:32 iPad browsing quirks and dealing with outdated Safari 28:26 What to do when you encounter a badly built or inaccessible website 33:37 Is the Effect TypeScript library worth the learning curve? 37:04 Where to start with modern full-stack JavaScript 43:39 Are column grid frameworks still relevant with modern CSS? Graffiti 49:54 Sick Picks + Shameless Plugs Sick Picks Scott: AVerMedia Video Capture Card Wes: Power Bar Extension Cord Shameless Plugs Phases Podcast 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 DescriptionChris talks through going public with CodePen v2's beta, the magic words and AI skills needed today, Chris has a beef with anchor positioning, thoughts on classless CSS libraries, Eleventy growing up into Build Awesome, and how would you pass an hour by quickly? (Hopefully by listening to this podcast.) Listen on WebsiteWatch on YouTubeLinks Magic Words Anchor Interpolated Morph (AIM) · January 23, 2026 Build Awesome by Font Awesome Build Awesome: We're pausing our Kickstarter! Build a Web Site in 7 Minutes with Build Awesome Quiet UI Good Sudoku CodePen

Wes and Scott talk with Paolo Ricciuti about Svelte custom renderers and how Svelte actually talks to the DOM. They dig into compiler internals, CSS handling, native bridges, and the realities of maintaining ambitious open source tooling. Show Notes 00:00 Welcome to Syntax! March MadCSS 01:44 Paolo's role at Mainmatter and his work on Svelte custom renderers 02:52 Why Paolo chose Svelte Why I choose Svelte Shift Dev 2019: “Rethinking Reactivity” 05:16 From Svelte ambassador to working on the project 07:45 How custom renderers change what Svelte can target 10:10 How Svelte uses the DOM and why that makes custom renderers tricky 20:32 What Lynx provides and how it differs from a web view 24:18 Brought to you by Sentry.io 35:56 Using Svelte with CSS outside the browser 39:09 The timeline and current state of the Lynx app 44:51 Sick Picks + Shameless Plugs Sick Picks Paolo: Opencode Shameless Plugs Paolo: Svelte Custom Renderers | TCMP 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