CodeExchange: Supporting Reformulation of Internet-Scale Code Queries in Context (T)

Martie, Lee; LaToza, Thomas D.; Hoek, André van der

doi:10.1109/ase.2015.51

Cited by 20 publications

(15 citation statements)

References 36 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Though our survey considered only general resources, there also exist a number of source code finding systems today integrated into specialized software development tools (e.g. Hoffmann et al, 2007;Linstead et al, 2009Linstead et al, , 2008Martie et al, 2015;Ossher et al, 2009;Ye and Fischer, 2002;Zagalsky et al, 2012).…”

Section: How Scientists and Engineers Find Softwarementioning

confidence: 99%

Software search is not a science, even among scientists: A survey of how scientists and engineers find software

Hucka

Graham

2018

Journal of Systems and Software

View full text Add to dashboard Cite

a b s t r a c tImproved software discovery is a prerequisite for greater software reuse: after all, if someone cannot find software for a particular task, they cannot reuse it. Understanding people's approaches and preferences when they look for software could help improve facilities for software discovery. We surveyed people working in several scientific and engineering fields to better understand their approaches and selection criteria. We found that even among highly-trained people, the rudimentary approaches of relying on general Web searches, the opinions of colleagues, and the literature were still the most commonly used. However, those who were involved in software development differed from nondevelopers in their use of social help sites, software project repositories, software catalogs, and organization-specific mailing lists or forums. For example, software developers in our sample were more likely to search in community sites such as Stack Overflow even when seeking ready-to-run software rather than source code, and likewise, asking colleagues was significantly more important when looking for ready-to-run software. Our survey also provides insight into the criteria that matter most to people when they are searching for readyto-run software. Finally, our survey also identifies some factors that can prevent people from finding software.

show abstract

Section: How Scientists and Engineers Find Softwarementioning

confidence: 99%

Software search is not a science, even among scientists: A survey of how scientists and engineers find software

Hucka

Graham

2018

Journal of Systems and Software

View full text Add to dashboard Cite

show abstract

“…A line of work on facilitating information discoverability includes work by Moreno at al., as well as Martie at al., who propose solutions for improving code search capabilities [36,34]. There are also approaches that aim to reduce information overhead in issuetracking systems [2,8] and in change management systems [41].…”

Section: Existing Researchmentioning

confidence: 99%

The challenges of staying together while moving fast

Rubin

Rinard

2016

Proceedings of the 38th International Conference on Software Engineering

View full text Add to dashboard Cite

We report on the results of an empirical study conducted with 35 experienced software developers from 22 high-tech companies, including Google, Facebook, Microsoft, Intel, and others. The goal of the study was to elicit challenges that these developers face, potential solutions that they envision to these challenges, and research initiatives that they think would deliver useful results.Challenges identified by the majority of the study participants relate to the collaborative nature of the work: the availability and discoverability of information, communication, collaborative planning and integration with work of others. Almost all participants also addressed the advantages and disadvantages of the current "fast to the market" trend, and the toll it takes on the quality of the software that they are able to deliver and on their professional and personal satisfaction as software engineers.We describe in depth the identified challenges, supporting our findings with explicit quotes from the study participants. We also put these findings in context of work done by the software engineering community and outline a roadmap for possible future research initiatives.

show abstract

“…• Offer in-situ auto complete and documentation for third party APIs (e.g, IntelliSense [48]). • Support searching for and integrating code examples (e.g, Codeexchange [49], Strathcona [50], and Codelets [51]). • Offer potential fixes and explanations of error messages (e.g, HelpMeOut [52]).…”

Section: ) Causes Of Gaps Within and Between Edit-run Cyclesmentioning

confidence: 99%

Edit-Run Behavior in Programming and Debugging

Alaboudi¹,

LaToza²

2021

Preprint

Self Cite

View full text Add to dashboard Cite

As developers program and debug, they continuously edit and run their code, a behavior known as edit-run cycles. While techniques such as live programming are intended to support this behavior, little is known about the characteristics of edit-run cycles themselves. To bridge this gap, we analyzed 28 hours of programming and debugging work from 11 professional developers which encompassed over three thousand development activities. We mapped activities to edit or run steps, constructing 581 debugging and 207 programming edit-run cycles. We found that edit-run cycles are frequent. Developers edit and run the program, on average, 7 times before fixing a defect and twice before introducing a defect. Developers waited longer before again running the program when programming than debugging, with a mean cycle length of 3 minutes for programming and 1 minute for debugging. Most cycles involved an edit to a single file after which a developer ran the program to observe the impact on the final output. Edit-run cycles which included activities beyond edit and run, such as navigating between files, consulting resources, or interacting with other IDE features, were much longer, with a mean length of 5 minutes, rather than 1.5 minutes. We conclude with a discussion of design recommendations for tools to enable more fluidity in edit-run cycles.

show abstract

CodeExchange: Supporting Reformulation of Internet-Scale Code Queries in Context (T)

Cited by 20 publications

References 36 publications

Software search is not a science, even among scientists: A survey of how scientists and engineers find software

Software search is not a science, even among scientists: A survey of how scientists and engineers find software

The challenges of staying together while moving fast

Edit-Run Behavior in Programming and Debugging

Contact Info

Product

Resources

About