Upgrade to Pro — share decks privately, control downloads, hide ads and more …

[Keynote] What do you need to know about DevEx ...

Sponsored · SiteGround - Reliable hosting with speed, security, and support you can count on. →
Salaboy
October 08, 2025

[Keynote] What do you need to know about DevEx in 2025

for more information visit: https://www.salaboy.com

Salaboy

October 08, 2025

Transcript

27 slides
  1. What you need to know about Developer Experience in 2025

    Mauricio Salatino Software Engineer at Diagrid @Salaboy
  2. • Creating and Managing Kubernetes • Build production-grade containers •

    GitOps (Deploying stuff) • Security and Observability • Creating cloud resources on Cloud Providers • Creating APIs to abstract away complexity • I made a lot of friends … 2 Platform Engineers care about…
  3. 5 Developers care about… • Having the right tools for

    their apps • Frameworks to save time • Infra they need to run and test their applications • Understand what happens when things go wrong in production (observability)
  4. 6 There is a big gap, we need to talk

    about it • Part I: The Inner Development Loop • Part II: Cloud Native Runtimes • Part III: The Path to Production
  5. 8 Platform Engs … The current DevEx has a direct

    impact on how successful your platform initiatives will be.
  6. 10 Friction Points of DevEx 11 1. Kicking Off a

    New Project 2. Setting Up a Development Environment 3. Making a Change 4. Testing a Change 5. Running a Change 6. Debugging a Change 7. Integrating a Change with the Mainline 8. Validating a Change 9. Deploying a Change 10. Observing a Change
  7. 13 #1 Pattern: Development Environment Activation 13 1. With containers

    2. Without containers Two different approaches DevContainers (https://containers.dev/) Nix DevBox
  8. DevBox WIKI / Github README.md: • ✅ Java 25 •

    ✅ Maven 3.9.11 • ✅ kubectl 1.33.3 • ✅ dapr-cli 1.16.0
  9. 10 Friction Points of Developers Experience 16 1. Kicking Off

    a New Project 2. Setting Up a Development Environment 3. Making a Change 4. Testing a Change 5. Running a Change 6. Debugging a Change 7. Integrating a Change with the Mainline 8. Validating a Change 9. Deploying a Change 10. Observing a Change Contracts
  10. • We have been using containers as our contracts •

    What else can we provide to developers to simplify their tasks when building distributed applications? 17 Part II: Cloud Native Runtimes
  11. 1. More and more teams are using LLMs 2. Platform

    Engineering teams struggle to enable dev teams 3. New friction points and patterns are popping up 👀 26 Let’s reflect on: PE + DevEx + AI Agents

More Decks by Salaboy

Other Decks in Technology