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

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

Transcript

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. Friends teach you things June 2022: https://www.youtube.com/watch?v=OJwQkFl7gRY
4. Friends teach you things June 2022: https://www.youtube.com/watch?v=OJwQkFl7gRY
5. 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)
6. 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
7. 7 We noticed… “PE and DE are NOT two separate problems”
8. 8 Platform Engs … The current DevEx has a direct impact on how successful your platform initiatives will be.
9. 9 Devs know… Platform initiatives will directly affect their DevEx
10. 10 Friction Points of Developers Experience 10
11. 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
12. #1 Pattern: Development Environment Activation 12 CDEs @ Spring I/O 2025 by Saeed Zarinfam
13. 13 #1 Pattern: Development Environment Activation 13 1. With containers 2. Without containers Two different approaches DevContainers (https://containers.dev/) Nix DevBox
14. 14 14 NixOS (https://nixos.org) without containers
15. DevBox WIKI / Github README.md: • ✅ Java 25 • ✅ Maven 3.9.11 • ✅ kubectl 1.33.3 • ✅ dapr-cli 1.16.0
16. 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
17. • 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
18. 18 Spoiler Alert! APIs are always the answer
19. But there is a gap… 19
20. Platform people like CLIs 20
21. 21 21 Decoupling applications from infrastructure with APIs
22. Integrating with the Application layer 22
23. Relying on specs for consistency and integrations 23 https://www.dash0.com/blog/observing-dapr-with-opentelemetry-and-dash0
24. Crafting local development experiences 24
25. Local developer experience without K8s 25 Dapr Spring Boot Testcontainers Microcks
26. 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
27. Make friends! https://github.com/devex-on-k8s/book/ https://www.manning.com/books/developer -experience-on-kubernetes 27