WillMcCall

6 ms·

1. 1.▲
   by WillMcCall 10mo ago

   Glad you liked it!
2. 2.▲
   by WillMcCall 2y ago

   Makes total sense, and sorry to hear about the incident. At the moment, closed source models are the only viable way to generate high quality diagrams. Once that changes, we'd prefer to switch to open source too for many of the reasons
3. 3.▲
   by WillMcCall 2y ago

   Thanks for the feedback! A fully local stack would give control back to developers, which we would love to do once open source model performance improves. Hoping we can change your mind on the value of navigating and editing code with vis
4. 4.▲
   by WillMcCall 2y ago

   The call graph doesn't highlight dead code specifically, but unused blocks are manually identifiable through isolated/broken chains. Is this something you'd like to see?
5. 5.▲
   by WillMcCall 2y ago

   Glad you see the potential! We do have an existing function "call graph" view that uses traditional static analysis methods with LSP calls. Augmenting this view with LLMs seems very promising, and we are very much headed in that
6. 6.▲
   by WillMcCall 2y ago

   That makes sense, we'll make this change!
7. 7.▲
   by WillMcCall 2y ago

   Curious to learn more about the project, what were you working on? We're not hiring at the moment, but let's stay in touch!
8. 8.▲
   by WillMcCall 2y ago

   Definitely an interesting thought, although we wouldn't be able to support any UI/UX. We could host a separate utility and expose endpoints for UML or markdown though.
9. 9.▲
   by WillMcCall 2y ago

   This sounds like an ambitious project with a number of interesting technical challenges. It may be some time before the tooling will exist to support your use case, but then again, you can always build custom tooling of your own! It's
10. 10.▲
    by WillMcCall 2y ago

    Thanks for the feedback and resources! In designing CodeViz we were inspired by the Maya hypershade, which closely resembles the diagram-based blender tool that you shared. https://help.autodesk.com/view/MAYAUL/202
11. 11.▲
    by WillMcCall 2y ago

    Re: Edit The top level categorizations are indeed fixed, however the nodes themselves can be arbitrary. We've found this helps with grouping and organization while still allowing for the flexibility required to accommodate different s
12. 12.▲
    by WillMcCall 2y ago

    Yes of course, Let's set up some time to chat! Looks like a great tool!
13. 13.▲
    by WillMcCall 2y ago

    Sounds good, thanks for the feedback! Would open-sourcing CodeViz change your willingness to give it a try? Definitely agree that rigor is a tricky term here, do you think the open-ended nature of C4 diagrams is a feature, not a bug? We&
14. 14.▲
    by WillMcCall 2y ago

    Great points/questions. I suspect that information relevant to codebase architectures follows the 80/20 principle. For example, a router and index file in a React App will usually give you around 80% of what's needed to inf
15. 15.▲
    by WillMcCall 2y ago

    The lines represent a connection or interaction between different parts of the codebase. Most often these are dependencies like you mentioned, but a "dependency" could be a parent-child relationship, API call, imported function,