Podcasts about Java

Links For The Occult Rejectshttps://linktr.ee/theoccultrejectsOccult Research Institutehttps://www.occultresearchinstitute.org/Substackhttps://substack.com/@theoccultrejects?r=7auau0&utm_campaign=profile&utm_medium=profile-pageCash Apphttps://cash.app/$theoccultrejectsVenmo@TheOccultRejectsBuy Me A Coffeebuymeacoffee.com/TheOccultRejectsPatreonhttps://www.patreon.com/TheOccultRejectsBibliographyAguilar, L. A., et al. “Total Solar Eclipse Triggers Dawn Behavior in Birds.” Science, 2025. Used for the updated science support showing that the April 8, 2024 total eclipse altered North American bird behavior, including dawn-like vocal responses.Britannica. “9 Celestial Omens.” Used for the Thales / Battle of the Eclipse tradition and the broader theme of celestial events being interpreted as historical omens.Britannica. “Apopis.” Used for Apep/Apopis as the serpent enemy of Re/Ra, the demon of chaos, and the force outside the ordered cosmos.Britannica. “Eclipse — Medieval European.” Used for medieval eclipse records, especially the 733 CE annular eclipse described as a “black and horrid shield.”Britannica. “Hindu Calendar.” Used for Hindu sacred timing, lunar-solar calendrical structure, and the religious context that helps explain eclipse observance as ritually serious time.Britannica. “Ma'at.” Used for Ma'at as truth, justice, balance, and cosmic order in ancient Egyptian religion.Britannica. “Navagraha.” Used for Rahu and Ketu as eclipse-associated shadow planets and lunar-node powers in Indian astral religion.Britannica. “Samudra Manthana / Churning of the Ocean of Milk.” Used for the mythic background of devas, asuras, amrita, Vishnu, Mohini, Rahu, and Ketu.Britannica. “Solar Eclipse.” Used for basic solar-eclipse definition and the Moon's shadow crossing Earth.Britannica. “The Sun Was Eaten: 6 Ways Cultures Have Explained Eclipses.” Used for comparative eclipse mythology, especially devourer myths, Chinese dragon traditions, Rahu, and Batammaliba reconciliation themes.Britannica. “What Causes Lunar and Solar Eclipses?” Used for clear basic mechanics of lunar and solar eclipses.CDLI / Cuneiform Digital Library Initiative. “Solar Omens of Enūma Anu Enlil: Tablets 23 (24)–29 (30).” Used for bibliographic information on van Soldt's edition of the solar omen tablets.European Space Agency. “27 August.” Used for the 413 BCE lunar eclipse during the Athenian retreat from Syracuse and Nicias' delay.Exploratorium. “Eclipse Stories from Around the World.” Used for global comparative eclipse stories, including Norse wolves, Batammaliba reconciliation, and other recurring mythic patterns.Foundation for the Preservation of the Mahayana Tradition. “Practice During Solar and Lunar Eclipses.” Used for Tibetan Buddhist practice advice, merit multiplication, and eclipse as intensified sacred time.Izzuddin, Ahmad, Mohamad A. Imroni, Ali Imron, and Mahsun. “Cultural Myth of Eclipse in a Central Javanese Village: Between Islamic Identity and Local Tradition.” HTS Teologiese Studies/Theological Studies, 2022. Used for Batara Kala, eclipse devouring myths in Java, pregnancy/livestock concerns, and living village practice.NASA. “Why Do Eclipses Happen?” NASA Science. Used for solar and lunar eclipse geometry, alignment, lunar nodes, and the reason eclipses do not occur every month.NASA Space Place. “Lunar Eclipses and Solar Eclipses.” Used for simple public-facing explanations of solar and lunar eclipse mechanics.National Folk Museum of Korea. “Solar and Lunar Eclipse / Ilsik, Wolsik.” Used for Bulgae, the Korean fire dogs from the Dark World who cause eclipses by biting the Sun and Moon.NOAA NESDIS. “NOAA Satellites View Total Solar Eclipse.” Used for environmental effects during totality, including temperature drops, changes in local air circulation, cloud behavior, and animal confusion.Rochester, University of. “Surprising Facts and Beliefs About Eclipses During Medieval and Renaissance Times.” Used for the point that medieval astronomers understood eclipse prediction while still interpreting eclipses as morally or religiously serious.Sefaria. Sukkah 29a. Used for rabbinic material treating eclipses as ominous signs.Sunnah.com. Sahih al-Bukhari, Book 16, “Eclipses.” Used for the hadith that the Sun and Moon do not eclipse because of the life or death of any person and that the correct response is prayer and invocation.The Metropolitan Museum of Art. “The Solar Eclipse and the Substitute King.” Used for Mesopotamian eclipse omens, danger to the king, priestly divination, substitute kingship, and the šar pūḫi ritual.U.S. Fish & Wildlife Service. “Wildlife Behavior and a Solar Eclipse.” Used for darkening skies, cooling temperatures, and wildlife shifting toward nighttime routines.University of Pittsburgh World History Center. Lilly Taylor, “Solar Eclipses and World History.” Used for the Batammaliba tradition of making peace and ending disputes during eclipse.van Soldt, Wilfred H. Solar Omens of Enūma Anu Enlil: Tablets 23 (24)–29 (30). Leiden: Nederlands Historisch-Archaeologisch Instituut te Istanbul, 1995. Used for Mesopotamian solar omen literature and the textual archive of unusual solar phenomena.This keeps Part 1 sourced without dragging Part 2's Mesoamerica, Andes, North American Indigenous, Australian, Arctic, Pacific, colonial, and modern eclipse-pilgrimage sources into the wrong half.Also want to remind people about the website, if you're into reading we have tons of information by multiple contributors, and we got t-shirts up on the site if you're interested. Fun fact, the art is all based on the eyeball. A

Suffering. Grief. Disappointment. Loss. Any one of these can shake us to our core. So how are we supposed to trust God when everything seems to go wrong? On this episode, Anne Graham Lotz (daughter of Billy Graham) and her daughter, Rachel-Ruth Lotz Wright, walk through the story of Joseph—a man who experienced betrayal, false accusation, and unfair circumstances that turned his life upside down. So how did Joseph remain steadfast in his faith? Anne and Rachel-Ruth explain how God's presence brings peace even in life's deepest pits. You'll discover why suffering is never wasted and how God uses even our hardest seasons to guide us, grow us, and bring about His greater purpose. SHOW NOTES: 413Podcast.com/408  Read the episode TRANSCRIPT in the show notes. Get my weekly email, Java with Jennifer, to be notified when a new podcast episode releases. Subscribe HERE.

Përzgjedhur nga Dee Jay-it e Top Albania Radios, mbrëmja e të dielës është e gjitha për t'u shijiuar. Java mbyllet me muzikë të mirë dhe përzgjidhet nga DJ resident të Top Albania Radio.

Përzgjedhur nga Dee Jay-it e Top Albania Radios, mbrëmja e të dielës është e gjitha për t'u shijiuar. Java mbyllet me muzikë të mirë dhe përzgjidhet nga DJ resident të Top Albania Radio.

Përzgjedhur nga Dee Jay-it e Top Albania Radios, mbrëmja e të dielës është e gjitha për t'u shijiuar. Java mbyllet me muzikë të mirë dhe përzgjidhet nga DJ resident të Top Albania Radio.

Përzgjedhur nga Dee Jay-it e Top Albania Radios, mbrëmja e të dielës është e gjitha për t'u shijiuar. Java mbyllet me muzikë të mirë dhe përzgjidhet nga DJ resident të Top Albania Radio.

Dopey Recovery Short Film Festival https://buytickets.at/thedopeyfoundation/2216905 Patreon - www.patreon.com/dopeypodcast   Summary   This week on the Dopey replay, Dave opens the show melting in a ninety-degree attic after removing his ugly window air conditioners and battling his third malfunctioning Rodecaster. He spirals through equipment frustration, a failed attempt to recruit an actress from The Pitt, and his anxiety about banking ten episodes before vacation, before reminding himself that gratitude and acceptance are the answer.   Dave promotes the June 26th Dopey Film Festival and reads heartfelt emails from listeners who discovered Dopey after Chris's death and have been listening from the beginning. He reflects on the murder of Dopey legend DJ Don, discussing the tragic circumstances surrounding his death and how loss remains an unavoidable part of making a podcast about addiction.   The replay itself features classic chemistry between Dave and Chris with special guest "Vinny," an old friend and longtime stoner. The episode wanders hilariously through stand-up comedy, Leonardo DiCaprio encounters, Perrier pronunciation debates, and Chris's legendary stories before landing on the centerpiece: Vinny's unbelievable Amsterdam LSD tale.   While studying abroad, Vinny and a group of fellow Americans drop acid in Amsterdam. One of them, "Tok," completely loses his mind, strips naked in a coffee shop, searches for his dog "Java," swings at strangers, gets whipped by two random guys carrying sex whips, and ultimately ends up handcuffed and sleeping it off in a Dutch jail. By morning, Tok remembers absolutely nothing.   The replay closes with stories about Dave bombing at open mic comedy, Chris reliving disgusting drunk escapades, and the timeless chemistry that made early Dopey such a cult classic.   Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

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

The Technos have been defeated but the city is not out of danger yet. ZOOT as returned and is stalking both the streets and EBONY's nightmares. MEGA and JAVA conspire, while rogue Technos kidnap SALENE, demanding RAM as ransom. But where has he disappeared to?

Your Java AI application is live in production. But have you tested whether it can be jailbroken, manipulated into revealing its system prompt, or tricked into printing content it should never output?In this episode, Iryna Dohndorf, Software Engineer at Karakun Group and creator of Tiberius, explains how to bring security testing to LLM-powered Java applications. We cover why traditional unit tests break down with non-deterministic systems, how the Scan-Fixture-Validate workflow works, what buff mutation testing is, and why even well-trained models can be cracked with something as simple as the grandmother attack.Topics include:Why LLM non-determinism breaks the classic input/output test modelThe Scan-Fixture-Validate principle and sharing test artifacts across teamsPrompt injection, jailbreaks, and emotional manipulation attacksBuff mutation: testing linguistic surface coverageProbabilistic security contracts and multi-trial scansFingerprinting and why your model choice should not be detectableLLM as a judge: using a second model as a guardrailGetting started with Tiberius in Spring Boot and LangChain4jGuestIryna Dohndorf - Software Engineer at Karakun GroupLinkedInLinksArticle on FoojayTiberius on GitHubSecurity Testing GuideTimestamps00:00 Introduction of topic and guest01:05 The problem Tiberius wants to solve06:39 How "traditional" unit tests don't work for LLM integrations10:23 Scan-Fixture-Validate principle and sharing artifacts15:15 Using different skills, for example, the grandmother skill17:33 Testing for required versus forbidden bias19:35 The probes across nine attack categories used by Tiberius20:44 Buff mutation testing26:55 Using Tiberius in your pipelines and when to fail29:35 Using multi-trial scans31:14 Fingerprinting: which model you use, should not be detectable32:55 Combining multiple models, model as a judge34:41 Sharing JSON models to improve tests36:05 How to get started with Tiberius in Spring and with LangChain4j36:41 Quarkus not supported yet, plans for the future39:07 Conclusions and a call out to everyone to become a Foojay author

Our souls long for less of us and more of God. For less of this broken world and more of Jesus' abundant life. Put simply… for revival.  So in this episode, author and podcaster Lisa Whittle shares the freedom that comes from surrendering to God—releasing your need for comfort, control, approval, and even blessings. You'll see how offering everything to God brings the renewed spiritual vitality we all crave. Because often, it's the very things we see as good that slowly pull our hearts away from God and lead to spiritual drift. So if you've started to sense that drift—or you already feel far off course—listen in. This conversation will help you identify what may be standing in the way of the soul revival you've been longing for. SHOW NOTES: 413Podcast.com/407  Read the episode TRANSCRIPT in the show notes. Get my weekly email, Java with Jennifer, to be notified when a new podcast episode releases. Subscribe HERE.

Welcome, Massimo Banzi of SuperModerno and co-founder of Arduino Introduction and SuperModerno: Massimo introduces himself as a “friendly nerd” and discusses his new project, SuperModerno The project aims to explain the “behind the scenes” of technology to prevent people from becoming “slaves to the platform” The History of Technology: Massimo expresses his passion for technology’s history, emphasizing non-American innovators to show Europeans they can also lead in technology, citing the UK-based origins of the Arm processor The Legacy of Olivetti: He highlights Olivetti (founded in 1908), which moved from typewriters to creating the Programma 101, the first desktop computer used by NASA to compute orbits for the Apollo program Design as a Differentiator: Olivetti was the first tech company to apply design to everything (products, posters, and architecture) This inspired Massimo's concept of the “invisible touch”, the idea that consistent, intentional design creates a unique connection with users and gives a company a competitive edge The Interaction Design Institute Ivrea (IDII): Massimo’s path led him to IDII, located in the former Olivetti research building, where he transitioned from a two-week sabbatical to a four-year stay Learning by Making: To help students with no electronics background, Massimo drew on how he learned as a seven-year-old (“learning by making”) to remove the friction of interacting with technology The Founding Team: He met Tom Igoe (ITP) and David Cuartielles, and they realized students were afraid to be creative because they feared “blowing up” expensive tools like the Basic Stamp The “Pizza and a Beer” Price Point: Massimo aimed for a hardware cost of 20 Euros, roughly what a student would spend on a pizza and a beer, to encourage experimentation Building the Platform: Along with David Mellis, the team adapted Processing (a language for artists) by “surgically” replacing Java with C++ to create the Arduino IDE Ivrea Manufacturing: Leveraging the industrial base of Ivrea and Torino (the “Detroit of Italy”), Massimo was able to find local PCB manufacturers and assemblers just a short drive away From Hacking to AVR: Massimo's early work involved hacking satellite TV PIC chips for soccer fans, but mentor Bill Verplank encouraged him to use AVR microcontrollers because they could be programmed simply in C Enabling Creators: Massimo shares stories of how Arduino enabled others, such as Josef Prusa, who started with Arduino as a teenager before building his global open-source 3D printer company The Innovation of Simplicity: Massimo argues that Arduino’s true innovation is the user experience This is measured by the “Time to First Blink”, the goal for a user to go from downloading software to blinking an LED in five minutes Standardization and “The Core”: Arduino became an ad-hoc standard by providing a compatibility layer across different microcontrollers Massimo believes in having a “small slice of a really large pie” by allowing other architectures to work within the ecosystem Hardware Architecture and the “Lasagna”: Inspired by the PC104 format, the board uses a layered approach where modules stack like a lasagna The “Shield of a King”: The name Arduino comes from King Arduino of Ivrea; David Cuartielles suggested that since the board was named after a king, the add-on modules should be called “Shields” Hardware Design Choices: The board fits a credit card size (to stay within the free version of Eagle software) and is blue because that color was thought to be less tiring for workers’ eyes Happy Accidents: The unique shape was chosen to be “ourselves instead of everyone else” During the design process, Massimo inadvertently moved a connector by half a step, creating an offset header that they kept for consistency after the first few thousand were made The Discovery of Auto-Reset: During a workshop in Germany, Massimo solved the frustration of manual resets by soldering a capacitor to the DTR pin, allowing the software to trigger the reset automatically The US Market and Legal Battles: Tom Igoe's adoption of Arduino at NYU helped the US become the project’s single biggest market This growth led to a difficult legal battle for control of the brand against a former partner Support from Arm: Massimo credits Arm Ltd (and CEO Simon Segars) for providing the strategic support that allowed the founders to regain control of the company. Massimo believes this is the first time he has talked about the role of Arm in the difficult legal process. Industrial and AI Expansion: Partnerships with Intel and Microsoft (Windows 10 IoT) led to early forays into TinyML (AI on small boards) back in 2017 The Qualcomm Acquisition: In October 2025, Qualcomm acquired Arduino, which Massimo sees as essential for bringing “advanced silicon” into the family to handle the increasing complexity of technology The “Arduino Formula” and Layering: Massimo views Arduino as a formula for simplification that can be applied to anything, including complex Linux machines like the Uno Q This is achieved by building in layers, where beginners use high-level abstractions and experts can “strip away” layers to reach the bare metal The Future Vision: Massimo looks forward to the “Arduino Formula” being applied to new fields, stating he is waiting for someone to develop an “Arduino for biology” using CRISPR and DNA technology

It's summer and almost the 4th of July so we had to travel up to the birthplace of America, Philadelphia, to have a very special guest Mark Normand on! Join us as Mark answer's some emails, we talk comedy Mount Rushmore's and bring you 3 historical tales. Brian brings the history of fart jokes and flautists, Steve brings us the story of a dog and a man in a legal duel to the death, and Anthony brings us the story of a man arrested for having a beard in America, Mark also tells us all about the Axeman of New Orleans. We also pick the next 3 movies we will be watching, come listen and have a laugh or two. Have a delicious cup of coffee from our friends over at The Wholly Roast and try some Java! Use the code Rhist26 for free shipping! https://thewhollyroast.com/ LIKE AND SUBSCRIBE PLEASE! We are proud to announce our NEW Patreon is available: https://www.patreon.com/reviewinghistory We hope you sign up and enjoy the fun we're having over there. Please give us a rating and a review on ApplePodcasts or Spotify. It helps potential sponsors find the show! Sign up for @Riversidefm: www.riverside.fm/?via=reviewi... Sign up for @BetterHelp: betterhelp.com/reviewinghistory Email Us: Reviewinghistorypod@gmail.com Follow Us: www.facebook.com/reviewinghistory twitter.com/rviewhistorypod letterboxd.com/antg4836/ letterboxd.com/spfats/ letterboxd.com/BrianRuppert/ letterboxd.com/brianruppert/list…eviewing-history/ twitter.com/Brianruppert #comedy #history #podcast #comedypodcast #historypodcast #marknormand #standupcomedy #comedian #tellemstevedave #tesd #americanhistory #america #andrewjackson #josephpalmer #flatulence #fart #flatuist #france #duel #greyhound #dog

Sungai Watch co-founder Gary Bencheghib spoke with SBS Indonesian about why he and his siblings, despite being foreigners, have dedicated their lives to stopping plastic pollution in rivers across Bali and Java. - Co-founder Sungai Watch, Gary Bencheghib, berbicara dengan SBS Indonesian tentang mengapa ia dan saudara-saudaranya, meskipun orang asing, mendedikasikan hidup mereka untuk menghentikan polusi plastik di sungai-sungai di Bali dan Jawa.

***SUMMER FAN FAVORITES SERIES!!***Do you ever wonder if you're walking through life alone? In this episode of Java with Jen, I sit down with Prophet Phil Rich to uncover the truth about the ministry of angels and how they are actively working in your life right now.Angels aren't just biblical characters from the past—they are created beings assigned by God to minister to, for, and with believers. Whether you're facing spiritual warfare or just need to understand the practical side of your faith, this conversation will change how you see your daily walk.We're breaking down the different forms angels take, the biblical truth behind "assigned" angels, and why it's critical to understand their speed and strength in your life. Don't miss this powerful discussion on activating your spiritual awareness.In this episode, we cover:Understanding the three distinct ways angels minister to believersThe difference between natural and spiritual sight regarding angelic encountersReal-life testimonies of protection and divine interventionHow to activate the purpose of the angels assigned to your lifePractical steps for discerning the presence of angels in your everyday lifeGrab your coffee and let's dive into the supernatural!------------------------------------------------------KEY TOPICS:✅ Introduction to Angels and Their Purpose✅ The Ministry of Angels✅ Engaging with Angels in Everyday Life✅ Real-Life Examples of Angelic Ministry✅ Seeing Angels: Natural vs. Spiritual Eyes✅ Angelic Encounters and Protection✅ Angels Assigned at Birth✅ The Speed and Strength of Angels✅ Angels in Different Forms✅ The Creativity of God and His Angels✅ Conclusion and Next Steps--------------------------------------------------------CONNECT WITH PHIL & JEN:Prophet Phil Rich: https://drphilrich.com/Jenilee: www.jenileesamuel.com Let's Stay Connected

Të informohesh dhe të argëtohesh… duket si mision i pamundur! Por jo për Julian Hurdha dhe Anxhelo Shkreli! Dyshja sjellin për publikun “Top Fare”, një emision humoristik ku nuk do të mungojnë të qeshurat, por as aktualiteti. Java nis me programin më provokues dhe që nuk kursen askënd. Më pak sarkazëm, ironi e pak ‘spec djegës', pasditet tuaja në Top Albania Radio nuk do jenë kurrë të mërzitshme!

This interview was recorded for the GOTO Book Club.http://gotopia.tech/bookclubBarry Feigenbaum - Retired Sr. Principal Software Engineer & Author of "Go for Java Programmers"Shon Saliga - IBM Storage EvangelistCheck out more here:https://gotopia.tech/episodes/444RESOURCESBarryhttps://www.linkedin.com/in/barryfeigenbaumShonhttps://www.linkedin.com/in/shon-saliga-32336b2DESCRIPTIONDr. Barry Feigenbaum — an IBM, Amazon and Dell veteran with a PhD in Computer Engineering and decades of Java experience — spent time working with Go on microservices and liked it enough to write the book he wished had existed when he made the switch. In this GOTO Book Club episode with longtime colleague Shon Saliga, he walks through the core contrasts: Go is a compiled language that targets a narrower domain than Java — primarily command-line tools and web servers — but excels there with smaller binaries, faster startup, and dramatically lower container overhead. Concurrency is the headline difference: Go's goroutines are far lighter than Java threads, and its channel-based communication model sidesteps many of the problems that make concurrent Java code hard to reason about.The error handling conversation is particularly illuminating. Java's exception mechanism, while powerful, encourages developers to overuse it for ordinary error reporting — Go simply doesn't allow that by design. Errors in Go are return values, not throws; panics are reserved for truly catastrophic situations. Similarly, Go's implicit interfaces (if you implement the methods, you implement the interface — no declaration required) give the language a flexibility that feels alien to Java developers at first but becomes a strength quickly. Barry's conclusion is clear: for greenfield servers and containerized microservices, Go is worth serious consideration — and for Java developers willing to reset a few mental models, the transition is more tractable than it looks.RECOMMENDED BOOKSBarry Feigenbaum • Go for Java Programmers • https://amzn.to/4uRL3liKen Christopher, Barry Feigenbaum, Shon Salig • DOS 5: The Basic • https://amzn.to/4tKDVGsA N M Bazlur Rahman • Modern Concurrency in Java • https://amzn.to/42w8cOkBen Evans & Jim Gough • Optimizing Cloud Native Java • https://amzn.to/41nivD9Ian F. Darwin • Java Cookbook 5th ed. • https://amzn.to/3QH0NZyVictor Grazi & Jeanne Boyarsky • Real-World Java • https://amzn.to/4oCEeBRBlueskyInstagramLinkedInFacebookCHANNEL MEMBERSHIP BONUSJoin this channel to get early access to videos & other perks:https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/joinLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

*DISCLAIMER* This interview includes some adult themes and is not intended for young ears.   Matthew 9:37 (NIV) "Then he said to his disciples, “The harvest is plentiful but the workers are few."   *Transcription of original episode* God, Sex, and Your Marriage: Special Patreon Release Interview with Dr. Juli Slattery   Questions We Discuss: For many couples, sex can be a difficult area of marriage and you encourage people that is normal, but you also warn us not to confuse normal with healthy. What is normal for married couples and what is healthy, as it relates to sexual intimacy in marriage? What is God's genius chemical cocktail that we experience during sex? Will you give a brief overview of your four pillars of intimacy?   Dr. Juli Slattery is a clinical psychologist, author, speaker and broadcast media professional with over twenty-five years of experience counseling, and teaching women. She's the president and co-founder of Authentic Intimacy, a unique ministry devoted to teaching God's design for intimacy and sexuality. In 2020, Juli launched SexualDiscipleship.com, a platform designed to help Christian leaders navigate sexual issues and questions with gospel-centered truth. She hosts a weekly podcast, Java with Juli, where she answers tough questions about relationships, marriage, and spiritual, emotional and sexual intimacy.  www.authenticintimacy.com   Other Episodes with Dr. Juli Slattery on The Savvy Sauce: Passion Pursuit with Dr. Juli Slattery Patreon 26 Holy Sex with Dr. Juli Slattery Life-Giving Marriage with Dr. Juli Slattery   Thank You to Our Sponsors: Female by Design   Connect with The Savvy Sauce on Facebook or Instagram or Our Website   Please help us out by sharing this episode with a friend, leaving a 5-star rating and review, and subscribing to this podcast!   Gospel Scripture: (all NIV) Romans 3:23 “for all have sinned and fall short of the glory of God,”   Romans 3:24 “and are justified freely by his grace through the redemption that came by Christ Jesus.”   Romans 3:25 (a) “God presented him as a sacrifice of atonement, through faith in his blood.”    Hebrews 9:22 (b) “without the shedding of blood there is no forgiveness.”    Romans 5:8 “But God demonstrates his own love for us in this: While we were still sinners, Christ died for us.”    Romans 5:11 “Not only is this so, but we also rejoice in God through our Lord Jesus Christ, through whom we have now received reconciliation.”    John 3:16 “For God so loved the world that he gave his one and only Son, that whoever believes in him shall not perish but have eternal life.”   Romans 10:9 “That if you confess with your mouth, “Jesus is Lord,” and believe in your heart that God raised him from the dead, you will be saved.”    Luke 15:10 says “In the same way, I tell you, there is rejoicing in the presence of the angels of God over one sinner who repents.”   Romans 8:1 “Therefore, there is now no condemnation for those who are in Christ Jesus”   Ephesians 1:13–14 “And you also were included in Christ when you heard the word of truth, the gospel of your salvation. Having believed, you were marked in him with a seal, the promised Holy Spirit, who is a deposit guaranteeing our inheritance until the redemption of those who are God's possession- to the praise of his glory.”   Ephesians 1:15–23 “For this reason, ever since I heard about your faith in the Lord Jesus and your love for all the saints, I have not stopped giving thanks for you, remembering you in my prayers. I keep asking that the God of our Lord Jesus Christ, the glorious Father, may give you the spirit of wisdom and revelation, so that you may know him better. I pray also that the eyes of your heart may be enlightened in order that you may know the hope to which he has called you, the riches of his glorious inheritance in the saints, and his incomparably great power for us who believe. That power is like the working of his mighty strength, which he exerted in Christ when he raised him from the dead and seated him at his right hand in the heavenly realms, far above all rule and authority, power and dominion, and every title that can be given, not only in the present age but also in the one to come. And God placed all things under his feet and appointed him to be head over everything for the church, which is his body, the fullness of him who fills everything in every way.”   Ephesians 2:8–10 “For it is by grace you have been saved, through faith – and this not from yourselves, it is the gift of God – not by works, so that no one can boast. For we are God‘s workmanship, created in Christ Jesus to do good works, which God prepared in advance for us to do.“   Ephesians 2:13 “But now in Christ Jesus you who once were far away have been brought near through the blood of Christ.“   Philippians 1:6 “being confident of this, that he who began a good work in you will carry it on to completion until the day of Christ Jesus.”

Jim Grisanzio from Oracle Java Developer Relations talks with Cristian Schuszter at JavaOne 2026. Cristian is a PhD in systems engineering and a Tech Lead at CERN in Geneva. He's been at CERN for 8 years, but he's been coding since he was eight years old. He loves working with and contributing to the Java community and other Open Source projects. This was Cristian's first JavaOne, and his session, "30 Years of Java Development: Keeping it All Together," covered how CERN keeps Java running across teams since 1998. Like any large company, CERN uses a lot of legacy code supporting systems that, in Cristian's words, "need to keep running." Java is not only used for business critical applications at CERN but also for accelerator system operations. On working at CERN among Nobel laureates, Cristian said, "I felt like I thrived in this kind of environment." Cristian also helped revive the Voxxed Days developer conference at CERN and started the CERN Java User Group.

Përzgjedhur nga Dee Jay-it e Top Albania Radios, mbrëmja e të dielës është e gjitha për t'u shijiuar. Java mbyllet me muzikë të mirë dhe përzgjidhet nga DJ resident të Top Albania Radio.

Përzgjedhur nga Dee Jay-it e Top Albania Radios, mbrëmja e të dielës është e gjitha për t'u shijiuar. Java mbyllet me muzikë të mirë dhe përzgjidhet nga DJ resident të Top Albania Radio.

Përzgjedhur nga Dee Jay-it e Top Albania Radios, mbrëmja e të dielës është e gjitha për t'u shijiuar. Java mbyllet me muzikë të mirë dhe përzgjidhet nga DJ resident të Top Albania Radio.

Përzgjedhur nga Dee Jay-it e Top Albania Radios, mbrëmja e të dielës është e gjitha për t'u shijiuar. Java mbyllet me muzikë të mirë dhe përzgjidhet nga DJ resident të Top Albania Radio.

An airhacks.fm conversation with Alvaro Hernandez (@ahachete) about: discussion about the quarkus Insights episode "#337 The Database Cloud" stackgres live demo, StackGres as a Quarkus and GraalVM native kubernetes operator for running Postgres, comparing CloudNativePG (CNPG) by EnterpriseDB to StackGres, Patroni for Postgres high availability, the split-brain risk of relying on Kubernetes and etcd alone, distributed consensus and leader lock election via etcd, why distributed systems and cryptography should not be self-implemented, async, synchronous and quorum (semi-synchronous) Postgres replication trade-offs, cascading and cross-region replication topologies, the false-positive problem and heuristic exceptions in two-phase commit, the ondb ("own your database") project for self-hosted Postgres, losing control with managed cloud services and untestable backups, vanilla unmodified Postgres on StackGres, the "Kubernetes without Kubernetes" (Kubeless) pattern, talking directly to ContainerD through the CRI API, runc and the Docker to ContainerD chain, a self-contained native binary that embeds ContainerD over Unix domain sockets, the slony node-local component named after the Postgres slonik elephant mascot, the Matriarch orchestrator component, reverse gRPC tunnels with Slonies phoning home across NAT and firewalls, a multi-tenant cloud control plane provided as a service, curl-pipe-shell node installation with a token, end-to-end encrypted Postgres protocol tunneling for JDBC from anywhere, psql compiled to wasm in the web console, Tailscale-inspired user experience, unifying nodes, Kubernetes clusters and cloud pools as resources, Slony Kubernetes controller, Java 25 source-mode scripting without dependencies, implementing your own MCP server for Postgres JDBC metadata, the Goose agentic UI donated by Block to the Linux Foundation, AI Rails BCE, Java, Web Components skills Alvaro Hernandez on twitter: @ahachete

We talk to ourselves all day long—often without even realizing it. And while we may not be able to turn off the constant chatter happening inside our minds, we can learn to change the conversation. In this episode, author and Moody Radio host Jon Gauger shares how self-talk can be either destructive or redemptive, depending on whether you speak lies or biblical truth to yourself. So today, Jon will teach you how to identify the lies you're believing, replace them with Scripture, and invite God to renew your thinking. You'll also hear practical ways to memorize Scripture, why the Psalms are such a powerful place to start, and how speaking truth to your soul can bring peace, patience, and hope into your everyday life. Plus, Jon offers a FREE download to help you shift gears in your mind and hide God's Word in your heart. SHOW NOTES: 413Podcast.com/406  Read the episode TRANSCRIPT in the show notes. Get my weekly email, Java with Jennifer, to be notified when a new podcast episode releases. Subscribe HERE.

In this interview Peter Mitchell gives a detailed account of a little known event in Australia's military history - the fighting on Java in the opening weeks of the Pacific War. He also provides an insight into the benefits of creative non-fiction as a means of providing factual details about an event while also providing a good story for the readers. Hosted on Acast. See acast.com/privacy for more information.

Të informohesh dhe të argëtohesh… duket si mision i pamundur! Por jo për Julian Hurdha dhe Anxhelo Shkreli! Dyshja sjellin për publikun “Top Fare”, një emision humoristik ku nuk do të mungojnë të qeshurat, por as aktualiteti. Java nis me programin më provokues dhe që nuk kursen askënd. Më pak sarkazëm, ironi e pak ‘spec djegës', pasditet tuaja në Top Albania Radio nuk do jenë kurrë të mërzitshme!

This interview was recorded for the GOTO Book Club.http://gotopia.tech/bookclubA N M Bazlur Rahman - Java Champion & Author of "Modern Concurrency in Java"Michael Redlich - Java Champion & Lead Java Queue News Editor at InfoQCheck out more here:https://gotopia.tech/episodes/443RESOURCESBazlurhttps://bsky.app/profile/bazlur.cahttps://x.com/bazlur_rahmanhttps://github.com/rokon12https://www.linkedin.com/in/bazlurhttps://bio.site/bazlurhttps://bazlur.caMichaelhttps://twitter.com/mpredlihttps://github.com/mpredli01https://www.linkedin.com/in/michael-redlich-13a966https://about.me/mpredliDESCRIPTIONIn this GOTO Book Club episode, Java Champion A N M Bazlur Rahman joins host and fellow Java Champion Michael Redlich to discuss Modern Concurrency in Java — the first comprehensive update to Java concurrency literature in 20 years. Bazlur traces his motivation to the arrival of virtual threads in JDK 21, which he describes as a fundamental shift in Java's concurrency cost model: platform threads were expensive and scarce, demanding careful pooling; virtual threads are cheap, plentiful, and behave like ordinary threads from the developer's perspective, without requiring a new programming model. The book covers this evolution end-to-end, from the history of threads through to structured concurrency, scope values, and the modern frameworks that have already adopted virtual threads — most with a single config change.The conversation also takes a nuanced look at reactive programming's future. Bazlur's conclusion is that reactive remains compelling in specific contexts — event-driven streaming systems, architectures needing end-to-end back-pressure — but it's no longer the default answer to scalability. For most microservices doing blocking I/O, virtual threads are now the stronger default, and reactive becomes a deliberate architectural choice rather than an automatic one. The book's goal is to give developers both the conceptual grounding and the practical guidance to make that choice confidently — understanding the tool one level deep, so they can design better systems, not just configure their way through a framework.RECOMMENDED BOOKSA N M Bazlur Rahman • Modern Concurrency in Java • https://amzn.to/42w8cOkBen Evans & Jim Gough • Optimizing Cloud Native Java • https://amzn.to/41nivD9Ben Evans, Jason Clark & David Flanagan • Java in a Nutshell • https://amzn.to/43FDoMAIan F. Darwin • Java Cookbook 5th ed. • https://amzn.to/3QH0NZyVictor Grazi & Jeanne Boyarsky • Real-World Java • https://amzn.to/4oCEeBRBlueskyInstagramLinkedInFacebookCHANNEL MEMBERSHIP BONUSJoin this channel to get early access to videos & other perks:https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/joinLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

Fredrik snackar Kotlinconf 2026 och språket Kotlin i allmänhet med Johan Blomgren och Emil Kantis. Hur var konferensen? Hur fungerar utvecklingen av Kotlin, och vad är på gång i språket? Det blir tips på intressanta presentationer värda att se när de släpps på nätet, och en förklaring av varför Kotlinconfs officiella app inte känns helt hemma på Appletelefoner. Vi snuddar också - inte helt oväntat - vid språkmodeller. Vi pratar om AI, teknikutvecklingen, och presentationen av saker som oundvikliga kontra att bygga en bättre värld genom att helt enkelt prata mer med andra människor. Gärna öga mot öga också. Det är en mänsklig superkraft! Som avslutning bjuds på en snabb genomgång av anledningar att byta till Kotlin från Java. Ett stort tack till Cloudnet som sponsrar vår VPS! Har du kommentarer, frågor eller tips? Vi är @kodsnack, @thieta, @krig, och @bjoreman på Mastodon, har en sida på Facebook och epostas på info@kodsnack.se om du vill skriva längre. Vi läser allt som skickas. Gillar du Kodsnack får du hemskt gärna recensera oss i iTunes! Du kan också stödja podden genom att ge oss en kaffe (eller två!) på Ko-fi, eller handla något i vår butik. Länkar Johan Emil Java Kotlin Komma igång med Kotlin som Java-utvecklare Att övertyga andra om Kotlins storhet Helping decision makers say yes to Kotlin React Vue ATG Junit Kotest Kotlin-test Kotlinconf 2026 Keynoten för Kotlinconf 2026 Jetbrains utvecklar både IDE:er och Kotlin Javazone i Oslo Kotlin på Youtube - inklusive inspelninigar från Kotlinconf 2026 när de släpps KEEP - Kotlin evolution and enhancement process Local lifetimes i Kotlin Value semantics i Kotlin Rich errors i Kotlin Sum types Union types Javas projekt Leyden och projekt Valhalla Virtual threads i Java Kotlin multiplatform Compose multiplatform Kotlinconf-appen Stöd oss på Ko-fi! Erik Hellman Eriks presentation på Kotlinconf 2025 om IOT MQTT Matter Spec-driven development Jake Wharton - pratade om composebaserat terminal-UI-bibliotek Jesse Wilson Okhttp - Squarebyggt ramverk Lena Reinhard snackade om utvecklares roll i AI-världen Professional development - presentation från Google IO 2026 Clean code Kotlins LSP Junie - Jetbrains kodagent Lars Wikman Coursera-kurs om Kotlin för Javautvecklare Kotlin-övningar Builder pattern Bygga DSL:er med Kotlin WASM Uber snackar Kotlin Titlar Min Kotlinbana Kotlin på många olika sätt (Min upplevelse av) Sex år i Kotlin Bypassa hela stdout Jag är ju redan i utlandet Här slutade nullpointers En konstruktor som har alla parametrar

Further reading: Is the Javan tiger Panthera tigris sondaica extant? DNA analysis of a recent hair sample The Sunda tiger [photo by Alfonsopazphoto – Own workAnimaisFotos, CC BY-SA 3.0, https://commons.wikimedia.org/w/index.php?curid=16029853]: Show transcript: Welcome to Strange Animals Podcast. I'm your host, Kate Shaw. We're going to learn about a mystery tiger this month, but first we have to learn about the place where it's supposed to live. Java is a large island that was formed by volcanic activity millions of years ago, and it's been home to humans and our ancestors for over a million years. Its soil is rich and the climate is tropical, but the island's ecosystems include tall mountains, savannas, rainforests, and mangrove forests. Naturally, lots and lots of animals live on Java that are found nowhere else in the world. Unfortunately, a whole lot of people live on Java too, which means that many animals and their habitats are threatened by habitat loss and pollution. Many animals have gone extinct in the last few hundred years. That includes the Java tiger. The Java tiger was small compared to tigers in other areas, although even a small tiger is a big animal. A big male tiger can grow about ten feet long, or 3 meters, and the Java tiger could grow about 8 feet long, or almost two and a half meters. The Java tiger was lightly built, though, and rarely weighed much more than 300 pounds, or about 140 kilograms. Despite its relatively small size, it was extremely strong and had paws as big as the much larger Bengal tiger. It also had lots of thin stripes. Originally scientists thought the Java tiger was a separate subspecies of tiger, but in 2017 it was reclassified as a population of Sunda tigers that have only been isolated from other populations for around 12,000 years. That doesn't mean it wasn't important, though. It showed differences from other Sunda tigers that weren't yet significant enough to warrant it being a separate subspecies, but which definitely indicated it was on its way to evolving into a separate subspecies. Unfortunately, the Java tiger's habitat was largely destroyed to make way for farming and logging, and as a result its usual prey animals became rare or went extinct. People would also poison or shoot any tiger they could. It only survived in a few small nature preserves, but the last tiger footprints were spotted in 1989 and since then, no tigers have been officially seen on Java. A 1999 expedition that set up camera traps in hopes of spotting a few tigers mostly got photos of poachers hunting in what was supposed to be a protected area. The Java tiger was declared extinct. Rumors persisted that tigers still lived on Java, though. Sometimes I think people claim to see recently extinct animals as a way to feel less guilty about humans having driven an animal to extinction. But in 2019 someone saw a tiger outside a village in western Java and reported the sighting to some local foresters. The foresters investigated and discovered footprints, claw marks, and a single hair on a fence. The foresters collected the hair carefully and gave it to a team of geologists who were working in the area. The geologists sent it to the West Java Nature Conservation Authority, which sent it for genetic analysis. They also sent some tiger hairs from other types of tigers to compare it to, including hairs from a museum specimen of a tiger killed on Java in 1930. The hair discovered in 2019 was definitely from a tiger, and its genetic signature most closely matched the genetic signature of the 1930 Java tiger specimen. This doesn't 100% mean the Java tiger isn't extinct, but it does mean that there's hope that it's still around. Java is part of Indonesia these days, and a few days ago as this episode goes live, the Indonesian government announced a plan to search for signs of the tiger, with an expedition getting underway soon to place camera traps. Conservationists are hoping that the tiger is discovered, which will allow it to be protected. The Sunda tiger is critically endangered, only surviving in the wild on the island of Sumatra, with possibly fewer than 400 of them left alive. Another population of Sunda tigers, the Bali tiger, was declared extinct in the 1940s. A few hundred captive tigers living in zoos around the world show congenital health issues as a result of inbreeding. If the Java tiger is still alive, it could mean the difference between extinction and survival of the entire Sunda tiger subspecies. Fingers crossed that the camera traps reveal a healthy, safe population of tigers on Java! Thanks for your support, and thanks for listening!

Three more forgotten campaigns… The strange, sprawling, global war fought by British soldiers, sailors, marines and East India Company troops in places most people never associate with the redcoat at all. Today we are heading first to the River Plate, where Britain tries to break into Spanish South America through Montevideo and Buenos Aires with some courage, some skill, and quite a lot of  misplaced optimism Then we go to Mauritius, or Isle de France, a French base in the Indian Ocean where Napoleon's ships were making life deeply unpleasant for British trade. And finally, we end up in Java, where a British expeditionary force lands in the East Indies to take on a Dutch colony that had effectively become part of Napoleon's empire. Three campaigns. Three continents. Three very different stories. Support the channel and join my Patreon here - https://www.patreon.com/RedcoatHistory  Buy Steve's books here - https://www.helion.co.uk/people/steve-brown.php 

Jim Grisanzio from Oracle Java Developer Relations talks with Martin Chalupa from Netflix at JavaOne 2026. Martin is a software developer with about eight years at Netflix and about twenty years working with Java. At Netflix, Martin works on the JVM ecosystem team, which grew from the build tooling team and now also handles broader JVM work such as tuning, garbage collection, and upgrading. In his session at JavaOne Martin covered Java ahead of time compilation and Project Leyden, and he shared what Netflix has learned from experimenting with the technology. Just as many software developers, Martin found his way into engineering through this experience gaming as a kid. He built his first game in Java for the old Nokia phones as a school project. He has watched Java change a great deal over the years. The language keeps getting more comfortable and more approachable for young developers. His advice for students is to explore different options and find their own passion in the work. "With a little bit of work you can achieve some cool stuff," he says. So, get out there and "discover your passion." Martin at LinkedIn Jim at LinkedIn

Connect with Salil here: https://www.linkedin.com/in/salil-monga/If you're trying to make the jump into AI engineering, join Parsity: https://parsity.io/ai-devSalil Monga had a 4.0 GPA, applied to over 1,000 jobs, and landed three interviews. Not one of the jobs he actually got came from those applications.I sat down with Salil, now CTO of Cupe Connect, to dig into how you actually get hired in a difficult market: warm connections over cold applications, fundamentals over chasing the "golden stack," and why he walked into an interview thinking JavaScript was Java and still walked out with the offer.What we get into:- The 1,000-applications, 3-interviews reality, and why the applications were the wrong game to begin with- How every job he landed came from a professor or a peer, not a job board- Getting emotionally wrecked by applications, and the strategic mindset that fixes it- Using AI to actually learn instead of copy-pasting answers, and how he taught students to do the same- Why there's no golden stack, and how he shipped an iOS app having never built one before- Why fundamentals and problem-solving beat the framework of the month- How LeetCode quietly came back as a hiring filter, and how to treat it like one instead of hating it- Treating interviews as a game of chance you can tilt in your favor with rapport- Cube Connect: his no-algorithm, 50-meter-radius iOS app built to get people talking in real life againSalil is one of the more generous guests I've had on. He literally offered to review resumes and talk shop with anyone who reaches out, so go take him up on it.

This week, Felder calls in from England and tells us all about his own garden and his trip to Java's garden. Let's Get Dirty!Email Felder anytime at FelderRushing.Blog and listen Friday and Saturday mornings at 9 to The Gestalt Gardener on MPB Think Radio. In the meantime, in Felder's words, "get out and get dirty."If you enjoyed listening to this podcast, please consider contributing to MPB: https://donate.mpbfoundation.org/mspb/podcast Hosted on Acast. See acast.com/privacy for more information.

Have you ever caught yourself being a little… judgy? It's no secret—judgment is everywhere these days, even in the church. But aren't we also supposed to use good judgment? It's tricky, right? Well today, you're going to get biblical clarity on how to use good judgment without being judgmental. Shannon Popkin is back on the podcast to help you understand the difference between healthy discernment and being kinda judgy. You'll learn what Jesus actually meant in Matthew 7 when He said, "Judge not," how personal convictions can get in the way of judging rightly, and what it looks like to speak truth with compassion rather than condemnation. Plus, since not every issue is black and white, Shannon shares some practical ways to keep humility and God's grace at the center of it all. SHOW NOTES: 413Podcast.com/405  Read the episode TRANSCRIPT in the show notes. Get my weekly email, Java with Jennifer, to be notified when a new podcast episode releases. Subscribe HERE.

An airhacks.fm conversation with Bruno Borges (@brunoborges) about: discussion about the JAZ command launcher for Java, JVM tuning and default ergonomics for containers versus dedicated cloud environments, replacing the Java launcher with jaz in container images, supporting Java 8 to 25, maximizing resource utilization on kubernetes to reduce waste, running Java on Azure Functions, Azure App Service deploying a fat JAR without a container image, Azure Container Apps as a platform on AKS without YAML, Azure Kubernetes Service and AKS Automatic, Bicep as infrastructure as code, deploying a JAR to Kubernetes via OCI artifacts and a custom operator, Microsoft Foundry and the Microsoft Agent Framework, Semantic Kernel learnings, the Copilot SDK for Java communicating with headless CLIs, A2A and ACP protocols and MCP, agents as microservices with scoped tasks, guardrails, and sandboxing, per-agent model selection for cost and reasoning trade-offs, observability and traceability between agents with opentelemetry, grounding LLMs against MicroProfile, Jakarta EE, JAX-RS normative RFC 2119 specifications for hallucination-free Java code generation, the Boundary Control Entity pattern and business components as Java packages, package-info.java for semantic context, GitHub Copilot skills and custom instructions in Visual Studio Code, the AI Rails skills site, zero-dependency Java CLI scripting, reducing dependencies by reusing source code instead of JARs, the org.json reference implementation reduced to five classes, StackGres and OnGres running Quarkus and GraalVM to manage Postgres on Kubernetes, the Digg Into Java community Bruno Borges on twitter: @brunoborges

We're recapping a packed Disney trip that took us from Blizzard Beach to EPCOT, from a one-night resort stay to Banana Ball, and finally to Disney's Animal Kingdom for breakfast, snacks, shopping, and Disney's new Bluey experience. We kick things off at Blizzard Beach, where we cool down with some water park fun, try a couple of sweet treats including the S'mores Churro, and even run into a listener along the way. From there, we head to EPCOT to check out the limited-time Annual Passholder Lounge inside Restaurant Marrakesh and share whether this summer perk is worth making time for. Next, we check into the Meliá Orlando Celebration for a one-night stay before heading to ESPN Wide World of Sports to experience Banana Ball. We'll discuss the atmosphere, entertainment, and whether this unique event lives up to the hype. On Saturday, we make our way to Disney's Animal Kingdom for breakfast at Satu'li Canteen, check out some new merchandise, sample snacks from Isle of Java and Pizzafari, and join the virtual queue for Disney's newest Bluey experience.  Along the way, we highlight our favorite moments, biggest surprises, best values, and the experiences we'd most recommend. Whether you're planning a Walt Disney World vacation or just love hearing about what's new around the parks, this episode is packed with reviews, tips, and plenty of Disney fun.

Të informohesh dhe të argëtohesh… duket si mision i pamundur! Por jo për Julian Hurdha dhe Anxhelo Shkreli! Dyshja sjellin për publikun “Top Fare”, një emision humoristik ku nuk do të mungojnë të qeshurat, por as aktualiteti. Java nis me programin më provokues dhe që nuk kursen askënd. Më pak sarkazëm, ironi e pak ‘spec djegës', pasditet tuaja në Top Albania Radio nuk do jenë kurrë të mërzitshme!

What does it mean to rethink religion from the ground up? University of Colorado's religious studies professor Sam Gill draws on biology, philosophy, and decades of research and dance practice to argue that we are moving, whole organisms before we are divided into mind and body. Gill proposes that humans possess a biologically enabled capacity to hold together what we know to be different as if it were the same—a dynamic that underlies the powers of metaphor, masking, dancing, ritual action, symbol, and language. Through vivid examples from Hopi initiation, Javanese shadow puppetry and dance, and Navajo prayer ceremonials, Gill shows how religious actions create worlds, identities, and enduring cultural coherence. Series: "Ethics, Religion and Public Life: Walter H. Capps Center Series" [Humanities] [Show ID: 41541]

Tim Berglund talks to Gunnar Morling (Confluent) about his career in open source Java and data infrastructure. Gunnar's first job: a student PHP developer in AMD's e-learning group. His challenge: building Hardwood, a fast, multi-threaded Parquet engine for Java with minimal dependencies.► The One Billion Row Challenge blog post: https://www.morling.dev/blog/one-billion-row-challenge/SEASON 2 Hosted by Tim Berglund, Adi Polak and Viktor Gamov Produced and Edited by Noelle Gallagher, Peter Furia and Nurie Mohamed Music by Coastal Kites Artwork by Phil Vo  

Addison, Texas is proof that a small map footprint can deliver huge flavor. We drove up from Waco and immediately felt it: this pocket of the Dallas Fort Worth Metroplex runs on good food, big gatherings, and the kind of walkable energy that makes you want to park once and just explore. Sweet Paris: https://www.sweetparis.com/ Landmark Kitchen and Bar:  https://www.landmarkbars.com/addison Fuzz Labs: https://fuzzlab.co/ Dolce Paradiso:  https://www.dolceparadiso.net/ Visit Addison: https://visitaddison.com/Sidecar Social : https://sidecarsocial.com/addison/ Kick it Festival:  https://visitaddison.com/kickit/We're joined by Amber Patterson from Visit Addison, who breaks down what makes the city such a magnet for meetups and weekend trips. We talk Kaboom Town, Addison's legendary July 3 fireworks celebration, and Addison Oktoberfest, a long-running festival that brings a surprisingly authentic Munich-style experience to North Texas. Then we get into the stat that stops every foodie in their tracks: roughly 200 restaurants packed into 4.4 square miles, plus the local backstory of how Addison became a launchpad for iconic concepts.Sports fans get love too. With the World Cup coming to the Dallas area, Amber shares how Addison is preparing with watch-friendly restaurants and a four-day Kick It in Addison festival at Addison Circle Park, complete with a huge screen and all-day match viewing. We also swap notes on why the park itself is worth a stop, and how Java and Hops Coffee House turns a simple stroll into the perfect park lunch plan with standout coffee.We kick off our restaurant recap with Sweet Paris, and we preview more spots and experiences we're adding shortly after a quick technical hiccup.  Also mentioned in this episode: Jessica Vasquez- Design It Dallas: @DesignitDallas Part 2: Exploring Moray Speyside-Scotland: A Day of Hidden Treasures, Adventure, and Culinary Delights | 229 | https://www.buzzsprout.com/263670/episodes/15853436From Lighthouses to Castles - Join us in Moray Speyside, Scotland - Part 1 | 228 | https://www.buzzsprout.com/263670/episodes/15845252Subscribe so you don't miss the updated full rundown, and if you enjoyed the travel and food intel, share the episode and leave us a review.Ready for Summer? Get 10% OFF your own roadsurfer adventure!https://link.roadsurfer.com/roamiesCODE: ROAMIES10And it means the world to us when you subscribe, rate and share our podcast.Alexa and RoryThe ROAMiesFollow us at:http://www.TheROAMies.com@The ROAMies: Facebook and Instagram YouTube and X.

AP correspondent Charles de Ledesma reports on a Russian drone landing on Romanian - rather than Ukrainian - soil; the Laos cave rescue mission continues; Europe's heat wave is affecting the French Open tennis tournament; and communities in east Java commemorate a tragic event from 14 years ago.

Have you ever felt the passion in your faith slowly fading? Maybe there was a time when you couldn't wait to open your Bible, go to church, or talk about God. But somewhere along the way, your fire went out. Your enthusiasm faded. And now? You're in a spiritual funk—maybe even numb. Well today, Dallas Theological Seminary President, Dr. Mark Yarbrough, joins us for a deeply honest and hope-filled conversation about what it means to revive a faith that's grown cold. Mark explains why every believer is vulnerable to drifting spiritually—whether it's due to an abrupt hardship or a slow fade of familiarity—and he'll give you six essential markers of a rekindled heart, all of which are rooted in returning to your identity in Christ. Oh friend, this conversation is not about trying harder or following a spiritual checklist. It's about pointing you back to the One who can set your heart ablaze again. SHOW NOTES: 413Podcast.com/404  Read the episode TRANSCRIPT in the show notes. Get my weekly email, Java with Jennifer, to be notified when a new podcast episode releases. Subscribe HERE.

Java's use of memory, often chided for being excessive, is actually a strength as it trades more memory use for fewer CPU cycles. Java can only make this tradeoff due to its moving garbage collectors, something more memory efficient platforms often cannot. But what's the point in leaving available memory on the table if using it makes your program run faster? Efficient use of that resource wouldn't be to leave it untapped but to use it to speed up the program. In this "Ask the Architect" episode of the Inside Java Podcast, recorded during JavaOne 2026, Nicolai Parlog talks to Ron Pressler, Java Architect at Oracle.

The new AIEWF website is live! CFPs close in 2 days and we will run our first New Engineer Orientation this weekend, get your tickets booked ASAP as they -will- sell out. Take the AI Engineering Survey and get >$2k in credits and free AIE WF tickets!One of the central tensions in the agents industry is that even while there are major decacorn agent labs like Sierra, Decagon, Notion and Cursor being built up, it is also true that it has never been easier to DIY agents, with a plethora of agent frameworks like LangGraph and Pydantic and Flue, and managed agents from Anthropic and Gemini and Amazon. There has been a wave of companies building their own background agents from Shopify to Stripe to Paradigm to Razorpay, and even Cognition's friends Ramp have built their own coding agent with other friend Modal.You'd think Cognition might feel a bit threatened, but they're not - even after all this, they were way oversubscribed for the $1B Series D they just announced:Walden Yan, coiner of context engineering and Chief Product Officer/Cofounder of Cognition, invited OpenInspect's Cole Murray to talk about why the Devin is in the Details.Full conversation live on the pod today: In retrospect, async agents were the most AGI pilled bet you could make in 2024 - the models weren't good enough yet to vibecode, and people didn't trust AI enough to let it rip, nobody (including early Cognition) was sure about the form factors. Now it is obvious:* The first wave of AI coding tools made the developer faster but remain heavily in the loop. Copilor and Cursor's tab autocomplete are prime examples However, the workflow was still heavily centered around and bottlenecked by the developer's local workflow: a developer in an IDE, watching the model, accepting or rejecting changes, and pushing code one interaction at a time.* The second wave was local agents: Claude Code, Windsurf, Cursor's agents pane: first one and increasingly many terminals all running concurrently.* The current Age of Async Agents points to a different future focused more on agent orchestration which drives end-to-end development.According to previous guest Steve Yegge, there are finer-grained 8 levels to agent adoption, but we have collapsed it into three.As Cursor's Michael Truell put it in The third era of AI software development:Cursor is no longer primarily about writing code. It is about helping developers build the factory that creates their software. This factory is made up of fleets of agents that they interact with as teammates: providing initial direction, equipping them with the tools to work independently, and reviewing their work.The agent should not sit solely inside the developer's flow. It should be setup to work in the background so that you can give it a task, a repo, a machine, a shell, a browser, tests, memory, and review loops to go do the work somewhere else.In less than a year, the sentiment has shifted from avoiding multi-agent systems:to suggesting approaches that actually work:From coining “context engineering” to building the infrastructure behind Devin's 7x PR growth and jump from 16% to 80% of commits across Cognition repos, Walden Yan has had a front-row seat to the background-agent shift. In this episode, Cognition co-founder and CPO Walden Yan joins swyx alongside Cole Murray, creator of OpenInspect, to unpack why everyone is building their own Devin, what changed after the December 2025 model inflection, and why “spec to pull request” is now becoming a real production workflow.We go deep on the architecture of background agents: harness-in-the-box vs out-of-the-box, why Devin separates the “brain” from the machine, why repo setup is still one of the hardest problems, why Docker is not always enough, and how full VMs, snapshots, scoped secrets, GitHub bots, Slack integrations, and video-based testing all fit together. Walden and Cole also dig into memory, MCP limitations, multi-agent orchestration, AI code review, SRE auto-triage, PMs shipping code from Slack, Windsurf 2.0, hybrid frontier/sub-frontier systems, and the real failure mode of uncontrolled vibe coding: your codebase regressing to your worst engineer.And as agents eat software… and software eats the world… you can draw the conclusion on what is next:We discuss:* Why the engineering world is waking up to background agents and cloud agents* The December 2025 model inflection that made spec-to-PR workflows practical* Devin's 7x merged PR growth and rise from 16% to 80% of commits* Why Cole built OpenInspect as an open-source background-agent system* The economics of $20/seat agent products and why monetization is tricky* What Cognition actually sells beyond Devin: infra, onboarding, integrations, and adoption* Harness in the box vs out of the box, and why architecture matters* Why Devin separates the brain from the machine for security and permissions* Repo setup, scoped secrets, Docker Compose, and agent-ready dev environments* Why full VMs matter when agents need to run real applications and test them* Android, macOS, Windows, nested virtualization, and machine-specific agent work* Why testing is much harder than “computer use”* Screenshots, video verification, and the “I know it works” merge moment* GitHub UX, Devin Review, AI reviewers, and agents responding to PR comments* Why MCP alone is not enough for first-class Slack and enterprise integrations* Memory, Knowledge, skills, Claude.md, and why retrieval is still unsolved* Devin's auto-generated memories and the challenge of memory pruning* Always-on agents as permanent PMs for issues, tickets, and product areas* Sub-agents, meta-Devin management, and what multi-agent systems actually add* Why pure auto-merge vibe coding breaks down after about two weeks* AI code smells, lint rules, reward hacking, and Semgrep for agent-written code* GitAI, inline context, and preserving the “why” behind code changes* Local testing, mock servers, older codebases, and preparing companies for agents* Windsurf 2.0 and the handoff between local foreground agents and cloud background agents* SRE auto-triage, support workflows, and agents as first responders* PMs, marketing, and non-engineers creating pull requests from Slack* AI agent budgets, $1k-$5k per engineer spend, and hybrid frontier/sub-frontier systems* The rise of autonomous coding factories and who Cognition is hiringWalden Yan* X: https://x.com/walden_yan* LinkedIn: https://www.linkedin.com/in/waldenyan/Cole Murray* X: https://x.com/_colemurray* LinkedIn: https://www.linkedin.com/in/colemurray/* OpenInspect / Background Agents: https://github.com/ColeMurray/background-agentsTimestamps00:00:00 Introduction00:00:43 Why Everyone Is Building Their Own Devin00:01:57 Devin's 2025 Ramp: 7x PR Growth and 80% of Commits00:03:49 OpenInspect and the Rise of Open-Source Background Agents00:07:59 What Cognition Actually Sells Beyond Devin00:09:56 Background Agent Architecture: Harness In vs Out of the Box00:12:08 Separating the Brain from the Machine00:14:07 Repo Setup, Secrets, Docker, and Full VMs00:19:13 Why Testing Is Harder Than Computer Use00:22:40 Video Verification and the “I Know It Works” Merge Moment00:23:19 GitHub UX, Devin Review, and AI Code Review00:25:42 MCP, Slack, and Enterprise Agent Integrations00:28:59 Memory, Knowledge, and Always-On Agents00:36:16 Sub-Agents, Multi-Agent Orchestration, and Meta-Devin00:43:55 Vibe Coding, Auto-Merge, and Codebase Decay00:48:38 Agent Infra, VPCs, Cloud Providers, and Fast VM Restore00:52:25 AI Code Smells, Reward Hacking, and Code Review Systems00:56:10 Making Codebases Agent-Ready00:58:30 Windsurf 2.0 and the Local-to-Cloud Agent Handoff01:01:15 SRE Auto-Triage, PMs Shipping Code, and Agent Use Cases01:04:32 Agent Budgets, Hybrid Models, and Autonomous Coding Factories01:06:51 Hiring at Cognition and OpenInspect Consulting01:07:45 OutroTranscriptIntroduction: Walden Yan, Cole Murray, and Context EngineeringSwyx [00:00:00]: All right, we're in the studio with Walden Yan, co-founder of Cognition, CPO.Walden [00:00:08]: Happy to be here.Swyx [00:00:09]: Which is a cool title. And coiner of context engineering.Walden [00:00:15]: Although I think there are many people who'd used the terms in various ways beforehand, but I did find that people, both internally and externally, enjoyed the upgrade from prompt engineering or model wrapping into maybe a more thoughtful way to build agents.Swyx [00:00:33]: For those who haven't caught up on that, I have on screen the Don't Build Multi-Agents post, which you should go read on and we might refer to, and Cole Murray, who created OpenInspect.Cole [00:00:43]: Great to be here.Swyx [00:00:43]: So let's talk about it. Everyone is building their own Devins. What's going on?The December Shift: From Handholding Models to Autonomous PRsCole [00:00:51]: So I think the engineering world is waking up to this idea of background agents, cloud agents, whatever you'd like to call it. And I think we saw a shift around the December timeframe of 2025, where the models Opus 4.5 and GPT 5.2, they reached a capability where we moved away from handholding the model and being able to actually more or less autonomously drive the model. And what I mean by that is that we could pretty much go from a specification to a completed pull request, assuming the spec was good enough, with very little friction. And that paradigm alone, I think, changed a lot of how we interact with agents, and opened this world where background agents became more practical.Swyx [00:01:41]: I think for Cole, everyone experienced this in December, but I feel like there was just this increasing ramp, right? There was this moment which was, I think, Sonnet 3.7, where, You guys rewrote Devin in one night or something. So describe 2025 or how it felt from your side.Walden [00:02:01]: In retrospect, we always thought it was ramping up, but then even now, over the last three, four months from today, it's been ramping up even faster. So it's almost funny to be talking about how, big of a leap Sonnet 3.7 was, and honestly, a lot of it was stripping out parts of Devin that were no longer needed with that jump in of intelligence. But I also just think that a lot of the recent leaps, especially, you look at, models like Opus and the latest GPT models, they are reaching levels of autonomy where people are actually finding that they actually can just be hands-off. And people who were once debating, “Oh, do I need to be in the weeds with my model in the IDE? Can I just completely move it off into the cloud?” That's a more serious conversation, and we've seen that in all of our growth charts. Internally there's this funny graph where our usage has, of PRs, our merged PRs, has grown 7X since I forget what it was called.Swyx [00:02:57]: I think Dev, maybe tweeted that. Yes.Walden [00:03:01]: it grew like 7X over, the last, I think it was, two months, three months, something like that. And then you see our engineering headcount growth. It's, gone up by, 10% or something.Swyx [00:03:11]: We were, we were afraid To release this. So this is Devin commit percentages on all Devin repos, was 16% in January and now 80% in March.Walden [00:03:25]: It's a big shift right now. And so it makes sense that a lot of people are now thinking about, buying Devin, but also maybe, trying to build their own and there's Lots of I have a lot of fun building Devin, so I can see why other people would want to build their own cloud agents as well. Matt, well, maybe it's good to hear, what initially inspired you to try to build OpenInspect?OpenInspect: Ramp, Cloud Agents, and Open SourceCole [00:03:49]: OpenInspect came about, through primarily my clients observing how they were using tools like Claude, OpenAI's Codex at the time, and seeing some of the friction that they were having with it. Primarily the Claude was being used through Slack, and a big issue they ran into was that the sessions that were launched were specific to whoever called it via Slack. And so if a PM was the one who invoked the session and they would then go to pass context to engineering can't see the session. And that in itself was a deal breaker because the PM, “Hey, engineering, can you jump in?” But there's nothing to jump in on unless they're copy-pasting out or the single response that came back. And so seeing some of these problems, I had built a similar architecture internally, just to experiment with, test out different ideas as this trend of moving off of localhost was starting to become, And as Ramp released their blog post, I had a lot of the pieces for this already in place, and just thought it would be funny to, see what Claude could do just purely from the blog post. And on my X account, there's actually a thread of where I live tweeted, going through thisCole [00:05:14]: comparing GPT and Claude as both of them are going through it.Swyx [00:05:17]: On the announcement thing or something else?Cole [00:05:19]: right after it got released. We can put it in the show notes. Yeah, it was helpful that I had already knew how to verify the system. I knew what I was looking for. I think Ramp did a great job of really illustrating, the technical aspects of how to build something. It was much more than just like, “Hey, we built a great system.” It was, “And here's how you can build it too.” And so, I resonated a lot with that, just with the problems that I was already seeing, and I thought that, looking around, I didn't really see anything in the open source community that, met this type of system. I think there's a lot that run, in localhost like Superset, Conductor, and many others.But nothing that was actually running in the cloud. And so, I built it, and I thought it was interesting to just open source it and allow anyone to then have a foundation that they can mix and match on top of.The Business of Background Agents: Open Source vs. DevinSwyx [00:06:16]: So literally after Devin was launched was, there was OpenDevin Which became All Hands. I don't know if you tried that orWalden [00:06:22]: I was going to say, one of the things that interested me a lot with OpenInspect was, you didn't try to go make it then something you monetize. There are a lot of, I think, these open source projects would then go and really try to, raise VSwyx [00:06:36]: That's why no OpenDevin. Yeah.Walden [00:06:38]: yeah, and how did you think about that? I thought that was very interesting.Cole [00:06:44]: I thought, and just what I had seen across my clients, was that having a background agent system is going to become a critical infrastructure within their company. And so because of that, I think that I wanted to open source it so that they could fork it and put in whatever customization they wanted. To that question though, I get asked all, “Oh, are you going to raise? Are you going to turn this into a service?”Walden [00:07:08]: I'm sure you've gotten offers.Cole [00:07:09]: but primarily I don't want to do that for a few reasons. One, I think that I don't want to compete for, $20 a seat. I think that is just a really difficult business. I think it's very easy to copy the main pieces of it. Again, I built this fairly quickly. And I think because you are not owning, I guess, the entire stack, it's hard to monetize. You have money being made at the sandbox layer with Daytona, E2b, many other players. You have money being made at the model layer. And you sit in this weird in-between gray area where what are you actually selling? You're selling, I guess, the infrastructure. You're selling, the integrations maybe.Swyx [00:07:55]: let's ask the guy. What are you What are you selling?Walden [00:07:59]: Well, yeah, there's multiple layers to this in practice, and actually it's funny you mentioned the infrastructure, ‘cause when we got started building Devin as well, we had to go figure out how to make the infrastructure as well because,Swyx [00:08:10]: You had to build this two years before everyone else,?Swyx [00:08:15]: Including, the model sideWalden [00:08:17]: It was not, it was not very polished at the start, when we just built it off of raw VMs from cloud providers like EC2, the boot up time was so slow, I think, And especially then, turning off the machines, saving them, and then to be able to bring them back up again when the, when you want Devin to wake up again later. It would just be out cold for like 10 minutes because that's just how long these systems took. They were not built for this repeated down and up usage. And so we actually had to go do all of that. And as a result now, one thing we offer when we go and sell Devin to people is, you don't have to worry about all the compute side of things. We'll make it work. We'll make it work in your cloud if you want it to. But aside from the product, and I want to go into the agents and the tuning of the intelligence part later, but I think a big part of what we do at Cognition as well is to just make sure that your company learns and uses and adopts these coding agents. ‘Cause I think for especially the largest enterprises in the world, you find that there is a lot of people who want to move over to using AI for their day-to-day workloads. But because of the way projects are planned, because, not everyone is literate in using AI in these ways, having a team of engineers who can actually go in and onboard you, set up all the integrations you need, the automations you need to really get to that level of, leverage with AI, is super helpful. And so We do that. We show thought partners to the customers that we work with as well.Swyx [00:09:56]: So let's talk about, architectural stuff. I think that's always, that is something that was the topic of conversation between the two of you. Is this, the mental model that you want to start with or something else? I'll just leave the floor open to you guys.Agent Architecture: Harness in the Box vs. Out of the BoxCole [00:10:11]: I think, maybe we can start here as just a general what are the pieces of a background agent system. And then maybe we can go into some of the nuances of, Decisions that you can make.Swyx [00:10:22]: But I guess I also Like, what, maybe what Walden is saying is the agent is like in this open code box, I guess. Right? This is infra, and then there's, that's the agent. And you had this discussion about whether you put the agent in here or in Out externally. Can you tease that out?Cole [00:10:39]: In a background agent systems, you have a decision to make of where the agent is actually going to run. This is typically described as the harness in the box or out of the box. With running the agent in the box, you're making some trade-offs by doing that. The negative trade-off you're making is primarily security. Because the agent is running in that box, unless you otherwise design it, all of your secrets need to go into that box as well. And given the nature of AI, it can be unpredictable, and you could very easily end up accidentally exfilling your secrets, or other unintended behavior. Now, the out of the box is the idea that we are going to have the actual agent running not directly in the sandbox, and we will have, quote-unquote, the brain of the agent running in some type of worker, control plane. That sandbox then is going to serve as the hands where the brain is basically operating and making tool calls into that environment to manipulate it. I guess other trade-off that you're making between the two systems is that, in my opinion, running it out of the box is much more complex because, you have state that has to be managed, whereas if you're running it in the box, all of the state of that agent is actually in the box, and yes, it's you could persist it elsewhere, but it's all localized and you have less concerns to worry about.Walden [00:12:08]: I think a lot of that, what you mentioned, is why we actually from the start built Devin to what we called separate the brain from the machine. The other thing that this allows you to do is reuse any existing infrastructure you have for dev boxes Perhaps. And so you don't have to worry as much about making a new type of dev box that has all the dependencies the brain needs, as you mentioned, the secrets the brain needs as well. One thing that we've seen some customers run into is, you have a GitHub app and you want Devin, your agent, whatever, be able to interact with GitHub through this application, but then you have different users with different actual permissions. If they are all interacting through the same GitHub app and there's no actual, separation between the system that decides, what it does and the actual secrets on the machine, then you run into an issue where, okay, it's hard to do the separation. But in practice, with Devin, it's much easier because we just say whatever you put on the machine, that is, the scope of basically what the user is free to do, what the agent is free to do. So only put the most scoped secrets on that machine, and then the brain is fully not accessible from the machine. So you don't have to worry about messing with the, any of the most secure parts of the brain if the user is free to do whatever they want with the machine.Swyx [00:13:31]: I was going to just bring, I have this, chart from OpenAI, where I don't know if this is, in the box, out of the box. That is something that they do use to describe it. And then also recently Anthropic did, managed agentsSwyx [00:13:44]: Which is, this is their thing. I don't know. It's all, it's all variations of the same pattern, right?Cole [00:13:49]: So this would be out of the box.Swyx [00:13:51]: Which, is preferable for them because it's less work?Cole [00:13:56]: I would say it's more work.Swyx [00:13:58]: It's more work?Cole [00:13:58]: But it, in my opinion, it is the better architecture of the two. It's just, you're taking on a bit of complexity by doing that.Repo Setup, Docker, and VM-Based Development EnvironmentsWalden [00:14:07]: One thing I've not seen a lot of other players do well is how do you manage what's actually on the box? And this can be complex for many reasons. Let's say you have a big repository that's changing and updating a lot with changing dependencies. How do you make sure that the working environment of the agent actually stays up to date, has all the credentials it needs to, let's say, run the app and test it, and all the things you want your autonomousSwyx [00:14:34]: So a repo setup.Walden [00:14:35]: Exactly. So in, internally At Cognition, we call this repo setup.Cole [00:14:39]: The hardest part ofWalden [00:14:40]: It's been a perennial problem since the start of the company, of how do we help people get this set up? Because not everyone just has, working cloud environments working out of the box. And do you find this to be a common problem withSwyx [00:14:53]: How do you solve it?Walden [00:14:53]: Your clients?Cole [00:14:54]: This is a very common problem, and through my consulting, this is a lot of what I help teams do. A lot of teams don't really have great developer environment setups, if any. A lot of the times it's, “Go talk to Bob and get the secrets,” and that obviously doesn't work when the agent needs to actually set this up. And so a lot of that, most teams are using Docker Compose or some type of microservices. And so for theSwyx [00:15:19]: Even in prod?Cole [00:15:20]: Not in prod. With the OpenInspect, you are using this primarily to interact, and make code changes. There is other use cases, but you can hook, whether through CLI, MCPs, other tools, you can then hook that into your production systems primarily for, SRE type use cases. But you are not, necessarily, trying to test your prod internal microservice through the system.Walden [00:15:48]: And you mentioned Docker Compose. I think one direction we saw some of our friends take early on was, using Docker containers as the level of abstraction for their models. There's lots of reasons, I think, why Docker containers are not great. One thing is, Docker container's not really a true security boundary, for one. But the other is, if you are running real applications, a lot of times those applications use Docker, and then you have to think about Docker in Docker, which is, really weird. And so I think part of, the really hard challenge of getting VMs to work, why did we do that? Well, it was because we realized that you actually needed, full VMs to be able to do these types of things. And especially nowadays where there's actually value in running the application and clicking around and sending you screen recordings of these things. The value just, keeps adding on top of that. But it is a decision I see people run into when they try to build their own systems, is, “Oh, do we, in addition to this, do we put the agent in the machine or out of the machine? Do we use Docker? Do we use something else?” What do you recommend people nowadays?Cole [00:16:57]: I think Docker is a good solution for maybe not running the agent, but running your infrastructure, because that is more or less the same setup your engineers are probably already using. If they're not, then I don't know what they're using. But they're probably already using Docker Compose.Swyx [00:17:14]: I've always had a small candle for web containers. I don't know if you guys have tried them before.Swyx [00:17:19]: To me, they were, supposed to be like Docker Light.Cole [00:17:22]: Is it?Swyx [00:17:22]: I don't know.Cole [00:17:22]: No, I haven't tried it. But yeah, I think any environment that you've set up that is a good experience for your developer naturally lends itself to being easy to set up for the agent. And once you figure out that local developer story, you've more or less solved the agent in a sandbox, environment setup. OpenInspect does have hooks as well, where you can, run a setup SH script that will pre-install everything. You can then pre-snapshot that build so it starts instantly, and then there is a second hook to actually then, restore the state of the sandbox when it comes back. And so you can already have all of those microservices running and basically get the same experience that you would on your machine within the sandbox.Testing Agents: Computer Use, Screenshots, and Real App WorkflowsWalden [00:18:08]: Another thing that we've been thinking a lot about is like Different VM service offerings. Have you had customers where they needed like macOS specific VMs or like Windows specificWalden [00:18:20]: VMs?Walden [00:18:22]: There are like many technologies in the world that only work on specific types of machines, right? If you're building a.NET application that has to run on Windows or like, maybe more commonly if you want to build iOS or macOS Does that workSwyx [00:18:32]: Does Commission supportSwyx [00:18:33]: Choices like that?Walden [00:18:35]: The fundamental architecture we do, because we do the separation, it does support, but the actual work in progress is happening right now on these. Another thing that we've actually recently added support now for, it's in beta, is doing Android development. To do that, we needed to support, I think, nested virtualization within our machines because the VM itself is like a, is a virtualized Firecracker instance, and then you had to then run another Android emulator inside. And there's like weird performance issues that like, it, which is why it's like still in beta. We have to think through these problems, but it unlocks a lot for anyone who wants to do Android development.Swyx [00:19:13]: I was trying to find like a reference video for the testing thing. I couldn't find it, but I think you worked on the testing, capability. Why call it testing and not like computer use or I don't know, it's, what's the general Category of problem?Walden [00:19:26]: I think that when people think about the ability of an AI to run your app and test it, I think they actually over-index on the computer use part of it because computer use in my mind is the literal, okay, you want what button you want to click. Can you emit the right coordinates to go click that button? I think testing is actually a really interesting likeWalden [00:19:48]: Problem-solving, challenge for these AIs because if you wanted to do arbitrary testing, imagine you make a change that spans the frontend and the backend, maybe, even some other like even more deeply nested service. To actually test that change, we have to reason through what-- how do you first run these applications to orchestrate with each other with the right version of the code? Then, okay, how do I trigger the feature or how do I make the thing actually happen? And this can get arbitrarily hard, maybe you have to be an admin. Maybe a certain thing has to be feature flagged on. Maybe, you have to like run two sessions and then send us a very specific word into one of them to trigger a specific behavior. And figuring out how do you do that requires a lot of code base context, requires, a lot of orchestration that we've specifically done. And in some cases, we found that you actually, no one frontier model can actually do this full end-to-end task itself.Walden [00:20:42]: We've seen cases where we actually had to orchestrate different frontier models together to solve this problem together. That is where we spend most of our time when we think about this testing problem, not so much the computer use part. Computer use for what it's worth has gotten a lot better with recent models and it's made that part of the job certainly easier.Swyx [00:20:58]: Especially with like even 4.7, that they released yesterday, apparently like way better in terms of the vision stuff, which is going to be encompassing computer use.Walden [00:21:08]: Having evals for all these as well is something that like takes a while to build up. And having the evals be right is tricky as well. Do you ever see like, clients who are building their own agents have to start standing up evals to make sure things don't regress?Swyx [00:21:25]: Not so much evals in the traditional sense, but specific to the testing part that has just gone in. I just added support for screenshots And in theory you can also do video. I need to put in a plugin to do that. But they do show up natively, and it was a very heavily requested feature, especially after Cursor's recording came out. I think that was very enlightening for everyone of like, “Oh, this is a very good feature to actually have.”, I think with Devin you guys have had this for a while.Swyx [00:21:57]: Oh, yeah. See how screenshots work. Yeah, I don't know if there's anything, super and not obvious. It's like once what feature to build, you can just prompt it and it Will mostly work.Walden [00:22:09]: I think to Walden's point, though, the computer use is a subset of the larger testing problem, and I think that's very specific to the code base that you're working and it's not something that, out of the box that you could just solve it. The-- you do need the code base context to actually know how to test it. And I think in the case of a background agent system, you fortunately do have that code base locally that what is changing and could then inspect it and use that to drive the model.Swyx [00:22:40]: For those who haven't seen it before, this is an example of how it works. You, after the PR is done, you click testing approved, and then it sends you back a video. What I really like is that it labels, It's very small here, but it actually labels what it's testing. And then it-- and then you actually see the cursor and everything. So I don't know, yeah, the engineering in this, just Whatever you want to show. ‘cause this is like, this is one of those like, oh, few of the AGI moments, right? ‘cause Once I look at this, I actually don't I wish I can just merge inside Of Slack instead of going to GitHub ‘cause I don't need to see the code. I know it works.Walden [00:23:19]: Maybe a new feature in Cursor. Yeah, the annotations at the bottom was also a big difference for me when I, when I added those.Swyx [00:23:27]: It's just like, what am I looking at? What are you trying to demonstrate?Walden [00:23:30]: Exactly. There's a surprisingly long tail of small details that ends up making a big difference for this end metric of like how fast do you actually merge the code in. One experience that we spent a lot of time tuning early on was what is the right experience on GitHub for these tools. Because I think, most tools out there when you build the agent, you'll think about, oh, it'll create the PR for you. We try to take that a step further and say, “Oh, what if we actually made sure you could interact Devin, with direct Devin directly on GitHub?” And so we made sure that you can comment on GitHub, and Devin would actually receive those comments and address them back. But there's actually quite a bit of tuning you have to do here because you can imagine that actually like-We recently have Devin Review, for example. Devin Review will post comments on his own PR And then Devin has to then goGitHub Workflows: Devin Review, Comments, and PR AutomationSwyx [00:24:23]: He answers his own comments, which is Really loopy. So like, yeah, I like that it just updates here that it's, that I have commented But usually it's just me saying like, “Hey, merged, fix any merge conflicts.”Walden [00:24:37]: The, so when Devin fixes his own comments, you might be scared that, oh, maybe I'll infinite loop. But we've put a lot of work into making sure it doesn't, both by making sure that the comments are high signal, but also that the agent is thoughtful about what comments it immediately goes and tries to fix, and what comments it's like, “Wait a second, I think you're wrong.” Actually, that's one of my favorite moments is when Devin tells me that I'm wrong, when I try to get it to do something different. But tuning that behavior, actually makes a big difference in terms of how useful the actual GitHub experience is.Cole [00:25:06]: I think to touch on that as well, I think having the AI reviewer integrated into the system is a critical part of this background system. OpenInspect does have that. It has a GitHub code reviewer that you can control the prompt. It does do comments as well. It doesn't do them automatically yet. The capability is there, but it's not fully used.Swyx [00:25:27]: So you have to ask for it?Cole [00:25:28]: you do, yeah. You can tag it on GitHub, and then whatever you named your, GitHub bot, it will then follow up on it. It will then, if you have merge conflicts or whatever you have asked it to resolve, it will then resolve it, but it doesn't do it automatically yet.Integrations: Slack, MCP, and First-Party Agent InterfacesWalden [00:25:42]: Well, I'm curious, what is, the most common thing that people end up requesting, that they still need on top of OpenInspect when you help them go implement it?Cole [00:25:52]: I think a lot of it comes down to actually integrating it into the company. It's one thing to have the background agent system set up, but if it isn't actually integrated into your larger ecosystem, it isn't that useful. It is useful to be able to kick off sessions, but what we really want to be able to do is hook it into all of our other systems, whether that is the production database with read-only credentials, the logs, a Confluence or internal knowledge-based system. I think that is where I see the huge leap for companies, and that can be a challenge for companies as well who are maybe not familiar with exactly how to approach it, especially if they're in environments that have more compliance type things where, access control can be pretty big and how do you deliberately think about these problems, I find to be, one of the problems that comes with a system like this.Walden [00:26:46]: The thing we found is So, MCPs, obviously it has been like this, really big explosion of, oh, you can go, integrate it with all these different things. But to actually get the integration right and the and get the right experience, oftentimes we found that we had to go build our own ad hoc things. I think Slack is a great example of this. You could give your agent a Slack MCP and okay, it can post messages back to you on Slack. But we actually use Devin like a coworker in Slack, and that's how it's been built from the ground up. But to do that, you actually need to, support webhooks that come back, right? And then Devin has to respond in a natural way and then hopefully don't spam your threads too much and annoy the people in your company. So you got to tune that experience just right. Especially when there's a lot of back and forths, we find that we actually have to go beyond the simple MCP integrations in these places.Swyx [00:27:39]: I just pulled up the MCP marketplace. I know this is a Fair amount of work. Is the answer to eventually take first party control of all the top MCPs? Is that theWalden [00:27:48]: I would love a world where you could have something that's more expressive than MCP. That, goes both ways, not just a set of tools, but a proper system that interacts back and lets it Have the right experience with all these interfaces.Swyx [00:28:03]: So there actually is sampling in the MCP spec, but nobody Uses it, right?Walden [00:28:07]: And so I think that's the other part is, actually we found that when the MCP spec starts to get too complicated, it starts to lose its original promise of Being like a simple one-step connect. Now then we have to go figure out how to support all these different variations of things and It starts to look a lot like just building the first party integrations in a lot of these cases now.Cole [00:28:29]: I think it matters, too, how critical it is to your company, right? If this is something that nearly every session is going through, it probably makes sense to own it so that you can make optimizations on top of it Versus just whatever is off the shelf.Swyx [00:28:43]: Awesome. Other than MCPs, what else, sorry, well, I don't know if that's Narrowing in too much on, integrations. But what else? What other elements of building OpenInspect or Devin that you guys really sink on?Memory and Knowledge: What Agents Should RememberCole [00:28:59]: I think, a problem that comes up very frequently is this idea of memories or knowledge base.Swyx [00:29:05]: Oh, boy. How do you solve it?Cole [00:29:08]: so not solved yet, is the short answer.Cole [00:29:11]: it's something, there's a open issue for it, someone asking about it.Swyx [00:29:16]: There's, I, D Wiki hasn't indexed anything about memory yet.Cole [00:29:20]: how I'm seeing it solved across my clients is primarily through skills. I find that skills can be a good gap within that or updating Claude MD, but I think memory as a whole is a pretty unsolved problem, and it is why I've been hesitant to add it. I think there is parts of memory and that can be addressed, but I think as a whole it's a very difficult retrieval problem.Swyx [00:29:44]: Oh my God. RAMP didn't write anything about memory? I see zero search results.Walden [00:29:50]: No. Memory can be quite tricky to get right because it's the retrieval, but also the generation of the memories that can be really tricky. You don't want it to just like Remember very specific details.Swyx [00:29:59]: Walk us through the Devin memory journey because I know there's been a journey.Walden [00:30:03]: the first version of memory that like stuck around for a while was A system we have called Knowledge. And the idea was we wanted it to pick up things over time and not need the user to be proactive about teaching Devin things. So, okay, any time you remind Devin, “Wait, no, that's not quite the way you're supposed to use Git”Like, we actually want Devin to say, “Hey, do you want me to actually just remember this for the future?” And for you to just basically quickly approve or reject and for it to build up over time. ‘Cause I find that, 95%, I think, or some crazy stat like that of the memories that Devin has are all through these auto-generated things. Very few people actually just want to sit down and write big docs on Here's how you're supposed to work with the technology, et cetera. The generation and the retrieval has been something that we've been trying to tune a lot over the years. Generation, you don't want it to remember something like, if you asked one time to like, “Oh, please open as a draft PR,” you don't want to be like, “Oh, everyone forever now should get their PRs as draft PRs.” But you do want some, conveyor. Maybe you want to say like, “Oh, Cole generally likes, things to be created as draft PRs.” Same with retrieval, if you have thousands of these memories, how do you actually make sure they're retrieved at the right time? And that can be quite tricky to do right without exploding the context with a bunch of useful yeah, useless information. Surprising amount of just, eval work to just make sure that, memory is, remains a reliable system as new models come and go.Cole [00:31:31]: Do you have anything that you could share on, memory pruning? And like the temporal aspect of memory?Swyx [00:31:36]: Deleting and forgetting?Walden [00:31:39]: The, today, the, So the things they could do is it could edit memories. And so if your memory used to say like, “Oh, Cole likes to open everything as like a draft PR,” then you can imagine, “No, don't do that.” And then it'll say, “Oh, do you want me to update the memory to be Cole now want everything as, open PRs?” I think that at the same time we don't know if this is going to be the final version of the system. Whatever we have here will probably, translate into the new system that we'll be coming up with. But I think one big difference between two years ago and today is these agents are really good at using anything that resembles a file system natively. And so part of us are, is thinking, “Oh, should we rebuild memories to feel more like a file system that we let the agent navigate on its own?” That's been an interesting exploration. Also similar ideas in the scale space.Swyx [00:32:35]: I am pulling up OpenClaude's memory thing right now. So memory, OpenClaude has like this like daily memory journal thing, right? And you can I mean, that is a file system you can grep through and is a source of truth. I don't know if it's the best. It's probably super noisy, but at least, if you lose something you can discover it or you can apply some, forgetting algorithm to, more ancient memories that don't get recalled again or something. I don't know.Walden [00:33:01]: One thing we've been trying to do to push the boundaries of how you use agents at your company is letting an agent basically have a very similar file, a memory.md or something, and just like be your permanent PM for a specific set of issues maybe. So we have like some Slack channels internally, maybe a Slack channel dedicated to, a specific product like DeepWiki maybe. And you can imagine that, or you want a Devin that never stops, it's just always awake, but it has this like memory dock that it can just maintain for itself about, okay, what are like the number one priorities of what we have to fix and prioritize? Who is responsible for some upcoming work? Maybe they'll even Devin will even tag you on some recurring basis. And so it's been an interesting move to see, okay, how can we actually use Devin for more than just engineering? Can we actually upstream above the engineering process and maybe it's just Devin creating tickets, which then maybe some humans do, but then maybe other Devins do.Swyx [00:34:00]: One of my more fun automations is go research competitors and just suggest stuff to me on a weekly basis. That's the automation. I can't find it right now, but basically it just like, “Look at competitors and suggest things.” “And here are three things that you've suggested that I don't want any more of,” and you just stick that in the prompts. But like I wish actually So for like when I, for example, when I reject a PR, I wish that it updated memory so that I can then just not have to go up, go back and update the scheduled, sync, but anyway, feature request.Walden [00:34:31]: what? We might change it soon. I guess OpenInspect, in the time you've been around, has there been anything you tried to implement but then you had to like undo and like do a different way?OpenInspect Architecture: Webhooks, Control Planes, and Agent StateCole [00:34:41]: Nothing yet, but something that is on my mind. The initial way that I built it was that each of the integrations lives as its own package. And so you have The Slack bot, which is what's handling the webhooks, and then is basically interacting with the control plane. As I'm seeing the system starting to be more integrated, specifically with the GitHub bot integration, I'm considering bringing that all into the central control plane because especially now I want to start, And a request that I'm getting is the ability to monitor, the actual, pull requests being merged, as well as just tracking ofSwyx [00:35:19]: What do I have open?Cole [00:35:21]: What do I have open? How many of these are getting merged? How many comments are showing up? To just understand the health of the system. And so in the case of a GitHub app, you only have one webhook. And so then it's a question of do I put that webhook in that GitHub bot package? That's weird. It doesn't really make sense to live there because that package is more for like the code reviewer. Or do I like centralize it? So that's something that's on my mind of, making that decision. I think the other one we touched on earlier is the harness in the box versus out of the box. I think long term the architecture will eventually come back out of the box. Some of the newer tools that I've added are calling back into the control plane so that you don't have the secrets in the sandbox. And so I think long term I probably will pull the actual, agent out of the box, but I think for now it's fine.Subagents and Multi-Agent Systems: When Parallelism Helps or HurtsSwyx [00:36:16]: Just, a quick question on pulling the agent out of the box. I'm One thing I'm very bullish on this year is agents calling other agents or spawning sub-agents or Whatever you want to call it. Does that make it harder or easier? I can't tell. Because if the harness is in the box, you can just spin up more boxes. If the harness is outside the box, then you're, it's less easy because you are, you have a unicorn pet of a, of a harness that's, living outside the box.Cole [00:36:45]: In theory it would be the same way, right? Whether, one agent has launched many, sub-sessions within it, OpenInspect, for example, can launch sub-sessions and actually create other environments and then monitor them. In the case where it is out of the box, that would basically just be an additional session that's running. And so that session is also running outside of the box. It's running in your worker plane, wherever you're running this. And then you really just have to think about how does your top level agent then interact with it. I do think it can be more complex, just ‘cause again, you have now a more difficult architecture. But I think if you figured it out once, it's probably fine.Swyx [00:37:26]: Well, then I'm just, throwing it open to you in terms of, I call this like meta Devin management. Which is like the, Devin's calling Devins or Devin scheduling Devins or querying trajectories or anything like that. What have you built or unshipped, anything?Cole [00:37:46]: I think one of the surprising things we've seen is that a lot of the ways that, these, separate agents work with each other, and you want them to, parallelize their work, has still mostly followed the same manager sub-agents regime. And a lot of people I think are excited about this world where you have swarms of agents that, talk with each other all over the place. We've actually given Devin an MCP so they can just go arbitrarily message other Devins And create new Devins, et cetera. But I guess, it somehow creates, a really chaotic world in that sense. And so we've still found that most practical use on a day-to-day basis has been one single Devin.Cole [00:38:33]: Figuring out how to segregate the work and get, have other Devins work on it in, a relatively isolated sense, each with their own boxes Not sharing machines, so there's, a very little room for conflict is the regime that you have to create today.Swyx [00:38:50]: I'll call out, the experiments from Cursor, right? This is Wilson Lin's work on Single agent to multi-agent, and you're obviously famously on the side of don't build multi-agent. But they went through the whole thing, only to arrive at, this Which is exactly what Devin has, I think.Cole [00:39:08]: I think there will be a revision to that post at some point AboutSwyx [00:39:12]: Tell us about itCole [00:39:12]: I think multi-agents were very much not at all possible a year ago. You do see more multi-agent experiments today, but you can argue, are they really multi-agents, or are they just just, tool calls,? There are people who, will create sub-agents to go look for XYZ file, XYZ implementation. Has really nice context management benefits because all of the tool calls and tokens that it spends then get collapsed back to just the answer for the main agent. There's a lot of benefits to doing this. We basically have Devin do this with Deep Bookie, make a call out to Deep Bookie, give you back the results, but that feels like a tool call,? It's not like these, two collaborators actually talking back with each, back and forth with each other. But I think the thing that gives me the most bullishness that multi-agents might actually be possible is actually what I said earlier about Devin will actually sometimes tell me I'm wrong and push back, and I think that demonstrates a level of maturity and communication today that makes a multi-agent world possible. One, can two agents who have seen different information come back to each other and actually figure out who is right, what is the correct implementation? They're not just, yes men. Claude, I guess is like, used to just say, what is it? “You're right,” or,Swyx [00:40:25]: “You're absolutely right.”Cole [00:40:26]: “You're absolutely right.” Yeah.Swyx [00:40:28]: The Have you seen, did you seeCole [00:40:29]: The age is overSwyx [00:40:30]: The Codex app troll in Topic? This is the Codex app. Inside of Settings, there's a little, there's a little Easter egg, right? So if you go to, the Themes or Appearance, right? There's all these, color codes, and the top is absolutely, and it's the Topic's colors. Which is such a troll. Anyway.Model Behavior: Pushback, Adversarial Prompts, and Agent SkepticismCole [00:40:53]: I love that Easter egg. Did you discover that yourself?Swyx [00:40:54]: No, it was, someone was, tweeting about it And I was like, I was like, “Is this true?” Because, sometimes people just tweet stuff to, get a rise out of you. But yeah, there you go, in Topic colors.Cole [00:41:06]: Yeah. So yeah, we're out of this regime where, it just says you're absolutely right, and they can have real conversations and real back and forths.Swyx [00:41:13]: You can prompt it as well to be more adversarial or whatever. Yeah. Okay. Yeah, that, I mean, to me, that is more intelligence, right? That is not just something that's, a dumb tool, it's actually pushing back on you I think. Yeah.Cole [00:41:24]: when you mentioned, of course, the blog posts. There was one blog they had where they fed a swarm of agents together and built a browser.Swyx [00:41:34]: That was I think that was the one.Cole [00:41:36]: You can have, likeSwyx [00:41:37]: I think it's the same oneCole [00:41:37]: Creation of it. We found a surprising success of, don't do a swarm or anything, just have one Devin, it does its own context management. Just let it keep running for a while and give it some crazy tasks. I think we asked it to, rebuild, a Windows OS system. And it managed to do it just like, going on for long enough. It'sSwyx [00:41:55]: Was this Andrew's thing?Cole [00:41:58]: there were lots of demos that we ended up not posting, ‘cause at some point we'd just be posting way too much a bunch of, Demos. But I love that because it shows that I think the multi-agent thing still has, a bit of exciting sexiness to it, which is maybe still beyond still, the actual delta it adds to the capabilities of these systems. But it's absolutely the future. I think we're heading in that direction and we can see the progress being made there already.Swyx [00:42:25]: If I were to, make one super minor pushback because I don't feel that confident about it yetCole [00:42:33]: Go for itSwyx [00:42:33]: But I've had Ryan Lopopolo from OpenAI on the pod And he's a super slop cannon, right? Oh my God, that's my coding agent being done. I downloaded this, Peon Ping. I don't know if you guys have heard this. It takes like-, sound packs from popular games like, Command and Conquer and Warcraft, and then it plays it whenever it's done. And so it's like, “Work,” or whatever, “At your command,” or something. Anyway, what I got from the Cursor code base and from Ryan's thing was that there's a slop cannon approach where you try to loosen the single agent's, bottleneck, and I feel like that is, probably an, a very important thing to try to figure out. I don't think anyone's, really solved it. Because then you just have more reviewer slop on top of the agent slop To try to wrangle it all. Ryan will probably very strongly object that I say that he hasn't solved it, but he thinks he's He thinks he's completely solved it. But I think it's still I think it's, very important, ‘cause, that is a bottleneck, right? I feel Devin is slow sometimes Because I'm like, well, yeah, this is very readable and very sensible, but also it is slower than it could be if I just, I want a button to just say, “Just ramp this up 1,000 next parallel, in parallel and just, see what happens,”? And I don't know if that's, feasible at some point in the future.Code Review, Entropy, and AI SlopWalden [00:43:55]: I And we've also run experiments internally where we've basically tried to build entire products, true products that we knew we would eventually ship, but for now, let's try to see if we can do it just by purely, vibe coding on top of each other, auto merge, no code review at all. And then there's this benchmark of how many weeks can you go onto this for Before you say, “We have the trashiest code base.”Walden [00:44:18]: “Let's actually rewrite it from scratch.”Swyx [00:44:19]: Start a new factory, yeah. What'd you find?Walden [00:44:21]: I think we found that the state-of-the-art in December was you can probably, run this for about two weeks. By the end of those two weeks, you'd find that, hey, you want to, change the color of a button. Well, it turns out this button is implemented in, 10 different places, and they, have All these different variations, and oh, you forgot one of them, and actually it's a slightly different color in one spot. And you're like, “Okay, this is too much to work with. Let's actually try to do code review at the same time.” And make sure that we're on top of our software, actually cleaning it up a bit And making sure it's done in a scalable way.Cole [00:44:54]: I think building on that, the idea of, you don't have to look at code, I think is generally a bad idea. And the meme that I have for thatWalden [00:45:03]: What timeline, all right, is Do you think that statement will be true on?Cole [00:45:06]: I think probably for a while it'll be true that you should continue to look at your code. A problem that I see a lot of teams run into that I work with who are embracing AI native, AI first coding, is The meme that I have is that your code base regresses to your worst engineer, because that engineer who is, very gung-ho about AI and is not auditing their code, their pattern starts cementing into the code, and now the AI is referencing their patterns. And so now their if/else block that, is 20 if/elses back and forth, the AI is seeing that as the pattern of how things are done and starts to then exponentially grow this slop. And I find to your point, a pretty good approach to that is having scheduled cleanup, whether by humans or through systems, that are looking for duplication. They then address that. You'll end up with like 12 helpers for how to format a date. And you need to address that, because otherwise it will continue to sprawl.Swyx [00:46:09]: Within balance, I think it's fine to have some duplication, and then sometimes To have garbage collection, right? Yeah. The What I've been, talking about with a lot of engineering leaders is that you want to be very strict about the boundaries between modules, and it's your job as an architect, as a CTO, whatever, to say like, “Okay, here's the hard contract between you guys and you guys. Whatever you do inside this black box is your business. You do whatever. But between these guys, let's be, really damn clear, and any movement must be signed off by a human or me,” or. Then, and like that's that. I don't know if you have any other modifications or advice.Walden [00:46:44]: Well, I guess generally on the topic of, where humans can be useful, I found that ‘cause, some of these, really deep infra problems, sometimes just having a human that just has, really deep expertise can make a big difference. I've actually seen this come into play when actually building agents. So we've had a few friends now, try building their own coding agents, and I think one same problem that I recurringly heard a lot of them run into was this problem of like, “Oh, Grep is really slow on our agents' machines.” And so a lot of them, I assume because they're using AI and they themselves don't have, super deep infra background knowledge, say, “Okay, we're going to go build our own custom Grep index. It's going to be really fast,” and use that as a way around this problem. When we ran into this problem About like, maybe like a year and a half ago when we were, in the early days of building Devin, we obviously didn't have AI then. We just asked our, how to, how to do this. You can just swap out a new Grep index, so.Infrastructure Details: Grep, File Systems, and SandboxesSwyx [00:47:45]: What do you mean you hand-coded Devin? What?Walden [00:47:48]: It's like, can you believe we hand-wrote this code? And we had, our infra people who are really amazing, they were looking into it and they're like, “Oh, what? We realized that actually the root cause of this problem is actually super simple, but like fine-grain detail,” which is that a lot of these virtual machines actually underlying them don't use real file systems. They use these, network file systems where things are actually cached over the network actually in S3. So when you're Grepping, you're actually making network calls Every time you're doing these things, and that's why Grep is extremely slow on these machines. And so again, goes back to, what is all of the crazy infra work that we had to do to actually get these machines working. If you try to do this yourself, there are tons of small details like this, and so we had to eventually go swap out that network file system. ButSwyx [00:48:35]: I think there's a write-up about it, right? Silas did one about the virtual file system.Walden [00:48:38]: Oh, that was a whole other thing. TheSwyx [00:48:39]: Oh, that's a different thingWalden [00:48:40]: The BlockDev file storage formatSwyx [00:48:42]: I'll bring it upWalden [00:48:42]: Which is, a file system format that we built so that the VMs could be spun up and down very quickly. Basically, the intuition behind this is-Imagine you have, a terabyte of disk, and your agent only, wrote, a hundred lines of code on top of that disk. How long does it, say, take to, save and re-bring up that disk? And most systems, because you're not optimizing for this case, it's just, on the order of a terabyte of work because you have to Save all of that and bring it back up. In our system, we try to build a file system that incrementally builds on top of each other. So every time you save and bring the machine back up, you're only doing work that is proportional to effectively the diff in the file system. And so this, shaves off a lot of time in the boot-up process of Devin. I think we This is actually now outdated. We have a newer system inside of Devin. But yeah, there's a lot of tiny details you have to get right here to actually get the day-to-day experience of Devin to be good.Swyx [00:49:39]: It's, not technically agents, but it is agent infra, and when you sell an agent as a company, you sell agent plus agent infra.Walden [00:49:46]: At least the way we do it be And the other The nice thing about having the agent infra being done together is, you We get to deploy Devin in whatever environment we want now. We don't need to wait for some underlying infra provider to also go and support VPC or on-prem or FedGovCloud, for instance. So we can actually go and figure out, okay, since we own the infrastructure, how can we get that set up for you?Cloud Providers: Modal, Daytona, and Enterprise SandboxesSwyx [00:50:12]: Whereas you're Cloudflare dependent.Cole [00:50:15]: so Cloudflare runs the control plane. The sandboxes, Modal is supported. A contributor just added Daytona. E2B is on the roadmap, and I think there's an abstraction in place that if any contributor wants to add a new provider, they can add that in.Walden [00:50:32]: Well, what are, How are the customers you work with Do they generally try to then go set up a contract with another one of these third-party providers? Do they try to do the VMs in-house?Cole [00:50:44]: most of them I see using Modal. I think Modal has a greatWalden [00:50:48]: Shout out Modal.Swyx [00:50:48]: Shout out Modal.Cole [00:50:50]: I think Modal has a great offering. It captures all of the sandbox pieces you need, snapshots being a pretty big piece of that, and given that they also offer GPUs, I think it's a pretty nice offering as a whole.Swyx [00:51:04]: no debate there.Walden [00:51:07]: Modal is great, especially, I think their container offering is, the most natural, and so especially if you are willing to, forego, the full VM requirements Modal is, a really vast place you can spin something up on.Swyx [00:51:20]: Is there a point So Modal's very Python, and I feel like most workload, has really shifted to JavaScript. I don't know if you guys Get the same feeling. So, okay, when I started Landspace and IE and all these things, I was like 50/50 Python and JS, right? That's roughly. I think that's wrong now. I think JS has won. I don't know if you guys Like, I Maybe I'm overstating it, and maybe for cognition, there's, C# and Java and what have you. But for, new greenfield apps, do you feel that Do you get that sense? Does it matter?Cole [00:51:52]: I think that most of the libraries that I see in this space are Python native first, especially in theCole [00:51:58]: Observability space. That said, I think that there is a pretty big appeal of having your entire system in one language. Especially when you have both your frontend and backend communicating, you can have one central type Which is very nice.Swyx [00:52:11]: That's my case against Modal, which is Then you have to run JS. You can run JS inside Modal. It's just, one extra step That, isn't native to the runtime. I don't know ifWalden [00:52:22]: I don't knowSwyx [00:52:23]: Reviews. Do you have numbers? I don't know.Walden [00:52:25]: the one thing I don't like about Python is whenever AI, whenever it writes Python, it always does, the weirdest patterns, andSwyx [00:52:32]: Oh, because it's, mixing two and three or what?Walden [00:52:34]: I think it's something mixing two and three, yeah. The I don't know if you see this. It always tries to do, has attribute on objects as likeCole [00:52:41]: Oh, my God.Walden [00:52:41]: But it's like But that you shouldn't be doing that. It should error if there wasSwyx [00:52:45]: Because it's training on library code?Cole [00:52:47]: I think it's more of, likeCole [00:52:48]: From what I've seen, it's more of, a reward hacking mechanism where it doesn't want to basicallyWalden [00:52:54]: It'll never error.Cole [00:52:54]: It doesn't want the code to fail. And so it Even when it knows it has the attribute, it'll call getattr on a, and for a lot of my clients who have moved towards more autonomous coding, we've put that in as a lint rule That if you do getattr, your pull request is going to fail.Slop Signatures: Comments, Backwards Compatibility, and TypesSwyx [00:53:12]: Ooh, this is a fun topic. Can you tell me more about this? What else is a sign of AI coding that you have to put guards in?Walden [00:53:21]: So we were talking just before this about Opus 4.7. One of the things this new model likes to do is it writes lots of comments. Not like, it'll, comment every line, but it'll write, paragraph, PRDs, on top of every function. But I will say, to its credit, these aren't slop, descriptions like they were before. “Oh, here's what this function does.” It's like, “Oh, here's actually the r

Hi Spring fans! In this installment I talk to my friend, of JClarity and Microsoft fame, fellow Java champion and Java guru Martijn Verburg

#352: Vibe coding is the latest version of a promise the industry has been making since the first generation of programming languages. Type what you want, get an app. Jeff Kuo from Ragic has been working on the no-code version of that same promise for almost twenty years. He has thoughts on why the promise keeps not quite landing. The honest answer is that AI-assisted coding is great for people who already know what the code is doing. It is counterproductive for everyone else. A non-developer can generate a lot of code. They cannot maintain any of it. That gap is where every weekend vibe-coded project goes to die six months in, when the codebase has ballooned and the AI is in a loop confidently identifying the wrong root cause for the seventh time. So what does work? Jeff's argument is that no-code platforms become the guardrail AI actually needs. Strip the infrastructure layer away, leave only the business logic, and the model only has to reason about one thing at a time -- which is the one thing today's models are good at. Ragic generates form and report definitions, not code, and the Java engine underneath does the rest. There is also the strange consumer behavior nobody is talking about. People love AI chat boxes in tools they have never used before. They close AI chat boxes in tools they already know. Which means the future of AI-native software might not belong to the incumbents at all -- it belongs to the new tools being built right now for users who do not have any muscle memory to defend. And one piece of advice that has aged perfectly across forty years of software: the maintenance is the thing that keeps you awake at night. AI makes it faster to build things from scratch and harder to maintain anything at scale. Begin with the end in mind. Or do not, and become the next cautionary tale.   Jeff's contact information: LinkedIn: https://www.linkedin.com/in/ragic/   YouTube channel: https://youtube.com/devopsparadox   Review the podcast on Apple Podcasts: https://www.devopsparadox.com/review-podcast/   Slack: https://www.devopsparadox.com/slack/   Connect with us at: https://www.devopsparadox.com/contact/

Sometimes you need to look back and see God in your past to help you trust Him for your future.  In this episode, author and speaker Laurie Polich Short will show you how what felt like a detour may have actually been divine direction. Whether you've experienced closed doors, extended seasons of waiting, or deep disappointment, you'll be reminded that God is present in every part of your story. Laurie will help you trace God's fingerprints all throughout your life—even in the moments that were confusing, painful, or unexpected—and invite you to release your expectations of how He "should" show up so you can begin to recognize how He already has. Plus, be sure to listen until the very end because I'm singing a special blessing over you! SHOW NOTES: 413Podcast.com/403  Read the episode TRANSCRIPT in the show notes. Get my weekly email, Java with Jennifer, to be notified when a new podcast episode releases. Subscribe HERE.

What if the Jesus you know has been shaped more by culture than by Scripture? All too often, we create a customized Jesus to fit our preferences instead of following the true Jesus revealed in God's Word. And without even realizing it, He becomes the Lord of our comfort and convenience instead of the Lord of our lives. So today, pastor and bestselling author Kyle Idleman will give us a clear understanding of who Jesus is as Messiah and King! He'll unpack how our view of Jesus can quietly drift, how to recognize when we've turned Him into a life coach instead of a King, and what it looks like to follow Him for who He truly is. SHOW NOTES: 413Podcast.com/402  Read the episode TRANSCRIPT in the show notes. Get my weekly email, Java with Jennifer, to be notified when a new podcast episode releases. Subscribe HERE.