Using unexplained numbers makes your code hard to understand, and difficult to adapt and extend. Static analysis tools like Understand can find them, but take care fixing them.
Why swing just one hammer…oops IDE?
Humans didn’t stop needing special tools when they started editing code. Your time and brain are special – use the right tool for the job.
Precise Searching for Smarter Changes
Using precise cross-references from static analysis tools like Understand tells you exactly where to look both for direct implications of what you are about to change and also, importantly, for subsequent impacts or side-effects of those changes
Our Favorite Computer Science Quotations
An ever growing list of quotations about computer science, with an emphasis on software maintenance
Why use Understand? (Dinner Party edition)
A long, and growing, list of dinner party conversation reasons Ken gives for why customers use Understand.
Licensing Understand As You Grow
Understand has a very flexible licensing system that can adapt and grow with your project. It supports single users or groups and works in online and offline environments.
Blame Can Be Good
A bug in the control flow graph is solved using the Git blame margin in Understand to quickly find a related fix in a recent commit.
Making Graphs Interesting
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.
Useful Scripts: Scanning source code for profanity
Using this custom Python script with Understand, you can quickly scan your project for instances of profanity and scrub them clean.
Making sense of GIT source code
Making a functional decomposition architecture of the source for GIT helps me understand code that is new to me much better while also making an upcoming deeper analysis more organized, clear, and concise.