In this blog post, I want to show you how you can visualize the contributions of developers to your code base over time. I came across the Stream Graph visualization and it looks like it would fit quite nicely for this purpose…
![Session Summary [DevOps Camp compact 2017]](https://www.feststelltaste.de/wp-content/uploads/2017/10/game_over.jpg "Session Summary [DevOps Camp compact 2017]")
At the BarCamp “DevOps Camp compact 2017” last weekend, I moderated a discussion round based on the question
“What prevents you from doing software development effectively?”
The original reason for this question was that I wanted to know…
When working with bigger software systems, it’s easy to get lost in all the source code that makes up the system. A good software system has to provide a structure that allows developers to quickly grasp the main ideas of a system. A proven method to achieve this is using hierarchies and schemas. With this approach, tiny things can be summed up to bigger ones that make somehow sense in a more broader view…
In Carola Lilienthal’s talk about architecture and technical debt at Herbstcampus 2017, I was reminded that I wanted to implement some of the examples of her book “Long-lived software systems” (available only in German) with the structural analysis tool jQAssistant. Especially the visualizations of the dependencies between different business subdomains seemed like a great starting point to try out some stuff…
Recently I came over a great visualization of imported classes by one class made by Mike Bostock with his Hierarchical Edge Bundling in D3. I wondered how hard it would be to reimplement this visualization with jQAssistant and Neo4j and show actual dependencies between Java types. So let’s have a look!