Nicholas Sawadsky – Reverb: Recommending Code-Related Web Pages

Developers often use the web (Google, StackOverflow) to find information while coding. The idea of Nicholas is to exploit knowledge in the IDE to improve queries. Their tool Reverb saves web searches that a developer performs while building the code and shows them when a developer revisits this code and searches again. Previous searches and Read more about Nicholas Sawadsky – Reverb: Recommending Code-Related Web Pages[…]

Brittany Johnson – Why Don’t Software Developers Use Static Analysis Tools to Find Bugs?

To answer this research question, Brittany held interactive semi-structured interviews, during which developers were interviewed, but also worked with static analysis tools to get them more involved in the interviews. Participants were 16 industry developers and 4 grad students. The results were coded into 6 categories: Tool output (hard to understand) User input and customizability Read more about Brittany Johnson – Why Don’t Software Developers Use Static Analysis Tools to Find Bugs?[…]

Bogdan Dit – How to Effectively Use Topic Models for Software Engineering Tasks? An Approach Based on Genetic Algorithms

Over the past few years, many techniques have been proposed to gather topics from documents, among which Latent Dirichlet Allocation. These authors propose to use LDA for traceability link recovery, feature location, and software artifact labeling. However, the standard version of LDA does not work so well on source code. Luckily, there is good news, as source Read more about Bogdan Dit – How to Effectively Use Topic Models for Software Engineering Tasks? An Approach Based on Genetic Algorithms[…]

Na Meng – Locating and Applying Systematic Edits by Learning from Examples

The motivation for this idea is that as a developer, you often have to perform similar, but not identical changes. For instance when updating an API or when preventing SQL injection attacks. In previous work, the authors created Sydit, that produces code transformation from, however, Sydit requires developers to supply target edit locations. This is where LACE comes Read more about Na Meng – Locating and Applying Systematic Edits by Learning from Examples[…]

Sarah Rastkar – Why did this code change?

The following paper has a similar aim to Yun’s, Sarah too want to support developers in understanding why their code has changed. To find out why a certain piece of code has changed, often you need to look in many different documents places. Often you start by finding the related commit message. However, this is Read more about Sarah Rastkar – Why did this code change?[…]