Podcasts about Compaction

Sherri Harrah continues the show on Sunday May 31, 2026 from Her garden helping with Virginia Button Weed, mosquito control, Lawn compaction, How to build a great garden bed, squash mildew and fruit trees as heard weekends on SportsRadio 610 The post Virginia Button Weed, Mosquito Control, Compaction, Garden Beds, Squash, Fruit Trees -260531-H2 appeared first on HomeShow Garden Pros Radio.

Java 26 est là, GraalVM cartonne chez Trivago (43 à 12 réplicas !), OpenJDK interdit le code généré par LLM, Spring et Quarkus enchaînent les releases. Côté IA : ADK 1.0, A2A, Lyria 3 chante (mal ?), Yann LeCun lance Ami Labs et ses World Models. Mythos d'Anthropic fait trembler la sécu, Claude Code a leaké son source, et les git worktrees envahissent vos terminaux. Bonus : la mort annoncée de l'IDE, vagues de licenciement chez Oracle et Block, et nos voix toutes clonées. Bon week-ends de mai ! Enregistré le 7 mai 2026 Téléchargement de l'épisode LesCastCodeurs-Episode-340.mp3 ou en vidéo sur YouTube. News Langages Retour d'expérience d'une migration vers graalVM chez Trivago https://medium.com/graalvm/inside-trivagos-graalvm-migration-native-image-for-graphql-at-scale-912bca9df841 La passerelle GraphQL de Trivago (point d'entrée de tout le trafic vers 48 microservices) souffrait de pics de timeout au démarrage JVM Résultats spectaculaires après migration vers GraalVM Native Image : réduction des réplicas de 43 à 12, CPU de 15 à 5 cœurs, images Docker plus légères Obstacles techniques : incompatibilité Log4j → migration vers Logback, remplacement de Mockk par Testcontainers, compilation CI/CD très gourmande Netflix DGS et d'autres librairies manquaient de support GraalVM → l'équipe a contribué des correctifs upstream en open source Approche recommandée : commencer par les services les moins complexes, investir massivement dans les tests automatisés À la 14e migration, le processus était si rodé qu'il allait plus vite que la toute première tentative OpenJDK Interim Policy on Generative AI - https://openjdk.org/legal/ai OpenJDK adopte une politique intérimaire interdisant toute contribution incluant du contenu généré par des LLMs, modèles de diffusion ou systèmes deep-learning Le périmètre est large : code source, texte, images dans les dépôts Git, pull requests GitHub, emails, pages wiki et issues JBS Les contributeurs peuvent utiliser les outils d'IA de manière privée pour comprendre, déboguer et relire le code OpenJDK, mais ne peuvent pas contribuer le contenu généré Trois risques justifient cette politique : surcharge des relecteurs face au code plausible mais incorrect, risques de sûreté/sécurité pour une plateforme critique, et risques de propriété intellectuelle (l'OCA exige que les contributeurs possèdent les droits IP de leurs contributions) Même éditer partiellement du code AI-généré ne le rend pas acceptable à la contribution Oracle, sponsor corporatif d'OpenJDK, travaille sur une politique complète à soumettre au Governing Board GraalVM Native Image et la Closed-World Assumption en Java https://pvs-studio.com/en/blog/posts/java/1357/ Un bon article de rappel du contexte de closed world en Java GraalVM Native Image compile les applications Java en exécutables natifs statiques, sans JVM au runtime. La JVM fonctionne en monde ouvert : les classes sont chargées à la demande, les appels sont des références symboliques résolues dynamiquement. Native Image impose la "closed-world assumption" : tous les chemins d'exécution doivent être connus à la compilation. Les fonctionnalités dynamiques Java (réflexion, proxies, chargement de classes) créent des chemins cachés invisibles à l'analyse statique. C'est pourquoi Native Image exige des fichiers de configuration explicites pour la réflexion, les proxies, les ressources et la FFM API. L'article illustre le problème avec la Foreign Function & Memory API pour appeler printf natif : fonctionne sur JVM, échoue en Native Image sans config. Inclure tout le bytecode accessible serait inutilisable : binaire géant, compilation très lente, et la réflexion nécessite des métadonnées précises. La configuration n'est pas un défaut de conception mais une conséquence logique du passage du dynamique au statique. Java 26 : les nouveautés https://foojay.io/today/java-26-whats-new/ Java est le langage de la JVM, publié tous les 6 mois depuis Java 9 ; Java 26 est une version non-LTS avec 10 JEPs. JEP 500 : protection des champs final modifiés par réflexion profonde, avec des avertissements configurables. JEP 504 : suppression définitive de l'API Applet, plus supportée par les navigateurs. JEP 516 : le cache AOT (Project Leyden) fonctionne désormais avec n'importe quel garbage collector. JEP 517 : support HTTP/3 dans le client HTTP, HTTP/2 reste le défaut mais HTTP/3 est accessible à la demande. JEP 522 : amélioration du débit du GC G1 en réduisant la synchronisation entre threads applicatifs et threads GC. Nouveau support des UUIDv7 via UUID.ofEpochMillis(), naturellement triables et adaptés aux identifiants de bases de données. Process devient AutoCloseable, utilisable dans un try-with-resources. Aucune fonctionnalité en preview n'est graduée en standard ; Structured Concurrency en est à sa 6e preview. Librairies Guillaume a créé une petite librairie Java sans dépendance pour extraire le JSON d'une réponse d'un LLM un peu verbeux https://glaforge.dev/posts/2026/03/22/extracting-json-from-llm-chatter-with-jsonspotter/ Les LLM génèrent souvent du JSON, mais il est parfois entouré de bla-bla et/ou contient des erreurs (ex: commentaires, virgules finales) qui bloquent les parseurs JSON standards. Guillaume a créé une petite librairie légère sans dépendance pour localiser et extraire la structure la plus longue ressemblant à du JSON (même malformé) On peut ensuite passé cette chaîne à un parseur "lénient" (plus tolérant) comme Jackson pour ensuite avoir de bons vieux objets Java fortement typés Librairie dispo sur Maven Central ADK Java sort sa version 1.0 (Agent Development Kit par Google) https://developers.googleblog.com/announcing-adk-for-java-100-building-the-future-of-ai-agents-in-java/ ADK est un framework open source de Google pour créer des agents IA, initialement en Python, maintenant multi-langages (Python, Java, Go, Typescript). Nouvelles fonctionnalités majeures : Outils puissants : GoogleMapsTool, UrlContextTool, ContainerCodeExecutor, VertexAiCodeExecutor, abstraction ComputerUseTool. Architecture de plugins centralisée : Nouveau conteneur App pour gérer les Plugins à l'échelle de l'application (ex: LoggingPlugin, GlobalInstructionPlugin). Context engineering amélioré : Compaction d'événements pour gérer la taille des fenêtres de contexte (résumé et rétention). Human-in-the-Loop (HITL) : Supporte les workflows ToolConfirmation pour approbation humaine des actions d'agent. Services de session et de mémoire : Contrats clairs pour la gestion de l'état (InMemory, VertexAI, Firestore) et la mémoire à long terme. Support Agent2Agent (A2A) : Collaboration native entre agents distants de différents frameworks via le protocole A2A. Dans cet autre article, Guillaume partage comment il a développé l'application Comic Trip montrée dans la vidéo YouTube et qui utilise ADK 1.0 https://glaforge.dev/posts/2026/03/30/building-my-comic-trip-agent-with-adk-java-1-0/ Nouvelle version du SDK Java pour Agent2Agent Protocol, avec le support de la version 1.0 de la spécification https://medium.com/google-cloud/a2a-java-sdk-1-0-0-beta1-released-e83c414b34cc Alignement avec la version 1.0 de la spécification Nouveau groupId org.a2aproject.sdk et package org.a2aproject.sdk Protocoles de transport : support complet et équivalent pour JSON-RPC, gRPC et HTTP+JSON/REST. Gestion des erreurs : introduction de codes d'erreur et détails structurés pour une meilleure observabilité. Optimisation HTTP : ajout d'en-têtes de cache pour les métadonnées des agents (Agent Card). Flexibilité du client HTTP : support par défaut du JDK HttpClient, avec option Vert.x pour les environnements Quarkus. Nouvelles fonctionnalités techniques : méthode DataPart.fromJson() pour la création simplifiée d'objets depuis du JSON brut. Prochaines étapes (v1.0.0.GA) : support simultané des versions 1.0.0 et 0.3.0 du protocole pour assurer l'interopérabilité. JPA 4.0 Milestone 2 : nouvelles fonctionnalités pour Jakarta Persistence https://in.relation.to/2026/04/23/JPA-4-M2/ Jakarta Persistence (JPA) est la spécification standard Java pour le mapping objet-relationnel (ORM), implémentée notamment par Hibernate. JPA 4.0 M2 est la deuxième milestone de la prochaine version majeure de la spécification, annoncée par Gavin King. Construction de requêtes Criteria à partir de chaînes JPQL, offrant plus de flexibilité dans la composition dynamique des requêtes. Nouveaux types d'expressions spécialisés (TextExpression, NumericExpression) pour simplifier l'écriture des requêtes Criteria. Nouvelle interface FetchOption pour contrôler explicitement la stratégie de chargement des associations, dont un BatchSize intégré. Nouvelle annotation @EntityListener qui découple les classes entités de leurs listeners, supprimant les dépendances à la compilation. Les listeners peuvent cibler plusieurs types de callbacks et s'appliquer globalement à toute l'unité de persistance. Introduction de FlushModeType.EXPLICIT et QueryFlushMode pour un contrôle plus fin de la synchronisation avec la base de données. La méta-annotation @Discoverable permet de placer des annotations comme @NamedQuery sur n'importe quelle classe ou interface. Améliorations du DDL via @Index amélioré et clarifications de la spécification via la javadoc. Quarkus 3.35 : tree-shaking, PGO et AOT Semeru https://quarkus.io/blog/quarkus-3-35-released/ Quarkus est un framework Java cloud-natif optimisé pour GraalVM et HotSpot, conçu pour les microservices et les environnements conteneurisés. Nouveau JAR tree-shaking expérimental : analyse des dépendances à la compilation pour supprimer les classes inutilisées. Sur le CLI Quarkus, cela supprime plus de 6 000 classes et économise environ 18 Mo (39,5 %). Support du Profile-Guided Optimization (PGO) pour les builds natifs via quarkus.native.pgo.enabled=true. Le PGO est une fonctionnalité Oracle GraalVM, non disponible dans la Community Edition. Support de l'AOT IBM Semeru : le démarrage passe de ~380 ms à ~190 ms dans les premiers tests. Nouvelle extension quarkus-reactive-transactions : support de @Transactional pour les méthodes Hibernate Reactive retournant Uni. Configuration CORS dédiée pour l'interface de management, indépendante de l'interface HTTP principale. Les tests n'utilisent plus les System Properties pour la propagation de configuration, facilitant la parallélisation future. Le serializer jackson sans reflection n'est pas le default du aux retours de cas limites, encore du travail This Week in Spring - 21 avril 2026 https://spring.io/blog/2026/04/21/this-week-in-spring-april-21-2026 Spring Framework 6.2.18 et 7.0.7 corrigent trois failles de sécurité : DoS via fichiers multipart WebFlux, empoisonnement de cache de ressources statiques, et DoS sur Windows. Le support open source de Spring Framework 5.3.x et 6.1.x est terminé, la migration est recommandée. Spring Data 2026.0.0-RC1 introduit l'upsert (MERGE/INSERT ON CONFLICT) dans l'API Template de Spring Data Relational. Spring Data ajoute un RedisMessageSendingTemplate pour la cohérence avec les listeners Redis, et une optimisation de réinitialisation de caches en un seul appel. Spring AI introduit une Session API (série Agentic Patterns, partie 7) : architecture event-sourcée pour la mémoire des agents IA. La Session API supporte la compaction turn-safe, l'isolation de sous-agents en parallèle, et la persistence JDBC (PostgreSQL, MySQL, MariaDB, H2). Elle vise Spring AI 2.1 (novembre 2026) et remplacera à terme l'API ChatMemory. Spring Vault 4.1.0-RC1 et 4.0.2 sont disponibles. Netflix a présenté son usage de Java, Spring Boot et Spring AI dans une vidéo. This Week in Spring - 28 avril 2026 https://spring.io/blog/2026/04/28/this-week-in-spring-april-28-2026 Cette série hebdomadaire de Josh Long compile les nouveautés de l'écosystème Spring : articles, outils, podcasts et annonces de la communauté. Spring Boot 4 introduit un package natif de résilience org.springframework.resilience avec une nouvelle API de retry qui remplace les approches fragiles via Spring Retry ou Resilience4j. L'API retry native de Spring Boot 4 a des noms d'attributs et sémantiques différents des anciennes bibliothèques, rendant les tutoriels pré-2025 obsolètes et sources de bugs silencieux. Le SDK Spring AI pour Amazon Bedrock AgentCore est disponible en GA : il intègre les capacités AgentCore dans Spring AI via annotations et auto-configuration. Le SDK AgentCore gère automatiquement le contrat runtime AgentCore : endpoint /invocations, health check /ping, SSE avec backpressure. Il offre mémoire court terme (sliding window) et long terme (sémantique, préférences, résumé, épisodique), ainsi que des outils pour navigateur et exécution de code en sandbox. Un plugin Maven (Nullability Maven Plugin) simplifie l'intégration de JSpecify et NullAway pour enforcer la null-safety à la compilation dans les projets Java. Le plugin génère automatiquement les fichiers package-info.java par package et configure le compilateur pour traiter les violations de nullabilité comme des erreurs. Josh Long et Dr. Venkat Subramaniam ont co-présenté à Voxxed Days Amsterdam sur "Intelligent Kotlin", avec un épisode de podcast associé. Cloud Amazon S3 Files https://aws.amazon.com/about-aws/whats-new/2026/04/amazon-s3-files/ Amazon S3 Files est un nouveau service donnant un accès système de fichiers direct aux données stockées dans les buckets S3 Basé sur la technologie Amazon EFS, il supprime la barrière entre stockage objet et interface système de fichiers sans dupliquer les données Débit en lecture pouvant atteindre plusieurs téraoctets par seconde ; des milliers de ressources de calcul peuvent y accéder simultanément Les données restent accessibles via les deux interfaces : S3 API classique et système de fichiers standard, sans migration nécessaire Cas d'usage : agents IA pour la persistance de mémoire entre pipelines, équipes ML sans staging, simplification des data lakes Disponible dans 34 régions AWS Data et Intelligence Artificielle Comment générer de la musique et des clips audio en Java avec le modèle Lyria 3 https://glaforge.dev/posts/2026/03/25/generating-music-with-lyria-3-and-the-gemini-interactions-java-sdk/ Génération musicale avec Lyria 3 (DeepMind) et le SDK Java Gemini Interactions. Lyria 3 : modèle d'IA générative pour créer musique avec paroles ou pistes instrumentales. Utilisation via le SDK Java de l'API Gemini, nécessite une clé API Gemini. Deux versions de modèle Lyria 3 : lyria-3-clip-preview : Clips courts (30s), extraits. lyria-3-pro-preview : Chansons complètes (jusqu'à 3 min), structurées. Personnalisation via les prompts : Fournir ses propres paroles ou les faire générer. Contrôler la structure de la chanson ([Intro], [Verse], [Chorus], [Outro]). Générer des morceaux instrumentaux uniquement. Utiliser des images comme source d'inspiration (modèle multimodal). Sortie : Audio (MP3) et texte (paroles/structure) directement, sans décodage complexe. Facilite l'intégration de la génération musicale dans les applications Java. Les world model, la prochaine étape pour les IA https://www.lepoint.fr/sciences-nature/comment-le-commando-de-yann-le-cun-se-prepare-a-ringardiser-les-geants-mondiaux-de-lia-depuis-paris-OZVUWTDYBNE25C6WF44265ZQKE/ Yann LeCun a quitté Meta FAIR pour créer AMI Labs (Advanced Machine Intelligence) basée à Paris Sa thèse : les LLMs ne mèneront pas à l'intelligence générale, la vraie IA doit partir de la compréhension du monde physique AMI Labs a levé 1,03 milliard de dollars en seed (le plus grand seed round de l'histoire européenne) à 3,5 milliards de valorisation Les world models apprennent à prédire et comprendre la réalité physique plutôt qu'à prédire le prochain token d'une séquence Slogan d'AMI : "Real intelligence does not start in language. It starts in the world." Paris comme base stratégique pour challenger la Silicon Valley dans la prochaine rupture de l'IA Debezium 2026 : résultats du sondage communautaire https://debezium.io/blog/2026/04/27/debezium-2026-survey-results/ Debezium est un outil de Change Data Capture (CDC) open source qui capture les modifications de bases de données en temps réel pour les diffuser vers des systèmes comme Kafka. 98,6% des répondants utilisent Debezium activement ou prévoient de le faire dans l'année, avec 91,3% déjà en production. 63,8% des déploiements tournent sur Kubernetes, 60,9% utilisent Kafka Connect auto-géré, et 17,4% restent sur des VMs ou bare metal. Helm charts est l'approche dominante pour la gestion de configuration, souvent combiné avec GitOps, CI/CD, Ansible ou Terraform. PostgreSQL domine les connecteurs utilisés à 69,6%, suivi de MySQL (33,3%), SQL Server (29%) et Oracle (27,5%). Les volumes de changements capturés vont de 1-25 modifications par minute jusqu'à 1-2 millions par minute selon les environnements. Infinispan rejoint l'écosystème OGX comme fournisseur de stockage vectoriel https://infinispan.org/blog/2026/04/17/infinispan-joins-ogx-ecosystem OGX (anciennement Llama Stack) est un serveur API agentique open source pour construire des applications d'IA complètes. OGX compose des fournisseurs d'inférence, des stores vectoriels, des backends de sécurité, des runtimes d'outils et du stockage de fichiers en un seul serveur déployable. OGX se positionne comme une alternative à l'API OpenAI, déployable sur diverses infrastructures et modèles. OGX cible les workflows RAG (Retrieval-Augmented Generation) et les applications agentiques. Infinispan s'y intègre comme fournisseur de vector IO, apportant recherche vectorielle, par mots-clés et hybride. Je n'ai pas entendu parlé de ce renommage, vous le voyez dans vos deploiements ? Outillage cmux un nouveau terminal basé sur Ghostty spécialisé pour les coding agents https://cmux.com/ Application macOS native construite sur le moteur de rendu Ghostty (libghostty), offrant une accélération GPU pour une fluidité maximale Conçu spécifiquement pour le multitâche et les workflows assistés par IA, avec des onglets verticaux affichant la branche Git, le répertoire et les ports actifs Intègre des notifications qui illuminent les panneaux lorsqu'un agent IA (Claude Code, Codex, etc.) nécessite l'attention de l'utilisateur Propose un navigateur web intégré et scriptable qui peut être affiché en écran scindé à côté du terminal via une API Alternative moderne à tmux, ne nécessitant pas de fichiers de configuration complexes ou de préfixes de touches pour la gestion des vitres et des sessions Supporte nativement tous les agents de codage en ligne de commande et permet l'automatisation via une API socket et une interface CLI dédiée Git Worktree comme un chef https://www.metal3d.org/blog/2026/git-worktree-comme-un-chef/ Article par Patrice Ferlet Git Worktree: Travailler sur plusieurs branches simultanément via des répertoires distincts. Évite git stash ou clones multiples pour le changement de contexte rapide. Méthode "bare" (recommandée): Cloner le dépôt en mode bare (ex: .bare). Lier le dossier racine au dépôt bare via un fichier .git. Configurer le remote tracking pour voir toutes les branches distantes. Ajouter des worktrees pour chaque branche (git worktree add ). Avantages: Économie d'espace, source de vérité unique (un git fetch met tout à jour), hooks/configs partagés, sécurité. Conseils: Ne jamais faire de git checkout à l'intérieur d'un worktree. git fetch --all depuis n'importe quel worktree pour tout mettre à jour. git worktree add --detach pour tester des merges temporaires sans créer de branche. Supprimer: git worktree remove puis git worktree prune. Un script wtree est fourni pour automatiser l'initialisation du setup "bare". Améliore considérablement le workflow. L'IDE meurt et vite https://x.com/jdegoes/status/2036931874057314390?s=46&t=C18cckWlfukmsB_Fx0FfxQ Des leaders techniques prédisent la fin rapide de l'IDE traditionnel, remplacé par des interfaces conversationnelles agentiques Le changement de paradigme : le développeur n'écrit plus des lignes de code mais exprime son intention et supervise des agents autonomes Des outils comme Claude Code, Copilot et Cursor transforment déjà radicalement les workflows de développement quotidiens L'IDE centré sur l'éditeur de code perd sa raison d'être quand l'agent lit, modifie et structure le code de manière autonome La transition est comparable au passage du desktop au mobile : les pratiques établies depuis 30 ans remises en question en quelques mois Le source de Claude Code a leaké via probablement le codemap et un site decrit sont fonctionnement https://ccunpacked.dev/ Le 31 mars 2026, Anthropic a accidentellement inclus les sourcemaps dans un package npm de Claude Code, exposant ~512 000 lignes de TypeScript La fuite n'était pas un piratage mais une erreur humaine : un "*.map" oublié dans .npmignore Le site ccunpacked.dev a été lancé pour analyser et visualiser le code source décompressé Le code révèle un agent background permanent nommé "KAIROS", un mode furtif pour cacher les contributions des employés Anthropic à l'open source, et 44 feature flags cachés Une fonctionnalité inédite "Buddy" (animal de compagnie électronique dans le terminal) et un mode "dream" pour l'idéation continue ont été découverts Anthropic a confirmé : "Aucune donnée client sensible n'était impliquée. Erreur humaine dans le packaging de la release." Gemini CLI passe aux agents https://x.com/srithreepo/status/2039794081925382307?s=46&t=GLj1NFxZoCFCjw2oYpiJpw Gemini CLI, l'agent IA open source de Google pour le terminal, introduit des hooks dans sa boucle agentique Les hooks permettent d'exécuter des scripts automatiquement (scanners de sécurité, vérifications de conformité, logging) à chaque étape de l'agent Lancement de Gemini CLI GitHub Actions : un agent autonome pour les repositories qui peut exécuter des tâches de codage de routine Support des MCP servers pour étendre les capacités et des "Agent Skills" pour des workflows spécialisés Mode agent disponible dans VS Code et IntelliJ avec accès aux outils du système de fichiers et terminal Wispr, le speech to text en local sur macOS http://wispr.stormacq.com/ Wispr est une application macOS de dictée vocale entièrement locale, propulsée par Whisper (OpenAI) sur appareil, sans cloud ni tracking Sébastien Stormacq a développé Wispr en un jour et demi sans écrire une seule ligne de code, grâce à Kiro CLI (agent IA Amazon) Disponible en open source sur GitHub et via Homebrew Détection automatique de la langue, insertion du texte au curseur dans n'importe quelle application via un raccourci global En un mois : 19 releases incluant mode mains-libres, suppression des mots de remplissage, auto-envoi pour les chats, et un outil CLI Exemple concret de développement vibe coding produisant un outil de qualité production sans expertise Swift préalable Comment, Gordon, l'assistant spécialisé en Docker est né https://n9o.xyz/posts/202603-building-gordon/ Nuno Coração (n9o.xyz) détaille comment Gordon, l'assistant spécialisé Docker, a été construit sur docker-agent, le runtime d'agents IA open source de Docker écrit en Go Les agents sont définis en YAML déclaratif et distribués comme des artefacts OCI, sans mise à jour binaire nécessaire L'architecture initiale en essaim de 9 agents spécialisés a été abandonnée au profit d'un agent racine unique avec un prompt soigneusement conçu Le modèle utilisé est Claude Haiku 4.5, suffisant après optimisation des prompts Principe clé "show, then do" : toute action de l'agent nécessite une approbation explicite de l'utilisateur La description des outils impacte fortement la précision du LLM : ajouter des outils peut paradoxalement dégrader les performances existantes Le prompt est une spécification détaillée (identité, patterns d'accès fichiers, règles de sécurité) plutôt qu'une simple instruction IBM Bob https://bob.ibm.com/blog/announcing-ibm-bob-launch IBM Bob assistant IA d'IBM pour coder sur de vraies codebases (lancé avril 2026) 5 modes : Ask, Plan, Code, Advanced (MCP), Orchestrator Détecte la complexité du code en temps réel et propose des refactos Fait des revues de code automatiques sur tes branches/issues GitHub Permet d'écrire en langage naturel directement dans l'éditeur Fonctionne aussi en terminal/CLI et dans les pipelines CI/CD Sécurité : approbation manuelle, .bobignore, checkpoints, pas de training sur tes prompts How I use Claude - 50 tips pratiques https://www.youtube.com/watch?v=mZzhfPle9QU Staff Engineer Meta partage 50 tips après 6 mois d'utilisation intensive de Claude Code Basé sur ~12h/jour d'usage perso et professionnel Couvre tout : bases, workflows avancés, parallélisation Objectif : partager ce qu'il aurait voulu savoir dès le départ Méthodologies Quelqu'un rale sur la non soutenabilité des bases de code écritent avec des agents https://mariozechner.at/posts/2026-03-25-thoughts-on-slowing-the-fuck-down/ Mario Zechner estime que les agents IA font les mêmes erreurs répétitivement sans apprendre, accumulant la complexité à grande vitesse faute de bottlenecks humains Sans vision globale, les agents créent du cargo-cult : les "best practices" de l'industrie appliquées localement sans cohérence architecturale La croissance de la base de code dégrade la capacité des agents à retrouver le code existant → duplication et incohérences croissantes Il cite des pannes AWS et des initiatives qualité Microsoft comme signes préoccupants liés au code généré par IA Solution : réserver les agents aux tâches délimitées et évaluables, garder l'architecture, les APIs et les systèmes critiques écrits à la main Maintenir une revue de code rigoureuse et traiter les humains comme les gardiens finaux de la qualité On m'oblige à utiliser l'IA https://n.survol.fr/n/on-moblige-a-utiliser-lia Éric D. défend l'adoption obligatoire de l'IA comme décision stratégique légitime, comparable au choix du full remote ou de la stack technique Il distingue la décision stratégique (adoption IA) de la méthode d'accompagnement (qui reste collaborative et bienveillante) La compétence IA devient un critère de recrutement : chercher des candidats déjà curieux et explorateurs de ces outils L'alignement culturel sur les pratiques et outils est un prérequis à la cohésion d'équipe Le refus d'adopter certains outils stratégiques peut justifier de ne pas recruter un candidat autrement compétent Encore une metodo SPDD https://martinfowler.com/articles/structured-prompt-driven/ Problème : l'IA accélère le dev individuel mais amplifie ambiguïtés et incohérences à l'échelle d'une équipe. martinfowler SPDD : traiter les prompts comme des artefacts versionnés, révisables et réutilisables plutôt que des échanges jetables. martinfowler Canvas REASONS : 7 dimensions (Requirements, Entities, Approach, Structure, Operations, Norms, Safeguards) pour guider le LLM de l'intention à l'exécution. martinfowler Workflow en 6 étapes : exigences → analyse → contexte → prompt structuré → code → tests unitaires, chaque étape s'appuyant sur la précédente. martinfowler 3 compétences clés : abstraction d'abord, alignement de l'intention, revue itérative. martinfowler Limites : fort ROI sur du code métier complexe, peu adapté aux hotfixes urgents, scripts jetables ou travail créatif/visuel. m Sécurité Le projet Glasswing pour sécuriser les logiciels https://www.anthropic.com/glasswing Anthropic lance Glasswing, une initiative de cybersécurité utilisant Claude Mythos Preview pour identifier des vulnérabilités zero-day 12 partenaires fondateurs dont AWS, Apple, Cisco, CrowdStrike, Google, JPMorganChase, Linux Foundation, Microsoft et NVIDIA Anthropic investit 100 millions de dollars en crédits de modèle et 4 millions en dons aux organisations de sécurité open source Le modèle opère avec une autonomie substantielle, identifiant des milliers de vulnérabilités dans les OS, navigateurs et infrastructures critiques Plus de 40 organisations supplémentaires ont accès pour scanner et sécuriser leurs systèmes Objectif : donner l'avantage aux défenseurs avant que les techniques de hacking assistées par IA ne se généralisent chez les attaquants LinkedIn vous espionne https://frenchbreaches.com/blog/linkedin-est-accuse-de-fouiller-dans-votre-ordinateur-illegalement Scandale "BrowserGate" : LinkedIn injecte du JavaScript qui tente de détecter les extensions Chrome installées sur votre navigateur Le script analysé contient une liste codée en dur de 6 222 extensions Chrome avec identifiants et chemins de fichiers internes Croissance alarmante de la liste ciblée : 38 extensions en 2017 → 461 en 2024 → ~1 000 en mai 2025 → 6 222 début 2026 Les données collectées incluent aussi CPU, RAM, résolution d'écran, timezone et état batterie pour du fingerprinting Certaines extensions ciblées sont liées à la neurodivergence, aux pratiques religieuses ou aux opinions politiques → violation grave du RGPD LinkedIn défend que le scan vise uniquement à détecter les extensions qui pratiquent le scraping de données Post mortem de la supply chain attack sur la librairie NPM axios https://github.com/axios/axios/issues/10636 Le 31 mars 2026, deux versions malveillantes d'axios (1.14.1 et 0.30.4) ont été publiées via un compte mainteneur compromis Vecteur d'attaque : RAT installé via ingénierie sociale ciblée sur la machine personnelle du mainteneur principal La 2FA ne protège pas si la machine de l'utilisateur est compromise : l'attaquant contrôle tout et peut agir comme l'utilisateur Les packages malveillants injectaient plain-crypto-js@4.2.1, un cheval de Troie multi-plateforme (macOS, Windows, Linux) Détection communautaire en ~3 heures, suppression par npm, mesures correctives : rotation complète des credentials Changements préventifs : publication via OIDC, releases immuables, amélioration des pratiques GitHub Actions Passbolt un gestionnaire de mots de passe open source https://lesjoiesducode.fr/passbolt-gestionnaire-de-mots-de-passe-gratuit-open-source-que-votre-equipe-merite-vraiment Gestionnaire de mots de passe open source conçu pour le partage d'identifiants en équipe, utilisé par plus de 50 000 organisations Chiffrement individuel par utilisateur et par version de credential, pas de coffre-fort partagé — architecture zero-knowledge "Forward secrecy" : quand un membre quitte l'équipe, ses copies chiffrées sont automatiquement révoquées sans reset manuel Supporte TOTP, clés SSH, tokens API et champs personnalisés avec piste d'audit complète de tous les accès Édition communautaire entièrement gratuite avec utilisateurs illimités, auto-hébergeable ou cloud Chiffrement OpenPGP nécessitant passphrase + clé privée, avec tokens visuels anti-phishing Loi, société et organisation Anthropic fait un don d'1,5 millions de dollars à la fondation Apache https://news.apache.org/foundation/entry/the-apache-software-foundation-announces-1-5m-donation-from-anthropic Anthropic donne 1,5 million de dollars à l'ASF pour soutenir l'infrastructure, la sécurité et la communauté open source Vitaly Gudanets (CISO d'Anthropic) : "Soutenir l'ASF est un investissement direct dans la résilience et l'intégrité des systèmes dont dépend l'IA moderne" Les fonds financeront les systèmes de build, les processus de sécurité et les services aux projets Apache Ce don est le déclencheur de l'initiative IA responsable à 10 millions de dollars de l'ASF L'infrastructure Apache est invisible mais critique : des systèmes financiers aux plateformes de santé, elle sous-tend l'écosystème logiciel mondial L'ASF lance l'initiative IA responsable https://news.apache.org/foundation/entry/the-apache-software-foundation-launches-10m-responsible-ai-initiative-with-initial-1-75m-donation L'ASF lance une initiative pour une IA responsable dotée d'un budget de 10 millions de dollars sur 3 ans minimum Anthropic est le premier donateur avec 1,5 million de dollars ; Alpha-Omega contribue 250 000 dollars L'initiative fournit aux projets Apache un accès à des modèles IA pour l'expérimentation et la sécurité Elle soutient l'ensemble de la chaîne IA/ML : pipelines de données, infrastructure, frameworks de deep learning Des tracks de conférences, hackathons et bourses de voyage sont prévus pour élargir la communauté Les principes directeurs incluent la supervision humaine, l'intégrité des licences et la sécurité open source Oracle vire 30000 personnes https://rollingout.com/2026/03/31/oracle-slashes-30000-jobs-with-a-cold-6/ Oracle licencie 20 000 à 30 000 employés, 18% de ses effectifs mondiaux. Les salariés ont appris leur licenciement par un simple email à 6h du matin, sans aucun préavis. L'accès à tous les systèmes (Slack, Zoom, badges) a été coupé immédiatement après. But : libérer 8 à 10 milliards de dollars pour construire des centres de données IA. Oracle a déjà contracté 50 milliards de dettes en 2026 pour financer ses projets IA. Paradoxe : l'entreprise affiche un bénéfice record de 6,13 milliards, mais ses liquidités sont dans le rouge. L'action Oracle a perdu plus de la moitié de sa valeur depuis septembre 2025. Et si l'IA n'était qu'un prétexte pour licencier https://eventuallycoding.com/p/ia-licenciements-et-si-l-intelligence-artificielle-n-etait-qu-une-excuse Hugo Lassiège (eventuallycoding) estime que les entreprises utilisent l'IA comme narratif commode pour masquer des erreurs de gestion passées (Block a triplé ses effectifs post-COVID sans croissance des revenus correspondante) Moins de 1% des licenciements technologiques seraient réellement dus à des gains de productivité IA selon les analyses citées Mesurer la productivité des développeurs reste un problème non résolu, mais les entreprises affirment des gains d'efficacité sans preuves Des pressions économiques réelles (inflation, guerres commerciales, coûts énergétiques) sont masquées derrière le discours IA Les restructurations nécessaires sont présentées comme des transformations AI-driven positives pour rassurer les investisseurs Il y voit une fenêtre d'opportunité pour l'Europe pendant que les géants américains se restructurent GitHub Copilot va utiliser les interacitons pour entrainer ses modèles sauf si vous vous délistez https://github.blog/news-insights/company-news/updates-to-github-copilot-interaction-data-usage-policy/ À partir du 24 avril 2026, GitHub utilise par défaut les interactions des utilisateurs Copilot Free, Pro et Pro+ pour entraîner ses modèles Les données collectées incluent le code accepté ou modifié, les snippets envoyés, les noms de fichiers et structures de dépôts, et les retours utilisateurs Les utilisateurs Copilot Business, Enterprise et les dépôts d'entreprise sont exclus de cette collecte de données d'entraînement Opt-out disponible dans les paramètres GitHub > "Privacy" ; les préférences de désactivation préalables sont conservées automatiquement Objectif déclaré : améliorer la précision des modèles sur les langages et cas d'usage du monde réel Grosse percée de Claude Code dans les commits sur GitHub https://aifoc.us/damn-claude-thats-a-lot-of-commits/ Explosion de Claude Code : En six mois, Claude Code est passé de 0,7 % à 4,5 % de tous les commits publics sur GitHub, surpassant tous les autres outils d'IA combinés. Adoption massive des agents IA : Environ 5 % des commits publics sur GitHub sont désormais générés par des agents IA, un chiffre en croissance rapide depuis fin 2025. Domination des bots sur GitHub : Au-delà des commits, les outils d'IA sont omniprésents dans la gestion des pull requests et des problèmes (Copilot et CodeRabbit notamment). Limites méthodologiques : Les données ne concernent que les dépôts publics (les entreprises utilisent massivement des dépôts privés, invisibles ici). Le comptage dépend fortement de la visibilité des signatures (certains outils comme Claude marquent systématiquement leurs commits, d'autres non) L'API de recherche GitHub présente une fiabilité variable à cette échelle. Changement de paradigme : Le développement logiciel vit une transition majeure, comparable au passage du desktop au mobile. L'intégration des agents IA dans le cycle de production n'est plus une expérimentation, mais une réalité opérationnelle à grande échelle. Dysmaths une application pour aider à apprendre les mathématiques et la géométrie lorsque l'on souffre de dyspraxie, dysgraphie https://dysmaths.com/ Application web pour aider les élèves de collège et lycée souffrant de dysgraphie et dyspraxie à faire des maths et de la géométrie Outils de dessin à main levée, géométrie précise (compas, rapporteur, règle) et opérations structurées (fractions, racines, puissances, symboles mathématiques) Export PDF et PNG avec conservation fidèle de l'échelle pour l'impression et la soumission des exercices Options d'accessibilité : police OpenDyslexic, personnalisations d'interface, import d'images et de PDFs Répond à un besoin réel : les outils standards ne sont pas adaptés aux difficultés de coordination et d'organisation spatiale en mathématiques IA ou réalité ? Par Amistory https://www.youtube.com/watch?v=PPYdAhBBF2I L'IA génère des contenus (images, voix, vidéos) de plus en plus indétectables Les arnaques au clonage de voix et deepfakes sont en forte hausse Les faux contenus viraux manipulent l'opinion à grande échelle Le faux n'est plus un accident, c'est devenu un système organisé La société entre dans une ère de doute généralisé sur le réel Comment s'informer quand le réel lui-même peut être simulé ? Conférences La liste des conférences provenant de Developers Conferences Agenda/List par Aurélie Vache et contributeurs : 6-7 mai 2026 : Devoxx UK 2026 - London (UK) 12 mai 2026 : Lead Innovation Day - Leadership Edition - Paris (France) 12-13 mai 2026 : Lyon Craft - Lyon (France) 19 mai 2026 : La Product Conf Paris 2026 - Paris (France) 19-20 mai 2026 : Green Code Challenge - Paris (France) 21-22 mai 2026 : Flupa UX Days 2026 - Paris (France) 22 mai 2026 : AFUP Day 2026 Lille - Lille (France) 22 mai 2026 : AFUP Day 2026 Paris - Paris (France) 22 mai 2026 : AFUP Day 2026 Bordeaux - Bordeaux (France) 22 mai 2026 : AFUP Day 2026 Lyon - Lyon (France) 27 mai 2026 : aMP Day Strasbourg 2026 - Strasbourg (France) 28 mai 2026 : DevCon 27 : I.A. & Vibe Coding - Paris (France) 28 mai 2026 : Cloud Toulouse 2026 - Toulouse (France) 29 mai 2026 : NG Baguette Conf 2026 - Paris (France) 29 mai 2026 : Agile Tour Strasbourg 2026 - Strasbourg (France) 2-3 juin 2026 : Agile Tour Rennes 2026 - Rennes (France) 2-3 juin 2026 : OW2Con - Paris-Châtillon (France) 3 juin 2026 : IA–NA - La Rochelle (France) 4 juin 2026 : Workplace Intelligence Days - 1ère édition - Lyon (France) 5 juin 2026 : TechReady - Nantes (France) 5 juin 2026 : Fork it! - Rouen - Rouen (France) 6 juin 2026 : Polycloud - Montpellier (France) 9 juin 2026 : JFTL - Montrouge (France) 9 juin 2026 : C: - Caen (France) 9 juin 2026 : France API 2026 - Paris (France) 11-12 juin 2026 : DevQuest Niort - Niort (France) 11-12 juin 2026 : DevLille 2026 - Lille (France) 12 juin 2026 : Tech F'Est 2026 - Nancy (France) 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) 25-26 juin 2026 : Agile Tour Toulouse 2026 - Toulouse (France) 27 juin 2026 : Asynconf - Paris (France) 2 juillet 2026 : Azur Tech Summer 2026 - Valbonne (France) 2-3 juillet 2026 : Sunny Tech - Montpellier (France) 3 juillet 2026 : Agile Lyon 2026 - Lyon (France) 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 : 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) 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) 12 octobre 2026 : Dev With AI - Paris (France) 27-29 octobre 2026 : Directions EMEA 2026 - Paris (France) 29-30 octobre 2026 : BDX I/O 2026 - Bordeaux (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) 27 novembre 2026 : DevFest Paris 2026 - Paris (France) 1-3 décembre 2026 : Apidays Paris - 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) 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/

Ep. 302- May Promotions 2026: Sun Care, Tea Tree Oil & DIY Shower Melt Recipes Join us as we discuss all things wonderful May Promos. From Tea Tree to fun Limited addition products, we have a fun episode for you.  Also..... Get this Book! Link for Essential Emotions book. You need it.  https://aromatools.com/collections/frontpage/products/essential-emotions-14th-edition The Essential Life book here https://essentiallife.com/product/essential-life-10th-edition/ If this episode touched something in your heart, just know you don't have to walk through it alone. This is the kind of emotional healing work we support our clients through, and we'd be honored to walk alongside you when you're ready. Book with Vicki: https://vickilebrilla.com/coaching Book with Sarah: https://sarahsepos.com/coaching   Scoop of the Day Do yourself a favor and get on rewards to start earning rewards points today   Shower Melt Recipe 1 Cup Baking (Bi-Carb) Soda Sifted 1/4 Cup Citric Acid 1/4 Cup Corn Starch Water Distilled or purified is best Epsom Salts Essential Oils Sprinkle several different Epsom Salts in the bottom of each hole of your cupcake pan.  In this case less is more.  The Epsom salts won't stick to each other but they will stick to the shower melt ingredients so make sure there are gaps in between the salts. Sift the baking soda, citric acid, and corn starch into a bowl, mixing until no lumps are present.  Add water a few drops at a time. Use a spoon or your hands to combine the mixture, rubbing it between your fingers to evenly disperse the water.  You'll know you've used enough when it sticks together/packs down and can keep its shape.   It will still look kind of dry, but if you take a handful of the mixture and squeeze it, it should pack easily into a ball. Too much water will make the mixture continue to fizz and puff up more.    It may seem odd, but using your ears can help you with this step.  As you are mixing, bring your ear down to the bowl and listen.  Your mixture should be damp but not fizzing. If you used too much water in the mixture, it will continue to fizz and rise while it is drying. Constant and increasing fizzing means you may have added too much water, you can counteract this by adding more dry ingredients to the mix if it is too wet. Once you get the correct consistency, begin to fill your mold, pushing down the mixture into the holes and compacting it into place.  Compaction is an important step as it may mean the difference between hard and crumbly melts once they are dry. It will also help your Epsom salts stick to the melts if you are using this decoration method. Set the melts aside to air dry for 24-36 hours (depending on the humidity where you live). When sufficiently hardened, your shower melts should release from your pan fairly easily, if they are still wet, they will not fall out with ease. Add your essential oils to the shower melts right before using.  Drop the oils directly on top, then place in the corner of your shower where it will get wet, but is not directly below the water stream.  Watch it melt as you shower and wash any residue down the drain when you are finished.   #doterra #doterraMayPromotions #TeaTreeOil #SunCare #NaturalWellness #ShinrinYoku #BathBar #HairOil #DIYShowerMelts #EssentialOils #SummerWellness #CleanLiving #SelfCareRoutine #EssentialOilLifestyle #HolisticWellness   Welcome into our little essential oil world where we talk about the physical and emotional support of our essential oils.   Hi friends, don't forget to leave us a review, your feedback is always welcome, and helps this podcast reach more ears. Join us in our New Facebook Community! Connect on Instagram  Follow us on YouTube: https://www.youtube.com/@TheEssentialOilScoopPodcast   We upload a brand new episode every Tuesday and Thursday!   Want to learn more about us? theessentialoilscoop.com   Remember to like, share, and subscribe to our podcast so you will be notified every time we upload a brand new episode.  Leave us a review as well, your feedback is always welcome. Also opt-in to our newsletter at https://theessentialoilscoop.com/newsletter   If you have any questions or have subject ideas you would like us to cover please email us at theessentialoilscoop@gmail.com   Tag us on socials using #theessentialoilscoop #essentialoilpodcast #oilpodcast   Disclaimer:  Welcome to The Essential Oil Scoop Podcast. We want to remind our listeners that the information provided in this podcast is for educational purposes only and should not be considered as a substitute for professional medical advice, diagnosis, or treatment. The use of essential oils is a personal choice and should be done at your own risk. We are not medical professionals and cannot diagnose, treat, or prescribe any medical condition. Please consult with a qualified healthcare provider before using any essential oils or making changes to your healthcare routine. Any information or opinions expressed in this podcast are those of the hosts and guests and do not necessarily reflect the views of any particular organization. Thank you for listening.

See omnystudio.com/listener for privacy information.

Auch ein Boden hat mal einen Kater - nach Schadverdichtungen muss er sich mühsam wieder zu alter Leistungsfähigkeit kämpfen. Christoph beleuchtet in dieser Folge mit Laura, welche Bodeneigenschaften sich nach einer Verdichtung wiederherstellen und welche möglicherweise langfristig verändert bleiben.

Guy and Eitan discuss several very interesting new features recently announced by Microsoft. Relevant links for more info: Stop defragmenting and start living: introducing auto index compaction | Microsoft Community Hub Automatic Index Compaction - SQL Server | Microsoft Learn Database DevOps (preview) in SSMS 22.4.1 | Microsoft Community Hub Manage SQL database schemas in VS Code: Publish dialog and item templates - Azure SQL Dev Corner Publish SQL Database Projects from Visual Studio Code - SQL Server | Microsoft Learn SQL code analysis in VS Code: Configure rules without editing your project file - Azure SQL Dev Corner SQL Projects Roadmap - DacFx Wiki Author Custom Code Analysis Rules - SQL Server | Microsoft Learn

Tillage has a lot of downsides, and cover crops can help prevent erosion and decrease compaction.

In this episode, soil specialist and consultant Jim Hoorman of Hoorman Soil Health sheds light on the impact of soil compaction on soil pore space.   Subscribe for more content on sustainable farming, market farming tips, and business insights!   Get market farming tools, seeds, and supplies at Modern Grower. Follow Modern Grower:  Instagram  Instagram Listen to other podcasts on the Modern Grower Podcast Network:  Carrot Cashflow  Farm Small Farm Smart  Farm Small Farm Smart Daily  The Growing Microgreens Podcast  The Urban Farmer Podcast  The Rookie Farmer Podcast  In Search of Soil Podcast Check out Diego's books:  Sell Everything You Grow on Amazon   Ready Farmer One on Amazon **** Modern Grower and Diego Footer participate in the Amazon Services LLC. Associates Program, an affiliate advertising program designed to provide a means for sites to earn advertising fees by advertising and linking to Amazon.com.

After a well-earned family break, Peter "Wheat Pete" Johnson is back—and there’s no shortage of agronomy to cover in this late February episode. From manure management mishaps to sulphur math confusion and long-term compaction damage, this week’s Word is packed with practical lessons and listener-driven questions. As always, the episode blends sharp agronomy insight with... Read More

After a well-earned family break, Peter "Wheat Pete" Johnson is back—and there’s no shortage of agronomy to cover in this late February episode. From manure management mishaps to sulphur math confusion and long-term compaction damage, this week’s Word is packed with practical lessons and listener-driven questions. As always, the episode blends sharp agronomy insight with... Read More

Atombeam CEO Charles Yeomans joins Chris Lustrino to break down a deceptively simple idea with massive implications: make data smaller while it's streaming so you can move and process more of it—without upgrading networks.Charles explains Atombeam's commercial product NeurPack, how it can often quadruple effective bandwidth, and why this matters across IoT, smart meters, satellites, defense, oil & gas wells, fintech, and eventually data centers and GPU utilization. They also dig into the realities of commercialization—choosing near-term deals that close fast while still pursuing multi-year “industry standard” opportunities—and why execution (not invention) is the real differentiator.00:00 What Atombeam does (pizza analogy)03:13 NeurPack explained05:35 Why 95% of IoT data doesn't move09:38 “Like launching 3 more satellites”13:57 Commercialization + customers16:31 Data centers + GPU utilization24:29 Defense traction + partnerships26:44 What success looks like (distribution)

Contact Scott from Bonsai MatsuBeautiful bonsai for me have well balanced and positioned foliage pads. While it is easy initially to create larger pads, longer term this can be to the detriment of the structure of your bonsai. There is a process I use to create and separate pads. Another thought that runs continuously through my head when working on bonsai is Compaction. How do I make this tree smaller and push it back? Not by using twisted long branches but by developing good structure. It comes back to the inner buds and the ..... bud conveyor! And Autumn is just around the corner so start to monitor your watering habits.Support the showBecome a podcast supporter and show the Bonsai Love (it's really appreciated) ❤️https://www.buzzsprout.com/263290/supportWhere to find Bonsai Matsu:InstagramFacebookYouTube Web

Latest products for beet and bean diseases. Minnesota business uses ancient technique for healthier tortillas. Tips for reducing soil compaction. Help for young people to start sheep flocks.

In this episode, soil specialist and consultant Dr. Jim Hoorman of Hoorman Soil Health discusses exactly how cover crops can help mitigate and resolve soil compaction.   Subscribe for more content on sustainable farming, market farming tips, and business insights!   Get market farming tools, seeds, and supplies at Modern Grower. Follow Modern Grower:  Instagram  Instagram Listen to other podcasts on the Modern Grower Podcast Network:  Carrot Cashflow  Farm Small Farm Smart  Farm Small Farm Smart Daily  The Growing Microgreens Podcast  The Urban Farmer Podcast  The Rookie Farmer Podcast  In Search of Soil Podcast Check out Diego's books:  Sell Everything You Grow on Amazon   Ready Farmer One on Amazon **** Modern Grower and Diego Footer participate in the Amazon Services LLC. Associates Program, an affiliate advertising program designed to provide a means for sites to earn advertising fees by advertising and linking to Amazon.com.

What if everything you've been told about soil compaction is only half the story?In this episode of Regen Radio, Denver Black and farmer Craig Harding tackle one of agriculture's most assumed villains: compaction. From deep ripping to gypsum applications, we unpack whether the problem is really physical—or if it's chemical, biological, or even electromagnetic.

Hey ya'll, Alex here, and this week I was especially giddy to record the show! Mostly because when a thing clicks for me that hasn't clicked before, I can't wait to tell you all about it! This week, that thing is Agent Skills! The currently best way to customize your AI agents with domain expertise, in a simple, repeatable way that doesn't blow up the context window! We mentioned skills when Anthropic first released them (Oct 16) and when they became an open standard but it didn't really click until last week! So more on that below. Also this week, Anthropic released a research preview of Claude Cowork, an agentic tool for non coders, OpenAI finally let loos GPT 5.2 Codex (in the API, it was previously available only via Codex), Apple announced a deal with Gemini to power Siri, OpenAI and Anthropic both doubled down on healthcare and much more! We had an incredible show, with an expert in Agent Skills, Eleanor Berger and the usual gang on co-hosts, strongly recommend watching the show in addition to the newsletter! Also, I vibe coded skills support for all LLMs to Chorus, and promised folks a link to download it, so look for that in the footer, let's dive in! ThursdAI is where you stay up to date! Subscribe to keep us going! Big Company LLMs + APIs: Cowork, Codex, and a Browser in a WeekAnthropic launches Claude Cowork: Agentic AI for Non‑Coders (research preview)Anthropic announced Claude Cowork, which is basically Claude Code wrapped in a friendly UI for people who don't want to touch a terminal. It's a research preview available on the Max tier, and it gives Claude read/write access to a folder on your Mac so it can do real work without you caring about diffs, git, or command line.The wild bit is that Cowork was built in a week and a half, and according to the Anthropic team it was 100% written using Claude Code. This feels like a “we've crossed a threshold” moment. If you're wondering why this matters, it's because coding agents are general agents. If a model can write code to do tasks, it can do taxes, clean your desktop, or orchestrate workflows, and that means non‑developers can now access the same leverage developers have been enjoying for a year.It also isn't just for files—it comes with a Chrome connector, meaning it can navigate the web to gather info, download receipts, or do research and it uses skills (more on those later)Earlier this week I recorded this first reactions video about Cowork and I've been testing it ever since, it's a very interesting approach of coding agents that “hide the coding” to just... do things. Will this become as big as Claude Code for anthropic (which is reportedly a 1B business for them)? Let's see! There are real security concerns here, especially if you're not in the habit of backing up or using git. Cowork sandboxes a folder, but it can still delete things in that folder, so don't let it loose on your whole drive unless you like chaos.GPT‑5.2 Codex: Long‑Running Agents Are HereOpenAI shipped GPT‑5.2 Codex into the API finally! After being announced as the answer for Opus 4.5 and only being available in Codex. The big headline is SOTA on SWE-Bench and long‑running agentic capability. People describe it as methodical. It takes longer, but it's reliable on extended tasks, especially when you let it run without micromanaging.This model is now integrated into Cursor, GitHub Copilot, VS Code, Factory, and Vercel AI Gateway within hours of launch. It's also state‑of‑the‑art on SWE‑Bench Pro and Terminal‑Bench 2.0, and it has native context compaction. That last part matters because if you've ever run an agent for long sessions, the context gets bloated and the model gets dumber. Compaction is an attempt to keep it coherent by summarizing old context into fresh threads, and we debated whether it really works. I think it helps, but I also agree that the best strategy is still to run smaller, atomic tasks with clean context.Cursor vibe-coded browser with GPT-5.2 and 3M lines of codeThe most mind‑blowing thing we discussed is Cursor letting GPT‑5.2 Codex run for a full week to build a browser called FastRenderer. This is not Chromium‑based. It's a custom HTML parser, CSS cascade, layout engine, text shaping, paint pipeline, and even a JavaScript VM, written in Rust, from scratch. The codebase is open source on GitHub, and the full story is on Cursor's blog It took nearly 30,000 commits and millions of lines of code. The system ran hundreds of concurrent agents with a planner‑worker architecture, and GPT‑5.2 was the best model for staying on task in that long‑running regime. That's the real story, not just “lol a model wrote a browser.” This is a stress test for long‑horizon agentic software development, and it's a preview of how teams will ship in 2026.I said on the show, browsers are REALLY hard, it took two decades for the industry to settle and be able to render websites normally, and there's a reason everyone's using Chromium. This is VERY impressive

Celena Hawkins joins me to discuss soil compaction and its effects on crop yield. We talk about how to avoid it, manage it, and ultimately correct the layers of compacted soils that cause all sorts of problems to a person's field. TOP Ag Services is a Beck's Hybrids seed dealer as well as a franchise partner for Sweetwater Technologies. We provide Hybrid Corn Seed, Soybean Seed, and Wheat Seed. Beck's has access to the best genetics and trait technologies from suppliers worldwide. Through Sweetwater Technologies we have access to industry standard name brand herbicides, insecticides, fungicides, and many others! We have access to biological stress mitigators, biological fertility foliar, and many other products in the category of crop protection and stress prevention. Through our business associates Dirks Bros, we offer fertilizer, soil sampling, and a whole suite of crop nutrition solutions. We are the first to market with the best products & provide the latest, most accurate agronomic information through proven research. If you need agronomic assistance or want to be added to these updates, feel free to reach out via the messaging feature or contact us at topagservices.com/contact or call us at 417-684-5301 to be connected with someone who can help you. All information here is for informational purposes only. It is not a recommendation for your farm. You should not act or refrain from acting on the basis of any content included in this presentation without seeking other professional advice. The contents of this presentation contain general information and may not reflect current agronomic or developments or address your situation. We (Wendell Koehn and all of his affiliates, guests, or assistants) disclaim all liability for actions you take or fail to take based on any content in this presentation.

Learn how liquid soil aerators use organic ingredients like humic acids, kelp, and beneficial microbes to tackle lawn compaction without chemicals. Find out why this method outperforms traditional core aeration and how to achieve a healthier, greener lawn naturally. Read more at https://gsplantfoods.com/products/softsoil GS Plant Foods City: Lake Mary Address: 4300 West Lake Mary Boulevard Website: https://gsplantfoods.com/

Hammad Bashir, CTO of Chroma, joins the show to break down how modern vector search systems are actually built from local, embedded databases to massively distributed, object-storage-backed architectures. We dig into Chroma's shared local-to-cloud API, log-structured storage on object stores, hybrid search, and why retrieval-augmented generation (RAG) isn't going anywhere.Follow Hammad:Twitter/X:  https://twitter.com/HammadTimeLinkedIn: https://www.linkedin.com/in/hbashirChroma: https://trychroma.comFollow Aaron:Twitter/X:  https://twitter.com/aarondfrancis Database School: https://databaseschool.comDatabase School YouTube Channel: https://www.youtube.com/@UCT3XN4RtcFhmrWl8tf_o49g  (Subscribe today)LinkedIn: https://www.linkedin.com/in/aarondfrancisWebsite: https://aaronfrancis.com - find articles, podcasts, courses, and more.Chapters:00:00 – Introduction From high-school ASICs to CTO of Chroma01:04 – Hammad's background and why vector search stuck03:01 – Why Chroma has one API for local and distributed systems05:37 – Local experimentation vs production AI workflows08:03 – What “unprincipled data” means in machine learning10:31 – From computer vision to retrieval for LLMs13:00 – Exploratory data analysis and why looking at data still matters16:38 – Promoting data from local to Chroma Cloud19:26 – Why Chroma is built on object storage20:27 – Write-ahead logs, batching, and durability26:56 – Compaction, inverted indexes, and storage layout29:26 – Strong consistency and reading from the log34:12 – How queries are routed and executed37:00 – Hybrid search: vectors, full-text, and metadata41:03 – Chunking, embeddings, and retrieval boundaries43:22 – Agentic search and letting models drive retrieval45:01 – Is RAG dead? A grounded explanation48:24 – Why context windows don't replace search56:20 – Context rot and why retrieval reduces confusion01:00:19 – Faster models and the future of search stacks01:02:25 – Who Chroma is for and when it's a great fit01:04:25 – Hiring, team culture, and where to follow Chroma

In this episode, soil specialist and consultant Jim Hoorman of Hoorman Soil Health talks about the nitty-gritty details behind how cover crops actually help break up compaction.  Subscribe for more content on sustainable farming, market farming tips, and business insights!   Get market farming tools, seeds, and supplies at Modern Grower. Follow Modern Grower:  Instagram  Instagram Listen to other podcasts on the Modern Grower Podcast Network:  Carrot Cashflow  Farm Small Farm Smart  Farm Small Farm Smart Daily  The Growing Microgreens Podcast  The Urban Farmer Podcast  The Rookie Farmer Podcast  In Search of Soil Podcast Check out Diego's books:  Sell Everything You Grow on Amazon   Ready Farmer One on Amazon **** Modern Grower and Diego Footer participate in the Amazon Services LLC. Associates Program, an affiliate advertising program designed to provide a means for sites to earn advertising fees by advertising and linking to Amazon.com.

Soil specialist and consultant Dr. Jim Hoorman of Hoorman Soil Health defines what soil compaction is and the leading causes of compacted soils.   Subscribe for more content on sustainable farming, market farming tips, and business insights!   Get market farming tools, seeds, and supplies at Modern Grower. Follow Modern Grower:  Instagram  Instagram Listen to other podcasts on the Modern Grower Podcast Network:  Carrot Cashflow  Farm Small Farm Smart  Farm Small Farm Smart Daily  The Growing Microgreens Podcast  The Urban Farmer Podcast  The Rookie Farmer Podcast  In Search of Soil Podcast Check out Diego's books:  Sell Everything You Grow on Amazon   Ready Farmer One on Amazon **** Modern Grower and Diego Footer participate in the Amazon Services LLC. Associates Program, an affiliate advertising program designed to provide a means for sites to earn advertising fees by advertising and linking to Amazon.com.

10 21 25 Compaction by Ag PhD

Does Compaction Cure actually work? The UGA study shows results of several criteria including surface hardness, root weight and more. Get your Christmas Lights: Christmas Lights

UI Extension study shows promise for raising, grazing cover crops after grain harvest.

Harvest machinery is getting heavier and heavier, increasing the risk for soil compaction. Learn more about how you can combat soil compaction during harvest and ensure the health of future crops. Learn more about your ad choices. Visit podcastchoices.com/adchoices

Ready to change the way you look at football fields forever? It's not as simple as managing an acre of grass.   In this episode of The Dirt, Dr. Bryan G. Hopkins joins Mike Howell to break down the art and science of sports turf management. From irrigation timing and mowing height, paint and shade, to compaction and crowns, you'll hear what really goes into the fields our athletes play on.   Explore why natural grass has become the turf of choice, how stadium layouts affect growth and uncover innovative technologies that have changed the turfgrass management game for NFL and college football consultants like Dr. Bryan Hopkins.   Looking for the latest in crop nutrition research? Visit nutrien-ekonomics.com   Subscribe to our YouTube channel: https://www.youtube.com/@NutrieneKonomics  

Welcome to this Agronomic Monday edition of RealAg Radio! On today’s show, host Lyndsey Smith is joined by Peter Johnson, RealAgriculture’s in-house agronomist, to discuss: How corn and beans react during drought conditions; Fall-seeded crops in dry conditions and what to watch for, and; Key compaction day learnings and important points to take away. Plus,... Read More

Welcome to this Agronomic Monday edition of RealAg Radio! On today’s show, host Lyndsey Smith is joined by Peter Johnson, RealAgriculture’s in-house agronomist, to discuss: How corn and beans react during drought conditions; Fall-seeded crops in dry conditions and what to watch for, and; Key compaction day learnings and important points to take away. Plus,... Read More

On this episode of the Strip-Till Farmer podcast, brought to you by Environmental Tillage Systems, Understanding Ag consultant Brian Dougherty gets to the root of compaction. Every equipment pass risks soil compaction, a problem that affects root and crop growth, water infiltration, crop fertility access and your bottom line. But many management practices exist to help fix compaction and avoid it in the future.

In this episode, grazing expert and longtime SGF contributor Jim Gerrish tackles a frequently overlooked threat to pasture health—soil compaction. While it's easy to spot visible issues like weeds or bare patches, compaction is stealthy. It reduces infiltration, chokes out biology, and quietly erodes pasture productivity—even when everything above ground looks fine. The episode explores how compaction develops in both dry and wet conditions, why certain grazing practices (like overstocking or ignoring soil moisture) make it worse, and how to manage your land in a way that protects the invisible ecosystem beneath your animals' hooves. Jim also dives into his personal experience observing compaction on both his Missouri and Idaho properties, highlighting how the signs and solutions vary by climate and soil type.

On this episode of Conservation Ag Update, brought to you by Yetter, Michael Thompson, No-Till Farmer's 2025 Conservation Ag Operator Fellow, shares how he's alleviating compaction with an AerWay unit in Almena, Kan. Plus, no-tillers exchange ideas and strategies for fighting slugs in soybean fields.

In this episode of the Digging Deeper podcast, Brandon interviews Justin Zupanc, Compaction Product Manager for Volvo Construction Equipment, at World of Asphalt. They dive into Volvo's innovative compaction solutions, highlighting the new DD 15 electric compactor and the company's commitment to both electric and diesel technologies. The conversation explores key industry challenges like labor shortages and the potential of autonomous equipment, while showcasing Volvo's approach to improving operator efficiency through smart technologies like intelligent compaction. Justin shares insights on emerging trends, the importance of data-driven solutions, and how new technologies are transforming the road building and construction sectors. Whether you're interested in electric machinery, compaction techniques, or the future of construction equipment, this podcast offers a comprehensive look at Volvo's cutting-edge developments.

Soil Compaction, "often known as the hidden yield-limiting factor," can be minimized through strategic and intentional choices on our farms. Please tune in to hear the research and advice from Dr. John Fulton and his fantastic team at Ohio State University! See more from A Penney For Your Thoughts 

Soil compaction plays a massive role in corn and soybean production. Dr. Fulton provides insight into how these biological, chemical, and physical soil components are affected by soil compaction. We also gain insight into Dr. Fulton and his team's research better to understand this complex aspect of our soil health. See more from A Penney For Your Thoughts 

Dr. Gabe LaHue discusses improving water infiltration and soil structure, and if soil organic matter increases the ability of the soils to hold water. Episode transcription: smallgrains.wsu.edu/wbp208 Resources: WSU Soils and Water Program: labs.wsu.edu/lahue/ Mount Vernon NWREC: mtvernon.wsu.edu WSU Small Grains Soil and Water Resources: smallgrains.wsu.edu/soil-and-water-resources/ Contact information: Gabe LaHue: gabiel.lahue@wsu.edu, cahnrs.wsu.edu/people-directory/people/wsu-profile/gabriel.lahue/, 360-848-6146

Today we talk about Base Preparation through a series of interviews discussing Soil Identification, Compaction, Geotextile, Geogrid, and Aggregates. Sponsors: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Cycle CPA⁠⁠⁠⁠⁠⁠⁠⁠⁠ Moasure

Data Streaming und Stream Processing mit Apache Kafka und dem entsprechenden Ecosystem.Eine ganze Menge Prozesse in der Softwareentwicklung bzw. für die Verarbeitung von Daten müssen nicht zur Laufzeit, sondern können asynchron oder dezentral bearbeitet werden. Begriffe wie Batch-Processing oder Message Queueing / Pub-Sub sind dafür geläufig. Es gibt aber einen dritten Player in diesem Spiel: Stream Processing. Da ist Apache Kafka das Flaggschiff, bzw. die verteilte Event Streaming Platform, die oft als erstes genannt wird.Doch was ist denn eigentlich Stream Processing und wie unterscheidet es sich zu Batch Processing oder Message Queuing? Wie funktioniert Kafka und warum ist es so erfolgreich und performant? Was sind Broker, Topics, Partitions, Producer und Consumer? Was bedeutet Change Data Capture und was ist ein Sliding Window? Auf was muss man alles acht geben und was kann schief gehen, wenn man eine Nachricht schreiben und lesen möchte?Die Antworten und noch viel mehr liefert unser Gast Stefan Sprenger.Bonus: Wie man Stream Processing mit einem Frühstückstisch für 5-jährige beschreibt.Unsere aktuellen Werbepartner findest du auf https://engineeringkiosk.dev/partnersDas schnelle Feedback zur Episode:

Thanks for tuning in to this agronomic Monday on RealAg Radio! Host Shaun Haney is joined by RealAgriculture's in-house agronomist, Peter “Wheat Pete” Johnson, to discuss a number of topics including: Profitability concerns; Fall compaction in flooded rice; and Choosing hybrid varieties. Also, hear a spotlight interview with Patrick Langille for Helena Products Group as... Read More

Thanks for tuning in to this agronomic Monday on RealAg Radio! Host Shaun Haney is joined by RealAgriculture's in-house agronomist, Peter “Wheat Pete” Johnson, to discuss a number of topics including: Profitability concerns; Fall compaction in flooded rice; and Choosing hybrid varieties. Also, hear a spotlight interview with Patrick Langille for Helena Products Group, as… Read More

Thanks for tuning in to this agronomic Monday on RealAg Radio! Host Shaun Haney is joined by RealAgriculture's in-house agronomist, Peter “Wheat Pete” Johnson, to discuss a number of topics including: Profitability concerns; Fall compaction in flooded rice; and Choosing hybrid varieties. Also, hear a spotlight interview with Patrick Langille for Helena Products Group, as... Read More

WSU graduate student Diana Salguero shares her research into soil compaction and soil properties that impact crop performance. Resources: Soil Health: soilhealth.wsu.edu Soil Health, Compaction: soilhealth.wsu.edu/compaction Contact information: Dr. Haly Neely: cahnrs.wsu.edu/people-directory/people/wsu-profile/h.neely/ Episode Transcription: smallgrains.wsu.edu/wbp193

10 03 24 Fixing Soil Compaction by Ag PhD

No ruts, no worries, right? Not so, at least not when it comes to deep compaction impacts. Air pockets and macropores in soil structure help move water down the soil profile, and where water goes, so do the nutrients. Compacted soils restrict root growth, oxygen, and nutrient and water movement, ultimately restricting yield potential. What’s... Read More

A conversation with Bridget Emmett, a principal scientist at the UK Centre for Ecology and Hydrology and a board member of the EU Mission Soil. Bridget shares her inspiring journey from a passionate botany student to a leading soil scientist, revealing the critical, yet often overlooked, intricacies of soil health. We explore its complex structure, teeming biodiversity, and indispensable role in sustaining life, all while diving into the cutting-edge technologies like remote sensing and digital twins that are revolutionizing soil monitoring and conservation.We'll discuss the urgent need to expand regenerative agricultural practices beyond early adopters to the broader farming community, tackling challenges such as rising costs and climate change. Bridget stresses the importance of effective communication and tailored advisory support from policymakers, shedding light on how these elements can facilitate a smoother transition to sustainable farming methods.From the strengths and limitations of satellite technology in soil health monitoring to the groundbreaking potential of digital twins, in this episode Bridget delves into the critical issue of soil compaction and the role of advanced machinery, robotics, and sensors in preventing it. We'll also examine the intricate balance between farming practices and their environmental impacts, the transition to plant-based diets, and the concept of a circular economy in agriculture.---------------------------------------------------Join our Gumroad community, discover the tiers and benefits on www.gumroad.com/investinginregenag. Support our work:Share itGive a 5-star ratingBuy us a coffee… or a meal! www.Ko-fi.com/regenerativeagriculture----------------------------------------------------More about this episode on https://investinginregenerativeagriculture.com/bridget-emmett.Find our video course on https://investinginregenerativeagriculture.com/course.----------------------------------------------------The above references an opinion and is for information and educational purposes only. It is not intended to be investment advice. Seek a duly licensed professional for investment advice.Send us a Text Message.https://groundswellag.com/2024-speakers/ https://planetary.dk/ https://foodhub.nl/en/opleidingen/your-path-forward-in-regenerative-food-and-agriculture/Support the Show.Feedback, ideas, suggestions? - Twitter @KoenvanSeijen - Get in touch www.investinginregenerativeagriculture.comJoin our newsletter on www.eepurl.com/cxU33P! Support the showThanks for listening and sharing!

Troy Deutmeyer visits with Chris about the recent planting delays and some of the key agronomic principles in a wet and delayed environments. The discussion includes the following topics: Compaction penalties versus calendar date. When is it time to go to earlier maturity hybrids? Seeding populations on late planting dates. Seed treatment benefits. Insecticide rates with corn on corn and later planting dates. Potential nitrogen loss: Leaching and volatilization. Potential future disease pressures to watch for. Crop protection and weed control: pre-emerge and post emerge applications. Replant decisions. Calendar dates and population considerations.

Live Business For Sale -We dive in with Matt Hash on his Mobile Trash Compaction Business which is listed for sale right now.FF&E - $220k Rev - $175k Profit - $80k Price - $449,000 https://www.bizbuysell.com/Business-Opportunity/Established-Mobile-Trash-Compaction-Business/2155561/

Last time we spoke about Operation Flintlock, the invasion of the Marshall islands. The allies brought overwhelming power against the Marshalls, unleashing the simultaneous invasions of numerous islands in an attempt to strike at the heart of the island chain at Kwajalein. The horror of the Gilbert Island campaign plagued the minds of the commanders who hoped to thwart such carnage. Airstrikes, naval bombardments and massive amounts of land based artillery smashed the Japanese defenders into submission before amphibious assaults were made. Countless islands such as Roi-Namur fell one by one as the Americans secured places to deploy further artillery to forces the ultimate submission of the defenses on Kwajalein. The casualties were light, but the fight for Kwajalein would soon descend into a bitter struggle, for the Japanese were not going to give up their stronghold without a good fight. This episode is The Fall of Kwajalein Welcome to the Pacific War Podcast Week by Week, I am your dutiful host Craig Watson. But, before we start I want to also remind you this podcast is only made possible through the efforts of Kings and Generals over at Youtube. Perhaps you want to learn more about world war two? Kings and Generals have an assortment of episodes on world war two and much more  so go give them a look over on Youtube. So please subscribe to Kings and Generals over at Youtube and to continue helping us produce this content please check out www.patreon.com/kingsandgenerals. If you are still hungry for some more history related content, over on my channel, the Pacific War Channel you can find a few videos all the way from the Opium Wars of the 1800's until the end of the Pacific War in 1945.  Operation Flintlock went off with a bang, and was initially a grand success. Aerial bombing, followed by naval bombardment and then land based artillery was smashing the Japanese defenders into submission. One by one the islands were falling into the Americans hands. On the second day of the battle, Roi-Namur, the northern objective was seized. Yet the stronghold of Kwajalein would provide much more of a fight. Back on the morning of January 28th Admiral Frederick Sherman's Task Force 58.3 landed a knockout blow against Kwajalein's airfield. Dawn saw a Hellcat fighter sweep ensure the airfield would not be tossing any further action before the amphibious assault occurred. The next day Sherman's force hit Eniwetok with the same kind of treatment. Sherman's carriers would remain off Eniwetok for 3 days while his aircraft smashed its airfields and ground installations. On the third say not much was left, just heaps of rubble and a few scattered palm trees stripped of their foliage. Sherman's airmen reported “they could not find any targets on the ground or in the lagoon that seemed worth bombing, and the island looked like a desert waste.” The warships came in on the 31st just off Roi and at 6:51am, Admiral Conolly maneuvered Maryland 2000 yards away from the northern beaches before unleashing 16 inch guns. As Holland Smith put it “So close that his guns almost poked their muzzles into Japanese positions.” By 7:15am the naval guns went silent as carrier planes came swooping in. Then 127mm artillery from Roi began firing, alongside cruisers and destroyers. Return fire occurred, but for a very short amount of time as they were snuffed out. Admiral Truman Hedding recalled “We learned a lot about softening up these islands before we sent the Marines in. We really worked that place over. They developed a tactic called the ‘Spruance haircut.' We just knocked everything down; there wasn't even a palm tree left.”  The Kwajalein atoll islands were hit with 15,000 tons of bombs and naval shells in 72hrs. Admiral Turner would make a Churchillian statement about the event “Never in the history of human conflict has so much been thrown by so many at so few.” Then transports carrying nearly 64,000 men of the 4th marine division and the 7th army division were launched at Ivan, Jacob, Allen, Andrew, Albert and Abraham islands. Once they were secured, the marines set up artillery batteries. The 7th infantry division was assigned the task of taking the banana shaped Kwajalein island as their colleagues set up 105mm and 155mm howitzers on nearby Roi-Namur. The 32nd and 184th regiments landed on the lagoon side at 9:30am on February 1st, first encountered only feeble and intermittent resistance. The eastern half of the island was secured in quick time, as the bombardments had certainly inflicted heavy casualties upon the enemy. The army moved slowly and methodically, advancing cautiously against the Japanese fixed positions. Soon they reached Carl Road, where they were met with an impressive defense system consisting of an anti-tank ditch on the south and a long rifle trench on the north. As February 2nd came on, so did another wide scale smashing of the Japanese. Artillery fire on Carlson Island and from the 32nd Regiments Cannon Company in the Wart Area coordinated with the tank and infantry movements. While the new assault units were moving up, the enemy in Corn Strong Point were kept under heavy artillery bombardment and were isolated from possible reinforcements by naval gunfire. Enemy guns that were still active in the northeastern end of the island were struck by dive bombers. The jump-off was ordered for 12:45. A series of delays deferred this crucial attack over an hour. To assemble the staff and coordinate the plans for employing tanks, artillery, and infantry while the 3d Battalion made its approach march, proved difficult to arrange. The time for the assault had passed before the planning difficulties were resolved. Then came notice of an air strike to be made at 1:15pm later postponed, on Admiral Turner's order, to 1:30, thus necessitating the suspension of all artillery fire. Since the attack on Corn Strong Point was to be immediately preceded by a heavy artillery barrage, the whole operation was postponed to 2:00. For the initial assault on the tank trap and Corn Strong Point, Colonel Logie's 32d Infantry's 3d Battalion was ordered to pass through its 2nd Battalion at Carl Road and to lead the attack. These fresh troops were to be supported by the tanks of A and D comapnies, 767th Tank Battalion and, from the left flank, by the tanks of B company, which would be temporarily detached from the 184th. The tanks of A company, 767th Tank Battalion, lined up along Carl Road to fire against the strong point, while those from B company took up positions almost at right angles to that road and prepared to strike the enemy from the left flank during the first stage of the attack. One of the batteries on Carlson continued to fire during the air strike, and the Cannon Company's howitzers also laid a preparation on the target area before the advance commenced at 2pm. Then, while the artillery lifted fire to ground northeast of the target, the tanks and infantry approached the tank trap in a 225-yard advance across open ground. The tanks poured machine gun fire into the area. Thirty yards behind them the troops came forward to the shelter of the tank ditch without receiving an enemy shot. The Japanese were pinned down. The assault initially saw the Americans pin down the Japanese. While the left wing of infantry troops started to push across the wide tank barrier, the tanks on their left momentarily broke off fire from the flank. A few tanks from A company, 767th Tank Battalion, moved toward the ocean to bypass the deep ditch, and the others after a brief hesitation laid a base of fire to cover the infantry's advance. The tanks hesitated to poke out along the flimsy wooden bridge by which Wallace Road cut through the angle of the tank trap. At this stage, a concentration of white phosphorus shells commenced to fall into the area in which I company, 32nd Infantry, was moving, and countless men were burned. After hesitating briefly the infantry moved steadily to the tank ditch. There the troops remained for some time because the medium tanks pulled back claiming they could not get over the ditch. The tanks finally broke through and began to make their way to the beach smashing pillboxes in the Corn strongpoint. An estimated 100 Japanese were killed in the area, the majority by demolition charges carried forward by engineer details while rifle and BAR men covered them. Little or no defense was put up against these tactics. The Japanese remained huddled in their shelters in spite of efforts made to coax them out to surrender. Only a single prisoner was taken in the whole area. Grenades were thrown into the shelters, and those who survived were then destroyed by demolition charges. Altogether, it took about 35 minutes to reduce Corn Strong Point once the American infantry got beyond the tank trap. Contact between the forward battalion of the 32nd Infantry and that of the 184th was temporarily lost during this fray, and K company, 32nd Infantry, moved through the left platoon of I company to establish contact firmly as soon as Corn Strong Point was taken. Advance to the Nora Road line seemed practicable within the time remaining before taking defensive positions for the night. To escape spending the night in an area too heavily wooded for security, the 3rd Battalion, 32nd Infantry, planned to advance northeast of the junction of Nora Road and Wallace Road, even though that would place its perimeter slightly forward of the 184th's front-line elements, which were resting just short of Nora Road itself. To the north, Colonel O'Sullivan's 2nd Battalion began advancing at 12:45 without tank support. F Company was on the right while E Company on the left along the lagoon. For the first 45 minutes no serious resistance was met. There were no tank obstacles in the area and the enemy's positions along the lagoon shore were less formidable than had been expected. At 1:30, however, the 184th had to lend its medium tanks to the 32nd Infantry as the latter moved against Corn Strong Point. This left the infantry unprotected at a time when they began to meet their first serious resistance. Without the tank support the infantry became stalled. The 184th suffered over 60 casualties by the end of the day, including the loss of F Company's commanding officer. O'Sullivan was forced to organize night defenses just 100 yards northeast of Carl Road, which also forced Logie to pull back to the abandoned trenches of Corn for the night. Heavy casualties were suffered that day, with 11 dead and 241 wounded. Japanese prisoners reported only 200 to 300 defenders remained, so the Americans expected a banzai charge to occur during the night. General Corlett's headquarters warned, "Be alert for counterattack at anytime day or night, it's bound to come. The Jap makes his suicide counterattack at dawn on the day after his cause becomes hopeless. Watch out tomorrow morning.” Yet there was no attach, so General Corlett prepared his men for a new assault at 07:15am. For the next day's operations, General Corlett ordered the two assault regiments: "Organize vigorous attack 0715 tomorrow… Finish the job not later than 1500 3 February. The Northern Force [at Roi-Namur] has finished the job…". At this point the Americans on Kwajalein faced a narrow 2000 yards of island. After artillery rained down at 7am, O'Sullivans 1st battalion advanced. In the first 150 yard B Company, along the lagoon, and Company A, at the right, advanced through rubble and broken trees west of Nora Road without more than scattered rifle fire from Japanese riflemen and occasional light machine gun fire from pillboxes. Their momentum carried them on for another 75 yards with such rapidity that the prospects for swift advance seemed excellent. B Company cleaned out an air raid shelter with grenades and shot down fleeing Japanese wearing arm bands like those of the American troops. Both companies were advancing over ground that had been under American mortar fire just before the jumpoff. At 8:06 enemy opposition was reported to be weak. After 250 yards the Americans reached the Admiralty area, finding a group of shattered buildings along the lagoon shore where it was believed the Japanese HQ was. Among the ruins were several underground shelters, with great earthen mounds above them. There were also concrete blockhouses.  Against strong resistance, B Company would not be able to advance further; A Company, meanwhile, pushed farther north and attempted to attack from the flank through the Admiralty area, but became quickly bogged down. At the same time, Logie sent forward his 3rd Battalion, with I Company rapidly advancing along the coast while K Company stopped to subdue a large concrete pillbox on the corner of the Admiralty area. By midday, I Company reached Noel Road and K Company successfully bypassed the Admiralty area. Yet behind them, there was a vertical gap including most of the Admiralty area between the two regiments. Thus, Corlett sent Logie's 1st Battalion to cover the gap and O'Sullivan's 2nd Battalion to swing right and continue the advance north while his 1st Battalion contained and neutralized the Admiralty area. At 3:30, the new attack was launched, with Logie's 3rd Battalion rapidly smashing into the Nap strongpoint while O'Sullivan's 1st Battalion concentrated on the Admiralty area and his 2nd Battalion attacked north towards Nob Pier. E Company started its attack before those of either G Company or the 1st Battalion. At 2:40 E Company began moving northwest. Somewhat more than half an hour later E Company  crossed Noel Road, with G Company on their right. 2 medium and 2 light tanks, taken over from the 1st Battalion, moved forward with each of the companies, and each had one squad of engineer troops with demolitions. Enemy rifle fire was heavy. The men broke up into small groups, proceeding unevenly in the general direction of Nob Pier. Between 6:30 and 7:00, Captain Peter Blaettler, commander of E Company was seriously wounded. Control from the battalion command post was lost seeing the men hugging the ground to avoid sharp fire from enemy riflemen. Colonel Aulich became separated from the main part of his battalion and was to remain so until the next morning, for all intensive purposes he lost command of his unit. The 2nd Battalion's attack was pushed along the eastern side of Will Road toward Nathan Road, but as sunset approached it became evident not only that Company E would not reach Nob Pier but also that across Will Road on the left flank there was an area with many strong enemy defense positions too powerful to be occupied in the 45 minutes before dark. Meanwhile, at 3:45 A Company 1st battalion was joined by 2 medium tanks and C Company  by 2 mediums and 2 M10 tank destroyers. At 4:05 they assaulted the western edge of the built-up Admiralty area along a 300 yard front, with A Company's right wing somewhat south of Noel Road. 10 minutes later they advanced towards the lagoon. Will Road was crossed shortly after 4:30. The enemy was much more firmly established between the highway and the beach, in pillboxes, blockhouses, and strong shelters. Mortar fire kept the enemy down until the tanks and infantry approached. The coordinated effort of tanks, infantry, and demolition teams ran very smoothly, gradually destroying the pillboxes and blockhouses of the Admiralty area, successfully reaching the lagoon by 6pm.  To the east, Logie's I Company rapidly reduced the weakly-defended Nap strongpoint and then pushed forward to the objective Nathan Road with haste while the other companies made slower progress against stronger defenses and would not be able to reach their objectives before nightfall. The Japanese in the areas south of the front line, were in greater numbers than on either of the preceding nights of the Kwajalein Island operation. They prowled in the forward area all night. Some incidents occurred as far to the rear as Corn Strong Point, more than a 1000 yards from the 32nd Infantry's advanced position. Japanese came out of shelters, screaming and yelling, throwing grenades, and charging at the men in their foxholes. They fired rifles and threw grenades from buildings that offered places of advantage. In a pocket northeast of the Admiralty area, they greatly harassed the companies near them. Attacks from the north and from the lagoon shore were also attempted by enemy troops at various times during the night. Just after sunset, a bugle could be heard sounding among the enemy shelters near the base of Nob Pier, and shortly afterward a headlong counterattack by screaming Japanese was made toward E and G Companies, 184th Regiment. As the Japanese tried to cross Will Road, they were cut down to the last man. 5 more attacks were broken up before they were actually in progress by barrages along the entire front from mortars and from the supporting batteries of artillery on Carlson Island; and more attacks followed after midnight. From various positions beyond Nathan Road, enemy machine gun, mortar, and artillery fire was directed into the forward area at irregular intervals during the night, sometimes coinciding so closely with the fire from Carlson Island that Japanese monitoring of the artillery radio was suspected. Nonetheless, over 1000 yards had been gained, by February 3. The Americans estimated they had killed around 1300 Japanese, more than were expected to still be in the island, at the cost of 54 dead and 255 wounded.  After sunset, several Japanese counterattacks and infiltration attempts were carried out against the steadfast Americans, all ending disastrously. Corlett expected to end the enemy resistance by February 4; but far too many small pockets remained in the rear and the reserve battalions were experiencing difficulties rooting them out. Corlett's final plan was for Logie's 1st Battalion to clear the remainder of the island, allowing  Companies C, B and A to attack through O'Sullivan's 2nd Battalion and Logie's 3rd Battalion. Unbeknownst to him, O'Sullivan also directed his 2nd Battalion to attack towards Nob Pier in order to complete the unfinished task of the previous day.  At 7:15, Corlett unleashed his final attack, supported by tanks. On the east, Logie's Companies A and B ran into a full-scale battle with the Japanese who had been bypassed the day before and who now poured heavy fire on the companies as they advanced toward the line of departure. It was not until 10:00 that the 2 1st Battalion companies reached the lines held by the 3rd Battalion. Then, the Americans successfully managed to advance 200 yards past Nathan Road, where the advance was stopped pending relief. Meanwhile, to the west, the attack of O'Sullivan's 2nd Battalion, supported by B Company , prevented the advance of Logie's C Company until 11:00. The Americans managed to push towards Nob Pier by 1:00, where they found no enemy resistance. Behind them, the lagoon shore continued to be mopped up, showcasing a surprising number of Japanese and Koreans surrendering.  All forward movement of the 1st Battalion had stopped, its line consisting of a series of small, exhausted groups in a dense confusion of debris. The ground was interlaced with innumerable trenches and foul with bodies of the enemy, many of them long dead. Some of the corpses had been mangled by maneuvering tanks, adding greatly to the nauseating stench that blighted the area. Finally, at 3:45, Logie's 2nd Battalion passed through the 1st to complete the assault along Kwajalein. These troops would successfully push to the island's northern tip, blasting through the remaining Japanese camouflaged dugouts and ruined concrete blockhouses.  As in every other island battle, Japanese stragglers had infiltrated the American lines through tunnels and overlooked bunkers, and the assault troops quickly learned to watch their backs. Nisei interpreters broadcast surrender appeals through loudspeakers, but there were only a few dozen takers, and most of the men who gave themselves up were Korean laborers. At long last, G Company reached Nero Point at 3:15. At 4:10 Corlett radioed to Admiral Turner: "All organized resistance… has ceased. The troops have been organized for mopping up operations." yet F Company, would still have to methodically destroy the enemy positions until they finally secured Kwajalein's northern end at 7:20. Ken Dodson went ashore the next morning. Writing to his wife, he described a desolate landscape of “shell craters and hillocks of upturned coral. Some of the Japanese had been dead from the first bombardment, the day before we landed. Their bodies were seared and bloated, and the stench was sickening. I saw one half buried in a pillbox. You could not tell whether he had on any clothes or not. The skin was burned off his back and his head lay a few feet from his body. Another looked like a bronze statue in Golden Gate Park. He lay forward in a crouch, helmet still on, both hands holding on to a coconut log of his pillbox. There were many, many others. I lie in bed at night remembering how they looked, and that awful sweetish sickening stench of powder, and kerosene and decaying human flesh, and I wonder, after all, what war is all about. I feel sorry for those Japs in a way. They died courageously after a stubborn, last-ditch, hopeless fight. They fought for the things they had been taught to believe in, with their poor little bundles with pictures of their wives and kiddies tied to their belts. . . . They can't tell me war is a fine and noble thing.' Losses during the last day were 252 wounded, with 65 Japanese killed and over 100 captured. Thus, for the Battle of Kwajalein Island, the Americans suffered a total of 142 killed, 845 wounded and 2 missing, killing around 4300 Japanese and capturing another 166. During the week after Operation Flintlock, numerous high ranking visitors descended on the battle-scarred islands of Kwajalein Atoll. Admiral Nimitz flew out from Pearl Harbor with an entourage of officers. On February 5, when fires were still burning on Kwajalein Island, he toured the blackened wastes alongside Spruance, Turner, Smith, and several other major commanders of the fleet and Amphibious Corps. Three weeks earlier Nimitz had been the guest of honor at a huge “Texas Picnic” in a Honolulu park. Walking among 40,000 sailors, soldiers, and civilians. He had pitched horseshoes, posed for photographs, and signed autographs. Afterward, the park looked as if it had been hit by a hurricane—clean-up crews had to cart away more than 50 truckloads of garbage and debris. An estimated 120,000 beer bottles had been left strewn across the grass. Now, upon setting foot on the lagoon beach at Kwajalein, Nimitz was waylaid by a mob of correspondents. “What do you think of the island?” one asked. The admiral drew a cheerful laugh by replying, “Gentlemen, it's the worst scene of devastation I have ever witnessed—except for the Texas picnic.” The operation had been a model one in almost every respect. The attacking force had achieved strategic surprise; artillery preparation, naval gunfire, and aerial bombardment had successfully softened up the target in a fashion unexcelled at any other time in the Pacific War; the ship-to-shore movement had been conducted expeditiously and without too many hiccups; supplies flowed ashore and to the front lines relatively smoothly and without interruption; the infantry-engineer teams assisted by tanks moved steadily clearing the enemy from shelters and pillboxes; and American casualties had been fairly light. Altogether, the battle for Kwajalein represented the ideal for all military operations. To complete the conquest of the southern Kwajalein islands, detachments of amphibian tanks had been landed on Buster and Byron back on February 3. Troops of the 2nd Battalion, 17th Regiment landed on Burnet and Blakenship on February 4; the chain between Ashberry and Bennett was secured by February 5. On that same day, Clement, Clarence, and Clifford Islands were also secured, although on Clifton a force of 101 Japanese fought to the death. Beverly, Benson and Berlin were also secured on February 5, seeing 119 Japanese dead on the latter. Bennett fell against the 7th Reconnaissance Troop and O'Sullivan's 3rd Battalion with 94 Japanese killed. Most importantly, Colonel Zimmerman's 1st and 3rd Battalions landed on Burton's Beach Orange 4. The fortifications on Burton were much lighter than those on Kwajalein, mostly machine gun positions and rifle pits. These were organized at the beaches with a concentration of dual-purpose machine guns grouped around the seaplane base in the lagoon. At the base of the south seaplane ramp was a 20-mm. antiaircraft machine gun. Near it, and between the two seaplane ramps, were two 13-mm. single-mount machine guns, three 7.7-mm. machine guns, and a concrete pillbox. Two 8-cm. dual-purpose guns were located on the ocean shore. The large number of empty machine gun emplacements would seem to indicate that the defenses of the island had not been completed at the time of the invasion. The few pillboxes found in the vicinity of the seaplane base were small, reinforced concrete shelters, each with two firing ports facing seaward. Most of the fire trenches and rifle pits were on the ocean side at the center of the island and at the north and south ends of the island. On the morning of February 3 after a heavy artillery, air and naval bombardment, the 1st Battalion traversed the southern end of the island against weak resistance and began pushing north supported by tanks, ultimately getting stopped by strong enemy resistance at Bailey Pier.  The following morning, the assault was resumed at 0730, the main enemy resistance had shifted to the eastern side of the island. The Japanese had reoccupied four pillboxes close to the American front line on the ocean side, and were able to hold up A Company, but with the aid of self-propelled mounts, the company took the positions. During the morning, a flight of five Navy bombers made two runs over targets that had been spotted with the aid of information from a prisoner. The planes dropped a total of two and three quarters tons on an ammunition dump, a shelter, and a heavy machine gun that had an excellent field of fire across the hangar apron. Direct hits on these targets apparently disheartened the enemy. Not a single shot was fired by them at any later time during the operation. They remained buried in their dugouts until forced out or until they killed themselves. By 1130, when the 3d Battalion passed through and took up the assault, B Company  had moved about 350 yards to the southern edge of the concrete apron, and on the right A Company  was fifty to 75 yards farther back. The 3rd Battalion continued the advance north against meager resistance, ultimately reaching Burton's northern tip by 12:10. After this, the last of the enemy were readily mopped up; and by 3:37, the island was fully secured. During this battle, the 17th Regiment suffered 7 killed and 82 wounded while reporting 450 Japanese dead. Meanwhile, to the north, the 25th Marines led by Colonel Samuel C. Cumming occupied some 55 islands in the northern part of the atoll between February 2-7, finding absolutely no enemy resistance. With Kwajalein Atoll finally secured, the next objective in the Marshalls for Admirals Nimitz and Spruance would be Eniwetok, where Major-General Nishida Yoshimi was preparing his men to fight to the last. Yet that's it for the Marshall islands today, as now we are traveling over to the CBI theater, where Generals Christison and Stilwell's offensives continued.  Now last time we left off with the gang in Burma General Liao's 22nd division, Colonel Rothwell Brown's 1st provisional tank group, General Merrill's Galahad Unit alongside Chinese and American engineers were busy building the Ledo Road through the Hukawng valley. Location parties up ahead cleared a trace the width of a bulldozer and put in the center-line stakes. The final clearing averaged 150 feet. The route of the Ledo Road in some cases followed existing roads, a circumstance that did not greatly diminish the amount of clearing needed. Most clearing was by bulldozer. Combat trails and access roads were cleared to the necessary minimum that would permit heavy equipment to use them. In the valleys, the road was generally built on embankments in order to lift it above flood level. In mountainous regions, side-hill cuts were used. The road itself had about seven culverts to the mile in the mountains and five to the mile in the lowlands. These culverts were most necessary as the road was a barrier to the normal runoff of water. Surfacing was with stream-bed gravel in the valley sections and, so far as hauling permitted, natural gravel in the mountainous sections. Surfacing was about ten inches thick on the average, and from twenty to twenty-eight feet wide. Compaction was by the normal road traffic. Two regiments of Chinese engineers did pioneer construction work. There was also a combat road, a hasty improvement of the existing Kamaing Road plus the Kachin and Naga trails, that ran through Shingbwiyang, Yupbang Ga, and Taihpa Ga, then went south. The trace of the Ledo Road was moved to higher ground on the north. Forward construction units were rationed from combat supply points. Meanwhile Vinegar Joe sought to end the campaign with a single decisive victory. He planned to deploy the 1st Tank Battalion as an armored spearhead against Maingkwan, the 1st battalion, 66th regiment, the 113th was to follow down the road to take over successive positions, while the 114th would assemble at Taihpa in reserve and the 112th was to protect the flank east of the Tanai, advancing on Mashi Daru. He expected his men to hit the enemy across their rear areas. Now January had been a very rainy month, armored warfare does not do well in mud, so it was important the terrain was dry for the offensive. Stilwell would end up on February 4th decided to shift the bulk of the 22nd division to seize Yawngbang-Lakyen line while General Sun's 38th Division cleaned up the area south and east of the Tanai.  Once this first phase was done, then General Liao's 2 regiments could support an armored advance south towards Walawbum. The bad weather, however, had also delayed road work and hampered their supply lines. Stilwell biding his time, building up a reserve at Shingbwiyang and Ningam, while the men progressed their work on the Ledo Road, and built an airfield at Taihpa before launching his second phase. This unfortunately also gave enough time for General Tanaka to prepare an orderly withdrawal towards Maingkwan. During early february, General Sun's 32nd division successfully accomplished their part of the mission, but to the southwest, the enveloping hook from the Taro Plain did not go as planned. By February 14th, the 66th regiment were beginning to arrive on the Taro Plain through heavy rain, but only the 3rd battalion of the 65th regiment managed to join them. The 66th regiment was forced to continue without the proper support until they diverted to Yawngbang Ga which they seized on the 16th. By the 18th, Stilwell and Liao personally went over to check on their regiment's location and found the entire force was within the neighborhood of the 66th command post. It seems the utter confusion during these movements saved the Japanese, as quoted by General Tanaka: "If the Chinese 65th and 66th Infantry Regiments operating in the vicinity of Yawngbang had been prompt in closing in on our left rear flank on the 15th or 16th, as predicted, the main force of the 18th Division would have faced a grave crisis." After sorting out the confusion,  the Chinese advanced from Yawngbang Ga to Lakyen Ga. There they captured a Japanese document indicating they were withdrawing. Thus another chance to envelop the enemy had thus been lost.    Meanwhile, to support Stilwell's offensive, the two Allied long-range penetration units, the Chindits and Merrill's Marauders, were preparing to embark on a new mission, codenamed Operation Thursday. It was to be the second Chindit expedition with the objective of mounting a long range penetration behind the Japanese who were opposing Stilwells forces in the Northern front. It was hoping the action would prevent the arrival of any reinforcements from the two Japanese divisions on the Central Front. General Hap Arnold wanted his airmen to take the Chindits behind Japanese lines, carry their supplies, evacuate their wounded and eventually fly them off, so he decided to create the 1st Air Commando Unit, under Lieutenant-Colonel Philip Cochram. The unit consisted of a squadron of P-51s; one of B-25s; 100 C4A Waco gliders; and a squadron of C-47s. Arnold spelled out the mission to Cochram and Lieutenant-Colonel John Alison, his deputy. "This man [Wingate] has really done some remarkable things. He has walked through the jungles. He has carried his supplies on mules. It takes him about six weeks to get his men through the jungle, across the rivers, and in behind the Japanese lines. The next time he goes in, I don't want him to walk. I want him to go by air. I want to make this an air operation completely independent of land transport. I want to demonstrate that you can use the air just like the navy uses the sea. You can land and maintain a force and support it in battle. I want you to go in there and take out General Wingate's wounded. We will make available the resources that you need. 'I not only want you to do that... but I want the USAAF to spearhead General Wingate's operations.' We gathered he wouldn't mind if we turned it into an air show." The mad onion lad Wingate also wanted to created strongholds within the Japanese controlled areas that could serve as bases to receive aircrafts of all types, store  supplies, hold wounded until they could be extracted, and act as centers for locals resisting the enemy. The motto for the Stronghold, as he called it, was “No Surrender”. Meanwhile Stilwell ordered Merril to close in on Ledo by February 7th, and the last American unit would arrive to Margherita on February 9th. Merrill's Marauders were to assemble at Ningbyen by February 21st whereupon they would envelop the 18th divisions east flank and block the Kamaing road near Shaduzap with the support of Sun's 113th Regiment. Simultaneously Stilwell's other troops were preparing for their attack on Maingkwan. Further in the south General Christison's 15th Corps was in a lot of trouble. The Japanese had been bringing in a lot of reinforcements for their forthcoming Arakan counteroffensive from both within and outside the Burma theater throughout December and January. By early February, General Hanaya had assembled his men and was ready to launch the first phase of Operation Ha-Go. General Hanaya planned to destroy the 7th Indian Division in the region east of Mayu Range using a pincer movement launched simultaneously from the north and south. After that, he would shift the main weight of his 55th Division near Ngangyaung against the 5th Indian Division in the Maungdaw region west of the Mayu Range. From there, he hoped to advance along the Kaladan valley to perform the phase of Ha-Go, named the Kaladan Operation. For this the men would advance towards Chittagong to distract attention from around Imphal and to draw the British reserves into Arakan.  On the night of February 3, Hanaya unleashed his offensive, with several columns, under the command of Major-General Sakurai Tokutaro, commander of the 55th Infantry Group. His force secretly infiltrated through the jungle under the cover of darkness, on the left bank of the Kalapanzin river near Buthidaung, through gaps between the 7th Division's widely separated brigades. The element of terrain and weather was paramount. Throughout the dry season a morning mist with heavy dew formed daily in the small hours and, unless cleared by rain and wind, normally persisted till well after sunrise; the noise made by the dew falling from the trees on to the dry undergrowth was loud enough to drown the sound of footsteps so that, in the jungle, movement in the early morning could be unheard as well as unseen. The tides were an important factor in planning, for at high tide many of the chaungs were unfordable. The knife-edge ridges into which the Japanese so often dug their defenses presented an unusual artillery problem. If guns were to bring effective fire to bear, they had to be sited on the line of the axis of a ridge, which was always difficult and sometimes impossible. Fire from any other angle meant that reverse slope defenses were untouched and accurate ranging was extremely difficult. The dense jungle covering the hilltops greatly restricted their use as observation points. Using the early morning mists, Hanaya's men shrouded their columns advance cutting deeply into the British defenses. At about 9 am the Gwalior Lancers reported to 7th Division by wireless that a column of Japanese about a hundred strong followed by another about eight hundred strong were approaching Taung Bazar. Major-General Frank Messervy immediately ordered his reserve brigade, the 89th to advance north to locate and destroy them and asked 15th Corps to speed up the arrival of the tanks. Christison ordered the 25th Dragoons to send a squadron to Sinzweya and 5th Division to send an infantry detachment to prevent infiltration over Goppe Pass. The 89th Brigade advanced north in two columns: the right column encountered the Japanese at about 4 pm near Ingyaung resulting in hand to hand fighting, and the left reached the bend of the Prein Chaung east of Preingyaung. The right column  dug in at Ingyaung and Lin babi and the left over the Prein Chaung. Although the main force of the 1st Echelon was delayed by some confusion, the advance guard surprised the Taung Bazar garrison at 7am. Without delay, the Battalion crossed the Kalapanzin River south of Taung Bazar, using captured boats, and was followed closely by the 2nd Echelon and the 3rd Battalion of the 112th Infantry Regiment. The main body of the 1st Echelon crossed the river northwest of Taung Bazar on the morning of the 5th. By 9am Taung Bazar was overwhelmed as the Japanese forces crossed the Kalapanzin River to cut the Ngakyedauk Pass in order to isolate the 7th Division. Meanwhile the 1st Battalion, 213th Regiment headed towards Ngangyaung. The battalion advanced parallel to the Sakurai Column before moving towards Goppe Bazaar. It was held up short of its objective, however, by the leading elements of 26th Indian Division committed from army reserve on 5th February to bolster 15th Corps. Despite this local setback, the Japanese hauled their mountain guns and equipment over the Mayu Range, midway between Goppe and Ngakyedauk, before attacking administrative troops, bridges, dumps, ambushing convoys and building a roadblock on the main line of communications along the Bawli-Maungdaw road. It failed to prevent supplies reaching 5th Indian Division, however, whose ammunition, equipment and food was transported by sea to Maungdaw. Overnight the rear areas of 15th Corps were transformed into the front line with administrative troops bearing much of the burden of dealing with advancing Japanese troops. To the surprise of many officers, they displayed a determination and fighting spirit unknown a year before and took a heavy toll of the Japanese attackers bearing out Slim's direction that every man in the army should be a soldier first and a tradesman or specialist second. The bulk of the 112th regiment led by Colonel Tanahashi Shinsaku marched towards the pass as the 2nd battalion 143rd regiment and Sakurai's HQ advanced south. The quickly found enemy resistance near Ingyaung which delayed their advance for over 2 days. Failing to make contact with General Sakurai, the Battalion continued its advance southward, bypassing Awlanbyin. Major Gen. Sakurai and his headquarters also got involved in fighting off enemy counterattacks near Ingyaung on the 5th and 6th and due to failure of his communications, was unable to keep in touch with his units. To further support the offensive, Japanese fighters and bombers from the 5th Air Division's 7th Air Brigade launched a heavy offensive to gian air superiority over the battlefield, using 34 fighters and 10 bombers. Between the 4th and 14th their fighters flew 350 sorties, and bombers attacked the Bawli and Briasco bridges and Sinzweya. Spitfires intercepted them but had less success than before. Japanese losses were believed to be some 14 aircraft destroyed and a number damaged, while RAF losses during the same period were around 11 fighters. On february 5th, having made such quick progress, Hanaya ordered the 143rd regiment to advance north. The 3rd battalion, 143rd managed to infiltrate through the Indian brigades en route and joined Sakurai's men to hit the pass. Seeing the danger, General Slim decided to reinforce Christison with the 26th Indian division led by Under General Lomax. Christison in turn ordered Lomax to move it forward to Bawli Bazar as quickly as possible. Upon their arrival at Bawli North, the 71st Brigade was then ordered to relieve the detachment from 5th Division on Goppe Pass and then attack the Japanese operating in rear of 7th Division. Likewise the 36th Indian division of Major-General F. W. Festing sped up their advance towards Chittagong while C-46 Commandos and C-47 Dakotas air dropped ammunition, food and other supplies to the front units. On the morning of the 6th, the 112th Regiment reached the sector north of Sinzweya and overran the headquarters of the British-Indian 7th Division while the 1st Battalion cut the Ngakyedauk Pass. In a perfect position to envelop the enemy in Sinzweya, Colonel Tanahashi disregarded the vital necessity for speed and delayed for 24 hours, giving the British time to establish a perimeter defense in the Sinzweya Basin. East of the range at about 5:00am, an enemy force, estimated at battalion strength, penetrated the widely separated posts held by the company of 24th Engineer Battalion defending 7th Division Headquarters, established machine-gun posts on tracks throughout the headquarters area and broke into the signal center. In hand-to-hand fighting the attackers were driven out, but not before all communications had been cut and ciphers compromised. Tanks from Sinzweya moved to the sound of the fighting as soon as it was light but the ground prevented them from reaching the headquarters area; rain which set in about 8:30 further hampered them and they had to withdraw. At about 10:00am, the signal center was finally overrun. Messervy, unable to exercise command any longer, sent orders to all branches of his headquarters to destroy papers and equipment of value and make their way in small parties to Sinzweya. Most of them succeeded in doing so during the following 24 hours. Major-General Frank Messervy and his staff would manage to successfully escape towards Sinzweya. Consequently, instead of ordering a general withdrawal like the Japanese expected, Christison directed the 9th Brigade to organize a defense of Sinzweya, which was the weakest link of the four isolated, self-contained all-round defensive boxes held by each brigade of the 7th Division. By the 7th, the defense of Sinzweya, also known as the Admin Box had been consolidated. The perimeter consisted of a series of small defended posts held, in the main, by administrative units, except at the south east and southwest corners where the roads entered the area. These were held by 4/8th Gurkhas and a company of 2nd West Yorkshire. There were insufficient troops to hold the whole of the Point 315 feature, and thus there was a deep reentrant between the southeast and northeast corners of the perimeter extending back to the southern end of Ammunition Hill. Most of the artillery was disposed on the southern face with attachments holding perimeter posts. The 25th Dragoons were in mobile reserve in two harbors held by a company of 3/4th Bombay Grenadiers, one each side of Ammunition Hill. The 2nd West Yorkshire constituted the infantry reserve and was located with divisional and garrison headquarters on the western side of Ammunition Hill. The main dressing station in the southwest corner was being moved to a more secure area. During the night, the Japanese launched an assault against Sinzweya, yet the tenacious defenders managed to hold on against the fierce enemy pressure. That night, the 33rd Brigade also managed to repulse an attack against Sinohbyin, though the arrival of these reinforcements would allow Sakurai to extricate himself from Ingyaung and head to Sinzweya to take command over the assault. On February 8, all British troops east of the Mayu range were receiving supplies by air, yet the strong presence of enemy fighters disrupted the first few attempts. Eventually, British air superiority would be restored. The No. 31 Squadron and 62 Squadron were reinforced on the 10th by 194 Squadron and on the 25th by 117 Squadron, recently arrived from the Middle East. Not only were 7th and 81st Divisions kept supplied with food and ammunition, but such amenities as cigarettes, rum, mail, razor blades and newspapers were delivered by air to the troops in increasing quantities as time went on, certainly a morale booster. Throughout the battle the Strategic Air Force and 224 Group gave constant close support to 15th Corps. In addition to providing escorts for transport squadrons, Hurricanes harried road, river and coastal transport on the Japanese lines of communication to Arakan that movement by day into the area virtually ceased. Tactical bombing of enemy positions was undertaken by two Vengeance squadrons which flew no less than 269 sorties in just over a week. The transports flew a total of 714 sorties in 5 weeks, successfully delivering nearly 2300 tons of supplies. From the night of February 8 onwards, the Admin and other boxes would also hold firm against repeated ferocious Japanese infantry night assaults, occasional air attacks and limited artillery bombardment from a handful of mountain and battalion guns by day and a medium gun firing from the nearby tunnels, thus showcasing the new spirit of the British-Indian troops. As quoted by Lieutenant-General Pownall: “We've learned how to fight where we stand and NOT to be frightened of the bogey of infiltration.” I would like to take this time to remind you all that this podcast is only made possible through the efforts of Kings and Generals over at Youtube. Please go subscribe to Kings and Generals over at Youtube and to continue helping us produce this content please check out www.patreon.com/kingsandgenerals. If you are still hungry after that, give my personal channel a look over at The Pacific War Channel at Youtube, it would mean a lot to me. Kwajalein has finally fallen, leaving the rest of the Marshalls at the mercy of the colossal allied air, land and sea forces. Within Burma, the Chinese, British, Indian and Americans were ferociously meeting the Japanese, showcasing their dominance in the theater was no longer as sure thing, now the Japanese faced a much stronger enemy.   

Is music the key to better brain health later in life?  A woman manages to survive trash compaction and we look back on the first groundhog day. Plus, this day in history — the details of the ABSCAM scandal were released to the public – and if you don't know what that is, well, keep listening! Music Link to Better Health (GNN) Woman Suvives Trash Compaction (AP News) History of The Groundhog (History) (Independent) (Wild Explained) (Punxsutawney Groundhog Club) AbScam (Britannica) Contact the show - coolstuffcommute@gmail.com Instagram - Facebook 

10 23 23 Fixing Soil Compaction by Ag PhD

In this episode, Jon Teater (Whitetail Landscapes) and Austin Delano (Mossy Oak BioLogic) discuss ways to reverse drought concerns, long-term drought resilience properties and soil compaction. Austin provides soil improvement techniques to include mechanical methods of changing water collection and retention. Jon explains high level ways to architect your landscape for water, and how water can be the most important resource we have. Jon and Austin discuss fallow areas, and Austin provides plant options that are more drought tolerant, which can change these areas and your food plots. Austin explains the concept of subsoiling and how this can change the ground we work. Jon and Austin discuss when to subsoil, the multitude of benefits and what they have learned from doing this technique. Austin suggests certain tractor requirements and how this technique alleviates hardpans. Austin explains to Jon the new radishes that are being released by biologic and how he expects these to be a game changer to those across the country. Check out the Sportsmen's Empire Podcast Network for more relevant outdoor content! Social Links https://whitetaillandscapes.com/ https://www.facebook.com/whitetaillandscapes/ https://www.instagram.com/whitetail_landscapes/?hl=en https://www.instagram.com/austind_1/?hl=en https://www.plantbiologic.com/ https://www.mossyoak.com/ Learn more about your ad choices. Visit megaphone.fm/adchoices