[HN Gopher] Tools for visualizing a codebase
       ___________________________________________________________________
        
       Tools for visualizing a codebase
        
       Author : tslmy
       Score  : 31 points
       Date   : 2022-04-02 20:03 UTC (2 hours ago)
        
 (HTM) web link (lmy.medium.com)
 (TXT) w3m dump (lmy.medium.com)
        
       | vaidik wrote:
       | Try Cidescene.io
        
       | TacticalCoder wrote:
       | A dependency structure matrix is a nice tool to have for some
       | languages too (used to worked fine from IntelliJ for Java at
       | least 10 years ago and I bet it still does).
        
       | adhesive_wombat wrote:
       | CMake can also generate a graph of the targets with graphviz,
       | which can be very useful (and also make horrible things like
       | cyclic linkages evident).
        
       | ilovecaching wrote:
       | Anyone know of some tools that could draw graphs of the Linux
       | kernel ? I'd like to draw subsystems or pick a function and have
       | it diffuse out to build a graph.
        
       | jdougan wrote:
       | For a more dynamic moldable approach, look at Moose.
       | https://moosetechnology.org/
        
       | rajandatta wrote:
       | Ver helpful post. This is an under-covered topic especially for
       | large code bases.
       | 
       | Anyone aware of efforts to pair these tools with tools to filter
       | and examine different call paths to interactively explore a large
       | code bases. A model like specifying a filter and having the view
       | be filtered by paths that meet criteria.
        
       | possiblydrunk wrote:
       | Back in the day, Visual Age for Java (IBM) had a cool dynamic
       | call graph visualization tool. Would be great if companies
       | released their tool sources when they abandon them.
        
       | cc101 wrote:
       | You should have a QuickStart. Use the ReadMe to explain what the
       | QuickStart does. Then, use the QuickStart as a skeleton on which
       | to elaborate things not covered.
        
         | tslmy wrote:
         | Good idea! I should learn about the conventional sections in
         | repo documentations.
        
       ___________________________________________________________________
       (page generated 2022-04-02 23:00 UTC)