The IDE as a scriptable information system

Asenov, Dimitar; Müller, Péter; Vogel, Lutz

doi:10.1145/2970276.2970329

Cited by 4 publications

(2 citation statements)

References 24 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…An interesting direction may also be in merging intrinsic metadata already available in IDEs with the preserved, extrinsic ones, and providing a querying facility for the resulting model. The queries could be used to customize views of code provided by an IDE, similarly to the concept of scriptable IDE presented by Asenov et al [24].…”

Section: Discussionmentioning

confidence: 99%

Supporting Source Code Annotations with Metadata-Aware Development Environment

Juhár¹

2019

Proceedings of the 2019 Federated Conference on Computer Science and Information Systems

View full text Add to dashboard Cite

To augment source code with high-level metadata with the intent to facilitate program comprehension, a programmer can use annotations. There are several types of annotations: either those put directly in the code or external ones. Each type comes with a unique workflow and inherent limitations. In this paper, we present a tool providing uniform annotation process, which also adds custom metadata-awareness for an industrial IDE. We also report an experiment in which we sought whether the created annotating support helps programmers to annotate code with comments faster and more consistently. The experiment showed that with the tool the annotating consistency was significantly higher but also that the increase in annotating speed was not statistically significant.

show abstract

Section: Discussionmentioning

confidence: 99%

Supporting Source Code Annotations with Metadata-Aware Development Environment

Juhár¹

2019

Proceedings of the 2019 Federated Conference on Computer Science and Information Systems

View full text Add to dashboard Cite

show abstract

“…Asenov et al [15] present an IDE which enables programmers to query and modify programs using a combination of source code and other resources. Custom queries can be written using scripts, and the queries are composable using pipes.…”

Section: Related Workmentioning

confidence: 99%

IDE-independent program comprehension tools via source file overwriting

Sulír

Porubãn

Zoričák

2017

2017 IEEE 14th International Scientific Conference on Informatics

View full text Add to dashboard Cite

Traditionally, we have two possibilities to design tools for program comprehension and analysis. The first option is to create a standalone program, independent of any source code editor. This way, the act of source code editing is separated from the act of viewing the code analysis results. The second option is to create a plugin for a specific IDE (integrated development environment) -in this case, a separate version must be created for each IDE. We propose an approach where information about source code elements is written directly into source files as annotations or special comments. Before committing to a version control system, the annotations are removed from the source code to avoid code pollution. We briefly evaluate the approach and delineate its limitations.

show abstract

A Systematic Literature Review on the Influence of Enhanced Developer Experience on Developers' Productivity: Factors, Practices, and Recommendations

Razzaq,

Buckley,

Lai

et al. 2024

ACM Comput. Surv.

View full text Add to dashboard Cite

Context and Motivation – Developer eXperience (Dev-X) is a recent research area that focuses on developers perceptions, feelings, and values with respect to software development and software quality. Research suggests that factors and practices related to Dev-X can have a substantial impact on developer productivity (Dev-P). However, despite a large and diverse body of literature on factors that can impact Dev-P in general, there is no coherent and comprehensive characterization of how Dev-X-specific insights can influence developer productivity. Aims – In the presented research, we aim to provide a coherent, comprehensive characterization of factors and practices related to Dev-X, with a particular focus on those factors and practices that potentially affect Dev-P. Method – To this end, we performed a systematic literature review and identified 218 relevant papers in this area. We characterize the papers based on the related frameworks, and concepts common to Dev-X and Dev-P as presented in the existing literature. Dev-X factors such as ’work fragmentation’ and practices such as ’collaboration with owner-developer’ are identified using a grounded-in-the-literature, content-analysis method, guided by the theory. For each Dev-X factor, we identify attributes that might be used to assess/measure the current status (of an organisation or project) regarding that factor and how that factor and its effects on productivity have been evidenced in the literature (mentioned vs. considered in questionnaires vs. substantiated with a more positivist evaluation). Results – We identify 33 Dev-X-related factors and 41 Dev-X-related practices which are organized into ten themes to summarize their influence. The results suggest that the availability of required resources, relevant expertise re the allocated tasks, and fewer interruptions are among the top positively impacting factors. Conversely, factors like code complexity, heterogeneous contexts of tasks, and non-adherence to standardization harm Dev-X and Dev-P. Top industrial practices employed to mitigate the negative influence of factors include characterization-based task assignments, mental model support, and the timely evolution of technologies. Conclusions – Overall, this research suggests that organizations can influence Dev-P through improved Dev-X, incorporating suitable practices to mediate relevant factors in their context. Important in this regard are practices like fragmenting large tasks, highlighting the utility of proposed tasks/changes to the developers, and promoting (developer) ownership of artefacts. Finally, our results point to areas where further research seems appropriate, i.e., where Dev-X factors/practices have been proposed as being impactful on Dev-P but not yet fully substantiated or explored as such (factors like ‘Nature of Activity’ and practices like choosing practices/protocols appropriately).

show abstract

The IDE as a scriptable information system

Cited by 4 publications

References 24 publications

Supporting Source Code Annotations with Metadata-Aware Development Environment

Supporting Source Code Annotations with Metadata-Aware Development Environment

IDE-independent program comprehension tools via source file overwriting

A Systematic Literature Review on the Influence of Enhanced Developer Experience on Developers' Productivity: Factors, Practices, and Recommendations

Contact Info

Product

Resources

About