Programming is all about detail so when looking at even simple code it can be bloated with irrelevant stuff, logging, error handling, comments.
Often, nitty gritty details hides the true purpose of a piece of code. So being able to navigate through souce code you need to understand what highlevel and lowlevel abstractions are made when designing and implementing the software.
In SEAMCAT we have abstractions like Systems, Simulations, Antennas and plugins but we need to have a good mental picture of how they relate to each other.
With SEAMCAT you can setup victim, setup a number of interferers, define interference properties, control the number of snapshots, simulate and inspect the collected results after the simulation. This is nothing new to a seasoned SEAMCAT user but that does not really help when the source code is to be navigated.