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.
Tag: <span>graphs</span>
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.
A look at the most popular graphs in Understand, from Architecture Graphs to UML.
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.
Showing references in Understand graphical trees is a great way to hone in on the calls that built the tree as you debug or try to comprehend source code.
The first rule of being in a hole is to stop digging. Ken shows how to use architectures to identify the areas of your code using problematic function
Adding a bit of human knowledge to the automatically built Directory Structure architecture can improve its visual appeal and utility quite a bit.
Use”Relationship” graphs, which draw sub-graphs between entities, to break big graphs into little graphs and work your way thru them – turning a big thorny graph into a few easy-to-follow graphs.