Understand Anything

ttaubek about 4 hours ago 17 commentsRead Article on github.com

FR version is available. Content is displayed in original English for accuracy.

⚡ Community Insights

Discussion Sentiment

78% Positive

Analyzed from 681 words in the discussion.

Discussion (17 Comments)Read Original on HackerNews

chromacity•about 2 hours ago

For me, practical knowledge comes from trying to figure things out. The more polished and "ELI5" the material is, the less I retain. I've played with quite a few LLM tools that promised to help me "understand anything", but I don't think they help with intuition all that much. For what it's worth, it's not an LLM-specific problem. I like YouTube content like 3Blue1Brown, but I don't think that I retained anything useful from any of it.

I don't question that LLMs are useful for answering questions about codebases, but this is closer to "turn a codebase into a curriculum", and... does that actually work?

Hunpeter•about 1 hour ago

An important tenet of modern education is that true knowledge is that which the learner (re)constructs in their mind. Heuristic learning (i.e. "trying to figure things out") is often a great way to do this.

beej71•about 1 hour ago

Definitely. As instructors, we see this in action all the time. We describe stuff in writing and in lecture, discuss it with the students, and everybody seems to have good understanding. And then we have them implement it.

And that's when the shit hits the fan. :-D Only after concerted effort do the students actually gain understanding.

prerok•about 1 hour ago

On another post I've already argued that Romans already had a proverb "Scribere bis legere." Translated, this means "writing is reading twice".

In practice, what this means is that you have to know how to reproduce the knowledge you've read, in your words. Only then can you be sure you've mastered what you've read. It's the reason for homework and all other stuff we have to do. Reading something five or more times simply does not suffice for our brains.

zaitsev1393•about 2 hours ago

Are those 9.7k real users? I mean, maybe I am too old fashioned, but whenever I tried to use such tools long before AI, it actually didn't help much. It was much easier to read the codebase and find the needed connection on my own.

It reminds me on NX graphs, which are helpful to find the circular dependencies, but other than that, doesn't provide a lot of value as I can see the same kind of structure just looking at the codebase.

Am I doing something wrong with these tools?

graypegg•about 1 hour ago

Playing amateur detective here, but "A huge thank you to the community!" blurb was added to the repo on March 20th [0], just before the hockey stick inflection point on the 21st where they got exactly 1800 more stars... then exactly 1000 more the next day, 1000 more after that, then 900... etc. [1] The only point where we see the first sig digit be NOT zero is today. Maybe there's some truncation that github does on their end for the API, but it being exactly +1000 a couple days in a row is indicative.

Wow. I thought the github clout market would be a bit more subtle about it.

[0] https://github.com/Lum1104/Understand-Anything/commit/9866fc...

[1] https://www.star-history.com/lum1104/understand-anything#his...

throwup238•about 2 hours ago

Just look at the star graph on the bottom of the readme (itself a sign of a hype driven project with little substance). I highly doubt that hockey stick is organic.

jrflo•about 1 hour ago

the hockey stick was probably from when they paid for fake stars: https://awesomeagents.ai/news/github-fake-stars-investigatio...

mert-kurttutan•about 2 hours ago

Did anyone actually use this on a complex codebase and have any kind of intuition for it ?

Like, having looked at the demo, it feels less intuitive and extra complex than going through the codebase myself with tmux + codex + reading it myself. I think for you to understand the codebase, it should be easier to interact without. This seems to introduce way too many steps to interact with the codebase

kamranahmedse•about 2 hours ago

Interesting approach. I built something similar https://github.com/nilbuild/diffity to understand unknown codebases. The difference is it gives you the interactive walk-through with mermaid diagrams, guiding you through the feature or part of the codebase that you're looking at.

victorbjorklund•about 1 hour ago

Fake GitHub stars. Move a long.

raincole•about 1 hour ago

Vibe coded projects and fake github stars. Name a more iconic dual.

analogpixel•about 3 hours ago

is this like Obsidian's graph view? Looks pretty/makes cool screenshots but has no actual value and is just cumbersome to use? (btw, this isn't meant to be a mean comment, just a question after looking at the output.)

docheinestages•about 3 hours ago

What evidence is there that this makes any difference at all? There are a gazillion (and one) codebase understanding solutions using knowledge graphs. How do I know if it's any good compared to just using Codex or Claude Code?

darshanmakwana•about 2 hours ago

It depends on an individual's personal taste of how he/she understands things, some people like to YOLO and tinker while some like to read docs first before looking at any code and some like to do both synchronously. To me it seems the reason why there is no basis that one solution works better than others is exactly why it's easy to make trending/popular repos these days

m3kw9•39 minutes ago

A big az graph with 100s of spagatti nodes is the kind of learning I try to avoid. Is better to just ask directly, "where do i start?", "teach me about...". This is over engineered education.

beepbooptheory•about 1 hour ago

Provocative title, then seeing the like 8+ dot folders in the repo really made this seem like some kind of obscure satire at first.