Using task context to improve programmer productivity

By Mik Kersten, Gail C. Murphy. SIGSOFT '06/FSE-14, 2006

492 citations recorded by the source corpus.

Subfields: Computer Networks and Communications, Information Systems, Information Systems and Management

View Paper: https://www.semanticscholar.org/paper/02d3872f241cdf34504e9dece7ad8daeb279a585

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Computer Networks and Communications

In Information Systems

In Information Systems and Management

Citations in the corpus

What Makes a Good Bug Report? (2008, methodology): “In the meantime, things have changed: The Mylyn tool by Kersten and Murphy [36] allows attaching a task context to bug reports so that changes can be tracked on a very fine-grained level.”
How Program History Can Improve Code Completion (2008, result): “Mylyn’s task contexts feature a form of code completion prioritizing elements belonging to the task at hand [4], which is very similar to our approach.”
Is GitHub Copilot a Substitute for Human Pair-programming? An Empirical Study (2022, background): “There have been studies on how professional developers comprehend software to understand how software development should be done, such as how programmers refactor while validating other programmers [7], and how implementation of task context for the Eclipse development environment improved productiv”
A practical guide to controlled experiments of software engineering tools with human participants (2013, background): “Therefore, a critical step in preparing an experiment is to run pilots (Keppel 1982): test runs of a study intended to find sources of extraneous variation.”
Measuring Program Comprehension: A Large-Scale Field Study with Professionals (2018, background): “In practice, Mylyn(14) [24], can help reduce the side effect due to task switching, and improve productivity by reducing searching, scrolling, and navigation.”
Global Software Engineering: The Future of Socio-technical Coordination (2007, methodology): “Kersten et al [45] design a tool, Mylar, that computes a degree of interest for project artifacts, using task context and project history, and provides a filter function to help identify useful artifacts.”
Evaluating the evaluations of code recommender systems: A reality check (2016, background): “However, existing approaches either capture data that is not appropriate to build or evaluate source-based RSSE (e.g., [10,11]) or they do not perform automated evaluations and evaluate results manually (e.g., [16]).”
On the localness of software (2014, background): “For instance, one thread of research [10, 20, 25, 39] concerns on the suggestion of method calls and class names.”
Graph-Based Statistical Language Model for Code (2015, unknown): “There exist deterministic approaches to improve code completion/suggestion and code search by using recent editing history [29], [30], cloned code [31], developers’ editing history [32], API usages, examples, and documentation [33], [34], [35], [36], [37], [38], structural context [39], parameter fi”