Hacker News

Article URL: https://github.com/teddytennant/wizard

Comments URL: https://news.ycombinator.com/item?id=48845182

Points: 1

# Comments: 1

Article URL: https://www.backblaze.com/blog/backblaze-drive-stats-for-q1-2026/

Comments URL: https://news.ycombinator.com/item?id=48845161

Points: 1

# Comments: 0

Article URL: https://homosabiens.substack.com/p/listen-youre-probably-not-good-at

Comments URL: https://news.ycombinator.com/item?id=48845158

Points: 1

# Comments: 0

Article URL: https://github.com/sgInnora/wc2026-prediction-ledger

Comments URL: https://news.ycombinator.com/item?id=48845154

Points: 1

# Comments: 0

Article URL: https://link.springer.com/article/10.1007/s10071-026-02048-2

Comments URL: https://news.ycombinator.com/item?id=48845145

Points: 1

# Comments: 0

One of the things I do when approaching a new codebase is to find the entry points and start exploring down the call paths. This gives a good overview of the different components in the code and how they're connected. I wanted to translate that to a visual experience, similar to how you would use call graphs, but there's a couple of problems with classical call graphs. One, call graphs represent flow at the function level, so the architectural context is lost. And call graphs tend to get very large and can grow exponentially with program size.

The approach I'm exploring is to construct "multi-level" call graphs. These are call graphs represented in the form of program structure showing control flow not just at the function level, but rolled up to higher level units such as classes and packages. This gives you the ability to zoom in and out and see your code at different levels of abstraction, à la C4 diagrams, allowing you to navigate large graphs by expanding the areas you care about and collapsing the rest.

The graph is then fed to an LLM for semantic analysis. This does two things, detects telemetry, trivial utilities to strip them out of the graph further condensing it, and identifies external interfaces and dependencies to enrich the graph. The result is a single graph which incorporates both structural and behavioral aspects. You can see package level dependencies, class composition and relationships, as well as external services, databases and user interactions. Think of it as a package diagram + class diagram + use case diagram combined into a single composite diagram.

Of course, ultimately source is king. There is no substitute for reading code to understand the details of what it is doing. But a map doesn't replace the terrain, it tells you where to walk. As we shift from hand coding each line to orchestrating agents that are generating all the code, maintaining the "big picture" becomes ever more important. We need better maps to help us navigate the terrain.

I would love to hear what you think though. Do check out some of the example diagrams in the link [1] and share your feedback. Also interested in your general thoughts on program comprehension!

[1] Link: https://arcaide.foo

Comments URL: https://news.ycombinator.com/item?id=48845142

Points: 2

# Comments: 0

Article URL: https://twitter.com/i/status/2075161900275360076

Comments URL: https://news.ycombinator.com/item?id=48845140

Points: 2

# Comments: 0

So, I have a Lenovo Idea Tab (11") tablet where I don't use a Google account, and several Google apps are disabled including the Play Store. I use Aurora Store and F-Droid to install and update packages. Only time I enable Play Store is to install an update to Play Services because Aurora Store can't (conflicting packages, meaning the signing key of the Play Services package has changed). I keep it disabled because it ignores the 'Don't Auto-update Packages' setting and updates Google apps packages updates without permission (and sometimes re-enables them)...

What does show up as an update in Aurora? The Android Developer Verification package. Of course I immediately blacklisted it. Possible avenue to not install it?

Don't know if this will really stop it but it will be an interesting experiment. Will let you know in the near future.

Discuss.

Comments URL: https://news.ycombinator.com/item?id=48845131

Points: 2

# Comments: 0

Article URL: https://eqrion.net/ten-years-at-mozilla/

Comments URL: https://news.ycombinator.com/item?id=48845113

Points: 2

# Comments: 0

Article URL: https://github.com/vercel-labs/native

Comments URL: https://news.ycombinator.com/item?id=48845084

Points: 2

# Comments: 0

Article URL: https://carter.sande.duodecima.technology/inline-script-pitfalls/

Comments URL: https://news.ycombinator.com/item?id=48845075

Points: 2

# Comments: 0

Article URL: https://futurism.com/future-society/executives-corporations-ai-bills-metered-billing

Comments URL: https://news.ycombinator.com/item?id=48845070

Points: 3

# Comments: 0

Article URL: https://transformer-circuits.pub/2026/workspace/index.html

Comments URL: https://news.ycombinator.com/item?id=48845069

Points: 2

# Comments: 0

Article URL: https://calnode.com/

Comments URL: https://news.ycombinator.com/item?id=48845065

Points: 3

# Comments: 0

Article URL: https://apps.apple.com/us/app/snapid-object-identifier/id6761325361

Comments URL: https://news.ycombinator.com/item?id=48845059

Points: 2

# Comments: 0

Article URL: https://www.bloomberg.com/news/articles/2026-07-09/wall-street-banks-miss-multibillion-dollar-ai-deals-in-hong-kong

Comments URL: https://news.ycombinator.com/item?id=48845056

Points: 2

# Comments: 0

Article URL: https://18words.com/

Comments URL: https://news.ycombinator.com/item?id=48845049

Points: 10

# Comments: 0

Article URL: https://claude.com/blog/a-field-guide-to-claude-fable-finding-your-unknowns

Comments URL: https://news.ycombinator.com/item?id=48845045

Points: 2

# Comments: 0

Article URL: https://gomakethings.com/articles/generative-colors-with-css/

Comments URL: https://news.ycombinator.com/item?id=48845017

Points: 3

# Comments: 0

Article URL: https://dkryaklin.com/blog/colordx-gpu

Comments URL: https://news.ycombinator.com/item?id=48844554

Points: 1

# Comments: 0