Why DevEx is important in the development of IDP and how to measure it – Vladimir Kalugin (Category Management)

It's interesting. speech My colleague Vladimir Kalugin talks about developer experience and why it is important when creating internal development platforms. This talk was part of our Platform Engineering Night conference. told earlier. Vladimir at T-Bank acts as a technical product manager and develops everything around code, assemblies and artifacts - that is, Vova improves the developer experience of all our engineers. In fact, Vova talks about the DevEx model, which includes cognitive load on engineers, feedback loops and flow state. This is how the authors of the model describe themselves.

1. Feedback loops Software organizations commonly look for ways to optimize their value stream by reducing or eliminating delays in software delivery. Shortening feedback loops—the speed and quality of responses to actions performed—is equally important to improving DevEx.
2. Cognitive load Software development is inherently complex, and the ever-growing number of tools and technologies is further adding to the cognitive load faced by developers. Cognitive load encompasses the amount of mental processing required for a developer to perform a task.
3. Flow state Developers often speak of "getting into the flow" or "being in the zone." Such statements colloquially describe the concept of flow state, a mental state in which a person performing an activity is fully immersed in a feeling of energized focus, full involvement, and enjoyment. The essence of the work on DevEx is to reduce cognitive load, shorten feedback cycles and allow engineers to get into a flow state more often. In order to assess how well this works, you need to use two types of data: Engineer surveys - allow you to collect information about the perception of engineers of a process, tool or interference

• System data (logs, metrics,) - allows you to collect factual information Combining these data sources provides a more relevant picture Interestingly, Vova showed some examples from our IDP experience about what data was collected and how it was used to make the engineers’ experience better.

Finally, there is a list of materials to study, among which

1. Whitepaper "DevEx: What Actually Drives Productivity- I've already done it in blog
2. Whitepaper "DevEx in Action- I've already done it in blog
3. Whitepaper "DevOps metrics- I haven't read it yet.
4. Website about internal development platforms Internal Developer Platform
5. Article "The top 10 fallacies in platform engineering"

I also recommend reading about this topic. Google researchers columnThe human centric approach to engineering productivity. For now. 8 articles 4 I've already looked into the details.

#Management #Leadership #Software #SoftwareDevelopment #Architecture #SoftwareArchitecture #Metrics #Devops #Processes