An advanced workaround for visualizing graphs when the layout fails – and I use it to fix a bug in the UML Class Diagram.
Tag: graphs
Visualizing Change
Understand lets you step back and visualize exactly what parts of your code have changed and see the impact.
Short-term memory overload while debugging
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.
Hyper-Xref in Understand
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.
Interesting Graphs about Your Code
A look at the most popular graphs in Understand, from Architecture Graphs to UML.
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.
Code Browsing using Graphical Views
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.
Tracking Uses of Deprecated Code Using Architectures
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
Pro Tip: Start with Directory Structure and add some Human to it.
Adding a bit of human knowledge to the automatically built Directory Structure architecture can improve its visual appeal and utility quite a bit.