Bin Lin

Bin Lin

Auto-generated profile, based on publicly available information

Bin Lin

Hangzhou Dianzi University, Hangzhou, China

Research Focus & Metrics

Academic Career Length

11Years (2016-Present)

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

Representative Publications

View All Publications
27 May 2018
Verified
Conference Paper
Open access
PDF file
BLBin Lin
Bin Lin
FZFiorella Zampetti
Fiorella Zampetti
GBGabriele Bavota
Gabriele Bavota
MPMassimiliano Di Penta
Massimiliano Di Penta
MLMichele Lanza
Michele Lanza
RORocco Oliveto
Rocco Oliveto

27 February 2016
Verified
Conference Paper
Open access
PDF file
BLBin Lin
Bin Lin
AZAlexey Zagalsky
Alexey Zagalsky
MSMargaret-Anne Storey
Margaret-Anne Storey
ASAlexander Serebrenik
Alexander Serebrenik
Slack is a modern communication platform for teams that is seeing wide and rapid adoption by software develop-ment teams. Slack not only facilitates team messaging and archiving, but it also supports a wide plethora of inte-grations to external services and bots. We have found that Slack and its integrations (i.e., bots) are playing an increas-ingly significant role in software development, replacing email in some cases and disrupting software development processes. To understand how Slack impacts development team dynamics, we designed an exploratory study to inves-tigate how developers use Slack and how they benefit from it. We find that developers use Slack for personal, team-wide and community-wide purposes. Our research also reveals that developers use and create diverse integrations (called bots) to support their work. This study serves as the first step towards understanding the role of Slack in sup-porting software engineering.

7 March 2022 in ACM Transactions on Software Engineering and Methodology
Verified
Journal Article
Open access
BLBin Lin
Bin Lin
NCNathan Cassee
Nathan Cassee
ASAlexander Serebrenik
Alexander Serebrenik
GBGabriele Bavota
Gabriele Bavota
NNNicole Novielli
Nicole Novielli
MLMichele Lanza
Michele Lanza
Opinion mining, sometimes referred to as sentiment analysis, has gained increasing attention in software engineering (SE) studies. SE researchers have applied opinion mining techniques in various contexts, such as identifying developers’ emotions expressed in code comments and extracting users’ critics toward mobile apps. Given the large amount of relevant studies available, it can take considerable time for researchers and developers to figure out which approaches they can adopt in their own studies and what perils these approaches entail. We conducted a systematic literature review involving 185 papers. More specifically, we present (1) well-defined categories of opinion mining-related software development activities, (2) available opinion mining approaches, whether they are evaluated when adopted in other studies, and how their performance is compared, (3) available datasets for performance evaluation and tool customization, and (4) concerns or limitations SE researchers might need to take into account when applying/customizing these opinion mining techniques. The results of our study serve as references to choose suitable opinion mining tools for software development activities and provide critical insights for the further development of opinion mining techniques in the SE domain.

1 May 2017
Verified
Conference Paper
Closed access
BLBin Lin
Bin Lin
GRGregorio Robles
Gregorio Robles
ASAlexander Serebrenik
Alexander Serebrenik
Large open source software projects often have a globally distributed development team. Studies have shown developer turnover has a significant impact on the project success. Frequent developer turnover may lead to loss of productivity due to lacking relevant knowledge and spending extra time learning how projects work. Thus, lots of attention has been paid to which factors are related to developer retention, however, few of them focus on the impact of activities of individual developers. In this paper, we study five open source projects from different organizations and examine whether developer turnover is affected by when they start contributing and what types of contributions they are making. Our study reveals that developers have higher chances to survive in software projects when they 1) start contributing to the project earlier, 2) mainly modify instead of creating files, 3) mainly code instead of dealing with documentations. Our results also shed lights on the potential approaches to improving developer retention.

24 December 2021 in ACM Transactions on Software Engineering and Methodology
Verified
Journal Article
Open access
LTLuca Traini
Luca Traini
DPDaniele Di Pompeo
Daniele Di Pompeo
MTMichele Tucci
Michele Tucci
BLBin Lin
Bin Lin
SSSimone Scalabrino
Simone Scalabrino
VCVittorio Cortellessa
Vittorio Cortellessa
Refactoring aims at improving the maintainability of source code without modifying its external behavior. Previous works proposed approaches to recommend refactoring solutions to software developers. The generation of the recommended solutions is guided by metrics acting as proxy for maintainability (e.g., number of code smells removed by the recommended solution). These approaches ignore the impact of the recommended refactorings on other non-functional requirements, such as performance, energy consumption, and so forth. Little is known about the impact of refactoring operations on non-functional requirements other than maintainability. We aim to fill this gap by presenting the largest study to date to investigate the impact of refactoring on software performance, in terms of execution time. We mined the change history of 20 systems that defined performance benchmarks in their repositories, with the goal of identifying commits in which developers implemented refactoring operations impacting code components that are exercised by the performance benchmarks. Through a quantitative and qualitative analysis, we show that refactoring operations can significantly impact the execution time. Indeed, none of the investigated refactoring types can be considered “safe” in ensuring no performance regression. Refactoring types aimed at decomposing complex code entities (e.g., Extract Class/Interface, Extract Method) have higher chances of triggering performance degradation, suggesting their careful consideration when refactoring performance-critical code.

14 May 2016
Verified
Conference Paper
Open access
PDF file
BLBin Lin
Bin Lin
ASAlexander Serebrenik
Alexander Serebrenik