[OC] I mapped my Unity C# codebase as a taxonomy instead of a dependency hairball

Hi,

I am a developer of DAWG – Digital Audio Workstation Game, a project I am working on for the last few months that is made in Unity with C#

Because DAW style software is very sensitive, I wanted a way to understand and maintain the structure of the codebase over time. In a project like this, architectural problems do not stay isolated for long, they tend to show as timing issues, DSP issues, bugs, and general decay of the system.

In line with main project DAWG I was working on a project called LDF – Living Document Framework, which is basically a framework I designed for myself so I can keep track of the codebase, architecture, decisions, invariant,…

Since I had pretty good knowledge about relations between the files in the codebase I was thinking how to display the knowledge on the graph, without beeing a hair ball and also while accounting the codebase architectural desing in the mix.

I come to a conclusion that taxonomy is working for nature, so why it should not work on the codebases too.

End result is visualization of different taxonomy levels, but adapted to my codebase writen in C# for Unity.

You can check the attached pictures, and I can also make a video so you can see how it works in real time.

Happy to answer any question about visualization, its functions or the architecture of the codebase.

I see pictures are ugly, will change then shortly!