Improving developer participation rates in surveys

Smith, E. K. M.; Loftin, Robert; Murphy-Hill, Emerson; Bird, Christian; Zimmermann, Thomas

doi:10.1109/chase.2013.6614738

Cited by 106 publications

(90 citation statements)

References 30 publications

(33 reference statements)

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Furthermore, it was explained that the results would only be used anonymously but that it was also possible to leave behind an email address in order to receive the results when the study is completed. Lastly, as monetary prizes can increase response rates [145], it was announced that one lucky participant would receive an Amazon gift card worth 50 dollars.…”

Section: Designing the Complete Surveymentioning

confidence: 99%

Why and how JavaScript developers use linters

Tomasdottir

Aniche

Deursen

2017

2017 32nd IEEE/ACM International Conference on Automated Software Engineering (ASE)

View full text Add to dashboard Cite

A linter is a type of static analysis tool that warns software developers about possible errors in code or violations to coding standards. By using such a tool, errors can be surfaced early in the development process when they are cheaper to fix, and code can be kept more readable and maintainable. For such a tool to be successful, it is important for its creators to understand the needs and challenges of developers when using a linter. Furthermore, it needs to be made clear to developers why using such a tool can be beneficial, along with how linters can be configured to identify appropriate and relevant issues for their projects.In this thesis, we examine developers' perceptions of linters to increase our knowledge on these tools for JavaScript, the most widely used programming language in the world today. More specifically, we study why and how developers use ESLint, the most popular JavaScript linter, along with the challenges that they face while using the tool. We collect data with three different methods where we first interview 15 experts on using linters, then analyze over 9,500 ESLint configuration files and finally survey more than 300 developers from the JavaScript community. The combined results from these analyses provide developers, tool makers and researchers with valuable knowledge and advice on using and developing a linter for JavaScript.

show abstract

Section: Designing the Complete Surveymentioning

confidence: 99%

Why and how JavaScript developers use linters

Tomasdottir

Aniche

Deursen

2017

2017 32nd IEEE/ACM International Conference on Automated Software Engineering (ASE)

View full text Add to dashboard Cite

show abstract

“…Some works have reported a low rate of participation, what have motivated recent investigation on this topic [33]. We report the following factors and procedures we used to invite developers.…”

Section: Survey Samplingmentioning

confidence: 99%

“…They helped us to achieve a reasonable number of participants and improve our response rate. We apply here the same terminology used in [29] [27] [33].…”

Section: Survey Samplingmentioning

confidence: 99%

An empirical study on how developers reason about module cohesion

Silva

Sant’Anna

Chávez

2014

Proceedings of the 13th International Conference on Modularity

View full text Add to dashboard Cite

Several cohesion metrics have been proposed to support development and maintenance activities. The most traditional ones are the structural cohesion metrics, which rely on structural information in the source code. For instance, many of these metrics quantify cohesion based how methods and attributes are related to each other within a given module. Recently, conceptual cohesion metrics have been proposed for computing cohesion based on the responsibilities a given module realizes. Besides different flavors of cohesion, there is a lack of empirical evidence about how developers actually perceive cohesion and what kind of cohesion measurement aligns with developers' perception. In this paper we fill this gap by empirically investigating developers opinion through a web-based survey, which involved 80 participants from 9 countries with different levels of programming experience. We found that: most of the developers are familiar with cohesion; and they perceive cohesion based on class responsibilities, thus associating more with conceptual cohesion measurement. These results support the claim that conceptual cohesion seems to be more intuitive and closer to the human-oriented view of software cohesion. Moreover, the results showed that conceptual cohesion measurement captures the developers' notion of cohesion better than traditional structural cohesion measurement.

show abstract

“…We used the time frame of January 1, 2017 to August 1, 2017 to minimize the amount of organizational churn during the time period and identify employees' activity in their current role and team. As we have found that incentives can increase participation [71], survey participants were entered into a raffle for four $25 gift cards. We received 507 valid answers (20% response rate).…”

Section: Interviewsmentioning

confidence: 99%

Does Reviewer Recommendation Help Developers?

Kovalenko

Tintarev

Pasynkov³

et al. 2020

IIEEE Trans. Software Eng.

Self Cite

View full text Add to dashboard Cite

Abstract-Selecting reviewers for code changes is a critical step for an efficient code review process. Recent studies propose automated reviewer recommendation algorithms to support developers in this task. However, the evaluation of recommendation algorithms, when done apart from their target systems and users (i.e., code review tools and change authors), leaves out important aspects: perception of recommendations, influence of recommendations on human choices, and their effect on user experience. This study is the first to evaluate a reviewer recommender in vivo. We compare historical reviewers and recommendations for over 21,000 code reviews performed with a deployed recommender in a company environment and set out to measure the influence of recommendations on users' choices, along with other performance metrics. Having found no evidence of influence, we turn to the users of the recommender. Through interviews and a survey we find that, though perceived as relevant, reviewer recommendations rarely provide additional value for the respondents. We confirm this finding with a larger study at another company. The confirmation of this finding brings up a case for more user-centric approaches to designing and evaluating the recommenders. Finally, we investigate information needs of developers during reviewer selection and discuss promising directions for the next generation of reviewer recommendation tools. Preprint: https://doi.org/10.5281/zenodo.1404814

show abstract

Improving developer participation rates in surveys

Cited by 106 publications

References 30 publications

Why and how JavaScript developers use linters

Why and how JavaScript developers use linters

An empirical study on how developers reason about module cohesion

Does Reviewer Recommendation Help Developers?

Contact Info

Product

Resources

About