Analyzing how a CMake-based project has changed over time (Part 4 of 5). This article focuses on creating a trendline of changes to avoid the artifacts caused by non-linear history.
Tag: power user
CMake Compare Part 3: Violation Trends
Analyzing how a CMake-based project has changed over time (Part 3 of 5). This article focuses on creating a CodeCheck Violation trend line from multiple databases representing different time points in GitAhead.
CMake Compare Part 2: Automation
Analyzing how a CMake-based project has changed over time (Part 2 of 5). Using command-line tools to create hundreds of comparison databases and constructing a trend line of analysis errors over time
CMake Compare Part 1: Creation
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.
Where to start?
Understand makes it easy to know where to start looking to track down a bug, Find where to place breakpoints, and identify which locations in the code need to be updated.
Git Comparison Projects
You can now create Understand Comparison Projects directly from git
How Hard is it?
Understand is used to determine how much work it would take to create a database that reads files from a git repository.
Minimize the Impact of Interruptions
Now you keep interruptions from ruining your thought process in Understand. Session Browser lets you save your work, explore something completely unrelated, and then switch back to where you were.
Short-term memory overload while debugging
The decisions you make while thinking about code are far too complicated to trust to memory. Ken shows how Understand helps you not rely on short term memory and walk code in an organized fashion that misses nothing.
2 Uber Fast Ways to Browse Your Code
In this short video, Ken shows you two similar but crucially different fast ways to browse code in Understand.