Context: Burnout is a work-related syndrome that, similar to many occupations, influences
most software developers. For decades, studies in software engineering (SE) have explored …

Context: In scientific software, the inability to reproduce results is often due to technical
issues and challenges in recreating the full computational workflow from the original …

Understanding and identifying the causes behind developers' emotions (eg, Frustration
caused by'delays in merging pull requests') can be crucial towards finding solutions to …

Self-admitted technical debt (SATD) consists of annotations, left by developers as comments
in the source code or elsewhere, as a reminder about pieces of software manifesting …

Emotions (eg, Joy, Anger) are prevalent in daily software engineering (SE) activities, and are
known to be significant indicators of work productivity (eg, bug fixing efficiency). Recent …

Code intelligence tools such as GitHub Copilot have begun to bridge the gap between
natural language and programming language. A frequent software development task is the …

Upon evolving their software, organizations and individual developers have to spend a
substantial effort to pay back technical debt, ie, the fact that software is released in a shape …

Abstract Self-Admitted Technical Debt (SATD) is primarily studied in Object-Oriented (OO)
languages and traditionally commercial software. However, scientific software coded in …

Abstract Self-Admitted Technical Debt (SATD) consists of annotations—typically, but not
only, source code comments—pointing out incomplete features, maintainability problems, or …

Kee** track of and managing Self-Admitted Technical Debts (SATDs) is important for
maintaining a healthy software project. Current active-learning SATD recognition tool …