Software engineering evolved from a rigid process to a dynamic interplay of people (eg,
stakeholders or developers). Organizational and social literature call this interplay an …

A variety of research methods and techniques are available to SE researchers, and while
several overviews exist, there is consistency neither in the research methods covered nor in …

Nearly every popular programming language comes with one or more package managers.
The software packages distributed by such package managers form large software …

The mirroring hypothesis predicts that organizational ties within a project, firm, or group of
firms (eg, communication, collocation, employment) will correspond to the technical …

Code smells are poor implementation choices applied by developers during software
evolution that often lead to critical flaws or failure. Much in the same way, community smells …

The industrial sector is an important player in the global sustainable development agenda.
Over the last several decades, the sector has made considerable progress towards the …

Continuous Integration (CI) has become a common practice in both industrial and open-
source software development. While CI has evidently improved aspects of the software …

Software engineering is now more than ever a community effort. Its success often weighs on
balancing distance, culture, global engineering practices and more. In this scenario many …

A broken snapshot represents a snapshot from a project's change history that cannot be
compiled. Broken snapshots can have significant implications for researchers, as they could …

Social debt is analogous to technical debt in many ways: it represents the state of software
development organisations as the result of “accumulated” decisions. In the case of social …