Podcasts about sdks

Join Dan Vega and DaShaun Carter for an insightful session with Bruno Borges, Principal Product Manager at Microsoft, as we dive into the next generation of AI-assisted development. In this episode, we explore the GitHub Copilot CLI and the new Copilot Java SDK, uncovering how these tools are transforming the terminal into a powerful environment for Spring developers. Learn how to go beyond simple autocomplete, using agentic workflows to automate complex tasks like upgrading Spring Boot versions, refactoring legacy code, and streamlining Azure deployments. We'll also discuss how the Copilot Java SDK allows developers to embed AI capabilities directly into their own JVM-based tooling and CI/CD pipelines. You can participate in our live stream to ask questions or catch the replay on your preferred podcast platform.Show Notes: Bruno on X/TwitterBruno on LinkedInGitHub CopilotCopilot SDK

professorjrod@gmail.comIn this episode, we explore the 'Pocket Revolution' that transformed not just the phone but the entire technology landscape. Discover how the iPhone's breakthrough in multi-touch science, silicon strategy, and platform economics reshaped IT skills development and technology education. We also discuss the impact of Apple's innovation on enterprise communication and how understanding these shifts can help you in your CompTIA exam prep and tech certification journey. Whether you're studying with a group or using a CompTIA study guide, this episode connects revolutionary tech history with practical IT skills development tips to help you succeed.We dive into the hidden engine of the mobile era: the App Store. By standardizing distribution, payments, security reviews, and SDKs, Apple transformed a device into an ecosystem that seeded ridesharing, mobile banking, creator tools, and on‑demand everything. Security became everyday: sandboxing, code signing, and direct OS updates reduced risk for consumers while biometrics and secure enclaves made cryptography feel effortless. At the same time, attention and data became currency. Push notifications, infinite feeds, and engagement loops pulled us into a new marketplace where design and business models overlapped with our habits and mental health.Underneath the experience, custom silicon changed the game. We break down how Apple's SoCs integrated CPU, GPU, and neural engines to enable on‑device AI, privacy‑first biometrics, and unmatched performance per watt. Then we zoom out: supply chains as geopolitical power, BYOD reshaping workplace control, and regulation arriving as smartphones turn into infrastructure. Finally, we ask where we go from here—AR overlays, wearables, and ambient computing—or a cognitive leap where AI becomes the interface. Subscribe, share with a friend who still misses their keyboard, and leave a review telling us what you think replaces the smartphone next.Support the showArt By Sarah/DesmondMusic by Joakim KarudLittle chacha ProductionsJuan Rodriguez can be reached atTikTok @ProfessorJrodProfessorJRod@gmail.com@Prof_JRodInstagram ProfessorJRod

An airhacks.fm conversation with Kabir Khan (@kabirkhan) about: Discussion about the A2A (Agent-to-Agent) protocol initiated by Google and donated to the Linux Foundation, the A2A Java SDK reference implementation using quarkus, the Java SDK development accepted by Google, comparison of python and Java expressiveness and coding practices, the concept of an agent as a stateful process versus a tool as a stateless function call, the agent card as a JSON document advertising capabilities including supported protocols and descriptions and input/output modes and examples, the three wire protocols supported: JSON RPC and HTTP+JSON (REST) and grpc, the proto file becoming the single source of truth for the upcoming 1.0 spec, the facade/adapter pattern for the unified client across protocols, the agent executor interface with request context and event queue parameters, the distinction between simple message interactions and long-running multi-turn tasks, tasks as Java Records containing conversation history with messages and artifacts, message parts including text parts and data parts and file parts, task lifecycle with task IDs and context IDs for stateful conversations, the event queue as internal plumbing for propagating task updates, the separation between spec package (wire protocol entities) and server package (implementation details), the task store as a CRUD interface with in-memory default and database-backed implementations in extras, replicated queue manager using microprofile reactive messaging with Kafka for kubernetes environments, building A2A agents without any LLM involvement for simple use cases like backup systems, the role of LLMs in creating prompts from task messages and context, the agentic loop and the challenge of deciding when an agent's work is complete, the relationship between MCP (Model Context Protocol) for tool access and A2A for agent-to-agent communication, the possibility of wrapping agent calls as MCP tools, memory management considerations with short-term and long-term memory and prompt size affecting LLM quality, the distinction between the bare reference implementation and Quarkus-specific enhancements like annotations and dependency injection, upcoming 1.0 release with standardized Java records for all API classes and improved JavaDoc, protocol extensions including the agent payment protocol and GUI snippet extensions using template engines, authentication support with OAuth2 tokens and API keys and bearer tokens, the authenticated agent card containing more information than the public agent card, authorization hooks being discussed for task-level access control, the API and SPI segregation suggestion for better clarity between spec and implementation Kabir Khan on twitter: @kabirkhan

In this episode, we are again joined by Michael Gants, founder and CEO of Encore, a new SDK helping subscription app developers turn churned users into paying subscribers.Michael is a Stanford grad, a Time Magazine “Leader of Tomorrow”, and a seasoned founder with a passion for building sustainable consumer businesses. Michael breaks down how leading apps use lifecycle experimentation, not just acquisition, but to retain and to winback. We'll go deep into A/B testing across the user journey, smart winback strategies, and the systems top teams use to improve retention, conversions, and subscriber value without relying on more installs.If you're building or scaling a subscription app, this session will help you think beyond surface-level experiments and focus on what actually moves revenue.You will discover:✅ What lifecycle experiments every subscription app should be running✅ How to structure A/B tests beyond onboarding and paywalls✅ Proven winback strategies that actually bring subscribers back✅ How smart layers and options increase subscriber conversionLearn More:Explore Encorehttps://encorekit.com/You can also watch this video here: https://youtube.com/live/x-JmAZbnD9M⁠⁠*********************************************SPONSORSStill designing, resizing, and uploading screenshots manually? AppScreens lets you pick from hundreds of high-converting templates, generate for every device size and language in minutes, and upload automatically to directly to App Store Connect and Google Play Console. Trusted by more than 100K developers and ASO experts worldwide.Try it free: https://appscreens.com/?via=am*********************************************Thinking about your next great app? This is the best time to make it! Contact Chaim at b7dev.com and get your idea started! Delivery times are super short; you'll be surprised by the cost to develop! B7dev.com*********************************************If you're advertising your growing mobile app, you need a measurement partner you can actually rely on — and that's where AppsFlyer comes in.It gives you a clear view of your entire funnel — from the first impression all the way to the install, in-app events, and user LTV. You'll know what's driving real results, and what's just noise.What teams love about it? It's stable, accurate, and built to handle everything the mobile world throws at you — privacy changes, creative optimization, you name it.And when you need help? Their global support team is there 24/7 — not just to fix things, but to help you grow.If you're ready to level up your mobile marketing and make smarter decisions, check out AppsFlyer.com *********************************************Follow us:YouTube: ⁠AppMasters.com/YouTube⁠Instagram: ⁠@App MastersTwitter: ⁠@App MastersTikTok: ⁠@stevepyoung⁠Facebook: ⁠App Masters⁠*********************************************

Steve Ruiz joins us for a deep-dive on tldraw (a very good free whiteboard) and the business he's built selling SDKs that help others build very good whiteboards (and more) with tldraw's high-performance web canvas. Along the way, we discuss the excitement/fear we share about keeping our agents busy, how SDK and infra companies are affected differently by agentic software than SaaS companies, how Steve is approaching the coming era of internal tooling, what will happen when we equip LLMs with an infinite canvas, and more.

Ils ont créé Seald avec une ambition claire : Ils voulaient démocratiser le chiffrement de bout en bout… bien avant que cela devienne un sujet grand public.Le chiffrement bout en bout, c'est ce qui crypte les conversations Whatsapp depuis très longtemps grâce à des clefs privées côté destinataire et côté émetteur et rend vos conversations quasi inviolables.Mais pour créer tout une application autour d'une conversation cryptée... ce n'est pas simple, et c'est ce pouvoir que donne aujourd'hui Seald à tout développeur d'applications.Timothée Rebours et Mehdi Kouhen, 2 des 4 cofondateurs, racontent dans cet épisode les 10 années d'aventure de Seald, du lancement à Berkeley en 2016, des prototypes bricolés en colocation aux premières levées, jusqu'à l'acquisition par OVHcloud le 7 janvier 2026.Dans cet épisode de La Galère, ils reviennent sur ce que personne ne met dans les pitch decks : les cycles de vente qui n'aboutissent pas, les “marques d'intérêt” qui ne signent jamais, la course permanente au cash (en passant plusieurs fois très proche du cash burn à finir par maitrisé l'art de trouver des solutions en dernière minute aka "invoquer de l'argent"), les certifications qui coûtent cher, les subventions en retard, et la nécessité d'inventer des plans B, C et Z pour ne pas tomber.On y parle aussi de ce qui a fini par débloquer la machine : le passage d'un outil “bureautique” à un SDK pour développeurs, l'arrivée de clients européens, l'effet Doctolib, et un objectif de rachat mené en parallèle… tout en continuant à faire comme si de rien n'était.

Steve Ruiz joins us for a deep-dive on tldraw (a very good free whiteboard) and the business he's built selling SDKs that help others build very good whiteboards (and more) with tldraw's high-performance web canvas. Along the way, we discuss the excitement/fear we share about keeping our agents busy, how SDK and infra companies are affected differently by agentic software than SaaS companies, how Steve is approaching the coming era of internal tooling, what will happen when we equip LLMs with an infinite canvas, and more.

If you think eCPM is the most important metric in ad monetization, this episode is for you.Felix breaks down:• eCPM vs Fill Rate• Why Ad ARPDAU is king• Recency model & impression decay• Why more ads can hurt revenue• SDK crash risks & ANR thresholds• Aggressive end cards & churn• How mediation doubles revenue• Networks vs exchanges explainedThis is a practical introduction to how mobile ads actually work once the SDK is live.Key takeaway:Ad monetization is not about showing more ads. It's about optimizing per user.The biggest misconception in mobile ad monetization is obsessing over eCPM. eCPM alone is meaningless. Revenue comes from eCPM × fill rate, and the only metric that truly matters is Ad ARPDAU. That's your real performance line of sight. If eCPM goes up but fill drops, you can still lose money. Networks respect publishers who talk about Ad ARPDAU because it shows you understand the business, not just vanity metrics.eCPMs are not fixed. They are dynamic and driven by complex algorithms. Networks use dozens of parameters including device type, geo, historical installs, auction loss rate, and most importantly recency models. The first few impressions per user are the most valuable. After 5–7 impressions, the per-unit value drops sharply. If you keep pushing more interstitials, you may increase impressions per DAU but flatten total revenue while damaging retention. More ads ≠ more money.Operational discipline separates professionals from amateurs. Never rush SDK updates. Android ANRs and crash thresholds can destroy organic distribution. Aggressive end cards increase churn. Mediation doubles revenue when implemented correctly because it creates a marketplace instead of a single buyer. And exchanges are not networks — they are resellers. Understanding these mechanics is the difference between earning $100 a day and scaling to $1,200+ before expanding demand sources.---------------------------------------This is no BS gaming podcast 2.5 gamers session. Sharing actionable insights, dropping knowledge from our day-to-day User Acquisition, Game Design, and Ad monetization jobs. We are definitely not discussing the latest industry news, but having so much fun! Let's not forget this is a 4 a.m. conference discussion vibe, so let's not take it too seriously.Panelists: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Jakub Remia⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠r,⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Felix Braberg, Matej Lancaric⁠Podcast: Join our slack channel here: https://join.slack.com/t/two-and-half-gamers/shared_invite/zt-2um8eguhf-c~H9idcxM271mnPzdWbipgChapters00:00 – Why Most Studios Misunderstand Ads01:20 – The 4 Metrics That Actually Matter03:30 – Why eCPM Is Overrated05:10 – Ad ARPDAU: The Only Metric That Counts07:00 – How Networks Calculate eCPM09:20 – Recency Model & Impression Decay11:40 – Why More Ads Don't Always Mean More Revenue13:00 – SDK Risks, ANRs & Crash Thresholds15:10 – Aggressive End Cards & Churn17:10 – Mediation Explained (Why It Doubles Revenue)---------------------------------------Matej LancaricUser Acquisition & Creatives Consultant⁠https://lancaric.meFelix BrabergAd monetization consultant⁠https://www.felixbraberg.comJakub RemiarGame design consultant⁠https://www.linkedin.com/in/jakubremiar---------------------------------------Please share the podcast with your industry friends, dogs & cats. Especially cats! They love it!Hit the Subscribe button on YouTube, Spotify, and Apple!Please share feedback and comments - matej@lancaric.me---------------------------------------If you are interested in getting UA tips every week on Monday, visit ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠lancaric.substack.com⁠⁠⁠⁠⁠⁠ & sign up for the Brutally Honest newsletter by Matej LancaricDo you have UA questions nobody can answer? Ask ⁠⁠⁠⁠⁠⁠⁠⁠Matej AI⁠⁠⁠⁠⁠⁠ - the First UA AI in the gaming industry! https://lancaric.me/matej-ai

Emmanuel et Guillaume discutent de divers sujets liés à la programmation, notamment les systèmes de fichiers en Java, le Data Oriented Programming, les défis de JPA avec Kotlin, et les nouvelles fonctionnalités de Quarkus. Ils explorent également des sujets un peu fous comme la création de datacenters dans l'espace. Pas mal d'architecture aussi. Enregistré le 13 février 2026 Téléchargement de l'épisode LesCastCodeurs-Episode-337.mp3 ou en vidéo sur YouTube. News Langages Comment implémenter un file system en Java https://foojay.io/today/bootstrapping-a-java-file-system/ Créer un système de fichiers Java personnalisé avec NIO.2 pour des usages variés (VCS, archives, systèmes distants). Évolution Java: java.io.File (1.0) -> NIO (1.4) -> NIO.2 (1.7) pour personnalisation via FileSystem. Recommander conception préalable; API Java est orientée POSIX. Composants clés à considérer: Conception URI (scheme unique, chemin). Gestion de l'arborescence (BD, métadonnées, efficacité). Stockage binaire (emplacement, chiffrement, versions). Minimum pour démarrer (4 composants): Implémenter Path (représente fichier/répertoire). Étendre FileSystem (instance du système). Étendre FileSystemProvider (moteur, enregistré par scheme). Enregistrer FileSystemProvider via META-INF/services. Étapes suivantes: Couche BD (arborescence), opérations répertoire/fichier de base, stockage, tests. Processus long et exigeant, mais gratifiant.   Un article de brian goetz sur le futur du data oriented programming en Java https://openjdk.org/projects/amber/design-notes/beyond-records Le projet Amber de Java introduit les "carrier classes", une évolution des records qui permet plus de flexibilité tout en gardant les avantages du pattern matching et de la reconstruction Les records imposent des contraintes strictes (immutabilité, représentation exacte de l'état) qui limitent leur usage pour des classes avec état muable ou dérivé Les carrier classes permettent de déclarer une state description complète et canonique sans imposer que la représentation interne corresponde exactement à l'API publique Le modificateur "component" sur les champs permet au compilateur de dériver automatiquement les accesseurs pour les composants alignés avec la state description Les compact constructors sont généralisés aux carrier classes, générant automatiquement l'initialisation des component fields Les carrier classes supportent la déconstruction via pattern matching comme les records, rendant possible leur usage dans les instanceof et switch Les carrier interfaces permettent de définir une state description sur une interface, obligeant les implémentations à fournir les accesseurs correspondants L'extension entre carrier classes est possible, avec dérivation automatique des appels super() quand les composants parent sont subsumés par l'enfant Les records deviennent un cas particulier de carrier classes avec des contraintes supplémentaires (final, extends Record, component fields privés et finaux obligatoires) L'évolution compatible des records est améliorée en permettant l'ajout de composants en fin de liste et la déconstruction partielle par préfixe Comment éviter les pièges courants avec JPA et Kotlin - https://blog.jetbrains.com/idea/2026/01/how-to-avoid-common-pitfalls-with-jpa-and-kotlin/ JPA est une spécification Java pour la persistance objet-relationnel, mais son utilisation avec Kotlin présente des incompatibilités dues aux différences de conception des deux langages Les classes Kotlin sont finales par défaut, ce qui empêche la création de proxies par JPA pour le lazy loading et les opérations transactionnelles Le plugin kotlin-jpa génère automatiquement des constructeurs sans argument et rend les classes open, résolvant les problèmes de compatibilité Les data classes Kotlin ne sont pas adaptées aux entités JPA car elles génèrent equals/hashCode basés sur tous les champs, causant des problèmes avec les relations lazy L'utilisation de lateinit var pour les relations peut provoquer des exceptions si on accède aux propriétés avant leur initialisation par JPA Les types non-nullables Kotlin peuvent entrer en conflit avec le comportement de JPA qui initialise les entités avec des valeurs null temporaires Le backing field direct dans les getters/setters personnalisés peut contourner la logique de JPA et casser le lazy loading IntelliJ IDEA 2024.3 introduit des inspections pour détecter automatiquement ces problèmes et propose des quick-fixes L'IDE détecte les entités finales, les data classes inappropriées, les problèmes de constructeurs et l'usage incorrect de lateinit Ces nouvelles fonctionnalités aident les développeurs à éviter les bugs subtils liés à l'utilisation de JPA avec Kotlin Librairies Guide sur MapStruct @IterableMapping - https://www.baeldung.com/java-mapstruct-iterablemapping MapStruct est une bibliothèque Java pour générer automatiquement des mappers entre beans, l'annotation @IterableMapping permet de configurer finement le mapping de collections L'attribut dateFormat permet de formater automatiquement des dates lors du mapping de listes sans écrire de boucle manuelle L'attribut qualifiedByName permet de spécifier quelle méthode custom appliquer sur chaque élément de la collection à mapper Exemple d'usage : filtrer des données sensibles comme des mots de passe en mappant uniquement certains champs via une méthode dédiée L'attribut nullValueMappingStrategy permet de contrôler le comportement quand la collection source est null (retourner null ou une collection vide) L'annotation fonctionne pour tous types de collections Java (List, Set, etc.) et génère le code de boucle nécessaire Possibilité d'appliquer des formats numériques avec numberFormat pour convertir des nombres en chaînes avec un format spécifique MapStruct génère l'implémentation complète du mapper au moment de la compilation, éliminant le code boilerplate L'annotation peut être combinée avec @Named pour créer des méthodes de mapping réutilisables et nommées Le mapping des collections supporte les conversions de types complexes au-delà des simples conversions de types primitifs Accès aux fichiers Samba depuis Java avec JCIFS - https://www.baeldung.com/java-samba-jcifs JCIFS est une bibliothèque Java permettant d'accéder aux partages Samba/SMB sans monter de lecteur réseau, supportant le protocole SMB3 on pense aux galériens qui doivent se connecter aux systèmes dit legacy La configuration nécessite un contexte CIFS (CIFSContext) et des objets SmbFile pour représenter les ressources distantes L'authentification se fait via NtlmPasswordAuthenticator avec domaine, nom d'utilisateur et mot de passe La bibliothèque permet de lister les fichiers et dossiers avec listFiles() et vérifier leurs propriétés (taille, date de modification) Création de fichiers avec createNewFile() et de dossiers avec mkdir() ou mkdirs() pour créer toute une arborescence Suppression via delete() qui peut parcourir et supprimer récursivement des arborescences entières Copie de fichiers entre partages Samba avec copyTo(), mais impossibilité de copier depuis le système de fichiers local Pour copier depuis le système local, utilisation des streams SmbFileInputStream et SmbFileOutputStream Les opérations peuvent cibler différents serveurs Samba et différents partages (anonymes ou protégés par mot de passe) La bibliothèque s'intègre dans des blocs try-with-resources pour une gestion automatique des ressources Quarkus 3.31 - Support complet Java 25, nouveau packaging Maven et Panache Next - https://quarkus.io/blog/quarkus-3-31-released/ Support complet de Java 25 avec images runtime et native Nouveau packaging Maven de type quarkus avec lifecycle optimisé pour des builds plus rapides voici un article complet pour plus de detail https://quarkus.io/blog/building-large-applications/ Introduction de Panache Next, nouvelle génération avec meilleure expérience développeur et API unifiée ORM/Reactive Mise à jour vers Hibernate ORM 7.2, Reactive 3.2, Search 8.2 Support de Hibernate Spatial pour les données géospatiales Passage à Testcontainers 2 et JUnit 6 Annotations de sécurité supportées sur les repositories Jakarta Data Chiffrement des tokens OIDC pour les implémentations custom TokenStateManager Support OAuth 2.0 Pushed Authorization Requests dans l'extension OIDC Maven 3.9 maintenant requis minimum pour les projets Quarkus A2A Java SDK 1.0.0.Alpha1 - Alignement avec la spécification 1.0 du protocole Agent2Agent - https://quarkus.io/blog/a2a-java-sdk-1-0-0-alpha1/ Le SDK Java A2A implémente le protocole Agent2Agent qui permet la communication standardisée entre agents IA pour découvrir des capacités, déléguer des tâches et collaborer Passage à la version 1.0 de la spécification marque la transition d'expérimental à production-ready avec des changements cassants assumés Modernisation complète du module spec avec des Java records partout remplaçant le mix précédent de classes et records pour plus de cohérence Adoption de Protocol Buffers comme source de vérité avec des mappers MapStruct pour la conversion et Gson pour JSON-RPC Les builders utilisent maintenant des méthodes factory statiques au lieu de constructeurs publics suivant les best practices Java modernes Introduction de trois BOMs Maven pour simplifier la gestion des dépendances du SDK core, des extensions et des implémentations de référence Quarkus AgentCard évolue avec une liste supportedInterfaces remplaçant url et preferredTransport pour plus de flexibilité dans la déclaration des protocoles Support de la pagination ajouté pour ListTasks et les endpoints de configuration des notifications push avec des wrappers Result appropriés Interface A2AHttpClient pluggable permettant des implémentations HTTP personnalisées avec une implémentation Vert.x fournie Travail continu vers la conformité complète avec le TCK 1.0 en cours de développement parallèlement à la finalisation de la spécification Pourquoi Quarkus finit par "cliquer" : les 10 questions que se posent les développeurs Java - https://www.the-main-thread.com/p/quarkus-java-developers-top-questions-2025 un article qui revele et repond aux questions des gens qui ont utilisé Quarkus depuis 4-6 mois, les non noob questions Quarkus est un framework Java moderne optimisé pour le cloud qui propose des temps de démarrage ultra-rapides et une empreinte mémoire réduite Pourquoi Quarkus démarre si vite ? Le framework effectue le travail lourd au moment du build (scanning, indexation, génération de bytecode) plutôt qu'au runtime Quand utiliser le mode réactif plutôt qu'impératif ? Le réactif est pertinent pour les workloads avec haute concurrence et dominance I/O, l'impératif reste plus simple dans les autres cas Quelle est la différence entre Dev Services et Testcontainers ? Dev Services utilise Testcontainers en gérant automatiquement le cycle de vie, les ports et la configuration sans cérémonie Comment la DI de Quarkus diffère de Spring ? CDI est un standard basé sur la sécurité des types et la découverte au build-time, différent de l'approche framework de Spring Comment gérer la configuration entre environnements ? Quarkus permet de scaler depuis le développement local jusqu'à Kubernetes avec des profils, fichiers multiples et configuration externe Comment tester correctement les applications Quarkus ? @QuarkusTest démarre l'application une fois pour toute la suite de tests, changeant le modèle mental par rapport à Spring Boot Que fait vraiment Panache en coulisses ? Panache est du JPA avec des opinions fortes et des défauts propres, enveloppant Hibernate avec un style Active Record Doit-on utiliser les images natives et quand ? Les images natives brillent pour le serverless et l'edge grâce au démarrage rapide et la faible empreinte mémoire, mais tous les apps n'en bénéficient pas Comment Quarkus s'intègre avec Kubernetes ? Le framework génère automatiquement les ressources Kubernetes, gère les health checks et métriques comme s'il était nativement conçu pour cet écosystème Comment intégrer l'IA dans une application Quarkus ? LangChain4j permet d'ajouter embeddings, retrieval, guardrails et observabilité directement en Java sans passer par Python Infrastructure Les alternatives à MinIO https://rmoff.net/2026/01/14/alternatives-to-minio-for-single-node-local-s3/ MinIO a abandonné le support single-node fin 2025 pour des raisons commerciales, cassant de nombreuses démos et pipelines CI/CD qui l'utilisaient pour émuler S3 localement L'auteur cherche un remplacement simple avec image Docker, compatibilité S3, licence open source, déploiement mono-nœud facile et communauté active S3Proxy est très léger et facile à configurer, semble être l'option la plus simple mais repose sur un seul contributeur RustFS est facile à utiliser et inclut une GUI, mais c'est un projet très récent en version alpha avec une faille de sécurité majeure récente SeaweedFS existe depuis 2012 avec support S3 depuis 2018, relativement facile à configurer et dispose d'une interface web basique Zenko CloudServer remplace facilement MinIO mais la documentation et le branding (cloudserver/zenko/scality) peuvent prêter à confusion Garage nécessite une configuration complexe avec fichier TOML et conteneur d'initialisation séparé, pas un simple remplacement drop-in Apache Ozone requiert au minimum quatre nœuds pour fonctionner, beaucoup trop lourd pour un usage local simple L'auteur recommande SeaweedFS et S3Proxy comme remplaçants viables, RustFS en maybe, et élimine Garage et Ozone pour leur complexité Garage a une histoire tres associative, il vient du collectif https://deuxfleurs.fr/ qui offre un cloud distribué sans datacenter C'est certainement pas une bonne idée, les datacenters dans l'espace https://taranis.ie/datacenters-in-space-are-a-terrible-horrible-no-good-idea/ Avis d'expert (ex-NASA/Google, Dr en électronique spatiale) : Centres de données spatiaux, une "terrible" idée. Incompatibilité fondamentale : L'électronique (surtout IA/GPU) est inadaptée à l'environnement spatial. Énergie : Accès limité. Le solaire (type ISS) est insuffisant pour l'échelle de l'IA. Le nucléaire (RTG) est trop faible. Refroidissement : L'espace n'est pas "froid" ; absence de convection. Nécessite des radiateurs gigantesques (ex: 531m² pour 200kW). Radiations : Provoque erreurs (SEU, SEL) et dommages. Les GPU sont très vulnérables. Blindage lourd et inefficace. Les puces "durcies" sont très lentes. Communications : Bande passante très limitée (1Gbps radio vs 100Gbps terrestre). Le laser est tributaire des conditions atmosphériques. Conclusion : Projet extrêmement difficile, coûteux et aux performances médiocres. Data et Intelligence Artificielle Guillaume a développé un serveur MCP pour arXiv (le site de publication de papiers de recherche) en Java avec le framework Quarkus https://glaforge.dev/posts/2026/01/18/implementing-an-arxiv-mcp-server-with-quarkus-in-java/ Implémentation d'un serveur MCP (Model Context Protocol) arXiv en Java avec Quarkus. Objectif : Accéder aux publications arXiv et illustrer les fonctionnalités moins connues du protocole MCP. Mise en œuvre : Utilisation du framework Quarkus (Java) et son support MCP étendu. Assistance par Antigravity (IDE agentique) pour le développement et l'intégration de l'API arXiv. Interaction avec l'API arXiv : requêtes HTTP, format XML Atom pour les résultats, parser XML Jackson. Fonctionnalités MCP exposées : Outils (@Tool) : Recherche de publications (search_papers). Ressources (@Resource, @ResourceTemplate) : Taxonomie des catégories arXiv, métadonnées des articles (via un template d'URI). Prompts (@Prompt) : Exemples pour résumer des articles ou construire des requêtes de recherche. Configuration : Le serveur peut fonctionner en STDIO (local) ou via HTTP Streamable (local ou distant), avec une configuration simple dans des clients comme Gemini CLI. Conclusion : Quarkus simplifie la création de serveurs MCP riches en fonctionnalités, rendant les données et services "prêts pour l'IA" avec l'aide d'outils d'IA comme Antigravity. Anthropic ne mettra pas de pub dans Claude https://www.anthropic.com/news/claude-is-a-space-to-think c'est en reaction au plan non public d'OpenAi de mettre de la pub pour pousser les gens au mode payant OpenAI a besoin de cash et est probablement le plus utilisé pour gratuit au monde Anthropic annonce que Claude restera sans publicité pour préserver son rôle d'assistant conversationnel dédié au travail et à la réflexion approfondie. Les conversations avec Claude sont souvent sensibles, personnelles ou impliquent des tâches complexes d'ingénierie logicielle où les publicités seraient inappropriées. L'analyse des conversations montre qu'une part significative aborde des sujets délicats similaires à ceux évoqués avec un conseiller de confiance. Un modèle publicitaire créerait des incitations contradictoires avec le principe fondamental d'être "genuinely helpful" inscrit dans la Constitution de Claude. Les publicités introduiraient un conflit d'intérêt potentiel où les recommandations pourraient être influencées par des motivations commerciales plutôt que par l'intérêt de l'utilisateur. Le modèle économique d'Anthropic repose sur les contrats entreprise et les abonnements payants, permettant de réinvestir dans l'amélioration de Claude. Anthropic maintient l'accès gratuit avec des modèles de pointe et propose des tarifs réduits pour les ONG et l'éducation dans plus de 60 pays. Le commerce "agentique" sera supporté mais uniquement à l'initiative de l'utilisateur, jamais des annonceurs, pour préserver la confiance. Les intégrations tierces comme Figma, Asana ou Canva continueront d'être développées en gardant l'utilisateur aux commandes. Anthropic compare Claude à un cahier ou un tableau blanc : des espaces de pensée purs, sans publicité. Infinispan 16.1 est sorti https://infinispan.org/blog/2026/02/04/infinispan-16-1 déjà le nom de la release mérite une mention Le memory bounded par cache et par ensemble de cache s est pas facile à faire en Java Une nouvelle api OpenAPI AOT caché dans les images container Un serveur MCP local juste avec un fichier Java ? C'est possible avec LangChain4j et JBang https://glaforge.dev/posts/2026/02/11/zero-boilerplate-java-stdio-mcp-servers-with-langchain4j-and-jbang/ Création rapide de serveurs MCP Java sans boilerplate. MCP (Model Context Protocol): standard pour connecter les LLM à des outils et données. Le tutoriel répond au manque d'options simples pour les développeurs Java, face à une prédominance de Python/TypeScript dans l'écosystème MCP. La solution utilise: LangChain4j: qui intègre un nouveau module serveur MCP pour le protocole STDIO. JBang: permet d'exécuter des fichiers Java comme des scripts, éliminant les fichiers de build (pom.xml, Gradle). Implémentation: se fait via un seul fichier .java. JBang gère automatiquement les dépendances (//DEPS). L'annotation @Tool de LangChain4j expose les méthodes Java aux LLM. StdioMcpServerTransport gère la communication JSON-RPC via l'entrée/sortie standard (STDIO). Point crucial: Les logs doivent impérativement être redirigés vers System.err pour éviter de corrompre System.out, qui est réservé à la communication MCP (messages JSON-RPC). Facilite l'intégration locale avec des outils comme Gemini CLI, Claude Code, etc. Reciprocal Rank Fusion : un algorithme utile et souvent utilisé pour faire de la recherche hybride, pour mélanger du RAG et des recherches par mots-clé https://glaforge.dev/posts/2026/02/10/advanced-rag-understanding-reciprocal-rank-fusion-in-hybrid-search/ RAG : Qualité LLM dépend de la récupération. Recherche Hybride : Combiner vectoriel et mots-clés (BM25) est optimal. Défi : Fusionner des scores d'échelles différentes. Solution : Reciprocal Rank Fusion (RRF). RRF : Algorithme robuste qui fusionne des listes de résultats en se basant uniquement sur le rang des documents, ignorant les scores. Avantages RRF : Pas de normalisation de scores, scalable, excellente première étape de réorganisation. Architecture RAG fréquente : RRF (large sélection) + Cross-Encoder / modèle de reranking (précision fine). RAG-Fusion : Utilise un LLM pour générer plusieurs variantes de requête, puis RRF agrège tous les résultats pour renforcer le consensus et réduire les hallucinations. Implémentation : LangChain4j utilise RRF par défaut pour agréger les résultats de plusieurs retrievers. Les dernières fonctionnalités de Gemini et Nano Banana supportées dans LangChain4j https://glaforge.dev/posts/2026/02/06/latest-gemini-and-nano-banana-enhancements-in-langchain4j/ Nouveaux modèles d'images Nano Banana (Gemini 2.5/3.0) pour génération et édition (jusqu'à 4K). "Grounding" via Google Search (pour images et texte) et Google Maps (localisation, Gemini 2.5). Outil de contexte URL (Gemini 3.0) pour lecture directe de pages web. Agents multimodaux (AiServices) capables de générer des images. Configuration de la réflexion (profondeur Chain-of-Thought) pour Gemini 3.0. Métadonnées enrichies : usage des tokens et détails des sources de "grounding". Comment configurer Gemini CLI comment agent de code dans IntelliJ grâce au protocole ACP https://glaforge.dev/posts/2026/02/01/how-to-integrate-gemini-cli-with-intellij-idea-using-acp/ But : Intégrer Gemini CLI à IntelliJ IDEA via l'Agent Client Protocol (ACP). Prérequis : IntelliJ IDEA 2025.3+, Node.js (v20+), Gemini CLI. Étapes : Installer Gemini CLI (npm install -g @google/gemini-cli). Localiser l'exécutable gemini. Configurer ~/.jetbrains/acp.json (chemin exécutable, --experimental-acp, use_idea_mcp: true). Redémarrer IDEA, sélectionner "Gemini CLI" dans l'Assistant IA. Usage : Gemini interagit avec le code et exécute des commandes (contexte projet). Important : S'assurer du flag --experimental-acp dans la configuration. Outillage PipeNet, une alternative (open source aussi) à LocalTunnel, mais un plus évoluée https://pipenet.dev/ pipenet: Alternative open-source et moderne à localtunnel (client + serveur). Usages: Développement local (partage, webhooks), intégration SDK, auto-hébergement sécurisé. Fonctionnalités: Client (expose ports locaux, sous-domaines), Serveur (déploiement, domaines personnalisés, optimisé cloud mono-port). Avantages vs localtunnel: Déploiement cloud sur un seul port, support multi-domaines, TypeScript/ESM, maintenance active. Protocoles: HTTP/S, WebSocket, SSE, HTTP Streaming. Intégration: CLI ou SDK JavaScript. JSON-IO — une librairie comme Jackson ou GSON, supportant JSON5, TOON, et qui pourrait être utile pour l'utilisation du "structured output" des LLMs quand ils ne produisent pas du JSON parfait https://github.com/jdereg/json-io json-io : Librairie Java pour la sérialisation et désérialisation JSON/TOON. Gère les graphes d'objets complexes, les références cycliques et les types polymorphes. Support complet JSON5 (lecture et écriture), y compris des fonctionnalités non prises en charge par Jackson/Gson. Format TOON : Notation orientée token, optimisée pour les LLM, réduisant l'utilisation de tokens de 40 à 50% par rapport au JSON. Légère : Aucune dépendance externe (sauf java-util), taille de JAR réduite (~330K). Compatible JDK 1.8 à 24, ainsi qu'avec les environnements JPMS et OSGi. Deux modes de conversion : vers des objets Java typés (toJava()) ou vers des Map (toMaps()). Options de configuration étendues via ReadOptionsBuilder et WriteOptionsBuilder. Optimisée pour les déploiements cloud natifs et les architectures de microservices. Utiliser mailpit et testcontainer pour tester vos envois d'emails https://foojay.io/today/testing-emails-with-testcontainers-and-mailpit/ l'article montre via SpringBoot et sans. Et voici l'extension Quarkus https://quarkus.io/extensions/io.quarkiverse.mailpit/quarkus-mailpit/?tab=docs Tester l'envoi d'emails en développement est complexe car on ne peut pas utiliser de vrais serveurs SMTP Mailpit est un serveur SMTP de test qui capture les emails et propose une interface web pour les consulter Testcontainers permet de démarrer Mailpit dans un conteneur Docker pour les tests d'intégration L'article montre comment configurer une application SpringBoot pour envoyer des emails via JavaMail Un module Testcontainers dédié à Mailpit facilite son intégration dans les tests Le conteneur Mailpit expose un port SMTP (1025) et une API HTTP (8025) pour vérifier les emails reçus Les tests peuvent interroger l'API HTTP de Mailpit pour valider le contenu des emails envoyés Cette approche évite d'utiliser des mocks et teste réellement l'envoi d'emails Mailpit peut aussi servir en développement local pour visualiser les emails sans les envoyer réellement La solution fonctionne avec n'importe quel framework Java supportant JavaMail Architecture Comment scaler un système de 0 à 10 millions d'utilisateurs https://blog.algomaster.io/p/scaling-a-system-from-0-to-10-million-users Philosophie : Scalabilité incrémentale, résoudre les goulots d'étranglement sans sur-ingénierie. 0-100 utilisateurs : Serveur unique (app, DB, jobs). 100-1K : Séparer app et DB (services gérés, pooling). 1K-10K : Équilibreur de charge, multi-serveurs d'app (stateless via sessions partagées). 10K-100K : Caching, réplicas de lecture DB, CDN (réduire charge DB). 100K-500K : Auto-scaling, applications stateless (authentification JWT). 500K-10M : Sharding DB, microservices, files de messages (traitement asynchrone). 10M+ : Déploiement multi-régions, CQRS, persistance polyglotte, infra personnalisée. Principes clés : Simplicité, mesure, stateless essentiel, cache/asynchrone, sharding prudent, compromis (CAP), coût de la complexité. Patterns d'Architecture 2026 - Du Hype à la Réalité du Terrain (Part 1/2) - https://blog.ippon.fr/2026/01/30/patterns-darchitecture-2026-part-1/ L'article présente quatre patterns d'architecture logicielle pour répondre aux enjeux de scalabilité, résilience et agilité business dans les systèmes modernes Il présentent leurs raisons et leurs pièges Un bon rappel L'Event-Driven Architecture permet une communication asynchrone entre systèmes via des événements publiés et consommés, évitant le couplage direct Les bénéfices de l'EDA incluent la scalabilité indépendante des composants, la résilience face aux pannes et l'ajout facile de nouveaux cas d'usage Le pattern API-First associé à un API Gateway centralise la sécurité, le routage et l'observabilité des APIs avec un catalogue unifié Le Backend for Frontend crée des APIs spécifiques par canal (mobile, web, partenaires) pour optimiser l'expérience utilisateur CQRS sépare les modèles de lecture et d'écriture avec des bases optimisées distinctes, tandis que l'Event Sourcing stocke tous les événements plutôt que l'état actuel Le Saga Pattern gère les transactions distribuées via orchestration centralisée ou chorégraphie événementielle pour coordonner plusieurs microservices Les pièges courants incluent l'explosion d'événements granulaires, la complexité du debugging distribué, et la mauvaise gestion de la cohérence finale Les technologies phares sont Kafka pour l'event streaming, Kong pour l'API Gateway, EventStoreDB pour l'Event Sourcing et Temporal pour les Sagas Ces patterns nécessitent une maturité technique et ne sont pas adaptés aux applications CRUD simples ou aux équipes junior Patterns d'architecture 2026 : du hype à la réalité terrain part. 2 - https://blog.ippon.fr/2026/02/04/patterns-darchitecture-2026-part-2/ Deuxième partie d'un guide pratique sur les patterns d'architecture logicielle et système éprouvés pour moderniser et structurer les applications en 2026 Strangler Fig permet de migrer progressivement un système legacy en l'enveloppant petit à petit plutôt que de tout réécrire d'un coup (70% d'échec pour les big bang) Anti-Corruption Layer protège votre nouveau domaine métier des modèles externes et legacy en créant une couche de traduction entre les systèmes Service Mesh gère automatiquement la communication inter-services dans les architectures microservices (sécurité mTLS, observabilité, résilience) Architecture Hexagonale sépare le coeur métier des détails techniques via des ports et adaptateurs pour améliorer la testabilité et l'évolutivité Chaque pattern est illustré par un cas client concret avec résultats mesurables et liste des pièges à éviter lors de l'implémentation Les technologies 2026 mentionnées incluent Istio, Linkerd pour service mesh, LaunchDarkly pour feature flags, NGINX et Kong pour API gateway Tableau comparatif final aide à choisir le bon pattern selon la complexité, le scope et le use case spécifique du projet L'article insiste sur une approche pragmatique : ne pas utiliser un pattern juste parce qu'il est moderne mais parce qu'il résout un problème réel Pour les systèmes simples type CRUD ou avec peu de services, ces patterns peuvent introduire une complexité inutile qu'il faut savoir éviter Méthodologies Le rêve récurrent de remplacer voire supprimer les développeurs https://www.caimito.net/en/blog/2025/12/07/the-recurring-dream-of-replacing-developers.html Depuis 1969, chaque décennie voit une tentative de réduire le besoin de développeurs (de COBOL, UML, visual builders… à IA). Motivation : frustration des dirigeants face aux délais et coûts de développement. La complexité logicielle est intrinsèque et intellectuelle, non pas une question d'outils. Chaque vague technologique apporte de la valeur mais ne supprime pas l'expertise humaine. L'IA assiste les développeurs, améliore l'efficacité, mais ne remplace ni le jugement ni la gestion de la complexité. La demande de logiciels excède l'offre car la contrainte majeure est la réflexion nécessaire pour gérer cette complexité. Pour les dirigeants : les outils rendent-ils nos développeurs plus efficaces sur les problèmes complexes et réduisent-ils les tâches répétitives ? Le "rêve" de remplacer les développeurs, irréalisable, est un moteur d'innovation créant des outils précieux. Comment creuser des sujets à l'ère de l'IA générative. Quid du partage et la curation de ces recherches ? https://glaforge.dev/posts/2026/02/04/researching-topics-in-the-age-of-ai-rock-solid-webhooks-case-study/ Recherche initiale de l'auteur sur les webhooks en 2019, processus long et manuel. L'IA (Deep Research, Gemini, NotebookLM) facilite désormais la recherche approfondie, l'exploration de sujets et le partage des résultats. L'IA a identifié et validé des pratiques clés pour des déploiements de webhooks résilients, en grande partie les mêmes que celles trouvées précédemment par l'auteur. Génération d'artefacts par l'IA : rapport détaillé, résumé concis, illustration sketchnote, et même une présentation (slide deck). Guillaume s'interroge sur le partage public de ces rapports de recherche générés par l'IA, tout en souhaitant éviter le "AI Slop". Loi, société et organisation Le logiciel menacé par le vibe coding https://www.techbuzz.ai/articles/we-built-a-monday-com-clone-in-under-an-hour-with-ai Deux journalistes de CNBC sans expérience de code ont créé un clone fonctionnel de Monday.com en moins de 60 minutes pour 5 à 15 dollars. L'expérience valide les craintes des investisseurs qui ont provoqué une baisse de 30% des actions des entreprises SaaS. L'IA a non seulement reproduit les fonctionnalités de base mais a aussi recherché Monday.com de manière autonome pour identifier et recréer ses fonctionnalités clés. Cette technique appelée "vibe-coding" permet aux non-développeurs de construire des applications via des instructions en anglais courant. Les entreprises les plus vulnérables sont celles offrant des outils "qui se posent sur le travail" comme Atlassian, Adobe, HubSpot, Zendesk et Smartsheet. Les entreprises de cybersécurité comme CrowdStrike et Palo Alto sont considérées plus protégées grâce aux effets de réseau et aux barrières réglementaires. Les systèmes d'enregistrement comme Salesforce restent plus difficiles à répliquer en raison de leur profondeur d'intégration et de données d'entreprise. Le coût de 5 à 15 dollars par construction permet aux entreprises de prototyper plusieurs solutions personnalisées pour moins cher qu'une seule licence Monday.com. L'expérience soulève des questions sur la pérennité du marché de 5 milliards de dollars des outils de gestion de projet face à l'IA générative. Conférences En complément de l'agenda des conférences de Aurélie Vache, il y a également le site https://javaconferences.org/ (fait par Brian Vermeer) avec toutes les conférences Java à venir ! La liste des conférences provenant de Developers Conferences Agenda/List par Aurélie Vache et contributeurs : 12-13 février 2026 : Touraine Tech #26 - Tours (France) 12-13 février 2026 : World Artificial Intelligence Cannes Festival - Cannes (France) 19 février 2026 : ObservabilityCON on the Road - Paris (France) 6 mars 2026 : WordCamp Nice 2026 - Nice (France) 18 mars 2026 : Jupyter Workshops: AI in Jupyter: Building Extensible AI Capabilities for Interactive Computing - Saint-Maur-des-Fossés (France) 18-19 mars 2026 : Agile Niort 2026 - Niort (France) 20 mars 2026 : Atlantique Day 2026 - Nantes (France) 26 mars 2026 : Data Days Lille - Lille (France) 26-27 mars 2026 : SymfonyLive Paris 2026 - Paris (France) 26-27 mars 2026 : REACT PARIS - Paris (France) 27-29 mars 2026 : Shift - Nantes (France) 31 mars 2026 : ParisTestConf - Paris (France) 31 mars 2026-1 avril 2026 : FlowCon France 2026 - Paris (France) 1 avril 2026 : AWS Summit Paris - Paris (France) 2 avril 2026 : Pragma Cannes 2026 - Cannes (France) 2-3 avril 2026 : Xen Spring Meetup 2026 - Grenoble (France) 7 avril 2026 : PyTorch Conference Europe - Paris (France) 9-10 avril 2026 : Android Makers by droidcon 2026 - Paris (France) 9-11 avril 2026 : Drupalcamp Grenoble 2026 - Grenoble (France) 16-17 avril 2026 : MiXiT 2026 - Lyon (France) 17-18 avril 2026 : Faiseuses du Web 5 - Dinan (France) 22-24 avril 2026 : Devoxx France 2026 - Paris (France) 23-25 avril 2026 : Devoxx Greece - Athens (Greece) 6-7 mai 2026 : Devoxx UK 2026 - London (UK) 12 mai 2026 : Lead Innovation Day - Leadership Edition - Paris (France) 19 mai 2026 : La Product Conf Paris 2026 - Paris (France) 21-22 mai 2026 : Flupa UX Days 2026 - Paris (France) 22 mai 2026 : AFUP Day 2026 Lille - Lille (France) 22 mai 2026 : AFUP Day 2026 Paris - Paris (France) 22 mai 2026 : AFUP Day 2026 Bordeaux - Bordeaux (France) 22 mai 2026 : AFUP Day 2026 Lyon - Lyon (France) 28 mai 2026 : DevCon 27 : I.A. & Vibe Coding - Paris (France) 28 mai 2026 : Cloud Toulouse 2026 - Toulouse (France) 29 mai 2026 : NG Baguette Conf 2026 - Paris (France) 29 mai 2026 : Agile Tour Strasbourg 2026 - Strasbourg (France) 2-3 juin 2026 : Agile Tour Rennes 2026 - Rennes (France) 2-3 juin 2026 : OW2Con - Paris-Châtillon (France) 3 juin 2026 : IA–NA - La Rochelle (France) 5 juin 2026 : TechReady - Nantes (France) 5 juin 2026 : Fork it! - Rouen - Rouen (France) 6 juin 2026 : Polycloud - Montpellier (France) 9 juin 2026 : JFTL - Montrouge (France) 9 juin 2026 : C: - Caen (France) 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) 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) 24-25 juin 2026 : Agi'Lille 2026 - Lille (France) 24-26 juin 2026 : BreizhCamp 2026 - Rennes (France) 2 juillet 2026 : Azur Tech Summer 2026 - Valbonne (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) 2 août 2026 : 4th Tech Summit on Artificial Intelligence & Robotics - Paris (France) 20-22 août 2026 : 4th Tech Summit on AI & Robotics - Paris (France) & Online 4 septembre 2026 : JUG Summer Camp 2026 - La Rochelle (France) 17-18 septembre 2026 : API Platform Conference 2026 - Lille (France) 24 septembre 2026 : PlatformCon Live Day Paris 2026 - Paris (France) 1 octobre 2026 : WAX 2026 - Marseille (France) 1-2 octobre 2026 : Volcamp - Clermont-Ferrand (France) 5-9 octobre 2026 : Devoxx Belgium - Antwerp (Belgium) 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/

-Introduction TomTom isn't just “navigation” anymore. In this episode of the InsurTech Leadership Podcast, Josh Hollander talks with Vinod Poomalai, Head of InsurTech Product Marketing at TomTom, about how insurers are using location, map, and traffic intelligence to improve how they price risk, validate claims, and build telematics programs that actually produce underwriting signal. Guest bio Vinod Pumalai leads go-to-market for TomTom's insurance and InsurTech vertical. His work focuses on helping carriers, brokers, actuaries, and InsurTech teams integrate TomTom's location and traffic data into risk models, pricing engines, and telematics workflows—with a practical emphasis on adoption inside real operating environments. Key topics -From static territories to live location intelligence -Why “territory” is a crude proxy—and how mobility patterns add resolution to risk. -Territory risk models powered by traffic + map data -How insurers use location and traffic attributes to refine pricing and portfolio strategy. -Telematics enablement: APIs, SDKs, and flexible integration -What teams actually plug into, and what the implementation path looks like in practice. -Claims validation and fraud detection using mobility history -Using historical mobility/traffic context to validate events faster and reduce leakage. -Where experimentation becomes operational value -The difference between demos and workflows that move loss ratio outcomes. -What the insurance market is missing in location data -Why the market has been underserved—and what that creates as an opportunity. -Talent and leadership required to make it real -Product, data, and insurance domain collaboration: what “good” looks like inside carriers. Quotes -“The insurance market as a whole is very underserved when it comes to location data, traffic data, and so on.” -“At the end of the day, what our clients really care about… is loss ratios.” -“Customers are leveraging our traffic data in validating auto insurance claims.” Resources -Vinod Poomalai: https://www.linkedin.com/in/vinod-kumar-poomalai/ -TomTom Insurtech: https://www.tomtom.com/solutions/insurtech/ -Joshua Hollander: https://www.linkedin.com/in/joshuarhollander/ If you found this useful, subscribe to the InsurTech Leadership Podcast on YouTube and your preferred podcast app. Share the episode with an underwriting, claims, or telematics leader on your team—and leave a review to help more operators find the show.

Hello Playdate Community! This week, Ryan and Don have the night off, while Nick interviews the Playdate community powerhouse, Xania Lasagna! If Xania's name isn't familiar, it should be!  Xania is the developer of many Playdate applications using Pulp and the SDK, and the editor of Uncrank'd Magazine.  We discuss each of her applications, her background, and her process for creation.   Xania's Games and Applications: Reach the Ocean Soothsayer: the Oraclepus Knows All Playdate Bunny Bundle App Fun in the Sun Playdate Bundle App Solaris Arcana: The Eye of the Soothsayer Terrorween Playdate Bundle App Snatchy Carrots Uncrank'd Zine App Yulelog (2025) Sacre Sleuth! Crank into '24 Shellslinger Spelltooth Uncrank'd Narrative Nexus Runeloop Pop, Fizz, Cheers! Uncrank'd Magazine: Uncrank'd News Uncrank'd Storefront - subscriptions, merchandise, and more! Uncrank'd Youtube Channel Tools Discussed: Procreate Aseprite Pulp Playdate SDK   Contact: Hello Playdate on Discord Hello Playdate on Bluesky Hello Playdate on YouTube Hello Playdate on Threads Hello Playdate on Instagram Playdatepodcast.com PDGames Pick of the Week Collection Indie Game of the Week Collection on itch.io Helloplaydatepodcast (at) gmail dot com Voice Mail - 1-(724)-BINGOS-1  (1-724-246-4671) For Amusement Only Games Merch DRAINED on Vinyl! For Amusement Only Podcast, Nick's EM Bingo and Pinball Podcast Game and Cast, Ryan's Handheld Gaming Podcast Series Tags: video games, gaming, handheld, handhelds, panic, playdate, play, date, yellow, crank, gameboy, ds, pocket, videogames, nintendo, sega, xbox, playstation, sony, vita, psp, ngage, itch.io, Keita Takahashi, katamari, gamegear

Elijah Straight, PM for Microsoft Agent Framework, walks through how to build a multi-agent workflow to automate work using the framework's graph-based orchestration capabilities. Microsoft Agent Framework is a multi-language SDK for Python and .NET that enables building, orchestrating, and deploying AI agents with support for streaming, checkpointing, and human-in-the-loop capabilities. Chapters 00:00 - Introduction 01:35 - Visualization of demo 04:11 - PowerPoint to be synthesized 05:03 - Start of demo 10:27 - GitHub 11:47 - Wrap up Recommended resources Learn Docs GitHub Connect Scott Hanselman | @SHanselman: https://x.com/SHanselman Elijah Straight | @elijahbuilds: https://x.com/elijahbuilds Azure Friday | Twitter/X: @AzureFriday Azure | Twitter/X: @Azure

Elijah Straight, PM for Microsoft Agent Framework, walks through how to build a multi-agent workflow to automate work using the framework's graph-based orchestration capabilities. Microsoft Agent Framework is a multi-language SDK for Python and .NET that enables building, orchestrating, and deploying AI agents with support for streaming, checkpointing, and human-in-the-loop capabilities. Chapters 00:00 - Introduction 01:35 - Visualization of demo 04:11 - PowerPoint to be synthesized 05:03 - Start of demo 10:27 - GitHub 11:47 - Wrap up Recommended resources Learn Docs GitHub Connect Scott Hanselman | @SHanselman: https://x.com/SHanselman Elijah Straight | @elijahbuilds: https://x.com/elijahbuilds Azure Friday | Twitter/X: @AzureFriday Azure | Twitter/X: @Azure

Sats Terminal is the first native Bitcoin super app, bringing together Bitcoin loans, yield, and trading in a single interface and developer SDK. Sats Terminal is backed by YZi Labs (formerly Binance Labs), Coinbase Ventures, and Draper Associates.The founders of Sats Terminal recently joined the Bitcoin.com News Podcast to talk about the technology.Stan Havryliuk (CEO and Co-Founder) and Rishabh Java (CTO and Co-Founder) of Sats Terminal shared their journey, starting with their backgrounds in crypto and fintech. Stan had previous experience with Bitcoin.com and running a large Eastern European exchange, while Java had built and sold a fintech company, finding crypto to be a more open building environment. The inspiration for Sats Terminal stemmed from a highly problematic user experience Stan encountered while trading BRC20s, which resulted in him overpaying significantly for a single token. This incident highlighted a clear need for good, user-friendly interfaces in the growing Bitcoin DeFi market to encourage wider adoption. The two founders met online while working on a previous project and formalized their partnership after meeting in person in Buenos Aires.The company secured notable financial backing from major investors. Java's connection to Coinbase Ventures was established after winning an AI agent hackathon at their San Francisco office, which led to a successful pitch. Stan described how they were quickly accepted into the YZi Labs (aka Binance Labs) accelerator program after applying shortly before the deadline on a friend's recommendation, benefiting from a good product growth trajectory at the time. They also received early backing from the Draper family of VCs, including Draper Associates, Draper Dragon, and Boost VC. Stan's key advice for aspiring startups seeking funding is to "just keep building" and iterating fast, emphasizing that consistency compounds into success, alongside networking and participating in hackathons.Java elaborated on the evolution of native Bitcoin assets, moving from Ordinals to BRC20s and then to the improved Runes standard. He reported that Sats Terminal has already captured approximately 70% of the market share for trading Runes, showcasing their success in the ecosystem. They also acknowledged that the Bitcoin ecosystem's complexity, due to the lack of a central authority, means the market will ultimately decide which token standard becomes the long-term winner.The core of Sats Terminal's vision is encapsulated in their motto: "never sell your Bitcoin," but instead to make it work through products like trading, earning, and borrowing. Stan highlighted their belief that Bitcoin is the "only pristine collateral for loans," and their products are laying the groundwork for Bitcoin's transition from "digital gold" to a "productive asset." Java detailed their Borrow product as a self-custody, trust-minimized cross-chain loan solution where users can collateralize their Bitcoin for a loan without KYC. Stan announced that the first version of the Earn product, designed to simplify DeFi complexity for end-users, is being finalized and expected to go live in the next few weeks.Stan Havryliuk, CEO and Co-Founder of Sats Terminal, early Bitcoin investor and Web3 veteran with over eight years of experience scaling crypto businesses worldwide. Ex-Bitcoin.com and zondacrypto.com (BitBay.com).Rishabh Java, CTO and Co-Founder of Sats Terminal, serial entrepreneur, inventor, and Bitcoin builder with a proven track record of creating great technologies. Winner of 50 international hackathons, awarded by Steve Wozniak at 15 for BCI tech and exited Web2 startup at 21.To learn more about the project visit the website, and follow the team on X.

In this episode, the discussion revolves around Breez's innovative SDK and its nodeless implementation, which simplifies the integration of Bitcoin and Lightning into applications. The guests share their experiences from the ‘Time to Build' challenge, highlighting the ease of use and the potential for new applications in the Bitcoin ecosystem. Brianna discusses her social events platform, Evento, and how it leverages the Breez SDK to facilitate peer-to-peer value exchange. Aljaz shares insights on developing a BTC Pay plugin that enhances payment processing without the need for a full Lightning node. The conversation also touches on user experience design, the role of vibe coding in development, and the growing excitement around Bitcoin and Layer 2 solutions.Takeaways:

Join Christina Warren and Brett Terpstra as they navigate the freezing Minnesotan cold without running water, delve into the intersection of tech and political turmoil, and explore the latest in AI agents and multi-agent workflows. Dive into a whirlwind of emotions, tech tips, and political ranting, all while contemplating the ethics of open source funding and AI coding. From brutal weather updates to philosophical debates on modern fascism, this episode pulls no punches. Sponsor Copilot Money can help you take control of your finances. Get a fresh start with your money for 2026 with 2 months free when you visit try.copilot.money/overtired. Show Links Crimethinc: Being “Peaceful” and “Law-Abiding” Will Not Stop Authoritarianism Gas Town Apex OpenCode Backdrop Cindori Sensei Moltbot Chapters 00:00 Introduction and Host Updates 00:21 Brett’s Water Crisis 02:27 Political Climate and Media Suppression 06:32 Police Violence and Public Response 18:31 Social Media and Surveillance 22:15 Sponsor Break: Copilot Money 26:20 Tech Talk: Gas Town and AI Agents 31:58 Crypto Controversies 37:09 Ethics in Journalism and Personal Dilemmas 39:45 The Future of Open Source and Cryptocurrency 45:03 Apex 1.0? 48:25 Challenges and Innovations in Markdown Processing 01:02:16 AI in Coding and Personal Assistants 01:06:36 GrAPPtitude 01:14:40 Conclusion and Upcoming Plans Join the Conversation Merch Come chat on Discord! Twitter/ovrtrd Instagram/ovrtrd Youtube Get the Newsletter Thanks! You’re downloading today’s show from CacheFly’s network BackBeat Media Podcast Network Check out more episodes at overtiredpod.com and subscribe on Apple Podcasts, Spotify, or your favorite podcast app. Find Brett as @ttscoff, Christina as @film_girl, Jeff as @jsguntzel, and follow Overtired at @ovrtrd on Twitter. Transcript AI Agents and Political Chaos Introduction and Host Updates Christina: [00:00:00] Welcome back. You’re listening to Overtired. I’m Christina Warren. Joined as always by Brett Terpstra. Jeff Severns. Guntzel could not be with us this week, um, but uh, but Brett and I are here. So Brett, how are you? How’s the cold? Brett: The cold. Brett’s Water Crisis Brett: So I’m going on day four without running water. Um, I drove to my parents last night to shower and we’re, we’re driving loads of dishes to friends’ house to wash them. We have big buckets of melted snow in our bathtub that we use to flush the Toyland. Um, and we have like big jugs with a spout on them for drinking water. So we’re surviving, but it is highly inconvenient. Um, and we don’t know yet if it’s a frozen pipe. Or if we have [00:01:00] a bad pump on our, well, uh, hopefully we’ll find that out today. But no guarantees because all the plumbers are very busy right now with negative 30 degree weather. They tend to get a lot of calls, lots of stuff happens. Um, so yeah, but I’m, I’m staying warm. I got a fireplace, I got my heat’s working Christina: I mean, that’s the important thing. Brett: and that went out, that went out twice, in, twice already. This winter, our heat has gone out, um, which I’m thankful. We, we finally, we added glycol to our, so our heat pumps water through, like, it’s not radiators, it’s like baseboard heat, but it, it uses water and. Um, and though we were getting like frozen spots, not burst pipes, just enough that the water wouldn’t go through fast enough to heat anything. So we added glycol to that [00:02:00] system to bring the freeze point down to like zero degrees. So it’s not perfect, but we also hardwired the pump so that it always circulates water, um, even when the heat’s not running. So hopefully it’ll never freeze again. That’s the goal. Um, and if we replace the well pump, that should be good for another 20 years. So hopefully after this things will be smoother. Political Climate and Media Suppression Brett: Um, yeah, but that, that’s all in addition to, you know, my state being occupied by federal agents and even in my small town, we’ve got people being like, abducted. Things are escalating quickly at this point, and a lot of it doesn’t get talked about on mainstream media. Um, but yeah, things, I don’t know, man. I think we’re making progress because, um, apparently Binos [00:03:00] getting retired Christina: I was going to say, I, I, I, I heard, I heard that, and I don’t know if that’s good or if that’s bad. Um, I can’t, I can’t tell. Brett: it’s, it’s like, it’s like if Trump died, we wouldn’t know if that was good or bad because JD Vance as president, like maybe things get way worse. Who knows? Uh, none of these, none of these actual figureheads are the solution. Removing them isn’t the solution to removing the kinda maga philosophy behind it. But yeah, and that’s also Jeff is, you know, highly involved and I, I won’t, I won’t talk about that for him. I hope we can get him monsoon to talk about that. Christina: No, me, me, me too. Because I’ve, I’ve been thinking about, about him and about you and about your whole area, your communities, you know, from several thousand miles away. Like all, all we, all we see is either what people post online, which of course now is being suppressed. [00:04:00] Uh, thanks a lot. You know, like, like the, oh, TikTok was gonna be so terrible. Chi the, the Chinese are gonna take over our, uh, our algorithms. Right? No, Larry Ellison is, is actually going to completely, you know, fuck up the algorithms, um, and, and suppress anything. I, yeah. Yeah. They’re, they’re Brett: is TikTok? Well, ’cause Victor was telling me that, they were seeing videos. Uh, you would see one frame of the video and then it would black out. And it all seemed to be videos that were negative towards the administration and we weren’t sure. Is this a glitch? Is this coincidence? Christina: well, they claim it’s a glitch, but I don’t believe it. Brett: Yeah, it seems, it seems Christina: I, I mean, I mean, I mean, the thing is like, maybe it is, maybe it is a glitch and we’re overreacting. I don’t know. Um, all I know is that they’ve given us absolutely zero reason to trust them, and so I don’t, and so, um, uh, apparently the, the state of California, this is, [00:05:00] so we are recording this on Tuesday morning. Apparently the state of California has said that they are going to look into whether things are being, you know, suppressed or not, and if that’s violating California law, um, because now that, that, that TikTok is, is controlled by an American entity, um, even if it is, you know, owned by like a, you know, uh, evil, uh, billionaire, you know, uh, crony sto fuck you, Larry Ellison. Um, uh, I guess that means we won’t be getting an Oracle sponsorship. Sorry. Um, uh, Brett: take it anyway. Christina: I, I know you wouldn’t, I know you wouldn’t. That’s why I felt safe saying that. Um, but, uh, but even if, if, if that were the case, like I, you know, but apparently like now that it is like a, you know, kind of, you know, state based like US thing, like California could step in and potentially make things difficult for them. I mean, I think that’s probably a lot of bluster on Newsom’s part. I don’t think that he could really, honestly achieve any sort of change if they are doing things to the algorithm. Brett: Yeah. Uh, [00:06:00] if, if laws even matter anymore, it would be something that got tied up in court for a long time Christina: Right. Which effectively wouldn’t matter. Right. And, and then that opens up a lot of other interesting, um, things about like, okay, well, you know, should we, like what, what is the role? Like even for algorithmically determined things of the government to even step in or whatever, right now, obviously does, I think, become like more of a speech issue if it’s government speech that’s being suppressed, but regardless, it, it is just, it’s bad. So I’ve been, I’ve been thinking about you, I’ve been thinking about Jeff. Police Violence and Public Response Christina: Um, you know, we all saw what happened over the weekend and, and, you know, people be, people are being murdered in the streets and I mean that, that, that’s what’s happening. And, Brett: white people no less, Christina: Right. Well, I mean, that’s the thing, right? Like, is that like, but, but, but they keep moving the bar. They, they keep moving the goalpost, right? So first it’s a white woman and, oh, she, she was, she was running over. The, the officer [00:07:00] or the ice guy, and it’s like, no, she wasn’t, but, but, but that, that’s immediately where they go and, and she’s, you know, radical whatever and, and, and a terrorist and this and that. Okay. Then you have a literal veterans affair nurse, right? Like somebody who literally, like, you know, has, has worked with, with, with combat veterans and has done those things. Who, um, is stepping in to help someone who’s being pepper sprayed, you know, is, is just observing. And because he happens to have, um, a, a, a, a gun on him legally, which he’s allowed to do, um, they immediately used that as cover to execute him. But if he hadn’t had the gun, they would’ve, they would’ve come up with something else. Oh, we thought he had a gun, and they, you know what I mean? So like, they, they got lucky with that one because they removed the method, the, the, the weapon and then shot him 10 times. You know, they literally executed him in the street. But if he hadn’t had a gun, they still would’ve executed. Brett: Yeah, no, for sure. Um, it’s really frustrating that [00:08:00] they took the gun away. So he was disarmed and, and immobilized and then they shot him. Um, like so that’s just a straight up execution. And then to bring, like, to say that it, he, because he had a gun, he was dangerous, is such a, an affront to America has spent so long fighting against gun control and saying that we had the right to carry fucking assault rifles in the Christina: Kyle Rittenhouse. Kyle Rittenhouse was literally acquitted. Right? Brett: Yeah. And he killed people. Christina: and, and he killed people. He was literally walking around little fucking stogey, you know, little blubbering little bitch, like, you know, crying, you know, he’s like carrying around like Rambo a gun and literally snipe shooting people. That’s okay. Brett: They defended Christina: if you have a. They defended him. Of course they did. Right? Of course they did. Oh, well he has the right to carry and this and that, and Oh, you should be able to be armed in [00:09:00] these places. Oh, no, but, but if you’re, um, somebody that we don’t like Brett: Yeah, Christina: and you have a concealed carry permit, and I don’t even know if he was really concealed. Right. Because I think that if you have it on your holster, I don’t even think that counts as concealed to Brett: was supposedly in Christina: I, I, I don’t, I don’t, I don’t. Brett: like it Christina: Which I don’t think counts as concealed. I think. Brett: No. Christina: Right, right. So, so, so, so, so that, that, that wouldn’t be concealed. Be because you have someone in, in that situation, then all of a sudden, oh, no. Now, now the, the key, the goalpost, okay, well, it’s fine if it’s, you know, uh, police we don’t like, or, or other people. And, and, and if you’re going after protesters, then you can shoot and kill whoever you want, um, because you’ve perceived a threat and you can take actions into your, to your own hands. Um, but now if you are even a white person, um, even, you know, someone who’s, who’s worked in Veterans Affairs, whatever, if, if you have, uh, even if you’re like a, a, a, you know, a, a gun owner and, and have permits, um, now [00:10:00] if we don’t like you and you are anywhere in the vicinity of anybody associated with law enforcement, now they have the right to shoot you dead. Like that’s, that’s, that’s the argument, which is insanity. Brett: so I’m, I’m just gonna point out that as the third right came to power, they disarmed the Jews and they disarmed the anarchists and the socialists and they armed the rest of the population and it became, um, gun control for people they didn’t like. Um, and this is, it’s just straight up the same playbook. There’s no, there’s no differentiation anymore. Christina: No, it, it, it actively makes me angry that, um, I, I could be, because, ’cause what can we do? And, and what they’re counting on is the fact that we’re all tired and we’re all kind of, you know, like just, [00:11:00] you know, from, from what happened, you know, six years ago and, and, and what happened, you know, five years ago. Um, and, and, and various things. I think a lot of people are, are just. It kind of like Brett: Sure. Christina: done with, with, with being able to, to, to, right. But now the actual fascism is here, right? Like, like we, we, we saw a, a, you know, a whiff of this on, on, on January 6th, but now it’s actual fascism and they control every branch of government. Brett: Yeah. Christina: And, um, and, and, and I, and I don’t know what we’re supposed to do, right? Like, I mean it, because I mean, you know, uh, Philadelphia is, is, is begging for, for, for them to come. And I think that would be an interesting kind of standoff. Seattle is this, this is what a friend of mine said was like, you know, you know Philadelphia, Filch Philadelphia is begging them to come. Seattle is like scared. Um, that, that they’re going to come, um, because honestly, like we’re a bunch of little bitch babies and, um, [00:12:00] people think they’re like, oh, you know the WTO. I’m like, yeah, that was, that was 27 years ago. Um, uh, I, I don’t think that Seattle has the juice to hold that sort of line again. Um, but I also don’t wanna find out, right? Like, but, but, but this is, this is the attack thing. It’s like, okay, why are they in Minnesota? Right? They’re what, like 130,000, um, Brett: exactly Christina: um, immigrants in, in Minnesota. There are, there are however many million in Texas, however many million in Florida. We know exactly why, right? This isn’t about. Anything more than Brett: in any way. Christina: and opt. Right, right. It has nothing, it has nothing to do with, with, with immigration anyway. I mean, even, even the Wall Street Journal. The Wall Street Journal who a, you know, ran an op-ed basically saying get out of Minnesota. They also, they also had like a, you know, a news story, which was not from the opinion board, which like broke down the, the, the footage showing, you know, that like the, the video footage doesn’t match the administration’s claims, but they also ran a story. Um, that [00:13:00] basically did the math, I guess, on like the number of, of criminals, um, or people with criminal records who have been deported. And at this point, like in, you know, and, and when things started out, like, I guess when the raid started out, the, the majority of the people that they were kind of going after were people who had criminal records. Now, whether they were really violent, the worst, the worst, I mean that’s, I’m, I’m not gonna get into that, but you could at least say like, they, they could at least say, oh, well these were people who had criminal records, whatever. Now some, some huge percentage, I think it’s close to 80% don’t have anything. And many of the people that do the, the criminal like thing that they would hold would be, you know, some sort of visa violation. Right. So it’s, it’s, it’s Brett: they deported a five-year-old kid after using him as bait to try to get the rest of his family. Christina: as bait. Brett: Yeah. And like it’s, it’s pretty deplorable. But I will say I am proud of Minnesota. Um, they have not backed [00:14:00] down. They have stood up in the face of increasing increasingly escalated attacks, and they have shown up in force thousands of people out in the streets. Like Conti, like last night they had a, um, well, yeah, I mean, it’s been ongoing, but, uh, what’s his name? Preddy Alex. Um, at the place where he was shot, they had a, like continuing kind of memorial protest, I guess, and there’s footage of like a thousand, a thousand mins surrounding about 50, um, ICE agents and. Like basically corralling them to the point where they were all backed into a corner and weren’t moving. And I don’t know what happened after that. Um, but thus far it hasn’t been violent on the part of protesters. It’s been very violent on the part of ice. I [00:15:00] personally, I don’t know where I stand on, like, I feel like the Democrats are urging pacifism because it affects their hold on power. And I don’t necessarily think that peace when they’re murdering us in the street. I don’t know if peace is the right response, but I don’t know. I’m not openly declaring that I support violence at this point, but. At the same time, do I not? I’m not sure. Like I keep going back and forth on is it time for a war or do we try to vote our way out of this? Christina: I mean, well, and the scary thing about voting our way out of this is will we even be able to have free elections, right? Be because they’re using any sort of anything, even the most benign sort of legal [00:16:00] protest, even if violence isn’t involved in all of a sudden, talks of the Insurrection Act come Brett: yeah. And Trump, Trump offered to pull out of Minnesota if Minnesota will turn over its voter database to the federal government. Like that’s just blatant, like that’s obviously the end goal is suppression. Christina: Right, right. And, and so to your point, I don’t know. Right. And I’m, I’m never somebody who would wanna advocate outwardly for violence, but I, I, I, I, I don’t know. I mean, they’re killing citizens in the streets. They’re assassinating people in cold blood. They’re executing people, right. That’s what they’re doing. They’re literally executing people in the streets and then covering it up in real time. Brett: if the argument is, if we are violent, it will cause them to kill us. They’re already killing Christina: already doing it. Right. So at, at this point, I mean, like, you know, I mean, like, w to your point, wars have been started for, for, for less, or for the exact same things. Brett: [00:17:00] Yeah. Christina: So, I don’t know. I don’t know. Um, I know that that’s a depressing way to probably do mental health corner and whatnot, but this is what’s happening in our world right now and in and in your community, and it’s, it’s terrifying. Brett: I’m going to link in the show notes an article from Crime Think that was written by, uh, people in Germany who have studied, um, both historical fascism and the current rise of the A FD, which will soon be the most powerful party in Germany, um, which is straight up a Nazi party. Um, and it, they offered, like their hope right now lies in America stopping fascism. Christina: Yeah. Brett: Like if we can, if we can stop fascism, then they believe the rest of Europe can stop fascism. Um, but like they, it, it’s a good article. It kind of, it kind of broaches the same questions I do about like, is it [00:18:00] time for violence? And they offer, like, we don’t, we’re not advocating for a civil war, but like Civil wars might. If you, if you, if you broach them as revolutions, it’s kind of, they’re kind of the same thing in cases like this. So anyway, I’ll, I’ll link that for anyone who wants to read kinda what’s going on in my head. I’m making a note to dig that up. I, uh, I love Crime Fake Oh and Blue Sky. Social Media and Surveillance Brett: Um, so I have not, up until very recently been an avid Blue Sky user. Um, I think I have like, I think I have maybe like 200 followers there and I follow like 50 people. But I’ve been expanding that and I am getting a ton of my news from Blue Sky and like to get stories from people on the ground, like news as it happens, unfiltered and Blue Sky has been [00:19:00] really good for that. Um, I, it’s. There’s not like an algorithm. I just get my stuff and like Macedon, I have a much larger following and I follow a lot more people, but it’s very tech, Christina: It’s very tech and, Brett: there for. Christina: well, and, and MAs on, um, understandably too is also European, um, in a lot of regards. And so it’s just, it’s not. Gonna have the same amount of, of people who are gonna be able to, at least for instances like this, like be on the ground and doing real-time stuff. It’s not, it doesn’t have like the more normy stuff. So, no, that makes sense. Um, no, that’s great. I think, yeah, blue Sky’s been been really good for, for these sorts of real-time events because again, they don’t have an algorithm. Like you can have one, like for a personalized kind of like for you feed or whatever, but in terms of what you see, you know, you see it naturally. You’re not seeing it being adjusted by anything, which can be good and bad. I, I think is good because nothing’s suppressing things and you see things in real time. It can be bad because sometimes you miss things, but I think on the whole, it’s better. [00:20:00] The only thing I will say, just to anyone listening and, and just to spread onto, you know, people in your communities too, from what I’ve observed from others, like, it does seem like the, the government and other sorts of, you know, uh, uh, the, you know, bodies like that are finally starting to pay more attention to blue sky in terms of monitoring things. And so that’s not to say don’t. You know, use it at all. But the same way, you don’t make threats on Twitter if you don’t want the Feds to show up at your house. Don’t make threats on Blue Sky, because it’s not just a little microcosm where, you know, no one will see it. People are, it, it’s still small, but it’s, it’s getting bigger to the point that like when people look at like where some of the, the, the fire hose, you know, things observable things are there, there seem to be more and more of them located in the Washington DC area, which could just be because data centers are there, who knows? But I’ve also just seen anecdotally, like people who have had, like other instances, it’s like, don’t, don’t think [00:21:00] that like, oh, okay, well, you know, no one’s monitoring this. Um, of course people are so just don’t be dumb, don’t, don’t say things that could potentially get you in trouble. Um. Brett: a political candidate in Florida. Um, had the cops show up at her house and read her one of her Facebook posts. I mean, this was local. This was local cops, but still, yeah, you Christina: right. Well, yeah, that’s the thing, right? No, totally. And, and my, my only point with that is we’ve known that they do that for Facebook and for, for, you know, Twitter and, and, uh, you know, Instagram and things like that, but they, but Blue Sky, like, I don’t know if it’s on background checks yet, but it, uh, like for, uh, for jobs and things like that, I, I, I don’t know if that’s happening, but it definitely is at that point where, um, I know that people are starting to monitor those things. So just, you know, uh, not even saying for you per se, but just for anybody out there, like, it’s awesome and I’m so glad that like, that’s where people can get information out, but don’t be like [00:22:00] lulled into this false sense of security. Like, oh, well they’re not gonna monitor this. They’re not Brett: Nobody’s watching me here. Christina: It is like, no, they are, they are. Um, so especially as it becomes, you know, more prominent. So I’m, I’m glad that that’s. That’s an option there too. Um, okay. Sponsor Break: Copilot Money Christina: This is like the worst possible segue ever, but should we go ahead and segue to our, our, our sponsor break? Brett: Let’s do it. Let’s, let’s talk about capitalism. Christina: All right. This episode is brought to you by copilot money. Copilot money is not just another finance app. It’s your personal finance partner designed to help you feel clear, calm, and in control of your money. Whether it’s tracking your spending, saving for specific goals, or simply getting the handle on your investments. Copilot money has you covered as we enter the new year. Clarity and control over our finances has never been more important with the recent shutdown of Mint and rising financial stress, for many consumers are looking for a modern, trustworthy tool to help navigate their financial journeys. That’s where copilot money comes in. [00:23:00] With this beautifully designed app, you can see all your bank accounts, spending, savings and goals and investments all in one place. Imagine easily tracking everything without the clutter of chaotic spreadsheets or outdated tools. It’s a practical way to start 2026 with a fresh financial outlook. And here’s the exciting part. As of December 15th, copilot money is now available on the web so you can manage your finances on any device that you choose. Plus, it offers a seamless experience that keeps your data secure with a privacy first approach, when you sign up using our link, you’ll get two months for free. So visit, try. Copilot money slash Overtired to get started with features like automatic subscription tracking so you never miss a renewal date and customizable savings goals to help you stay on track. Copilot money empowers you to take charge of your financial life with confidence. So why wait Start 2026 with clarity and purpose. Download copilot money on your devices or visit. Try copilot money slash [00:24:00] overti today to claim you’re two months free and embrace a more organized, stress-free approach to your finances. Try copilot.money/ Overtired. Brett: Awesome that I appreciate this segue. ’cause we, we, we could, we could be talking about other things. Um, like it’s, it feels so weird, like when I go on social media and I just want to post that like my water’s out. It feels out of place right now because there’s everything that’s going on feels so much more important than, Christina: Right. Brett: than anything else. Um, but there’s still a place for living our lives, um, Christina: there are a absolutely. I mean, and, and, and in a certain extent, like not to, I mean, maybe this is a little bit of a cope, but it’s like, if all we do is focus on the things that we can’t control at the expense of everything else, it’s like then they win. You know? Like, which, which isn’t, which, which isn’t even to [00:25:00] say, like, don’t talk about what’s happening. Don’t try to help, don’t try to speak out and, and, um, and do what we can do, but also. Like as individuals, there’s very little we can control about things. And being completely, you know, subsumed by that is, is not necessarily good either. Um, so yeah, there’s, there, there are other things going on and it’s important for us to get out of our heads. It’s important, especially for you, you know, being in the region, I think to be able to, to focus on other things and, and hopefully your water will be back soon. ’cause that sucks like that. I’ve been, I’ve been worried about you. I’m glad that you have heat. I’m glad you have internet. I’m glad you have power, but you know, the pipes being frozen and all that stuff is like, not Brett: it, the, the internet has also been down for up to six hours at a time. I don’t know why. There’s like an amplifier down on our street. Um, and that has sucked because I, out here, I live in a, I’m not gonna call it rural. Uh, we’re like five minutes from town, [00:26:00] but, um, we, we don’t. We have shitty internet. Like I pay for a gigabit and I get 500 megabits and it’s, and it’s up and down all the time and I hate it. But anyway. Tech Talk: Gas Town and AI Agents Brett: Let’s talk about, uh, let’s talk about Gas Town. What can you tell me about Gastown? Christina: Okay. So we’ve talked a lot about like AI agents and, um, kind of like, uh, coding, um, loops and, and things like that. And so Gastown, uh, which is available, um, at, I, it is not Gas Town. Let me find the URL, um, one second. It’s, it’s at a gas town. No, it’s not. Lemme find it. Um. Right. So this is a thing that, that Steve Yy, uh, has created, and [00:27:00] it is a multi-agent workspace manager. And so the idea is basically that you can be running like a lot of instances of, um, of, of Claude Code or, um, I guess you could use Codex. You could use, uh, uh, uh, co-pilot, um, SDK or CLI agent and whatnot. Um, and basically what it’s designed to do is to basically let you coordinate like multiple coding agents at one time so they can all be working on different tasks, but then instead of having, um, like the context get lost when agents restart, it creates like a, a persistent, um, like. Work state, which it uses with, with git on the backend, which is supposed to basically enable more multi-agent workflows. So, um, basically the idea would be like, you get, have multiple agents working at once, kind of talking to one another, handing things off, you know, each doing their own task and then coordinating the work with what the other ones are doing. But then you have like a persistent, um, uh, I guess kind of like, you know, layer in the backend so that if an agent has to restart or whatever, it’s not gonna lose the, [00:28:00] the context, um, that that’s happening. And you don’t have to manually, um, worry about things like, okay, you know, I’ve lost certain things in memory and, and I’ve, you know, don’t know how I’m, I’m managing all these things together. Um, there, there’s another project, uh, called Ralph, which is kind of based on this, this concept of like, what of Ralph Wickham was, you know, coding or, or was doing kind of a loop. And, and it’s, it’s, it’s a, it’s kind of a similar idea. Um, there’s also. Brett: my nose wouldn’t bleed so much if I just kept my finger out of there. Christina: Exactly, exactly. My cat’s breath smells like cat food. Um, and um, and so. Like there are ideas of like Ralph Loops and Gastown. And so these are a couple of like projects, um, that have really started to, uh, take over. So like, uh, Ralph is more of an autonomous AI agent loop that basically like it runs like over and over and over again until, uh, a task is done. Um, and, and a lot of people use, use Gastown and, [00:29:00] and, and Ralph together. Um, but yeah, no Ga gastown is is pretty cool. Um, we’ll we’re gonna talk about it more ’cause it’s my pick of the week. We’ll talk about Molt bot previously known as Claude Bot, which is, uses some, some similar ideas. But it’s really been interesting to see like how, like the, the multi-agent workflow, and by multi-agent, I mean like, people are running like 20 or 30 of them, you know, at a time. So it’s more than that, um, is really starting to become a thing that people can, uh, can do. Um, Brett: gets expensive though. Christina: I was, I was just about to say that’s the one thing, right? Most people who are using things like Gastown. Are using them with the Claude, um, code Max plans, which is $200 a month. And those plans do give you more value than like, what the, what it would be if you spent $200 in API credits, uh, but $200 a month. Like that’s not an expensive, that’s, you know, that, that’s, that, that, like, you know what I mean? Like, like that, that, that, that, that, that’s a lot of money to spend on these sorts of things. Um, but people [00:30:00] are getting good results out of it. It’s pretty cool. Um. There have been some open models, which of course, most people don’t have equipment that would be fast enough for them to, to run, uh, to be able to kind of do what they would want, um, reliably. But the, the AgTech stuff coming to some of the open models is better. And so if these things can continue, of course now we’re in a ram crisis and storage crisis and everything else, so who knows when the hardware will get good enough again, and we can, when we as consumers can even reasonably get things ourselves. But, but in, in theory, you know, if, if these sorts of things continue, I could see like a, a world where like, you know, some of the WAN models and some of the other things, uh, potentially, um, or Quinn models rather, um, could, uh. Be things that you could conceivably, like be running on your own equipment to run these sorts of nonstop ag agentic loops. But yeah, right now, like it’s really freaking cool and I’ve played around with it because I’m fortunate enough to have access to a lot of tokens. [00:31:00] Um, but yeah, I can get expensive real, real fast. Uh, but, but it’s still, it’s still pretty awesome. Brett: I do appreciate that. So, guest Town, the name is a reference to Mad Max and in the kind of, uh, vernacular that they built for things like background agents and I, uh, there’s a whole bunch, there are different levels of, of the interface that they kind of extrapolated on the gas town kind of metaphor for. Uh, I, it was, it, it, there were some interesting naming conventions and then they totally went in other directions with some of the names. It, they didn’t keep the theme very well, but, but still, uh, I appreciate Ralph Wig and Mad Max. That’s. It’s at the very least, it’s interesting. Christina: No, it definitely is. It definitely is. Crypto Controversies Christina: I will say that there’s been like a little bit [00:32:00] of a kerfuffle, uh, involved in both of those, uh, developers because, um, they’re both now promoting shit coins and, uh, and so that’s sort of an interesting thing. Um, basically there’s like this, this, this crypto company called bags that I guess apparently like if people want to, they will create crypto coins for popular open source projects, and then they will designate someone to, I guess get the, the gas fees, um, in, um, uh, a Solana parlance, uh, no pun intended, with the gas town, um, where basically like that’s, you know, like the, the, the fees that you spend to have the transaction work off of the blockchain, right? Like, especially if there’s. A lot of times that it would take, like, you pay a certain percentage of something and like those fees could be designated to an individual. And, um, in this case, like both of these guys were reached out to when basically they were like, Hey, this coin exists. You’ve got all this money just kind of sitting in a crypto wallet waiting for you. [00:33:00] Take the money, get, get the, the transaction fees, so to speak. And, uh, I mean, I think that, that, that’s, if you wanna take that money right, it’s, it’s there for you. I’m not gonna certainly judge anyone for that. What I will judge you for is if you then promote your shit coin to your community and basically kind of encourage everyone. To kind of buy into it. Maybe you put in the caveat, oh, this isn’t financial advice. Oh, this is all just for whatever. But, but you’re trying to do that and then you go one step beyond, which I think is actually pretty dumb, which is to be like, okay, well, ’cause like, here’s the thing, I’m not gonna judge anyone. If someone who’s like, Hey, here’s a wallet that we’re gonna give you, and it has real cash in it, and you can do whatever you want with it, and these are the transaction fees, so to speak, like, you know, the gas fees, whatever, you know what you do. You, even if you wanna let your audience know that you’ve done that, and maybe you’re promoting that, maybe some people will buy into it, like, people are adults. Fine. Where, where I do like side eye a little bit is if you are, then for whatever reason [00:34:00] going to be like, oh, I’m gonna take my fees and I’m gonna reinvest it in the coin. Like, okay, you are literally sitting on top of the pyramid, like you could not be in a better position and now you’re, but right. And now you’re literally like paying into the pyramid scheme. It’s like, this is not going to work well for you. These are rug bulls. Um, and so like the, the, the, the gas town coin like dropped like massively. The Ralph coin like dropped massively, like after the, the, the Ralph creator, I think he took out like 300 K or something and people, or, you know, sold like 300 K worth of coins. And people were like, oh, he’s pulling a rug pull. And I’m like, well, A, what did you expect? But B it’s like, this is why don’t, like, if someone’s gonna give you free money from something that’s, you know, kind of scammy, like, I’m not saying don’t take the money. I am saying maybe be smart enough to not to reinvest it into the scam. Brett: Yeah. Christina: Like, I don’t know. Anyway, that’s the only thing I will mention on that. ’cause I don’t think that that takes [00:35:00] anything away from either of those projects or it says that you shouldn’t use or play around with it either of those ideas at all. But that is just a thing that’s happened in the last couple of weeks too, where it’s like, oh, and now there’s like crypto, you know, the crypto people are trying to get kind of involved with these projects and, um, I, I think that that’s, uh, okay. You know, um, like I said, I’m, I’m not gonna judge anybody for taking free money that, that somebody is gonna offer them. I will judge you if you’re gonna try to then, you know, try to like, promote that to your audience and try to be like, oh, this is a great way where we, where you can help me and we can all get rich. It’s like, no, there are, if you really wanna support creators, like there are things like GitHub sponsors and there are like other methods that you can, you can do that, that don’t involve making financial risks on shit coins. Brett: I wish anything I made could be popular enough that I could do something that’s stupid. Yeah. Like [00:36:00] I, I, I, I’m not gonna pull a rug pull on anyone, but the chances that I’ll ever make $300,000 on anything I’m working on, it’s pretty slim. Christina: Yeah, but at the same time, like if you, if you did, if you were in that position, like, I don’t know, I mean, I guess that’d be a thing that you would have to kind of figure out, um, yourself would be like, okay, I have access to this amount of money. Am I going to try to, you know, go all in and, and maybe go full grift to get even more? Some, something tells me that like your own personal ethics would probably preclude you from that. Brett: I, um, I have spent, what, um, how old am I? 47. I, I’ve been, since I started blogging in like 1999, 2000, um, I have always adhered to a very strict code and like turning down sponsors. I didn’t agree with [00:37:00] not doing anything that would be shady. Not taking, not, not taking money from anyone I was writing about. Ethics in Journalism and Personal Dilemmas Brett: Like, it’s been, it’s a pain in the ass to try to be truly ethical, but I feel like I’ve done it for 30 some years and, and I don’t know, I wouldn’t change it. I’m not rich. I’ll never be rich. But yeah, I think ethics are important, especially if you’re in any kind of journalism. Christina: Yeah, if you’re in any sort of journalism. I think so, and I think like how people wanna define those things, I think it’s up to them. And, and like I said, like I’m not gonna even necessarily like, like judge people like for, because I, I don’t know personally like what my situation would be like. Like if somebody was like, Christina, here’s a wallet that has the equivalent of $300,000 in it and it’s just sitting here and we’re not even asking you to do anything with this. I would probably take the money. I’m not gonna lie, I don’t, I don’t, I don’t [00:38:00] know if I would promote it or anything and I maybe I would feel compelled to disclose, Hey, Brett: That is Christina: wallet belongs to me. Brett: money though. Christina: I, I, right. I, I, I might, I might be, I might feel compelled to com to, to disclose, Hey, someone created this coin in this thing. They created the foam grow coin and they are giving me, you know, the, the, the gas fees and I have accepted Brett: could be, I’d feel like you could do it if you were transparent enough about it. Christina: Yeah, I mean, I, I, I think where I draw the line is when you then go from like, because again, it’s fine if you wanna take it. It’s then when you are a. Reinvesting the free money into the coin, which I think is just idiotic. Like, I think that’s just actually dumb. Um, like I just, I just do like, that just seems like you are literally, like I said, you’re at the top of the pyramid and you’re literally like volunteering to get into the bottom again. Um, and, or, or b like if you do that and then you try to rationalize in some way, oh, well, you know, I think [00:39:00] that this could be a great thing for everybody to, you know, I get rich, you know, you could get rich, we could all get money out of this because this is the future of, you know, creator economy or whatever. It’s like, no, it’s not. This is gambling. Um, and, and, and, and you could make the argument to me, and I’d probably be persuaded to be like, this isn’t that different from poly market or any of the other sorts of things. But you know what? I don’t do those things either. And I wouldn’t promote those things to any audience that I had either. Um, but if somebody wanted to give me free money. I probably wouldn’t turn it down. I’m not gonna pretend that my ethics are, are that strong. Uh, I just don’t know if I would, if I would, uh, go on the other end and be like, okay, to the Moom, everyone let, let’s all go in on the crypto stuff. It’s like, okay, The Future of Open Source and Cryptocurrency Brett: So is this the future of open source is, ’cause I mean like open source has survived for decades as like a concept and it’s never been terribly profitable. But a [00:40:00] lot of large companies have invested in open source, and I guess at this point, like most of the big open source projects are either run by a corporation or by a foundation. Um, that are independently financed, but for a project like Gastown, like is it the future? Is this, is this something people are gonna start doing to like, kind of make open source profitable? Christina: I mean, maybe, I don’t know. I think the problem though is that it’s not necessarily predictable, right? And, and not to say that like normal donations or, or support methods are predictable, but at least that could be a thing where you’re like, they’re not, but, but, but it’s not volatile to the extent where you’re like, okay, I’m basing, you know, like my income based on how well this shit coin that someone else controls the supply of someone else, you know, uh, uh, created someone else, you know, burned, so to speak, somebody else’s is going to be, uh, [00:41:00] controlling and, and has other things and could be responsible for, you know, big seismic like market movements like that I think is very different, um, than anything else. And so, I don’t know. I mean, I, I think that they, what I do expect that we’ll see more of is more and more popular projects, things that go viral, especially around ai. Probably being approached or people like proactively creating coins around those things. And there have been some, um, developers who’ve already, you know, stood up oddly and been like, if you see anybody trying to create a coin around this, it is not associated with me. I won’t be associated with any of it. I won’t do it. Right. Uh, and I think that becomes a problem where you’re like, okay, if these things do become popular, then that becomes like another risk if you don’t wanna be involved in it. If you’re involved with a, with a popular project, right? Like the, like the, like the creator of MPM Isaac, like, I think there’s like an MPM coin now, and that, that he’s, you know, like involved in and it’s like, you know, again, he didn’t create it, but he is happy to promote it. He’s happy to take the money. I’m like, look, I’m happy for [00:42:00] Isaac to get money from NPMI am at the same time, you know, bun, which is basically like, you know, the, you know, replacement for, for Node and NPM in a lot of ways, they sold to Anthropic for. I guarantee you a fuck load more money than whatever Isaac is gonna make off of some MPM shitcoin. So, so like, it, it’s all a lottery and it’s not sustainable. But I also feel like for a lot of open source projects, and this isn’t like me saying that the people shouldn’t get paid for the work, quite the contrary. But I think if you go into it with the expectation of I’m going to be able to make a sustainable living off of something, like when you start a project, I think that that is not necessarily going to set you up for, I think that those expectations are misaligned with what reality might be, which again, isn’t to say that you shouldn’t get paid for your work, it’s just that the reason that we give back and the reason we contribute open source is to try to be part of like the, the greater good and to make things more available to everyone. Not to be [00:43:00] like, oh, I can, you know, quit my job. Like, that would be wonderful. I, I wish that more and more people could do that. And I give to a lot of, um, open source projects on, on a monthly basis or on an annual basis. Um, Brett: I, I give basically all the money that’s given to me for my open source projects I distribute among other open source projects. So it’s a, it’s a, it’s a wash for me, but yeah, I am, I, I pay, you know, five, 10 bucks a month to 20 different projects and yeah. Christina: Yeah. I mean, I think it’s important, but, but I, I don’t know. I, I, I hope that it’s not the future. I’m not mad, I think like if that’s a way where people can make, you know, a, a, an income. But I do, I guess worry the sense that like, if, if, if, I don’t want that to be, the reason why somebody would start an open source project is because they’re like, oh, I, I can get rich on a crypto thing. Right? Like, ’cause that that’s the exact wrong Brett: that’s not open source. That’s not the open source philosophy. Christina: no, [00:44:00] it’s not. And, and so, I mean, but I think, I think if it already exists, I mean, I don’t know. I, I also feel like no one should feel obligated. This should go without saying that. If you see a project that you like that is involved in one of those coins. Do you have a zero obligation to be, uh, supportive of that in any way? And in fact, it is probably in your financial best interest to not be involved. Um, it, it is your life, your money, your, you do whatever you want, gamble, however you want. But, uh, I, I, I, I do, I guess I, I bristle a little bit. Like if people try to portray it like, oh, well this is how you can support me by like buying into this thing. I’m like, okay, that’s alright. Like, I, I, if you wanna, again, like I said, if you wanna play poly market with this, fine, but don’t, don’t try to wrap that around like, oh, well this is how you can give back. It’s like, no, you can give back in other ways. Like you can do direct donations, you can do other stuff. Like I would, I would much rather encourage people to be like, rather than putting a hundred dollars in Ralph Coin, [00:45:00] give a hundred dollars to the Ralph Guy directly. Apex 1.0? Brett: So, speaking of unprofitable open source, I have Apex almost to 1.0. Um, it officially handles, I think, all of the syntax that I had hoped it would handle. Um, it does like crazy things, uh, that it’s all built on common mark, GFM, uh, like cmar, GFM, GitHub’s project. Um, so it, it does all of that. Plus it handles stuff from like M mark with like indices. Indices, and it incorporates, uh. Uh, oh, I forget the name of it. Like two different ways of creating indices. It handles all kinds of bibliography syntax, like every known bibliography syntax. Um, I just added, you can, you can create insert tags with plus, plus, uh, the same way you would create a deletion with, uh, til detail. Um, and [00:46:00] I’ve added a full plugin structure, and the plugins now can be project local. So you can have global plugins. And then if you have specific settings, so like I have a, I, my blogs are all based on cramdown and like the bunch documentation is based on cramdown, but then like the mark documentation. And most of my writing is based on multi markdown and they have different. Like the, for example, the IDs that go on headers in multi markdown. If it’s, if it has a space in multi markdown, it gets compressed to no space in common Mark or GFM, it gets a dash instead of a space, which means if I have cross links, cross references in my document, if I don’t have the right header syntax, the cross reference will break. So now I can put a, a config into like my bunch documentation that tells Apex to use, [00:47:00] um, the dash syntax. And in my Mark documentation, I can tell it to use the multi markdown syntax. And then I can just run Apex with no command line arguments and everything works. And I don’t know, I, I haven’t gotten adoption for it. Like the one place I thought it could be really useful was DEVONthink, Christina: Mm-hmm. Brett: which has always been based on multi markdown, which. Um, is I love multi markdown and I love Fletcher and, um, it’s just, it’s missing a lot of what I would consider modern syntax. Christina: Right. Brett: so I, I offered it to Devin think, and it turned out they were working on their own project along the same lines at the same time. Um, but I’m hoping to find some, some apps that will incorporate it and maybe get it some traction. It’s solid, it’s fast, it’s not as fast as common Mark, but it does twice as much. Um, like the [00:48:00] benchmarks, it a complex document renders in common mark in about. Uh, 27 milliseconds, and in Apex it’s more like 46 milliseconds. But in the grand scheme of things, I could render my whole blog 10 times faster than I can with cramm down or Panoc and yeah, and, and I can use all the syntax I want. Challenges and Innovations in Markdown Processing Brett: Did I tell you about, did I tell you about, uh, Panoc Divs? The div extension, um, like you can in with the panoc D extension, you can put colon, colon, colon instead of like back, take, back, take backtick. So normally, like back ticks would create a code block with colons, it creates a div, and you can apply, you can apply inline attribute lists after the colons to make, to give it a class and an ID and any other attributes you wanna apply to it. I extended that so that you can do colon, [00:49:00] colon, colon, and then type a tag name. So if you type colon, colon, colon aside and then applied an attribute list to it, it would create an aside tag with those attributes. Um, the, the only pan deck extension that I wish I could support that I don’t yet is grid tables. Have you ever seen grid tables? Christina: I have not. Brett: There, it’s, it’s kind of like multi markdown table syntax, except you use like plus signs for joints and uh, pipes and dashes, and you actually draw out the table like old ASCI diagrams Christina: Okay. Brett: and that would render that into a valid HTML table. But that supporting that has just been, uh, tables. Tables are the thing. I’ve pulled the most hair out over. Christina: Yeah, I was gonna say, I think I, they feel like tables are hard. I also feel like in a lot of circumstances, I mean obviously people use tables and whatnot, but like, [00:50:00] only thing I would say to you, like, you know, apex is, is so cool and I hope that other projects adopt it. Um, and, uh, potentially with the POC support as far as you’ve gotten with it, maybe, you know, projects that support some of POC stuff could, could, you know, uh, jump into it. But I will say it does feel like. Once you go into like the Panoc universe, like that almost feels like a separate thing from the markdown Flavors like that almost feels like its own like ecosystem. You know what I mean? Brett: Well, yeah, and I haven’t tried to adopt everything Panoc does because you can als, you can also use panoc. You can pipe from Apex into Panoc or vice versa. So I’m not gonna try to like one for one replicate panoc, Christina: No, no. Totally Brett: do all of panoc export options because Panoc can take HTML in and then output PDFs and Doc X and everything. So you can just pipe output from Apex into Panoc to create your PDF or whatever Christina: And like, and, and like to, [00:51:00] and like to me, like that seems ideal, right? But I feel like maybe like adopting some of the other things, especially like, like their grid, you know, table, things like that. Like that would be cool. But like, that feels like that’s a, potentially has the, has the potential, maybe slow down rendering and do other stuff which you don’t want. And then b it’s like, okay, now are we complicated to the point that like, this is, this is now not becoming like one markdown processor to rule them all, but you Brett: Yeah, the whole point, the whole point is to be able to just run Apex and not worry about what cex you’re using. Um, but grid tables are the kind of thing that are so intentional that you’re not gonna accidentally use them. Like the, the, the, the impetus for Apex was all these support requests I get from people that are like the tilde syntax for underline or delete doesn’t work in Mark. And it, it does if you choose the right processor. But then you have to know, yeah, you have to [00:52:00] know what processor supports what syntax and that takes research and time and bringing stuff in from, say, obsidian into mart. You would just kind of expect things to work. And that’s, that’s why I built Apex and Christina: right? Brett: you are correct that grid tables are the kind of thing, no one’s going to use grid tables if they haven’t specifically researched what Christina: I right. Brett: they’re gonna work with. Christina: And they’re going to have a way that has their file marked so that it is designated as poc and then whatever, you know, flags for whatever POC features it supports, um, does. Now I know that the whole point of APEX is you don’t have to worry about this, but, but I am assuming, based on kind of what you said, like if I pass like arguments like in like a, you know, in a config file or something like where I was like, these documents or, or, or this URL or these things are, you know, in this process or in this in another, then it can, it can just automatically apply those rules without having to infer based on the, on the syntax, right. Brett: right. It has [00:53:00] modes for cram down and common mark and GFM and discount, and you can like tell it what mode you’re writing in and it will limit the feature set to just what that processor would handle. Um, and then all of the flags, all of the features have neg negotiable flags on them. So if you wanted to say. Skip, uh, relax table rendering. You could turn that off on the command line or in a config file. Um, so yeah, everything, everything, you can make it behave like any particular processor. Uh, but I focus mostly on the unified mode, which again, like you don’t have to think about which processor you are using. Christina: Are you seeing, I guess like in, in circumstances like, ’cause I, in, in my, like, my experience, like, I would never think to, like, I would probably like, like to, I would probably do like what you do, which is like, I’m [00:54:00] going to use one syntax or, or one, you know, processor for one type of files and maybe another and another. Um, but I, I don’t think that like, I would ever have a, and maybe I’m misunderstanding this, but I don’t think I would ever have an instance where I would be like mixing the two together in the same file. Brett: See, that’s my, so that’s, that’s what’s changing for me is I’m switching my blog over to use Apex instead of Cramdown, which means I can now incorporate syntax that wasn’t available before. So moving forward, I am mixing, um, things from common mark, things from cram down, things from multi markdown. Um, and, and like, so once you know you have the option Christina: right. Then you might do that Brett: you have all the syntax available, you start doing it. And historically you won’t have, but like once you get used to it, then you can. Christina: Okay. So here’s the next existential question for you. At what point then does it go from being, you know, like [00:55:00] a, a, a rendering engine, kind of like an omni rendering engine to being a syntax and a flavor in and of itself? Brett: That is that, yeah, no, that’s a, that’s a very valid question and one that I have to keep asking myself, um, because I never, okay, so what to, to encapsulate what you’re saying, if you got used to writing for Apex and you were mixing your syntax, all of a sudden you have a document that can’t render in anything except Apex, which does eventually make it its own. Yeah, no, it is, it’s always, it’s a concern the whole time. Christina: well, and I, I wouldn’t even necessarily, I mean, like, and I think it could be two things, right? I mean, like, you could have it live in two worlds where, like on the one hand it could be like the rendering engine to end all rendering engines and it can render, you know, files and any of them, and you can specify like whatever, like in, in, in like a tunnel or something. Like, you know, these files are, [00:56:00] are this format, these are these, and you know, maybe have some sort of, you know, um, something, even like a header files or whatever to be like, this is what this rendering engine is. Um, you know, with, with your projects to have it, uh, do that. Um. Or have it infer, you know, based on, on, on, um, the, the logic that you’re importing. But it could also be one of those things where you’re like, okay, I just have created like, you know, the omni syntax. And that’s a thing that maybe, maybe you get people to try to encourage or try, try to adopt, right? Like, it’s like, okay, you can always just use common mark. You can always just use GFM, you can always just use multi markdown, but we support these other things too, from these other, um, systems and you can intermix and match them. Um, because, because I, I do feel like at a certain point, like at least the way you’re running it yourself, you have your own syntax. Like, like, you know. Brett: yeah. No, you have perfectly encapsulated the, the major [00:57:00] design concern. And I think you’re correct. It can exist, it can be both things at once. Um, but I have like, nobody needs another markdown syntax. Like there are so many flavors right now. Okay. There may be a dozen. It’s not like an infinite number, but, but there’s enough that the confusion is real. Um, and we don’t need yet another markdown flavor, but we do need a universal processor that. Makes the differentiations less, but yeah, no, it’s, I need, I need to nail down that philosophy, uh, and really like, put it into writing and say, this is the design goal of this project, uh, which I have like hinted at, but I’m a scattered thinker and like, part of, part of the design philosophy is if someone says, Hey, [00:58:00] could you make this work? I just wanted a project where I could say, yeah, I’m gonna make that work. I, I, I’m gonna add this somewhat esoteric syntax and it’s just gonna work and it’s not gonna affect anything else. And you don’t have to use it, but if you do, there it is. So it’s kind of, it was designed to bloat to a circuit certain extent. Um, but yeah, I need to, I need to actually write a page That’s just the philosophy and really, really, uh, put, put all my thoughts together on that. Christina: Yeah, no, ’cause I was just kind of thinking, I was like, ’cause it’s so cool. Um, but the way that I would’ve envisioned using it, like I, I still like, it’s cool that you can mix all those things in together. I still feel like I probably wouldn’t because I’m not you. And so then I would just have like this additional dependency that it’s like, okay, if something happens to Apex one day and that’s the only thing that can render my documents, then like, you know what I mean? And, and, and if it’s not getting updated [00:59:00] anymore or whatever, then I’m kind of like SOL, um, Brett: Maku. Do you remember Maku? Christina: vaguely. Brett: It’s, the project is kind of dead and a lot of its syntax has been incorporated into various other processors. But if you built your whole blog on Maku, you have to, you have to be able to run like a 7-year-old binary, um, and, and it’ll never be updated, and eventually you’re gonna run into trouble. The nice thing about Unix based stuff is it’s. Has a, you can stop developing it and it’ll work for a decade, um, until, like, there’s a major shift in processors, but like, just the shift to arm. Like if, if Maku was only ever compiled for, uh, for, uh, Intel and it wasn’t open source, you would, it would be gone. You wouldn’t be able to run it anymore. So yeah, these things can happen. Christina: [01:00:00] Well, and I just even think about like, you know, the fact that like, you know, like some of the early processors, like I remember like back, I mean this is a million years ago, but having to use like certain, like pearl, you know, based things, you know, but depending on like whatever your backend system was, then you moved to PHP, they maybe you move, moved to, you know, Ruby, if you’re using like Jekyll and maybe you move to something else. And I was like, okay, you know, what will the thing be in the future? Yeah. If, if I, if it’s open source and there’s a way that, you know, you can write a new, a new processor for that, but it does create like, dependencies on top of dependencies, which is why I, I kind of feel like I like having like the omni processor. I don’t know if, like, for me, I’m like, okay, I, I would probably be personally leery about intermingling all my different syntaxes together. Brett: to that end though, that is why I wanted it in C um, because C will probably never die. C can be compiled on just about any platform. And it can be used with, like, if you have, if you have a Jekyll blog and you wanna [01:01:00] incorporate a C program into a gem, it’s no problem. Uh, you can incorporate it into just about any. Langu

This week's episode is packed with Expo-heavy updates, early looks at AI agent tooling, and some honest numbers and lessons from Tiny Harvest. We also zoom out and talk about the idea that we might be living through an Industrial Revolution of Software.⚛️ React Native Radar

In episode 499 James and Frank dive into the messy, exciting world of coding agents — from burning through Copilot credits and avoiding merge conflicts to practical workflows for letting agents run tasks while you sleep. They share real tips: break big features into bite-sized tasks, have agents ask clarifying questions, and use Copilot CLI or the new SDK to resolve conflicts, auto-fix lint/build failures, and automate mundane repo work. The conversation then maps the evolution from simple completions to autonomous loops like Ralph — a structured, repeatable process that generates subtasks, runs until acceptance tests pass, and updates your workflow. If you're curious how agents, MCPs and SDKs can elevate your dev flow or spark new automations, this episode gives pragmatic examples, trade-offs, and inspiration to start experimenting today. Follow Us Frank: Twitter, Blog, GitHub James: Twitter, Blog, GitHub Merge Conflict: Twitter, Facebook, Website, Chat on Discord Music : Amethyst Seer - Citrine by Adventureface ⭐⭐ Review Us ⭐⭐ Machine transcription available on http://mergeconflict.fm

Episode 23 - Agree Ahmed, CEO Flowglad Anablock Podcast—this podcast is brought to you by Anablock In Episode 23 of the Anablock Podcast, CEO Agree Ahmed discusses Flowglad, an open-source payment provider that simplifies integration for developers with a focus on real-time sync and compliance challenges, while leveraging insights from emerging markets to inform their strategy. The company prioritizes developer needs and startups, avoiding enterprise-first approaches, and is based in New York to tap into diverse fintech talent. Interview Topics: 1. Flowglad Overview: Open-source payment provider simplifying integration and maintenance with state management and feature entitlements. 2. Developer Integration: Requires only customer ID for setup, supporting React, Next.js, and common authentication platforms like Clerk. 3. Product Philosophy: Focus on developers and startups, leveraging open-source for market traction, avoiding enterprise-first strategies. 4. Roadmap Focus: Building real-time sync, ORM-like SDK, and CI/CD tools within 4-6 weeks to enhance reliability for developers. 5. Geographic Advantage: Experience in emerging markets like Kenya informs strategy; New York chosen for its diverse talent in fintech. 6. Compliance Challenges: Layered billing handles software features, while payments navigate complex tax and regulatory requirements.   Learn More About the Guest Agree Ahmed, LinkedIn - https://www.linkedin.com/in/agreea/ Flowglad Company - https://www.flowglad.com/   About Anablock Anablock offers innovative AI-powered solutions designed to streamline business operations and enhance customer engagement. Our key services include: AI Agents for Workflow Automation: Simplify and automate repetitive tasks to improve efficiency and reduce operational costs. AI Chatbot Solutions: Enhance customer support with intelligent chatbots that provide instant responses and 24/7 assistance. Digital Marketing: Leverage data-driven strategies to boost online presence and drive targeted traffic to your business. Software Development: Custom software solutions tailored to meet specific business needs and improve overall performance. System Integration: Seamlessly connect various systems and applications to ensure smooth data flow and enhance productivity. SCHEDULE DEMO - https://www.anablock.com/schedule-demo/ With Anablock, businesses can harness the power of AI to optimize processes, engage customers effectively, and drive growth.

In our latest episode, co-hosts Robby and Tim talk with Robert Brennan, Co-Founder & CEO of OpenHands - the open platform for cloud coding agents. Their open source project, also called OpenHands, has 67K starts on GitHub and provides a software agent SDK, CLI, and local GUI. They also have OpenHands cloud - their paid, hosted version of the OpenHands GUI. This episode traces the rise of OpenDevin - now OpenHands - as an open-source alternative to closed AI coding agents like Devin. Open to anyone from day one, it attracted highly technical developers, academics, and eventually large enterprises that valued flexibility, privacy, and lack of model lock-in. Launched amid the 2024 surge of excitement around autonomous coding agents, OpenHands quickly built a massive community and differentiated itself by rejecting the idea of replacing engineers, instead focusing on empowering them through transparent, human-in-the-loop tooling.The discussion also covers the fragmented AI dev-tool landscape and why open source may define future standards. While many tools compete in the individual “inner loop” of coding, OpenHands emphasizes the collaborative “outer loop,” safety, and running agents at scale. Its organic growth, community-driven roadmap, and focus on real developer pain points highlight a future where AI accelerates software creation without removing human accountability.

Join Simtheory: https://simtheory.ai---Join the most average AI LinkedIn group: https://www.linkedin.com/groups/16562039/It's 2026 and everyone's having an existential crisis. In this episode, we unpack the two camps dominating AI C/Twitter: hype boys claiming "Claude Code can do my washing" vs. software developers doom-scrolling themselves into career panic. We put the agentic hype to the test and discover that no, you can't actually run 8 agents recreating your local business ecosystem while you sleep. Plus, we reflect on why MCP is exhausting, why Gemini 3 Pro is somehow worse than Gemini 2.5 Pro, and why Geoffrey Hinton would rather write his book than answer questions in Tasmania. Also featuring: the $200,000/month enterprise AI problem, why SaaS isn't dead (but it's scared), and our prediction that AI workspaces will become the everything app.CHAPTERS:00:00 Intro - Unpacking the 2026 AI Vibes02:21 Putting Claude Code and Agentic Hype to the Test05:57 Why Twitter AI Demos Never Show the Receipts07:03 Honest Assessment of Where Frontier Models Are At11:19 Building the Everything App with Email, Calendar and Files16:47 Collaborative Mode vs Agentic Delegation in Practice21:29 The Real Cost of Enterprise AI at Scale24:32 Why Cheaper Models Like Haiku and Gemini Flash Matter29:25 Is SaaS Actually Dead or Just Disrupted38:11 The Future of AI Platforms, SDKs and App Stores43:35 The Untapped Opportunity in Paid Proprietary MCPs51:21 Geoffrey Hinton Refuses to Take Questions in Tasmania55:05 2026 Plans and the Still Relevant Tour AnnouncementThanks for listening. Like & Sub. xoxox

Подкаст RadioDotNet выпуск №129 от 19 января 2026 года В этом эпизоде вы можете услышать историю про источники уникальных данных от международного разработчика ПО Altenar. Сайт подкаста: radio.dotnet.ru Boosty (₽): boosty.to/RadioDotNet Темы: [00:02:20] — SharpIDE — Cross-Platform IDE with Godot! github.com/MattParkerDev/SharpIDE [00:09:20] — Changing Immutable Collections codeblog.jonskeet.uk/changing-immutable-collections [00:21:50] — Creating a custom MSBuild SDK to reduce boilerplate in .NET projects meziantou.net/creating-a-custom-msbuild-sdk-to-reduc... [00:48:35] — How We Synchronize .NET's Virtual Monorepo devblogs.microsoft.com/dotnet/how-we-synchronize-dotnets-virt... [01:19:05] — Кратко о разном habr.com/ru/articles/982300 dev.to/nikolaos_protopapas_d3bd6/the-0-locali... youtube.com/playlist Фоновая музыка: Максим Аршинов «Pensive yeti.0.1»

Ian and Aaron are joined by Taylor Otwell for their first ever in-person episode of Mostly Technical to talk about everything from the Laravel AI SDK to Private Cloud to vibe coding MUD's and so much more.Sponsored by SavvyCal Appointments, Bento, Mastering Laravel, and Laravel Private Cloud.Interested in sponsoring Mostly Technical?  Head to https://mostlytechnical.com/sponsor to learn more.(00:00) - Imaginary Tech Stuff Is Real (04:01) - Taylor's Journey With AI (12:18) - Laravel AI SDK (24:48) - Coding In The AI Era (32:51) - Laravel Private Cloud (37:06) - Cloud CLI (38:48) - First Year of Cloud (43:05) - Sprites.dev (46:30) - What's Next (50:02) - Post Credit Scene Links:Multi-user DungeonLaravel SimplifierElevenlabsPrismWelcome to Gas TownSprites.dev

De retour à cinq dans l'épisode, les cast codeurs démarrent cette année avec un gros épisode pleins de news et d'articles de fond. IA bien sûr, son impact sur les pratiques, Mockito qui tourne un page, du CSS (et oui), sur le (non) mapping d'APIs REST en MCP et d'une palanquée d'outils pour vous. Enregistré le 9 janvier 2026 Téléchargement de l'épisode LesCastCodeurs-Episode-335.mp3 ou en vidéo sur YouTube. News Langages 2026 sera-t'elle l'année de Java dans le terminal ? (j'ai ouïe dire que ça se pourrait bien…) https://xam.dk/blog/lets-make-2026-the-year-of-java-in-the-terminal/ 2026: Année de Java dans le terminal, pour rattraper son retard sur Python, Rust, Go et Node.js. Java est sous-estimé pour les applications CLI et les TUIs (interfaces utilisateur terminales) malgré ses capacités. Les anciennes excuses (démarrage lent, outillage lourd, verbosité, distribution complexe) sont obsolètes grâce aux avancées récentes : GraalVM Native Image pour un démarrage en millisecondes. JBang pour l'exécution simplifiée de scripts Java (fichiers uniques, dépendances) et de JARs. JReleaser pour l'automatisation de la distribution multi-plateforme (Homebrew, SDKMAN, Docker, images natives). Project Loom pour la concurrence facile avec les threads virtuels. PicoCLI pour la gestion des arguments. Le potentiel va au-delà des scripts : création de TUIs complètes et esthétiques (ex: dashboards, gestionnaires de fichiers, assistants IA). Excuses caduques : démarrage rapide (GraalVM), légèreté (JBang), distribution simple (JReleaser), concurrence (Loom). Potentiel : créer des applications TUI riches et esthétiques. Sortie de Ruby 4.0.0 https://www.ruby-lang.org/en/news/2025/12/25/ruby-4-0-0-released/ Ruby Box (expérimental) : Une nouvelle fonctionnalité permettant d'isoler les définitions (classes, modules, monkey patches) dans des boîtes séparées pour éviter les conflits globaux. ZJIT : Un nouveau compilateur JIT de nouvelle génération développé en Rust, visant à surpasser YJIT à terme (actuellement en phase expérimentale). Améliorations de Ractor : Introduction de Ractor::Port pour une meilleure communication entre Ractors et optimisation des structures internes pour réduire les contentions de verrou global. Changements syntaxiques : Les opérateurs logiques (||, &&, and, or) en début de ligne permettent désormais de continuer la ligne précédente, facilitant le style "fluent". Classes Core : Set et Pathname deviennent des classes intégrées (Core) au lieu d'être dans la bibliothèque standard. Diagnostics améliorés : Les erreurs d'arguments (ArgumentError) affichent désormais des extraits de code pour l'appelant ET la définition de la méthode. Performances : Optimisation de Class#new, accès plus rapide aux variables d'instance et améliorations significatives du ramasse-miettes (GC). Nettoyage : Suppression de comportements obsolètes (comme la création de processus via IO.open avec |) et mise à jour vers Unicode 17.0. Librairies Introduction pour créer une appli multi-tenant avec Quarkus et http://nip.io|nip.io https://www.the-main-thread.com/p/quarkus-multi-tenant-api-nipio-tutorial Construction d'une API REST multi-tenant en Quarkus avec isolation par sous-domaine Utilisation de http://nip.io|nip.io pour la résolution DNS automatique sans configuration locale Extraction du tenant depuis l'en-tête HTTP Host via un filtre JAX-RS Contexte tenant géré avec CDI en scope Request pour l'isolation des données Service applicatif gérant des données spécifiques par tenant avec Map concurrent Interface web HTML/JS pour visualiser et ajouter des données par tenant Configuration CORS nécessaire pour le développement local Pattern acme.127-0-0-1.nip.io résolu automatiquement vers localhost Code complet disponible sur GitHub avec exemples curl et tests navigateur Base idéale pour prototypage SaaS, tests multi-tenants Hibernate 7.2 avec quelques améliorations intéressantes https://docs.hibernate.org/orm/7.2/whats-new/%7Bhtml-meta-canonical-link%7D read only replica (experimental), crée deux session factories et swap au niveau jdbc si le driver le supporte et custom sinon. On ouvre une session en read only child statelesssession (partage le contexte transactionnel) hibernate vector module ajouter binary, float16 and sparse vectors Le SchemaManager peut resynchroniser les séquences par rapport aux données des tables Regexp dans HQL avec like Nouvelle version de Hibernate with Panache pour Quarkus https://quarkus.io/blog/hibernate-panache-next/ Nouvelle extension expérimentale qui unifie Hibernate ORM with Panache et Hibernate Reactive with Panache Les entités peuvent désormais fonctionner en mode bloquant ou réactif sans changer de type de base Support des sessions sans état (StatelessSession) en plus des entités gérées traditionnelles Intégration de Jakarta Data pour des requêtes type-safe vérifiées à la compilation Les opérations sont définies dans des repositories imbriqués plutôt que des méthodes statiques Possibilité de définir plusieurs repositories pour différents modes d'opération sur une même entité Accès aux différents modes (bloquant/réactif, géré/sans état) via des méthodes de supertype Support des annotations @Find et @HQL pour générer des requêtes type-safe Accès au repository via injection ou via le métamodèle généré Extension disponible dans la branche main, feedback demandé sur Zulip ou GitHub Spring Shell 4.0.0 GA publié - https://spring.io/blog/2025/12/30/spring-shell-4-0-0-ga-released Sortie de la version finale de Spring Shell 4.0.0 disponible sur Maven Central Compatible avec les dernières versions de Spring Framework et Spring Boot Modèle de commandes revu pour simplifier la création d'applications CLI interactives Intégration de jSpecify pour améliorer la sécurité contre les NullPointerException Architecture plus modulaire permettant meilleure personnalisation et extension Documentation et exemples entièrement mis à jour pour faciliter la prise en main Guide de migration vers la v4 disponible sur le wiki du projet Corrections de bugs pour améliorer la stabilité et la fiabilité Permet de créer des applications Java autonomes exécutables avec java -jar ou GraalVM native Approche opinionnée du développement CLI tout en restant flexible pour les besoins spécifiques Une nouvelle version de la librairie qui implémenter des gatherers supplémentaires à ceux du JDK https://github.com/tginsberg/gatherers4j/releases/tag/v0.13.0 gatherers4j v0.13.0. Nouveaux gatherers : uniquelyOccurringBy(), moving/runningMedian(), moving/runningMax/Min(). Changement : les gatherers "moving" incluent désormais par défaut les valeurs partielles (utiliser excludePartialValues() pour désactiver). LangChain4j 1.10.0 https://github.com/langchain4j/langchain4j/releases/tag/1.10.0 Introduction d'un catalogue de modèles pour Anthropic, Gemini, OpenAI et Mistral. Ajout de capacités d'observabilité et de monitoring pour les agents. Support des sorties structurées, des outils avancés et de l'analyse de PDF via URL pour Anthropic. Support des services de transcription pour OpenAI. Possibilité de passer des paramètres de configuration de chat en argument des méthodes. Nouveau garde-fou de modération pour les messages entrants. Support du contenu de raisonnement pour les modèles. Introduction de la recherche hybride. Améliorations du client MCP. Départ du lead de mockito après 10 ans https://github.com/mockito/mockito/issues/3777 Tim van der Lippe, mainteneur majeur de Mockito, annonce son départ pour mars 2026, marquant une décennie de contribution au projet. L'une des raisons principales est l'épuisement lié aux changements récents dans la JVM (JVM 22+) concernant les agents, imposant des contraintes techniques lourdes sans alternative simple proposée par les mainteneurs du JDK. Il pointe du doigt le manque de soutien et la pression exercée sur les bénévoles de l'open source lors de ces transitions technologiques majeures. La complexité croissante pour supporter Kotlin, qui utilise la JVM de manière spécifique, rend la base de code de Mockito plus difficile à maintenir et moins agréable à faire évoluer selon lui. Il exprime une perte de plaisir et préfère désormais consacrer son temps libre à d'autres projets comme Servo, un moteur web écrit en Rust. Une période de transition est prévue jusqu'en mars pour assurer la passation de la maintenance à de nouveaux contributeurs. Infrastructure Le premier intérêt de Kubernetes n'est pas le scaling - https://mcorbin.fr/posts/2025-12-29-kubernetes-scale/ Avant Kubernetes, gérer des applications en production nécessitait de multiples outils complexes (Ansible, Puppet, Chef) avec beaucoup de configuration manuelle Le load balancing se faisait avec HAProxy et Keepalived en actif/passif, nécessitant des mises à jour manuelles de configuration à chaque changement d'instance Le service discovery et les rollouts étaient orchestrés manuellement, instance par instance, sans automatisation de la réconciliation Chaque stack (Java, Python, Ruby) avait sa propre méthode de déploiement, sans standardisation (rpm, deb, tar.gz, jar) La gestion des ressources était manuelle avec souvent une application par machine, créant du gaspillage et complexifiant la maintenance Kubernetes standardise tout en quelques ressources YAML (Deployment, Service, Ingress, ConfigMap, Secret) avec un format déclaratif simple Toutes les fonctionnalités critiques sont intégrées : service discovery, load balancing, scaling, stockage, firewalling, logging, tolérance aux pannes La complexité des centaines de scripts shell et playbooks Ansible maintenus avant était supérieure à celle de Kubernetes Kubernetes devient pertinent dès qu'on commence à reconstruire manuellement ces fonctionnalités, ce qui arrive très rapidement La technologie est flexible et peut gérer aussi bien des applications modernes que des monolithes legacy avec des contraintes spécifiques Mole https://github.com/tw93/Mole Un outil en ligne de commande (CLI) tout-en-un pour nettoyer et optimiser macOS. Combine les fonctionnalités de logiciels populaires comme CleanMyMac, AppCleaner, DaisyDisk et iStat Menus. Analyse et supprime en profondeur les caches, les fichiers logs et les résidus de navigateurs. Désinstallateur intelligent qui retire proprement les applications et leurs fichiers cachés (Launch Agents, préférences). Analyseur d'espace disque interactif pour visualiser l'occupation des fichiers et gérer les documents volumineux. Tableau de bord temps réel (mo status) pour surveiller le CPU, le GPU, la mémoire et le réseau. Fonction de purge spécifique pour les développeurs permettant de supprimer les artefacts de build (node_modules, target, etc.). Intégration possible avec Raycast ou Alfred pour un lancement rapide des commandes. Installation simple via Homebrew ou un script curl. Des images Docker sécurisées pour chaque développeur https://www.docker.com/blog/docker-hardened-images-for-every-developer/ Docker rend ses "Hardened Images" (DHI) gratuites et open source (licence Apache 2.0) pour tous les développeurs. Ces images sont conçues pour être minimales, prêtes pour la production et sécurisées dès le départ afin de lutter contre l'explosion des attaques sur la chaîne logistique logicielle. Elles s'appuient sur des bases familières comme Alpine et Debian, garantissant une compatibilité élevée et une migration facile. Chaque image inclut un SBOM (Software Bill of Materials) complet et vérifiable, ainsi qu'une provenance SLSA de niveau 3 pour une transparence totale. L'utilisation de ces images permet de réduire considérablement le nombre de vulnérabilités (CVE) et la taille des images (jusqu'à 95 % plus petites). Docker étend cette approche sécurisée aux graphiques Helm et aux serveurs MCP (Mongo, Grafana, GitHub, etc.). Des offres commerciales (DHI Enterprise) restent disponibles pour des besoins spécifiques : correctifs critiques sous 7 jours, support FIPS/FedRAMP ou support à cycle de vie étendu (ELS). Un assistant IA expérimental de Docker peut analyser les conteneurs existants pour recommander l'adoption des versions sécurisées correspondantes. L'initiative est soutenue par des partenaires majeurs tels que Google, MongoDB, Snyk et la CNCF. Web La maçonnerie ("masonry") arrive dans la spécification des CSS et commence à être implémentée par les navigateurs https://webkit.org/blog/17660/introducing-css-grid-lanes/ Permet de mettre en colonne des éléments HTML les uns à la suite des autres. D'abord sur la première ligne, et quand la première ligne est remplie, le prochain élément se trouvera dans la colonne où il pourra être le plus haut possible, et ainsi de suite. après la plomberie du middleware, la maçonnerie du front :laughing: Data et Intelligence Artificielle On ne devrait pas faire un mapping 1:1 entre API REST et MCP https://nordicapis.com/why-mcp-shouldnt-wrap-an-api-one-to-one/ Problématique : Envelopper une API telle quelle dans le protocole MCP (Model Context Protocol) est un anti-pattern. Objectif du MCP : Conçu pour les agents d'IA, il doit servir d'interface d'intention, non de miroir d'API. Les agents comprennent les tâches, pas la logique complexe des API (authentification, pagination, orchestration). Conséquences du mappage un-à-un : Confusion des agents, erreurs, hallucinations. Difficulté à gérer les orchestrations complexes (plusieurs appels pour une seule action). Exposition des faiblesses de l'API (schéma lourd, endpoints obsolètes). Maintenance accrue lors des changements d'API. Meilleure approche : Construire des outils MCP comme des SDK pour agents, encapsulant la logique nécessaire pour accomplir une tâche spécifique. Pratiques recommandées : Concevoir autour des intentions/actions utilisateur (ex. : "créer un projet", "résumer un document"). Regrouper les appels en workflows ou actions uniques. Utiliser un langage naturel pour les définitions et les noms. Limiter la surface d'exposition de l'API pour la sécurité et la clarté. Appliquer des schémas d'entrée/sortie stricts pour guider l'agent et réduire l'ambiguïté. Des agents en production avec AWS - https://blog.ippon.fr/2025/12/22/des-agents-en-production-avec-aws/ AWS re:Invent 2025 a massivement mis en avant l'IA générative et les agents IA Un agent IA combine un LLM, une boucle d'appel et des outils invocables Strands Agents SDK facilite le prototypage avec boucles ReAct intégrées et gestion de la mémoire Managed MLflow permet de tracer les expérimentations et définir des métriques de performance Nova Forge optimise les modèles par réentraînement sur données spécifiques pour réduire coûts et latence Bedrock Agent Core industrialise le déploiement avec runtime serverless et auto-scaling Agent Core propose neuf piliers dont observabilité, authentification, code interpreter et browser managé Le protocole MCP d'Anthropic standardise la fourniture d'outils aux agents SageMaker AI et Bedrock centralisent l'accès aux modèles closed source et open source via API unique AWS mise sur l'évolution des chatbots vers des systèmes agentiques optimisés avec modèles plus frugaux Debezium 3.4 amène plusieurs améliorations intéressantes https://debezium.io/blog/2025/12/16/debezium-3-4-final-released/ Correction du problème de calcul du low watermark Oracle qui causait des pertes de performance Correction de l'émission des événements heartbeat dans le connecteur Oracle avec les requêtes CTE Amélioration des logs pour comprendre les transactions actives dans le connecteur Oracle Memory guards pour protéger contre les schémas de base de données de grande taille Support de la transformation des coordonnées géométriques pour une meilleure gestion des données spatiales Extension Quarkus DevServices permettant de démarrer automatiquement une base de données et Debezium en dev Intégration OpenLineage pour tracer la lignée des données et suivre leur flux à travers les pipelines Compatibilité testée avec Kafka Connect 4.1 et Kafka brokers 4.1 Infinispan 16.0.4 et .5 https://infinispan.org/blog/2025/12/17/infinispan-16-0-4 Spring Boot 4 et Spring 7 supportés Evolution dans les metriques Deux bugs de serialisation Construire un agent de recherche en Java avec l'API Interactions https://glaforge.dev/posts/2026/01/03/building-a-research-assistant-with-the-interactions-api-in-java/ Assistant de recherche IA Java (API Interactions Gemini), test du SDK implémenté par Guillaume. Workflow en 4 phases : Planification : Gemini Flash + Google Search. Recherche : Modèle "Deep Research" (tâche de fond). Synthèse : Gemini Pro (rapport exécutif). Infographie : Nano Banana Pro (à partir de la synthèse). API Interactions : gestion d'état serveur, tâches en arrière-plan, réponses multimodales (images). Appréciation : gestion d'état de l'API (vs LLM sans état). Validation : efficacité du SDK Java pour cas complexes. Stephan Janssen (le papa de Devoxx) a créé un serveur MCP (Model Context Protocol) basé sur LSP (Language Server Protocol) pour que les assistants de code analysent le code en le comprenant vraiment plutôt qu'en faisant des grep https://github.com/stephanj/LSP4J-MCP Le problème identifié : Les assistants IA utilisent souvent la recherche textuelle (type grep) pour naviguer dans le code, ce qui manque de contexte sémantique, génère du bruit (faux positifs) et consomme énormément de tokens inutilement. La solution LSP4J-MCP : Une approche "standalone" (autonome) qui encapsule le serveur de langage Eclipse (JDTLS) via le protocole MCP (Model Context Protocol). Avantage principal : Offre une compréhension sémantique profonde du code Java (types, hiérarchies, références) sans nécessiter l'ouverture d'un IDE lourd comme IntelliJ. Comparaison des méthodes : AST : Trop léger (pas de compréhension inter-fichiers). IntelliJ MCP : Puissant mais exige que l'IDE soit ouvert (gourmand en ressources). LSP4J-MCP : Le meilleur des deux mondes pour les workflows en terminal, à distance (SSH) ou CI/CD. Fonctionnalités clés : Expose 5 outils pour l'IA (find_symbols, find_references, find_definition, document_symbols, find_interfaces_with_method). Résultats : Une réduction de 100x des tokens utilisés pour la navigation et une précision accrue (distinction des surcharges, des scopes, etc.). Disponibilité : Le projet est open source et disponible sur GitHub pour intégration immédiate (ex: avec Claude Code, Gemini CLI, etc). A noter l'ajout dans claude code 2.0.74 d'un tool pour supporter LSP ( https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md#2074 ) Awesome (GitHub) Copilot https://github.com/github/awesome-copilot Une collection communautaire d'instructions, de prompts et de configurations pour optimiser l'utilisation de GitHub Copilot. Propose des "Agents" spécialisés qui s'intègrent aux serveurs MCP pour améliorer les flux de travail spécifiques. Inclut des prompts ciblés pour la génération de code, la documentation et la résolution de problèmes complexes. Fournit des instructions détaillées sur les standards de codage et les meilleures pratiques applicables à divers frameworks. Propose des "Skills" (compétences) sous forme de dossiers contenant des ressources pour des tâches techniques spécialisées. (les skills sont dispo dans copilot depuis un mois : https://github.blog/changelog/2025-12-18-github-copilot-now-supports-agent-skills/ ) Permet une installation facile via un serveur MCP dédié, compatible avec VS Code et Visual Studio. Encourage la contribution communautaire pour enrichir les bibliothèques de prompts et d'agents. Aide à augmenter la productivité en offrant des solutions pré-configurées pour de nombreux langages et domaines. Garanti par une licence MIT et maintenu activement par des contributeurs du monde entier. IA et productivité : bilan de l'année 2025 (Laura Tacho - DX)) https://newsletter.getdx.com/p/ai-and-productivity-year-in-review?aid=recNfypKAanQrKszT En 2025, l'ingénierie assistée par l'IA est devenue la norme : environ 90 % des développeurs utilisent des outils d'IA mensuellement, et plus de 40 % quotidiennement. Les chercheurs (Microsoft, Google, GitHub) soulignent que le nombre de lignes de code (LOC) reste un mauvais indicateur d'impact, car l'IA génère beaucoup de code sans forcément garantir une valeur métier supérieure. Si l'IA améliore l'efficacité individuelle, elle pourrait nuire à la collaboration à long terme, car les développeurs passent plus de temps à "parler" à l'IA qu'à leurs collègues. L'identité du développeur évolue : il passe de "producteur de code" à un rôle de "metteur en scène" qui délègue, valide et exerce son jugement stratégique. L'IA pourrait accélérer la montée en compétences des développeurs juniors en les forçant à gérer des projets et à déléguer plus tôt, agissant comme un "accélérateur" plutôt que de les rendre obsolètes. L'accent est mis sur la créativité plutôt que sur la simple automatisation, afin de réimaginer la manière de travailler et d'obtenir des résultats plus impactants. Le succès en 2026 dépendra de la capacité des entreprises à cibler les goulots d'étranglement réels (dette technique, documentation, conformité) plutôt que de tester simplement chaque nouveau modèle d'IA. La newsletter avertit que les titres de presse simplifient souvent à l'excès les recherches sur l'IA, masquant parfois les nuances cruciales des études réelles. Un développeur décrit dans un article sur Twitter son utilisation avancée de Claude Code pour le développement, avec des sous-agents, des slash-commands, comment optimiser le contexte, etc. https://x.com/AureaLibe/status/2008958120878330329?s=20 Outillage IntelliJ IDEA, thread dumps et project Loom (virtual threads) - https://blog.jetbrains.com/idea/2025/12/thread-dumps-and-project-loom-virtual-threads/ Les virtual threads Java améliorent l'utilisation du matériel pour les opérations I/O parallèles avec peu de changements de code Un serveur peut maintenant gérer des millions de threads au lieu de quelques centaines Les outils existants peinent à afficher et analyser des millions de threads simultanément Le débogage asynchrone est complexe car le scheduler et le worker s'exécutent dans des threads différents Les thread dumps restent essentiels pour diagnostiquer deadlocks, UI bloquées et fuites de threads Netflix a découvert un deadlock lié aux virtual threads en analysant un heap dump, bug corrigé dans Java 25. Mais c'était de la haute voltige IntelliJ IDEA supporte nativement les virtual threads dès leur sortie avec affichage des locks acquis IntelliJ IDEA peut ouvrir des thread dumps générés par d'autres outils comme jcmd Le support s'étend aussi aux coroutines Kotlin en plus des virtual threads Quelques infos sur IntelliJ IDEA 2025.3 https://blog.jetbrains.com/idea/2025/12/intellij-idea-2025-3/ Distribution unifiée regroupant davantage de fonctionnalités gratuites Amélioration de la complétion des commandes dans l'IDE Nouvelles fonctionnalités pour le débogueur Spring Thème Islands devient le thème par défaut Support complet de Spring Boot 4 et Spring Framework 7 Compatibilité avec Java 25 Prise en charge de Spring Data JDBC et Vitest 4 Support natif de Junie et Claude Agent pour l'IA Quota d'IA transparent et option Bring Your Own Key à venir Corrections de stabilité, performance et expérience utilisateur Plein de petits outils en ligne pour le développeur https://blgardner.github.io/prism.tools/ génération de mot de passe, de gradient CSS, de QR code encodage décodage de Base64, JWT formattage de JSON, etc. resumectl - Votre CV en tant que code https://juhnny5.github.io/resumectl/ Un outil en ligne de commande (CLI) écrit en Go pour générer un CV à partir d'un fichier YAML. Permet l'exportation vers plusieurs formats : PDF, HTML, ou un affichage direct dans le terminal. Propose 5 thèmes intégrés (Modern, Classic, Minimal, Elegant, Tech) personnalisables avec des couleurs spécifiques. Fonctionnalité d'initialisation (resumectl init) permettant d'importer automatiquement des données depuis LinkedIn et GitHub (projets les plus étoilés). Supporte l'ajout de photos avec des options de filtre noir et blanc ou de forme (rond/carré). Inclut un mode "serveur" (resumectl serve) pour prévisualiser les modifications en temps réel via un navigateur local. Fonctionne comme un binaire unique sans dépendances externes complexes pour les modèles. mactop - Un moniteur "top" pour Apple Silicon https://github.com/metaspartan/mactop Un outil de surveillance en ligne de commande (TUI) conçu spécifiquement pour les puces Apple Silicon (M1, M2, M3, M4, M5). Permet de suivre en temps réel l'utilisation du CPU (E-cores et P-cores), du GPU et de l'ANE (Neural Engine). Affiche la consommation électrique (wattage) du système, du CPU, du GPU et de la DRAM. Fournit des données sur les températures du SoC, les fréquences du GPU et l'état thermique global. Surveille l'utilisation de la mémoire vive, de la swap, ainsi que l'activité réseau et disque (E/S). Propose 10 mises en page (layouts) différentes et plusieurs thèmes de couleurs personnalisables. Ne nécessite pas l'utilisation de sudo car il s'appuie sur les API natives d'Apple (SMC, IOReport, IOKit). Inclut une liste de processus détaillée (similaire à htop) avec la possibilité de tuer des processus directement depuis l'interface. Offre un mode "headless" pour exporter les métriques au format JSON et un serveur optionnel pour Prometheus. Développé en Go avec des composants en CGO et Objective-C. Adieu direnv, Bonjour misehttps://codeka.io/2025/12/19/adieu-direnv-bonjour-mise/ L'auteur remplace ses outils habituels (direnv, asdf, task, just) par un seul outil polyvalent écrit en Rust : mise. mise propose trois fonctions principales : gestionnaire de paquets (langages et outils), gestionnaire de variables d'environnement et exécuteur de tâches. Contrairement à direnv, il permet de gérer des alias et utilise un fichier de configuration structuré (mise.toml) plutôt que du scripting shell. La configuration est hiérarchique, permettant de surcharger les paramètres selon les répertoires, avec un système de "trust" pour la sécurité. Une "killer-feature" soulignée est la gestion des secrets : mise s'intègre avec age pour chiffrer des secrets (via clés SSH) directement dans le fichier de configuration. L'outil supporte une vaste liste de langages et d'outils via un registre interne et des plugins (compatibilité avec l'écosystème asdf). Il simplifie le workflow de développement en regroupant l'installation des outils et l'automatisation des tâches au sein d'un même fichier. L'auteur conclut sur la puissance, la flexibilité et les excellentes performances de l'outil après quelques heures de test. Claude Code v2.1.0 https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md#210 Rechargement à chaud des "skills" : Les modifications apportées aux compétences dans ~/.claude/skills sont désormais appliquées instantanément sans redémarrer la session. Sous-agents et forks : Support de l'exécution de compétences et de commandes slash dans un contexte de sous-agent forké via context: fork. Réglages linguistiques : Ajout d'un paramètre language pour configurer la langue de réponse par défaut (ex: language: "french"). Améliorations du terminal : Shift+Enter fonctionne désormais nativement dans plusieurs terminaux (iTerm2, WezTerm, Ghostty, Kitty) sans configuration manuelle. Sécurité et correction de bugs : Correction d'une faille où des données sensibles (clés API, tokens OAuth) pouvaient apparaître dans les logs de débogage. Nouvelles commandes slash : Ajout de /teleport et /remote-env pour les abonnés claude.ai afin de gérer des sessions distantes. Mode Plan : Le raccourci /plan permet d'activer le mode plan directement depuis le prompt, et la demande de permission à l'entrée de ce mode a été supprimée. Vim et navigation : Ajout de nombreux mouvements Vim (text objects, répétitions de mouvements f/F/t/T, indentations, etc.). Performance : Optimisation du temps de démarrage et du rendu terminal pour les caractères Unicode/Emoji. Gestion du gitignore : Support du réglage respectGitignore dans settings.json pour contrôler le comportement du sélecteur de fichiers @-mention. Méthodologies 200 déploiements en production par jour, même le vendredi : retours d'expérience https://mcorbin.fr/posts/2025-03-21-deploy-200/ Le déploiement fréquent, y compris le vendredi, est un indicateur de maturité technique et augmente la productivité globale. L'excellence technique est un atout stratégique indispensable pour livrer rapidement des produits de qualité. Une architecture pragmatique orientée services (SOA) facilite les déploiements indépendants et réduit la charge cognitive. L'isolation des services est cruciale : un développeur doit pouvoir tester son service localement sans dépendre de toute l'infrastructure. L'automatisation via Kubernetes et l'approche GitOps avec ArgoCD permettent des déploiements continus et sécurisés. Les feature flags et un système de permissions solide permettent de découpler le déploiement technique de l'activation fonctionnelle pour les utilisateurs. L'autonomie des développeurs est renforcée par des outils en self-service (CLI maison) pour gérer l'infrastructure et diagnostiquer les incidents sans goulot d'étranglement. Une culture d'observabilité intégrée dès la conception permet de détecter et de réagir rapidement aux anomalies en production. Accepter l'échec comme inévitable permet de concevoir des systèmes plus résilients capables de se rétablir automatiquement. "Vibe Coding" vs "Prompt Engineering" : l'IA et le futur du développement logiciel https://www.romenrg.com/blog/2025/12/25/vibe-coding-vs-prompt-engineering-ai-and-the-future-of-software-development/ L'IA est passée du statut d'expérimentation à celui d'infrastructure essentielle pour le développement de logiciels en 2025. L'IA ne remplace pas les ingénieurs, mais agit comme un amplificateur de leurs compétences, de leur jugement et de la qualité de leur réflexion. Distinction entre le "Vibe Coding" (rapide, intuitif, idéal pour les prototypes) et le "Prompt Engineering" (délibéré, contraint, nécessaire pour les systèmes maintenables). L'importance cruciale du contexte ("Context Engineering") : l'IA devient réellement puissante lorsqu'elle est connectée aux systèmes réels (GitHub, Jira, etc.) via des protocoles comme le MCP. Utilisation d'agents spécialisés (écriture de RFC, revue de code, architecture) plutôt que de modèles génériques pour obtenir de meilleurs résultats. Émergence de l'ingénieur "Technical Product Manager" capable d'abattre seul le travail d'une petite équipe grâce à l'IA, à condition de maîtriser les fondamentaux techniques. Le risque majeur : l'IA permet d'aller très vite dans la mauvaise direction si le jugement humain et l'expérience font défaut. Le niveau d'exigence global augmente : les bases techniques solides deviennent plus importantes que jamais pour éviter l'accumulation de dette technique rapide. Une revue de code en solo (Kent Beck) ! https://tidyfirst.substack.com/p/party-of-one-for-code-review?r=64ov3&utm_campaign=post&utm_medium=web&triedRedirect=true La revue de code traditionnelle, héritée des inspections formelles d'IBM, s'essouffle car elle est devenue trop lente et asynchrone par rapport au rythme du développement moderne. Avec l'arrivée de l'IA ("le génie"), la vitesse de production du code dépasse la capacité de relecture humaine, créant un goulot d'étranglement majeur. La revue de code doit évoluer vers deux nouveaux objectifs prioritaires : un "sanity check" pour vérifier que l'IA a bien fait ce qu'on lui demandait, et le contrôle de la dérive structurelle de la base de code. Maintenir une structure saine est crucial non seulement pour les futurs développeurs humains, mais aussi pour que l'IA puisse continuer à comprendre et modifier le code efficacement sans perdre le contexte. Kent Beck expérimente des outils automatisés (comme CodeRabbit) pour obtenir des résumés et des schémas d'architecture afin de garder une conscience globale des changements rapides. Même si les outils automatisés sont utiles, le "Pair Programming" reste irremplaçable pour la richesse des échanges et la pression sociale bénéfique qu'il impose à la réflexion. La revue de code solo n'est pas une fin en soi, mais une adaptation nécessaire lorsque l'on travaille seul avec des outils de génération de code augmentés. Loi, société et organisation Lego lance les Lego Smart Play, avec des Brique, des Smart Tags et des Smart Figurines pour faire de nouvelles constructions interactives avec des Legos https://www.lego.com/fr-fr/smart-play LEGO SMART Play : technologie réactive au jeu des enfants. Trois éléments clés : SMART Brique : Brique LEGO 2x4 "cerveau". Accéléromètre, lumières réactives, détecteur de couleurs, synthétiseur sonore. Réagit aux mouvements (tenir, tourner, taper). SMART Tags : Petites pièces intelligentes. Indiquent à la SMART Brique son rôle (ex: hélicoptère, voiture) et les sons à produire. Activent sons, mini-jeux, missions secrètes. SMART Minifigurines : Activées près d'une SMART Brique. Révèlent des personnalités uniques (sons, humeurs, réactions) via la SMART Brique. Encouragent l'imagination. Fonctionnement : SMART Brique détecte SMART Tags et SMART Minifigurines. Réagit aux mouvements avec lumières et sons dynamiques. Compatibilité : S'assemble avec les briques LEGO classiques. Objectif : Créer des expériences de jeu interactives, uniques et illimitées. Conférences La liste des conférences provenant de Developers Conferences Agenda/List par Aurélie Vache et contributeurs : 14-17 janvier 2026 : SnowCamp 2026 - Grenoble (France) 22 janvier 2026 : DevCon #26 : sécurité / post-quantique / hacking - Paris (France) 28 janvier 2026 : Software Heritage Symposium - Paris (France) 29-31 janvier 2026 : Epitech Summit 2026 - Paris - Paris (France) 2-5 février 2026 : Epitech Summit 2026 - Moulins - Moulins (France) 3 février 2026 : Cloud Native Days France 2026 - Paris (France) 3-4 février 2026 : Epitech Summit 2026 - Lille - Lille (France) 3-4 février 2026 : Epitech Summit 2026 - Mulhouse - Mulhouse (France) 3-4 février 2026 : Epitech Summit 2026 - Nancy - Nancy (France) 3-4 février 2026 : Epitech Summit 2026 - Nantes - Nantes (France) 3-4 février 2026 : Epitech Summit 2026 - Marseille - Marseille (France) 3-4 février 2026 : Epitech Summit 2026 - Rennes - Rennes (France) 3-4 février 2026 : Epitech Summit 2026 - Montpellier - Montpellier (France) 3-4 février 2026 : Epitech Summit 2026 - Strasbourg - Strasbourg (France) 3-4 février 2026 : Epitech Summit 2026 - Toulouse - Toulouse (France) 4-5 février 2026 : Epitech Summit 2026 - Bordeaux - Bordeaux (France) 4-5 février 2026 : Epitech Summit 2026 - Lyon - Lyon (France) 4-6 février 2026 : Epitech Summit 2026 - Nice - Nice (France) 5 février 2026 : Web Days Convention - Aix-en-Provence (France) 12 février 2026 : Strasbourg Craft #1 - Strasbourg (France) 12-13 février 2026 : Touraine Tech #26 - Tours (France) 19 février 2026 : ObservabilityCON on the Road - Paris (France) 6 mars 2026 : WordCamp Nice 2026 - Nice (France) 18-19 mars 2026 : Agile Niort 2026 - Niort (France) 20 mars 2026 : Atlantique Day 2026 - Nantes (France) 26 mars 2026 : Data Days Lille - Lille (France) 26-27 mars 2026 : SymfonyLive Paris 2026 - Paris (France) 26-27 mars 2026 : REACT PARIS - Paris (France) 27-29 mars 2026 : Shift - Nantes (France) 31 mars 2026 : ParisTestConf - Paris (France) 1 avril 2026 : AWS Summit Paris - Paris (France) 2 avril 2026 : Pragma Cannes 2026 - Cannes (France) 9-10 avril 2026 : AndroidMakers by droidcon - Paris (France) 16-17 avril 2026 : MiXiT 2026 - Lyon (France) 22-24 avril 2026 : Devoxx France 2026 - Paris (France) 23-25 avril 2026 : Devoxx Greece - Athens (Greece) 24-25 avril 2026 : Faiseuses du Web 5 - Dinan (France) 6-7 mai 2026 : Devoxx UK 2026 - London (UK) 22 mai 2026 : AFUP Day 2026 Lille - Lille (France) 22 mai 2026 : AFUP Day 2026 Paris - Paris (France) 22 mai 2026 : AFUP Day 2026 Bordeaux - Bordeaux (France) 22 mai 2026 : AFUP Day 2026 Lyon - Lyon (France) 29 mai 2026 : NG Baguette Conf 2026 - Paris (France) 5 juin 2026 : TechReady - Nantes (France) 5 juin 2026 : Fork it! - Rouen - Rouen (France) 6 juin 2026 : Polycloud - Montpellier (France) 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) 17-19 juin 2026 : Devoxx Poland - Krakow (Poland) 17-20 juin 2026 : VivaTech - Paris (France) 2 juillet 2026 : Azur Tech Summer 2026 - Valbonne (France) 2-3 juillet 2026 : Sunny Tech - Montpellier (France) 3 juillet 2026 : Agile Lyon 2026 - Lyon (France) 2 août 2026 : 4th Tech Summit on Artificial Intelligence & Robotics - Paris (France) 4 septembre 2026 : JUG Summer Camp 2026 - La Rochelle (France) 17-18 septembre 2026 : API Platform Conference 2026 - Lille (France) 24 septembre 2026 : PlatformCon Live Day Paris 2026 - Paris (France) 1 octobre 2026 : WAX 2026 - Marseille (France) 1-2 octobre 2026 : Volcamp - Clermont-Ferrand (France) 5-9 octobre 2026 : Devoxx Belgium - Antwerp (Belgium) 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/

What if paying players actually made games more profitable?In this episode, we sit down with Ben Cousens (Chief Strategy Officer at ZBD) to unpack how embedded payouts, loyalty rewards, and regulated payments infrastructure can radically change retention, LTV, and monetization in mobile games.This is payments, psychology, and monetization design.Topics covered• Why gaming has a payments problem• Embedded rewards vs cash-for-tasks• How ZBD increases retention by 180%• Sharing ad revenue with players• Anti-fraud & compliance realities• UA creatives that attract better cohorts• Bank payouts & real-world spend in 2026More on ZBD SDK: https://zbd.gg/z/rewards-sdkCase studies mentioned: https://zbdpay.com/en/case-studiesZBD: https://zbdpay.comBen Cousens : https://www.linkedin.com/in/bencousens/RSVP to Game of Tones II: https://luma.com/07c3ffq0?utm_source=twoandahalfgamers---------------------------------------This is no BS gaming podcast 2.5 gamers session. Sharing actionable insights, dropping knowledge from our day-to-day User Acquisition, Game Design, and Ad monetization jobs. We are definitely not discussing the latest industry news, but having so much fun! Let's not forget this is a 4 a.m. conference discussion vibe, so let's not take it too seriously.Panelists: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Felix Braberg, Matej Lancaric⁠Special guest: Ben Cousens https://www.linkedin.com/in/bencousens/Join our slack channel here: https://join.slack.com/t/two-and-half-gamers/shared_invite/zt-2um8eguhf-c~H9idcxM271mnPzdWbipgChapters00:00 — Why 180% retention sounds like BS?01:35 — Ben's background: games, banking, VC, ZBD04:25 — What ZBD actually is (and isn't)06:20 — The real payments problem in gaming09:10 — Money lifecycle in games: pay-in, move, pay-out11:15 — Why pay-outs are allowed when pay-ins aren't13:00 — Embedded rewards vs “cash for tasks”14:30 — Bitcoin Miner & easter-egg rewards explained17:20 — Why sharing ad revenue increases LTV19:40 — From Bitcoin wallets to direct bank payouts22:00 — How rewards change player behavior long-term24:00 — Fraud, bots & anti-abuse systems26:50 — Why this works better than classic rewards apps29:35 — Tech integration & SDK reality31:40 — UA creatives and signaling “this game pays you”33:45 — Regulation costs & why others can't copy this35:10 — What's coming in 2026 (bank, real-world spend)37:10 — Blurring virtual and real economies39:20 — Who should actually use ZBD41:10 — Final take: owning the player relationship---------------------------------------Matej LancaricUser Acquisition & Creatives Consultant⁠https://lancaric.meFelix BrabergAd monetization consultant⁠https://www.felixbraberg.comJakub RemiarGame design consultant⁠https://www.linkedin.com/in/jakubremiar---------------------------------------Please share the podcast with your industry friends, dogs & cats. Especially cats! They love it!Hit the Subscribe button on YouTube, Spotify, and Apple!Please share feedback and comments - matej@lancaric.me---------------------------------------If you are interested in getting UA tips every week on Monday, visit ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠lancaric.substack.com⁠⁠⁠⁠⁠⁠ & sign up for the Brutally Honest newsletter by Matej LancaricDo you have UA questions nobody can answer? Ask ⁠⁠⁠⁠⁠⁠⁠⁠Matej AI⁠⁠⁠⁠⁠⁠ - the First UA AI in the gaming industry! https://lancaric.me/matej-ai

Edge AI is evolving quickly - what's changing in the tooling and frameworks that support it? And where do the biggest opportunities for improvement lie? In this episode of Edge of Tomorrow – The Edge AI Debate, host Pete Bernard (CEO, EDGE AI FOUNDATION) is joined by Elia Schoenberger (Product Marketing, AI Division at Civa) and Nathan Francis (Business Development at AIZip) for an in-depth discussion on the role of tooling and frameworks in shaping the future of Edge AI. While much of the attention in AI is placed on models and hardware, this conversation focuses on the layers in between — compilers, SDKs, deployment pipelines, and frameworks — and how they influence speed, scalability, and collaboration across the ecosystem. The discussion explores how hardware constraints, model design, and tooling choices intersect, whether the industry is moving toward standardisation or continuing to prioritise innovation, and what practical steps could help simplify Edge AI development without slowing progress. This episode offers a look at how the Edge AI stack is evolving - and what it will take to support broader, more efficient deployment in the years ahead. Chapters… 00:00 Introductions 01:40 Why tooling and frameworks matter in Edge AI 03:25 Hardware constraints, models, and deployment realities 05:23 Fragmentation vs fit-for-purpose tooling 07:59 Power, performance, and memory trade-offs 09:18 Where Edge AI sits on the maturity curve 11:32 Standardisation, innovation, and ecosystem balance 13:32 Compilers, MLIR, and unifying the toolchain 16:02 Deployment challenges and quantisation complexity 25:17 Generative models arriving at the edge 31:36 Local-first intelligence and when the cloud still matters 32:52 What would help accelerate Edge AI development 36:13 Final reflections and closing thoughts The episode is live on all major listening platforms now: https://linktr.ee/theiotpodcast Connect with our guests… Elia Schoenberger (CIVA,Inc): https://www.linkedin.com/in/eliashenberger/ Nathan Francis (AIZip): https://www.linkedin.com/in/nathanfrancis99/ About Edge of Tomorrow – The Edge AI Debate Edge of Tomorrow is our debate-led spin-off series bringing together leaders from across the Edge AI ecosystem to explore the technical, commercial, and strategic decisions shaping how intelligence moves closer to the real world. SUBSCRIBE TO THE IOT PODCAST ON YOUR FAVOURITE LISTENING PLATFORM: https://linktr.ee/theiotpodcast Sign up for exclusive email updates: https://theiotpodcast.com/get-exclusive-access/ Contact us to become a guest or partner: https://theiotpodcast.com/contact/

✍【乱翻书时刻】• 2025Meta壕购字节没收成的Manus——2017字节吞并Facebook放弃的Musical.ly——这对信息流广告超级机器，早在2012年就已如同师生，尤其是在组织与商业化上。2018年，双方的全球竞争终于亮牌。扎克伯格和张一鸣心中不同的北极星指标，抖音夸张的商业化攫取效率，构成了必然发生在2025/2026的交叉点。• 激进的商业化标杆也解释了——为何2018年初抖音赶超快手，年终国内月活就拉开2亿差距，海外TikTok遥遥领先。2017快手商业化首年就超过70亿收入。双方当年战略空间和定力的差异，大概就源于张利东刘思齐等在2014-2016三年建成了今日头条广告系统，OCPX类效果广告占比约60%，已经从KA和SMB获取了75亿的收入弹药储备。• 张利东曾经是一位怎样的记者，为什么这位传统报纸经营者那么猛，一年调高十倍销售目标？字节为何立下每月3000人+的招聘目标，全力做重支持SMB广告业务？电商平台和中国半数VC融资，为什么都被卷入这种营销风潮？百度和腾讯的商业化团队为什么无法做出有效反击？

The Vision for a Core AI SubscriptionIn this snippet, Sam Altman, CEO of OpenAI, outlines a bold ambition: making OpenAI the core AI subscription people rely on every day.Built on experiences like ChatGPT, the vision includes:

Allen, Joel, and Rosemary break down the Trump administration’s sudden halt of five major offshore wind projects, including Coastal Virginia Offshore Wind and parts of Vineyard Wind, over national security claims the hosts find questionable. They also cover the FCC’s ban on new DJI drone imports and what operators should do now, plus Fraunhofer’s latest wind research featured in PES Wind Magazine. Sign up now for Uptime Tech News, our weekly email update on all things wind technology. This episode is sponsored by Weather Guard Lightning Tech. Learn more about Weather Guard’s StrikeTape Wind Turbine LPS retrofit. Follow the show on Facebook, YouTube, Twitter, Linkedin and visit Weather Guard on the web. And subscribe to Rosemary Barnes’ YouTube channel here. Have a question we can answer on the show? Email us! The Uptime Wind Energy Podcast brought to you by Strike Tape, protecting thousands of wind turbines from lightning damage worldwide. Visit strike tape.com. And now your hosts, Alan Hall, Rosemary Barnes, Joel Saxon, and Yolanda Padron. Welcome to the Uptime Wind Energy Allen Hall: Podcast. I’m your host, Alan Hall, and I’m here with. Rosemary Barnes in Australia and Joel Saxon is down in Austin, Texas. Yolanda Padron is on holiday, and well, there’s been a lot happening in the past 24 hours as we’re recording this today. If you thought the battle over offshore wind was over based on some recent court cases, well think again. The Trump administration just dropped the hammer on five major offshore wind projects. Exciting. National security concerns. The Secretary of the Interior, Doug Bergham announced. The immediate pause affecting projects from Ted Eor, CIP and Dominion Energy. So Coastal [00:01:00] Virginia, offshore wind down in Virginia, right? Which is the one we thought was never gonna be touched. Uh, the Department of War claims classified reports show these giant turbines create radar interference that could blind America’s defenses. Half of vineyard winds, turbines are already up and running, producing power, by the way. Uh, and. I guess they, it sounds like from what I can see in more recent news articles that they turn the power off. They just shut the turbines off even though those turbines are fully functioning and delivering power to shore. Uh, so now the question is what happens? Where does this go? And I know Osted is royally upset about it, and Eor obviously along with them, why not? But the whole Denmark us, uh, relationship is going nuclear right now. Joel Saxum: I think here’s a, here’s a technical thing that a lot of people might not know. If you’re in the wind industry in the United States, you may know this. There’s a a few sites in the northern corner of Colorado that are right next to Nebraska, [00:02:00] and that is where there is a strategic military installations of subsurface, basically rocket launches and. And in that entire area, there is heavy radar presence to be able to make sure that we’re watching over these things and there are turbines hundreds of meters away from these launch sites at like, I’ve driven past them. Right? So that is a te to me, the, the radar argument is a technical mute point. Um, Alan, you and I have been kind of back and forth in Slack. Uh, you and I and the team here, Rosemary’s been in it too, like just kind of talking through. Of course none of us were happy. Right. But talking through some of the points of, of some of these things and it’s just like basically you can debunk almost every one of them and you get down to the level where it is a, what is the real reasoning here? It’s a tit for tat. Like someone doesn’t like offshore wind turbines. Is it a political, uh, move towards being able to strengthen other interests and energy or what? I don’t know. ’cause I can’t, I’m not sitting in the Oval Office, but. [00:03:00] At the end of the day, we need these electrons. And what you’re doing is, is, is you’re hindering national security or because national security is energy security is national security, my opinion, and a lot of people’s opinions, you’re hindering that going forward. Allen Hall: Well, let’s look at the defense argument at the minute, which is it’s, it’s somehow deterring, reducing the effectiveness of ground radars, protecting the shoreline. That is a bogus argument. There’s all kinds of objects out on the water right now. There’s a ton of ships out there. They’re constantly moving around. To know where a fixed object is out in the water is easy, easy, and it has been talked about for more than 15 years. If you go back and pull the information that exists on the internet today from the Department of Defense at the time, plus Department of Interior and everybody else, they’ve been looking at this forever. The only way these turbines get placed where they are is with approval from the Department of Defense. So it isn’t like it didn’t go through a review. It totally did. They’ve known about this for a long, long time. So now to bring up this [00:04:00] specious argument, like, well, all of a sudden the radar is a problem. No, no. It’s not anybody’s telling you it’s a classified. Piece of information that is also gonna be a bogus argument because what is going along with that are these arguments as well, the Defense Department or Department of War says it’s gonna cause interference or, or some degradation of some sort of national defense. Then the words used after it have nothing to do with that. It is, the turbines are ugly, the turbines are too tall. It may interfere, interfere with the whales, it may interfere with fishing, and I don’t like it. Or a, a gas pipeline could produce more power than the turbines can. That that has nothing to do with the core argument. If the core argument is, is some sort of defense related. Security issue, then say it because it, it can’t be that complicated. Now, if you, if you knew anything about the defense department and how it operates, and also the defenses around the United States, of which I know a little bit about, [00:05:00] having been in aerospace for 30 freaking years, I can tell you that there are all kinds of ways to detect all kinds of threats that are approaching our shoreline. Putting a wind turbine out there is not Joel Saxum: gonna stop it. So the, at the end of the day, there is a bunch, there’s like, there’s single, I call them metric and intrinsic, right? Metric being like, I can put data to this. There’s a point here, there’s numbers, whatever it may be. And intrinsic being, I don’t like them, they don’t look that good. A pipeline can supply more energy. Those things are not necessarily set in stone. They’re not black and white. They’re, they’re getting this gray emotional area instead of practical. Right. So, okay. What, what’s the outcome here? You do this, you say that we have radar issues. Do we do, does, does the offshore substation have a radar station on it for the military or, or what does that, what does that look like? Allen Hall: Maybe it does, maybe it doesn’t, but if the threat is what I think it is, none of this matters. None of this matters. It’s already been discussed a hundred times with the defense [00:06:00] department and everybody else is knowledgeable in this, in this space. There is no way that they started planted turbines and approve them two, three years ago. If it was a national security risk, there is no chance that that happened. So it really is frustrating when you, when you know some of the things that go on behind the scenes and you know what, the technical rationales could be about a problem. And that’s not what’s being talked about right now that I don’t like being lied to. Like, if you want to have a, a political argument, have a political argument, and the, if the political argument is America wants Greenland from Denmark, then just freaking say it. Just say it. Don’t tie Massachusetts, New York, Connecticut, new J, all, all these states up until this nonsense, Virginia, what are we doing? What are we doing? Because all those states approved all those projects knowing full well what the costs were, knowing how tall the turbines were, knowing how long it was gonna take to get it done, and they all approved them. This [00:07:00] is not done in a vacuum. These states approve these projects and these states are going to buy that power. Let them, you wanna put in a a, a big gas pipeline. Great. How many years is that gonna take, Doug? How many years is that gonna take? Doug Bergham? Does anybody know? He, he doesn’t know anything about that. Joel Saxum: You’re not getting a gas pipeline into the east coast anytime soon whatsoever. Because the, the east, the east coast is a home of Nimbyism. Allen Hall: Sure, sir. Like Massachusetts. It’s pretty much prohibited new gas pipelines for a long time. Okay. That’s their choice. That is their choice. They made that choice. Let them live with it. Why are you then trying to, to double dip? I don’t get it. I don’t get it. And, but I do think, Joel, I think the reason. This is getting to the level it is. It has to do something to do with Greenland. It has something to do with the Danish, um, uh, ambassador or whoever it was running to talk to, to California and Newsom about offshore tournaments. Like that was not a smart move, my opinion, but [00:08:00] I don’t run international relations with for Denmark. But stop poking one another and somebody’s gotta cut this off. The, the thing I think that the Trump administration is at risk at is that. Or instead, Ecuador has plenty of cash. They’re gonna go to court, and they are most likely going to win, and they’re going to really handcuff the Trump administration to do anything because when you throw bull crap in front of a judge and they smell it, the the pushback gets really strong. Well, they’re gonna force all the discussion about anything to do with offshore to go through a judge, and they’re gonna decide, and I don’t think that’s what the Trump administration wants, but that’s where they’re headed. I’m not sure why Joel Saxum: you’d wanna do that. Like at the end of the day, that may be the solution that has to come, but I don’t think that that’s not the right path either. Right? Because a judge is not an SME. A judge doesn’t know all of the, does the, you know, like a, a judge is a judge based on laws. They don’t, they’re, they’re not an offshore wind energy expert, so they sh that’s hard for them to [00:09:00] decide on. However, that’s where it will go. But I think you’re correct. Like this, this is more, this is a larger play and, and this mor so this morning when this rolled out, my WhatsApp, uh, and text messages just blew up from all of my. Danish friends, what is going on over there? I’m like, I don’t know what you want me to say. I’m not in the hopeful office. I can’t tell you what’s going on. I’m not having coffee in DC right now. I said, you know, but going back to it, like you can see the frustration, like, what, why, why is this the thing? And I think you’re right though, Alan, it is a large, there’s a larger political play in, in movement here of this Greenland, Denmark, these kind of things. And it’s a, it’s. It’s sad to see it ’cause it just gets caught. We’re getting caught in the crossfire as a wind industry. Yeah. It’s Allen Hall: not helping anybody. And when you set precedents like this, the other side takes note, right? So Democrats, when they eventually get back into the White House again, which will happen at some point, are gonna swing the pendulum just as hard and harder. So what are you [00:10:00] doing? None of, none of this matters in, in my opinion, especially if you, if you read Twitter today, you’re like, what the hell? All the things that are happening right now. RFK Jr had a post a few hours ago talking about, oh, this is great. We’re gonna shut off this off shore wind thing because it kills the whales. Sorry, it doesn’t. Sorry. It doesn’t, if you want, if you wanna make an argument about it, you have to do better than that. A Twitter post doesn’t make it fact, and everybody who’s listened to this and paying attention, I don’t want you to do your own research, but just know that you got a couple of engineers here, that that’s what we do for a living. We source through information, making sure that it makes sense. Does it align? Is it right? Is it wrong? Is, is there something to back it up with? And the information that we have here says. It is. It’s not hurting anything out there. You may not like them, but you know what? You don’t want a coal factor in your backyard either. Delamination and bottomline failures and blades are difficult problems to detect [00:11:00] early. These hidden issues can cost you millions in repairs and lost energy production. C-I-C-N-D-T are specialists to detect these critical flaws before they become expensive burdens. Their non-destructive test technology penetrates deep to blade materials to find voids and cracks. Traditional inspections completely. Miss C-I-C-N-D-T Maps. Every critical defect delivers actionable reports and provides support to get your blades back in service. So visit cic ndt.com because catching blade problems early will save you millions. Joel Saxum: When it comes down to sorting through data, I think that’s a big problem. Right? And that’s what’s happening with a lot of the, I mean, generalizing, a lot of the things that are happening in the United States in the last 10 years give it. Um, but people just go, oh, this person said this. They must be an authority. Like, no, it’s not true. We’ve been following [00:12:00] a lot of these things with offshore wind. I mean, probably closer than most. Uh, besides the companies that are developing those wind farms, simply because it’s a part of our day job, it’s what we do. We’re, we’re, we’re looking at these things, right? So. Understanding the risks, uh, rewards, the political side of things. The commercial side. The technical side. That’s what we’re here to kind of feed, feed the information back to the masses. And a lot of this, or the majority of all of this is bs. It doesn’t really, it doesn’t, it doesn’t play. Um, and then you go a little bit deeper into things and. Like the, was it the new Bedford Light, Alan, that said like, now they’re seeing that the turbines have actually been turned off, not just to stop work for construction. They’ve turned the turbines off up in Massachusetts or up off of in the northeast area? No, that they have. Allen Hall: And why? I mean, the error on the side of caution, I think if you’re an attorney for any of the wind operations, they’re gonna tell you to shut it off for a couple of days and see what we can figure out. But the, the timing of the [00:13:00] shutdown I think is a little unique in that the US is pretty much closed at this point. You’re not gonna see anything start back up for another couple of weeks, although they were doing work on the water. So you can impose a couple hundred million. Do, well, not a hundred million dollars, but maybe a couple million dollars of, of overhead costs in some of these projects because you can’t respond quick enough. You gotta find a judge willing to put a stay in to hold things the same and, and hold off this, uh, this, uh, b order, but. To me, you know, it’s one of those things when you deal with the federal government, you think the federal government is erratic in just this one area? No, it’s erratic in a lot of areas. And the frustration comes with do you want America to be stronger or do you want nonsense to go on? You know? And if I thought, if that thought wind turbines were killing whales, I’d be the first one up to screaming. If I thought offshore wind was not gonna work out in term, in some long-term model, I would be the first one screaming about it. That’s not Joel Saxum: reality. [00:14:00] Caveat that though you said, you’re saying if I thought, I think the, the real word should be if I did the research, the math and understood that this is the way it was gonna be. Right? Because that’s, that’s what you need to do. And that’s what we’ve been doing, is looking at it and the, the, all the data points to we’re good here. If someone wanted to do harm Allen Hall: to the United States, and God forbid if that was ever the case. That wouldn’t be the way to do it. Okay. And we, and we’ve seen that through history, right. So it, it’s, it doesn’t even make any sense. The problem is, is that they can shield a judge from looking at it somewhat. If they classify well, the judge isn’t able to see what this classified information is. In today’s world, AI and everything on the internet, you don’t think somebody knows something about this? I do. And to think that you couldn’t make any sort of software patch to. Fix whatever 1965 radar system they have sitting on the shorelines of Massachusetts. They could, in today’s world, you can do that. So this whole thing, it [00:15:00] just sounds like a smoke screen and when you start poking around it, no one has an answer. That is the frustrating bit. If you’re gonna be seeing stuff, you better have backup data. But the Joel Saxum: crazy thing here, like look at the, the, the non wind side of this argument, like you’re hurting job growth. Everybody that goes into a, uh. Into office. One of the biggest things they run on all the time, it doesn’t matter, matter where you are in the world, is I’m gonna bring jobs and prosperity to the people. Okay. How many jobs have just been stopped? How many people have just been sent home? How much money’s being lost here? And who’s one of the biggest companies installing these turbines in the states? Fricking ge like so. You’re, you’re hurting your own local people. And not only is this, you stand there and say, we’re doing all this stuff. We’re getting all this wind energy. We’re gonna do all these things and we’re gonna win the AI race. To the point where you’ve passed legislation or you’ve written, uh, uh, executive order that says, Hey, individual states, if you pass legislation [00:16:00] that slows or halts AI development in your state, the federal government can sue you. But you’re doing the same thing. You’re halting and slowing down the ability for AI and data centers to power themselves at unprecedented growth. We’re at here, 2, 3, 4, 5% depending on what, what iso you ask of, of electron need, and we’re the fastest way you could put electrons to the grid. Right now in the United States, it’s. Either one of those offshore wind farms is being built today, or one of the other offs, onshore wind farms or onshore solar facilities that are being built right now today. Those are the fastest ways to help the United States win the AI race, which is something that Trump has loud, left and right and center, but you’re actively like just hitting people in the shins with a baseball bat to to slow down. Energy growth. I, I just, it, it doesn’t make any logical sense. Allen Hall: And Rosemary just chime in here. We’ve had enough from the Americans complaining about it. Rosemary Barnes: Yeah. I mean, it’s hard for me to comment in too much detail about all of the [00:17:00] American security stuff. I mean, defense isn’t, isn’t one of my special interests and especially not American defense, but. When I talk about this issue with other Australians, it’s just sovereign risk is the, the issue. I mean, it was, it’s similar with the tariffs. It’s just like how, and it’s not just for like foreign companies that might want to invest in America. American companies are affected just, uh, as equally, but like you might be anti wind and fine. Um, but I don’t know how any. Company of any technology can have confidence to embark on a multi-year, um, project. Now, because you don’t know, like this government hates wind energy, but the next one could hate ai or the next one could hate solar panels, electric cars, or you know, just, just anything. And so like you just can’t. You just can’t trust, um, that your plans are gonna be able to be fulfilled even if you’ve got contracts, even if you’ve got [00:18:00] approvals, even if you are most of the way through building something, it’s not enough to feel safe anymore. And it’s just absolutely wild. That’s, and yeah, I was actually discussing with someone yesterday. How, and bearing in mind I don’t really understand American politics that deeply, but I’m gonna assume that Republicans are generally associated with being business friendly. So there must be so many long-term Republican donors who have businesses that have been harmed by all of these kinds of changes. And I just don’t understand how everyone is still behind this type of behavior. That’s what, that’s what I struggle to understand. Joel Saxum: This is the problem at the higher levels in. In DC their businesses are, are oil and gas based though. That’s the thing, the high, the high power conservative party side of things in the United States politics. The, the lobby money and the real money and the like, like think like the Dick Cheney era. Right. That was all Weatherford, right? It’s all oil and gas. Rosemary Barnes: So it’s not like anybody [00:19:00] cares about the, you know, I don’t know, like there’d be steel fabricators who have been massively affected by this. Right? Like that’s a good, a good traditional American business. Right. But are you saying it’s not big enough business that anyone would care that, that they’ve been screwed over? Joel Saxum: Not anymore Allen Hall: because all that’s being outsourced. The, the other argument, which Rosemary you touched upon is, is the one I’m seeing more recently on all kinds of social medias. It’s a bunch of foreign companies putting in these wind turbines. Well, who the hell Joel Saxum: is drilling your oil baby? This is something that I’ve always said. When you go go to Houston, Texas, the energy capital of the world, every one of those big companies, none of ’em are run by a Texan. They are all run by someone from overseas. Every one of ’em. Allen Hall: You, you think that, uh, you know, the Saudis are all, you know, great moral people. What the hell are you talking about? Are you starting to compare countries now? Because you really don’t wanna do that. If you wanna do that into the traditional energy marketplace, you’re, you’re gonna have [00:20:00] a lot of problems sleeping at night. You will, I would much rather trust a dane to put in a wind turbine or a German to put in a wind turbine than some of the people that are in, involved in oil and gas. Straight up. Straight up. Right. And we’ve known that for years. And we, we, we just play along, look. The fact of the matter is if you want to have electrons delivered quickly to the United States, you’re gonna have to do something, and that will be wind and solar because it is the fastest, cheapest way to get this stuff done. If you wanna try to plant some sort of gas pipeline from Louisiana up to Massachusetts or whatever the hell you wanna do, good luck. You know how many years you’re talking about here. In the meantime, all those people you, you think you care about are gonna be sitting there. With really high electricity rates and gas, gas, uh, rates, it’s just not gonna end well. Speaker 5: Australia’s wind farms are growing fast, but are your operations keeping up? Join us February 17th and [00:21:00] 18th at Melbourne’s Poolman on the park for Wind energy o and M Australia 2026, where you’ll connect with the experts solving real problems in maintenance asset management. And OEM relations. Walk away with practical strategies to cut costs and boost uptime that you can use the moment you’re back on site. Register now at W OM a 2020 six.com. Wind Energy o and m Australia is created by wind professionals for wind professionals because this industry needs solutions. Not speeches if Allen Hall: you don’t have enough on your plate already. Uh, the FCC has panned the import and sale of all new drone models from Chinese manufacturers, including the most popular of all in America, DJI, uh, and they clo. They currently hold about 70% of the global marketplace, the ban as DGI and Autel Robotics to the quote unquote covered list of entities deemed [00:22:00] a national security risk. Now here’s the catch. Existing models that are already approved for sale can still be purchased. So you can walk down to your local, uh, drone store and buy A DJI drone. And the ones you already own are totally fine, but the next generation. Not happening. They’re not gonna let ’em into the United States. So the wind industry heavily relies on drones. And, and Joel, you and I have seen a number of DJI, sort of handheld drones that are used on sites as sort of a quick check of the health of a, or status of a blade. Uh, you, you, I guess you will still be able to do that if you have an older dj. I. But if you try to buy a new one, good luck. Not gonna happen. Joel Saxum: Yeah. I think the most popular drone right now in the field, of course two of ’em, I would, I would say this, it’s like the Mavic type, you know, the little tiny one that like a site supervisor or a technician may have, they have their part 1 0 7 license. They can fly up and look at stuff. Uh, and then the [00:23:00] other one is gonna be the more industrial side. That’s gonna be the DJ IM 300. And that’s the one where a lot of these platforms, the perceptual robotics and some of the others have. That’s their base because the M 300 has, if you’re not in the, the development world, it has what’s called a pretty accessible SDK, which software development kit. So they’re designed to be able to add your sensors, put your software, and they’re fly ’em the way you want to. So they’re kind of like purpose built to be industrial drones. So if you have an M 300 or you’re using them now, what this I understand is you’re gonna still be able to do that, but when it comes time for next gen stuff, you’re not gonna be able to go buy the M 400. And import that. Like once it’s you’re here, you’re done. So I guess the way I would look at it is if I was an operator and that was part of our mo, or I was using a drone inspection provider, that that’s what comes on site. I would give people a plan. I would say basic to hedge your risk. I would say [00:24:00]basically like, Hey, if you’re my drone operator and I’m giving you a year to find a new solution. Um, that integrates into your workflows to get this thing outta here simply because I can’t be at risk that one day you show up, this thing crashes and I can’t get another one. A lot of companies are already like, they’re set and ready to go. Like all the new Skys specs, the Skys specs, foresight, drone, it’s all compliant, right? It’s USA made USA approved. Good to go. I think the new Arons drone is USA compliant. Good to go. Like, no, no issues there. So. Um, I think that some of the major players in the inspection world have already made their moves, um, to be able to be good USA compliant. Um, so just make sure you ask. I guess that’s, that. Our advice to operators here. Make sure you ask, make sure you’re on top of this one so you just don’t get caught with your pants down. Allen Hall: Yeah, I know there’s a lot of little drones in the back of pickup trucks around wind farms and you probably ought to check, talk to the guys about what’s going on to make sure that they’re all compliant. [00:25:00] In this quarter’s, PES Win magazine, which you can download for free@pswin.com. There is an article by Fran Hoffer, and they’re in Germany. If you don’t know who Fran Hoffer is, they’re sort of a research institution that is heavily involved in wind and fixing some of the problems, tackling some of the more complex, uh, issues that exist in blade repair. Turbine Repair Turbine Lifetime. And the article has a number of the highlights that they’ve been working on for the last several years, and you should really check this out, but looking at the accomplishments, Joel, it’s like, wow, fraud offer has been doing a lot behind the scenes and some of these technologies are, are really gonna be helpful in the near future. Joel Saxum: Yeah. Think of Frown Hoffer of your our US com compadres listening. Think of frown Hoffer as and NRE L, but. Not as connected to the federal government. Right. So, but, but more connected to [00:26:00] industry, I would say. So they’re solving industry problems directly. Right. Some of the people that they get funding research from is the OEMs, it’s other trade organizations within the group. They’re also going, they’re getting some support from the German federal government and the state governments. But also competitive research grants, so some EU DPR type stuff, um, and then some funding from private foundations and donors. But when you look at Frow, offerer, it’s a different project every time you talk to ’em. But, and what I like to see is the fact that these projects that they’re doing. Are actually solving real world problems. I, I, I, Alan and I talk about this regularly on the podcast is we have an issue with government funding or supportive funding or even grant funding or competitive funding going to in universities, institutions, well, whoever it may be, to develop stuff that’s either like already developed, doesn’t really have a commercial use, like, doesn’t forward the industry. But Frow Hoffer’s projects are right. So like one of the, they, they have [00:27:00] like the large bearing laboratory, so they’re test, they’ve tested over 500 pitch bearings over in Hamburg. They’re developing a handheld cure monitoring device that can basically tell you when resin has cured it, send you an email like you said, Alan, in case you’re like taking a nap on the ropes or something. Um, but you know, and they’re working on problems that are plaguing the industry, like, uh, up working on up towel repairs for carbon fiber, spar caps. Huge issue in the industry. Wildly expensive issue. Normally RA blade’s being taken down to the ground to fix these now. So they’re working on some UPT tile repairs for that. So they’re doing stuff that really is forwarding the industry and I love to see that. Allen Hall: Yeah. It’s one of the resources that. We in the United States don’t really take advantage of all the time. And yeah, and there’s a lot of the issues that we see around the world that if you were able to call f Hoffer, you should think about calling them, uh, and get their opinion on it. They probably have a solution or have heard of the problem before and can direct you to, uh, uh, a reasonable outcome. [00:28:00] That’s what these organizations are for. There’s a couple of ’em around the world. DTU being another one, frow Hoffer, obviously, uh, being another powerhouse there. That’s how the industry moves forward. It, it doesn’t move forward when all of us are struggling to get through these things. We need to have a couple of focal points in the industry that can spend some research time on problems that matter. And, and Joel, I, I think that’s really the key here. Like you mentioned it, just focusing on problems that we are having today and get through them so we can make the industry. Just a little bit better. So you should check out PES WIN Magazine. You can read this article and a number of other great articles. Go to ps win.com and download your articles today. That wraps up another episode of the Uptime Wind Energy Podcast. Thanks for joining us and we appreciate all the feedback and support we receive from the wind industry. If today’s discussion sparked any question or ideas, we’d love to hear from you. Just reach out to us on LinkedIn and please don’t forget to subscribe so you [00:29:00] never miss an episode For Joel, Rosemary and Yolanda, I’m a hall. We’ll catch you next week on the Uptime Wind Energy Podcast.

Learn how to host secure and scalable remote MCP servers on Azure Functions! Hosting MCP servers remotely allows others to access tools in your servers, not just agents running on your local machine. Azure Functions provides remote hosting for two flavors of MCP servers - those built with the Functions MCP extension or with the official MCP SDKs. In this week's Azure Friday, Lily talks about how to host the SDK flavor with Scott. Check it out if you're looking to build or have already built some servers with these SDKs and are looking for a place to remotely host them! Chapters 00:00 - Introduction 02:51 - Server project walk through 06:12 - Server deployment 07:01 - Test server in Copilot 13:56 - Questions from Scott 16:44 - Sample links and wrap up Recommended resources Learn Docs Azure Product page Azure free trial Connect Scott Hanselman | @SHanselman Azure Friday | Twitter/X: @AzureFriday Azure | Twitter/X: @Azure

Learn how to host secure and scalable remote MCP servers on Azure Functions! Hosting MCP servers remotely allows others to access tools in your servers, not just agents running on your local machine. Azure Functions provides remote hosting for two flavors of MCP servers - those built with the Functions MCP extension or with the official MCP SDKs. In this week's Azure Friday, Lily talks about how to host the SDK flavor with Scott. Check it out if you're looking to build or have already built some servers with these SDKs and are looking for a place to remotely host them! Chapters 00:00 - Introduction 02:51 - Server project walk through 06:12 - Server deployment 07:01 - Test server in Copilot 13:56 - Questions from Scott 16:44 - Sample links and wrap up Recommended resources Learn Docs Azure Product page Azure free trial Connect Scott Hanselman | @SHanselman Azure Friday | Twitter/X: @AzureFriday Azure | Twitter/X: @Azure

Learn how to host secure and scalable remote MCP servers on Azure Functions! Hosting MCP servers remotely allows others to access tools in your servers, not just agents running on your local machine. Azure Functions provides remote hosting for two flavors of MCP servers - those built with the Functions MCP extension or with the official MCP SDKs. In this week's Azure Friday, Lily talks about how to host the SDK flavor with Scott. Check it out if you're looking to build or have already built some servers with these SDKs and are looking for a place to remotely host them! Chapters 00:00 - Introduction 02:51 - Server project walk through 06:12 - Server deployment 07:01 - Test server in Copilot 13:56 - Questions from Scott 16:44 - Sample links and wrap up Recommended resources Learn Docs Azure Product page Azure free trial Connect Scott Hanselman | @SHanselman Azure Friday | Twitter/X: @AzureFriday Azure | Twitter/X: @Azure

Learn how to host secure and scalable remote MCP servers on Azure Functions! Hosting MCP servers remotely allows others to access tools in your servers, not just agents running on your local machine. Azure Functions provides remote hosting for two flavors of MCP servers - those built with the Functions MCP extension or with the official MCP SDKs. In this week's Azure Friday, Lily talks about how to host the SDK flavor with Scott. Check it out if you're looking to build or have already built some servers with these SDKs and are looking for a place to remotely host them! Chapters 00:00 - Introduction 02:51 - Server project walk through 06:12 - Server deployment 07:01 - Test server in Copilot 13:56 - Questions from Scott 16:44 - Sample links and wrap up Recommended resources Learn Docs Azure Product page Azure free trial Connect Scott Hanselman | @SHanselman Azure Friday | Twitter/X: @AzureFriday Azure | Twitter/X: @Azure

Ari Paparo and Eric Franchi sit down with MoPub and MAX founder Jim Payne to unpack his new company CloudX, how “monetization as code” lets mobile publishers manage their entire ad stack in files that AI can edit, why he teamed up with Meta on a secure auction using trusted execution environments, and what all of this means for SDK complexity, mobile vs desktop, AppLovin, performance TV, retail media, and the next wave of ad tech. Takeaways CloudX lets mobile publishers manage their ad stack as code. Jim built CloudX with Meta to power a more secure mobile auction. Line items and targeting live in files instead of spreadsheets. Trusted execution environments keep bidder data locked down. AI agents can now traffic ads and tweak setups automatically. Jim looks back on Mopub, Max and big outcomes for early teams. The crew also breaks down Pinterest TV Scientific and other ad tech news. Chapters 00:00 Intro and why Jim finally joins. 02:10 Jim's path through Mopub, Max and Meta. 06:00 What monetization as code actually means. 11:30 How AI agents can traffic ads. 15:00 Secure auctions and why Meta cares. 20:30 Why messy mobile stacks need flexibility. 27:00 Jim on AppLovin and mobile versus desktop. 33:30 Jim Payne legends and big career bets. 44:00 Pinterest buys tvScientific news reaction. 52:00 DSP fees, CTV buying and meta layers. Learn more about your ad choices. Visit megaphone.fm/adchoices

Show DescriptionChris and Jessica from Studioworks join us to talk about their new app, why they're uniquely qualified to run an invoicing app, what the long term vision is for Studioworks, pricing models of subscription apps, how invoicing isn't just for web nerds anymore, helping neurospicy people get paid for their work, and what it's like to transfer to a new invoicing app. Listen on WebsiteWatch on YouTubeGuestsJessica HischeGuest's Main URL • Guest's SocialJessica Hische is a lettering artist and author with a tendency to overshare and a penchant for procrastiworking. Chris ShiflettGuest's Main URL • Guest's SocialChris Shiflett is a husband, father, entrepreneur, community leader, author, speaker, and amateur athlete. Links Studioworks.app The web's grain by Frank Chimero SponsorstldrawHave you ever wanted to build an app that works kinda like Miro or Figma, that has a zoomable infinite canvas, that's multiplayer, and really good, but you also want to build it in React with normal React components on the canvas? Good news! tldraw is the world's first, best, and only SDK for building infinite canvas apps in React. tldraw takes care of all the canvas complexities — things like the camera, selection logic, and undo redo — so that you can focus on building the features that matter to your users. It's easy to use with plenty of examples and starter kits, including a kit where you can use AI to create things on the canvas. Get started for free at tldraw.dev/shoptalk, or run npm create tldraw to spin up a starter kit.

In this episode, we are joined by Michael Gants, founder and CEO of Encore, a new SDK helping subscription app developers turn churned users into paying subscribers.Michael is a Stanford grad, a Time Magazine “Leader of Tomorrow”, and a seasoned founder with a passion for building sustainable consumer businesses.He will also share what he's learned about monetizing consumer apps, understanding user psychology, and how Encore's technology is rethinking app revenue models.You will discover:✅ How developers can turn churned users into paying subscribers✅ The psychology of user retention and what triggers reactivation✅ Why traditional monetization models are broken for consumer apps✅ How Encore's SDK simplifies subscription monetizationLearn More:Explore Encorehttps://encorekit.com/You can also watch this video here: https://www.youtube.com/live/F_FYZUgGjNYWant expert guidance to grow your app? Book a quick call with App Masters:https://appmasters.com/contact-us/Get training, coaching, and community: https://appmasters.com/academy/*********************************************SPONSORSGot tons of freemium users who won't upgrade? Encore turns free users into paying customers and reduces churn by adding smart, curated affiliate offers at key user moments. Everyone wins with Encore.Learn more at https://encorekit.com/*********************************************Launch a high-performing branded Web Shop in minutes—or build a fully custom storefront without the hassle.Xsolla's modular solution reduces platform fees, supports 1,000+ global payment methods, and ships with built-in LiveOps and customization tools—so every purchase puts more revenue back in your studio's pocket.Check out now: https://tinyurl.com/43hda5tf*********************************************Follow us:YouTube: ⁠AppMasters.com/YouTube⁠Instagram: ⁠@App MastersTwitter: ⁠@App MastersTikTok: ⁠@stevepyoung⁠Facebook: ⁠App Masters⁠*********************************************

In this episode of The Digital Executive, Brian Thomas interviews Ashish Aggarwal, Co-Founder of AppBroda—a no-code ad network empowering mobile app and game developers to scale revenue without writing a single line of code. Drawing on his experience at Google working with thousands of developers, Ashish explains the industry's biggest friction point: developers don't want additional SDKs or code that slow apps, risk crashes, or violate privacy rules.Ashish shares how AppBroda solves that challenge with automated, data-driven monetization tools now used by over 2,000 studios, contributing to more than $2B in annual recurring revenue. He breaks down what separates consistently successful studios—data-driven systems, adaptability, and access to capital—and how privacy shifts and platform policies have reshaped mobile ad economics.Looking ahead, Ashish predicts a new era where AI enables anyone to become an app or game creator. He explains how no-code platforms like AppBroda will power this next wave of digital entrepreneurs by simplifying monetization for non-technical builders. This conversation is a must-listen for developers, creators, and anyone following the future of mobile apps.If you liked what you heard today, please leave us a review - Apple or Spotify. See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

For episode 646 of the BlockHash Podcast, host Brandon Zemp is joined by Rodney Prescott, CEO of ENTRY.Rodney is a seasoned founder and product architect in compliance-native Web3 infrastructure, with deep experience bridging institutional standards with decentralized finance. He leads ENTRY, a next-generation compliance layer for DeFi that brings real-world regulatory readiness on-chain through zero-knowledge proofs, automated risk controls, and verifiable identity frameworks. Under Rodney's leadership, ENTRY has evolved from a stealth zero-knowledge research lab into a fully structured ecosystem spanning the ENTRY Foundation (open protocol, token, standards) and Zekret Labs (AI-driven compliance engine and institutional SDKs). ⏳ Timestamps: (0:00) Introduction(0:53) Who is Rodney Prescott?(3:37) What is ENTRY?(5:00) What are the problems with compliance today?(8:53) How to build compliance into DeFi(10:53) How does on-chain screening work?(15:36) Federated AI(19:24) Use-cases(22:46) ENTRY roadmap for 2026 

Most software teams still think of payments as a chore. We take you inside the playbook that turns it into a growth engine. I sits down with NMI CTO Phillip Goericke to unpack how embedded payments evolved from a basic checkout to a full-stack platform that handles onboarding, underwriting, payouts, analytics, and even embedded finance. The conversation is straight talk on what actually works when you're shipping fast and scaling globally.We dig into the architectural choices that matter: start with a no-code drop-in to activate revenue quickly, then progress to low-code SDKs and finally full APIs when you need deep control. Phillip shares where platforms stall - manual KYC, fragmented global rules, and data blind spots and how a modular approach fixes these without ripping out your stack. You'll hear how compliance-as-a-service, network tokenization, and adaptive 3D Secure can raise approval rates, reduce fraud, and simplify audits while keeping the checkout experience seamless.Looking ahead, we explore why identity, compliance, and data are the foundation for embedded finance. Philip outlines NMI's unified experience that brings payments, onboarding, insights, and new services like business capital into one place. We also tackle AI with clear eyes: use it to augment decisioning and anomaly detection, but wrap it with deterministic controls so money-critical outcomes are consistently right. The key takeaway is a mindset shift: stop treating payments as a feature and start using it as a strategic lever for revenue, retention, and product velocity.If you're building software with transactions anywhere in the flow, this is your blueprint for turning payments into a competitive moat. Subscribe for more deep dives, share with a teammate who owns monetization, and leave a review to tell us what topic you want next.

Show DescriptionWhy do we turkey when there's so many (better) options for meals, how many hobbies do we really need and why can't we do all of them, Clues by Sam difficulties and doing the puzzle game circuit, does Dave like D&D or does Dave like systems, the ongoing web monetization attempts, and Brecht on range group. Listen on WebsiteLinks Alton Brown Cooks Food | Episode 1: The Big Bird Big Green Egg Tobi Workwear Clues By Sam Stars – Daily Puzzle | Inkwell Games Fields – Daily Puzzle | Inkwell Games Tiled Words 646: Hard Code & Soft Skills – ShopTalk Lasers & Feelings by John Harper Greetings, Scoundrel | Blades in the Dark RPG Monster of the Week – Evil Hat Mothership RPG – Tuesday Knight Games Pathfinder Roleplaying Game | Paizo Baldur's Gate 3 on Steam 633: Thomas Steiner on AI in Chrome and the Web – ShopTalk Web Monetization is Still Inching Along – Frontend Masters Blog Open Letter Interledger Foundation Web Monetization – Chrome Web Store GateHub Grid Paper utilitybend Blog SponsorstldrawHave you ever wanted to build an app that works kinda like Miro or Figma, that has a zoomable infinite canvas, that's multiplayer, and really good, but you also want to build it in React with normal React components on the canvas? Good news! tldraw is the world's first, best, and only SDK for building infinite canvas apps in React. tldraw takes care of all the canvas complexities — things like the camera, selection logic, and undo redo — so that you can focus on building the features that matter to your users. It's easy to use with plenty of examples and starter kits, including a kit where you can use AI to create things on the canvas. Get started for free at tldraw.dev/shoptalk, or run npm create tldraw to spin up a starter kit.

Jeanne DeWitt Grosser built world-class GTM teams at Stripe, Google, and, most recently, Vercel, where she serves as COO and oversees marketing, sales, customer success, revenue operations, and field engineering. She transformed Stripe's early sales organization from the ground up and advises founders on GTM strategy.We discuss:1. Why GTM is becoming more strategically important in the AI era2. The rise of the GTM engineer3. A primer on segmentation4. How to build a sales org that engineers and product teams respect5. The changing calculus of build vs. buy for go-to-market tools in the AI era6. Why most customers buy to avoid pain rather than to gain upside—Brought to you by:Datadog—Now home to Eppo, the leading experimentation and feature flagging platform: https://www.datadoghq.com/lennyLovable—Build apps by simply chatting with AI: https://lovable.dev/Stripe—Helping companies of all sizes grow revenue: https://stripe.com/—Transcript: https://www.lennysnewsletter.com/p/what-the-best-gtm-teams-do-differently—My biggest takeaways (for paid newsletter subscribers): https://www.lennysnewsletter.com/i/179503137/my-biggest-takeaways-from-this-conversation—Where to find Jeanne DeWitt Grosser:• X: https://x.com/jdewitt29• LinkedIn: https://www.linkedin.com/in/jeannedewitt—Where to find Lenny:• Newsletter: https://www.lennysnewsletter.com• X: https://twitter.com/lennysan• LinkedIn: https://www.linkedin.com/in/lennyrachitsky/—In this episode, we cover:(00:00) Introduction to Jeanne DeWitt Grosser(05:26) Defining go-to-market(08:43) The evolution of go-to-market roles(11:23) The rise of the go-to-market engineer(14:21) Implementing AI in sales processes(15:28) Optimizing sales with AI agents(23:47) Defining sales roles: SDRs and AEs(26:04) When to hire a GTM engineer(29:04) Hiring and scaling sales teams(30:50) The ideal go-to-market engineer(34:24) The go-to-market tool stack(40:39) Advice on building a great sales bot(44:34) Vercel's unfair advantage(46:37) Go-to-market as a product(47:04) Innovative sales tactics at Stripe(52:38) Effective go-to-market tactics(01:00:37) Segmentation strategies(01:09:31) Building a sales org that engineers love(01:14:00) Thoughts on PLG and pricing(01:16:44) Sales compensation and hiring(01:19:24) Lightning round and final thoughts—Referenced:• Vercel: https://vercel.com• Stripe: https://stripe.com• Rosalind Franklin: https://en.wikipedia.org/wiki/Rosalind_Franklin• Ben Salzman on LinkedIn: https://www.linkedin.com/in/bensalzman• SDK: https://ai-sdk.dev/docs/introduction• Gong: https://www.gong.io• Lyft: https://www.lyft.com• Instacart: https://www.instacart.com• DoorDash: https://www.instacart.com• “Sell the alpha, not the feature”: The enterprise sales playbook for $1M to $10M ARR | Jen Abel: https://www.lennysnewsletter.com/p/the-enterprise-sales-playbook-1m-to-10m-arr• A step-by-step guide to crafting a sales pitch that wins | April Dunford (author of Obviously Awesome and Sales Pitch): https://www.lennysnewsletter.com/p/a-step-by-step-guide-to-crafting• Kate Jensen on LinkedIn: https://www.linkedin.com/in/kateearle• Lessons from scaling Stripe | Claire Hughes Johnson (former COO of Stripe): https://www.lennysnewsletter.com/p/lessons-from-scaling-stripe-tactics• Atlassian: atlassian.com—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com.—Lenny may be an investor in the companies discussed. To hear more, visit www.lennysnewsletter.com

Show DescriptionDave has famous people blindness, a cologne life hack is dropped, what is the killer feature of web components, MCPs are so done—focus on skills instead, should custom events exist, and thoughts about streaming HMTL. Listen on WebsiteWatch on YouTubeLinks Good Hang With Amy Poehler - The Ringer Sebastian Maniscalco Has a Little More Pepper in His Hair These Days - The Ringer Guitar Center Austin Music Store normansrareguitars.com – Norman's Rare Guitars The killer feature of Web Components - daverupert.com figma/code-connect: A tool for connecting your design system components in code with your design system in Figma Chrome DevTools (MCP) for your AI agent | Blog | Chrome for Developers Stop Using CustomEvent SponsorstldrawHave you ever wanted to build an app that works kinda like Miro or Figma, that has a zoomable infinite canvas, that's multiplayer, and really good, but you also want to build it in React with normal React components on the canvas? Good news! tldraw is the world's first, best, and only SDK for building infinite canvas apps in React. tldraw takes care of all the canvas complexities — things like the camera, selection logic, and undo redo — so that you can focus on building the features that matter to your users. It's easy to use with plenty of examples and starter kits, including a kit where you can use AI to create things on the canvas. Get started for free at tldraw.dev/shoptalk, or run npm create tldraw to spin up a starter kit.

What if paying with crypto felt as effortless as tapping your card? We sit down with Jess Houlgrave, CEO of WalletConnect, to unpack how stablecoins, smarter wallet-to-app messaging, and a new wave of SDKs are collapsing the gap between crypto checkout and the one-click experiences consumers expect.Jess traces her path from investment banking to early Bitcoin research to leading a network that connects 700 wallets to 70,000 applications and moves hundreds of billions in value. We dig into the real merchant story: slashing fees from the typical 2–3% card rates to basis points, settling in seconds instead of days, and opening doors in markets where stablecoins are already everyday money. The caveat has always been clunky UX - QR codes, chain selection, gas fees - but that's changing fast as partners like Coinbase Commerce, Mesh, and Privy streamline onboarding and data sharing.We explore two frontiers set to unlock the next wave of growth. First, in-store payments, where WalletConnect's new POS SDK aims to meet the speed and reliability of retail environments and is already rolling out with partners in Asia. Second, recurring payments, where crypto's push model needs safer, revocable permissions to mirror subscriptions without sacrificing user control. Along the way, we zoom out to embedded finance, where neobanks become financial hubs offering custody, trading, and wealth tools, and to data privacy, where wallets enable selective disclosure so users share only what's needed for shipping, KYC, or age checks.Enjoy the conversation, and if it sparks ideas, subscribe, share this episode with a colleague, and leave a quick review to help others find the show.

This week, our hosts ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Dave Bittner⁠⁠⁠⁠⁠⁠⁠⁠, ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Joe Carrigan⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠, and ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Maria Varmazis⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ (also host of the ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠T-Minus⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Space Daily show) are sharing the latest in social engineering scams, phishing schemes, and criminal exploits that are making headlines. We start with some follow up on China sentencing five members of a violent Kokang-based gang to death for running brutal scam compounds in Myanmar. And in related news, China has also extradited alleged scam kingpin She Zhijiang, a major figure behind one of Southeast Asia's largest fraud hubs, as Beijing intensifies its crackdown on global cyber-fraud networks. Listener Jon reports a new twist on sextortion, where scammers used an unsolicited FaceTime call to capture an image, generate an AI-manipulated obscene photo, and then extort an employee using publicly scraped contact lists. Joe's story is on Anthropic's claim that attackers jailbroke its Claude model to carry out what it calls the first AI-orchestrated cyber-espionage campaign, a narrative now being challenged by researchers like Dan Goodin and Dan Tentler, who argue the attack was far less “autonomous” than advertised and comparable to long-standing hacking tools rather than a breakthrough in offensive AI. Dave's story is on a new phishing scam where attackers use the contact info displayed on a lost iPhone's lock screen to send fake “Find My” texts claiming the device was found, luring victims to a spoofed Apple login page to steal their Apple ID and bypass Activation Lock. Maria has the story on Zimperium's Mobile Shopping Report, which shows that during the holiday season mobile threats surge across mishing, fake retail and payment apps, and app-level vulnerabilities—making this the peak time for scammers to exploit shoppers with spoofed texts, malicious apps, and insecure SDKs hidden inside legitimate shopping tools. Our catch of the day comes from the phishing subreddit as someone is impersonating a woman who is sick with cancer asking for the victim to take care of their money. Resources and links to stories: ⁠⁠⁠⁠China sentences 5 to death for building, running criminal gang fraud centers in Myanmar's lawless borderlands Man Accused of Running Southeast Asia Scam Compound Is Extradited to China Disrupting the first reported AI-orchestrated cyber espionage campaign Researchers question Anthropic claim that AI-assisted attack was 90% autonomous Lost iPhone? Don't fall for phishing texts saying it was found ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Have a Catch of the Day you'd like to share? Email it to us at ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠hackinghumans@n2k.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠.

Show DescriptionWhat do Balatro streamers do when the game is over, Random in CSS is so hot right now, Dave has a better idea for charts and graphs that would change the world, Quiet UI follow up, Dave tries vibe coding a tennis app and doesn't completely John McEnroe his laptop, Chris wonders about better cursor UI on the web, and debating affordances vs conventions. Listen on WebsiteWatch on YouTubeLinks Jynxzi - Twitch BALL x PIT on Steam Could Open Graph Just Be a CSS Media Type? | Scott Jehl, Web Designer/Developer https://webawesome.com Podcast Awesome Quiet UI A Beautiful Site Eleventy is a simpler static site generator Don't use custom CSS mouse cursors – Eric Bailey Home | Rach Smith's digital garden The Two Button Problem – Frontend Masters Blog SponsorstldrawHave you ever wanted to build an app that works kinda like Miro or Figma, that has a zoomable infinite canvas, that's multiplayer, and really good, but you also want to build it in React with normal React components on the canvas? Good news! tldraw is the world's first, best, and only SDK for building infinite canvas apps in React. tldraw takes care of all the canvas complexities — things like the camera, selection logic, and undo redo — so that you can focus on building the features that matter to your users. It's easy to use with plenty of examples and starter kits, including a kit where you can use AI to create things on the canvas. Get started for free at tldraw.dev/shoptalk, or run npm create tldraw to spin up a starter kit.

Show DescriptionSteve Ruiz talks about what tldraw is and who it's for, how they've dealt with data on all the computers, what's new in the tldraw SDK, ideas for building on top of tldraw, tldraw's business model, and what the future holds for tldraw the company. Listen on WebsiteWatch on YouTubeGuestsSteve RuizGuest's Main URL • Guest's SocialA developer, designer, and now startup founder in London. I build lots of prototypes. Sometimes those prototypes turn into products. Links tldraw • very good free whiteboard tldraw computer makereal Docs • tldraw tldraw - Visual Studio Marketplace Globs Designer ClickUp | The everything app for work Steve Ruiz steveruizok (Steve Ruiz) tldraw (@tldraw) / X

Ready to integrate build automation into your applications? Carl and Richard talk to Mattias Karlsson about the new Cake.SDK as an additional component of the Cake (C# Make) open source project. Mattias talks about integrating the Cake scripting experience into your .NET console applications. The conversation digs into speeding up the building of infrastructure for testing and pre-production environments so that you can get features shipped quickly!