Skip to main content

Code Review

Software engineering is not a one-man-show. Software engineering is inherently collaborative, requiring people with different skill sets and backgrounds to work together in building software systems of unprecedented complexity. To build better software and to build software better, we need to deeply understand and enhance collaborative software engineering practices like code review.

Code review is the discussion around a code change among developers and has become a core practice in collaborative software engineering.

In our research, we aim to understand code review not only as quality assurance practice but as communication network among developers.

Quo Vadis, Code Review? Exploring the Future of Code Review
The Capability of Code Review as a Communication Network
Visualizing Information Diffusion in Python
For my journal-first presentation at ESEM 2024 on our work on the upper bound of information diffusion in code review, I prepared a visualization to make the idea of our simulation easier understandible. In this blogpost, you can find the Python code for the visualization.
Measuring Information Diffusion in Code Review at Spotify
The Microsoft Case: Lessons for Post-BEPS Software Development Cost Contribution Arrangements
Need for Tax Compliance in Software Engineering
In third and last blog post in the series on tax compliance in software engineering, we will estimate the prevelance of cross-border collaboration, and therefore, the need for tax compliance in software engineering by measuring cross-border code review in a multinational software company.
The Upper Bound of Information Diffusion in Code Review
Only Time Will Tell: Modelling Information Diffusion in Code Review with Time-Varying Hypergraphs