Developer productivity / how DX measures it (Series #DeveloperProductivity)
Our 3 AImigo episode is moving to Friday: one of the hosts didn’t get well over the weekend. Today I’ll do another stream on a related subject, looking at the approach taken by DX, the platform Atlassian bought last autumn for $1 billion. Here’s one way to put the productivity question: if a team ships more pull requests, how can you tell whether it’s become more productive? And how do you assess AI’s contribution if coding gets faster but the review queue grows?
Live today at 17:00 Moscow time, I’ll look at how DX answers those questions. 🔸 The history of DX Where the platform started and how research into developer experience shaped its approach to measuring productivity. 🔸 DX Core 4 What the framework borrowed from DORA, SPACE and DevEx, and how it brings together four dimensions: speed, developer effectiveness, quality and business impact. 🔸 AI Measurement Framework How to connect the use of assistants and agents to changes in a team’s work and work out what the resulting gains cost. 🔸 CAFE(S) How to check whether context is clear to an agent, actionable, accurate, complete enough and safe to share. What changed in 2024–2026? I’ll compare DX reports on the flow of pull requests and show what these data can tell us about development speed and when it’s worth looking separately at time to first review.
#Management #Leadership #Engineering #Software #Productivity #Processes #Metrics