Guardado en:
| Autores principales: | , , , , , , , , , , |
|---|---|
| Formato: | Preprint |
| Publicado: |
2025
|
| Materias: | |
| Acceso en línea: | https://arxiv.org/abs/2503.10977 |
| Etiquetas: |
Agregar Etiqueta
Sin Etiquetas, Sea el primero en etiquetar este registro!
|
| _version_ | 1866908955578466304 |
|---|---|
| author | Beller, Moritz Park, Amanda Nakad, Karim Patel, Akshay Mohanty, Sarita Garberson, Ford Malone, Ian G. Garg, Vaishali Verroken, Henri Kennedy, Andrew Avgustinov, Pavel |
| author_facet | Beller, Moritz Park, Amanda Nakad, Karim Patel, Akshay Mohanty, Sarita Garberson, Ford Malone, Ian G. Garg, Vaishali Verroken, Henri Kennedy, Andrew Avgustinov, Pavel |
| contents | This paper introduces Diff Authoring Time (DAT), a powerful, yet conceptually simple approach to measuring software development productivity that enables rigorous experimentation. DAT is a time based metric, which assess how long engineers take to develop changes, using a privacy-aware telemetry system integrated with version control, the IDE, and the OS. We validate DAT through observational studies, surveys, visualizations, and descriptive statistics. At Meta, DAT has powered experiments and case studies on more than 20 projects. Here, we highlight (1) an experiment on introducing mock types (a 14% DAT improvement), (2) the development of automatic memoization in the React compiler (33% improvement), and (3) an estimate of thousands of DAT hours saved annually through code sharing (> 50% improvement). DAT offers a precise, yet high-coverage measure for development productivity, aiding business decisions. It enhances development efficiency by aligning the internal development workflow with the experiment-driven culture of external product development. On the research front, DAT has enabled us to perform rigorous experimentation on long-standing software engineering questions such as "do types make development more efficient?" |
| format | Preprint |
| id |
arxiv_https___arxiv_org_abs_2503_10977 |
| institution | arXiv |
| publishDate | 2025 |
| record_format | arxiv |
| spellingShingle | What's DAT? Three Case Studies of Measuring Software Development Productivity at Meta With Diff Authoring Time Beller, Moritz Park, Amanda Nakad, Karim Patel, Akshay Mohanty, Sarita Garberson, Ford Malone, Ian G. Garg, Vaishali Verroken, Henri Kennedy, Andrew Avgustinov, Pavel Software Engineering This paper introduces Diff Authoring Time (DAT), a powerful, yet conceptually simple approach to measuring software development productivity that enables rigorous experimentation. DAT is a time based metric, which assess how long engineers take to develop changes, using a privacy-aware telemetry system integrated with version control, the IDE, and the OS. We validate DAT through observational studies, surveys, visualizations, and descriptive statistics. At Meta, DAT has powered experiments and case studies on more than 20 projects. Here, we highlight (1) an experiment on introducing mock types (a 14% DAT improvement), (2) the development of automatic memoization in the React compiler (33% improvement), and (3) an estimate of thousands of DAT hours saved annually through code sharing (> 50% improvement). DAT offers a precise, yet high-coverage measure for development productivity, aiding business decisions. It enhances development efficiency by aligning the internal development workflow with the experiment-driven culture of external product development. On the research front, DAT has enabled us to perform rigorous experimentation on long-standing software engineering questions such as "do types make development more efficient?" |
| title | What's DAT? Three Case Studies of Measuring Software Development Productivity at Meta With Diff Authoring Time |
| topic | Software Engineering |
| url | https://arxiv.org/abs/2503.10977 |