Weidenwalker
Joined 9 years ago
Karma
95
Submissions
22
Member since
Mar 23
Recent submissions
Comment · 2 years ago
Comment · 2 years ago
If you enjoyed Permutation City, you‘d probably also like „The Metamorphosis of Prime Intellect“ by Roger Williams!
It explores a similar premise of a post-singularity future (though the mechanism is superintelligence rather than cellular automata/mind uploading), but rather than imagining exactly how we‘d get there, it tries to imagine what human flourishing would look like in a world of perfect abundance!
Comment · 2 years ago
Ooops, I should take more care pasting links from markdown, this one works: https://codeatlas.dev/gallery
Comment · 2 years ago
This is cool, basically the first 3D codebase visualization I've seen that doesn't immediately give me a headache, so good job! :)
Always interesting to see different ways of visualising the same thing. A while ago my friend and I also made a codebase visualisation tool ([https://www.codeatlas.dev/gallery](https://www.codeatlas.dev...), but instead of taking the graph route, we opted for Voronoi treemaps in 2D! It's a tradeoff between form and function for sure, modelling code as a DAG is definitely more powerful for static analysis. However, in most graph-based visualizations (this, gource) I just find myself getting lost super quickly, because the shapes are just not very recognisable.
Really impressed by how polished this already is, nice docs, on-the-fly rendering, congrats!
If I ever find time to work on codebase visualisation again, I might have to steal the idea of codebase entropy to better layout which files to place close to which others!
Comment · 3 years ago
Nice post - treemaps are great!
My friend and I made a codebase visualisation tool (https://www.codeatlas.dev/gallery) that's based on Voronoi treemaps, maybe of interest as an illustration of the aesthetics with a non-rectangular layout!
We've opted for zooming through double-clicks as the main method of navigating the map, because in deep codebases, the individual cells quickly get too small to accurately target with the cursor as shown in the key-path label approach!
If anyone's interested, this is also available as a Github Action to generate the treemap during CI: https://github.com/codeatlasHQ/codebase-visualizer-action
Comment · 3 years ago
If you find this type of codebase visualisation useful, you might want to checkout codeatlas.dev and its Github Action (https://github.com/codeatlasHQ/codebase-visualizer-action). It doesn't animate the repo over time like gource (yet), but instead aims to give a beautiful interactive visual snapshot of a repo at a particular point in time. It also lets you zoom in on specific aspects like recent commit activity, programming language and hopefully in the future test coverage.
E.g. see here for a visualisation of the pytorch codebase we did a while ago: https://codeatlas.dev/gallery/pytorch/pytorch
(disclaimer: I'm the author)
Comment · 3 years ago
I visualized this codebase here: https://codeatlas.dev/github/codeatlasHQ/the-algorithm/main
Maybe this is helpful to anyone for navigating what's in there!
Comment · 3 years ago
If you think this is useful, you might also like codeatlas.dev and its Github Action (https://github.com/codeatlasHQ/codebase-visualizer-action). It currently does not support per-contributor activity, but we put a lot of effort into making the diagrams beautiful to look at and the basic approach of using treemaps for visualisation seems very similar. In fact, could be cool to collaborate on this, DM me if interested!
Comment · 3 years ago
https://codeatlas.dev - codebase visualisation tool
Takes your git repo and generates a beautiful visual representation of the code. Sort of an alternative navigation tool (in addition to IDEs) for large codebases. Can also run it as part of CI with our Github Action (https://github.com/codeatlasHQ/codebase-visualizer-action).
We made this because grokking complex software projects is really difficult and we've found that a visual overview of what's in a codebase can be quite helpful to get started.
E.g. checkout https://codeatlas.dev/gallery/kubernetes/kubernetes for the generated visualisation of the Kubernetes Github repo!
Currently making -10$/year to pay for the domain :D We slowed down active development after our initial attempts at dissemination didn't really go anywhere (bragging about side projects on the internet, ugh), but I'm still really keen on getting some feedback on whether this is actually useful to anyone else!
Note: The site works somewhat on mobile, but is much better on desktop!
Also, funny there's a post like this again, just like https://news.ycombinator.com/item?id=34531989 yesterday.
Comment · 3 years ago
https://codeatlas.dev - codebase visualisation tool
It takes your git repo and generates a beautiful visual representation of the actual code that's in it. Sort of an alternative navigation tool (in addition to IDEs) for large codebases. You can run codeatlas as part of your CI with our Github Action (https://github.com/codeatlasHQ/codebase-visualizer-action).
We made this because grokking complex software projects is really difficult and we've found that a visual overview of what's in a codebase can be quite helpful to get started.
E.g. checkout https://codeatlas.dev/gallery/kubernetes/kubernetes for the generated visualisation of the Kubernetes Github repo!
We slowed down active development after our initial attempts at dissemination didn't really go anywhere (bragging about side projects on the internet, ugh), but would still love feedback on whether this is possibly useful to anyone else!
Note: The site works somewhat on mobile, but is much better on desktop!
Comment · 4 years ago
Previous discussions for context:
- Our initial Show HN post: https://news.ycombinator.com/item?id=30430165. The previous post was only showing our static gallery - we've since turned this into a GitHub Action that can visualize any repo as part of CI, so thought a repost was warranted
- Discussion about visualizing software in general: https://news.ycombinator.com/item?id=31569646
- Discussion about a similar project by Github Next, using a different approach to generate the diagrams: https://news.ycombinator.com/item?id=28074827
Comment · 4 years ago
Hmm - at some point we'll have to think about how fund further development, but the current plan for the github action is for it to be open-source (under a BSL-like license) and free to use!
Comment · 4 years ago
Huh, I hadn't thought about it that way - you're right, infrequent changes could indeed be a good proxy for stability! (or for "dead-and-forgotten" :D)
Complexity is an interesting measure too - I'm currently not sure how we'd model this, but this could definitely help codeowners understand which parts of their codebase is currently difficult for people to wrap their heads around. Or whether there's any complex parts that there's only a single contributor to, without whom the project would be left with a serious knowledge gap.
Once this can run as part of a CI pipeline and thus lives directly in the repo, I'd also love to add an overlay with the output of the testsuite to see which parts of the codebase aren't covered by tests! Or the output of a profiler, to see which functions are actually called the most.
The 2022 edition isn’t so much about LLMs as about image generation with stable diffusion, but the underlying techniques are still foundational enough to be generally useful. YMMV, but for me building things from scratch, even if results don‘t reach SOTA, is the single most effective way to learn what‘s really going on.