Project Visualization

Consider this: You've bought Sad Cows new game and want to study the brilliant source code.
How do you visualize the project and read the source?

I usually open the folder in an editor which displays it in a TreeView. Alternatives include clicking through the file explorer with file preview enabled or typing cat **.

I'm frustrated and feel like this is a archaic and inefficient method to understand a large tree structure.

Sad Cow's psychopatic source code is of no interest to me

Build a tiny search engine i guess

first pass could pick up all user-defined functions, second pass to learn the function-function pathways

functional theory? borrowing a bit from graphs, not sure if it's fully consistent

leaf functions - doesn't call any other
pipe functions - calls a number of leaf and/or another single pipe
branch - calls more than one pipe
trunk - calls one or more branches
stump - called from main

But Sad Cows won't finish his's game

Ha! Turns out there's work in that area: sourcetrail.

Exactly what I imagined.

Like >>3 I don't believe I'd be willing to study the psychopathic source code. If I had an undocumented huge ass project to study, I'd generate diagrams and flowcharts for all interfaces, classes, methods... but it's all so tiresome. Edited on 04/05/2020 05:42.

Like >>3 I don't believe I'd be willing to study the psychopathic source code. If I'd have an undocumented huge ass project to study, I'd generate diagrams and flowcharts for all interfaces, classes, methods... but it's all so tiresome.
Like >>3 I don't believe I'd be willing to study the psychopathic source code. If I had an undocumented huge ass project to study, I'd generate diagrams and flowcharts for all interfaces, classes, methods... but it's all so tiresome.

Open the file in text editor
Just double click it
HIBT?