Here is a short demo that I show regularly in my talks about Software Analytics. It shows how you can identify components in your code that are so old that probably nobody knows anything about it anymore.
Video: No-Go Areas in the Linux Kernel
Race Condition Demo Notebook
In my talks, I’m using a short example that illustrates how the mechanics of my notebook-driven approach for analyzing software systems works. Here you can now find another example on my blog, too…
Checking the modularization of software systems by analyzing co-changing source code files
In my previous blog post, we’ve seen how we can identify files that change together in one commit.
In this blog post, we take the analysis to an advanced level…
Spotting co-changing files
In his book Software Design X-Ray, Adam Tornhill shows a nice metric to find out if some parts of your code are coupled regarding their conjoint changes: Temporal Coupling.
In this and the next blog posts, I’m playing around with Adam’s ideas (and more) to find hidden dependencies of code parts based on version control data…
Data Analysis in Software Development
When you come across my blog, you may be thinking “What is this guy doing”? There are some weird analyses that have somehow to do with software development. But why all this?