[1/2] Measuring Developer Experience With a Longitudinal Survey (Filed under DevEx)

[1/2] Measuring Developer Experience With a Longitudinal Survey (Rubric #DevEx)

I read it interesting. whitepaper From the guys at Google who talked about their way of doing surveys to measure developer experiences. This is another article in the series “Hunam centric approach to developer productivity” from the guys at Google. beforehand. Now for the highlights of the article

1. The authors begin the story by conducting such surveys with 2018 of the year and that is why longitudinal surveyIn the article, they will share the main conclusions.
2. But to start with, why would you want to do these surveys, and they say something like this? Surveys are initially people-centric – asking questions about how engineers perceive, think and feel Surveys are fast and flexible - they are definitely easier to start and change than measurements, which are based on logs from systems. Surveys can reveal things that cannot be objectively measured, such as satisfaction, and open-ended questions can be asked. Surveys can be launched quickly to start collecting developer productivity data
3. Many people criticize the polls, noting that Surveys are subjective and can be misinterpreted They may be biased, especially if respondents are interested in biased results They can display the situation as people perceive it, not what is happening in reality. The authors solve these problems by sharing surveys and logs-based measurements, which gives a more complete picture. At the same time, the longevity of research helps - authors can show how the picture changes as recommendations are applied to improve the situation.

Continuation of the review in next post.

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