Use These 5 Tips to Help You Visualize Code
Use These 5 Tips to Help You Visualize Code
When building a codebase, make sure to look out for ways to make it easier and to help yourself reason clearly about your code.
Join the DZone community and get the full member experience.Join For Free
The Agile Zone is brought to you in partnership with Techtown Training. Learn how DevOps and SAFe® can be used either separately or in unison as a way to make your organization more efficient, more effective, and more successful in our SAFe® vs DevOps eBook.
Source code doesn't have any physical weight - at least not until you print it out on paper. But it carries a lot of cognitive weight. It starts off simply enough. But before long, you have files upon files, folders upon folders, and more lines of code than you can ever keep straight. This is where the quest to visualize code comes in.
The solution file and namespaces organization make for a pretty unhelpful visualization aid. But that's nothing against those tools. It's just not what they're for. Nevertheless, if the only way you attempt to visualize code involves staring at hierarchical folders, you're gonna have a bad time.
How do most people handle this? Well, they turn to whiteboards, formal design documents, architecture diagrams, and the like. This represents a much more powerful visual aid, and it tends to serve as table stakes of meaningful software development.
But it's a siren song. It's a trap.
Why? Well, as I've discussed previously, those visualization aids just represent someone's cartoon of what they think the code will look like when complete. You draw up a nice layer-cake architecture, and you wind up with something that looks more like six tumbleweeds glued to a barbed wire fence. Those visual aids are great...for visualizing what everyone wishes your code looked like.
What I want to talk about today are strategies to visualize code - your actual code, as it exists.
Generate Class Diagrams
Whoa, whoa. Put down your pencil or whiteboard marker. I'm not reversing myself immediately and suggesting that you hand-draw some UML. I'm talking about actually creating class diagrams from your code.
Using this functionality, you can literally drag and drop your classes onto a canvas and start creating relationships between them. You can model both inheritance schemes and relationship cardinality. This represents a vast improvement over following chains of inheritance across multiple files or taking notes to understand how a sequence of types relates.
Plus, unlike its hand-drawn cousin, this lightweight use of UML stays in sync with your code. This helps a lot with visualizing your class relationships.
In-Editor Coverage Visualization
This tip is less about visualizing relationships among code elements and more about visualizing how comprehensive your automated tests are. Surely you've heard of test coverage. There's even a good chance management somewhere has bludgeoned you with it a bit.
But what everyone is after there is a number - a percentage. Get your code coverage up to 80% or whatever. That's no help for visualization.
Luckily, Visual Studio offers an option to help turn that number into something immediately useful to you. You can select an option to paint the editor with different colors for covered and uncovered lines. This means that you can glance through your files and easily visualize where your tests reach and where they don't.
Of course, you have a more powerful option for this particular visualization as well. I'm a huge fan of NCrunch, which continually runs your tests, updates coverage data, and paints the IDE accordingly.
Heat Maps and Hot Spots
Since I originally wrote this for the NDepend blog, it'd be pretty weird if I didn't mention an NDepend feature or two. Well, fear not. Here that comes.
One your most powerful options to visualize code is the NDepend heat map. Here's an example.
NDepend lets you compute all sorts of metrics about your code. But without visualization, those metrics are just dusty data points hiding on your build server somewhere.
When you take them and plug them into a heat map, they come to life. You can pick a metric to use to vary box size and another to use to vary the color. This gives you striking visual representations of hot spots in your code: excessively complex methods, lots of dependency risk, CRAP-y code, etc.
As the expression goes, a picture like this is worth a thousand words when trying to visualize code.
Once you've figured out strategies to turn code metrics into visual representations of your codebase, you can realize another powerful visualization. This time I'm talking about the idea of trend metrics.
It's easiest to reason about our code by discounting any time other than the present. After all, as I mentioned before, codebases are already insanely complex and hard to picture without adding an entire other dimension to the mix. And yet, that dimension is critically important. Sure, your code has problematic pockets of cyclomatic complexity. But does it have more pockets than it did last month, or does it have fewer? That's an enormously important distinction.
Trend graphs let you visualize properties of code as they vary through time. Here are some examples that might interest you:
- Are we maintaining a consistent level of test coverage?
- Is our code growing more complex, normalized by codebase size, or are things getting more snarled?
- What is the ratio of nodes to edges in our dependency graph (more on this shortly)?
- What is the type rank of our top 20 types?
You get the idea. It's one thing to keep track of this. But it's another altogether to visualize it with graphs over the course of time as you work in the codebase.
The last tip that I'll offer is the one that I find to be the most crucial of all. I'm talking about the dependency graph. If you take nothing else away from this post, take away that it is utterly critical that you get a visual bead on how your code interrelates.
I once saw an actual dependency graph in the wild that looked like this.
You just see that giant mass of nodes, but if you could zoom in at the incredible magnitude, the edges put them to shame. I can't show you that because you'd need a mural-on-a-building-sized screen to get enough resolution. That's how jaw-droppingly snarled this code was.
How do you think that happens? I'll bet the people responsible have some impressively layered diagram somewhere of what this should look like. But it came to look like this instead. That happens because nobody's visualizing the real deal and incorporating that feedback into the development effort.
Your code's dependency graph models how things interrelate. Most commonly, you'll view this at the assembly level or (in the case above) at the namespace level. It shows you how all of the parts fit together when push comes to shove.
Use the dependency graph to inform you as to whether you're actually building something that's loosely coupled, rationally organized, and easy to maintain.
I've given you five tips here on how to visualize your code. But there are no real definitive or canonical approaches. You have to get creative both with tooling and with your own imagination when you try to visualize code.
Building codebases is difficult and complex. Forming a clear mental image of them is even more so. Make sure always to be on the lookout for ways to make it easier and to help yourself reason clearly about your code.
Published at DZone with permission of Erik Dietrich , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.