Thomas D. LaToza

Thomas D. LaToza

Auto-generated profile, based on publicly available information

Thomas D. LaToza

George Mason University, Fairfax, Virginia, USA

Research Focus & Metrics

Academic Career Length

13Years (2014-Present)

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

Representative Publications

View All Publications
11 September 2023 in Empirical Software Engineering
Verified
Journal Article
Closed access
PDF file
AAAbdulaziz Alaboudi
Abdulaziz Alaboudi
TLThomas D. LaToza
Thomas D. LaToza

7 March 2020 in Empirical Software Engineering
Verified
Journal Article
Closed access
PDF file
TLThomas D. LaToza
Thomas D. LaToza
MAMaryam Arab
Maryam Arab
DLDastyni Loksa
Dastyni Loksa
AKAmy J. Ko
Amy J. Ko

24 July 2023 in ACM Transactions on Software Engineering and Methodology
Verified
Journal Article
Open access
MDMatthew C. Davis
Matthew C. Davis
EAEmad Aghayi
Emad Aghayi
TLThomas D. Latoza
Thomas D. Latoza
XWXiaoyin Wang
Xiaoyin Wang
BMBrad A. Myers
Brad A. Myers
JSJoshua Sunshine
Joshua Sunshine
A key goal of software engineering research is to improve the environments, tools, languages, and techniques programmers use to efficiently create quality software. Successfully designing these tools and demonstrating their effectiveness involves engaging with tool users—software engineers. Researchers often want to conduct user studies of software engineers to collect direct evidence. However, running user studies can be difficult, and researchers may lack solution strategies to overcome the barriers, so they may avoid user studies. To understand the challenges researchers face when conducting programmer user studies, we interviewed 26 researchers. Based on the analysis of interview data, we contribute (i) a taxonomy of 18 barriers researchers encounter; (ii) 23 solution strategies some researchers use to address 8 of the 18 barriers in their own studies; and (iii) 4 design ideas, which we adapted from the behavioral science community, that may lower 8 additional barriers. To validate the design ideas, we held an in-person all-day focus group with 16 researchers.

28 March 2017 in IEEE Software
Verified
Journal Article
Closed access
KSKlaas-Jan Stol
Klaas-Jan Stol
TLThomas D. LaToza
Thomas D. LaToza
CBChristian Bird
Christian Bird
Crowdsourcing, which leverages the intelligence and contributions of a large group of people to achieve a specific goal, is disrupting business models and work practices. Because crowdsourcing approaches could have a far-reaching impact on future software development, this theme issue explores various ways developers and managers can benefit from these new opportunities. The Web Extra https://youtu.be/Z_8vWQjU7iY is an audio podcast of the introduction to the theme issue on crowdsourcing for software engineering.

8 November 2022 in Empirical Software Engineering
Verified
Journal Article
Closed access
PDF file
SMSahar Mehrpour
Sahar Mehrpour
TLThomas D. LaToza
Thomas D. LaToza

5 April 2018 in IEEE Transactions on Software Engineering
Verified
Journal Article
Closed access
TLThomas D. LaToza
Thomas D. LaToza
ALArturo Di Lecce
Arturo Di Lecce
FRFabio Ricci
Fabio Ricci
WTW. Ben Towne
W. Ben Towne
AHAndre van der Hoek
Andre van der Hoek
Traditional forms of crowdsourcing such as open source software development harness crowd contributions to democratize the creation of software. However, potential contributors must first overcome joining barriers forcing casually committed contributors to spend days or weeks onboarding and thereby reducing participation. To more effectively harness potential contributions from the crowd, we propose a method for programming in which work occurs entirely through microtasks, offering contributors short, self-contained tasks such as implementing part of a function or updating a call site invoking a function to match a change made to the function. In microtask programming, microtasks involve changes to a single artifact, are automatically generated as necessary by the system, and nurture quality through iteration. A study examining the feasibility of microtask programming to create small programs found that developers were able to complete 1008 microtasks, onboard and submit their first microtask in less than 15 minutes, complete all types of microtasks in less than 5 minutes on average, and create 490 lines of code and 149 unit tests. The results demonstrate the potential feasibility as well as revealing a number of important challenges to address to successfully scale microtask programming to larger and more complex programs.