Natural Language Checking with Program Checking Tools

Written text is an important component in the process of knowledge acquisition and communication. Poorly written text fails to deliver clear ideas to the reader no matter how revolutionary and ground-breaking these ideas are. Providing text with good writing style is essential to transfer ideas smoothly. While we have sophisticated tools to check for stylistic problems in program code, we do not apply the same techniques for written text. In this paper we present TextLint, a rule-based tool to check for common style errors in natural language. TextLint provides a structural model of written text and an extensible rule-based checking mechanism.

What do we mean by Female and Male in Neurocognitive Experiments on Language?

For several years now, neuroscientific research has been striving towards fundamental answers to questions about the relevance of sex/gender to language processing in the brain. This research has been effected through the search for sex/gender differences in the neurobiology of language processing. Thus, the main aim has ever been to focus on the differentiation of the sexes/genders, failing to define what sex, what gender, what female or male is in neurolingustic research. In other words, although neuroscientific findings have provided key insights into the brain functioning of women and men, neuropsychology has rarely questioned the complexity of the sex/gender variable beyond biology. What does “female” or “male” mean in human neurocognition; how are operationalisations implemented along the axes of “femaleness” or “maleness”; or what biological evidence is used to register the variables sex and/or gender? In the neurosciences as well as in neurocognitive research, questions such as these have so far not been studied in detail, even if they are highly significant for the scientific process. Instead, the variable of sex/gender has always been thought as solely dichotomous (as either female or male), oppositional and exclusionary of each other. Here, this theoretical contribution sets in. Based on findings in neuroscience and concepts in gender theory, this poster is dedicated to the reflection about what sex/gender is in the neuroscience of language processing. Following this aim, two levels of interest will be addressed. First: How do we define sex/gender at the level of participants? And second: How do we define sex/gender at the level of the experimental task? For the first, a multifactorial registration (work in progress) of the variable sex/gender will be presented, i.e. a tool that records sex/gender in terms of biology and social issues as well as on a spectrum between femaleness and maleness. For the second, the compulsory dichotomy of a gendered task when neurolinguistically approaching our cognitions of sex/gender will be explored.

Pangea: A Workbench for Statically Analyzing Multi-Language Software Corpora

Software corpora facilitate reproducibility of analyses, however, static analysis for an entire corpus still requires considerable effort, often duplicated unnecessarily by multiple users. Moreover, most corpora are designed for single languages increasing the effort for cross-language analysis. To address these aspects we propose Pangea, an infrastructure allowing fast development of static analyses on multi-language corpora. Pangea uses language-independent meta-models stored as object model snapshots that can be directly loaded into memory and queried without any parsing overhead. To reduce the effort of performing static analyses, Pangea provides out-of-the box support for: creating and refining analyses in a dedicated environment, deploying an analysis on an entire corpus, using a runner that supports parallel execution, and exporting results in various formats. In this tool demonstration we introduce Pangea and provide several usage scenarios that illustrate how it reduces the cost of analysis.

On Understanding How Developers Use the Spotter Search Tool

Analyzing how software engineers use the Integrated Development Environment (IDE) is essential to better understanding how engineers carry out their daily tasks. Spotter is a code search engine for the Pharo programming language. Since its inception, Spotter has been rapidly and broadly adopted within the Pharo community. However, little is known about how practitioners employ Spotter to search and navigate within the Pharo code base. This paper evaluates how software engineers use Spotter in practice. To achieve this, we remotely gather user actions called events. These events are then visually rendered using an adequate navigation tool chain. Sequences of events are represented using a visual alphabet. We found a number of usage patterns and identified underused Spotter features. Such findings are essential for improving Spotter.