Interesting idea - I'm not sure this is quite the right approach but I like the idea of pivoting from the standard filesystem view of code.
In olden procedural times utilities that showed how routines related were genuinely useful in helping build a mental map but became rather redundant as calls moved from static to dynamic and then to objects.
One counter argument to showing an alternative view is that in a well designed app the file layout represents a mix of specific application and general development models of behaviour and functionality, so is adequate (if not optimal) and standard for a reason.
Interesting idea - I'm not sure this is quite the right approach but I like the idea of pivoting from the standard filesystem view of code.
In olden procedural times utilities that showed how routines related were genuinely useful in helping build a mental map but became rather redundant as calls moved from static to dynamic and then to objects.
One counter argument to showing an alternative view is that in a well designed app the file layout represents a mix of specific application and general development models of behaviour and functionality, so is adequate (if not optimal) and standard for a reason.