Tag: <span>engineer</span>

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.

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.