Skip to content
#Management

[2/2] Title: Developer Productivity for Humans (Category Management)

#Management #Engineering #Software #Bigtech #Productivity #Leadership #Processes

Continue. story I will share the remaining articles in this series.

8 ) Build Latency, Predictability, and Developer Productivity. A very interesting article describing how the researchers were tasked with the importance of building acceleration. They describe how they defined the tradeoff between the cost of infra and the benefits of acceleration, and eventually realized that not only speed, but also the predictability of assembly is important in order for engineers to plan their work. Detailed analysis blogging. 9 ) Hybrid Productivity. Here, the authors analyze a rather cholivar topic of productivity in the office and remote work. They show in their study how they measured it and also share their findings. For example, the work shows that hybrid work during covid led to problems with onboarding new employees compared to pre-covid office work. Detailed analysis blogging 10) Onboarding and Ramp-Up. The article is about how the guys measured the effectiveness of onboarding, what metrics they used. Partially overlaps with the second article about hybrid work, as the same case about the speed and quality of onboarding during COVID-19. Detailed analysis separate post in tg 11) Measuring Flow, Focus, and Friction for Developers. This article is about the human side of productivity, or rather about the perception of engineers of two concepts: flow and friction. To do this, the authors conducted surveys and asked engineers to keep diaries, and then they matched this data with logs from tools that the engineers used. As a result, the researchers managed to create heuristics for transforming signals from logs into metrics, which are significantly associated with flow, focus and friction. Detailed analysis in separate post in tg. 12) Creativity in Software Engineering. The authors analyzed what creativity in development is, it turned out that it is a smart reuse, and not complete novelty, as is customary in other areas. In addition, this quality is inherent in cool engineers. And then they tried to juxtapose creativity and productivity and hypothesized that productivity is about the near future, and creativity is about the long-term effect of quality code. Detailed analysis in separate post in tg 13) Measuring Productivity: All Models are Wrong But Some are Useful. A summary of the work, where the authors told about the principles and methods that Google developed to overcome the limitations of models and gain valuable insights. Discussion is in separate post in tg

#Engineering #Software #Bigtech #Productivity #Management #Leadership #Processes