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.
If you hover over your code in Understand it will tell you all sorts of things about what you are hovering over.
A long, and growing, list of dinner party conversation reasons Ken gives for why customers use Understand.
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.
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.
They are nice. They care about the places they’ve worked/studied. They are interested in computer science.