Podcasts about Terraform

Database branching has, for a long time, been a troublesome piece in the modern developer workflow puzzle: a good idea in principle but in practice a slow and often expensive challenge. Get it right and you can accelerate productivity and remove bottlenecks; get it wrong and you're potentially creating all sorts of trouble for yourself, from privacy risks to additional complexity. However, things are changing. Thanks to the emergence of new platforms such as Neon, Supabase and Databricks Lakebase, branching a database can become as familiar to developers as managing code branches and multiple environments with, say, Git and Terraform.  On this episode of the Technology Podcast, host Ken Mugrage is joined by his Thoughtworks colleague Cam Casher and Databricks' Kevin Hartman to discuss the work Thoughtworks and Databricks have been doing together on Lakebase. They discuss the platform, their experience using it with Spotify's Backstage and the opportunities database branching can offer software engineering teams in an increasingly AI-assisted and agentic world. Read Cam and Kevin's recent series on using Databricks Lakebase with Backstage: https://www.thoughtworks.com/insights/blog/data-engineering/backstage-lakebase-databricks

IPv8 уже в драфте, Terraform хоронят в блогах, а одна компания жжёт $7M в год на Claude Code. Собрали новости DevOps, которые вы накидали через бота. О ЧЁМ ВЫПУСК Новостной выпуск: накопилось 63 новости, разобрали самое горячее. И снова с нами Ярослав. В этом выпуске: • IPv8: драфт в IETF - ASN в первых 32 битах, старый IPv4 во вторых. Без NAT и dual-stack, плюс токен-идентичность на каждый девайс • Terraform 1.15: переменные в source и version модулей, отдельная аутентификация для S3 backend • "Terraform is dead": разбираем хайповую статью - спека как desired state, Pulumi, CDK и причём тут AI • Terragrunt 1.0: units, stacks и фильтр по affected-ресурсам через git worktree • NGINX 1.30: sticky sessions, keep-alive и HTTP/2 к апстримам, Early Hints (103), Encrypted Client Hello • Экономика AI: Semi-Analysis масштабировала Claude Code до $7M/год, дефицит RAM • Google Agent Sandbox: новый Kubernetes CRD между StatefulSet и Deployment Сквозная мысль выпуска: AI ускоряет всё, но без понимания, как работают системы, спека и вайб-кодинг рано или поздно стреляют в ногу. ГОСТЬ Ярослав Бледковский - Un-principal SRE, Wargaming ССЫЛКИ Все новости выпуска (тезисы, голосование, ссылки): https://dkt-ai.github.io/episodes-news/episodes/episode-97-ru Присылайте новости через бота: @dkt_news_bot Упомянутые ресурсы: • IPv8 draft (IETF): https://www.ietf.org/archive/id/draft-thain-ipv8-00.html • Terraform 1.15: https://github.com/hashicorp/terraform/releases/tag/v1.15.0 • "Terraform is dead" (статья): https://grahamgilbert.com/blog/2026/04/20/terraform-is-dead/ • Terragrunt 1.0: https://github.com/gruntwork-io/terragrunt/releases/tag/v1.0.0 • NGINX 1.30: https://github.com/nginx/nginx/releases/tag/release-1.30.0 • AI tokens (Dylan Patel / Semi-Analysis): https://www.youtube.com/watch?v=LF3aUIM57uw • Kubernetes Agent Sandbox: https://github.com/kubernetes-sigs/agent-sandbox ПОДКАСТ YouTube - www.youtube.com/@DevOpsKitchenTalks Apple Podcasts - https://apple.co/41O6mqA Spotify - https://t.ly/Jg5_2 Yandex Music - https://music.yandex.ru/album/10151746 PodBean - https://devopskitchentalks.podbean.com НАВИГАЦИЯ 00:00 - Интро: вы уже на IPv6 или ещё IPv4? И снова в гостях Ярослав 02:53 - Anthropic и 200K карточек от Маска: лимиты Claude отпустило 04:26 - Адженда из 63 новостей через наш Telegram-бот

This Open Source Startup Podcast episode has our co-hosts Robby and Tim in conversation with James Bayer, Chief Product Officer at software development platform Flox.Flox's open source, also called flox, provides a software environment platform powered by package manager Nix.In this episode, James shares lessons from his career across Cloud Foundry, Pivotal, and HashiCorp, where he helped turn widely adopted open-source projects like Terraform into sustainable businesses. His core takeaway is that support-only open source is difficult to scale; successful companies usually monetize the “multiplayer” capabilities that teams and enterprises need while keeping individual usage free.Now at Flox, James sees a similar opportunity built on top of Nix, a powerful but historically complex technology. He joined because Flox makes Nix dramatically easier to use, helping developers and AI agents manage software environments and dependencies. He also discussed the balance between open-source principles and commercial viability, and why he remains optimistic about the future of software development in the age of AI.

Bryan and Adam discuss the process of restoring a software project--BattleTris--untouched and unbuilt in over 20 years! How did LLMs help restore code Bryan started in the mid-1990s and what does that teach us about developing and maintaining software in the future?Your hosts were Bryan Cantrill and Adam Leventhal.Previously on Oxide and FriendsOxF s03e24 - Fork in the road for Terraform?OxF s06e02 - Engineering Rigor in the LLM AgeOxF s06e01 - Predictions 2026!!Some of the topics we hit on, in the order that we hit them:BattleTris on githubSurge 2011 ~ Closing Plenary ~ Theo SchlossnagleFrom the Governor of DelawareIf we got something wrong or missed something, please file a PR! Our next show will likely be on Monday at 5p Pacific Time on our Discord server; stay tuned to our Mastodon feeds for details, or subscribe to this calendar. We'd love to have you join us, as we always love to hear from new speakers!

In this episode of the Crazy Wisdom Podcast, host Stewart Alsop sits down with returning guest Ekue Kpodar for their third conversation together, covering a wide range of topics at the intersection of technology, geopolitics, and the evolving information age. They dig into Ekue's unconventional setup of running local AI models across roughly 15 computers, the growing case for open source models over closed ones from companies like OpenAI and Anthropic, and how Chinese open source models may be positioned to outcompete Western alternatives on a global scale. The conversation also touches on vibe coding and the democratization of software development, the strategic use of small models for IoT and enterprise applications, the role of Israel and China as dominant players in the information age, and how smaller nations and even individuals may wield outsized power as AI continues to collapse the cost of knowledge work. You can find Ekue Kpodar on X @ekpodar and LinkedIn.Timestamps00:00 Stewart welcomes Ekue for their third episode, diving into vibe coding and AI-driven development changes.05:00 Ekue explains using Claude on Chrome to auto-reply on Skool, burning tokens through screenshots, and Playwright as a more efficient alternative.10:00 Stewart describes his Claude-dependent planning and coding agent system breaking after a model update, prompting him to build his own chatbot.15:00 Small models discussed as critical for IoT, defense, and privacy-focused enterprises building internal APIs instead of routing traffic to OpenAI.20:00 Open source versus closed source debated, with Chinese models gaining global traction while US foundational labs remain expensive and restrictive.25:00 SaaS apocalypse explored as AI commoditizes knowledge work, with Linux and Terraform cited as proof open source still generates wealth.30:00 OpenAI's sci-fi terminator fears explained as the reason they stayed closed source, ultimately handing China a strategic open source advantage.35:00 China's economic dumping strategy applied to AI, potentially displacing US model dominance globally the same way manufacturing was disrupted.40:00 Israel's signals intelligence dominance discussed alongside asymmetric warfare, drones defeating tanks, and information control replacing military muscle.45:00 Global information age rankings debated, Israel leading, US and China tied, France and Poland emerging as sovereign tech players.50:00 Qatar, NVIDIA, and Iran cited as proof that rare resources and technology matter more than population size in the 21st century power landscape.Key Insights1. Running local AI models on a network of affordable computers can be more cost-effective than relying entirely on third-party APIs. By using compressed or smaller open source models locally, developers can handle repetitive or lower-stakes tasks without burning through expensive tokens from providers like Anthropic or OpenAI.2. Small AI models are becoming increasingly important for IoT, defense applications, and companies that do not want to send sensitive data to external providers. Organizations can download open source models, run them on internal servers, and build proprietary APIs around them, creating something like an intranet of specialized small models.3. The value created by AI tools is being redistributed away from traditional SaaS companies toward foundational model providers and individual builders. People are canceling subscriptions to software they once paid hundreds per month for, because AI now allows a single person to build comparable tools themselves.4. Open source technology does not eliminate the ability to profit. Linux and Terraform are both open source yet made their creators wealthy. People will still pay for installation, setup, troubleshooting, and customization even when the underlying software is free.5. China is applying its longstanding manufacturing dumping strategy to artificial intelligence by releasing cheap open source models globally, which threatens to erode US dominance in AI the same way Chinese manufacturing undercut other countries for decades.6. In the information age, the size of a country or institution matters far less than its access to rare resources or advanced technology. Qatar, Israel, and NVIDIA each demonstrate that small populations or headcounts can wield enormous global negotiating power through concentrated technological or resource advantages.7. Asymmetric warfare is redefining military power, with inexpensive drones defeating tanks that cost millions to build. This shifts the advantage toward nations that excel at signals intelligence and information management rather than those with the largest conventional military forces.

What if Earth isn't just our planet anymore? In this episode of UFO WARNING, we explore the controversial UFO believer theory that Earth may already be undergoing alien terraforming. From climate manipulation and genetic engineering claims to mysterious UFO activity around nuclear sites and environmental disasters, we examine the speculation that a non-human intelligence could be influencing humanity and reshaping the planet for an unknown purpose.We dive into theories surrounding ancient astronauts, hybridization programs, geoengineering conspiracies, and the idea that humanity itself may unknowingly be helping transform Earth for extraterrestrial occupation. Featuring discussion of researchers like Jacques Vallée and John E. Mack, this episode explores one of the darkest and most fascinating concepts in UFO lore.Are aliens preparing Earth for themselves? Has the process already begun? And what role could humanity play in a hidden cosmic agenda?Listen now to this deep dive into alien terraforming theories, UFO conspiracies, climate manipulation claims, ancient astronaut speculation, and the possibility that Earth's future may not belong entirely to us.

What if you could run 35 AWS services locally in under 25 milliseconds, using just 13 megabytes of memory, with a single Docker command and no cloud bill? That's exactly what Floci does.In this episode, Frank Delporte talks with Hector Ventura, the creator of Floci, a free and open-source cloud emulator built with Quarkus and GraalVM native compilation. Hector walks us through why he built it when LocalStack dropped its open-source community edition, how AI tooling helped him accelerate development of new service integrations, the challenges of keeping GraalVM happy with third-party libraries, and the road ahead for Azure and GCP support.If you're a developer who wants fast local testing, a DevOps engineer writing Terraform, or a student learning cloud without the cost, Floci is worth a look!Guest: Hector Ventura Foojay Author page LinkedInLinks On Foojay: Introducing Floci: A High-Performance, GraalVM-Powered AWS Emulator Floci project site Floci on GitHub Migrate from LocalStackContent00:00 Introduction of topic and guest01:48 What is Floci?02:15 How Floci compares to LocalStack03:01 Why Hector started Floci04:02 Floci emulates the cloud APIs05:02 How additional services got integrated with AI assistance06:31 Meaning of the name Floci07:07 Why Quarkus and GraalVM as the starting point for Floci09:35 How Floci starts up very fast and only uses a low amount of memory12:18 GraalVM can be hard with some libraries or frameworks14:02 What is needed to use Floci14:56 The challenges to support AWS, Azure, GCP and finding contributors20:24 Funding Floci21:04 How data is persisted in Floci22:37 Verifying Floci versus the "real" APIs with compatibility tests23:56 In the future: UI for Floci25:04 Biggest challenges while creating Floci25:32 Functionality compared between Floci and LocalStack and migrating28:15 Feedback from the Floci users28:58 Long-term plans for Floci29:59 Biggest surprises during the development of Floci31:00 Best use-cases for Floci32:12 In the next releases...33:31 How to get started with Floci35:00 Conclusion

Parce que… c'est l'épisode 0x2FD! Shameless plug 3 au 5 juin 2026 - SSTIC 2026 24 et 25 juin 2026 - Troopers 26 et 27 juin 2026 - leHACK 19 septembre 2026 - Bsides Montréal 1 au 3 décembre 2026 - Forum INCYBER - Canada 2026 24 et 25 février 2027 - SéQCure 2027 Description Dans cet épisode spécial, Nicolas Bédard revient sur sa participation à Google Next 2026, son quatrième événement du genre, mais le premier qu'il vivait en tant qu'employé de Palo Alto plutôt que de Google. Il y présente les quatre intégrations majeures que Palo Alto a lancées en partenariat avec Google, dans un contexte où l'intelligence artificielle agentielle se déploie à grande vitesse — souvent sans encadrement de sécurité adéquat. Le contexte : la plateforme Gemini Enterprise se réorganise Avant d'aborder les intégrations, Nicolas explique les changements de nomenclature chez Google. Gemini Enterprise est désormais divisé en deux volets : Gemini Enterprise Apps : l'interface utilisateur permettant d'accéder aux agents, aux connecteurs de données (SharePoint, Outlook, etc.) et aux outils IA. Gemini Enterprise AI Platform : la couche cloud sous-jacente, qui remplace l'ancienne plateforme Vertex AI. Cette restructuration simplifie la compréhension de l'écosystème : tout ce qui touche à l'IA en entreprise chez Google s'appelle désormais Gemini Enterprise. Intégration 1 — Prisma AIRS dans l'Agent Gateway La première et probablement la plus stratégique des intégrations concerne Agent Gateway, une nouvelle fonction au cœur d'Agent Cloud, la plateforme Google pour exécuter des agents IA. Agent Gateway agit comme un point d'insertion au sein des load balancers internes : il permet d'injecter des fonctions de sécurité ou d'autres capacités dans les flux de communication entre agents, entre un agent et un serveur MCP, ou entre un utilisateur et son agent. Palo Alto a annoncé l'intégration de son AI Runtime de Prisma AIRS directement dans ce gateway. L'idée est de centraliser la sécurité plutôt que de la déléguer à chaque développeur. Concrètement, cela signifie que les garde-fous — validation des comportements, prévention des fuites de données, protection contre les abus — s'appliquent automatiquement à tous les agents, sans que les équipes de développement aient besoin d'expertise en cybersécurité. Agent Gateway s'articule autour de trois piliers : l'identité, le runtime (pare-feu IA) et l'observabilité. Pour l'instant, seuls les deux premiers sont ouverts aux partenaires tiers comme Palo Alto. Cette approche répond directement à la préoccupation numéro un des équipes de sécurité en entreprise : le Shadow AI, soit l'utilisation non contrôlée d'outils IA par des employés ou des développeurs, qui expose l'organisation à des risques importants. Intégration 2 — Le scan de modèles open source via Gemini Enterprise Apps La deuxième intégration adresse un risque souvent sous-estimé : l'utilisation de modèles IA provenant de plateformes communautaires comme Hugging Face. Si les grands modèles commerciaux (Google, Anthropic, OpenAI, Mistral) offrent des garanties relatives à leur provenance, les modèles open source sont publiés par n'importe qui, sans vérification systématique. Ils peuvent contenir des vulnérabilités cachées, des kill switches, du code malveillant dissimulé dans l'enveloppe du fichier (notamment via des fichiers pickle), ou avoir été entraînés sur des données douteuses. Palo Alto a lancé un agent de scan de modèles directement accessible depuis Gemini Enterprise Apps. Intégré au cycle de développement logiciel (SDLC), cet agent permet à un développeur de soumettre un modèle hébergé sur Hugging Face ou dans un registre interne pour vérification avant déploiement — sans avoir à sortir de son environnement de travail habituel. Nicolas précise que cet agent fonctionne dans le tenant du client, ce qui garantit que les données restent dans l'infrastructure de l'entreprise. Intégration 3 — Wildfire et l'analyse de malwares dans les flux IA La troisième intégration s'inscrit dans une approche plus classique, mais essentielle : la détection de malwares dans les fichiers transitant par des agents IA. Google utilisait déjà la technologie de pare-feu de Palo Alto pour son Cloud NGFW. Ce qui est nouveau à Google Next, c'est l'ajout de Wildfire, le moteur de sandboxing de Palo Alto, sous la forme d'un service géré appelé Advance Malware Sandboxing. Concrètement : lorsqu'un utilisateur envoie un fichier via un agent Gemini Enterprise — vers un dépôt documentaire, par exemple — ce fichier est intercepté, analysé dans un environnement isolé, puis validé avant d'être stocké. Cela protège les autres utilisateurs ou agents qui pourraient accéder à ce fichier ultérieurement. L'enjeu est d'autant plus grand que les malwares générés par IA sont désormais créés on the fly, spécifiquement pour une cible, ce qui rend les approches basées sur des signatures connues insuffisantes. Intégration 4 — Le pare-feu dans l'Application Design Center La quatrième intégration touche à l'expérience des développeurs. Google a ouvert son Application Design Center (ADC) aux partenaires tiers. L'ADC est un outil visuel dans la console cloud qui permet d'assembler des services Google (Cloud Run, Pub/Sub, BigQuery, etc.) pour créer des applications. Palo Alto a travaillé avec Google pour permettre l'insertion native d'un pare-feu dans ces assemblages. Un développeur qui crée une architecture dans l'ADC peut maintenant ajouter un gabarit Palo Alto d'un clic. Une fois la configuration validée, l'outil génère automatiquement le code Terraform correspondant, incluant les load balancers et le pare-feu. L'objectif est de démocratiser la sécurité réseau en la rendant accessible à des développeurs qui ne maîtrisent pas nécessairement les subtilités des pare-feux d'infrastructure. Collaborateurs Nicolas-Loïc Fortin Nicolas Bédard Crédits Montage par Intrasecure inc Locaux réels par Nicolas Bédard

Mock-интервью с Николаем Лебедевым - DevOps/SRE-инженер, 17 лет в Linux, 4 года AWS EKS. Stack: Terraform, Flux, Cassandra, Kafka, Vault, SOPS. Два часа - много практики, много каверзных вопросов. ЧТО СПРАШИВАЛИ ☁️ AWS: EKS и IRSA, VPC с нуля (CIDR, multi-AZ, multi-region), managed K8s vs self-hosted, Elasticache, Golden Signals и метрики SRE.

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/

The history of technology is often told as a history of progress. Thomas Dekeyser turns this story on its head, leading a journey to the critical junctures where people have rejected and tried to undo, rather than adopt, new technologies. In Techno-Negative: A Long History of Refusing the Machine, Dekeyser challenges readers to rethink the terms of our technological present and future. Here, Dekeyser is joined in conversation with Brian Merchant and Sarah Sharma.Thomas Dekeyser is a filmmaker and lecturer in human geography at the University of Southampton and author of Techno-Negative: A Long History of Refusing the Machine.Sarah Sharma is acting Vice Dean, Research and Program Innovation at the School of Graduate Studies at the University of Toronto, where she is also professor of media theory at the ICCIT/Faculty of Information and director of the Institute of Communication, Culture, Information and Technology. Sharma is author of Insufferable Tools: Feminism Against Big Tech and In the Meantime: Temporality and Cultural Politics.Brian Merchant is author of Blood in the Machine: The Origins of the Rebellion Against Big Tech and The One Device: The Secret History of the iPhone. He is a reporter in residence at the AI Now Institute, former technology columnist at the Los Angeles Times, co-founder and editor of Vice's speculative fiction outlet TERRAFORM, and his writing has appeared in the New York Times, Wired, The Atlantic, Harper's Magazine, and Fast Company.EPISODE REFERENCES:Donna Haraway's “A Cyborg Manifesto” (1985 essay)Film: Machines in FlamesTechno-Negative: A Long History of Refusing the Machine by Thomas Dekeyser is available from University of Minnesota Press. Thank you for listening.

PHP Podcast – April 30, 2026 Hosts: Eric Van Johnson & John Congdon Another fun episode of the PHP Podcast! Here’s what we covered: The Drone Slayer Strikes Eric and John wrapped up a Padres game at beautiful Petco Park in downtown San Diego — and things got weird on the way out. A rogue drone started buzzing around a busy intersection, lingering on a guy on a scooter, before making a fateful attempt to fly in front of Eric’s car. It did not make it. The controller came running out, Eric kept driving, and John has already dubbed him “the drone slayer.” Eric still hasn’t looked at whether his wife’s car got scratched, which feels like the bravest choice of all. Baseball Week Never Ends The reason today’s episode started an hour early? Baseball. John’s week was wall-to-wall: a Tuesday night little league game, the Padres game with Eric on Wednesday, practice Thursday night, the playoff draft reveal Friday, a little league game Saturday, and another Padres game Sunday. Eric pointed out John was wearing his own last name on a jersey to a Padres game, which opened up a whole sidebar on why anyone buys a $200 jersey with a player’s name on it when players change teams every two years anyway. Walking Pneumonia and the Power of the Right Antibiotic John’s week was also scrambled because his son had been diagnosed with regular pneumonia — but after not getting better, a second doctor visit revealed it was actually atypical (walking) pneumonia, which requires a completely different antibiotic. Once on the correct medication, his son bounced back almost immediately. The kid had been pushing himself trying to feel well enough for sixth grade camp, but there’s really no faking it with the wrong treatment. The Archie Situation — AI Standups Gone Sideways Eric has had a rough stretch after Anthropic shut down OpenClaw, the platform that powered their internal Discord bot Archie (a.k.a. Alfred). Archie had been running daily team standups, generating weekly summaries, letting team members tag it with updates throughout the day, and even setting reminders. Everyone got spoiled by it. Since then, attempts to migrate to Ollama — both locally and through the web service — have been plagued by slow response times and dropped messages. Eric is close to pulling the plug and going back to the old manual method, and he’s not happy about it. Claude SSH’d Into Eric’s Server and Fixed Everything For weeks, Eric had been fighting a broken Postiz Docker container — a self-hosted social media scheduling tool he uses to post across platforms. After updates broke it and multiple attempts at a fresh install still left it broken, he dropped the problem in Claude’s lap and explained the whole situation. Claude asked for permission to SSH into the remote server on Eric’s Tailscale network, and Eric said sure. Thirty minutes later, Claude had identified the culprit — a Temporal workflow engine losing its configuration on restart — wrote a fix script, configured the service to reconfigure properly on boot, and even set up a cron job to restart the container on reboot. Eric’s still trying to find that chat to review exactly what it did, but the service is running. GitHub is Getting Hammered by AI Agents GitHub has had a rough patch of outages, and the numbers tell the story: 20 million new repos per month, 1.4 billion commits, 90 million pull requests — with a dramatic spike right at the start of 2026. Part of the culprit? AI agents being unleashed on codebases to automatically open pull requests from backlog tickets. Eric has a client doing exactly this, and while it sounds impressive from the owner’s perspective (“look at all this work getting done!”), the developers on the ground report that a high percentage of those AI-generated PRs require significant human correction before they’re anywhere close to mergeable. The comparison to Reddit’s early explosion — and the one engineer who basically didn’t sleep for two years — felt pretty apt. The GitHub Security Vulnerability Nobody Talked About As if the outages weren’t enough, GitHub quietly disclosed a serious security vulnerability: a specially crafted git push — using malformed options in the push metadata — could allow arbitrary code execution on GitHub’s own servers. Eric had to dig to find the blog post because GitHub was not exactly shouting about it. To their credit, they state that their investigation found no evidence the vulnerability was ever exploited in the wild. But knowing that a specific sequence of bytes in a git push could have handed someone the keys to GitHub’s servers is genuinely unsettling. The Creator of Ghosty Is Leaving GitHub Mitchell Hashimoto — creator of the Ghostty terminal and formerly of HashiCorp — announced he’s leaving GitHub, where he’s been a user since 2008 (user #1299). This comes shortly after the Zig programming language made the same move, also citing reliability concerns. Eric was mildly skeptical of the “announcing I’m leaving” genre of posts, pointing out that GitHub doesn’t especially need your permission to stop using it. Notably, Hashimoto’s post doesn’t say what he plans to use instead. John joined GitHub in 2009, which led to a fun live expedition through his commit history — turns out he got serious about coding right around July 2013, roughly when DiegoDev landed its first client. Update Composer. Like, Right Now. PHP developers tend to set Composer up and forget about it — but there’s been a serious security vulnerability patched in a recent release that you absolutely want. The fix is simple: just run composer self-update. It updates in place and keeps a rollback copy in case anything breaks. While you’re at it, if you have global Composer packages installed, run composer global update to catch those too. Eric noted that Composer should really warn you when you’re significantly behind versions, the way Claude Code does. Until it does, just make a habit of it. Linux Kernel Exploit — Patch Your Servers A CVE was shared in the phparch Discord that affects Ubuntu, Amazon Linux, and Red Hat: a Linux kernel exploit that lets an attacker gain root access with a remarkably small payload — around 732 bytes targeting setuid. It’s a good reminder that the old sysadmin badge of honor (“my server has 5-year uptime, never rebooted”) is the wrong mentality now. With tools like Terraform and infrastructure-as-code, spinning up a freshly patched machine is the move. Keep your operating systems current, especially Linux servers running in production. Holly Built a PHP Tek App — And It’s Already Good Community member Holly built a native attendee app for PHP Tek, available now in beta on iOS (via TestFlight) and Android. You can browse the schedule, select the talks you want to attend, and it’ll warn you if two of your picks are in conflict — a “merge conflict,” as Eric put it. Best of all, it sends push notifications when sessions you’ve favorited get moved or rescheduled, which happens constantly at tech conferences. Eric’s wife installed it without being told anything about it and figured it out on her own — about as good a usability test as you can get. The app is built natively in Swift and Kotlin. Be kind to Holly — this is a gift to the community. PHP Tek in 19 Days + New PHP Architect Merch PHP Tek is nearly here — 19 days out in Chicago. A brand new PHP Architect elephant is coming (tentatively named Holly, after a live-stream vote). Eric also walked through new merch at store.phparch.com: a v-neck version of the classic rainbow PHP Architect shirt, and his personal labor of love — the “I have standards, specifically PSR 0, 1” tee — which he admits has sold exactly zero copies. If the hotel room block is sold out by the time you read this, reach out to the team directly and they’ll see what they can do. Links from the show: Postiz — Open Source Social Media Scheduling GitHub Security Advisory: Remote Code Execution via Git Push Options PHP Tek 2026 — Chicago PHP Architect Store PHP Architect Discord An update on GitHub availability Migrating from GitHub to Codeberg Ghostty Is Leaving GitHub Securing the git push pipeline: Responding to a critical remote code execution vulnerability Composer 2.9.6 fixes Perforce Driver Command Injection Vulnerabilities (CVE-2026-40261, CVE-2026-40176) Copy Fail: 732 Bytes to Root on Every Major Linux Distribution. Host: Eric Van Johnson X: @shocm Mastodon: @eric@phparch.social Bluesky: @ericvanjohnson.bsky.social PHPArch.me: @eric John Congdon X: @johncongdon Mastodon: @john@phparch.social Bluesky: @johncongdon.bsky.social PHPArch.me: @john Streams: Youtube Channel Twitch Connect & Hire PHP Architect Website Twitter/X Mastodon Hire PHP Developers Looking to hire PHP developers? Email support@phparch.com – Joe and the team are available for consulting, infrastructure work, Ansible playbooks, and code review. Partner This podcast is made a little better thanks to our partners Displace Infrastructure Management, Simplified Automate Kubernetes deployments across any cloud provider or bare metal with a single command. Deploy, manage, and scale your infrastructure with ease. https://displace.tech/ PHPScore Put Your Technical Debt on Autopay with PHPScore CodeRabbit Cut code review time & bugs in half instantly with CodeRabbit. Music Provided by Epidemic Sound https://www.epidemicsound.com/ Join Us Live Next Week Youtube Channel Got feedback? Join us on Discord at discord.phparch.com The post The PHP Podcast 2026.04.30 appeared first on PHP Architect.

In episode 287 of our SAP on Azure video podcast we talk about the SAP Deployment Automation Framework and the partner solution Cloud MotionAlmost two years ago we had a really good session on the SAP Deployment Automation Framework. SDAF helps customers to quickly deploy SAP sytems - not only for test and demo environments, but production ready, high available systems. All of this is available open source on GitHub. Now some partners have taken the code, collaborated with us and build tools and applications around this. Today we want to talk about this with Stergios and Kimmo. You can test the bot at: https://sdaf-ops.com/Find all the links mentioned here: https://www.saponazurepodcast.de/episode287Reach out to us for any feedback / questions:* Goran Condric: https://www.linkedin.com/in/gorancondric/* Holger Bruchelt: https://www.linkedin.com/in/holger-bruchelt/ #Microsoft #SAP #Azure #SAPonAzure #Deployment #Infrastructure #Automation #Terraform #Ansible- 0:00 Intro- 1:35 Introducing Stergios Gaidatzis and Kimmo Forss- 2:55 SAP Deployment Automation Framework (SDAF)- 5:20 Tooling - Azure DevOps, Terraform, Ansible- 9:00 Introduction Cloud Motion GmbH- 10:45 SDAF - Implementation Process- 14:10 Devops Engineer and Application Owner- 18:40 SDAF-OPS- 23:30 Demo- 27:00 Azure DevOps- 30:00 Pipline is triggered- 36:00 SDAF-OPS Architecture- 42:20 Implementation Process

 Elizabeth Barron returns to the show just four weeks after her debut appearance for a wide-ranging follow-up on her first months as Executive Director of the PHP Foundation. Elizabeth shares the key findings from her community listening tour, covers the upcoming PHP community survey in partnership with JetBrains, talks about the Foundation’s plans for transparency, documentation, and guest blogging, and discusses the challenges of the PHP newcomer experience. The episode also features a candid conversation about public speaking anxiety, conference culture, and the enduring warmth of the PHP community. Topics Covered PHP Foundation Community Findings Main Topic Elizabeth published a blog post summarising the findings from her listening tour across the PHP community. Four key themes emerged: Foundation transparency — Many people don’t know what the Foundation is doing; the website is too generic and needs to better reflect the team’s actual work. Marketing of PHP — How PHP is perceived externally, and how the community can better promote the language. Community support — What the Foundation can do to better support developers, user groups, and sub-communities. The language itself — Feedback and ideas relating to PHP’s ongoing development. Elizabeth noted that the volume of feedback was a good sign — silence would be a much bigger problem. A Part Two of the blog post is in the works and will cover strategy and next steps. Newcomer Experience & Documentation Gap A recurring theme from the community feedback was how hard it is for brand-new developers to get started with PHP: There is no single central “landing page” for newcomers — help is scattered across Discord, Reddit, local user groups, and elsewhere. The PHP manual assumes a baseline of programming knowledge that true beginners don’t yet have. Many existing beginner resources have not been updated as the language has evolved. PHP lacks the kind of gamified, beginner-friendly learning apps that Python and JavaScript enjoy. Mike noted that most coding bootcamps are JavaScript-first, leaving a gap for PHP-based introductory learning. Elizabeth is exploring whether the Foundation can help coordinate and amplify existing resources rather than compete with them — and fill in the gaps that remain. Matt Stafer’s recent involvement with the Foundation was highlighted as a potential access point for reaching newcomers, given his large following. PHP Community Survey (with JetBrains) The PHP Foundation is running a community survey in partnership with JetBrains (makers of PHPStorm). The goal is to generate open, usable data that anyone — including the Foundation, JetBrains, and the broader community — can analyse. Community members were invited to suggest their own questions (the submission window closed on the day of recording). The full survey was expected to launch in early June. Foundation Transparency & Hiring Update The Foundation’s developer hiring process (which had been open in a previous cycle) was paused while Elizabeth settled into the role and internal processes were stabilised. Many of the Foundation’s developers currently work in silos; improving collaboration and communication across the team is a near-term priority. The Foundation’s blog will be opened up to guest bloggers — Elizabeth teased an upcoming post she’s excited about but couldn’t yet name. Developer applications are expected to reopen in autumn 2025. Public Speaking Anxiety & Conference Culture An unexpectedly personal and engaging segment where all three speakers opened up about their experiences with social anxiety and public speaking: Mike shared that despite running the show and talking to guests regularly, he struggled to approach familiar faces at PHP conferences in person. The group discussed strategies: preparing thoroughly (Elizabeth and Shane), improvising with bullet points (Chris), and the benefit of pairing up to speak (Mike and Chris’s planed joint talk). Elizabeth reminded Mike that audiences are always rooting for the speaker — and encouraged him to keep pushing through the discomfort. Chris mentioned Merge PHP (online conference, 14th May) as a useful middle step between podcasting and live in-person talks. PHP Appalachia — A Community Origin Story Elizabeth shared the story of PHP Appalachia, one of the earliest informal PHP community gatherings, held in the Gatlinburg, Tennessee area starting around 2006. Around 12 people from the PHP IRC channel (phpC) rented a cabin with Wi-Fi, gave talks, and sat around a campfire — and Elizabeth is still friends with every single person who attended. Links & Resources PHP Foundation The Executive Director’s Manifesto — Chris’s article on PHP Architect, based on Elizabeth’s previous episode (free to read) Merge PHP — Online PHP conference, 14th May (Andy Snell: “More than just a cache, data-structured databases”) PHP Tech Conference — Coming up in a few weeks, running alongside JS Tech for the first time PHP Architect Magazine — Use code ALIVE3 for the first 3 months of a digital annual subscription free PHP Architect Store — T-shirts, caps, mugs and more PHP Architect Discord — Join the community, ask questions, and chat with PHP core contributors PHP Architect Social Media X: https://x.com/phparch Mastodon: https://phparch.social/@phparch Bluesky: https://bsky.app/profile/phparch.com PHPArch.me: https://phparch.me/@phparch Discord: https://discord.phparch.com Partner This podcast is made a little better thanks to our partner. Displace Infrastructure Management, Simplified. Automate Kubernetes deployments across any cloud provider or bare metal with a single command. Deploy, manage, and scale your infrastructure with ease — without the steep learning curve of Docker, Kubernetes, and Terraform. Perfect for solo developers and small teams who want enterprise-grade infrastructure without the enterprise-grade complexity. https://displace.tech/ Music Provided by Epidemic Sound The post PHP Alive And Kicking: Episode 29 Elizabeth Barron appeared first on PHP Architect.

Doug Houghton, director of global channels at Alkira There’s a line from this episode that’s worth leading with: “Networking is not sexy until it doesn’t work.” That’s Doug Houghton, Director of Global Channels at Alkira, and it’s a pretty concise summary of why his company exists. Alkira was founded by the team behind Viptela – the startup that essentially created the SD-WAN category before being acquired by Cisco. The lesson they carried out of that experience is that SD-WAN, for all its promise, still ran into the limits of underlying infrastructure. You ended up with disparate networks, latency constraints, and complexity that didn’t disappear – it just moved somewhere else. What they built in response is Network Infrastructure as a Service (NIaaS) – a cloud-native, consumption-based global backbone that abstracts multi-cloud connectivity into a single managed plane. The pitch to partners is concrete: consolidate 50 physical firewalls into virtualized functions, reduce total cost of ownership by 40-70%, and do it without a rip-and-replace cycle. The timing matters, and Houghton is direct about why. AI workloads – distributed large language models, agentic workflows reaching across multiple clouds simultaneously – demand a level of network elasticity that legacy infrastructure simply wasn’t designed for. Alkira’s argument is that they’re the smooth road that makes AI-driven infrastructure actually work in practice. For Canadian partners, Alkira has real resources on the ground: a solution architect based in Toronto, a dedicated channel account manager, and publicly referenceable Canadian customers including contact center provider ContactPoint 360. The Connect Partner Program, launched in March 2026, puts approximately 20 percent total margin on the table across base discount, rebates, MDF, and POC SPIFFs – with average initial deals around $500,000 USD and typical expansion of 4x in year one. Canadian partners interested in the conversation can reach the team at partners@alkira.com. Read Full Transcript Robert Dutt: Hello and welcome to In The Channel from ChannelBuzz.ca, bringing news and information to the Canadian IT channel community for the last sixteen years. I’m Robert Dutt, editor of ChannelBuzz.ca and your host for the show. If you were around when SD-WAN was the big disruptive idea in networking – the promise of simplifying branch connectivity, cutting costs, getting smarter about traffic – you probably also remember it didn’t quite deliver everything it promised. Not because the technology was bad, but because the underlying network architecture couldn’t keep up. You still ended up with complexity. It just moved somewhere else. That problem is essentially the founding insight behind Alkira. The company was built by Amir Khan and Atif Khan, the same team behind Viptela, the startup widely credited with creating the SD-WAN category before Cisco acquired it. What they learned in that experience is that SD-WAN, without a proper global backbone, just creates a different set of headaches. So they started fresh and built what they call NIaaS – Network Infrastructure as a Service – a cloud-native, consumption-based approach that abstracts the complexity of multi-cloud connectivity into something you could stand up, as my guest today puts it, with just a username and a password. The timing is not accidental, because what AI demands from a network – elasticity, low latency, the ability to reach distributed workloads almost anywhere instantly – is exactly what legacy infrastructure wasn’t built to handle. My guest is Doug Houghton, Director of Global Channels at Alkira. Doug has been in the channel a long time, knows the technology in a way that might genuinely surprise you coming from a channel chief, and has a lot to say about what it all means as a real business opportunity for Canadian VARs and MSPs. Let’s get right into it, my chat with Doug Houghton. Doug, thanks for taking the time. I appreciate it. Doug Houghton: It’s my pleasure. Thank you for having me on today, Robert. Robert Dutt: So you were part of the team that built up the SD-WAN market at Viptela back in the day. What did you learn there that told you the next big thing was going to be NIaaS, and why now? Doug Houghton: First off, that’s a great question. I felt a bit like a passenger in a car racing a thousand miles an hour when we were doing software-defined wide-area networking. What we learned was that without organizing your cloud infrastructure properly, your cloud bill gets ridiculously large – especially if you keep your control element decoupled from your data plane in the cloud with all these workloads churning. But what we really learned, and what’s applicable to what we’re now doing at Alkira, is that SD-WAN truly did deliver on its core promise. It allows customers to influence traffic based on link quality and improve the user experience. If you’re on a phone call and it starts to get goofy, you can move over to a better-performing link in real time without dropping the call. That’s powerful. And the same with data traffic. What I hadn’t fully thought through was what happens as global companies start to adopt SD-WAN and disaggregate across locations in Southeast Asia, China, Latin America, and everywhere else. The latency back to the control element isn’t easy to contend with. So you ended up with organizations making decisions that effectively created four separate, disparate networks for latency purposes. And that was not part of the original promise. What we learned was that you need a global backbone that’s high throughput and low latency. The edge can still be SD-WAN – there are real things in SD-WAN that people still want, whether that’s WAN optimization, deduplication, caching, policy-based routing, forward error correction. All of that still has practical application, and site-to-site communications are still needed in many use cases. But Alkira was built inside the cloud first, employing the same principle of decoupling control plane from data plane for scale. By abstracting the cloud infrastructure, we were able to remediate the latency that those four geographically dispersed networks created. We’re the global backbone – that middle mile with high throughput and low latency – and then you connect these clusters of SD-WAN networks together and all of a sudden the promise of SD-WAN gets a lot more consumable. You have a singular network managed from a singular control plane and element management orchestrator, and you can still get all the benefits of SD-WAN at the local sites. Robert Dutt So in plain language, a Canadian MSP or VAR is used to selling network hardware or managing someone else’s infrastructure. How is selling, deploying, and managing NIaaS different from what they’re already doing, and what makes that distinction important? Doug Houghton: Let’s take a half step back and talk about what NIaaS actually is. It’s Network Infrastructure as a Service. What Alkira does is abstract the cloud infrastructure and build a routed overlay on top of it. We think of it as a virtualized colocation facility that connects and normalizes communications across your entire network. For managed service providers and service providers, our solution accelerates bringing their customers to cloud applications, cloud workloads, storage, and everything else the cloud promises. The way I explain it to my mom – and I’ve told this joke once already today because I’m sitting in a partner’s office right now – is this: if you went to Russia, Japan, Argentina, and San Francisco all in one day and had to transact in each place, and you could speak the native language in each one, that would be ideal. What we focused on was normalizing communications regardless of the cloud service provider, colocation provider, data centre – private or public – or whatever type of router is at the branch office. As an MSP or service provider that comes in, what we give to our customers and partners is a username and a password. That lets you come in and – for your old-school folks in the audience – essentially etch-a-sketch your network together. You can turn a couple of knobs, and it’s not that we’ve cranked the amp up to eleven, we’ve just removed all the numbers and automated everything. It just knows what you want to do. It’s a routed BGP overlay with the control plane abstracted from it, so the forwarding plane can route around things like the CrowdStrike outage, or losing an AWS region – which happens more frequently than AWS would like to admit – or any cloud service provider incident. The multi-cloud reality has accelerated adoption, but it presents a new problem: you’ve got an AWS expert on staff, but you don’t have an Azure, GCP, OCI, or Alibaba Cloud expert. Those are all different languages. When I tell my mom that we normalize the communications between all the assets in the network and make it easy to connect to all of them, she gets that. For the MSP looking to monetize something new or add another revenue stream, we offer a couple of compelling things. In the middle of our stack, we place a solution inside the cloud – sitting in a VPC, VNet, VCN, or Google VPC – right in the middle of all the cloud, SaaS, and WAN workloads. We’ve pleased a lot of customers by lowering total cost of ownership through the consolidation of network services they already have in their environment, in the form of virtualized network functions. Take a Palo Alto firewall deployment – say you have fifty Palos out there, all talking to Panorama, with a security engineer managing policy centrally. Instead of having fifty firewalls on the ground, you consolidate them. You go from the ground – five to ten milliseconds to the nearest public cloud PoP – hop onto the Alkira fabric, and terminate that traffic on a virtual port on our exchange point. In the middle of that exchange point, sitting in a VPC or VNet, you place a Palo Alto virtualized network function. You get the IP address of the Panorama server, and if you didn’t tell the security engineer anything had changed, they would not know. The form factor changes, but not how they interact with Panorama, how they build policy, or anything about how they secure the traffic. That remains exactly the same. We virtualize the instance and place it on a global high-throughput, low-latency backbone inside our exchange point. We deploy exchange points in HA pairs, anywhere from 100 Mbps to 40 Gbps. The customer or service provider consumes one, and we maintain the other on their behalf – because every thirty days we’re fixing bugs and doing maintenance. We swing production workloads to the backup, do the work on the primary, then reverse the order, all while keeping these customers up and running. Because we’re delivering this as a service, it has to always be on. One of the most important architectural decisions we made from the start was ensuring those two exchange points are always running active-active in a full mesh configuration, buttressed by hundreds of other exchange points globally distributed – all synchronized and aware of each other’s states. Robert Dutt: You’ve said that legacy networks can’t handle what AI demands, specifically in terms of elasticity. Can you unpack that a little? When an MSP’s customer starts deploying language models or agentic workflows, what is it that actually breaks? Doug Houghton: Good question, and I’ll give you an honest answer. I’ve started to fall in love with Claude – I think it’s one of the coolest things in the world. I can do all sorts of creative things with it. But Claude isn’t talking only to me. He’s a bit of a flirt – he goes to a lot of different places to get knowledgeable about various things and produce the outcomes I’ve asked for. And those other places are where you run into problems. I used to say the three biggest AI providers are GCP, AWS, and Azure. That’s still largely true. But the likes of Anthropic and other AI labs are distributing LLM workloads everywhere. Without the right network underneath that, it’s like buying the hottest car and driving it down a pothole-filled road. What we offer is a high-throughput, low-latency, elastic network. If you need to turn it up in a heartbeat, you can. We helped complete the S&P Global and IHS Markit merger network integration in about a tenth of the time they expected, because we’re natively segmented. Think about those two networks as large datasets that AI agents need to access. You have to secure the traffic, and you need it to be elastic – able to reach anywhere, instantly, to produce the outcome the agent was asked for. The ability to go anywhere on a road that’s smooth as glass, in the hottest car possible – that’s what we offer. Our network infrastructure solution is an abstraction: a forwarding plane that goes everywhere, and your imagination is really the only limitation. Speed, elasticity, and securing access – even for agentic, self-directed workflows – it’s still a critical element. And nobody – I said this earlier today, so I’ll say it again – networking is not really sexy until it doesn’t work. If I have to get in and route-peer and manually configure transit gateways, I’m going to punch myself in the face repeatedly. I just don’t want to do it. It slows everything down. I can automate it with Terraform, sure. But I want to consume it now. I want to prompt it now. I want the outcome now. Robert Dutt: You’ve launched Alkira NIA, your AI co-pilot and network infrastructure assistant, along with an MCP server last year. It’s interesting – you’re essentially putting AI on top of the infrastructure that’s enabling AI. What does NIA actually do for an MSP’s day-to-day operations? Doug Houghton: Maybe I have a limited imagination, but I still use it like a utility. NIA is great because it allows you to search through all our documentation in a more organized way. We have amazing documentation – there’s a lot of it – and when you’re looking for a specific configuration or something captured in a knowledge base, that tool is really useful. But continuing the utility theme: how do I do something? If I want to create a micro-segment to distribute to a bunch of business units, or build an isolated Layer 3 routing table and get it to various business units, and then set up billing with specific billing tags for each segment – I know how to do that because I’ve done it many times. But a new user may not. You can use the NIA agent to search the documentation, search previous implementation notes, best practices, all of that. That’s real value. But you can also ask it something like “why is the sun bright” and it won’t return the answer you expect. I’ve done that too. Robert Dutt: Let’s talk about the Connect Partner Program and the economics. You’ve got the Partner Profit Stack – tiered margins, quarterly rebates, MDF, SPIFFs, the Connect Pipeline Fund. It’s a full toolkit, and it’s stuff partners have seen before. What’s the real math? What does a Canadian MSP at the Premier tier actually walk away with on a typical deal after they’ve done the work? Doug Houghton: Usually about nineteen percentage points – maybe a little more. On the pre-sale side, when we get into a POC, our Premier partners can earn a $1,000 SPIFF. We close about 85% of our POCs, so there’s real value in that. Add in the rebates and MDF access, and the total haul is closer to 20% on each deal. Worth mentioning: we’ve been a 100% channel company since May 2022. My partner David Klubinoff, my technical counterpart – we worked together at Viptela and we started the Alkira channel together. It took a couple of weeks to convince our CEO that going 100% channel was the right call. I think he’s a believer now. We’ve driven significant revenue for the company, and our partners are our thought leaders – out in the market talking about our solution and solving customer problems. I was in Chicago yesterday doing a technical enablement session with thirty-plus SAs and SEs. We had the classic SD-WAN questions, and a lot of questions about segmentation and M&A. There’s enormous consolidation happening in insurance, healthcare, and other sectors, and the overlapping IP address problem that comes with mergers is something MSPs face all the time. We’ve entirely simplified that. You build a NAT policy right in the solution and the overlapping IP issue is resolved within an hour. In the case of S&P Global and IHS Markit, they thought their merger network integration was going to take a couple of years. The issue was largely the overlapping IP addresses – IHS couldn’t talk to the HR applications at S&P, and vice versa, plus all the other interdependencies. You need a fast way to solve the overlapping IP problem before you can even get to the real work. That’s been a core design element of our solution from the very start: take care of the small things, and people can move faster and get to market faster. Our biggest MSP – and this is a publicly referenceable customer – is CEDA, a French-based organization that provides managed network services to 95% of the world’s airlines. For them, it means being able to turn up a new customer faster, connecting on-premises assets to their control elements so they can begin actually managing that network. Speed, and the efficiencies and cost reductions that come from it – that’s what it does for all MSPs. If you’re consolidating fifty firewalls into virtualized functions, you’re making a good commission, getting MDF support, quarterly rebates, and a SPIFF when you engage us collaboratively on a POC. All of that happens at an accelerated rate. I’ve been screaming from the mountaintop about our solution for about four years. Invariably, you’d walk into a room, say “Hi, I’m Doug Houghton from Alkira,” and they’d say “Who?” That’s starting to happen a lot less, which is a genuinely nice thing. Over the last twelve to twenty-four months, the business has grown exponentially, the diversity of our partner ecosystem has increased, and partner margins have been very healthy. The tiered structure was really about celebrating partners who have invested in us. Honestly, I’m waiting for the day my boss tells me to stop incentivizing partners – because when that happens, I’ll know we’ve hit the apex. Our partners will be generating so much revenue that someone gets uncomfortable with what we’re paying out. I can’t wait for that day. Some of the more interesting things in the program came from actually listening. I went around and talked to a bunch of partners about their ideal partner programs and built from there. And one of the realizations – I thought it was significant – was what we were actually doing on the post-sale side. We white-glove every implementation right now, because it’s critically important to us. We haven’t lost a customer, and we intend to keep it that way. But that doesn’t scale forever. So the question became: why don’t we help our partners productize the post-sale work? We built a product catalog, a pricing calculator, and a new partner portal we’re about to release, with its own AI agent for searching market assets. The product catalog was a light bulb moment. We pay healthy margins on the pre-sale side at every tier of Alkira Connect. But we had never touched the post-sale side at all. We’re largely automated and NIaaS is as simple as possible to consume – a username and a password. My thirteen-year-old could configure a network, and she’s really smart. But there’s still some implementation work. You still need to build policies in Panorama. There’s still DDI work. There are still services that partners can benefit from – and all partner types, MSPs, VARs, master agents, sub-agents, service providers, now have a post-sale commission opportunity. Robert Dutt: You mentioned services – you’ve got services attach plays around modernization assessments, segmentation design, migration sprints. Starting from zero, how long does it realistically take a partner to get their first deal with those services attached through the door, and what does the ramp look like? Doug Houghton: There’s a lot in that question. Let’s take a half step back. We have virtual sales and go-to-market training – three modules – and then five or six technical training modules. We’ve got a lab-in-a-box environment, foundational and advanced technical training, and DDI training. Partners typically start there. Then we run regular in-person and virtual sessions – one partner has regular office hours with me, my SE counterpart David, or our architect Christopher Arenas, and we just invite partners to come and ask questions. Getting partners genuinely comfortable with the technology is the most important thing we do, because nobody goes out and sells anything unless they’re confident they can explain how Alkira solves their customer’s problem. That’s what I’m doing in Chicago today. Our customers tend to be fairly large. We’ve got our first Fortune 10 customer now. The more complex the network, the larger and more global the deployment – multiple countries, security vendors, firewalls, DDI providers, load balancers, service providers, colos. We sit right on top of all of that. The average sales cycle is about 190 days – a little over six months. A newly enabled partner might encounter an M&A overlapping IP use case, recognize the problem, and say “I think we can solve this with Alkira.” They go through a POC together with us, the customer commits, and that first deal closes around 190 days. A little class week: it’s actually 190 and a half. The average deal size is about $500,000 USD. We then see significant expansion: typically 4x growth in the first twelve months after the initial close, and around 8x in the second twelve months. Real incentive to stick with it. We’re loyal – if the customer doesn’t kick the partner out, we go to bat with that partner on every expansion deal. We land, then expand, with the same partner. BNSF, one of our other public references, has expanded several times to address more and more use cases. The solution gets sticky and customers are genuinely surprised by how easy it is. On the post-sale side, we come in and help with implementation, especially early on. But we’re reaching the point where more capable partners can handle it themselves. We’re building a post-sale certification for Alkira right now. In the meantime, we ride shotgun through the first couple of implementations – virtually in Slack or in person – until partners are fully up to speed. All partners have access to our Slack channel, along with our entire solutions architecture and SE staff. One partner working on a Fortune 10 engagement has a great habit of putting a subject header in Slack and starting a conversation. He’s been on services at this customer for three or four months – a significant engagement. He’s the one who originally described the network as a “spaghetti mess,” which I still chuckle about. I actually built the product catalog based on those Slack headers – pulled them together, socialized them with a group of partners, got input, and built from there. To directly answer your question: you’ve got to get through that first deal, and we’re going to ride shotgun with you through the first couple of implementations. The partner learns, gets comfortable, can monetize it, and can deliver independently from there. We have no illusions about going back to being a direct company after May 2022. It’s ride or die – 100% channel, and we enable our partners to solve their customers’ problems and support them while they do it. Because our partners have been our biggest growth engine. Robert Dutt: You’ve talked about a goal of doubling revenue through partners. What does the ecosystem look like when you get there? This sounds like it could primarily be a GSI or large integrator play, given the customer complexity you’re describing. Or do you genuinely see a path for mid-market MSPs and VARs to build a meaningful NIaaS practice? Doug Houghton: Another tough question. Yes, I do have GSIs as partners. We have a fairly robust and diverse partner ecosystem, and we see small shops rising up while larger shops are moving a bit more slowly, honestly. We’re still in that brand awareness honeymoon period – people are realizing our technology is compelling, getting themselves enabled. Some large partners we’ve recently brought on are still ramping. The biggest and most established organizations aren’t yet as capable as they will be, but we’re working diligently on that. Some of our smaller partners, on the other hand – I’m thinking of a friend of mine in Utah who is just an absolute champion. He knows our solution better than almost anyone. He closed six or seven deals in the past year, supported the implementations, did it largely on his own, because he’s curious, motivated, read all the documentation, and has been through full implementation cycles with us. He works at a ten-person shop. They just happen to have really good customers, and he knows the solution cold. So we’re at different stages with different partners in terms of maturity. The answer to your question is genuinely both. The small shop in Utah and the large national partner dedicating more resources as they see more customer problems Alkira can solve – we see wins across both. In the networking space, a six-month sales cycle is about as fast as it gets. I’m giving you a username and a password and you’re going in and connecting all of a customer’s assets together. The path exists for partners of every size. Robert Dutt: You’ve called out Canada specifically in your expansion plans, alongside the UK, EU, and the Middle East. What does that look like operationally – localized support, a Canadian channel team – or is it more of a global platform available to Canadian partners? Doug Houghton: Let’s talk personnel. We have a dedicated rep in eastern Canada, based out of New Hampshire, and a brilliant solutions architect just outside of Toronto. We’ve got a channel account manager – very capable teammate of mine, Savannah Stone – and the entire global solutions architecture staff accessible via Slack. We recently closed a very significant logo in Canada – a large insurance company – and our publicly referenceable Canadian customer is ContactPoint 360, a contact centre and BPO provider. They wanted to connect their Latin American operations back to Canada and couldn’t find an effective way to do it without us. We route them through the US West region, and the results have been excellent. We’ve also added CDW Canada as a partner, and I’ve got a value-added distributor that helps with field events. It’s not a massive footprint yet – it’s a bit of “they come first, then we build” – but there is a tremendous amount of opportunity in Canada and in Latin America that I’m genuinely excited about. Nobody’s told me no yet on spending budget, so here we go. A great story on the Canadian side: a gentleman named Chris Thelosinos, an architect and consultant who works with others in our space, is a member at a wine shop in Toronto. During the Toronto International Film Festival last year, we hosted a wine event right next to TIFF. I don’t drink alcohol, so it was entirely about the conversations for me – and I had the best time. We had significant customers come out, and the demand for simplicity, ease of implementation, and everything Alkira does well was just as strong in Canada as anywhere else. The market need is real. We talk about global backbone as a service all the time. Connecting China to San Francisco carries a distance and time tax, but it’s easy to configure. For organizations navigating geopolitical complexity around China access, or needing GPU connectivity in and out, we just abstract the Azure and AWS mainland China instances. They operate the same way as their Canadian or US equivalents. And you can consume it pay-as-you-go – stop using it, stop paying for it. That’s a compelling model for MSPs looking to grow into different regions. Robert Dutt: Last question then. For that Canadian MSP who’s listened to this and is thinking, “This sounds like a real opportunity” – what’s the one thing you’d want them to take away and act on? Doug Houghton: I’d ask them to go to partners@alkira.com and send us a note. And I will ply them with all sorts of content – videos, learnings, deal registration information, everything they need to get started in the space. Tongue in cheek, and also completely seriously: partners@alkira.com. If you’re looking to grow your business as a managed service provider – managed network, managed security, managed load balancing, managed DDI, managed connectivity – we’re a really great place to start. Because it’s never unpopular to walk into a customer and solve their problem quickly and say, “I can help you with X, Y, and Z, and I can do it in the next couple of hours – and that’s going to drive a total cost of ownership savings of 40 to 70%.” Nobody ever kicks you out of the office when you say something like that. Robert Dutt: Amazing. Doug, I appreciate you taking the time. Thank you very much. Doug Houghton: Robert, thank you for the engaging conversation. I hope your listeners get some good stuff out of it. Robert Dutt: There you have it – Doug Houghton from Alkira. I’d like to thank Doug for his time, and honestly for being one of the more entertaining guests I’ve had on in a while. “Networking is not sexy until it doesn’t work” is a line I’m going to be thinking about for a while. Thanks to you for listening as well. If this conversation sparked something – whether it’s curiosity about NIaaS, the AI infrastructure angle, or what roughly 20% total margin on a $500,000 average deal could do for your business – Doug made it easy for you to take the next step. Drop a note to partners@alkira.com. That’s the front door. And from what I heard today, they will absolutely get back to you. Here’s the thing that stuck with me most in this conversation: the argument that the AI moment isn’t just a software or services play. It’s going to force a reckoning with network infrastructure that a lot of organizations have been deferring for years. The partners who treat that reckoning as an opportunity rather than a fire drill are probably going to look very smart in about three years. If you’re finding the In The Channel podcast from ChannelBuzz.ca useful, the best thing you can do is follow or subscribe wherever you get your podcasts. We’re on Apple Podcasts, Spotify, YouTube, and most major directories. And if you’re enjoying the show, ratings and reviews are genuinely appreciated – they help other people in the Canadian channel find us. Until next time, I’m Robert Dutt for ChannelBuzz.ca, and I’ll see you in the channel.

Die GamerDaddies – der Podcast rund um das Thema Gaming auf Konsolen und dem PC. Was sie von den anderen Podcasts zum Thema Videospiele unterscheidet, ist, dass sie alles aus dem Blickwinkel von Vätern für Väter betrachten. Gerit und Buddha analysieren, ob Computerspiele familientauglich sind und sprechen darüber, wie man am besten Familie, Kinder, Gaming und andere Hobbies unter einen Hut bekommt. Diesmal geht es um das Thema: Wie stärke ich das Selbstbewusstsein bei meinen Kindern? Gezockt haben die beiden Daddies natürlich auch und zwar Vampire Crawlers auf dem PC. Spotify: https://spoti.fi/32so0js Apple: https://apple.co/2NPCEvP www.gamerdaddies.de HOLY Energy: https://de.holy.com/discount/GEZOCKT?ref=geritzockt CODE: Gezockt (10 Prozent Rabatt) Partner: www.perfekt-zocken.de Twitch: www.twitch.tv/GeritZockt Discord: https://discord.gg/YaSrPYjbUg

Most engineers approach open source the wrong way. They write code, open a PR, and wonder why it never gets merged. Bruno Schaatsbergen, Terraform core contributor and ex-HashiCorp engineer, breaks down the real craft behind contributions that actually land, and why AI is quietly breaking the ecosystem we all depend on.In this episode, we cover:Why pull requests get ignored (and the counterintuitive fix)How AI slop is killing open source from the insideUsing AI agents without losing your identity as an engineerWhy open source beats a tailored resume in today's marketHow consistent contributions can reshape your entire careerIf you've ever wanted to contribute to open source but didn't know where to start, this episode gives you a clear perspective from someone who's been on both sides.Connect with Bruno:https://www.linkedin.com/in/bschaatsbergenOUTILNE00:00:00 - Intro00:01:04 - How Open Source Shaped My Entire Career00:02:14 - Why I Take Pride in Every PR I Write00:03:16 - Open Source vs Personal Projects: The Real Difference00:04:18 - Why Your PRs Get Ignored (And How to Fix It)00:05:41 - Know Your Audience: The Counterintuitive PR Hack00:06:35 - Dealing With Imposter Syndrome as a Contributor00:07:10 - Read Code Like a Writer Reads Books00:09:31 - My First Contribution (And How It Changed My Career)00:10:51 - Should You Contribute to Open Source Early in Your Career?00:12:46 - The Dark Side: When Contributions Become Noise00:13:44 - Killed With Kindness: The AI Slop Problem00:16:17 - How Maintainers Are Fighting AI Slop00:18:02 - How I Actually Use AI Agents in My Workflow00:19:11 - Don't Outsource Your Thinking to AI00:20:11 - Who's Liable for AI-Generated Code?00:21:16 - Earned Rights: Why Trust Matters in Open Source00:22:52 - How to Approach People at Tech Conferences00:24:52 - Open Source Is Not a Democracy00:26:04 - Why Open Source Beats a Tailored Resume00:27:12 - Never Contribute With the Goal of Getting Hired00:28:38 - The Real Reason Consistency Pays Off00:29:30 - Admitting I'm a University Dropout00:30:42 - Why I Haven't Contributed in Weeks (And That's Okay)00:32:07 - The Trap of Chasing Contributor Rankings00:34:32 - Open Source Lets You Work With Anyone in the World00:35:52 - Final Advice: Don't Let AI Steal Your Identity

An airhacks.fm conversation with Thorsten Hoeger (@hoegertn) about: discussion about migrating a German bank to AWS in 2012, early EC2 instances and the launch of AWS VPC for private networking, clicking the AWS console before discovering CloudFormation, CloudFormation released in 2011 with JSON-only templates, Hazelcast cluster synchronization bugs on single-core EC2 instances, multicast limitations in VPC and the transit gateway workaround, CFEngine from 1993 as a predecessor to declarative infrastructure management, Puppet and Chef and Ansible as configuration management tools, CloudFormation's declarative state reconciliation predating kubernetes by three years, CloudFormation's managed state versus Terraform's local state storage, three-way diff comparing new template and old template and physical resource state, drift detection and its limitations with default values, writing 3000 lines of CloudFormation JSON in Eclipse IDE, building a Jenkins plugin for CloudFormation lifecycle management, GitOps with Git servers and Jenkins for CloudFormation deployments, separating infrastructure changes from business logic changes in early setups, treating everything as a change in modern CI/CD pipelines, the origin of CDK at Amazon as an internal tool written in Java then rewritten in typescript, CDK beta participation through the AWS Hero program, CDK constructs and L1 low-level constructs mapping directly to CloudFormation resources, CDK synth phase serializing Java objects to CloudFormation JSON, Stacks as atomic deployment units in CDK, the trade-offs of splitting stateful resources into separate stacks versus single-stack deployments, AWS CloudFormation export and reference coupling between stacks, using AWS Parameter Store for loose coupling between stacks, CDK application as the project root with application code in subfolders, Terraform benefits for multi-provider scenarios like GitHub repos and on-prem routers, regulated industries and compliance benefits of cloud infrastructure as code, change management as a byproduct of Git-based infrastructure pipelines, serverless architecture similarities to application server and WAR deployment models, CDK asset system for versioning and pushing artifacts, CDK custom resource types and self-mutating pipelines as future topics, The CDK Book co-authored by Thorsten Hoeger and colleagues, Taimos GmbH consulting for AWS infrastructure Thorsten Hoeger on twitter: @hoegertn

Cloud Posse holds LIVE "Office Hours" every Wednesday to answer questions on all things related to AWS, DevOps, Terraform, Kubernetes, CI/CD. Register at https://cloudposse.com/office-hoursSupport the show

Думаете, знаете полный lifecycle удаления пода в Kubernetes? Даже опытный инженер с CKA запнулся на этом вопросе. Мок-собеседование на Senior DevOps с live coding и тремя интервьюерами. ЧТО СПРАШИВАЛИ - Cloud: миграция AWS в Yandex Cloud, DynamoDB в YDB, Kafka HA в трех зонах - Terraform: структура репозитория, Terragrunt, state management, code review модулей - Kubernetes: pod lifecycle, graceful shutdown, kube-proxy, endpoint slices - Live coding: Helm troubleshooting сломанного StatefulSet upgrade - AI/LLM: токенизация, промпт-инженерия, MCP Server - "обычно говоришь LLM сделай красиво" - CI/CD: pipeline от merge request до prod, rolling update vs canary, GitOps и Argo CD - Скриптинг: code review скрипта удаления Docker-образов из registry КАНДИДАТ Владимир Ушков - инфраструктурный DevOps-инженер с опытом в AWS, Yandex Cloud, Terraform, Kubernetes, CI/CD. Интересный момент: кандидат честно признался, что цифра "улучшил на 23%" в CV была "органолептической" - и добавил: "в эпоху LLM резюме тоже надо писать для LLM". Фидбэк по интервью доступен на Patreon/Boosty. Хотите пройти mock interview на нашем канале? Пишите нам! ССЫЛКИ Поддержать наш подкаст:   - Patreon - https://www.patreon.com/c/devopskitchentalks   - Boosty - https://boosty.to/devopskitchentalks ПОДКАСТ YouTube - www.youtube.com/@DevOpsKitchenTalks Apple Podcasts - https://apple.co/41O6mqA Spotify - https://t.ly/Jg5_2 Yandex Music - https://music.yandex.ru/album/10151746 PodBean - https://devopskitchentalks.podbean.com НАВИГАЦИЯ 00:00 - Знакомство: три интервьюера и кандидат 03:24 - Начало интервью: "Почему хотите работать у нас?" 06:37 - Self-presentation: опыт в DevOps и инфраструктуре ЧАСТЬ 1: CLOUD И ИНФРАСТРУКТУРА (Саша) 10:46 - AWS и Yandex Cloud: зоны ответственности инфра-команды 16:38 - Миграция AWS в Yandex Cloud: DynamoDB, риски, планирование 21:00 - Kubernetes: managed K8s, node pools и capacity planning ЧАСТЬ 2: TERRAFORM И IAC (Саша) 24:09 - Terraform: структура репозитория, Terragrunt, state 29:40 - Terraform модули: code review и best practices 32:05 - Стабильность кода: version locking и required providers ЧАСТЬ 3: KUBERNETES DEEP DIVE (Виктор) 42:25 - Kubernetes: CRD, операторы и что нравится в K8s 44:20 - Pod lifecycle: kubectl delete и graceful shutdown 48:00 - Kube-proxy: iptables, endpoint slices, сервисы ЧАСТЬ 4: LIVE CODING (Виктор) 55:00 - Практика: Helm troubleshooting StatefulSet upgrade 01:09:00 - Helm upgrade: дебаг "not valid zip" и restart стратегии 01:22:00 - SRE-подход: "дропаем бэкап, делаем rollout" ЧАСТЬ 5: AI И LLM (Виктор) 01:24:53 - AI для DevOps: токенизация, контекстное окно, промпт-инженерия 01:28:00 - MCP Server и практическое применение LLM в работе ЧАСТЬ 6: CI/CD И GITOPS (Саша) 01:34:24 - DORA-метрики и как считать "улучшил на 23%" 01:37:00 - CI/CD pipeline: от merge request до production 01:45:00 - Branching стратегии: GitFlow vs GitLab Flow 01:48:00 - Deployment: rolling update vs canary, Helm vs Argo CD 01:49:45 - GitOps: source of truth и configuration drift 01:53:00 - Скриптинг: code review скрипта удаления Docker-образов 01:56:57 - Завершение и благодарности ПОДПИСЫВАЙТЕСЬ Telegram - https://t.me/DevOpsKitchenTalks Instagram - https://www.instagram.com/devopskitchentalks/ #MockInterview #DevOps #Kubernetes #Terraform #CICD #LiveCoding #DKT #DevOpsKitchenTalks #SeniorDevOps #GitOps

Cloud Posse holds LIVE "Office Hours" every Wednesday to answer questions on all things related to AWS, DevOps, Terraform, Kubernetes, CI/CD. Register at https://cloudposse.com/office-hours Support the show

In this episode ofThe New Stack Agents, Marcin Wyszynski, co-founder of Spacelift and OpenTofu, explains how AI is transforming infrastructure as code (IaC). Originally built for individual operators, tools like Terraform struggled to scale across teams, prompting Wyszynski to help launch OpenTofu after HashiCorp's 2023 license change. Now, the bigger shift is AI: engineers no longer write configuration languages like HCL manually, as AI tools generate it, dramatically lowering the barrier to entry. However, this creates a dangerous gap between generating infrastructure and truly understanding it—like using a phrasebook to ask questions in a foreign language but not understanding the response. In infrastructure, that lack of comprehension can lead to serious risks. To address this, Spacelift introduced Intent, which allows AI to directly interact with cloud systems in real time while enforcing deterministic guardrails through policy controls. The broader challenge remains balancing speed with control—enabling faster experimentation without sacrificing safety. Wyszynski argues that, like humans, AI can be trusted when constrained by strong guardrails. Learn more from The New Stack about the latest developments around how AI is transforming infrastructure as code (IaC). The Maturing State of Infrastructure as Code in 2025 Generative AI Tools for Infrastructure as Code Join our community of newsletter subscribers to stay on top of the news and at the top of your game. 

Cloud Posse holds LIVE "Office Hours" every Wednesday to answer questions on all things related to AWS, DevOps, Terraform, Kubernetes, CI/CD. Register at https://cloudposse.com/office-hours Support the show

Rosemary Wang and Michael Kosir (developer advocates at HashiCorp, an IBM Company) discuss how to use Terraform and Packer agent skills, explorer in Terraform Enterprise 1.2, and caching in Vault Secrets Operator 1.3.0. Podcast Notes - GO-2026-4337: https://pkg.go.dev/vuln/GO-2026-4337 - Vault Secrets Operator 1.3.0: https://github.com/hashicorp/vault-secrets-operator/releases/tag/v1.3.0 - Terraform Enterprise 1.2: https://www.hashicorp.com/en/blog/terraform-enterprise-12-upgrades-workflows-visibility-and-brownfield-migration - Agent Skills: https://www.hashicorp.com/en/blog/introducing-hashicorp-agent-skills - Understanding instructions, context, skills and MCP servers for code generation by Sam McGeown: https://www.definit.co.uk/2026/03/understanding-instructions-context-skills-and-mcp-servers-for-code-generation/

One of the early promises of public cloud was that, in theory, you could move workloads from Cloud Provider A to Cloud Provider B for any number of reasons: lower costs, new capabilities, better uptime, and so on. In practice, once a workload goes into a public cloud and you build out all the other... Read more »

One of the early promises of public cloud was that, in theory, you could move workloads from Cloud Provider A to Cloud Provider B for any number of reasons: lower costs, new capabilities, better uptime, and so on. In practice, once a workload goes into a public cloud and you build out all the other... Read more »

One of the early promises of public cloud was that, in theory, you could move workloads from Cloud Provider A to Cloud Provider B for any number of reasons: lower costs, new capabilities, better uptime, and so on. In practice, once a workload goes into a public cloud and you build out all the other... Read more »

Cloud Posse holds LIVE "Office Hours" every Wednesday to answer questions on all things related to AWS, DevOps, Terraform, Kubernetes, CI/CD. Register at https://cloudposse.com/office-hours Support the show

Running Oracle Database@AWS is most effective when you have full visibility and control over your environment.   In this episode, hosts Lois Houston and Nikita Abraham are joined by Rashmi Panda, who explains how to monitor performance, track key metrics, and catch issues before they become problems. Later, Samvit Mishra shares key best practices for securing, optimizing, and maintaining a resilient Oracle Database@AWS deployment.   Oracle Database@AWS Architect Professional: https://mylearn.oracle.com/ou/course/oracle-databaseaws-architect-professional/155574 Oracle University Learning Community: https://education.oracle.com/ou-community LinkedIn: https://www.linkedin.com/showcase/oracle-university/ X: https://x.com/Oracle_Edu   Special thanks to Arijit Ghosh, Anna Hulkower, Kris-Ann Nansen, Radhika Banka, and the OU Studio Team for helping us create this episode. ------------------------------------------------------ Episode Transcript: 00:00 Welcome to the Oracle University Podcast, the first stop on your cloud journey. During this series of informative podcasts, we'll bring you foundational training on the most popular Oracle technologies. Let's get started! 00:26 Nikita: Welcome to the Oracle University Podcast! I'm Nikita Abraham, Team Lead: Editorial Services with Oracle University, and with me is Lois Houston, Director of Communications and Adoption with Customer Success Services  Lois: Hello again! Last week's discussion was all about how Oracle Database@AWS stays secure and available. Today, we're joined by two experts from Oracle University. First, we'll hear from Rashmi Panda, Senior Principal Database Instructor, who will tell you how to monitor and log Oracle Database@AWS so your environment stays healthy and reliable. Nikita: And then we're bringing in Samvit Mishra, Senior Manager, CSS OU Cloud Delivery, who will break down the best practices that help you secure and strengthen your Oracle Database@AWS deployment. Let's start with you, Rashmi. Is there a service that allows you to monitor the different AWS resources in real time? Rashmi: Amazon CloudWatch is the cloud-native AWS monitoring service that can monitor the different AWS resources in real time. It allows you to collect the resource metrics and create customized dashboards, and even take action when certain criteria is met. Integration of Oracle Database@AWS with Amazon CloudWatch enables monitoring the metrics of the different database resources that are provisioned in Oracle Database@AWS. Amazon CloudWatch collects raw data and processes it to produce near real-time metrics data. Metrics collected for the resources are retained for 15 months. This facilitates analyzing the historical data to understand and compare the performance, trends, and utilization of the database service resources at different time intervals. You can set up alarms that continuously monitor the resource metrics for breach of user-defined thresholds and configure alert notification or take automated action in response to that metric threshold being reached. 02:19 Lois: What monitoring features stand out the most in Amazon CloudWatch? Rashmi: With Amazon CloudWatch, you can monitor Exadata VM Cluster, container database, and Autonomous database resources in Oracle Database@AWS. Oracle Database@AWS reports metrics data specific to the resource in AWS/ODB namespace of Amazon CloudWatch. Metrics can be collected only when the database resource is an available state in Oracle Database@AWS. Each of the resource types have their own metrics defined in AWS/ODB namespace, for which the metrics data get collected.  02:54 Nikita: Rashmi, can you take us through a few metrics? Rashmi: At Exadata database VM Cluster, there is CPU utilization, memory utilization, swap space storage file system utilization metric. Then there is load average on the server, what is the node status, and the number of allocated CPUs, et cetera. Then for container database, there is CPU utilization, storage utilization, block changes, parse count, execute count, user calls, which are important elements that can provide metrics data on database load. And for Autonomous Database metrics data include DB time, CPU utilization, logins, IOPS and IO throughput, RedoSize, parse, execute, transaction count, and few others. 03:32 Nikita: Once you've collected these metrics and analyzed database performance, what tools or services can you use to automate responses or handle specific events in your Oracle Database@AWS environment? Rashmi: Then there is Amazon EventBridge, which can monitor events from AWS services and respond automatically with certain actions that may be defined. You can monitor events from Oracle Database@AWS in EventBridge, which sends events data continuously to EventBridge at real time. Eventbridge forwards these events data to target AWS Lambda and Amazon Simple Notification Service to perform any actions on occurrence of certain events. Oracle Database@AWS events are structured messages that indicate changes in the life cycle of the database service resource. Eventbridge can filter events based on your defined rules, process them, and deliver to one or more targets. Event Bus is the router that receives the events, optionally transform them, and then delivers the events to the targets. Events from Oracle Database@AWS can be generated by two means: they can be generated from Oracle Database@AWS in AWS, and they can also be generated directly from OCI and received by EventBridge in AWS. You can monitor Exadata Database and Autonomous Database resource events. Ensure that the Exadata infrastructure status is an available state. You can configure how the events are handled for these resources. You can define rules in EventBridge to filter the events of interest and the target, who is going to receive and process those events. You can filter events based on a pattern depending on the event type, and apply this pattern using Amazon EventBridge put-rule API, with the default event bus to route only those matching events to targets. 05:13 Lois: And what about events that AWS itself generates? Rashmi: Events that are generated in AWS for the Oracle Database@AWS resources are delivered to the default event bus of your AWS account. These events that are generated in AWS for Oracle Database@AWS resources include lifecycle changes of the ODB network. The different network events are successful creation or failure of the creation of the ODB network, and successful deletion or failure in deletion of the ODB network. When you subscribe to Oracle Database@AWS, then an event bus with prefix aws.partner/odb is created in your AWS account. All events generated in OCI for the Oracle Database@AWS resources are then received in this event bus. When you are creating filter pattern using Amazon EventBridge put-rule API, you must set the event bus name to this event bus. Make sure you do not delete this event bus. Events generated in OCI and received into event bus are extensive. They include events of Oracle Exadata infrastructure, VM Cluster, container, and pluggable databases. 06:14 Lois: If you want to look back at what's happened in your environment, like who made the changes or accessed resources, what's the best AWS service for logging and auditing all that activity? Rashmi: Amazon CloudTrail is a logging service in AWS that records the different actions taken by a user or roles, or an AWS service. Oracle Database@AWS is integrated with Amazon Cloud Trail. This enables logging of all the different events on Oracle Database@AWS resources.  Amazon Cloud Trail captures all the API calls to Oracle Database@AWS as events. These API calls include calls from the Oracle Database@AWS console, and code calls to Oracle Database@AWS API operations. These log files are delivered to Amazon S3 bucket that you specify. These logs determine the identity of the caller who made the call request to Oracle Database@AWS, their IP from which the call originated, the time of the call, and some additional details.  CloudTrail event history stores immutable record of the past 90 days of management events in an AWS region. You can view, search, and download these records from CloudTrail Event History. You can access CloudTrail when you create an AWS account that automatically gives you the access to CloudTrail. Event history. If you would like to retain the logs for a longer period of time beyond 90 days, you can create CloudTrail trails or CloudTrail Lake event data store.  Management events in AWS provide information about management operations that are performed on the resources in your AWS account. Management operations are also called control plane operations. Thus, the control plane operations in Oracle Database@AWS are logged as management events in CloudTrail logs.  07:59 Are you a MyLearn subscriber? If so, you're automatically a member of the Oracle University Learning Community! Join millions of learners, attend exclusive live events, and connect directly with Oracle subject matter experts. Enjoy the latest news, join challenges, and share your ideas. Don't miss out! Become an active member today by visiting mylearn.oracle.com. 08:25 Nikita: Welcome back! Samvit, let's talk best practices. What should teams keep in mind when they're setting up and securing their Oracle Database@AWS environment?  Samvit: Use IAM roles and policies with least privilege to manage Oracle Database@AWS resources. This ensures only authorized users can provision or modify DB resources, reducing the risk of accidental or malicious changes.  Oracle Data Safe monitors database activity, user risk, and sensitive data, while AWS CloudTrail records all AWS API calls. Together, they give full visibility across the database and cloud layers. Autonomous Database supports Oracle Database Vault for enforcing separation of duties. Exadata Database Service can integrate with Audit Vault and Database Firewall to prevent privileged users from bypassing security controls. Enable multifactor authentication for AWS IAM users managing Oracle Database@AWS. This adds a strong second layer of protection against stolen credentials.  Always deploy your Oracle Database@AWS in private subnets without public IPs. Use AWS security groups and NACLs to strictly limit inbound and outbound traffic, allowing access only from trusted applications. Exadata Database Service supports integration with Oracle Vault for key lifecycle management. And in case of Autonomous Database, the transparent data encryption keys are automatically managed. But you can bring your own keys with OCI Vault. Key rotation ensures compliance and reduces risk of key compromise. Oracle Database@AWS enforces encrypted connections by default. Ensure clients connect with TLS 1.2 or 1.3 to protect data in transit from interception or tampering.  Use Oracle Data Safe's user assessment features to detect dormant users or excessive privileges. Disable unused accounts and rightsize permissions to reduce insider threats and security gap. Export database audit logs to Oracle Data Safe Audit Vault or AWS S3 with object lock for immutability. This prevents lock tampering and ensures audit evidence is preserved for compliance.  11:25 Lois: OK, that covers security. Do you have any tips for making sure your Oracle Database@AWS setup is reliable and resilient? Samvit: Start with clear recovery objectives. Define how much downtime and data loss each workload can tolerate. These targets drive your HADR architecture and backup strategy.  Implement business continuity measures to deliver maximum uptime for your databases. As a best practice, you must configure disaster recovery environment for your critical databases so that, in the event of any disaster affecting the primary database, applications can be immediately failed over to the DR environment, ensuring least application downtime and zero or minimal data loss. With Oracle Database@AWS, you can automate the creation and management of DR environment for your database services using different deployment capabilities. You can opt to configure either cross-availability zone DR in the same region or configure cross-region DR. Since cross-availability zone can only provide site failure protection, you must also configure a cross-region DR to protect against regional failure. A DR plan is only effective if tested. Regular failover and switchover drills validate that people, processes, and systems can recover as designed.  For Exadata Database, Autonomous Recovery Service provides automated backup validation, recovery guarantees, and protection against accidental data loss or corruption.  Oracle-managed backups are fully managed by OCI. When you create your Oracle Exadata Database, you can enable automatic backups by choosing Enable Automatic Backups in the OCI Console. When you do that, you can select Amazon S3 or OCI Object Storage or Autonomous Recovery Service as the backup destination. Don't just take backups. You also need to test them. Regularly restore backups into non-production environment to validate integrity and recovery time.  Plan beyond just the database. Map application and middleware dependencies to ensure end-to-end business resilience. A database failover is useless if dependent apps can't reconnect. 14:09 Nikita: Another area of interest is performance and cost. What practices help teams balance the two? Samvit: Autonomous Database automatically scales CPU and storage as workloads grow. This ensures performance during peaks while avoiding overprovisioning. So you should enable ADB auto-scaling.  Monitor CPU, memory, and IO metrics with AWS CloudWatch to rightsize your compute. Scale up or down based on actual utilization instead of static provisioning. Autonomous databases continuously evaluate and creates indexes automatically. This improves query performance without requiring manual tuning.  Use connection pooling in your applications to optimize database connections. Minimizing round-trip reduces latency and improves throughput. Apply AWS tags to database and related resources for cost allocation and chargeback. Tagging also helps with governance and cost visibility.  Choose between bring your own license and license-included models for Oracle Database@AWS. The right model depends on your existing license portfolio and cost strategy. Not all workloads need long backup retention. Adjust retention policies based on business needs to balance compliance with storage costs.  Exadata Database supports Oracle multitenant with pluggable databases. Consolidating databases reduces infrastructure footprint and licensing costs. Performance tuning isn't just technical. Align metrics with business KPIs. correlating DB performance to user experience and revenue impact helps prioritize optimizations.  16:20 Lois: Before we wrap up, Samvit, let's look at operational efficiency. What advice do you have for making day-to-day operations more efficient? Samvit: Use infrastructure as code tools like Terraform or AWS CloudFormation to automate provisioning. This ensures consistent, repeatable deployments with minimal manual errors.  For Autonomous Database, enable auto-start/stop to optimize costs by running databases only when needed. This is ideal for dev test or seasonal workloads. Exadata Database Service provides fleet maintenance to patch multiple systems consistently. This reduces downtime and simplifies lifecycle management.  Integrate AWS CloudWatch for performance monitoring and EventBridge for event-driven automation. This helps detect issues early and trigger automated workflows. Oracle Data Safe provides ready-to-use audit and compliance reports. Use these to streamline governance and reduce the effort of manual compliance tracking.  For Autonomous databases, Performance Hub simplifies monitoring while Exadata users benefit from AWR and ASH reports. Together, they give deep insights into performance trends. Automated tagging policies and change management workflows help maintain governance. They ensure resources are tracked properly and changes are auditable.  Monitor storage consumption and growth patterns using AWS CloudWatch and the ADB Console. Proactive tracking helps avoid capacity issues and unexpected costs. Send CloudTrail logs into EventBridge to trigger automated incident responses. This shortens response time and builds operational resilience.  18:36 Nikita: Samvit and Rashmi, thanks for spending time with us today. Your insights always help bring the bigger picture into focus. Lois: They definitely do. And if you'd like to go deeper into everything we covered, head over to mylearn.oracle.com and look up the Oracle Database@AWS Architect Professional course. Until next time, this is Lois Houston… Nikita: And Nikita Abraham, signing off! 19:03 That's all for this episode of the Oracle University Podcast. If you enjoyed listening, please click Subscribe to get all the latest episodes. We'd also love it if you would take a moment to rate and review us on your podcast app. See you again on the next episode of the Oracle University Podcast.

Send us Fan MailThe ground under cybersecurity careers is shifting, and the fastest movers are pairing CISSP with modern, high-leverage skills that command premium pay. We dig into a practical roadmap: first, how to prepare your SOC for agentic AI with four concrete moves—reskill analysts to supervise and validate models, establish new roles for AI governance and orchestration, redesign playbooks around automation and escalation, and enforce tight guardrails with approvals and audit trails. The goal is simple: turn AI from chaos into a disciplined force multiplier.From there, we unpack five high-income skills that dovetail with CISSP's leadership mindset. Modern GRC is no longer paperwork; it's resilience, litigation exposure, and executive storytelling—with VCISO opportunities that reward clear risk narratives and continuous evidence automation. Cloud security architecture centers on software-defined security, Terraform policies as code, zero trust in Kubernetes, and the legal boundaries of shared responsibility and data residency. AI ethics and governance emerges as the unofficial ninth domain, where shadow AI containment, dataset audits for PII, and prompt-injection testing meet global regulation and model risk policy.We also dive into advanced identity as the new perimeter—taming machine identities, secrets sprawl, and rolling out phishing-resistant FIDO2 to make zero trust real. Finally, we get tactical with software supply chain security: SBOMs, signed artifacts, dependency hygiene, and CI/CD security gates that protect velocity without breaking builds. Along the way, we share market pay signals, “decision architect” expectations for senior roles, and smart bridge certifications like CISM, AI governance credentials, and CISA that accelerate credibility.If you're ready to pivot from “security says no” to “here's how to do it safely,” this is your map. Subscribe, share with a teammate who needs a nudge, and leave a quick review to help more CISSPs find their niche and lead the way.Gain exclusive access to 360 FREE CISSP Practice Questions at FreeCISSPQuestions.com and have them delivered directly to your inbox!  Don't miss this valuable opportunity to strengthen your CISSP exam preparation and boost your chances of certification success. Join now and start your journey toward CISSP mastery today!

Проверяем знания кандидата на позицию Senior DevOps инженера в прямом эфире. В этом выпуске: архитектурные паттерны в AWS, вечный спор Terraform против CloudFormation, глубокое погружение в Kubernetes (Karpenter, скейлинг) и Live-траблшутинг сломанного Helm-чарта. О ЧЁМ ВЫПУСК: • Архитектура и облака: Как выбрать между EKS и ECS/Fargate и настроить безопасное хранение бэкапов в S3.  • IaC войны: Честное сравнение Terraform и CloudFormation — где заканчивается удобство и начинается боль.  • Kubernetes под капотом: Разбираем Control Plane, работу контроллеров и нюансы обновления on-prem кластеров.  • Live Debug: Реальная задача по починке упавшего пода (CrashLoopBackOff) — работа с пробами, портами и Helm.  • CI/CD стратегии: Строим идеальный пайплайн с GitHub Actions и ArgoCD. ГОСТЬ: Максим — DevOps-инженер (5 лет опыта DevOps, 10 лет SysAdmin). Стек: AWS, Terraform, Kubernetes, Ansible, Monitoring. ССЫЛКИ

Cloud Posse holds LIVE "Office Hours" every Wednesday to answer questions on all things related to AWS, DevOps, Terraform, Kubernetes, CI/CD. Register at https://cloudposse.com/office-hours Support the show

#340: The smartest ops people are often the most likely to resist new technology -- and they're not wrong. If you don't change anything, nothing breaks, and nobody blames you. That's a completely rational choice. It's also the one that guarantees you fall behind. Bare metal to VMs, VMs to cloud, cloud to Kubernetes -- every time, the teams that played it safe ended up scrambling to catch up two years later. The safe bet isn't safe. It just feels that way. It gets worse when you look at where the tools come from. Kubernetes? Built by developers. Terraform? Developers. Containers? Developers. The tools ops teams depend on were made by a different tribe. So the pushback isn't really about whether the tech is ready or whether the risk is too high. It's about identity. 'Not my people' is a harder objection to overcome than 'not ready yet,' because no amount of documentation or proof-of-concepts answers it. And about proof -- everyone wants it before they'll move. But the proof already exists. It's the tool someone on your team has been running in shadow IT for a year without any official support. If it survived that long on its own, that's stronger evidence than any pilot program. That's your roadmap. And the way in is small chunks, not grand plans. Move one service. Learn something. Adjust. Repeat. AI in ops follows the exact same pattern. A tool that gets you 50% of the way there for free means you can focus your expertise on the other 50%. That's a win. But the people waiting for AI to be perfect before they'll touch it? They're making the same mistake as the teams that waited for perfect proof before migrating to the cloud. Different decade, same trap.   YouTube channel: https://youtube.com/devopsparadox   Review the podcast on Apple Podcasts: https://www.devopsparadox.com/review-podcast/   Slack: https://www.devopsparadox.com/slack/   Connect with us at: https://www.devopsparadox.com/contact/

An airhacks.fm conversation with Thorsten Hoeger (@hoegertn) about: first computer experience with an IBM 8086 and learning programming by modifying the QBasic Gorilla game, early programming journey from QBasic to Visual Basic and the discovery of event-driven programming, building a password security script for autoexec.bat as a childhood project, transition from Visual Basic to Java around 2005 starting with Java 1.4.2, working at a small bank in Stuttgart building a core banking system, experience with Eclipse RCP rich client platform and the overhead of plugin architecture in business software, migration from Swing to Eclipse RCP frontend with JBoss application server backend, building a custom Spring-based microservice framework called Dwallin (Icelandic for dwarf) before Spring Boot existed, using Apache CXF for REST and RPC over messaging with ActiveMQ, comparison of Java development trajectories between annotation-based and XML-heavy approaches, discussion of the infamous Java and XML O'Reilly book that popularized XML configuration, xdoclet as a precursor to Java annotations, contrasting approaches of JBoss-based thin WAR deployments versus Spring-based embedded server microservices, university experience learning Ada programming language and its strict compiler as excellent for learning programming, PL/SQL's Ada-based origins, brief experience with OSGi and strong criticism of its complexity and poor developer experience, comparison of OSGi with Java Platform Module System (JPMS), founding Taimos consulting company 10 years ago originally building BlackBerry enterprise software, pivoting to AWS migration consulting for regulated industries including banks and insurance companies, strong preference for serverless architecture with lambda Step Functions API Gateway and DynamoDB, criticism of running kubernetes on AWS versus using native services like ECS Fargate, the distinction between running "in the cloud" versus "on the cloud", detailed discussion of why GraalVM native images are unnecessary on AWS Lambda due to compliance overhead and memory allocation model, quarkus and SnapStart as solutions for Lambda cold start problems, Java's cost efficiency on Lambda due to fast execution times, involvement with AWS CDK since 2018-2019 including building L2 constructs for EC2 and AppSync, shift from code contributions to community organizing and prioritization work with the CDK team, launching CDK Terrain as successor to CDK for Terraform, nuanced discussion of open source economics when the project primarily benefits a paid cloud provider, using GitHub as a personal index and dashboard for reusable project templates, consulting perspective on contributing to open source for code reuse across multiple clients, teaser for a future deep-dive episode on CDK internals and promoting Java usage with CDK Thorsten Hoeger on twitter: @hoegertn

Managing people is still the hardest problem in business. We've built rockets, nuclear reactors, and AI systems… but getting humans to coordinate? Still unsolved.In this episode, Casey Handmer talks about what leadership actually looks like when real stakes are involved when families depend on payroll, when bad decisions compound, and when “being liked” can quietly kill performance. He shares what he's learned building Terraform Industries, why most management books aren't that useful, and why firsthand accounts from people like General Groves hit differently.This conversation gets into hard feedback, demanding standards, and first principles thinking and why leaders need the social permission to push people without becoming jerks. If you care about building things that actually work, this one's for you.If you enjoyed this episode, subscribe to the show and share it with one person who's building something hard. That's how this grows.Terraform Industries is hiring across multiple technical roles. If you want to work on synthetic fuels, energy, and real world hardware problems, check out their website for open positions.Episode Highlights00:00 Why management is still humanity's unsolved problem08:53 Managing people is kind of the perennial problem15:06 Coaching high performers even when they're better than you18:13 “Being liked is optional. Succeeding is mandatory.”21:39 How to argue hard without attacking the person23:30 Why most teams don't practice real first principles thinking28:18 What makes outlier companies different34:09 The power of simply being present as a leader38:10 Terraform's next milestonesTakeawaysCoordination is the real bottleneck in big problems.Avoiding short term discomfort creates long term damage.First principles thinking requires structure, not slogans.Coaching isn't optional even for top talent.Leadership compounds over time. Small edges add up.If this conversation resonated with you, make sure you're subscribed and send it to someone who needs to hear it.Terraform Industries is actively hiring engineers and operators who want to work on synthetic fuel, methanol production, and large scale energy systems. Learn more at their official site.Casey HandmerWebsite: https://www.caseyhandmer.com/X / Twitter: linkedin.com/in/casey-handmer-60183262LinkedIn: linkedin.com/in/casey-handmer-60183262Terraform Industries: https://terraformindustries.com/Matt GjertsenWebsite: https://www.bettereverydaystudios.com/LinkedIn: https://www.linkedin.com/in/matthewgjertsen/YouTube: https://www.youtube.com/@BetterEveryDayStudios

Matt and Nic are back with another week of news and deals. In this episode:  Kalshi has detected and banned two accounts for insider trading Is Polymarket going to have to add KYC? Is there a tradeoff between informational efficiency and market fairness The OCC de facto bans stablecoin yield in its rulemaking around GENIUS Meta is considering partnering with a stablecoin issuer Stripe is bullish in their annual report ZachXBT determines that Axiom employees have been abusing the platform Terraform labs accuses Jane Street of insider trading WSJ reports that Binance overlooked Iranian sanctions violations Justin Drake unveils a post-quantum roadmap for Ethereum Matt Corallo says Nic is wrong about Bitcoin and quantum Content mentioned: Larry Cermak: How Crypto Actually Works: The Missing Manual  

Crypto News: Bitcoin and altcoins see upside in price as Terraform sues Jane Street and market manipulation gets exposed. Ethereum unveils new 'Strawmap' roadmap adding private ETH transactions, quantum-proof security, and massive L2 scaling. Tether invests $200 million in digital marketplace Whop to expand stablecoin payments.Brought to you by ✅ VeChain is a versatile enterprise-grade L1 smart contract platform https://www.vechain.org/ 

Cloud Posse holds LIVE "Office Hours" every Wednesday to answer questions on all things related to AWS, DevOps, Terraform, Kubernetes, CI/CD. Register at https://cloudposse.com/office-hours Support the show

Tune in live every weekday Monday through Friday from 9:00 AM Eastern to 10:15 AM.⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Buy our NFT⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Join our Discord⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Check out our Twitter⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Check out our YouTube⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠DISCLAIMER: The views shared on this show are the hosts' opinions only and should not be taken as financial advice. This content is for entertainment and informational purposes.

Investiere in neue Videospiele (mit Umsatzbeteiligung!):gamevestor.co

Cryptocurrencies Decline as AI Concerns Impact Riskier AssetsPharos Network Forms Alliance to Standardize On-Chain Real-World AssetsJane Street accused of insider trading linked to Terraform's collapseBitcoin losses mount as short-term holders liquidate positions.

Send a textWant a clear path from CISSP to top-tier pay without getting lost in buzzwords? We break down five high-income specialties that pair perfectly with CISSP leadership: modern GRC, cloud security as code, AI ethics and governance, advanced identity, and software supply chain security. Along the way, we unpack how AI reasoning tools like Claude Code Security are reshaping AppSec by cutting false positives and detecting logic flaws scanners miss, and we translate that shift into concrete workflows, better guardrails, and faster delivery.We start with the career pivot many leaders are making—moving from generalist security management to “decision architect.” That means pairing risk fluency with hands-on understanding of Terraform, Kubernetes, and CI/CD gates, then proving value through resilient architectures and evidence-driven dashboards for boards. You'll hear why GRC is exploding under new enforcement trends, how to automate continuous evidence to beat audit fatigue, and where vCISO opportunities command premium rates when strategy meets measurable outcomes.From there, we get practical. We walk through cloud guardrails that stop drift before it hits prod, share how to navigate shared responsibility with AWS and Azure, and outline identity-first zero trust that tames API key sprawl and enables passwordless access. On AI, we go deep on shadow AI containment, prompt-injection red teaming, model transparency, and data loss prevention tuned for embeddings—governance that accelerates, not blocks. Finally, we turn to software supply chain security: SBOM mandates, signed artifacts, dependency risk, and the DevSecOps policies that keep pipelines moving while raising assurance.If you're mapping your next move, we also compare salary bands across roles and highlight bridge certifications—CISM for program leadership, AI governance credentials for compliance depth, and CISA for audit rigor—to level up fast. Subscribe, share this with a teammate plotting their niche, and leave a quick review to tell us which specialty you're pursuing next.Gain exclusive access to 360 FREE CISSP Practice Questions at FreeCISSPQuestions.com and have them delivered directly to your inbox! Don't miss this valuable opportunity to strengthen your CISSP exam preparation and boost your chances of certification success. Join now and start your journey toward CISSP mastery today!

Cloud Posse holds LIVE "Office Hours" every Wednesday to answer questions on all things related to AWS, DevOps, Terraform, Kubernetes, CI/CD. Register at https://cloudposse.com/office-hours Support the show

Rosemary Wang and Michael Kosir (developer advocates at HashiCorp, an IBM Company) discuss what's new in HCP Terraform, Terraform, Vault, and the Vault ecosystem including remote state sharing across projects, ephemeral resources in the Vault provider, and a sneak peek at the deprecated attribute in Terraform. Podcast Notes - https://developer.hashicorp.com/terraform/cloud-docs/workspaces/settings#remote-state-sharing - https://github.com/hashicorp/terraform/blob/v1.15.0-alpha20260204/CHANGELOG.md - https://github.com/hashicorp/terraform-provider-vault/releases/tag/v5.7.0 - https://github.com/hashicorp/vault/releases/tag/v1.21.2 - https://github.com/hashicorp/vault-helm/releases/tag/v0.32.0 - https://github.com/hashicorp/vault-secrets-operator/releases/tag/v1.2.0

Очередное мок-собеседование на канале! Сегодня в гостях Саша (не СТО) — Senior DevOps Engineer, с которым мы проходим по всему циклу разработки: от проектирования CI/CD до траблшутинга в Kubernetes.  Много практики, лайв-кодинга и архитектурных вопросов. Слушаем, запоминаем вопросы, влетаем за разбором на Patreon/Бусти!

Mike McQuaid, Project Leader of Homebrew, joins Corey Quinn to share how a package manager conceived in a London pub became essential for 10 million Mac users. Homebrew lets you install software with one command instead of downloading files and clicking through installers, maintained by just 30 people who each get $300 a month.Mike shares the origin story from a drunken conversation about package management, explains how Homebrew Bundle can set up a new Mac with one command, and why Homebrew refuses to package software with fake open source licenses like Terraform's new versions.Show Highlights:(01:44) Why Homebrew Works on Linux(04:02) The Curl Bash Security Problem(05:02) Homebrew Was Conceived in a London Pub(06:42) Apps That Auto-Update Four Times a Day(08:43) Brew Bundle(14:00) Why Homebrew Auto-Updates Itself(18:18) Homebrew Maintainers Get $300 a Month(22:19) The Brew Doctor Command(29:10) Why Homebrew Doesn't Package Fake Open Source(32:05) Open Source Is Not a Career(35:27) When Someone Blamed Homebrew for Breaking Their Business(37:39) Auto-Update Options for Homebrew(39:40) Where to Find MikeLinks:Website: https://mikemcquaid.comHomebrew: https://brew.shGitHub: https://github.com/homebrewSponsored by: duckbillhq.com

Join us as Sam demonstrates how to teach AI to write Terraform configurations using Model Context Protocol (MCP) servers. Sam introduces the Terraform MCP server and walks through practical demos showing how AI can understand and safely interact with your infrastructure. You'll see live examples of AI planning, generating, and evolving Terraform configurations� from creating landing zones to setting up workspace variables automatically. Whether you're managing complex multi-cloud environments or just getting started with infrastructure as code, this episode demonstrates how MCP servers bridge the gap between AI capabilities and real-world Terraform workflows. Learn how to get started, which Claude models work best for different tasks, and best practices for integrating AI into your IaC pipelines. Timestamps 0:00 Welcome & Introduction 4:37 Sam McGeown's Background 6:02 Introduction to Terraform MCP Server 12:35 What is Model Context Protocol? 18:22 Setting Up the Terraform MCP Server 24:16 Demo: Claude Desktop Integration 30:41 Creating Infrastructure with AI Prompts 36:52 Reading & Analyzing Existing Terraform Code 42:18 Generating Landing Zone Configurations 47:35 Working with Terraform Workspaces 50:37 Creating Variables Automatically 52:14 Model Selection: Sonnet vs Opus 55:11 Live Demo: Workspace Variable Creation 58:33 Getting Started & Resources How to find Sam: https://www.linkedin.com/in/sammcgeown/ Links from the show: https://developer.hashicorp.com/terraform/mcp-server

This week on the podcast, Patrick and Tracy welcome Seamus Sullivan, author of Daedalus Is Dead. About Daedalus Is Dead: Daedalus of Crete is many things: The greatest architect in the world. The constructor of the Labyrinth that imprisoned the Minotaur. And the grieving father of Icarus, who plunged into the sea as father and son flew from the grasp of the tyrannical King Minos. Now, Daedalus seeks to reunite with Icarus in the Underworld, even as he revisits his own memories of Crete, hoping to understand what went so terribly wrong at the end of his son’s life. Daedalus will confront any terror to see Icarus again?whether it’s the cruel punishments of Tartarus, the cunning Queen Persephone, or the insatiable ghost of the Minotaur. But the truth, stalking Daedalus in the labyrinth of his own heart, might be too monstrous for him to bear. About Seamus Sullivan: Seamus Sullivan's fiction has appeared in Terraform and his book reviews have appeared in Strange Horizons. He lives in Jersey City with his family. Deadalus is Dead is his first novel. This week's picks: Seamus: “The Best God Damn Band in Wyoming” – No-No Boy Tracy: Wake Up Dead Man: A Knives Out Mystery (Netflix) Patrick: The Search for Planet X: Renegade Game Studio & Foxtrot Games (Board Game) Links: Tracy Townsend on BluSky Patrick Hester on Instagram The Functional Nerds Patreon Page © 2026 Patrick Hester The post Episode 692-With Seamus Sullivan appeared first on The Functional Nerds.

If you're clicking through Jamf Pro configs manually, you're about to learn why that's becoming a problem. Security teams are starting to ban console access. MSPs are wasting hours rebuilding the same configs for each client. And organizations scaling to hundreds of Macs are drowning in manual changes with zero audit trail. Ryan Legg, Jamf's Solutions Engineer for Infrastructure as Code, breaks down how Terraform lets you manage your entire Jamf environment through code instead of clicking. Whether you're managing 50 Macs or 5,000, here's why this matters NOW. CHAPTERS 4:45 What is Infrastructure as Code - Explained for Non-Coders 8:15 What is Terraform and Why It Exists 11:30 How Terraform Talks to the Jamf API (Without You Writing Scripts) 14:45 Jamf Terraform Provider - 2+ Years in Development 18:20 Version Control for Configs - Git, Testing, Rollback 21:40 Why This Matters - Audit Trails, No Manual Errors, Scalability 24:30 MSP Use Case - Deploy to Multiple Clients in Minutes 27:15 Enterprise Use Case - Manage Hundreds of Configs with Code 30:10 Small Team Use Case - Document Everything as You Build 34:00 Why Every Admin Should Learn This NOW - The Future is Code 37:13 Getting Started - Resources and Documentation 39:09 Wrap-Up - Where to Get Help What You: 4:45 "Treating your Jamf config like a software project" - what that actually means 18:20 Multiple admins can submit changes through pull requests - no more stepping on each other 24:30 MSPs: Stop rebuilding configs manually - use one Terraform module across all clients 30:10 - Small teams: Codify early so the next person doesn't start from zero 34:00 - "Organizations are requiring admins OUT of consoles" - security trend you need to know   RESOURCES: Jamf Concepts (Start Here): https://concepts.jamf.com Trusted by Jamf (Tutorials): https://trusted.jamf.com  Jamf Developer Portal: https://developer.jamf.com MacAdmins Slack: https://macadmins.org   WHO NEEDS TO WATCH: Mac Admins who manually configure Jamf Pro (you're wasting time) MSPs managing multiple Jamf instances (you're rebuilding the same thing repeatedly) IT teams scaling past 500+ devices (manual configs won't scale)   Jamf After Dark: A podcast about managing Apple devices, hosted by Kat Garbis and Josh Thornton. Guest: Ryan Legg, Solutions Engineer III at Jamf #JamfAfterDark #Terraform #JamfPro

Mars once had a magnetic field—can we bring it back? Learn what new seismic data reveals about the Red Planet's heart and whether nuclear power could restart its spin.Grab one of our new SFIA mugs and make your morning coffee a little more futuristic — available now on our Fourthwall store! https://isaac-arthur-shop.fourthwall.com/Visit our Website: http://www.isaacarthur.netJoin Nebula: https://go.nebula.tv/isaacarthurSupport us on Patreon: https://www.patreon.com/IsaacArthurSupport us on Subscribestar: https://www.subscribestar.com/isaac-arthurFacebook Group: https://www.facebook.com/groups/1583992725237264/Reddit: https://www.reddit.com/r/IsaacArthur/Twitter: https://twitter.com/Isaac_A_Arthur on Twitter and RT our future content.SFIA Discord Server: https://discord.gg/53GAShECredits:Could We Nuke Mars' Core to Restart Its SpinWritten, Produced & Narrated by: Isaac ArthurSelect imagery/video supplied by Getty Images Music by Chris ZabriskieSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.