Papers by Pavlína Wurzel Gonçalves
Code review is an activity where developers receive feedback on their code contributions from oth... more Code review is an activity where developers receive feedback on their code contributions from other developers. The frequent and potentially negative feedback developers receive makes code review prone to interpersonal conflicts. There is a consensus about such behavior being antisocial and leading to negative outcomes for the code, team, project, and even the company. However, these conflicts are a naturally occurring phenomenon that can lead to reaping the benefits of code review if managed well. Interpersonal conflicts in code review are not necessarily an issue to avoid, but rather to be managed. In this study, we survey developers in two companies-Adnovum-working predominantly on closed-source projects-and in Red Hat open source projects. Based on a set of 154 respondents, we have found that 77% of developers sometimes experience interpersonal conflicts in code review, even though mostly not very frequently. These conflicts pose some degree of a problem to 64% of developers. However, developers are rather successful in deriving constructive outcomes in the face of conflicts-24% of developers report that conflicts have more positive than negative outcomes. While they are highly successful in deriving positive outcomes for code quality and maintainability, the motivation of developers and their communication and collaboration in a team has the most potential to be harmed by conflicts. The most effective strategy to have constructive rather than destructive conflicts is managing work effort and reassigning tasks in the team to reduce stress in review. Data and materials: https://zenodo.org/records/10477537. CCS CONCEPTS • Software and its engineering → Collaboration in software development; • Social and professional topics → Computing education.
Systematické review self-reportových screeningových a diagnostických metod pro poruchy příjmu potravy
Tato prace sestava ze systematickeho review self-reportových screeningových a diagnostických meto... more Tato prace sestava ze systematickeho review self-reportových screeningových a diagnostických metod pro poruchy přijmu potravy vytvořených nebo validizovaných po publikaci DSM-IV (Diagnostický a statistický manual mentalnich poruch, 4. vydani). Studie byla provedena za ucelem vytvořeni přehledu psychometrických kvalit těchto nastrojů a popisu standardů jejich validizace. Bylo identifikovano devět screeningových a tři diagnosticke metody pro adolescenty a dospěle a v praci bylo zahrnuto 31 studii zaměřených na validizaci těchto metod. Identifikovane metody byly ohodnoceny na zakladě psychometrických kriterii pokrývajicich oblasti obsahove, kriterialni a konstruktove validity, vnitřni konzistence, dalsich ukazatelů reliability a přesnosti naměřených skorů, efektu podlahy a stropu a možnosti interpretace jejich skorů. Prace take uvadikoeficienty senzitivity, specificity a pozitivni a negativni prediktivni hodnoty daných nastrojů. K dispozici je popis, souhrn a porovnani hodnoceni jednotlivých metod. Dostupne screeningove metody identifikuji osoby, u kterých je pravděpodobný výskyt poruchy přijmu potravy na obecne rovině, a některe metody dokaži specificky rozlisit možne riziko anorexie, bulimie nebo zachvatovite přejidani. Screeningove nastroje se lisi vzhledem k jejich delce, cilove populaci i kvalitě. Diagnosticke nastroje jsou vysoce uspokojive předevsim v kriteriich hodnoticich validitu a umožňuji hodnotit anorexii, bulimii a zachvatovite přejidani, ale take subtypy poruch přijmu potravy a kategorizovat symptomatickou populaci. V soucasných studiich vsak nejsou dostupna data podporujici validitu nastrojů s ohledem na kriteria formulovana v DSM-V.
Online sexuální obsahy očima dospívajících
Tento kvalitativni výzkum se zaměřuje na zažitky děti a adolescentů (9-16 let) na internetu spoje... more Tento kvalitativni výzkum se zaměřuje na zažitky děti a adolescentů (9-16 let) na internetu spojených se sexualitou, a to na sexualni materialy a sexualni komunikaci online. Cilem je popsat siři zažitků děti a adol-escentů online spojenou se sexualitou, emocionalni reakce na prožitou situaci a povědomi děti a adolescentů o sexualnich problematických situacich online. Zvlastě jsou popsany děti (9-10 let), rani adolescenti (11-13 let) a středni adolescenti (14-16 let). Výsledky je možne použit pro definovani online rizikoveho sexualniho chovani online, ktere zatim ve výzkumu chybi. Poukazala jsem take na to, že charakter online aktivit spojených se sexualitou se s věkem měni. Prakticka a výzkumna aplikace výsledků je diskutovana. Prace vychazi z projektu EU Kids Online III, zaměřeneho na problematicke situace online.
arXiv (Cornell University), Jan 14, 2022
Code review consists of manual inspection, discussion, and judgment of source code by developers ... more Code review consists of manual inspection, discussion, and judgment of source code by developers other than the code's author. Due to discussions around competing ideas and group decision-making processes, interpersonal conflicts during code reviews are expected. This study systematically investigates how developers perceive code review conflicts and addresses interpersonal conflicts during code reviews as a theoretical construct. Through the thematic analysis of interviews conducted with 22 developers, we confirm that conflicts during code reviews are commonplace, anticipated and seen as normal by developers. Even though conflicts do happen and carry a negative impact for the review, conflicts-if resolved constructively-can also create value and bring improvement. Moreover, the analysis provided insights on how strongly conflicts during code review and its context (i.e., code, developer, team, organization) are intertwined. Finally, there are aspects specific to code review conflicts that call for the research and application of customized conflict resolution and management techniques, some of which are discussed in this paper.
Supplementary Material for Competencies for Code Review
Zenodo (CERN European Organization for Nuclear Research), Dec 5, 2022
Proceedings of the ACM on Human-Computer Interaction
Peer code review is a widely practiced software engineering process in which software developers ... more Peer code review is a widely practiced software engineering process in which software developers collaboratively evaluate and improve source code quality. Whether developers can perform good reviews depends on whether they have sufficient competence and experience. However, the knowledge of what competencies developers need to execute code review is currently limited, thus hindering, for example, the creation of effective support tools and training strategies. To address this gap, we firstly identified 27 competencies relevant to performing code review through expert validation. Later, we conducted an online survey with 105 reviewers to rank these competencies along four dimensions: frequency of usage, importance, proficiency, and desire of reviewers to improve in that competency. The survey shows that technical competencies are considered essential to performing reviews and that respondents feel generally confident in their technical proficiency. Moreover, reviewers feel less confi...
Empirical Software Engineering
Code review is an important process in software engineering – yet, a very expensive one. Therefor... more Code review is an important process in software engineering – yet, a very expensive one. Therefore, understanding code review and how to improve reviewers’ performance is paramount. In the study presented in this work, we test whether providing developers with explicit reviewing strategies improves their review effectiveness and efficiency. Moreover, we verify if review guidance lowers developers’ cognitive load. We employ an experimental design where professional developers have to perform three code review tasks. Participants are assigned to one of three treatments: ad hoc reviewing, checklist, and guided checklist. The guided checklist was developed to provide an explicit reviewing strategy to developers. While the checklist is a simple form of signaling (a method to reduce cognitive load), the guided checklist incorporates further methods to lower cognitive demands of the task such as segmenting and weeding. The majority of the participants are novice reviewers with low or no co...
Interpersonal Conflicts During Code Review: Developers' Experience and Practices
Code review consists of manual inspection, discussion, and judgment of source code by developers ... more Code review consists of manual inspection, discussion, and judgment of source code by developers other than the code's author. Due to discussions around competing ideas and group decision-making processes, interpersonal conflicts during code reviews are expected. This study systematically investigates how developers perceive code review conflicts and addresses interpersonal conflicts during code reviews as a theoretical construct. Through the thematic analysis of interviews conducted with 22 developers, we confirm that conflicts during code reviews are commonplace, anticipated and seen as normal by developers. Even though conflicts do happen and carry a negative impact for the review, conflicts—if resolved constructively—can also create value and bring improvement. Moreover, the analysis provided insights on how strongly conflicts during code review and its context (i.e., code, developer, team, organization) are intertwined. Finally, there are aspects specific to code review con...
Data and Material for 'Interpersonal Conflicts During Code Review
Data and Material supporting the paper 'Interpersonal Conflicts During Code Review: Developer... more Data and Material supporting the paper 'Interpersonal Conflicts During Code Review: Developers' Experience and Practices'
Proceedings of the ACM on Human-Computer Interaction
Code review consists of manual inspection, discussion, and judgment of source code by developers ... more Code review consists of manual inspection, discussion, and judgment of source code by developers other than the code's author. Due to discussions around competing ideas and group decision-making processes, interpersonal conflicts during code reviews are expected. This study systematically investigates how developers perceive code review conflicts and addresses interpersonal conflicts during code reviews as a theoretical construct. Through the thematic analysis of interviews conducted with 22 developers, we confirm that conflicts during code reviews are commonplace, anticipated and seen as normal by developers. Even though conflicts do happen and carry a negative impact for the review, conflicts-if resolved constructively-can also create value and bring improvement. Moreover, the analysis provided insights on how strongly conflicts during code review and its context (i.e., code, developer, team, organization) are intertwined. Finally, there are aspects specific to code review con...
Replication package - Do Explicit Review Strategies Improve Code Review Performance? Towards Understanding the Role of Cognitive Load
Replication package of the paper "Do Explicit Review Strategies Improve Code Review Performa... more Replication package of the paper "Do Explicit Review Strategies Improve Code Review Performance? Towards Understanding the Role of Cognitive Load" The replication package contains: - A zip archive containing the logs of the experiment: The archive contains one log for each iteration of the experiment. - A defect.ods file with the description of the defects used in the experiment. - A csv file (<em>AllDevelopers.csv</em>) containing the results of all developers who took part in the experiment (generated from the logs using our data preparation program) - The R script used to perform the analysis of the results. - A pdf file containing the items included in our checklist. - A zip archive (<em>ExperimentUI</em>) containing the code of the online platform used for our experiment. - A zip archive (<em>Data preparations program</em>) containing the script used to analyse the experiment logs and create the final csv file (AllDevelopers.csv) - ...
Do Explicit Review Strategies Improve Code Review Performance?
Proceedings of the 17th International Conference on Mining Software Repositories
Characterizing Women (Not) Contributing to Open-Source
2019 IEEE/ACM 2nd International Workshop on Gender Equality in Software Engineering (GE)
Characterizing Women (Not) Contributing to Open-Source
2019 IEEE/ACM 2nd International Workshop on Gender Equality in Software Engineering (GE)
Uploads
Papers by Pavlína Wurzel Gonçalves