Blog

29 April 2015 - Uttering Threats to Validity

One of the reviews for my ICSE 2015 submission included the demand: "There is no threats to validity or limitation section. Please add this." When reporting on research results, it is of course necessary to state and discuss decisions of the experimental design that have major repercussions on how the results can be interpreted...

28 November 2014 - Summarizing Qualitative Evidence with Spark-Histograms

When reporting on data analyzed using a qualitative research approach, a major challenge is to properly indicate the nature and amount of the evidence that support a given observation...

15 October 2014 - Code Examples: Less is More, but What Should We Chop Off?

A lot of the documents we need to understand and use software technologies include code examples... To decide whether to study a code example in detail, it's useful to have a summary of what it's about, just like for any other document. But most techniques for summarizing "normal" documents don't apply to code...

8 August 2014 - Embracing Discrimination (in API Documentation)

A flat (non-hierarchical) content presentation mostly assumes the reader wants to read everything sequentially. This assumption is fine for suspenseful novels, but it crumples in the case of API documentation...

26 June 2014 - Good Practices for Software Analytics Papers

Much effort is currently invested to increase our understanding of software development by analyzing large data sets [...]. This type of effort is now known as Software Analytics [...]. We [provide] a list of desirable practices for reporting on software analytics projects.

12 May 2014 - APIs: What Should We Document (and Not Document)?

APIs are not always self-explanatory, so we need to complement them with documentation for better usability...But how do we do that? ...