Andre van der Hoek

Dr. Andre van der Hoek

orcid

Research Focus & Metrics

Academic Career Length

25Years (2002-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
19 September 2018 in IEEE Transactions on Software Engineering
Verified
Journal Article
Closed access
GGGleiph Ghiotto
Gleiph Ghiotto
LMLeonardo Gresta Paulino Murta
Leonardo Gresta Paulino Murta
MBMarcio Oliveira Barros
Marcio Oliveira Barros
AHAndre van der Hoek
Andre van der Hoek
When multiple developers change a software system in parallel, these concurrent changes need to be merged to all appear in the software being developed. Numerous merge techniques have been proposed to support this task, but none of them can fully automate the merge process. Indeed, it has been reported that as much as 10% to 20% of all merge attempts result in a merge conflict, meaning that a developer has to manually complete the merge. To date, we have little insight into the nature of these merge conflicts. What do they look like, in detail? How do developers resolve them? Do any patterns exist that might suggest new merge techniques that could reduce the manual effort? This paper contributes an in-depth study of the merge conflicts found in the histories of 2,731 open source Java projects. Seeded by the manual analysis of the histories of five projects, our automated analysis of all 2,731 projects: (1) characterizes the merge conflicts in terms of number of chunks, size, and programming language constructs involved, (2) classifies the manual resolution strategies that developers use to address these merge conflicts, and (3) analyzes the relationships between various characteristics of the merge conflicts and the chosen resolution strategies. Our results give rise to three primary recommendations for future merge techniques, that - when implemented - could on one hand help in automatically resolving certain types of conflicts and on the other hand provide the developer with tool-based assistance to more easily resolve other types of conflicts that cannot be automatically resolved.

27 November 2002 in Software: Practice and Experience
Verified
Journal Article
Closed access
PDF file
AHAndre van der Hoek
Andre van der Hoek
AWAlexander L. Wolf
Alexander L. Wolf

10 February 2010
Verified
Book Chapter
Closed access
PDF file
IMIvan Mistrík
Ivan Mistrík
JGJohn Grundy
John Grundy
AHAndre van der Hoek
Andre van der Hoek
JWJim Whitehead
Jim Whitehead

31 December 2004 in Science of Computer Programming
Verified
Journal Article
Closed access
AHAndre van der Hoek
Andre van der Hoek

19 April 2023
Verified
Conference Paper
Open access
NWNovia Wong
Novia Wong
VJVictoria Jackson
Victoria Jackson
AHAndre van der Hoek
Andre van der Hoek
IAIftekhar Ahmed
Iftekhar Ahmed
SSStephen M. Schueller
Stephen M. Schueller
MRMadhu Reddy
Madhu Reddy
Software engineers exhibit higher burnout and suicide rates compared to many other information workers. Consequently, mental wellbeing is a growing concern to technology organizations. To better understand the challenges of supporting mental wellbeing in the context of the work of software engineering, we conducted 14 interviews with software engineers. We examine the different aspects of their lived experiences with mental wellbeing at work, their strategies for managing mental wellbeing, the challenges they face in using these strategies, and recommendations they have for mental wellbeing technologies. We contribute to the HCI literature by discussing how mental wellbeing should be considered within the context of work across individual, team, and organization levels, and highlight the need for integrating mental wellbeing into the technologies employees use at work.

11 May 2024
Verified
Conference Paper
Open access
YCYoonha Cha
Yoonha Cha
IFIsabela Figueira
Isabela Figueira
JAJessy Ayala
Jessy Ayala
EEEmory James Edwards
Emory James Edwards
JGJoshua Garcia
Joshua Garcia
SBStacy Marie Branham
Stacy Marie Branham
Scholars have investigated numerous barriers to accessible software development tools and processes for Blind and Low Vision (BLV) developers. However, the research community has yet to study the accessibility of software development meetings, which are known to play a crucial role in software development practice. We conducted semi-structured interviews with 26 BLV software professionals about software development meeting accessibility. We found four key themes related to in-person and remote software development meetings: (1) participants observed that certain meeting activities and software tools used in meetings were inaccessible, (2) participants performed additional labor in order to make meetings accessible, (3) participants avoided disclosing their disability during meetings due to fear of career repercussions, (4) participants suggested technical, social and organizational solutions for accessible meetings, including developing their own solutions. We suggest recommendations and design implications for future accessible software development meetings including technical and policy-driven solutions.