From 661b4ec47300350301b794d1d398ddad80c81545 Mon Sep 17 00:00:00 2001 From: Nicholas Nelson Date: Mon, 17 Sep 2018 17:11:31 -0700 Subject: [PATCH] Updated the abstract included in the Titlepage.tex document that is required for EMSE Journal submissions --- Titlepage.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Titlepage.tex b/Titlepage.tex index 53dc0b8..1f7e85b 100644 --- a/Titlepage.tex +++ b/Titlepage.tex @@ -33,7 +33,7 @@ Without such knowledge, tool builders might be building on the wrong assumptions and researchers might miss opportunities for improving the state of the art. We conducted semi-structured interviews with 10 software developers across 7 organizations, including both open-source and commercial projects. -We identify key processes, techniques, and perceptions from developers, which we extend and validate via two surveys, a \emph{Processes Survey} and a \emph{Barriers Survey,} of 102 and 162 developers, respectively. +We identify key processes, techniques, and perceptions from developers, which we extend and validate via two surveys, a \emph{Barriers Survey} and a \emph{Processes Survey,} of 162 and 102 developers, respectively. Among others, we find that developers rely on reactive strategies of monitoring for merge conflicts. We find that developers defer responding to conflicts based on their perception of the complexity of the conflicting code and that deferring affects the workflow of the entire team.