Podcasts about developer experience

Nathen Harvey leads research at DORA, focused on how teams measure and improve software delivery. In today's episode of Engineering Enablement, Nathen sits down with host Laura Tacho to explore how AI is changing the way teams think about productivity, quality, and performance.Together, they examine findings from the 2025 DORA research on AI-assisted software development and DX's Q4 AI Impact report, comparing where the data aligns and where important gaps emerge. They discuss why relying on traditional delivery metrics can give leaders a false sense of confidence and why AI acts as an amplifier, accelerating healthy systems while intensifying existing friction and failure.The conversation focuses on how AI is reshaping engineering systems themselves. Rather than treating AI as a standalone tool, they explore how it changes workflows, feedback loops, team dynamics, and organizational decision-making, and why leaders need better system-level visibility to understand its real impact.Where to find Nathen Harvey:• LinkedIn: https://www.linkedin.com/in/nathenWhere to find Laura Tacho: • LinkedIn: https://www.linkedin.com/in/lauratacho/• X: https://x.com/rhein_wein• Website: https://lauratacho.com/• Laura's course (Measuring Engineering Performance and AI Impact): https://lauratacho.com/developer-productivity-metrics-courseIn this episode, we cover:(00:00) Intro(00:55) Why the four key DORA metrics aren't enough to measure AI impact(03:44) The shift from four to five DORA metrics and why leaders need more than dashboards(06:20) The one-sentence takeaway from the 2025 DORA report(07:38) How AI amplifies both strengths and bottlenecks inside engineering systems(08:58) What DX data reveals about how junior and senior engineers use AI differently(10:33) The DORA AI Capabilities Model and why AI success depends on how it's used(18:24) How a clear and communicated AI stance improves adoption and reduces friction(23:02) Why talking to your teams still matters Referenced:• DORA | State of AI-assisted Software Development 2025• Steve Fenton - Octonaut | LinkedIn• AI-assisted engineering: Q4 impact report

Aujourd'hui, les IA nous répondent. Demain, elles agiront pour nous.Charles Sonigo a compris que la vraie révolution de l'IA ne se joue pas dans les modèles de langage, mais dans leur capacité à interagir avec nos outils.En 2024, après avoir observé des agents IA galérer sur des actions pourtant simples, il se convainc qu'il faut repenser la façon dont l'IA communique avec les services existants.Début 2025, il cofonde Alpic, une startup entièrement dédiée au protocole MCP (Model Context Protocol), qui permet aux agents IA d'utiliser nativement les produits et services web.Dans cet épisode, Charles nous explique ce qu'est MCP, comment il se différencie d'une API traditionnelle, et pourquoi ce protocole pourrait bien devenir une des couches critiques de l'Internet de demain.On parle aussi de sécurité, d'expérience agentique, et des erreurs à éviter quand on conçoit un MCP serveur.————— PARTENARIAT —————Cet épisode est réalisé en partenariat avec NextLevel, qui accompagne les équipes tech dans l'adoption de l'IA et la création de Playbooks IA pour les équipes tech.————— CHARLES SONIGO —————Retrouvez Charles sur LinkedIn : https://www.linkedin.com/in/charles-sonigo-135a4340/Découvrez Alpic : https://alpic.ai————— CHAPITRAGE —————(01:12) Introduction à l'Opinionated(02:32) L'expertise de Charles(03:35) Qu'est-ce qu'un MCP ?(09:09) La différence avec une API traditionnelle(09:46) L'expérience agentique(17:57) Genèse du protocole MCP(19:14) Évolutions du MCP(21:46) Les enjeux de sécurité(34:58) Comment concevoir un MCP ?(49:54) Déploiement et Distribution(52:21) Intégration des MCP Serveurs(01:01:35) Mission d'Alpic et Hébergement(01:03:47) Cas d'Usage de MCP(01:09:27) Sécurité et Confiance dans les MCP(01:11:37) Erreurs et antipatterns des MCP(01:17:57) Ressources pour développeurs————— RESSOURCES —————Protocole MCP (Model Context Protocol)Services de LLM : Le Chat (Mistral), Claude (Anthropic), ChatGPT (OpenAI)Cursor et VS CodeMCP Server utilisés par Charles : GitHub, Sentry, LinearFrameworks d'authentification : Stitch, WorkOS, ScaleKitMCP Inspector (Anthropic)MCP JamCloudflareZillowStreamrootPassport.dev, le sponsor de ce hors-sérieAlpic : plateforme de hosting MCP cofondée par Charles————— 5 ÉTOILES —————Si cet épisode vous a plu, pensez à laisser une note et un commentaire - c'est la meilleure façon de faire découvrir le podcast à d'autres personnes !Envoyez-moi une capture de cet avis (LinkedIn ou par mail à dx@donatienleon.com) et je vous enverrai une petite surprise en remerciement.

Le MCP (Model Context Protocol) est en train de devenir l'une des couches les plus critiques de l'écosystème IA. En moins d'un an, ce protocole a connu une croissance fulgurante et transforme la manière dont les LLM interagissent avec leur environnement.Charles Sonigo décortique le MCP : ce que c'est vraiment, comment ça fonctionne techniquement, et pourquoi ça change tout pour passer d'une IA qui répond à une IA qui agit.Un extrait technique et accessible pour comprendre la révolution qui se construit sous nos yeux.————— CHARLES SONIGO —————Retrouvez Charles sur LinkedIn : https://www.linkedin.com/in/charles-sonigo/————— 5 ÉTOILES ————— Si cet épisode vous a plu, pensez à laisser une note et un commentaire - c'est la meilleure façon de faire découvrir le podcast à d'autres personnes !Envoyez-moi une capture de cet avis (LinkedIn ou par mail à dx@donatienleon.com) et je vous enverrai une petite surprise en remerciement.

Don't get stuck using AI to build faster horses. Instead, find the opportunities and rethink your software delivery processes! That, and only that, will help you increase Developer Experience and Efficiency!This episode is all about how to measure and improve DevEx in the age of Artificial Intelligence. And with Laura Tacho, CTO at DX, we think we found a perfect guest!Laura has been working in the dev tooling space for the past 15 years. In her current role at DX she is working on the evolution of DORA and SPACE into DX Core 4 and the DXI Measurement Framework.In our episode we learn about those frameworks but also how tech leaders need to rethink where and how to apply AI to improve overall efficiency, quality and effectiveness! The key takeaways from this conversation areDevEx is all about the identifying and reducing friction in the end-2-end development processTech Leaders need to become better in articulating technical change requirements to businessAs of today only 22% of code in git is really AI generated. Don't get fooled into believing AI is already betterBack to Basics makes companies successful with AI. That is: proper CI/CD, testing, documentation, observability!Here the links we discussedLaura's LinkedIn: https://www.linkedin.com/in/lauratacho/DX: https://getdx.com/Cloud Native Days Austria Talk: https://www.youtube.com/watch?v=kZ1F0-XS1l4Engineering Leadership Community: https://www.engineeringleaders.io/

This week, we discuss cloud earnings, Siri teaming up with Gemini, and AI bottlenecks. Plus, is cloning your dog weird? Watch the YouTube Live Recording of Episode (https://www.youtube.com/live/1FjknxuDc9Y?si=JH6rSQHErGMQQp9w) 545 (https://www.youtube.com/live/1FjknxuDc9Y?si=JH6rSQHErGMQQp9w) Runner-up Titles Stack the deck Pets and Chickens Blame it on Android They're fungible Are they going to have to introduce a new principle? Managers of rocks The world we live in Marketing wins We're the healthy skeptics Rundown Ex-NFL star QB Brady claims his dog is a clone (https://www.espn.com/nfl/story/_/id/46848973/tom-brady-says-dog-clone-family-previous-pet) Cloud Earnings AI & Cloud Trends for October 2025 (https://www.thecloudcast.net/2025/11/ai-cloud-trends-for-october-2025.html) Alphabet tops $100 billion quarterly revenue for first time, cloud grows 34% (https://www.cnbc.com/amp/2025/10/29/alphabet-google-q3-earnings.html) Google Cloud Q3 revenue surges 34% as backlog hits $155 billion (https://www.constellationr.com/blog-news/insights/google-cloud-q3-revenue-surges-34-backlog-hits-155-billion) Microsoft Azure sees 40% revenue growth in Q1 (https://www.constellationr.com/blog-news/insights/microsoft-azure-sees-40-revenue-growth-q1) Meta stock drops 10% as heightened AI spending overshadows strong results (https://www.cnbc.com/2025/10/30/meta-stock-earnings-ai-spend.html) Amazon revenues rise 13% on strength in cloud computing unit (https://giftarticle.ft.com/giftarticle/actions/redeem/b798e937-c39d-4e40-84a6-aa9210774e49) Clouded Judgement 10.31.25 - Cloud Giants Report Q3 (https://cloudedjudgement.substack.com/p/clouded-judgement-103125-cloud-giants?utm_source=post-email-title&publication_id=56878&post_id=177617088&utm_campaign=email-post-title&isFreemail=true&r=2l9&triedRedirect=true&utm_medium=email) 7m OpenAI work users (https://openai.com/index/1-million-businesses-putting-ai-to-work/) Amazon's culture went the wrong way (https://cote.io/2025/11/01/amazons-culture-went-the-wrong.html) Octoverse: A new developer joins GitHub every second as AI leads TypeScript to #1 (https://github.blog/news-insights/octoverse/octoverse-a-new-developer-joins-github-every-second-as-ai-leads-typescript-to-1/) What do we think of GitHub saying there are 180m developers in the world? (https://cote.io/2025/10/31/what-do-we-think-of.html) AWS and OpenAI announce multi-year strategic partnership (https://www.aboutamazon.com/news/aws/aws-open-ai-workloads-compute-infrastructure) Amazon stock jumps on $38 billion deal with OpenAI to use hundreds of thousands of Nvidia chips (https://finance.yahoo.com/news/amazon-stock-jumps-on-38-billion-deal-with-openai-to-use-hundreds-of-thousands-of-nvidia-chips-145357373.html) Relevant to your Interests Azure outage: Microsoft still working on fix, says recovery expected in several hours (https://www.cnbc.com/2025/10/29/microsoft-hit-with-azure-365-outage-ahead-of-quarterly-earnings.html) Microsoft takes $3.1 billion hit from OpenAI investment (https://www.cnbc.com/amp/2025/10/29/microsoft-open-ai-investment-earnings.html) Meta Stock Slides After Earnings. (https://www.investors.com/news/technology/meta-stock-q3-2025-earnings-ai-meta-news-zuckerberg/) AWS to Bare Metal Two Years Later: Answering Your Toughest Questions (https://oneuptime.com/blog/post/2025-10-29-aws-to-bare-metal-two-years-later/view) Meta denies torrenting porn to train AI, says downloads were for “personal use” (https://arstechnica.com/tech-policy/2025/10/meta-says-porn-downloads-on-its-ips-were-for-personal-use-not-ai-training/) Shocker! Reversal in AI ROI slide-wisdom: AI does works well (https://cote.io/2025/11/01/shocker-reversal-in-ai-roi.html) SaaS Monopoly | Khushi Lunkad (https://www.linkedin.com/posts/khushilunkad_saas-monopoly-activity-7390752595469914112-UWVw?utm_medium=ios_app&rcm=ACoAAADVjQ8Btsl3lKfl-gEYa6_6hmjCdJyRJyw&utm_source=social_share_send&utm_campaign=copy_link) The State of Developer Experience and Developer Productivity (https://lp.jetbrains.com/devex-productivity-report-full-2025-dataviz/?tab-OneOfTabWrapperBlock-1756889760421-44980=their-top-pain-points-) Why the “Free” Chef Version Could Be Your Most Expensive Mistake | Chef (https://www.chef.io/blog/chef-open-source-software-advice) Nonsense Disney yanks channels from YouTube TV after media giants fail to resolve carriage dispute | CNN Business (https://www.cnn.com/2025/10/30/media/disney-youtube-deal-biz-hnk) Traffic hits record high as commuters rewrite the rush hour - Texas A&M Transportation Institute (https://tti.tamu.edu/2025/10/traffic-hits-record-high-as-commuters-rewrite-the-rush-hour/) Denny's to be acquired and taken private in a deal valued at $620 million (https://apnews.com/article/dennys-investors-deal-private-company-f626f6b8c27f29f698a5c823ba855fc3) Conferences SREDay Amsterdam (https://sreday.com/2025-amsterdam-q4/), November 7th, Coté speaking. Wiz Wizdom Conferences (https://www.wiz.io/wizdom), November 17-19, London DevOpsDayLA at SCALE23x (https://www.socallinuxexpo.org/scale/23x), March 6th, Pasadena, CA Use code: DEVOP for 50% off. CFP open until Dec. 1st. SDT News & Community Join our Slack community (https://softwaredefinedtalk.slack.com/join/shared_invite/zt-1hn55iv5d-UTfN7mVX1D9D5ExRt3ZJYQ#/shared-invite/email) Email the show: questions@softwaredefinedtalk.com (mailto:questions@softwaredefinedtalk.com) Free stickers: Email your address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) Follow us on social media: Twitter (https://twitter.com/softwaredeftalk), Threads (https://www.threads.net/@softwaredefinedtalk), Mastodon (https://hachyderm.io/@softwaredefinedtalk), LinkedIn (https://www.linkedin.com/company/software-defined-talk/), BlueSky (https://bsky.app/profile/softwaredefinedtalk.com) Watch us on: Twitch (https://www.twitch.tv/sdtpodcast), YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured), Instagram (https://www.instagram.com/softwaredefinedtalk/), TikTok (https://www.tiktok.com/@softwaredefinedtalk) Book offer: Use code SDT for $20 off "Digital WTF" by Coté (https://leanpub.com/digitalwtf/c/sdt) Sponsor the show (https://www.softwaredefinedtalk.com/ads): ads@softwaredefinedtalk.com (mailto:ads@softwaredefinedtalk.com) Recommendations Brandon: Liquid Glass Transparency Toggle (https://www.macrumors.com/guide/ios-26-1-features/) Matt: The Other Two (https://www.imdb.com/title/tt8310612) Coté: NØLSON shirts (https://nolson.nl) Photo Credits Header (https://unsplash.com/photos/a-dog-sniffing-a-box-full-of-chickens-wyCOBbCztVw)

Our lived experiences often inform our work. This is true in the world of DevRel as well. Whether you have organized a church group, been in a band, or put together a big party - some of those experiences will leak over into how you see community and how you work in the Developer Relations world. Enjoy the podcast? Please take a few moments to leave us a review on iTunes (https://itunes.apple.com/us/podcast/community-pulse/id1218368182?mt=2) and follow us on Spotify (https://open.spotify.com/show/3I7g5W9fMSgpWu38zZMjet?si=eb528c7de12b4d7a&nd=1&dlsi=b0c85248dabc48ce), or leave a review on one of the other many podcasting sites that we're on! Your support means a lot to us and helps us continue to produce episodes every month. Like all things Community, this too takes a village.

Marie n'a jamais voulu choisir entre ambition professionnelle et soif de liberté. Alors elle a tout combiné.Diplômée de l'ESSEC, elle démarre dans le conseil en stratégie en Allemagne, convaincue que c'est sa voie. Mais rapidement, la frustration grandit : trop de politique, pas assez d'objectivité. C'est cette soif de logique qui la pousse vers la data en pleine pandémie.Pari risqué qui finit par payer. Elle décroche son premier poste de data analyst chez Papernest, devient manager en un an, puis rejoint Dougs comme première personne data avec pour mission de construire toute la stratégie from scratch. Et au moment où tout semble rouler, elle décide de tout arrêter pour partir un an faire le tour de l'Europe à vélo.——— MARIE LEFEVRE —————Retrouvez Marie sur LinkedIn : https://www.linkedin.com/in/marie-lefevre-b5770489/Articles Medium : https://medium.com/@marielefevre————— PARTIE 1/3 : PARCOURS —————(00:00) Intro + présentation(02:37) Parcours ESSEC et conseil en stratégie(06:23) Reconversion data pendant le COVID(10:41) Peurs et appréhensions dans la transition(15:22) Se sentir débordée par les demandes(19:30) C'est quoi concrètement le job de data analyst ?(26:31) Comment on fait de la data concrètement ?(35:18) Arrivée chez Dougs pour construire la data from scratch(42:05) Construire une stack data avec des compétences limitées(51:27) Comment prioriser sa liste de demandes(59:02) Définir ce que c'est la data chez Dougs(01:01:25) Recruter et faire grandir l'équipe(01:08:15) Pourquoi partir faire le tour de l'Europe à vélo(01:16:05) Ce qu'elle ramène du voyage - confiance et relativisation(01:21:00) Redéfinir son rôle au retour(01:24:22) Comment est arrivé le management(01:29:03) Erreurs en tant que manager débutant(01:35:14) Comment monter une équipe data(01:39:42) L'art de dire non dans la data(01:43:38) Évolution salariale dans la data————— PARTIE 2/3 : ROLL-BACK —————(01:51:06) Le projet complexe du calcul des primes commerciales(01:53:22) Pourquoi c'est un bourbier - exceptions et cas particuliers(01:56:04) Comment gérer cette complexité avec transparence(01:58:15) Autonomiser les équipes face aux données critiques————— PARTIE 3/3 : STAND-UP —————(01:59:19) Comment construire une architecture data fiable et robuste(02:00:53) Les outils - Airflow, Fivetran/Airbyte, BigQuery(02:03:12) DBT pour orchestrer les transformations SQL(02:08:20) Le star schema comme fondation(02:12:40) Tests et robustesse de la pipeline(02:20:39) Ressources recommandées(02:22:30) Le conseil ultime de Marie————— RESSOURCES —————Podcast Data Gen (Robin Conquet)Newsletter Data Engineering (Christophe Blefari - blef.fr)Coursera pour la formation SQL et PythonOutils : DBT, Airflow, Fivetran, Airbyte, BigQuery, Metabase, Looker Studio————— 5 ÉTOILES —————Si cet épisode vous a plu, pensez à laisser une note et un commentaire - c'est la meilleure façon de faire découvrir le podcast à d'autres personnes !Envoyez-moi une capture de cet avis (LinkedIn ou par mail à dx@donatienleon.com) et je vous enverrai une petite surprise en remerciement.Hébergé par Ausha. Visitez ausha.co/politique-de-confidentialite pour plus d'informations.

Discover how Amazon measures and improves developer experience at enterprise scale in this interview with Jim Haughwout, VP of Software Builder Experience at Amazon. Drawing from Amazon's retail business expertise, Jim reveals how the "cost to serve" metric transforms developer productivity measurement by focusing on system-level efficiency rather than individual performance. Learn how Amazon balances developer autonomy with standardization, implements tension metrics to prevent gaming, and leverages AI to re-imagine software development workflows. This essential discussion provides practical frameworks for quantifying developer experience improvements and connecting them directly to business value, from deployment automation to AI-assisted development at scale.

Che cosa rende davvero produttivo un team di sviluppo? Non solo skill tecniche o organigrammi: è la Developer Experience (DX), l'insieme di strumenti, processi e cultura che determina come gli sviluppatori pensano, creano e rilasciano valore. In questo video ti mostro perché la DX è la leva più sottovalutata per performance, benessere e retention, e come l'AI sta ridisegnando l'equilibrio tra velocità e qualità. Parliamo di:- I 4 pilastri della DX,- Come misurarla senza fuffa,- Quick wins tecnici e culturali che puoi implementare subito,- Il ruolo del CTO,- 3 casi studio (Spotify/Backstage, GitHub/Copilot, PMI italiana con +30% produttività). Se guidi team tech, qui trovi un framework pratico per ridurre attriti, aumentare focus e trasformare la DX in vantaggio competitivo.Vuoi farmi una domanda su questo o altri temi? Inviala qui e ti darò risposta nel prossimo video della rubrica #AskAlex: https://alexpagnoni.com/askalex/

In this episode of Engineering Enablement, host Laura Tacho talks with Fabien Deshayes, who leads multiple platform engineering teams at Monzo Bank. Fabien explains how Monzo is adopting AI responsibly within a highly regulated industry, balancing innovation with structure, control, and data-driven decision-making.They discuss how Monzo runs structured AI trials, measures adoption and satisfaction, and uses metrics to guide investment and training. Fabien shares why the company moved from broad rollouts to small, focused cohorts, how they are addressing existing PR review bottlenecks that AI has intensified, and what they have learned from empowering product managers and designers to use AI tools directly.He also offers insights into budgeting and experimentation, the results Monzo is seeing from AI-assisted engineering, and his outlook on what comes next, from agent orchestration to more seamless collaboration across roles.Where to find Fabien Deshayes: • LinkedIn: https://www.linkedin.com/in/fabiendeshayesWhere to find Laura Tacho: • LinkedIn: https://www.linkedin.com/in/lauratacho/• X: https://x.com/rhein_wein• Website: https://lauratacho.com/• Laura's course (Measuring Engineering Performance and AI Impact): https://lauratacho.com/developer-productivity-metrics-courseIn this episode, we cover:(00:00) Intro  (01:01) An overview of Monzo bank and Fabien's role  (02:05) Monzo's careful, structured approach to AI experimentation  (05:30) How Monzo's AI journey began  (06:26) Why Monzo chose a structured approach to experimentation and what criteria they used  (09:21) How Monzo selected AI tools for experimentation  (11:51) Why individual tool stipends don't work for large, regulated organizations  (15:32) How Monzo measures the impact of AI tools and uses the data  (18:10) Why Monzo limits AI tool trials to small, focused cohorts  (20:54) The phases of Monzo's AI rollout and how learnings are shared across the organization  (22:43) What Monzo's data reveals about AI usage and spending  (24:30) How Monzo balances AI budgeting with innovation  (26:45) Results from DX's spending poll and general advice on AI budgeting  (28:03) What Monzo's data shows about AI's impact on engineering performance  (29:50) The growing bottleneck in PR reviews and how Monzo is solving it with tenancies  (33:54) How product managers and designers are using AI at Monzo  (36:36) Fabien's advice for moving the needle with AI adoption  (38:42) The biggest changes coming next in AI engineering Referenced:Monzo The Go Programming LanguageSwift.orgKotlinGitHub Copilot in VS Code CursorWindsurfClaude CodePlanning your 2026 AI tooling budget: guidance for engineering leaders

Construire une architecture data from scratch, c'est un projet intimidant. Quels outils choisir ? Comment s'assurer que tout tient la route dans le temps ?Marie Lefevre, Lead Data Analyst chez Dougs, partage la stack data qu'elle a mise en place et qui fonctionne. Airflow, Fivetran, BigQuery, DBT, Metabase...Elle détaille chaque brique, son rôle, et pourquoi ces choix ont du sens pour une équipe de 5 personnes.Mais au-delà des outils, Marie insiste sur un point crucial : la robustesse ne vient pas que de la tech. Elle vient aussi des règles qu'on se fixe, de la discipline qu'on s'impose, et des tests qu'on met en place pour détecter les anomalies avant qu'elles ne cassent tout.————— MARIE LEFEVRE —————Retrouvez Marie sur LinkedIn : https://www.linkedin.com/in/marie-lefevre-b5770489/————— 5 ÉTOILES ————— Si cet épisode vous a plu, pensez à laisser une note et un commentaire - c'est la meilleure façon de faire découvrir le podcast à d'autres personnes !Envoyez-moi une capture de cet avis (LinkedIn ou par mail à dx@donatienleon.com) et je vous enverrai une petite surprise en remerciement.

Les dark patterns sont des techniques de design qui manipulent les utilisateurs de manière subtile pour les inciter à effectuer des achats ou des actions sans qu'ils en aient conscience.Par exemple, les réseaux sociaux sont criblés de dark patterns. Avec des mécanismes tels que le scroll infini ou le système de récompense basé sur les likes, tout est fait pour maintenir l'attention des utilisateurs et encourager une consommation excessive.On tente de définir la frontière entre un design qui optimise l'expérience utilisateur et un design qui devient manipulateur. Et bien sûr, on souligne l'importance d'une approche éthique du design.Dans cet extrait, on évoque les points suivants :➡️ Dark patterns ou comment pousser l'utilisateur à l'achat➡️ Frontière entre design efficace et manipulation➡️ Comment créer et promouvoir un design plus éthique➡️ Les dark patterns utilisés par les réseaux sociauxRetrouvez Paul :Sur LinkedIn : https://www.linkedin.com/in/paul-terrasson-duvernon/Sur Substack : https://thethinkinggallery.substack.com/Si cet épisode vous a plu, pensez à laisser une note et un commentaire - c'est la meilleure façon de faire découvrir le podcast à d'autres personnes !Envoyez-moi une capture de cet avis (LinkedIn ou par mail à dx@donatienleon.com) et je vous enverrai une petite surprise en remerciement.

In this episode, Darko welcomes Brian Douglas, Head of Developer Experience at Continue and longtime open source advocate. They talk about the rise of the AI engineer, how AI agents are reshaping developer workflows, and what's next for open source infrastructure. Enjoy the episode!Read the blog post: https://semaphore.io/blog/brian-douglasLike this episode? Be sure to leave a ⭐️⭐️⭐️⭐️⭐️ review on the podcast player of your choice and share it with your friends.

In this episode of Engineering Enablement, Laura Tacho and Abi Noda discuss how engineering leaders can plan their 2026 AI budgets effectively amid rapid change and rising costs. Drawing on data from DX's recent poll and industry benchmarks, they explore how much organizations should expect to spend per developer, how to allocate budgets across AI tools, and how to balance innovation with cost control.Laura and Abi also share practical insights on building a multi-vendor strategy, evaluating ROI through the right metrics, and ensuring continuous measurement before and after adoption. They discuss how to communicate AI's value to executives, avoid the trap of cost-cutting narratives, and invest in enablement and training to make adoption stick.Where to find Abi Noda:• LinkedIn: https://www.linkedin.com/in/abinoda  • Substack: ​​https://substack.com/@abinoda  Where to find Laura Tacho: • LinkedIn: https://www.linkedin.com/in/lauratacho/• X: https://x.com/rhein_wein• Website: https://lauratacho.com/• Laura's course (Measuring Engineering Performance and AI Impact): https://lauratacho.com/developer-productivity-metrics-courseIn this episode, we cover:(00:00) Intro: Setting the stage for AI budgeting in 2026(01:45) Results from DX's AI spending poll and early trends(03:30) How companies are currently spending and what to watch in 2026(04:52) Why clear definitions for AI tools matter and how Laura and Abi think about them(07:12) The entry point for 2026 AI tooling budgets and emerging spending patterns(10:14) Why 2026 is the year to prove ROI on AI investments(11:10) How organizations should approach AI budgeting and allocation(15:08) Best practices for managing AI vendors and enterprise licensing(17:02) How to define and choose metrics before and after adopting AI tools(19:30) How to identify bottlenecks and AI use cases with the highest ROI(21:58) Key considerations for AI budgeting (25:10) Why AI investments are about competitiveness, not cost-cutting(27:19) How to use the right language to build trust and executive buy-in(28:18) Why training and enablement are essential parts of AI investment(31:40) How AI add-ons may increase your tool costs(32:47) Why custom and fine-tuned models aren't relevant for most companies today(34:00) The tradeoffs between stipend models and enterprise AI licensesReferenced:DX Core 4 Productivity FrameworkMeasuring AI code assistants and agents2025 State of AI Report: The Builder's PlaybookGitHub Copilot · Your AI pair programmerCursorGleanClaude CodeChatGPTWindsurfTrack Claude Code adoption, impact, and ROI, directly in DXMeasuring AI code assistants and agents with the AI Measurement FrameworkDriving enterprise-wide AI tool adoptionSentryPoolside

Rémi a fait un parcours atypique : des neurosciences à Paris 6 au développement web, puis de développeur à engineering manager chez Wakeo. Pendant 7 ans dans la même boîte, il a tout vu : la croissance d'une startup, le doublement d'une équipe tech, la mise en place de process, les recrutements, la dette technique qui s'accumule... et ces moments de doute qui accompagnent chaque transition.Aujourd'hui, après 3 ans en tant qu'EM, Rémi se pose LA question : est-ce que le management, c'est vraiment fait pour lui ? Entre l'appel du code qu'il n'a jamais quitté et cette dimension humaine qu'il a appris à maîtriser, il cherche son équilibre.Dans cet échange, on parle de syndrome de l'imposteur, de culture d'entreprise, de shift produit vs tech, de recrutement, de feedback... et de ce moment où on réalise qu'on a peut-être besoin de remettre les mains dans le cambouis.————— RÉMI LEBIGRE —————Retrouvez Rémi sur LinkedIn : https://www.linkedin.com/in/remi-lebigre-6a102a53/————— PARTIE 1/3 : PARCOURS —————(01:04) Introduction à un parcours atypique(09:04) Découverte de la reconversion vers le développement(16:33) Transition progressive vers le management(42:30) Évolution vers le rôle d'Engineering Manager(45:16) Le quotidien d'un Engineering Manager(48:13) Gestion de l'agenda et priorisation(49:35) Développement et accompagnement de l'équipe(52:16) Suivi des projets et mesure de l'impact(56:30) Prise de décision et légitimité(1:00:26) Recrutement et culture d'entreprise chez Wakeo(1:05:07) Processus de recrutement détaillé(1:09:11) Structuration de l'équipe et chapters(1:10:02) Partage de connaissances : press days et R&D(1:16:18) Team Health : évaluation et amélioration continue(1:24:39) Syndrome de l'imposteur en tant que manager(1:31:56) Évolution salariale et reconnaissance(1:34:47) Réflexions sur la carrière et remise en question(1:38:17) Le podcast comme source d'inspiration(1:39:43) L'importance des entretiens et de la confrontation au marché(1:45:07) Valeurs et choix professionnels————— PARTIE 2/3 : ROLL-BACK —————(1:53:20) Le rollback : dette technique et stop-the-line produit(1:59:35) Culture et processus de management(2:10:59) Le rôle humain du manager————— PARTIE 3/3 : STAND-UP —————(2:16:19) Apprentissage et développement personnel(2:18:31) Ressources incontournables pour managers et devs(2:20:47) Passion et épanouissement dans la tech————— RESSOURCES —————Stay Sassy (SaaS) : ressources management pour heads of et EMsMartin Fowler : blog de référence sur l'architecture logicielleJosh W. Comeau : tutoriels interactifs React et CSSCharity Majors : article "The Engineer/Manager Pendulum"Communauté EM France————— 5 ÉTOILES —————Si cet épisode vous a plu, pensez à laisser une note et un commentaire - c'est la meilleure façon de faire découvrir le podcast à d'autres personnes !Envoyez-moi une capture de cet avis (LinkedIn ou par mail à dx@donatienleon.com) et je vous enverrai une petite surprise en remerciement.

Strategic Technology Consultation Services This episode of The Modern .NET Show is supported, in part, by RJJ Software's Strategic Technology Consultation Services. If you're an SME (Small to Medium Enterprise) leader wondering why your technology investments aren't delivering, or you're facing critical decisions about AI, modernization, or team productivity, let's talk. Show Notes "Simple is always the better choice, but easy is not always the best. So sometimes you'll go to graph, it's a little bit harder for us to write the code for around it, but the bandwidth consumption is considerably smaller. the compute consumption and the ability for it to run on a mobile device is considerably easier."— Jerry Nixon Hey everyone, and welcome back to The Modern .NET Show; the premier .NET podcast, focusing entirely on the knowledge, tools, and frameworks that all .NET developers should have in their toolbox. I'm your host Jamie Taylor, bringing you conversations with the brightest minds in the .NET ecosystem. Today, we're joined by Jerry Nixon. Jerry is a Principal Product Manager at Microsoft, focussing on the tooling and Developer Experience around Azure SQL Server. Jerry shares his advice for architecting web-based APIs, RESTful design, and using what fits within your team, and of course we talk about Data API Builder. "When you think about what an architect really is and their responsibility, the decisions, architectural decisions are the decisions that are the most expensive to change. That's kind of like who should be making this decision? Well, how expensive is it to change? It's very expensive."— Jerry Nixon We also talk about the importance of interpersonal skills in modern software engineering (whether you're working in open source or not), psychological safety, and the importance of self-reflection in our day-to-day work. Before we jump in, a quick reminder: if The Modern .NET Show has become part of your learning journey, please consider supporting us through Patreon or Buy Me A Coffee. Every contribution helps us continue bringing you these in-depth conversations with industry experts. You'll find all the links in the show notes. Anyway, without further ado, let's sit back, open up a terminal, type in `dotnet new podcast` and we'll dive into the core of Modern .NET. Full Show Notes The full show notes, including links to some of the things we discussed and a full transcription of this episode, can be found at: https://dotnetcore.show/season-8/designing-apis-like-a-pro-lessons-from-jerry-nixon-on-data-api-builder-and-beyond/ Useful Links: SQLBits The original definition of REST Data API Builder documentation Data API Builder on GitHub on MS Learn samples docker Registry SQL Dev Path FusionCache Jerry on X (formerly known as Twitter) Podcast editing services provided by Matthew Bliss Music created by Mono Memory Music, licensed to RJJ Software for use in The Modern .NET Show Supporting the show: Leave a rating or review Buy the show a coffee Become a patron Getting in Touch: Via the contact page Joining the Discord Remember to rate and review the show on Apple Podcasts, Podchaser, or wherever you find your podcasts, this will help the show's audience grow. Or you can just share the show with a friend. And don't forget to reach out via our Contact page. We're very interested in your opinion of the show, so please get in touch. You can support the show by making a monthly donation on the show's Patreon page at: https://www.patreon.com/TheDotNetCorePodcast. Music created by Mono Memory Music, licensed to RJJ Software for use in The Modern .NET Show. Editing and post-production services for this episode were provided by MB Podcast Services.

Rémi Lebigre a aidé à doubler la taille de l'équipe tech chez Wakeo, passant de 35 à 70 personnes. Mais sa méthode de recrutement est loin des standards : il passe 40 minutes à expliquer le poste au candidat, là où d'autres bâclent ça en 15 minutes pour maximiser le temps d'évaluation.Résultat ? Des candidats qui arrivent avec une vision claire, qui se projettent mieux, et qui ne découvrent aucune mauvaise surprise une fois en poste. Dans cet extrait, Rémi partage sa vision du recrutement, de la structuration d'équipes qui scalent, et des rituels qui maintiennent la cohésion quand tout grandit trop vite.——— RESSOURCES MENTIONNÉES ———Modèle Spotify (squads et chapters)Welcome to the JungleTeam Health (méthodologie de santé d'équipe)——— RÉMI LEBIGRE ———Retrouvez Rémi sur LinkedIn : https://www.linkedin.com/in/remi-lebigre-6a102a53/Si cet épisode vous a plu, pensez à laisser une note et un commentaire - c'est la meilleure façon de faire découvrir le podcast à d'autres personnes !Envoyez-moi une capture de cet avis (LinkedIn ou par mail à dx@donatienleon.com) et je vous enverrai une petite surprise en remerciement.

Hey everyone, Alex here

Everyone's talking about the AI datacenter boom right now. Billion dollar deals here, hundred billion dollar deals there. Well, why do data centers matter? It turns out, AI inference (actually calling the AI and running it) is the hidden bottleneck slowing down every AI application you use (and new stuff yet to be released). In this episode, Kwasi Ankomah from SambaNova Systems explains why running AI models efficiently matters more than you think, how their revolutionary chip architecture delivers 700+ tokens per second, and why AI agents are about to make this problem 10x worse.

Building Platform Products That Scale — Without Drowning in Stakeholders Platform products are some of the most complex beasts in product management. They have to serve multiple teams, stay flexible, and scale across the org—all while keeping technical and business needs in sync. In this episode, Rina Alexin chats with Aindra Misra, Director of Product Management for AI, Data, and Developer Experience at BILL (and former Twitter PM), about how to bring structure to platform chaos, build for scale, and win over even the loudest stakeholders.Key Topics Discussed in This EpisodeWhat Makes a Great Platform PMWhy platform product management is the sweet spot for technically curious PMs—and how mindset matters more than your coding background. The Art (and Science) of PrioritizationAindra's framework for balancing competing use cases, weighing business impact, and keeping the long-term platform vision intact. Stakeholder Alignment Without the DramaHow to turn “fight for priority” meetings into data-driven discussions that build stronger teams and better platforms. Why Listen to This Episode?What will you get out of this discussion? In this thought-provoking conversation, you'll gain: A framework for prioritizing platform features by impact, effort, and strategic value Real talk on managing competing stakeholders (and surviving to tell the tale) Insight into “horizontal thinking” and why it's key to scalable platforms Lessons from Twitter and BILL on how to balance speed, flexibility, and tech debt If you've ever tried to scale a platform product (or want to move into this space) this is your playbook. Related ResourcesCheck out these additional tools and resources to add to your PM belt:Productside Resource Library More Productside Stories Podcast Episodes Explore Productside Courses 

We're reflecting on how the show has evolved, from adding Pulse and tightening our structure to getting comfortable recording without guests. We also look back at the biggest shifts in DevRel over the past decade (no, you can't say AI), share thoughts on where the industry is headed, and dig into highlights from the Decade of DevRel report. Enjoy the podcast? Please take a few moments to leave us a review on iTunes (https://itunes.apple.com/us/podcast/community-pulse/id1218368182?mt=2) and follow us on Spotify (https://open.spotify.com/show/3I7g5W9fMSgpWu38zZMjet?si=eb528c7de12b4d7a&nd=1&dlsi=b0c85248dabc48ce), or leave a review on one of the other many podcasting sites that we're on! Your support means a lot to us and helps us continue to produce episodes every month. Like all things Community, this too takes a village.

“Engineering leaders are stuck between the expectations put out by sensational headlines and the reality of what they're seeing in their organization. There's a big disappointment gap.”Is your AI investment paying off? Many leaders struggle to see real ROI beyond the hype.In this episode, Laura Tacho, CTO of DX, shares DX's new research on measuring AI adoption success across 38,000+ engineers. Our conversation reveals why acceptance rates are misleading metrics and introduces DX's new AI Measurement Framework™ with its three critical dimensions: utilization, impact, and cost. Learn why treating AI as an organizational problem closes the “disappointment gap” between hype and reality.Note: This episode was recorded in July 2025. The AI adoption rate mentioned has since risen to nearly 80%.In this episode, you will learn about:The “Disappointment Gap” between AI hype and realityWhy the popular “acceptance rate” metric is misleadingThe DX AI Measurement Framework™ and its three dimensionsThe top time-saving AI use case (it's not code generation!)How AI impacts long-term software quality and maintainabilityWhy organizational readiness matters for successful AI adoptionThe bigger bottlenecks beyond coding that AI has not yet solvedTreating AI agents as team extensions, not digital employeesTimestamps:(00:00:00) Trailer & Intro(00:02:32) Latest DX Research on AI Adoption(00:03:54) AI Role on Developer Experience(00:05:43) The Current AI Adoption Rate in the Industry(00:09:27) The Leader's Challenges Against Al Hype(00:13:22) Measuring AI Adoption ROI Using Acceptance Rate(00:17:39) The DX AI Measurement Framework™(00:23:05) AI Measurement Framework: Utility Dimension(00:27:51) DX AI Code Metrics(00:30:31) AI Measurement Framework: Impact Dimension(00:32:57) The Importance of Measuring Productivity Holistically(00:35:54) AI Measurement Framework: Cost Dimension(00:38:34) AI Second Order Impact on Software Quality and Maintainability(00:42:38) The Danger of Vibe Coding(00:46:31) Treating AI as Extensions of Teams(00:52:31) The Bigger Bottlenecks to Solve Outside of AI Adoption(00:55:47) DX Guide to AI-Assisted Engineering(01:00:38) Being Deliberate for a Successful AI Rollout(01:02:32) 3 Tech Lead Wisdom_____Laura Tacho's BioLaura Tacho is CTO at DX, a developer intelligence platform, co-author of the Core 4 developer productivity metrics framework, and an executive coach. She's an experienced technology leader and engineering leadership coach with a strong background in developer tools and distributed systems.Her career includes leadership roles at organizations such as CloudBees, Aula Education, and Nova Credit, where she specialized in building high-performing engineering teams and delivering impactful products. Laura has worked with thousands of engineering leaders as they work to improve their engineering practices with data.Follow Laura:LinkedIn – linkedin.com/in/lauratachoTwitter – x.com/rhein_weinWebsite – lauratacho.com AI Measurement Framework – getdx.com/whitepaper/ai-measurement-framework/?utm_source=techleadjournal Guide to AI-Assisted Engineering – getdx.com/guide/ai-assisted-engineering/?utm_source=techleadjournalAI code metrics – getdx.com/ai-code-metricsLike this episode?Show notes & transcript: techleadjournal.dev/episodes/233.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

BONUS: Nesrine Changuel shares how to create product delight through emotional connection! In this BONUS episode we explore the book by Nesrine Changuel: 'Product Delight - How to make your product stand out with emotional connection.' In this conversation, we explore Nesrine's journey from research to product management, share lessons from her experiences at Google, Spotify, and Microsoft, and unpack the key strategies for building emotionally resonant products that connect with users beyond mere functionality. The Genesis of Product Delight "I quickly realized that there is something that is quite intense while building Skype... it's not just that communication tool, but it was iconic, with its blue, with ringtones, with emojis. So it was clear that it's not just for making calls, but also to make you feel connected, relaxed, and part of it." Nesrine's journey into product delight began during her transition from research to product management at Skype. Working on products at major companies like Skype, Spotify, and Google Meet, she discovered that successful products don't just function well—they create emotional connections. Her role as "Delight PM" at Google Meet during the pandemic crystallized her understanding that products must address both functional and emotional user needs to truly stand out in the market. Understanding Customer Delight in Practice "The delight is about creating two dimensions and combining these two dimensions altogether, it's about creating products that function well, but also that help with the emotional connection." Customer delight manifests when products exceed expectations and anticipate user needs. Nesrine explains that delight combines surprise and joy—creating positive surprises that go beyond basic functionality. She illustrates this with Microsoft Edge's coupon feature, which proactively suggests discounts during online shopping without users requesting it. This anticipation of needs creates memorable peak moments that strengthen emotional connections with products. Segmenting Users by Motivators "We can discover that users are using your product for different reasons. I mean, we tend to think that users are using the product for the same reason." Traditional user segmentation focuses on demographics (who users are) or behavior (what they do). Nesrine advocates for motivational segmentation—understanding why users engage with products. Using Spotify as an example, she demonstrates how users might seek music for specific songs, inspiration, nostalgia, or emotional regulation. This approach reveals both functional motivators (practical needs) and emotional motivators (feelings users want to experience), enabling teams to build features aligned with user desires rather than assumptions. In this segment, we refer to Spotify Wrapped.  The Distinction from Jobs To Be Done "There's no contrast. I mean to be honest, it's quite aligned, and I'm a big fan of the job to be done framework." While aligned with Clayton Christensen's Jobs To Be Done framework, Nesrine's approach extends beyond identifying triggers to practical implementation. She acknowledges that Jobs To Be Done provides the foundational theory, distinguishing between personal emotional motivators (how users want to feel) and social emotional motivators (how they want others to perceive them). However, many teams struggle to translate these insights into actual product features—a gap her Product Delight framework addresses through actionable methodologies. Navigating the Line Between Delight and Addiction "Building for delight is about creating products that are aligned with users' values. It's about aligning with what people really want themselves to feel. They want to feel themselves, to feel a better version of themselves." The critical distinction between delight and addiction lies in value alignment. Delightful products help users become better versions of themselves and align with their personal values. Nesrine contrasts this with addictive design that creates dependencies contrary to user wellbeing. Using Spotify Wrapped as an example, she explains how reflecting positive achievements (skills learned, personal growth) creates healthy engagement, while raw usage data (hours spent) might trigger negative self-reflection and potential addictive patterns. Getting Started with Product Delight "If you only focus on the functional motivators, you will create products that function, but they will not create that emotional connection. If you take into consideration the emotional motivators in addition to the functional motivators, you create perfect products that connect with users emotionally." Teams beginning their delight journey should start by identifying both functional and emotional user motivators through direct user conversations. The first step involves listing what users want to accomplish (functional) alongside how they want to feel (emotional). This dual understanding enables feature development that serves practical needs while creating positive emotional experiences, leading to products that users remember and recommend. Product Delight and Human-Centered Design "Making products feel as if it was done by a human being... how can you make your product feel as close as possible to a human version of the product." Nesrine positions product delight within the broader human-centered design movement, but focuses specifically on humanization at the product feature level rather than just visual design. She shares examples from Google Meet, where the team compared remote meetings to in-person experiences, and Dyson, which benchmarks vacuum cleaners against human cleaning services. This approach identifies missing human elements and guides feature development toward more natural, intuitive interactions. In this segment we refer to the books Emotional Design by Don Norman, and Design for Emotion by Aarron Walter..  AI's Role in Future Product Delight "AI is a tool, and as every tool we're using, it can be used in a good way, or could be used in a bad way. And it is extremely possible to use AI in a very good way to make your product feel more human and more empathetic and more emotionally engaging." AI presents opportunities to enhance emotional connections through empathetic interactions and personalized experiences. Nesrine cites ChatGPT's conversational style—including apologies and collaborative language—as creating companionship feelings during work. The key lies in using AI to identify and honor emotional motivators rather than exploit them, focusing on making users feel supported and understood rather than manipulated or dependent. Developer Experience as Product Delight "If the user of your products are human beings... whether business consumer engineers, they deserve their emotions to be honored, so I usually don't distinguish between B2B or B2C... I say like B2H, which is business to human." Developer experience exemplifies product delight in B2B contexts. Companies like GitHub have created metrics specifically measuring developer delight, recognizing that technical users also have emotional needs. Tools like Jira, Miro, and GitHub succeed by making users feel more competent and productive. Nesrine advocates for "B2H" (business to human) thinking, emphasizing that any product used by humans should consider emotional impact alongside functional requirements. About Nesrine Changuel Nesrine is a product coach, trainer, and author with experience at Google, Spotify, and Microsoft. Holding a PhD from Bell Labs and UCLA, she blends research and practice to guide teams in building emotionally resonant products. Based in Paris, she teaches and speaks globally on human-centered design. You can connect with Nesrine Changuel on LinkedIn.

It's been 10 years since the start of Community Pulse and, appropriately enough, we've reached the milestone of 100 episodes. To celebrate, we invited Jono Bacon -- our very first guest on the show -- and SJ Morris -- a former host of the show -- to join us and reminisce about changes in the DevRel industry as well as how we've changed personally and professionally over the last 10 years. We'll laugh a little… cry a little… and as always, learn a lot along the way. Checkouts Jason Bono * Primalbranding (https://a.co/d/0sCISVA) by Patrick Hanlon and Hooked (https://www.amazon.com/Hooked-How-Build-Habit-Forming-Products/dp/1591847788) by Nir Eyal - awesome books, very relevant * Attio (https://attio.com/) / OpusClip (https://www.opus.pro/) / Anam (https://anam.ai/) - awesome tools * Stateshift (https://www.stateshift.com/) * MobLand on Paramount+ (https://en.wikipedia.org/wiki/MobLand) SJ Morris * Developers, Reinvented (https://ashtom.github.io/developers-reinvented) * Design from the Margins (https://www.belfercenter.org/publication/design-margins) Wesley Faulkner * Kitten TTS (https://github.com/KittenML/KittenTTS) * Add Bluesky comments and likes to your blog (https://brittanyellich.com/bluesky-comments-likes/) PJ Hagerty * The AI Con (https://www.barnesandnoble.com/w/the-ai-con-emily-m-bender/1146281317?ean=9780063418561&gStoreCode=2542&gQT=2) - How to Fight Big Tech's Hype and Create the Future We Want by Emily M Bender and Alex Hanna * Tyler the Creator - Don't Tap the Glass (https://combine.fm/spotify/album/1jzv3jwZbt8lYfEtMjiD1R) Jason Hand * New After Pulse site (coming) * Anyone can Play Music (https://www.amazon.com/Anyone-Can-Play-Music-Potential/dp/0593850971) by Josh Turknett * 100 repos (and demos) * ai-tools-lab.com (https://ai-tools-lab.com/) * LLM Observability Learning Course (https://learn.datadoghq.com/courses/llm-obs-getting-started) (FREE) Mary Thengvall * Upcoming book that I had a preview of and am very excited about (coming from Apress in early 2026)! Developer Relations Activity Patterns: A Unified Approach to Devrel, DX and Community Management by Scott McAllister, David Neal, Ted Neward, and Chris Woodruff * Fun (random) things have made me smile lately: * Miniature Cheese Graters (https://amzn.to/45EJNbw) * Lapel Pins (https://amzn.to/41sYj3C) Special Guests: Jono Bacon and SJ Morris.

CEO Abi Noda is joined by DX CTO Laura Tacho to discuss the evolving role of Platform and DevProd teams in the AI era. Together, they unpack how AI is reshaping platform responsibilities, from evaluation and rollout to measurement, tool standardization, and guardrails. They explore why fundamentals like documentation and feedback loops matter more than ever for both developers and AI agents. They also share insights on reducing tool sprawl, hardening systems for higher throughput, and leveraging AI to tackle tech debt, modernize legacy code, and improve workflows across the SDLC.Where to find Abi Noda:• LinkedIn: https://www.linkedin.com/in/abinoda  • Substack: ​​https://substack.com/@abinoda  Where to find Laura Tacho: • LinkedIn: https://www.linkedin.com/in/lauratacho/• X: https://x.com/rhein_wein• Website: https://lauratacho.com/• Laura's course (Measuring Engineering Performance and AI Impact): https://lauratacho.com/developer-productivity-metrics-courseIn this episode, we cover:(00:00) Intro: Why platform teams need to evolve(02:34) The challenge of defining platform teams and how AI is changing expectations(04:44) Why evaluating and rolling out AI tools is becoming a core platform responsibility(07:14) Why platform teams need solid measurement frameworks to evaluate AI tools(08:56) Why platform leaders should champion education and advocacy on measurement(11:20) How AI code stresses pipelines and why platform teams must harden systems(12:24) Why platform teams must go beyond training to standardize tools and create workflows(14:31) How platform teams control tool sprawl(16:22) Why platform teams need strong guardrails and safety checks(18:41) The importance of standardizing tools and knowledge(19:44) The opportunity for platform teams to apply AI at scale across the organization(23:40) Quick recap of the key points so far(24:33) How AI helps modernize legacy code and handle migrations(25:45) Why focusing on fundamentals benefits both developers and AI agents(27:42) Identifying SDLC bottlenecks beyond AI code generation(30:08) Techniques for optimizing legacy code bases (32:47) How AI helps tackle tech debt and large-scale code migrations(35:40) Tools across the SDLCReferenced:DX Core 4 Productivity FrameworkMeasuring AI code assistants and agentsAbi Noda's LinkedIn postMeasuring AI code assistants and agents with the AI Measurement FrameworkThe SPACE framework: A comprehensive guide to developer productivityCommon workflows - AnthropicEnterprise Tech Leadership Summit Las Vegas 2025Driving enterprise-wide AI tool adoption with Bruno PassosAccelerating Large-Scale Test Migration with LLMs | by Charles Covey-Brandt | The Airbnb Tech Blog | MediumJustin Reock - DX | LinkedInA New Tool Saved Morgan Stanley More Than 280,000 Hours This Year - Business Insider

In this episode of the Crypto 101 podcast, host Bryce interviews Sreeram Kannan, founder of EigenCloud, discussing the innovative decentralized infrastructure being built for the crypto ecosystem. Sriram explains the vision behind EigenCloud, its unique features like EigenDA and Eigen compute, and how it aims to provide a verifiable and autonomous service layer for crypto builders. The conversation also touches on the evolution of Eigen, the importance of restaking, regulatory clarity, and the future of AI agents in the blockchain space. Sriram emphasizes the need for a cloud-like environment in crypto and the potential for EigenCloud to revolutionize the industry.Efani Sim Swap Protection: Get $99 Off: http://efani.com/crypto101Check out Plus500: https://plus500.comCheck out Avocado Green Mattress: https://avocadogreenmattress.comGet immediate access to my entire crypto portfolio for just $1.00 today! https://www.crypto101insider.com/cryptnation-directm6pypcy1?utm_source=Internal&utm_medium=YouTube&utm_content=Podcast&utm_term=DescriptionGet your FREE copy of "Crypto Revolution" and start making big profits from buying, selling, and trading cryptocurrency today: http://www.cryptorevolution.com/free?utm_source=Internal&utm_medium=YouTube&utm_content=Podcast&utm_term=DescriptionChapters00:00 Introduction to EigenCloud and Sriram Kannan01:06 Understanding EigenCloud's Vision and Functionality05:29 The Need for Decentralized Infrastructure in Crypto09:23 Evolution of Eigen and Shared Security Model10:53 Building a Cloud-like Environment for Crypto14:43 EigenDA and Its Role in Data Throughput16:07 EigenLayer's Unique Position in the Crypto Ecosystem18:49 Developer Experience and Programming Flexibility with EigenCompute22:29 Commercialization Efforts and Future Prospects for EigenCloud25:06 Understanding Total Value Locked (TVL) in EigenLayer26:38 Bootstrapping the Network and Earning Yield27:04 Redistribution in Ethereum Staking29:46 The Evolution of EigenLayer and DeFi Protocols30:16 Understanding Restaking and Addressing FUD33:33 Regulatory Clarity and Its Impact on Staking34:51 The Vision for the Future of Crypto41:37 Collaboration with Ethereum and Future Roadmap45:38 The Universal Utility of EigenLayerMERCH STOREhttps://cryptorevolutionmerch.com/Subscribe to YouTube for Exclusive Content:https://www.youtube.com/@crypto101podcast?sub_confirmation=1Follow us on social media for leading-edge crypto updates and trade alerts:https://twitter.com/Crypto101Podhttps://instagram.com/crypto_101Guest Linkhttps://x.com/eigenlayer*This is NOT financial, tax, or legal advice*Boardwalk Flock LLC. All Rights Reserved  ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬Fog by DIZARO https://soundcloud.com/dizarofrCreative Commons — Attribution-NoDerivs 3.0 Unported — CC BY-ND 3.0 Free Download / Stream: http://bit.ly/Fog-DIZAROMusic promoted by Audio Library https://youtu.be/lAfbjt_rmE8▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬Our Sponsors:* Check out Avocado Green Mattress: https://avocadogreenmattress.com* Check out Gemini Exchange: https://gemini.com/card* Check out Plus500: https://plus500.com* Check out Plus500: https://plus500.comAdvertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacy

BONUS: Jochen Issing on Building High-Performing Engineering Teams In this BONUS episode, we explore the fascinating journey of Jochen Issing, an engineering leader who brings unique insights from his background as a handball player and band member to building exceptional software development teams. From sports courts and music stages to engineering leadership, Jochen shares practical wisdom on psychological safety, team dynamics, and creating cultures where the best ideas win. From Sports and Music to Software Leadership "As soon as you complain about each other, you are starting to lose." Jochen's unconventional background as a handball player and band member has profoundly shaped his approach to engineering leadership. Drawing from team sports, he discovered that frustration leads to losing in both athletics and technology work. Great players in great teams optimize for the team's results, not individual glory. This translates directly to software development where great engineers slow down to make the team faster, recognizing that collective success trumps individual achievement. The lesson from the handball court is clear: when team members start blaming each other, they create a losing mindset that becomes self-fulfilling. Breaking the 10X Engineer Myth "It's not your success that makes our success, it's our success that makes your success." The mythology of the 10X engineer remains pervasive in software development, but Jochen challenges this with insights from team dynamics. The "hero culture" in companies often emerges when systems are already broken, requiring someone to step in and save the day. While we celebrate these heroes, we forget to ask the crucial question: how did we end up needing a hero in the first place? True high-performing teams don't require heroic individual efforts because they've built sustainable systems and shared knowledge. The goal isn't to eliminate talented individuals but to ensure that even the most skilled engineers can take time off without the organization grinding to a halt. Creating Psychological Safety Through Vulnerability "When psychological safety is missing, I try to ask ignorant questions - expose myself as being the least experienced person in the room." Building psychological safety requires intentional strategies that go beyond good intentions. Jochen employs a counterintuitive approach: when he senses team members hesitating to speak up, he deliberately asks "ignorant" questions to position himself as the least knowledgeable person in the room. This modeling behavior demonstrates that it's safe to admit uncertainty and ask questions. He also builds a culture of "challenging ourselves" by implementing ritualized dissent - assigning someone the specific job of finding flaws in proposed solutions. This prevents the dangerous harmony that can emerge when teams agree too quickly without proper scrutiny. The Power of the Expectation Sheet "I want people to share with me what might even drive them away from the company." Trust forms the foundation of effective team relationships, but building it requires explicit frameworks. Jochen uses an "expectation sheet" (See a prototype here Google Doc)- a document that formalizes mutual expectations between him and his team members. This tool establishes that he wants open, honest communication about everything, including situations that might drive someone to leave the company. The key principle is that he will never share confidential information or use personal disclosures against team members. This creates a relationship where he serves as both a representative of the company when necessary and a personal advocate for his team members when they need support navigating organizational challenges. Team-Centric Productivity and Collaboration "The team is the unit of productivity and delivery, not the individual." Effective engineering leadership requires balancing individual desires with team outcomes. Jochen emphasizes that while people naturally want to say "I did this," the focus must remain on team impact. This involves creating shared understanding of collective goals while still addressing individual needs and growth aspirations. Practical strategies include using on-call rotations to identify knowledge silos, implementing pair programming and mob programming to reinforce collaborative work patterns, and designing tasks that allow individuals to take ownership while remaining embedded in team efforts. The analogy to band dynamics is apt - when someone brings a song idea to the band, it evolves through collaboration into something different and usually better than the original vision. Building Sustainable High Performance "Great engineers slow down to make the team faster - which is how we get better teams." Sustainable high performance emerges when senior engineers invest in lifting the entire team rather than maximizing their individual output. This means senior staff level engineers focus less on their personal contributions and more on forming "tribes" across teams, coaching junior engineers, and building organizational capability. The measure of success shifts from individual heroics to collective achievement - if problems consistently require the same person to fix them, the team hasn't truly succeeded in building sustainable systems and shared knowledge. Recommended Resources for Further Reading Jochen recommends several foundational books for understanding team dynamics and engineering leadership. "The Culture Code" by Daniel Coyle explores the structure of high-performing teams and debunks myths about command-and-control leadership. "Product Development Flow" by Reinertsen provides the scientific foundation behind agile methodologies and explains what teams are really trying to solve. "The Culture Map" by Erin Meyer offers insights on working with diverse cultures and backgrounds to bring out the best in each team member. "Coaching Agile Teams" by Lyssa Adkins serves as a practical guide for developing coaching skills in technical environments. And our very own Scrum Master Toolbox podcast provides ongoing insights and real-world experiences from practitioners in the field. About Jochen Issing Jochen is an engineering leader who's all about building great teams and better developer experiences. From audio tech and cloud platforms to monorepos and feedback culture, he's done it all. A former bandmate and handball player, Jochen brings heart, trust, and collaboration into everything he builds with his teams. You can connect with Jochen Issing on LinkedIn and connect with Jochen Issing on Twitter.

In banking, every second matters. Fraud happens in milliseconds. Customers demand instant answers. And AI can only deliver value if it's powered by live, real-time data. Yet many banks are still relying on batch reports and outdated systems, making decisions based on yesterday's insights. The shift can't wait. Forrester predicts that by 2025, half of all businesses will use AI-powered self-service as their primary customer touchpoint. That future won't be possible without real-time data at the core. Banks that leverage streaming data will transform customer experiences, manage risks more efficiently, and unlock the full potential of AI. Those who don't risk being left behind. Today, I'm joined by Guillaume Aymé, CEO of Lenses.io and a leading voice on data innovation. Together, we'll explore why real-time data is becoming the lifeblood of modern banking, the hurdles institutions must overcome, and how to build the foundation for AI-driven success. This episode of Banking Transformed is sponsored by Lenses Lenses 6.0 is a Developer Experience designed to empower organizations to modernize applications and systems with real-time data autonomy. This is particularly crucial as AI adoption accelerates, and enterprises operate hundreds of Kafka clusters across multi-cloud environments. As the industry's first multi-Kafka developer experience, Lenses 6.0 allows teams to access, govern and process streaming data across any combination of Apache Kafka-based streaming platforms, from a single interface. https://lenses.io/

In this episode, host Laura Tacho speaks with Jesse Adametz, Senior Engineering Leader on the Developer Platform at Twilio. Jesse is leading Twilio's multi-year platform consolidation, unifying tech stacks across large acquisitions and driving migrations at enterprise scale. He discusses platform adoption, the limits of Kubernetes, and how Twilio balances modernization with pragmatism. The conversation also explores treating developer experience as a product, offering “change as a service,” and Twilio's evolving approach to AI adoption and platform support.Where to find Jesse Adametz: • LinkedIn: https://www.linkedin.com/in/jesseadametz/• X: https://x.com/jesseadametz• Website: https://www.jesseadametz.com/Where to find Laura Tacho:• LinkedIn: https://www.linkedin.com/in/lauratacho/• X: https://x.com/rhein_wein• Website: https://lauratacho.com/• Laura's course (Measuring Engineering Performance and AI Impact) https://lauratacho.com/developer-productivity-metrics-courseIn this episode, we cover:(00:00) Intro(01:30) Jesse's background and how he ended up at Twilio(04:00) What SRE teaches leaders and ICs(06:06) Where Twilio started the post-acquisition integration(08:22) Why platform migrations can't follow a straight-line plan(10:05) How Twilio balances multiple strategies for migrations(12:30) The human side of change: advocacy, training, and alignment(17:46) Treating developer experience as a first-class product(21:40) What “change as a service” looks like in practice(24:57) A mandateless approach: creating voluntary adoption through value(28:50) How Twilio demonstrates value with metrics and reviews(30:41) Why Kubernetes wasn't the right fit for all Twilio workloads (36:12) How Twilio decides when to expose complexity(38:23) Lessons from Kubernetes hype and how AI demands more experimentation(44:48) Where AI fits into Twilio's platform strategy(49:45) How guilds fill needs the platform team hasn't yet met(51:17) The future of platform in centralizing knowledge and standards(54:32) How Twilio evaluates tools for fit, pricing, and reliability (57:53) Where Twilio applies AI in reliability, and where Jesse is skeptical(59:26) Laura's vibe-coded side project built on Twilio(1:01:11) How external lessons shape Twilio's approach to platform support and docsReferenced:The AI Measurement FrameworkExperianTransact-SQL - WikipediaTwilioKubernetesCopilotClaude CodeWindsurfCursorBedrock

Lee Robinson helped Vercel grow to $200M+ in ARR and scaled the Next.js community to over 1.3 million active developers. I dive into his blog posts to uncover valuable insights and lessons about how he achieved this success, covering topics like docs, community building, developer education, marketing, and product development.This episode is brought to you by WorkOS. If you're thinking about selling to enterprise customers, WorkOS can help you add enterprise features like Single Sign On and audit logs.Links:   •  Lee Robinson's blog   •  Lee Robinson's X   •  Peter Yang's interview   •  swyx's interview   •  Gonto on Scaling DevTools   •  Developer Marketing CommunityP.s. this is a new style of episode, let me know what you think. 

In this episode of Engineering Enablement, host Laura Tacho talks with Bruno Passos, Product Lead for Developer Experience at Booking.com, about how the company is rolling out AI tools across a 3,000-person engineering team.Bruno shares how Booking.com set ambitious innovation goals, why cultural change mattered as much as technology, and the education practices that turned hesitant developers into daily users. He also reflects on the early barriers, from low adoption and knowledge gaps to procurement hurdles, and explains the interventions that worked, including learning paths, hackathon-style workshops, Slack communities, and centralized procurement. The result is that Booking.com now sits in the top 25 percent of companies for AI adoption.Where to find Bruno Passos:• LinkedIn: https://www.linkedin.com/in/brpassos/• X: https://x.com/brunopassosWhere to find Laura Tacho:• LinkedIn: https://www.linkedin.com/in/lauratacho/• X: https://x.com/rhein_wein• Website: https://lauratacho.com/• Laura's course (Measuring Engineering Performance and AI Impact) https://lauratacho.com/developer-productivity-metrics-courseIn this episode, we cover:(00:00) Intro(01:09) Bruno's role at Booking.com and an overview of the business (02:19) Booking.com's goals when introducing AI tooling(03:26) Why Booking.com made such an ambitious innovation ratio goal (06:46) The beginning of Booking.com's journey with AI(08:54) Why the initial adoption of Cody was low(13:17) How education and enablement fueled adoption(15:48) The importance of a top-down cultural change for AI adoption(17:38) The ongoing journey of determining the right metrics(21:44) Measuring the longer-term impact of AI (27:04) How Booking.com solved internal bottlenecks to testing new tools(32:10) Booking.com's framework for evaluating new tools(35:50) The state of adoption at Booking.com and efforts to expand AI use(37:07) What's still undetermined about AI's impact on PR/MR quality(39:48) How Booking.com is addressing lagging adoption and monitoring churn(43:24) How Booking.com's Slack community lowers friction for questions and support(44:35) Closing thoughts on what's next for Booking.com's AI planReferenced:Measuring AI code assistants and agentsDX Core 4 FrameworkBooking.comSourcegraph SearchCody | AI coding assistant from SourcegraphGreyson Junggren - DX | LinkedIn

Join me as I chat with Lee Robinson, VP of Developer Experience at Cursor, as he shares practical tips for maximizing productivity with Cursor's AI coding tools. He demonstrates how to structure prompts, create custom commands, and leverage agents for everything from bug fixes to code reviews. The conversation highlights how AI tools are making software development more accessible while enabling developers to build higher quality products with less effort. Timestamps: 00:00 - Intro 01:49 - Using AI Agents in Cursor 08:21 - Custom Rules within Cursor 11:49 - BugBot and code review automation 17:19 - CLI and headless options for Cursor agents 19:29 - Tips for getting the most out of Cursor 21:09 - Examples of innovative software built with Cursor Get Your Complete Financial OS at https://dub.sh/brex-sip Key Points: • Lee demonstrates how to effectively use Cursor's AI agents for discrete coding tasks • Setting up proper linting, formatting, and testing helps agents self-correct their outputs • Custom commands and rules can be created to enhance code reviews and writing quality • Cursor offers CLI and headless options for running agents in automation workflow The #1 tool to find startup ideas/trends - https://www.ideabrowser.com LCA helps Fortune 500s and fast-growing startups build their future - from Warner Music to Fortnite to Dropbox. We turn 'what if' into reality with AI, apps, and next-gen products https://latecheckout.agency/ Boringmarketing - Vibe Marketing for Companies: boringmarketing.com  The Vibe Marketer - Join the Community and Learn: thevibemarketer.com Startup Empire - a membership for builders who want to build cash-flowing businesses https://www.skool.com/startupempire/about FIND ME ON SOCIAL X/Twitter: https://twitter.com/gregisenberg  Instagram: https://instagram.com/gregisenberg/ LinkedIn: https://www.linkedin.com/in/gisenberg/ FIND LEE ON SOCIAL X/Twitter: https://x.com/leeerob YouTube: https://www.youtube.com/@leerob Personal Website: https://leerob.com

Web development is constantly evolving, and so are the tools we use to build. In this episode, Amy and Brad chat with the organizers of Squiggle Conf about the future of web dev tooling, how conferences shape the developer experience, and why community matters just as much as code.Chapters0:00 - Intro0:34 - Meet the Guests: Squiggle Conf OrganizersSquiggle Conf1:19 - What Makes Squiggle Conf Unique3:19 - Tooling and Developer Experience3:30 - Penguins, IMAX, and the Conference Venue4:18 - Who Should Attend Squiggle Conf5:31 - How Talks Are Selected and Curated6:51 - Social and Community Aspects of the Conference12:19 - Behind the Scenes of Organizing a Conference17:46 - Lessons Learned from Running Events23:30 - The Role of Tooling in Modern Development27:21 - Browser-Based Tools and Their Impact28:51 - Shoutout to Astro and Other FrameworksAstroStarlight - Astro's template for documentation33:51 - Comparing Different Conference Experiences38:55 - Building Momentum in the Developer Community40:45 - Looking Ahead: The Future of Squiggle Conf42:02 - Final Thoughts from the Organizers43:43 - Picks and PlugsAre the Types Wrong? — a package & CLI tool by Andrew Branch from the TypeScript teamThe Harry Potter movie seriesCloudflareOne Switch - Mac Menu Bar AppRedwoodSDK

Niklas and Marco break down SAP's new clean core levels using relatable metaphors, explain the evolution from the classic extensibility model, and share practical advice for developers and architects. Learn about essential tools like the SAP Discovery Center, Guidance Framework, and ABAP Test Cockpit, and get actionable best practices for your clean core journey. Whether you're a seasoned SAP developer or just starting out, this episode offers valuable insights, real-world examples, and even a few personal recommendations to inspire your next steps.

Niklas and Marco break down SAP's new clean core levels using relatable metaphors, explain the evolution from the classic extensibility model, and share practical advice for developers and architects. Learn about essential tools like the SAP Discovery Center, Guidance Framework, and ABAP Test Cockpit, and get actionable best practices for your clean core journey. Whether you're a seasoned SAP developer or just starting out, this episode offers valuable insights, real-world examples, and even a few personal recommendations to inspire your next steps.

This episode is sponsored by P0 Security. Visit p0.dev/idac to learn why P0 is the easiest and fastest way to implement just-in-time, short-lived, and auditable access to your entire infrastructure stack, like servers, databases, Kubernetes clusters, cloud consoles, and cloud services, for users as well as non-human identities.In this sponsor spotlight episode, Jim and Jeff are joined by Shashwat Sehgal, CEO and founder of P0 Security, to discuss the evolving challenges of privileged access management in modern, cloud-native environments. Shashwat explains how traditional PAM solutions often create friction for developers, leading to over-provisioning and security risks, and how P0 is tackling this problem with a developer-first, just in time (JIT) access model. The conversation covers the core problems with developer productivity, how P0's use of technologies like eBPF provides deep visibility and control without agents, the "Priority Zero" philosophy, and how a JIT approach simplifies audits and compliance. They also discuss the competitive landscape and what sets P0 Security apart from traditional and open-source solutions.Learn more about P0: https://www.p0.dev/idacConnect with Shashwat: https://www.linkedin.com/in/shashwatsehgal/Chapter Timestamps:00:00 - Podcast Intro00:29 - Sponsor Introduction: P0 Security01:38 - What is the problem P0 Security is trying to solve?03:52 - Defining "Just-in-Time" (JIT) Access06:21 - The challenge with traditional PAM for developers08:23 - How P0 provides access without agents using eBPF12:15 - What does the user experience look like?15:58 - Supporting various infrastructure and access protocols19:15 - How does P0 handle session recording and auditing?22:20 - Is this a replacement for Privileged Access Management (PAM)?26:40 - The story behind the name P0 Security29:20 - Who is the ideal customer for P0?33:15 - Handling break-glass scenarios36:04 - Discussing the competitive landscape42:30 - How is P0 deployed? (Cloud vs. On-prem)46:50 - The future of P0 and the "Priority Zero" philosophy50:32 - Final thoughts: "Access is our priority zero."Connect with us on LinkedIn:Jim McDonald: https://www.linkedin.com/in/jimmcdonaldpmp/Jeff Steadman: https://www.linkedin.com/in/jeffsteadman/Visit the show on the web at http://idacpodcast.comKeywords:P0 Security, Shashwat Sagal, Privileged Access Management, PAM, Just-in-Time Access, JIT, Developer Security, Cloud-Native Security, Hybrid Cloud, eBPF, Kubernetes, IAM, Identity and Access Management, Cybersecurity, Zero Trust, Ephemeral Access, Developer Experience, IDAC, Identity at the Center, Jeff Steadman, Jim McDonald

In this episode of Engineering Enablement, DX CTO Laura Tacho and CEO Abi Noda break down how to measure developer productivity in the age of AI using DX's AI Measurement Framework. Drawing on research with industry leaders, vendors, and hundreds of organizations, they explain how to move beyond vendor hype and headlines to make data-driven decisions about AI adoption.They cover why some fundamentals of productivity measurement remain constant, the pitfalls of over-relying on flawed metrics like acceptance rate, and how to track AI's real impact across utilization, quality, and cost. The conversation also explores measuring agentic workflows, expanding the definition of “developer” to include new AI-enabled contributors, and avoiding second-order effects like technical debt and slowed PR throughput.Whether you're rolling out AI coding tools, experimenting with autonomous agents, or just trying to separate signal from noise, this episode offers a practical roadmap for understanding AI's role in your organization—and ensuring it delivers sustainable, long-term gains.Where to find Laura Tacho:• X: https://x.com/rhein_wein• LinkedIn: https://www.linkedin.com/in/lauratacho/• Website: https://lauratacho.com/Where to find Abi Noda:• LinkedIn: https://www.linkedin.com/in/abinoda • Substack: ​​https://substack.com/@abinoda In this episode, we cover:(00:00) Intro(01:26) The challenge of measuring developer productivity in the AI age(04:17) Measuring productivity in the AI era — what stays the same and what changes(07:25) How to use DX's AI Measurement Framework (13:10) Measuring AI's true impact from adoption rates to long-term quality and maintainability(16:31) Why acceptance rate is flawed — and DX's approach to tracking AI-authored code(18:25) Three ways to gather measurement data(21:55) How Google measures time savings and why self-reported data is misleading(24:25) How to measure agentic workflows and a case for expanding the definition of developer(28:50) A case for not overemphasizing AI's role(30:31) Measuring second-order effects (32:26) Audience Q&A: applying metrics in practice(36:45) Wrap up: best practices for rollout and communication Referenced:DX Core 4 Productivity FrameworkMeasuring AI code assistants and agentsAI is making Google engineers 10% more productive, says Sundar Pichai - Business Insider

In this episode, Jason, Wesley, and Mary share some of our favorite tools of the trade—from live streaming setups and demo-building tricks to the software and hardware we rely on for recording videos and tracking metrics. Join us for a practical, behind-the-scenes look at the gear and workflows that help us connect with developers and communities every day. Categories Building & Managing Websites Hugo (https://gohugo.io/) Astro (https://astro.build/) Form Bricks (https://formbricks.com/) Local Recall (https://github.com/mudler/LocalRecall) SquareSpace (https://www.squarespace.com/) Eleventy (https://www.11ty.dev/) Data, metrics, and knowledge sharing Airtable (https://airtable.com/) Common Room (https://www.commonroom.io/) Metabase (https://www.metabase.com/) Scheduling meetings Cal.com (https://cal.com/) Fantastical (https://flexibits.com/fantastical) LiveStreaming & video recording and editing Streamyard (https://streamyard.com/) Riverside.fm (http://riverside.fm/) OBS (https://obsproject.com/) OpenShot (https://www.openshot.org/) Audacity (https://www.audacityteam.org/) VLC (https://www.videolan.org/vlc/) Descript (https://www.descript.com/) Otter Meeting Agent - AI Notetaker, Transcription, Insights (http://otter.ai/) Automation tools n8n (https://n8n.io/) Zapier (https://zapier.com/) IFTTT (https://ifttt.com/) Forums Slack (https://slack.com/) Discourse (https://www.discourse.org/) Podcast hosting Fireside (https://fireside.fm/) Building demos Claude Code (https://chat.chatbot.app/claude?utm_source=GoogleAds&utm_medium=cpc&utm_campaign={campaign}&utm_id=22665042439&utm_term=180325682866&utm_content=767386553008&gad_source=1&gad_campaignid=22665042439&gbraid=0AAAAA_a6ETtwr7jtRKa-4KqypAZlQydKF&gclid=CjwKCAjw49vEBhAVEiwADnMbbDl9w_QW525TCw1W56_NGJOqgGOZDKJopNiYSH_pc_yRGVDpUoZ1CxoCL1UQAvD_BwE) Lovable (https://lovable.dev/?via=promo80&via=promo80&gad_source=1) Cursor (https://cursor.com/en) LocalAI (https://localai.io/) Enjoy the podcast? Please take a few moments to leave us a review on iTunes (https://itunes.apple.com/us/podcast/community-pulse/id1218368182?mt=2) and follow us on Spotify (https://open.spotify.com/show/3I7g5W9fMSgpWu38zZMjet?si=eb528c7de12b4d7a&nd=1&dlsi=b0c85248dabc48ce), or leave a review on one of the other many podcasting sites that we're on! Your support means a lot to us and helps us continue to produce episodes every month. Like all things Community, this too takes a village. Photo by Todd Quackenbush on Unsplash.

In this special episode of the Engineering Enablement podcast, recorded live at LeadDev London, DX CTO Laura Tacho explores the growing gap between AI headlines and the reality inside engineering teams—and what leaders can do to close it.Laura shares data from nearly 39,000 developers across 184 companies, highlights the Core 4 and introduces the AI Measurement Framework, and offers a practical playbook for using data to improve developer experience, measure AI's true impact, and build better software without compromising long-term performance.Where to find Laura Tacho:• X: https://x.com/rhein_wein• LinkedIn: https://www.linkedin.com/in/lauratacho/• Website: https://lauratacho.com/In this episode, we cover:(00:00) Intro: Laura's keynote from LDX3(01:44) The problem with asking how much faster can we go with AI?(03:02) How the disappointment gap creates barriers to AI adoption(06:20) What AI adoption looks like at top-performing organizations(07:53) What leaders must do to turn AI into meaningful impact(10:50) Why building better software with AI still depends on fundamentals(12:03) An overview of the DX Core 4 Framework(13:22) Why developer experience is the biggest performance lever(15:12) How Block used Core 4 and DXI to identify 500,000 hours in time savings(16:08) How to get started with Core 4(17:32) Measuring AI with the AI Measurement Framework(21:45) Final takeaways and how to get started with confidenceReferenced:LDX3 by LeadDev | The Festival of Software Engineering Leadership | LondonSoftware engineering with LLMs in 2025: reality checkSPACE framework, PRs per engineer, AI researchThe AI adoption playbook: Lessons from Microsoft's internal strategyDX Core 4 Productivity FrameworkNicole ForsgrenMargaret-Anne StoreyDropbox.comEtsyPfizerDrew Houston - Dropbox | LinkedInBlockCursorDora.devSourcegraphBooking.com

In this episode of PodRocket, Daniel Roe, lead dev over at NuxtLabs, joins Paul to discuss the big news: NuxtLabs is joining Vercel. They dive into what this partnership means for Nuxt, the independence of the open-source framework, and how products like Nuxt UI Pro, Nuxt Studio, and Nuxt Hub are evolving. Daniel also shares insights on zero-config deployments, maintaining choice for developers, and the philosophy behind keeping Nuxt open and flexible. Links Website: https://roe.dev LinkedIn: https://www.linkedin.com/in/daniel-roe Github: https://github.com/danielroe Bluesky: https://bsky.app/profile/danielroe.dev Mastodon: https://mastodon.roe.dev/@daniel Twitch: https://www.twitch.tv/danielroe YouTube: https://www.youtube.com/@danielroe Resources Announcement Post: https://vercel.com/blog/nuxtlabs-joins-vercel Nuxt Labs: https://nuxtlabs.com We want to hear from you! How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend? Fill out our listener survey (https://t.co/oKVAEXipxu)! https://t.co/oKVAEXipxu Let us know by sending an email to our producer, Em, at emily.kochanek@logrocket.com (mailto:emily.kochanek@logrocket.com), or tweet at us at PodRocketPod (https://twitter.com/PodRocketpod). Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understanding where your users are struggling by trying it for free at LogRocket.com. Try LogRocket for free today. (https://logrocket.com/signup/?pdr) Special Guest: Daniel Roe.

How does someone with a non-traditional background end up leading Developer Relations for a tech giant like Slack? In this episode, host Jack McCurdy dives deep into the incredible story of Kurt Kemple.Kurt pulls back the curtain on his journey and shares the hard-won lessons that shaped his philosophy on community, collaboration, and creating meaningful tech. He reveals the critical importance of developer enablement and challenges a "build it and they will come" mentality.Get ready for a powerful conversation about the human side of DevOps. You'll hear Kurt's take on the future of community, the one framework that clarifies every project, and why building relationships is the ultimate key to shared success.About DevOps Diaries: Salesforce DevOps Advocate Jack McCurdy chats to members of the Salesforce community about their experience in the Salesforce ecosystem. Expect to hear and learn from inspirational stories of personal growth and business success, whilst discovering all the trials, tribulations, and joy that comes with delivering Salesforce for companies of all shapes and sizes. New episodes bi-weekly on YouTube as well as on your preferred podcast platform.Podcast produced and sponsored by Gearset. Learn more about Gearset: https://grst.co/4iCnas2Subscribe to Gearset's YouTube channel: https://grst.co/4cTAAxmLinkedIn: https://www.linkedin.com/company/gearsetX/Twitter: https://x.com/GearsetHQFacebook: https://www.facebook.com/gearsethqAbout Gearset: Gearset is the leading Salesforce DevOps platform, with powerful solutions for metadata and CPQ deployments, CI/CD, automated testing, sandbox seeding and backups. It helps Salesforce teams apply DevOps best practices to their development and release process, so they can rapidly and securely deliver higher-quality projects. Get full access to all of Gearset's features for free with a 30-day trial: https://grst.co/4iKysKWChapters:00:00 Introduction to Kurt Kemple and Slack02:56 Kurt's Journey into Tech and Developer Relations05:34 The Importance of Tech Enablement08:42 Building a Career in Tech11:35 The Role of Community in Tech14:16 Job to Be Done Framework and Its Impact17:25 The Future of Community and Connection19:57 Reflections on Personal Communities and Growth24:53 The Power of Community in Professional Growth26:40 Aligning Business with User Needs28:23 Building Internal Communities30:08 Overcoming Resistance in Internal Teams31:41 The Importance of User Feedback33:51 Empathy in Community Building35:40 The Flywheel Effect in Developer Relations37:36 Collaborative Language and Shared Ownership39:44 The Role of Developer Relations41:54 Education and Enablement through Community43:13 Leveraging Slack for Effective Collaboration47:02 The Future of Slack and Developer Experience

In this episode of the Engineering Enablement podcast, host Abi Noda is joined by Quentin Anthony, Head of Model Training at Zyphra and a contributor at EleutherAI. Quentin participated in METR's recent study on AI coding tools, which revealed that developers often slowed down when using AI—despite feeling more productive. He and Abi unpack the unexpected results of the study, which tasks AI tools actually help with, and how engineering teams can adopt them more effectively by focusing on task-level fit and developing better digital hygiene.Where to find Quentin Anthony: • LinkedIn: https://www.linkedin.com/in/quentin-anthony/• X: https://x.com/QuentinAnthon15Where to find Abi Noda:• LinkedIn: https://www.linkedin.com/in/abinoda In this episode, we cover:(00:00) Intro(01:32) A brief overview of Quentin's background and current work(02:05) An explanation of METR and the study Quentin participated in (11:02) Surprising results of the METR study (12:47) Quentin's takeaways from the study's results (16:30) How developers can avoid bloated code bases through self-reflection(19:31) Signs that you're not making progress with a model (21:25) What is “context rot”?(23:04) Advice for combating context rot(25:34) How to make the most of your idle time as a developer(28:13) Developer hygiene: the case for selectively using AI tools(33:28) How to interact effectively with new models(35:28) Why organizations should focus on tasks that AI handles well(38:01) Where AI fits in the software development lifecycle(39:40) How to approach testing with models(40:31) What makes models different (42:05) Quentin's thoughts on agents Referenced:DX Core 4 Productivity FrameworkZyphraEleutherAIMETRCursorClaudeLibreChatGoogle GeminiIntroducing OpenAI o3 and o4-miniMETR's study on how AI affects developer productivityQuentin Anthony on X: "I was one of the 16 devs in this study."Context rot from Hacker NewsTracing the thoughts of a large language modelKimiGrok 4 | xAI

TypeScript might feel slow, but is it really? In this episode, Mike Hartington DevRel at Nx joins us fresh off his React Miami talk to unpack what actually causes TypeScript slowdowns in large monorepos, and how techniques like project references, workspaces, and precompiled DTS files can supercharge your dev experience. We also dig into the upcoming Go-based TypeScript compiler and how it could deliver 10x+ performance gains. Links Website: https://mhartington.io X: https://x.com/mhartington Github: https://github.com/mhartington Bluesky: https://bsky.app/profile/mhartington.io LinkedIn: https://www.linkedin.com/in/mhartington Resources React Miami Talk: https://www.youtube.com/watch?v=QI3JBQl7SPM We want to hear from you! How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend? Fill out our listener survey (https://t.co/oKVAEXipxu)! https://t.co/oKVAEXipxu Let us know by sending an email to our producer, Em, at emily.kochanek@logrocket.com (mailto:emily.kochanek@logrocket.com), or tweet at us at PodRocketPod (https://twitter.com/PodRocketpod). Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understanding where your users are struggling by trying it for free at LogRocket.com. Try LogRocket for free today. (https://logrocket.com/signup/?pdr) Special Guest: Mike Hartington.

Cette semaine, tu vas faire la connaissance de Romain Huet, un Français à la trajectoire pas commune : ex-fondateur de startup devenu un pilier de la tech américaine chez Twitter, Stripe et désormais OpenAI. Il dirige - depuis San Francisco - la Developer Experience de la maison mère de ChatGPT. Avec lui et en exclu pour toi, on va revenir sur les coulisses des modèles d'IA, la révolution agentique, la plateforme développeur d'OpenAI, et les ambitions folles de cette startup valorisée 300 milliards avec ses 500 millions d'utilisateurs actifs chaque semaine. Je suis Seb Couasnon, tu aimes ce RDV ? Mets-moi 5 étoiles et laisse moi un commentaire, une remarque, une idée d'invité, tu me contactes sur LinkedIn ou X, je te réponds, d'avance merci, bon épisode !Et bel été si t'es en vacances ou t'apprêtes à souffler un peu ⛱️Distribué par Audiomeans. Visitez audiomeans.fr/politique-de-confidentialite pour plus d'informations.

C'est la startup la mieux valorisée au mode ! 300 mds de dollars, voilà ce que vaut la maison-mère de ChatGPT en cet été 2025

Vue developer Alex Riviere joins Amy to explore the fundamental differences between Vue and React, diving deep into Vue's unique approach to reactivity, templating, and developer experience. From the magic of V-Model eliminating controlled/uncontrolled input complexity to Vue's proxy-based reactivity system that "just works," Alex explains why Vue's mental model clicked for him coming from jQuery. The conversation covers Vue 3's Composition API and Script Setup syntax, the evolution from VueX to Pinia for state management, and exciting developments like Vue Vapor Mode that will eliminate the virtual DOM entirely. Alex also breaks down Evan You's recent $4.6M VoidZero funding to revolutionize JavaScript build tooling, the flexibility of Nuxt as a meta-framework, and why Vue remains approachable enough to sprinkle into any project without complex build steps. Show Notes00:00 - Intro01:10 - How Alex Got Started with Vue03:00 - Vue vs React Mental Models08:00 - Vue's Approach to Forms and V-Model10:20 - Vue Frameworks: Nuxt and the Ecosystem17:00 - Vue 2 to Vue 3 Migration Challenges19:00 - Nuxt as a Dev Dependency vs Runtime22:30 - When Do You Need a Framework with Vue?25:30 - Laravel Integration and Alpine.js Connection27:40 - Vue's Reactivity System and Proxies29:40 - State Management: VueX to Pinia Evolution32:20 - SSR and Server Components in Vue34:10 - Hosting and Deployment Options35:40 - Evan You's VoidZero Funding and Vision43:10 - Vue Vapor Mode: Eliminating Virtual DOM47:40 - Getting Started with Vue Resources48:40 - Picks and Plugs Links and ResourcesPeople MentionedAlex Riviere - @alexriviereEvan You - Vue.js creator - @youyuxiBen Hong - Vue core team member - @bencodezenDaniel Roe - Nuxt team - @danielcroeTaylor Otwell - Laravel creator - @taylorotwellVue.js ResourcesVue.js Official Site - vuejs.orgVue.js Documentation - vuejs.org/guideVue School - vueschool.ioVue Mastery - vuemastery.comFrameworks & Tools MentionedNuxt - nuxt.comVite - vitejs.devAstro - astro.buildPinia (Vue state management) - pinia.vuejs.orgVueX (legacy state management) - vuex.vuejs.orgAlpine.js - alpinejs.devLaravel - laravel.comLivewire - livewire.laravel.comSolid.js - solidjs.comReact - react.devSvelte - svelte.devBuild Tools & InfrastructureESBuild - esbuild.github.ioRollup - rollupjs.orgNitroPack - nitro.unjs.ioWebpack - webpack.js.orgVoidZero (Evan You's new company) - voidzero.devHosting PlatformsNetlify - netlify.comVercel - vercel.comCloudflare - cloudflare.comReact Ecosystem (for comparison)Next.js - nextjs.orgRemix - remix.runRedwoodJS - redwoodjs.comGatsby - gatsbyjs.comPodcasts & ContentDeja Vue Podcast - dejavue.fm (mentioned Evan You VoidZero interview)Vue.js Conferences - VueConf eventsTechnical Concepts to ResearchVue Composition API - vuejs.org/guide/extras/composition-api-faq.htmlVue Script Setup - vuejs.org/api/sfc-script-setup.htmlVue Directives - vuejs.org/guide/essentials/template-syntax.html#directivesVue Reactivity - vuejs.org/guide/extras/reactivity-in-depth.htmlVue Vapor Mode (experimental) - github.com/vuejs/core-vaporJavaScript Proxies - MDN Proxy DocumentationSignals (reactive programming) - General concept in modern frameworksPicks & PlugsDropout TV - Nobody Asked - dropout.tvCodeMash Conference - codemash.orgWhoosh Screen Cleaner - https://amzn.to/4nBR5UtAdditional Helpful ResourcesVue 2 to Vue 3 Migration Guide - v3-migration.vuejs.orgVue vs React Comparison - vuejs.org/guide/extras/composition-api-faq.html#comparison-with-react-hooksIslands Architecture - jasonformat.com/islands-architecture

In this episode, Matt and Mike dive into developer experience (DX) — what it is, why it matters, and how improving it can make you a better developer. They share personal stories of frustrating build processes, game-changing tools, and scripting away pain points. Whether it's speeding up deployments, eliminating unnecessary rebuilds, or embracing platforms like Vercel and PlanetScale, there's never been a better time to take your DX into your own hands. Show Notes: https://www.htmlallthethings.com/podcasts/why-developer-experience-matters Use our affiliate link (https://scrimba.com/?via=htmlallthethings) for a 20% discount!! Full details in show notes.

Developer experience is one of the areas where AI applications are showing significant return on investment, but there are significant hurdles to overcome in both changing established development patterns, as well as integrating AI tooling. Analyst Jean Atelsek and AWS vice president for developer experience Deepak Singh join host Eric Hanselman to explore the current state of AI code assistance and look at where it's headed. Auto-complete, where the next bit of a line of code is filled in for a programmer, has been evolving over a number of years, but the arrival of agents to augment code generation and task automation is being to revolutionize software development. Changing development patterns is hard, but the benefits offer strong incentives to change habits. Where early uses had AI engines generate smaller code snippets that developers integrated, that's changing to having AI tackle full functions that are then reviewed and corrected. Tooling around AI implementations are tailoring they way in which they interact with individual developers, enhancing their experience. Application modernization is an area where AI can shine, as it can assess a massive codebase whose authors are no longer available and provide not only documentation, but also prioritize recoding efforts. It's a task where the hours required for manual assessment can be daunting and error prone. Leveraging AI code generation securely requires that organizations have sufficiently secure development pipelines. Mitigating risks from confabulation and errors in AI generated code is the same process as ought to be in place for human coders, an area where some less mature organizations may have some catching up to do. More S&P Global Content: The 2025 Generative AI Outlook For S&P Global subscribers: Can generative AI modernize legacy code bases? It depends Tech Trend in Focus: Generative AI in programming Generative AI Market Monitor & Forecast Credits: Host/Author: Eric Hanselman Guests: Jean Atelsek, Deepak Singh Producer/Editor: Adam Kovalsky Published With Assistance From: Sophie Carr, Feranmi Adeoshun, Kyra Smith

In this episode of Talking Drupal, we dive into the world of Drupal user groups and meetups with guests Lee Walker, Bernardo Martinez, and Bo Shipley. Our guests share their experiences in organizing and participating in Drupal communities and the vital role these meetups play in fostering continuous learning and professional development. We also explore the newest features of Drupal Core 11.2 in the Module of the Week. For show notes visit: https://www.talkingDrupal.com/508 Topics Meet the Guests: Lee, Bo, and Bernardo Module of the Week: Drupal Core 11.2 Diving into Drupal User Groups and Meetups Personal Journeys into Drupal User Groups The Role of Meetup.com in Drupal Communities Organizing and Attending Meetups vs. Conferences Challenges and Strategies for Growing Meetups Virtual and Hybrid Meetups: Impact on Attendance Success Tips for Organizing Meetups Keeping Meetups Simple and Engaging Preventing Organizer Burnout Challenges and Changes in Meetup Cadence Finding and Retaining Meetup Members Communication Tools for Meetup Groups The Importance of In-Person Meetups Advice for Starting or Restarting Meetups Conclusion and Contact Information Resources Drupal.org Events The Drop Times Events Meetup.com Drupal Chattanooga Drupal Users Group Chattanooga Drupal Camp Guests Lee Walker - www.codejourneymen.com mr_scumbag Bo Shipley - simplyshipley Bernardo Martinez - linkedin bernardm28 Hosts Stephen Cross - stephencross John Picozzi - epam.com johnpicozzi JD Leonard - modernbizconsulting.com jdleonard Module of the Week with Martin Anderson-Clutz - mandclu.com mandclu Drupal Core 11.2 Single Directory Components (SDCs) have been a focus of excitement for Drupal's front end developers since they were added to Drupal 10.1 as an experimental module, and merged into 10.3 as a stable feature. With Drupal 11.2, SDCs now have a concept of variants, to allow for different ways of presenting a component's information. Some component frameworks like Storybook have a somewhat different concept of variants, which is really a set of property value presets that are useful for testing. Variants with Drupal SDCs strike me as being analogous to view modes for content types, in that you can have separate template files for each variant, or you can have conditional logic within a single template based on the variant in use. Our own nicxvan, chx, and some others put some significant work into allowing preprocess hooks to be defined as OOP classes, which bring us a significant step closer to not needing .module files anymore. Hooks (and .module files) are Drupalisms, so removing the need for them is a big improvement for Developer Experience, and makes it easier for developers to get started with Drupal In Drupal 11.2 the module installer has been updated to only rebuild the container after several modules have been installed, which significantly speeds up installing multiple modules at once. Drupal 11.2 also brings us a Recipe Unpack composer extension, so when you composer require a recipe, the dependencies get automatically added to your site's composer.json file, so you can apply and then remove the recipe and still have a fully functional site Package Manager is now a hidden module in Drupal core, which is critical for initiative like Automatic Updates and Project Browser, that the community has been working on for years Drupal core now also supports the next-generation AVIF format, with WEBP as a fallback with servers that don't support generating them Of course there are also a variety of dependency updates as well, for CKEDitor, Symfony, composer and more, as well as too many minor improvements and bugfixes to cover in detail here

Ryan Carniato, creator of SolidJS, joins the podcast to reflect on a decade of developing the framework. We dive into the evolution of frontend tooling, the rise of fine-grained reactivity, and why SolidJS continues to challenge virtual DOM conventions. Ryan also shares insights on open source maintenance, web standards, and the future of UI architecture. Links YouTube: https://www.youtube.com/@ryansolid X: https://x.com/ryancarniato Dev.to: https://dev.to/ryansolid SolidJS Website: https://www.solidjs.com Resources A Decade of SolidJS: https://dev.to/this-is-learning/a-decade-of-solidjs-32f4 We want to hear from you! How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend? Let us know by sending an email to our producer, Em, at emily.kochanek@logrocket.com (mailto:emily.kochanek@logrocket.com), or tweet at us at PodRocketPod (https://twitter.com/PodRocketpod). Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understanding where your users are struggling by trying it for free at LogRocket.com. Try LogRocket for free today. (https://logrocket.com/signup/?pdr) Special Guest: Ryan Carniato.