Live data from Hacker News

Show HN: Visualizing a Codebase

octo.github.com

71–80 of 101 posts

Re: Show HN: Visualizing a Codebase

#71

This is cool but using rectangles instead of circles would help this visualization. Circles waste real estate and not friendly to labels (e.g. curved text that is harder to read)

Agree on this. Rectangles can also be aligned and given a logical order. It’s probably less nice to the eye than circles, but more useful.

Re: Show HN: Visualizing a Codebase

#72
That's the same visualisation used by CodeScene (https://codescene.com/how-it-works/), but there is a more elaborate one that represents affinity (number of connections) as distance to create something like a geographical map: https://homepages.ecs.vuw.ac.nz/~craig/publications/vissoft2...

Re: Show HN: Visualizing a Codebase

#74
post #65
post #42

Apologies for the hot take, but imo GitHub has been really knocking it out of the park with terrible ideas lately (remember how everyone fell all over themselves during the Copilot release?). This is an absolutely worthless visualization that only impresses those that haven't heavily worked with visualizations. A few points right off the bat: - Labels are way too small, so you'll need to zoom in.. - ...but if you zoo…

This is a Show HN post. While you have valid criticisms (small labels, using filenames as labels produces lots of package.json, etc.), the way you shared it certainly violates the site guidelines (“Be kind”). You knew you were being harsh and let your emotional response get to you. But, you should remind yourself that a person was on the other side of this post, and she cared enough to share it. Even if you feel the…

Way back when I was in school and much less confident than I a now, it was actually comments like yours that hurt the most. What you're essentially saying is "I know what was said is true and I don't dispute that, but you shouldn't have said it".

For me this was like a second blow. Criticism always hurts, but at least the first guy thought I was tough enough to take it. You, on the other hand, not only agree with the first guy, you think I'm so feeble that I need a "nice" person like you to shield me.

When people stick their neck out they will sometimes get hurt. This is totally normal and a natural way of learning and developing. Safe spaces don't make successful people. The comment you are replying to didn't even seem emotional to me and certainly didn't attack the person. It was just honest feedback.

Re: Show HN: Visualizing a Codebase

#75

Earlier quoted context omitted.

The guy literally says he timeboxed his exploration on this experiment . I think it's pretty cool and would love to have the option to navigate repositories like this.

Author is a woman.

Sex is irrelevant.

Re: Show HN: Visualizing a Codebase

#77
I find that it's useful not just to look at the current contents of codebase, but how it has evolved over time. For example, after being onboarded, this lets me see where most of the current effort on a codebase is concentrated and what the biggest recent changes have been.

For this, i believe that Gource is a lovely tool, which you can just point at a Git repository and it will visualize it: https://gource.io/

Re: Show HN: Visualizing a Codebase

#78
I like the quick insights I can gain from this! Very promising. It's very basic in it's current implementation but I see a lot of potential specially about the "how files are linked" part.

It's a nice bird's eye view. One thing I'd like is for there to be multiple metrics to use for the size of packages e.g. lines of code, number of files, number of methods etc.

That way you can make sense of what are the heavyweight parts of the codebase.

Re: Show HN: Visualizing a Codebase

#80
post #42

Apologies for the hot take, but imo GitHub has been really knocking it out of the park with terrible ideas lately (remember how everyone fell all over themselves during the Copilot release?). This is an absolutely worthless visualization that only impresses those that haven't heavily worked with visualizations. A few points right off the bat: - Labels are way too small, so you'll need to zoom in.. - ...but if you zoo…

https://news.ycombinator.com/newsguidelines.html

> Be kind. Don't be snarky. Have curious conversation; don't cross-examine. Please don't fulminate. Please don't sneer, including at the rest of the community.

> When disagreeing, please reply to the argument instead of calling names. "That is idiotic; 1 + 1 is 2, not 3" can be shortened to "1 + 1 is 2, not 3."

> Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith.

Post reply on HN