  Developers interrupting their participation in a project might slowly forget
critical information about the code, such as its intended purpose, structure,
the impact of external dependencies, and the approach used for implementation.
Forgetting the implementation details can have detrimental effects on software
maintenance, comprehension, knowledge sharing, and developer productivity,
resulting in bugs, and other issues that can negatively influence the software
development process. Therefore, it is crucial to ensure that developers have a
clear understanding of the codebase and can work efficiently and effectively
even after long interruptions. This registered report proposes an empirical
study aimed at investigating the impact of the developer's activity breaks
duration and different code quality properties. In particular, we aim at
understanding if the amount of activity in a project impact the code quality,
and if developers with different activity profiles show different impacts on
code quality. The results might be useful to understand if it is beneficial to
promote the practice of developing multiple projects in parallel, or if it is
more beneficial to reduce the number of projects each developer contributes.
