Category: <span>Code Visualization</span>

Analyzing how a CMake-based project has changed over time (Part 1 of 5). This article focuses on getting the project to build successfully, both for the current state of the code and the 4-year-old initial version of the code.

Understand is used to determine how much work it would take to create a database that reads files from a git repository.

An advanced workaround for visualizing graphs when the layout fails – and I use it to fix a bug in the UML Class Diagram.

Understand lets you step back and visualize exactly what parts of your code have changed and see the impact.

Understand has a lot of different graphs that use the display area quite differently. Natasha goes into detail about how we determine what to display for that critical initial view of a graph.