If you want to make smarter, safer, and testable changes you need to know exactly where what you are changing will affect. Hyper-Xref technology, and the GUI and API/DevOps tools in Understand make you a safer, smarter engineer less likely to add bugs as you change code.
Author: Ken Nelson
Help your future self… write code not “magic”
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.
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.
Browsing Code with Tired Eyes
You are tired. Your eyes are old. Or you just have bad eyes. You CAN change the font look/size for most of Understand’s interface easily and press on!
Analyzing Makefile Based Source Code
We use “bear”, an open-source tool, to watch builds from a Makefile built project (bitcoin) and create a very useful Understand parse with it.
Understand’s most useful and smallest button
The button controlling how the Information Browser shows references packs a big punch in just 25 pixels.