169 citations · 201 across the 8 of their papers we have counts for
10 papers · 1 filter
Observing Fine-Grained Changes in Jupyter Notebooks During Development Time
Sergey Titov, Konstantin Grotov, Cristina Sarasua +5
In software engineering research, the analysis of fine-grained logs led to significant innovations in areas such as refactoring, security, and code completion. However, even though…
SZZ in the time of Pull Requests
Fernando Petrulio, David Ackermann, Enrico Fregnan +6
In the multi-commit development model, programmers complete tasks (e.g., implementing a feature) by organizing their work in several commits and packaging them into a commit-set. A…
Less is More: Supporting Developers in Vulnerability Detection during Code Review
Larissa Braz, Christian Aeberhard, Gül Çalikli +1
Reviewing source code from a security perspective has proven to be a difficult task. Indeed, previous research has shown that developers often miss even popular and easy-to-detect…
Interpersonal Conflicts During Code Review
Pavlína Wurzel Gonçalves, Gül Çalıklı, Alberto Bacchelli
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 d…
Why Don't Developers Detect Improper Input Validation?'; DROP TABLE Papers; --
Larissa Braz, Enrico Fregnan, Gül Çalikli +1
Improper Input Validation (IIV) is a software vulnerability that occurs when a system does not safely handle input data. Even though IIV is easy to detect and fix, it still commonl…
Building Implicit Vector Representations of Individual Coding Style
Vladimir Kovalenko, Egor Bogomolov, Timofey Bryksin +1
With the goal of facilitating team collaboration, we propose a new approach to building vector representations of individual developers by capturing their individual contribution s…