Mauricio Frias

Enhancing Developer Experience During Architecture Modernization

How do you modernize a monolith without burning out your engineers? Learn how Eurowings Digital used developer feedback to improve code quality and speed.

Enhancing Developer Experience During Architecture Modernization
#1about 2 minutes

The Ship of Theseus analogy for software modernization

Legacy systems are like the Ship of Theseus, where incremental changes over time raise questions about the system's core identity.

#2about 2 minutes

Recognizing the invisible value of technical upgrades

A major frontend framework migration from Vue 2 to Vue 3 resulted in no visible change, highlighting the challenge of communicating the business value of technical debt reduction.

#3about 2 minutes

Using surveys to identify key developer pain points

Internal surveys and analytics dashboards are used to pinpoint the most significant developer pain points, ensuring that improvement efforts are targeted and effective.

#4about 3 minutes

Implementing five pillars for a better developer experience

A strategy for improving developer experience is built on five pillars: smooth onboarding, knowledge-sharing forums, dedicated platform teams, and innovation-driving hackathons.

#5about 4 minutes

Building a tech strategy focused on developer enablement

A successful tech strategy supports developers through continuous learning, clear decision-making with Architecture Decision Records (ADRs), and robust knowledge-sharing practices.

#6about 3 minutes

Applying key architectural patterns for modernization

Modernization is achieved using patterns like Onion Architecture to protect business logic, Self-Contained Systems for independence, and well-sized services instead of pure microservices.

#7about 1 minute

Measuring the impact of an improved developer experience

Investing in developer experience leads to measurable results, including faster development cycles for new services, higher developer satisfaction, and improved code quality with fewer bugs.

#8about 8 minutes

Q&A on DevEx teams and documentation strategy

The Q&A session covers the benefits of a dedicated developer experience team, managing OS flexibility, and strategies for keeping documentation valuable and up-to-date using templates and governance.

Related jobs
Jobs that call for the skills explored in this talk.

Featured Partners

Related Videos

Multiple Ships to the Island - Micro Frontends & Island Architectures59:03

Multiple Ships to the Island - Micro Frontends & Island Architectures

Florian Rappl

Forget Developer Platforms, Think Developer Productivity!57:45

Forget Developer Platforms, Think Developer Productivity!

Robert Hoffmann & Christian Denich

Empowering Thousands of Developers: Our Journey to an Internal Developer Platform29:26

Empowering Thousands of Developers: Our Journey to an Internal Developer Platform

Bastian Heilemann, Bruno Margula

Interface Contracts in Microfrontend Architectures54:39

Interface Contracts in Microfrontend Architectures

Alexander Günsche

Advanced Micro Frontends: Multi-Version and Multi-Framework Scenarios24:47

Advanced Micro Frontends: Multi-Version and Multi-Framework Scenarios

Manfred Steyer

Domain-Driven Transformation—How to Bring (Back) Sustainable Architecture to Legacy and Monoliths1:01:30

Domain-Driven Transformation—How to Bring (Back) Sustainable Architecture to Legacy and Monoliths

Henning Schwentner

Get ready for new features - the legacy challenge58:52

Get ready for new features - the legacy challenge

Hans Hosea Schäfer

Next Level Enterprise Architecture: Modular, Flexible, Scalable, Multichannel and AI-Ready?21:19

Next Level Enterprise Architecture: Modular, Flexible, Scalable, Multichannel and AI-Ready?

Maik Wietheger, Jan-Christoph Schlieker

From learning to earning

Jobs that call for the skills explored in this talk.