The Architecture of Developer Experience (DX)

Your engineers are talented. They care deeply about the work. So why do they finish a sprint feeling exhausted instead of energized? Why do onboarding pipelines take weeks? Why do the best developers quietly start updating their resumes? The answer is not a people problem. Developer Experience is an architecture problem. In this session, we examine the real, measurable business cost of poor DX — from toil and context switching to attrition and lost flow state. We explore DX through three critical dimensions: cognitive load, feedback loop latency, and psychological safety and autonomy. We introduce the SPACE framework (Forsgren et al., 2021) as a rigorous, research-backed lens for measuring what matters. We look at the Internal Developer Platform (IDP) pattern, feedback loop latency hierarchies, and proven strategies for eliminating toil at scale. You will leave with a systems-thinker’s vocabulary, a concrete measurement model, and one challenge: find one DX friction point this week and eliminate it.

This session is rated level 300 -"More Advanced - Lots of Code".

Reference Links

• SPACE Framework
• Stack Overflow Developer Survey 2024

Interested in this Talk?

Would you like this talk at your event? You can send me an email. If you use Sessionize you can view the talk on Sessionize.