Stephan Salinger

Learn More
This paper describes the social practice of distributed party programming as a natural extension of pair programming in a distributed context with two or more software developers working together. To this end we provide an overview of the Eclipse plug-in Saros, a software implementation supporting this practice, and explain its technical architecture. The(More)
Abstract. Successful qualitative analysis of pair programming requires a terminology (such as a set of concepts or a coding scheme) that represents the observed phenomena on an appropriate abstraction level. On the one hand, different analysis goals will require different specialized terminology, on the other hand it would be helpful, if different studies(More)
The classical definition of pair programming (PP) describes it via two obvious roles: driver (the person currently having the keyboard) and observer (the other, alternatively called navigator). Although prior research has found some assumptions regarding these roles to be false, so far no alternative PP role model took hold. Instead, most PP research(More)
Previous research in the field of Agile Distributed Software Development often focused on the a synchronicity of working hours due to different time zones, as if this was the only risk when developing software in non-co-located environments. This case study reflects a near shoring setting in which this primary impediment does not exist and investigates a(More)
In side-by-side programming, two programmers (typically working on related aspects of a project) move their computers so close to one another that they can effortlessly change between working alone and working together, where working alone is the primary mode. The technique was proposed in order to obtain some of the advantages of pair programming at lower(More)
Since a number of quantitative studies of pair programming (the practice of two programmers working together using just one computer) have produced somewhat conflicting results, a number of researchers have started to study pair programming qualitatively. While most such studies use coding schemes that are fully or partially predefined, we have decided to(More)
Background: Distributed Pair Programming can be performed via screensharing or via a distributed IDE. The latter offers the freedom of concurrent editing (which may be helpful or damaging) and has even more awareness deficits than screen sharing. Objective: Characterize how competent distributed pair programmers may handle this additional freedom and(More)
Die im folgenden vorgestellte Diplomarbeit legt den theoretischen Rahmen für die verteilte Paarprogrammierung als Weiterentwicklung der klassischen Paarprogrammierung und beschreibt die Implementierung eines entsprechenden EclipsePlugins. Ein besonderes Augenmerk lag darin sinnvolle und realistische Anforderungen zu erarbeiten. Die Daten der(More)
In side-by-side programming, two programmers (typically working on related aspects of a project) move their computers so close to one another that they can effortlessly change between working alone and working together, where working alone is the primary mode. The technique was proposed in order to obtain some of the advantages of pair programming at much(More)