Podcasts about developer experience

————— COACHING —————Vous êtes leader tech ou product face à des défis majeurs ?

Jennifer St Pierre is Senior Vice President of Developer Experience and Transformation at Dell Technologies, where she leads the strategy for how Dell's Infrastructure Solutions Group builds, operates, and evolves software.In this session from DX Annual, Jen argues that the biggest challenge in adopting agentic AI is not the technology itself, but the people transition behind it. Drawing on lessons from earlier shifts like Agile, DevOps, and cloud adoption, she explains why organizations that treat AI as a simple tooling rollout may get compliance, but not commitment.Jen outlines five leadership imperatives for navigating the transition: building a shared understanding of why change is happening, defining a clear future state, clarifying how roles will evolve, creating psychological safety for experimentation, and aligning metrics and organizational structures with new ways of working. Throughout the talk, she emphasizes that while AI may generate code, humans remain responsible for direction, judgment, and meaning.Where to find Jennifer St Pierre: • LinkedIn: https://www.linkedin.com/in/jennifer-st-pierre-4935a81In this episode, we cover:(00:00) Intro(00:13) Why every major technology shift is ultimately a people transition(05:00) AI-generated code and the evolving role of software engineers(07:43) The importance of developing a shared understanding(12:00) Defining a clear future state and how engineering roles will evolve(19:12) How psychological safety enables experimentation and honest feedback(22:41) Why metrics and organizational structure must evolve for the age of AI(25:40) Why leaders must drive AI transformation intentionallyReferenced:• Measuring developer productivity with the DX Core 4• Understand team effectiveness 

————— COACHING —————Vous êtes leader tech ou product face à des défis majeurs ?

In this episode of Elixir Wizards, hosts Charles Suggs and Emma Whamond sit down with Marek Šuppa, creator of the Missing GitHub Status page, a project that reconstructs GitHub's historical uptime data and reveals discrepancies between official status reporting and the platform's actual reliability. Marek tells us about his dev journey from open source contributor at DuckDuckGo to machine learning engineer at Cisco-acquired Slido. Then, we discuss GitHub's evolution from a hosted Git service into a critical developer tool. We cover reliability, transparency, AI-driven platform growth, developer workflows, and the challenges of balancing convenience with resilience. Along the way, we cover alternative platforms, self-hosted solutions, and whether recent outages are changing how developers think about ownership, dependency, and the future of software collaboration. Topics Discussed in this Episode: Why did Mr. Shu create the Missing GitHub Status Page? GitHub's reported uptime versus developer experiences How open source contributions shaped Marek's career The evolution of GitHub from tool to critical infrastructure Centralization risks in modern software development Git's distributed roots and today's platform-centric workflows Developer reactions to GitHub outages Transparency and accountability in status reporting AI's impact on developer platforms and infrastructure demands Microsoft's stewardship of GitHub Forgejo, Codeberg, and alternative Git hosting platforms Self-hosted Git solutions and tradeoffs Network effects and platform lock-in The social side of software collaboration Building resilience into developer workflows What GitHub outages teach us about infrastructure dependency Links Mentioned: The Missing GitHub Status Page https://mrshu.github.io/github-statuses/ Slido https://www.slido.com/ https://duckduckgo.com/ The official GitHub Status Page https://www.githubstatus.com/ Statuspage.iohttps://www.atlassian.com/software/statuspage Zig Leaves GitHub https://ziglang.org/news/migrating-from-github-to-codeberg/ Ghostty Leaves GitHub https://mitchellh.com/writing/ghostty-leaving-github GitLab https://about.gitlab.com/ Codeberg https://codeberg.org/ https://git.kernel.org/ Forgejo Lightweight Self-Hosting https://forgejo.org/ Former GitHub CEO Thomas Dohmke launches Entire https://entire.io/news/former-github-ceo-thomas-dohmke-raises-60-million-seed-round Update on Spain and LALIGA blocks of the internet https://vercel.com/blog/update-on-spain-and-laliga-blocks-of-the-internet

————— COACHING —————Cet épisode vous a donné envie d'en savoir plus sur le coaching ?

Recorded live at Money 20/20 in Las Vegas, Nevada, Eyal is joined by Jess Turner, EVP and Global Head of Open Finance & Developer Experience at Mastercard. Credit cards, and the networks that power them, have been a central part of the global financial system for over 70 years, providing far more than just payments. As money becomes more and more digital, the role these networks play as data brokers and data custodians, is evolving in lockstep, fueled even further by the rise of open banking. Far from being viewed as a threat, card providers have been rapidly evolving to embrace the new opportunities presented by open banking, open finance and open data. Eyal and Jess discuss how the card industry is being impacted by this shift, and how Mastercard is working to firmly position itself as one of the leading trailblazers. Specifically they discuss:How card networks unlock dataThe importance of open standardsRegion-specific considerationsTrust, consent and controlThe legacy of Mastercard

In this episode of Community Pulse, we discuss the challenge DevRel teams face when raising concerns internally. Because they're closely connected to the developer community, they often spot issues before anyone else. Speaking up too often can make them seem overly negative or resistant to change. We explore how to communicate concerns effectively, maintain credibility with stakeholders, and continue advocating for the community without becoming “the person who always pumps the brakes.” Checkouts Wesley Faulkner Work's Not Working - A community for those struggling in the workplace to get real help instead of platitudes. Get suggestions from other people that are dealing with the same struggles that you are facing to get real support. Against Empathy - The book draws on the distinctions between empathy, compassion, and moral decision making. Jason Hand High Agency In 30 Minutes Datadog Community YouTube The State of AI Engineering Report Mary Thengvall Monte Williams - ALEU Leadership Development Project Hail Mary - book is amazing; audiobook narrator (Ray Porter) is phenomenal; and the movie holds up to the book - triple threat! Melissa Appel Re-reading Designing your Life - it uses design thinking, and especially prototyping / experimentation to help you figure out what's next in your professional or personal life Jonan Scheffler Zen Mind, Beginner's Mind - Shinryu Suzuki Drive, Dan Pink: Autonomy, Mastery, Purpose DM me if you're in Berlin, I'll buy you a beer. Enjoy the podcast? Please take a few moments to leave us a review on iTunes and follow us on Spotify, 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. Artwork photo by Nick Nice on UnsplashSpecial Guests: Jonan Scheffler and Melissa Appel.

An airhacks.fm conversation with Arun Gupta (@arungupta) about: learning Basic, Pascal, COBOL and C in college, early Java applets connecting to databases via JDBC, joining Sun Microsystems in March 1999 as an RMI/CORBA test engineer, the Portable Object Adapter and IIOP wire protocol, RMI-IIOP for language interoperability, J2EE 1.2 alpha release, JAX-B and JAX-RS testing, J2EE technologies migrating into Java SE, GlassFish as the open-source reference implementation, growing GlassFish downloads from zero to five million in three years, OSGi modularization in GlassFish V3, single-jar Java EE deployment, the Sun Grid early cloud attempt, the Sun Cloud REST API designed by Tim Bray, Red Hat JBoss technical marketing, recording an early docker screencast at Red Hat, Couchbase and the move to Amazon, principal open source technologist role, making Amazon join CNCF, launching Amazon Corretto with James Gosling at Devoxx Belgium 2019, the corretto name meaning coffee with liquor, Apple Open Source Program Office and the internal Apple openJDK fork used across Apple Music and Siri, Intel VP of Open Ecosystem, joining JetBrains as VP of Developer Experience, the book Fostering Open Source Culture, MineCraft Modding with Forge co-authored with his son who keynoted JavaOne at age 10, Devoxx4Kids in the US with over 200 workshops and 5000 kids taught, the not-invented-here syndrome, the conference program committee bias toward new topics, normative JSR specifications using must, shall and must not as a basis for LLM code generation, TCK and reference implementation model, Quarkus modernization of legacy J2EE applications, AGENTS.md and skill files on top of coding agents, running and weight training for mindfulness. Arun Gupta on twitter: @arungupta

Tester oui, mais par où commencer ? Et quels pièges éviter quand on débute ?Dans cet extrait, Antoine partage les grands principes qui guident ses choix de testing, que ce soit en phase exploratoire ou dans des contextes matures.Il aborde aussi un sujet brûlant : l'arrivée de l'IA dans les pratiques de testing. Automatiser plus, ou tester moins mais mieux ? Sa réponse est sans ambiguïté.Ce que vous allez entendre :Par où commencer quand on n'a jamais fait de testsPourquoi tester, ce n'est pas seulement une histoire de codeLes grands principes qui permettent de garder une stratégie de testing efficaceL'impact de l'IA sur le testing : plus de tests ≠ meilleure qualitéComment garder une approche frugale et pertinente face aux sirènes de l'automatisationRetrouvez Antoine :Sur LinkedIn : https://www.linkedin.com/in/acraske/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.

If your SaaS product delivers genuine value fast, growth takes care of itself. That's the core thesis Sanjay Sarathy has spent 8+ years proving at Cloudinary, where he oversees a self-service business representing nearly a third of the company's revenue across 11,000+ paying customers in 150+ countries — without feet on the ground in most of them.In this episode, Sanjay breaks down what product-led growth actually looks like when it's executed well: not just free trials and clever onboarding flows, but building such a frictionless, valuable experience that developers naturally tell other developers. He shares why Cloudinary invested in technical support before marketing, how they redefined "activation" to mean real value (not just uploading a file), why discoverability is a non-negotiable pillar of their growth strategy, and how they're now rethinking the developer experience for a world where AI agents and LLMs are writing the code.This is a masterclass in developer-led PLG from someone who has lived it at scale.Key Takeaways4:07 — The Growth Levers Have Changed SEO, outbound, and paid are still valid, but word of mouth (especially in developer communities), AEO, and agentic discoverability have become powerful new growth engines — when they're earned as a byproduct of value, not engineered as a primary goal.8:28 — Why PLG Before Enterprise Cloudinary was built by developers for developers. They started with self-service because that's what their founding team would have wanted. Only after PLG proved itself did enterprise customers come knocking — and it was far easier to layer on security, SLAs, and support than to bolt on a product that developers already loved.13:46 — Great Product Isn't Enough Without Distribution Cloudinary is in 150 countries with no boots on the ground in most of them. SEO, developer relations, and a docs site that functions as a discovery engine are what made global reach possible. Distribution and product must go hand-in-hand.15:36 — Discoverability Is a Strategy, Not a Tactic "Discoverability" is a recurring internal theme at Cloudinary — constantly asking how to ensure the right people, in the right context, can find and experience the product's value.16:03 — The Cannibalization Trap Cloudinary made the mistake of launching a new product without considering its impact on existing products — and cannibalized their own business. They now use a two-track product strategy: "mature" products with full go-to-market support, and "invest" products being validated for product-market fit before scaling.19:24 — Invest in Support Before Marketing One of Cloudinary's earliest and most impactful decisions: invest heavily in technical support first. Happy, successful developers become word-of-mouth advocates. That bet paid off across an entire community.21:06 — Developer Experience in the Age of AI Tooling Developer experience today means meeting developers where they work — VS Code, Cursor, Claude, Windsurf. Cloudinary built a VS Code extension and is working to minimize hallucinations by giving LLMs accurate, context-rich instructions for using Cloudinary correctly.24:03 — Redefining Activation Uploading a file to Cloudinary is not activation. Doing something with that file — transforming it, tagging it, delivering it — is activation. Reframing their metric around genuine value changed how they prioritized onboarding.33:25 — The Seven-Day Activation Window Data shows clearly: if users don't activate within the first 7 days, a second surge doesn't come. Most activation happens in the first 4–5 days. This insight shapes everything about how Cloudinary approaches onboarding urgency.27:01 — Speak Use Cases, Not Features "We have automated image optimization" means nothing. "Your images are 40% lighter and you'll save X on bandwidth" means everything. The language of outcomes and use cases is what drives adoption and expansion.36:39 — Pricing Must Communicate Value Cloudinary's self-service pricing has remained largely flat for years while the product has added enormous capability — intentionally improving the value/price ratio over time. They also offer pay-as-you-go flexibility for seasonal businesses.44:28 — The 90-Day PLG Focus: Build Trust For founders building a PLG motion right now, Sanjay's single most important recommendation: engender trust. Do what you say. Follow up when you say you will. Make your product deliver on its promise. Trust is the flywheel.Tweetable Quotes"We never set out to get word of mouth. We set out to create value. Word of mouth was the byproduct." — Sanjay Sarathy"If your product genuinely helps people win, growth becomes a natural byproduct." — Sanjay Sarathy"Distribution is equally as important as the product itself. You can have a great product and go nowhere." — Sanjay Sarathy"Discoverability isn't a campaign. It's a strategy." — Sanjay Sarathy"Uploading a file isn't activation. Doing something valuable with it is." — Sanjay Sarathy"If a developer doesn't activate in the first seven days, don't expect another surge. It won't come." — Sanjay Sarathy"Stop talking about your features. Start talking in the language of your customer's use cases." — Sanjay Sarathy"We're okay with free users who are actively using the product. They pay us back in word of mouth." — Sanjay Sarathy"In a PLG motion, trust is the flywheel. Without it, everything else breaks down." — Sanjay Sarathy"We fell in love with our own capabilities and forgot that customers don't care. Use cases are what drive adoption." — Sanjay SarathySaaS Leadership Lessons1. Build Distribution Like You Build Product Cloudinary reaches 150+ countries without sales reps in most of them — through SEO, developer relations, documentation, and community. Great products disappear without intentional distribution. Your discoverability strategy is a growth strategy.2. Earn Word of Mouth — Don't Engineer It The moment you prioritize getting word of mouth over generating it as a byproduct of genuine value, you've lost the plot. Build something that makes people win, then step back and let them talk. The data will tell you if it's working.3. Start Narrow, Validate, Then Scale Cloudinary's "invest vs. scale" product framework exists because they once cannibalized their own product line by expanding without rigor. Validate product-market fit in a controlled way before committing the full go-to-market machine. Repeatability before scale.4. Redefine Your Activation Metrics Around Real Value Ask yourself: is the action we're measuring actually a moment of value, or just a moment of presence? Cloudinary stopped counting uploads and started counting transformations. The metric you optimize shapes the product you build.5. Invest in Customer Success Before You Think You Need To Cloudinary prioritized technical support ahead of marketing in their early days. Counter-intuitive — and it was exactly right. Successful users become advocates. That investment compounded for years through word of mouth and developer trust.6. Speak the Language Your Customer Thinks In "Automated image optimization via F-Auto" is internal language. "Your images are 40% lighter and your site is faster" is customer language. The translation layer between what your product does and what your customer achieves is where adoption lives or dies. Build that bridge deliberately.Guest Resourcessanjay@cloudinary.comwww.cloudinary.comhttps://www.linkedin.com/in/sanjaysarathy/https://x.com/guffnuffEpisode SponsorThe Futureproof Series - https://www.youtube.com/playlist?list=PLfkXKUPZ5xuOqMPR7_gzGybncTtavyR1NThe Captain's KeysSmall Fish, Big Pond – https://smallfishbigpond.com/ Use the promo code ‘SaaSFuel'Champion Leadership Group – https://championleadership.com/SaaS Fuel ResourcesWebsite - https://championleadership.com/Jeff Mains on LinkedIn - https://www.linkedin.com/in/jeffkmains/Twitter - https://twitter.com/jeffkmainsFacebook - https://www.facebook.com/thesaasguy/Instagram - https://instagram.com/jeffkmains

————— COACHING —————Vous êtes leader tech ou product face à des défis majeurs ?

In Season 15 episode 3, Charles Suggs sits down with Greg Medland, aka “The Elixir Fixer,” to talk about the current state of hiring and the software jobs market in 2026.   Greg shares what he's seeing from both sides of the hiring process as an Elixir-focused recruiter, from shifting company expectations to the growing importance of specialization, communication skills, and real-world product thinking. We discuss how the market has changed since the 2021–2022 hiring boom, why things feel more uncertain today, and how developers are adapting to a slower, more competitive landscape.   The conversation also explores how AI is affecting hiring workflows, résumé quality, technical interviews, and even the rise of fraudulent candidates. Greg explains why human relationships and reputation still matter more than ever, especially in smaller ecosystems like Elixir where community connections carry real weight.   Along the way, we talk about what junior developers are up against, why senior engineers with domain expertise continue to stand out, and what developers can do to position themselves more effectively in today's market. Greg shares practical advice for building a sustainable career, developing a clear professional identity, and navigating a rapidly changing industry.   Topics discussed in this episode: The current state of the Elixir job market Hiring trends and market shifts since 2021–2022 How AI is changing hiring and recruiting workflows Fraudulent candidates and AI-generated résumés Domain expertise vs. generalist engineering skills Product thinking and customer-focused development What companies are looking for in 2026 Junior developer challenges in the current market Why senior specialists remain in demand Networking and relationship-building in tech Open source contributions and visibility in the Elixir community Standing out in a crowded hiring environment Résumé quality and application strategies The role of personal branding for developers Remote work trends and geographic hiring patterns Technical interview expectations and evaluation changes Startup vs. enterprise hiring differences Human connection in an increasingly automated industry Career resilience and long-term positioning Building a sustainable software engineering career   Links mentioned: Socially Responsible Recruitment https://sr2rec.com/en/ Greg's LinkedIn https://www.linkedin.com/in/elixirfixer/ Greg's email address: greg@sr2rec.com

————— COACHING —————Vous êtes leader tech ou product face à des défis majeurs ?

————— COACHING —————Vous êtes leader tech ou product face à des défis majeurs ?

Comment faire basculer une équipe tech entière — dont certains membres réfractaires postaient sur LinkedIn que l'IA était du bullshit — vers l'adoption collective et l'intelligence partagée ?Mathilde Rigabert partage sa méthode pour transformer la résistance en engagement. Pas de forcing, pas d'objectifs imposés. Mais 6 mois de préparation minutieuse, 2 jours intenses en physique, et une approche centrée sur l'humain et le collectif.Résultat : un basculement complet de l'état d'esprit, et des compétences IA qui se partagent naturellement entre collègues.Dans cet extrait, Mathilde partage les étapes qui ont permis cette transformation : de l'expérimentation cadrée avec les early adopters à la mise en place de skills partagées, en passant par l'importance du binômage et de la sécurisation psychologique.————— MATHILDE RIGABERT —————Retrouvez Mathilde sur LinkedIn : https://www.linkedin.com/in/mathildelemee/————— RESSOURCES —————Claude Code (outil d'IA pour développeurs)Skills V2 de ClaudeCursor (IDE avec IA intégrée)Code Rabbit (outil de revue de code assistée par IA)Gemma (modèle IA local)————— 5 ÉTOILES —————Si cet épisode vous a plu, pensez à laisser une note et un commentaire sur Spotify ou Apple Podcast. Ça ne vous coûte rien et ça m'aide beaucoup !————— COACHING —————Vous êtes leader tech ou product face à des défis majeurs ?

En 2009, Hugo rate les entretiens d'Atlassian. Ce raté devient le déclic qui le pousse à devenir freelance. Trois ans plus tard, un tweet change sa trajectoire : il rejoint Vincent Huguet pour créer Malt, une des rares scale-ups françaises à s'imposer à l'échelle européenne.Pendant 12 ans, Hugo traverse toutes les étapes de croissance : de 3 personnes à près de 700, de CTO codeur à leader d'une équipe de 150 personnes. Puis, en 2024, il quitte. Ni pour diriger une autre boîte, ni pour lever des fonds. Mais pour coder à nouveau, créer Writizzy, et défendre la souveraineté numérique européenne.Dans cet épisode, Hugo partage son histoire, sans dorure : comment on lâche un rôle qu'on a construit soi-même, pourquoi l'innovation meurt avec trop de process, et ce que ça change de développer à l'ère de l'IA.————— HUGO LASSIÈGE —————Retrouvez Hugo :Sur sa chaîne YouTube : https://www.youtube.com/@eventuallycodingSur son blog : https://eventuallycoding.comSur LinkedIn : https://www.linkedin.com/in/hugolassiege/————— PARTIE 1/3 : PARCOURS —————(04:24) Les entretiens ratés chez Atlassian : le déclic(17:24) La genèse de Malt : une suite d'opportunités(25:58) Comment Malt passe de 3 à 700 personnes(31:02) Les multiples rôles d'Hugo chez Malt(33:28) L'allergie aux process et au management classique(44:46) Culture d'entreprise vs syndrome de Peter Pan(52:44) Formaliser la culture d'entreprise chez Malt(56:46) Les moments où Hugo ne se sent plus à sa place(1:05:39) L'ambition initiale vs la réalité(1:17:07) 2024 : Hugo quitte son rôle de CTO————— PARTIE 2/3 : AUJOURD'HUI —————(1:26:24) Pourquoi Hugo choisit le solopreneuriat(1:27:16) L'ambition avec Writizzy(1:37:45) Développer un produit à l'ère de l'IA(1:39:27) La mutation du métier de développeur(1:45:15) Fiabiliser le code produit par l'IA————— PARTIE 3/3 : SOUVERAINETÉ —————(2:02:03) C'est quoi la souveraineté numérique ?(2:08:00) Sommes-nous déjà en guerre numérique ?(2:13:17) Les services européens qu'Hugo utilise(2:22:10) Peut-on avoir des GAFAM européens ?(2:24:56) Les médias : le vrai point noir————— RESSOURCES —————Writizzy : plateforme de blogging européenne créée par HugoProton : suite d'outils (email, calendrier, VPN, etc.) en alternative à GoogleBunny.net : alternative européenne à CloudflareCoolify : solution open source d'hébergementScaleway : cloud provider françaisLivre La fin du management (The Future of Management)Technopolitique par Asma MhallaAI Superpowers par Kai-Fu Lee————— 5 ÉTOILES —————Si cet épisode vous a plu, pensez à laisser une note et un commentaire. Ça ne vous coûte rien et ça m'aide beaucoup !————— COACHING —————Vous êtes leader tech ou product face à des défis majeurs ?

Alexander Lichter, DevRel at VoidZero, walks us through Void, a Vite-native deployment platform where your code is your infrastructure. From automatic provisioning of databases and KV storage to Rolldown's massive build speed improvements in Vite 6, Alex explains how Vite Plus handles local tooling while Void handles deployment, and how MCP support lets AI coding agents like Claude scaffold and deploy apps end-to-end with minimal human input. Links Website: https://www.lichter.io X: https://x.com/TheAlexLichter Mastodon: https://hachyderm.io/@manniL Github: https://github.com/manniL YouTube: https://www.youtube.com/@TheAlexLichter Twitch: https://www.twitch.tv/TheAlexLichter LinkedIn: https://www.linkedin.com/in/alexanderlichter Resources Void: https://void.cloud 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 Let us know by sending an email to our producer, Elizabeth, at elizabeth.becz@logrocket.com, or tweet at us at PodRocketPod. Check out our newsletter! https://blog.logrocket.com/the-replay-newsletter/ Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form, 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. ChaptersSpecial Guest: Alexander Lichter.

Développer un produit avec l'IA, ce n'est plus tout à fait le même métier.Hugo Lassiège en fait l'expérience au quotidien : 95% du code de Writizzy est généré par l'IA. Il ne code presque plus. Il spécifie, il relit, il met en place des garde-fous. Et surtout, il se pose des questions qu'il ne se posait pas avant : quelle direction pour mon produit ? Quel problème je cherche vraiment à résoudre ?Dans cet extrait, Hugo partage sa vision sur ce qui change (et ce qui reste) dans le métier de développeur à l'ère de l'IA. On parle aussi des mutations à venir dans les entreprises, de la convergence des rôles, et de ce qu'il faut savoir pour rester pertinent.————— HUGO LASSIÈGE ————— Retrouvez Hugo sur LinkedIn : https://www.linkedin.com/in/hugolassiege/————— RESSOURCES —————Writizzy ClaudeNuxt : framework utilisé par HugoMCP (Model Context Protocol) : protocole pour enrichir les capacités des LLMActivityPub : protocole derrière Mastodon————— 5 ÉTOILES —————Si cet épisode vous a plu, pensez à laisser une note et un commentaire sur Spotify ou Apple Podcast. Ça ne vous coûte rien et ça m'aide beaucoup !————— COACHING —————Vous êtes leader tech ou product face à des défis majeurs ?

L'IA rebat les cartes. Et elle le fait vite. Tellement vite qu'on court tous un peu dans tous les sens, poussés par l'excitation ou, plus souvent, par la peur.Mais courir sans direction, c'est exactement ce qu'on fait quand on laisse nos émotions prendre le volant.Dans cet épisode solo, je partage une approche pour reprendre le contrôle : raisonner par premiers principes.Plutôt que de réagir impulsivement à chaque nouvelle disruption, je vous propose de revenir à ce qui est fondamental pour vous, pour votre équipe, pour votre entreprise. Et de construire à partir de là.————— CHAPITRAGE —————(00:00) Intro + update sur la refonte du podcast(02:15) Retour sur le AI Product Day et le constat troublant(04:08) L'IA : une révolution subie, pas choisie(08:47) Pourquoi on court comme une poule sans tête(11:47) Excitation et peur : les deux émotions qui nous animent(13:14) Comprendre le rôle des émotions avec les neurosciences(15:31) L'excitation face à l'IA : un monde d'opportunités(16:20) La peur face à l'IA : quand l'écart se réduit(17:14) L'incertitude génère la peur, et la peur paralyse(19:26) Approche impulsive vs approche intentionnelle(21:35) Introduction au concept de premier principe (First Principles)(22:41) Raisonnement par analogie vs raisonnement par premier principe(23:07) Framework pour appliquer le raisonnement par premier principe(24:32) Exemple personnel : ma décision de me lancer dans le coaching(28:02) Contre-exemple : l'entreprise sans vision qui s'éparpille(29:05) Comment appliquer ce raisonnement face à l'IA(30:33) En tant qu'individu : revenir à ses valeurs et son pourquoi(31:20) Récap et conclusion————— RESSOURCES —————Paul Valéry (auteur mentionné)Concept des First Principles (Aristote)AI Product Day (conférence)————— 5 ÉTOILES —————Si cet épisode vous a plu, pensez à laisser une note et un commentaire sur Spotify ou Apple Podcast. Ça ne vous coûte rien et ça m'aide beaucoup !————— COACHING —————Vous êtes leader tech ou product face à des défis majeurs ?

Prompted by some content on “How to Succeed in DevRel” that was clearly AI produced, Jason, PJ, and Wesley go down the rabbit hole of how developers are affected by AI generated content, what the real value of AI content is to developers, and a few points on what exactly the value is of creating content for AI instead of human developers. Checkouts Wesley Faulkner Twilight Zone episode PJ Hagerty Asimov's I, Robot (not the movie) Jason Hand J's hackathon project Enjoy the podcast? Please take a few moments to leave us a review on iTunes and follow us on Spotify, 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. Artwork by Nahrizul Kadri on Unsplash

In this episode, Sammy Isaiah, co-founder of Discount Kit, shares insights into Shopify app development, the evolution of Shopify POS, and the innovative Discount Kit Live platform. Discover how these tools are transforming e-commerce experiences for developers and merchants alike.Keep up with the latest in Shopify Development NewsSubscribe to the Liquid Weekly Newsletter -https://liquidweekly.com/Support HeroesFor more information about the sponsor of this episode, Support Heroes, check out: http://thesupportheroes.comTimestamps00:00 Discount Kit Live: Enhancing User Experience06:29 The Role of Agencies and Developers in Shopify09:37 Technical Insights on Discount Management12:15 Future Prospects and Community Engagement15:25 Building the Foundation for User Experience18:36 Innovations in Cart Functionality21:52 Data Management Challenges22:58 Exploring Shopify Functions27:52 Transitioning to Point of Sale (POS) Development45:15 The Birth of Pause Cues47:33 Exploring the Functionality of Pause Cues50:26 The Impact of POS on Merchants52:25 The Developer Experience with Shopify POS56:24 Updates and Changes in Discount Kit59:25 Changelog Highlights and Community Feedback01:04:17 Picks of the Week and Closing ThoughtsFind Sammy OnlineTwitter - https://x.com/sammyIsseyeghLinkedIn - https://linkedin.com/in/sammyIsseyeghShopify App Store - https://apps.shopify.com/discount-kitDev Changelog- Legacy customer accounts are now deprecated - https://shopify.dev/changelog/legacy-customer-accounts-are-deprecated- New APIs to read and write shipping options in delivery profile - https://shopify.dev/changelog/new-apis-to-read-and-write-shipping-options-in-delivery-profile- Manage dev previews on your dev store without leaving admin - https://shopify.dev/changelog/manage-dev-previews-on-your-dev-store-without-leaving-admin- JSON metafield values limited to 128KB - https://shopify.dev/changelog/reduced-metafield-value-sizes- Shopify Dev Forums discussion: https://community.shopify.dev/t/metafield-values-limited-to-16kb/29775/39 - Bare query strings no longer bust the cache for assets - https://shopify.dev/changelog/bare-query-strings-no-longer-bust-the-cache-for-assets- Enhanced discounts support in the Shopify Functions Cart - https://shopify.dev/changelog/enhanced-discounts-support-in-the-shopify-functions-cart- New analyticsQueryable capability for Metafield Definitions - https://shopify.dev/changelog/new-analyticsqueryable-capability-for-metafield-definitions Picks of the WeekTaylor - Resend https://resend.com/Karl - Ghostty - https://ghostty.org/Sammy - Greptile - https://www.greptile.com/ResourcesShopify Developer Documentation -https://shopify.dev/Discount Kit App - https://apps.shopify.com/discount-kitShopify POS Development Resources - https://shopify.dev/docs/posShopify Functions GitHub Repository - https://github.com/Shopify/shopify-function-templateShopify WebAssembly API - https://shopify.dev/api/wasmReptile AI Code Review Tool - https://reptile.ai/Ghosty Terminal Emulator - https://ghosty.app/Key TopicsShopify app development evolutionIntroduction of Discount Kit Live platformShopify POS advancements and developer toolsImpact of Shopify updates on merchants and developersStrategies for building scalable Shopify appsSEO KeywordsShopify, Shopify POS, Discount Kit, Shopify apps, e-commerce, app development, Shopify functions, POS development, discount management, Shopify updates

This interview was recorded at GOTO Copenhagen 2025.https://gotocph.comAbby Bangser - Platform Engineering Insights from Syntasso delivering KratixAdrian Mouat - Developer Relations at Chainguard & Author of 'Using Docker'Holly Cummins - JavaOne Rock Star. Building Quarkus to Make the Cloud CloudierRESOURCESAbbyhttps://bsky.app/profile/abangser.bsky.socialhttps://twitter.com/a_bangserhttps://github.com/abangserhttps://www.linkedin.com/in/abbybangserhttps://www.syntasso.io/members-area/abby/profileAdrianhttps://bsky.app/profile/adrianmouat.comhttps://twitter.com/adrianmouathttps://github.com/amouathttps://linkedin.com/in/adrianmouathttp://www.adrianmouat.comHollyhttps://hollycummins.comhttps://hollycummins.com/type/bloghttps://bsky.app/profile/hollycummins.comhttps://hachyderm.io/@holly_cumminshttps://twitter.com/holly_cumminshttps://github.com/holly-cumminshttps://linkedin.com/in/holly-k-cumminsRECOMMENDED BOOKSAdrian Mouat • Using Docker • https://amzn.to/3PEYIJLLiz Rice • Container Security • https://amzn.to/3oU4iJeLiz Rice • Kubernetes Security • https://www.oreilly.com/library/view/kubernetes-security/9781492039075Anne Currie, Sarah Hsu, & Sara Bergman • Building Green Software • https://amzn.to/3UjSClvKief Morris • Infrastructure as Code • https://amzn.to/4e6EBQcBlueskyInstagramLinkedInFacebookCHANNEL MEMBERSHIP BONUSJoin this channel to get early access to videos & other perks:https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/joinLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

At Meta, even seemingly simple engineering tasks—like updating an API—become monumental undertakings when you're dealing with millions of lines of code and thousands of engineers, especially if the changes are security-related. In today's episode, Pascal talks to Alex and Tanu about the challenges and learnings from the journey of making Meta's mobile frameworks more secure at a scale few companies ever experience. Tune in to this episode and join us as we explore the compelling crossroads of security, automation, and AI within mobile development. Got feedback? Send it to us on Threads (https://threads.net/@metatechpod), Instagram (https://instagram.com/metatechpod) and don't forget to follow our host Pascal (https://mastodon.social/@passy, https://threads.net/@passy_). Fancy working with us? Check out https://www.metacareers.com/. Links How AI Is Transforming the Adoption of Secure-by-Default Mobile Frameworks - https://engineering.fb.com/2025/12/15/android/how-ai-transforming-secure-by-default-mobile-frameworks-adoption/  RCCLX: Innovating GPU Communications on AMD Platforms - https://engineering.fb.com/2026/02/24/data-center-engineering/rrcclx-innovating-gpu-communications-amd-platforms-meta/  The Death of Traditional Testing: Agentic Development Broke a 50-Year-Old Field, JiTTesting Can Revive It - https://engineering.fb.com/2026/02/11/developer-tools/the-death-of-traditional-testing-agentic-development-jit-testing-revival/  Timestamps Intro & News 0:06 Meet the Product Security Team 2:07 Understanding the Intent System 4:13 Security Challenges in Android's Intent System 6:44 Proposed Solutions for Intent Security 9:39 Meta's Unique Challenges at Scale 12:34 Implementing a Secure Link Launcher Framework 15:32 Leveraging AI for Contextual Understanding 17:55 Navigating AI-Driven Code Modifications 20:47 Developer Experience with AI Code Mods 21:49 Validation Challenges in AI Code Generation 25:37 Evolution of AI in Code Modifications 29:29 Identifying AI's Strengths in Security 36:20 Future Directions in AI and Framework Development 42:58 Outro 46:58  

In this episode of Book Overflow, Carter and Nathan discuss Frictionless by Nicole Forsgren and Abi Noda!Join the Book Overflow Discord here! https://discord.gg/ZwS2fqW7ZZ -- Want to talk with Carter or Nathan? Book a coaching session! ------------------------------------------------------------Carterhttps://www.joinleland.com/coach/carter-m-1Nathanhttps://www.joinleland.com/coach/nathan-t-2-- Books Mentioned in this Episode --Note: As an Amazon Associate, we earn from qualifying purchases.----------------------------------------------------------Frictionless by Nicole Forsgren and Abi Nodahttps://amzn.to/40l1Pfw---------------- 00:00 Intro04:57 About the Book and Authors08:24 Initial Thoughts on Frictionless13:02 What is Developer Experience20:33 AI Agents and Code Safety35:07 The DevX Framework40:47 Making the Business Case for DevX51:35 The RICE Framework1:01:51 Final ThoughtsSpotify: https://open.spotify.com/show/5kj6DLCEWR5nHShlSYJI5LApple Podcasts: https://podcasts.apple.com/us/podcast/book-overflow/id1745257325X: https://x.com/bookoverflowpodCarter on X: https://x.com/cartermorganNathan's Functionally Imperative: www.functionallyimperative.com----------------Book Overflow is a podcast for software engineers, by software engineers dedicated to improving our craft by reading the best technical books in the world. Join Carter Morgan and Nathan Toups as they read and discuss a new technical book each week!The full book schedule and links to every major podcast player can be found at https://www.bookoverflow.io

Depuis plus de deux ans, Katia Gil Guzman occupe un poste hautement sensible chez OpenAI. Au sein de l'équipe « Developer Experience », elle aide les développeurs dans l'appropriation des modèles et produits du groupe, de l'API historique aux agents de code comme Codex. Son rôle : faire le lien entre la recherche, les équipes produit et la communauté technique mondiale, afin de transformer des percées scientifiques en outils réellement exploitables.Ingénieure de formation, elle a débuté sa carrière chez Microsoft comme software engineer, où elle découvre déjà des fonctions d'« évangélisation » technologique. Elle cofonde ensuite une start-up dont elle devient CTO, avant de rejoindre Stripe, en France, comme solution architect. Chez OpenAI, elle accompagne la montée en puissance des agents capables d'écrire, corriger et tester du code de façon autonome. Elle décrit l'importante mutation en cours du métier de développeur qui devient de plus en plus chef d'orchestre d'équipes d'IA, davantage stratège que simple exécutant. Selon elle, la valeur se déplace à présent vers la capacité à penser l'architecture et à formuler les bonnes instructions. Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.

Russ Miles joins the show to unpack why developer platforms fail and how to rethink platform engineering through the lens of flow of value rather than factory-style developer productivity metaphors. Russ explains why every organization already has an internal developer platform, and why treating it as platform as a product changes everything. The conversation explores cognitive load and cognitive burden, how to design around strong feedback loops, and why the OODA loop mindset helps teams make better decisions closer to development time. They discuss the risks of overloading pipelines and CI/CD systems, the tension between shipping fast and handling security vulnerabilities in a regulated environment, and how to “shift left” without simply dumping responsibility onto developers. Drawing on lessons from Rod Johnson, the Spring Framework, TDD, and modern software engineering as described by Dave Farley, Russ reframes platforms as systems that support experimentation through the scientific method. The episode also touches on AI assisted coding, developer focus, and how thoughtful developer experience and DX surveys can prevent burnout while improving value delivery. Links Website: https://www.russmiles.com Substack: https://russmiles.substack.com X: https://x.com/russmiles Resources Talk: https://www.russmiles.com/platform-engineering-failure-keynote Substack article: https://russmiles.substack.com/p/developer-platform-devrel-listen 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 Let us know by sending an email to our producer, Elizabeth, at elizabeth.becz@logrocket.com, or tweet at us at PodRocketPod. Check out our newsletter! https://blog.logrocket.com/the-replay-newsletter/ Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form, 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. Chapters 00:00 What Is a Developer Platform 03:00 You Already Have a Platform 08:00 Cognitive Load vs Cognitive Burden 12:00 Feedback Loops and TDD 18:00 Pipelines, Security and OODA Loops 26:00 The Factory Metaphor Problem 31:00 Modern Software Engineering and Value Delivery 40:00 Avoiding Burnout Through Better DX 46:00 The Software Enchiridion and Final Thoughts

Bitcoin Core doesn't stand still even if consensus rules don't change. In this episode, Stéphan (Core Developer at Brink) explains how the Kernel and multiprocess projects are reshaping Bitcoin Core for long-term reliability. From modular validation logic to safer development workflows, this conversation shows why maintenance work matters. Hosted by Shinobi of Bitcoin Magazine.#BitcoinCore #BitcoinDevelopment #BitcoinKernel ⭐️⚔: SIGN UP WITH DUELBITS TODAY FOR A CHANCE TO WIN UP TO 2 BTC:

What are ways to improve how you're using GitHub? How can you collaborate more effectively and improve your technical writing? This week on the show, Adam Johnson is back to talk about his new book, "Boost Your GitHub DX: Tame the Octocat and Elevate Your Productivity".

Developer productivity is often framed as a tooling initiative or a morale issue. At scale, it's a more complex socio-technical systems challenge that spans engineering foundations, leadership alignment, organizational structure, and culture.In this episode, Laura Tacho sits down with Uma Namasivayam, Senior Director, Engineering Productivity at Dropbox, to discuss how the company approaches developer experience across an organization of nearly 1,000 engineers. Uma explains why productivity must be treated as a business problem, how executive alignment enables sustained progress, and what it means to run developer experience like a product.The conversation also explores the intersection of AI and developer experience. Uma shares how Dropbox prepared its engineering systems to support AI adoption, why daily AI use depends more on habits than access, and how the company evaluates build-versus-buy decisions as AI tools struggle to scale in large environments.The episode concludes with a candid discussion of the open questions facing engineering leaders today: how to understand where AI-driven capacity actually goes, and how to connect improvements in developer experience to meaningful business outcomes in 2026.Where to find Uma Namasivayam:• LinkedIn: https://www.linkedin.com/in/unamasivayamWhere 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:45) Dropbox's engineering org(01:59) Why developer productivity is a business problem(04:08) The role of executive sponsorship in developer productivity(06:02) How DX's Core Four framework created a shared language(08:13) Treating developer experience as a product(11:30) How Dropbox prioritizes developer experience work(14:20) The challenge of tying developer experience to business outcomes(16:38) How AI and developer experience intersect at Dropbox(18:35) The prerequisites for AI adoption to accelerate work(20:26) How Dropbox encourages daily AI use(23:12) AI use beyond code completion(25:00) Managing AI tool demand at scale(27:56) Early results from Dropbox's AI efforts(30:05) Progress on developer experience at Dropbox(32:55) Advice for organizations investing in developer experience(34:25) Capacity tradeoffs for developer experience(35:59) The unanswered questions around AI and capacity in 2026Referenced:• DX Core 4 Productivity Framework• Dropbox.com

Rich Harris joins the podcast to discuss his talk, fine-grained everything, exploring fine-grained reactivity, frontend performance, and the real costs of React Server Components and RSC payloads. Rich explains how Svelte and SvelteKit approach co-located data fetching, remote functions, and RPC to reduce server-side rendering costs, improve developer experience, and avoid unnecessary performance overhead on mobile networks. The conversation dives into async rendering, parallel async data fetching, type safety with schema validation, and why async-first frameworks may define the future of JavaScript frameworks and web performance. Links X: https://x.com/Rich_Harris Github: https://github.com/rich-harris Bluesky: https://bsky.app/profile/rich-harris.dev Resources Modern front-end frameworks like Svelte are astonishingly fast at rendering, thanks to techniques such as signal-based fine-grained reactivity. But there's more to performance than updating the screen at 60 frames per second. In this talk, we'll learn about new approaches that help you build fast, reliable, data-efficient apps. Slides: https://fine-grained-everything.vercel.app/1-1 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 Let us know by sending an email to our producer, Elizabeth, at elizabeth.becz@logrocket.com, or tweet at us at PodRocketPod. Check out our newsletter! https://blog.logrocket.com/the-replay-newsletter/ Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form, 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. ChaptersSpecial Guest: Rich Harris.

How do you turn a developer-first product into a growth engine without losing trust, clarity, or focus along the way? In this episode of Tech Talks Daily, I'm joined by Sanjay Sarathy, VP of Developer Experience and Self Service at Cloudinary, for a grounded and thoughtful conversation about product-led growth when developers sit at the center of the story. Sanjay operates at a rare intersection. He leads Cloudinary's high-volume self-service motion while also caring for the developer community that fuels adoption, advocacy, and long-term loyalty. That dual perspective, part business, part builder, shapes everything we discuss. Our conversation picks up on a theme I have been exploring across recent episodes. When technical work is explained clearly, whether that is security, performance, or reliability, it stops being background noise and starts supporting growth. Sanjay shares how Cloudinary approached this from day one, starting with founders who were developers themselves and carried a deep respect for developer trust into the company's DNA. Documentation that reflects reality, platforms that behave exactly as promised, and support that shows up early rather than as an afterthought all play a part. What stood out to me was how early Cloudinary invested in technical support, even before many traditional growth motions were in place. That decision shaped a self-service experience that still feels human at scale. With thousands of developer sign-ups every day and millions of developers using the platform, Sanjay explains how trust compounds into referrals, word of mouth, and sustained adoption. We also dig into developer advocacy and why community is rarely a single thing. Developers gather around frameworks, tools, workflows, and shared problems, and Cloudinary has learned to meet them where they already are rather than forcing them into a single branded space. From React and Next.js users to enterprise advisory boards, feedback loops become part of the product itself. As AI reshapes how software is built and developer tools become more crowded, Sanjay offers a clear-eyed view on what separates companies that grow steadily from those that burn bright and stall. Profitability, experimentation with intent, and the discipline to double down on what works all feature heavily in his thinking. It is a conversation rooted in experience rather than theory. If you care about product-led growth, developer trust, or building platforms that scale without losing their soul, this episode offers plenty to think about. As always, I would love to hear your perspective too. How do you see developer communities shaping the next phase of product growth, and where do you think companies still get it wrong?

In this episode of PodRocket, Daniel Thompson--Yvetot joins us to break down what's new in Tauri 2.0 and how developers are using the Tauri framework to build desktop and mobile apps with Rust and JavaScript. We discuss how Tauri lets developers use frameworks like React, Vue, and Angular for the UI while handling heavy logic in Rust, resulting in smaller app binaries and better performance than Electron alternatives. The conversation covers Create Tauri App for faster onboarding, the new plugin system for controlling file system and OS access, and how Tauri improves app security by reducing attack surfaces. They also dive into mobile app development, differences between system WebViews, experiments with Chromium Embedded Framework, and why cross platform apps still need platform-specific thinking. Daniel also shares what's coming next for Tauri, including flexibility in webviews, accessibility tooling, compliance requirements in Europe, and the roadmap toward Tauri 3.0. Links Tauri: https://v2.tauri.app LinkedIn: https://www.linkedin.com/in/denjell 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, Elizabeth, at elizabeth.becz@logrocket.com (mailto:elizabeth.becz@logrocket.com), or tweet at us at PodRocketPod (https://twitter.com/PodRocketpod). Check out our newsletter (https://blog.logrocket.com/the-replay-newsletter/)! https://blog.logrocket.com/the-replay-newsletter/ 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) Chapters Special Guest: Daniel Thompson-Yvetot.

Greg Foster, Co-founder and CTO of Graphite (recently acquired by Cursor), joins the podcast to discuss the massive shift occurring in software engineering: the move from maximizing "Inner Loop" speed (writing code) to solving "Outer Loop" bottlenecks (reviewing, testing, merging). With AI generating code faster than humans can review it, the traditional Pull Request model is under pressure. Greg explains how "Stacked PRs" and agentic review workflows are essential for high-performing teams, and why he believes the role of the software engineer is evolving into an "architect of agents." We also cover the strategic rationale behind the Graphite/Cursor merger, the controversial "PRs per engineer" metric, and why he predicts that by 2029, manual code writing will be near zero—but demand for engineers will be higher than ever.

Modern software development is evolving rapidly. New tools, processes, and AI-powered systems are reshaping how teams collaborate and how engineers find satisfaction in their craft. At the same time, developer experience has become a critical function for helping organizations balance agility, security, and scale while maintaining the creativity and flow that make top tier engineering The post Developer Experience at Capital One with Catherine McGarvey appeared first on Software Engineering Daily.

Modern software development is evolving rapidly. New tools, processes, and AI-powered systems are reshaping how teams collaborate and how engineers find satisfaction in their craft. At the same time, developer experience has become a critical function for helping organizations balance agility, security, and scale while maintaining the creativity and flow that make top tier engineering The post Developer Experience at Capital One with Catherine McGarvey appeared first on Software Engineering Daily.

Paul sits down with Mark Techson to break down Angular v21. They explore how Angular signals power new features like Angular signal forms, improve scalability, and simplify state management. The conversation dives deep into Angular AI tooling, including the Angular MCP server, Angular AI tutor, and the Angular Gemini CLI extension, explaining how Angular is adapting to modern AI-first developer workflows. Mark also shares how Angular Aria introduces Angular headless components with built-in Angular accessibility, reshaping UX collaboration. The episode wraps with updates on using Vitest with Angular, and performance features like Angular defer syntax and Angular incremental hydration. Links Blog: https://marktechson.com LinkedIn: https://www.linkedin.com/in/marktechson YouTube: https://www.youtube.com/@marktechson X: https://x.com/marktechson Github: https://github.com/MarkTechson Resources Announcing Angular v21: https://blog.angular.dev/announcing-angular-v21-57946c34f14b Angular v21 video announcement: https://www.youtube.com/watch?v=DDAHORVzQ5g 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, Elizabeth, at elizabeth.becz@logrocket.com (mailto:elizabeth.becz@logrocket.com), or tweet at us at PodRocketPod (https://twitter.com/PodRocketpod). Check out our newsletter (https://blog.logrocket.com/the-replay-newsletter/)! https://blog.logrocket.com/the-replay-newsletter/ 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) Chapters 00:00:00 – Introduction & What's New in Angular v21 00:01:00 – Angular Release Cadence & Why v21 Matters 00:02:45 – Who Angular v21 Is For: Scaling Teams & Apps 00:04:00 – AI in Modern Angular Workflows 00:05:00 – Context, Memory, and AI Tooling Strategy 00:07:30 – Web CodeGen Score & Evidence-Based Best Practices 00:08:50 – Introducing Signal Forms 00:11:00 – Client vs Server Validation with Signals 00:12:00 – Migration Strategy for Signal Forms 00:13:00 – Signals vs Observables: When to Use Each 00:15:00 – Rethinking UX with Angular Aria 00:17:00 – Headless Components & Design Systems 00:19:30 – Styling, AI, and Design Collaboration 00:22:00 – Testing in Angular v21 & Vitest 00:24:00 – Why Vitest Took Time to Land 00:26:00 – Developer Experience & Framework Fatigue 00:29:00 – Choosing Frameworks in 2025 00:31:00 – AI Tutors, MCP Servers & CLI Tooling 00:34:00 – Deferred Loading & Incremental Hydration 00:35:00 – Where to Learn More & Closing Remarks

In this year-end episode, we're reflecting on our 2025 DevRel conversations and the themes that defined the year. We revisit key insights from our guests, look at how the DevRel landscape continued to evolve, and call out the lessons that showed up again and again across our episodes. It's also a moment to thank our guests and listeners who made the show possible. Whether you joined us for one episode or all of them, this wrap-up looks back on where DevRel has been in 2025 and ahead to what's coming next. 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. Artwork by BoliviaInteligente on Unsplash.

As AI adoption accelerates across the software industry, engineering leaders are increasingly focused on a harder question: how to understand whether these tools are actually improving developer experience and organizational outcomes.In this year-end episode of the Engineering Enablement podcast, host Laura Tacho is joined by Brian Houck from Microsoft, Collin Green and Ciera Jaspan from Google, and Eirini Kalliamvakou from GitHub to examine what 2025 research reveals about AI impact in engineering teams. The panel discusses why measuring AI's effectiveness is inherently complex, why familiar metrics like lines of code continue to resurface despite their limitations, and how multidimensional frameworks such as SPACE and DORA provide a more accurate view of developer productivity.The conversation also looks ahead to 2026, exploring how AI is beginning to reshape the role of the developer, how junior engineers' skill sets may evolve, where agentic workflows are emerging, and why some widely shared AI studies were misunderstood. Together, the panel offers a grounded perspective on moving beyond hype toward more thoughtful, evidence-based AI adoption.Where to find Brian Houck:• LinkedIn: https://www.linkedin.com/in/brianhouck/ • Website: https://www.microsoft.com/en-us/research/people/bhouck/ Where to find Collin Green: • LinkedIn: https://www.linkedin.com/in/collin-green-97720378 • Website: https://research.google/people/107023Where to find Ciera Jaspan: • LinkedIn: https://www.linkedin.com/in/ciera • Website: https://research.google/people/cierajaspan/Where to find Eirini Kalliamvakou: • LinkedIn: https://www.linkedin.com/in/eirini-kalliamvakou-1016865/• X: https://x.com/irina_kAl • Website: https://www.microsoft.com/en-us/research/people/eikalliWhere 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(02:35) Introducing the panel and the focus of the discussion(04:43) Why measuring AI's impact is such a hard problem(05:30) How Microsoft approaches AI impact measurement(06:40) How Google thinks about measuring AI impact(07:28) GitHub's perspective on measurement and insights from the DORA report(10:35) Why lines of code is a misleading metric(14:27) The limitations of measuring the percentage of code generated by AI(18:24) GitHub's research on how AI is shaping the identity of the developer(21:39) How AI may change junior engineers' skill sets(24:42) Google's research on using AI and creativity (26:24) High-leverage AI use cases that improve developer experience(32:38) Open research questions for AI and developer productivity in 2026(35:33) How leading organizations approach change and agentic workflows(38:02) Why the METR paper resonated and how it was misunderstoodReferenced:• Measuring AI code assistants and agents• Kiro• Claude Code - AI coding agent for terminal & IDE• SPACE framework: a quick primer• DORA | State of AI-assisted Software Development 2025• Martin Fowler - by Gergely Orosz - The Pragmatic Engineer• Seamful AI for Creative Software Engineering: Use in Software Development Workflows | IEEE Journals & Magazine | IEEE Xplore• AI Where It Matters: Where, Why, and How Developers Want AI Support in Daily Work - Microsoft Research• Unpacking METR's findings: Does AI slow developers down?• DX Annual 2026

What does it really mean to support developers in a world where the tools are getting smarter, the expectations are higher, and the human side of technology is easier to forget? In this episode of Tech Talks Daily, I sit down with Frédéric Harper, Senior Developer Relations Manager at TinyMCE, for a thoughtful conversation about what it takes to serve developer communities with credibility, empathy, and long-term intent. With more than twenty years in the tech industry, Fred's career spans hands-on web development, open source advocacy, and senior DevRel roles at companies including Microsoft, Mozilla, Fitbit, and npm. That journey gives him a rare perspective on how developer needs have evolved, and where companies still get it wrong. We explore how starting out as a full-time developer shaped Fred's approach to advocacy, grounding his work in real-world frustration rather than abstract messaging. He reflects on earning trust during challenging periods, including advocating for open source during an era when some communities viewed large tech companies with deep skepticism. Along the way, Fred shares how studying Buddhist philosophy has influenced how he shows up for developers today, helping him keep ego in check and focus on service rather than status. The conversation also lifts the curtain on rich text editing, a capability most users take for granted but one that hides deep technical complexity. Fred explains why building a modern editing experience involves far more than formatting text, touching on collaboration, accessibility, security, and the growing expectations around AI-assisted workflows. It is a reminder that some of the most familiar parts of the web are also among the hardest to build well. We then turn to developer relations itself, a role that is often misunderstood or measured through the wrong lens. Fred shares why DevRel should never be treated as a short-term sales function, how trust and community take time, and why authenticity matters more than volume. From open source responsibility to personal branding for developers, including lessons from his book published with Apress, Fred offers grounded advice on visibility, communication, and staying human in an increasingly automated industry. As the episode closes, we reflect on burnout, boundaries, and inclusion, and why healthier communities lead to better products. For anyone building developer tools, managing technical communities, or trying to grow a career without losing themselves in the process, this conversation leaves a simple question hanging in the air: how do we build technology that supports people without forgetting the people behind the code? Useful Links Connect with Frédéric Harper Learn More About TinyMCE Tech Talks Daily is sponsored by Denodo

How much value do your developers actually get to deliver in a typical week, and how much of their time is quietly lost to meetings, context hunting, and process drag? I'm joined by Phil Heijkoop, Global Practice Head of Developer Experience at Valiantys, for a conversation that cuts through the hype surrounding AI and asks a harder question about why so many engineering teams still struggle to see meaningful returns.  Phil argues that most organizations are only unlocking a small fraction of a developer's true contribution, not because of a lack of talent, but because process drag slowly squeezes out deep, focused work. AI, he explains, does not fix this by default. Without the right foundations in place, it simply accelerates the wrong work at scale. We explore the long shadow cast by the "move fast and break things" mindset and why that philosophy becomes risky inside regulated, enterprise environments where resilience and trust matter more than speed alone. Phil shares what he sees when organizations chase shiny new tooling while ignoring technical debt, unclear standards, and fragile workflows.  From protecting uninterrupted time for deep work to automating manual friction points and setting shared guardrails, he outlines how teams can realistically unlock three to five times more output before AI even enters the picture. Only then, he says, does AI act as a multiplier rather than a source of chaos. The conversation also digs into developer experience as a business lever, not a perk, and why leadership clarity, cultural trust, and consistent standards matter as much as tooling choices. We discuss the growing risks in the software supply chain, the sustainability of open source dependencies, and what recent high-profile retirements signal for enterprise teams that depend on them.  If AI is accelerating your organization in the wrong direction, what foundational changes would you need to make today to ensure it amplifies value instead of friction, and how honest are you willing to be about what is really slowing your teams down? Useful Links Connect with Phil on LinkedIn Learn more about Phil's work Valiantys Website Tech Talks Daily is sponsored by Denodo  

In this episode, Matt is joined by Laura Tacho, CTO at DX — one of the leading voices in developer experience research and tooling. Together, they unpack how AI is really affecting software development teams, why developer experience has a “marketing problem,” and why organizational friction — not technology — is the biggest productivity killer.If you've been wondering whether AI is living up to the hype in engineering teams, this conversation will give you the data, the reality, and the leadership takeaways you can act on today.Key Discussion Points[00:48] – What “Developer Experience” Really Means[02:55] – The Real Sources of Developer Friction[03:44] – Core Developer Experience Problems (Pre- and Post-AI)[05:46] – Clarity as a Competitive Advantage[07:25] – The Mistake of “Shit Shielding”[08:18] – How AI Raises the Stakes for Product Thinking[10:00] – The 10x Developer Myth's Real Origin[11:30] – Measuring Developer Experience with the DX Index[14:00] – The Role of Leadership in Removing FrictionResources & Links DX – Research and tools for improving developer experience: https://getdx.com/Developer Experience Index https://getdx.com/dxi-reportingSubscribe to the Product Driven Newsletter: https://productdriven.com/newsletterWhat Smart CTOs Are Doing Differently With Offshore Teams in 2025: https://hirefullscale.com/offshore-hiring-guide

Subscriptions aren't enough anymore. We dig into why the next wave of software winners are building full commerce platforms where payments are invisible to users yet central to growth. With NMI's CMO Peter Galvin and Product Director of Developer Experience, Luis Peña, we unpack how vertical SaaS turns checkout into a native, on-brand experience that drives revenue, cuts churn, and opens the door to embedded finance.We start with the big shift: horizontal tools are giving way to vertical platforms that automate every workflow and own the moment of payment. From dentist offices to gyms and home services, merchants want one system that books, bills, and gets them paid. Peter explains how integrated payments changes the business model - subscription fees plus payments monetization and new fintech lines like working capital - while strengthening loyalty through a consistent, secure merchant and consumer experience.Luis takes us into the build. He shares a practical roadmap for developer-friendly adoption: onboard merchants within your app, collect card data with tokenization and design for webhooks, and exception paths from day one. We talk sandboxes, test suites that simulate real failure modes, and AI-friendly docs that make it easier for modern teams to ship quickly without cutting corners. Then we zoom out to the data advantage - interchange optimization, card mix insights, network tokenization, and benchmarking that inform pricing, conversion, and cross-sell strategies.The takeaway is simple: treat payments as a growth engine, not a bolt-on. When software controls the workflow and the commerce flow, the product becomes stickier, the economics improve, and customers stop thinking about payments at all.

AI engineering tools are evolving fast. New coding assistants, debugging agents, and automation platforms emerge every month. Engineering leaders want to take advantage of these innovations while avoiding costly experiments that create more distraction than impact.In this episode of the Engineering Enablement podcast, host Laura Tacho and Abi Noda outline a practical model for evaluating AI tools with data. They explain how to shortlist tools by use case, run trials that mirror real development work, select representative cohorts, and ensure consistent support and enablement. They also highlight why baselines and frameworks like DX's Core 4 and the AI Measurement Framework are essential for measuring impact.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-courseWhere to find Abi Noda:• LinkedIn: https://www.linkedin.com/in/abinoda  • Substack: ​​https://substack.com/@abinoda  In this episode, we cover:(00:00) Intro: Running a data-driven evaluation of AI tools(02:36) Challenges in evaluating AI tools(06:11) How often to reevaluate AI tools(07:02) Incumbent tools vs challenger tools(07:40) Why organizations need disciplined evaluations before rolling out tools(09:28) How to size your tool shortlist based on developer population(12:44) Why tools must be grouped by use case and interaction mode(13:30) How to structure trials around a clear research question(16:45) Best practices for selecting trial participants(19:22) Why support and enablement are essential for success(21:10) How to choose the right duration for evaluations(22:52) How to measure impact using baselines and the AI Measurement Framework(25:28) Key considerations for an AI tool evaluation(28:52) Q&A: How reliable is self-reported time savings from AI tools?(32:22) Q&A: Why not adopt multiple tools instead of choosing just one?(33:27) Q&A: Tool performance differences and avoiding vendor lock-inReferenced:Measuring AI code assistants and agentsQCon conferencesDX Core 4 engineering metricsDORA's 2025 research on the impact of AIUnpacking METR's findings: Does AI slow developers down?METR's study on how AI affects developer productivityClaude CodeCursorWindsurfDo newer AI-native IDEs outperform other AI coding assistants?

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.

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.

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.

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.

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.