HN user

billyp-rva

494 karma

Building Ilograph: https://www.ilograph.com

Posts29
Comments80
View on HN
app.ilograph.com 10d ago

Yt-Dlp Sequence Diagrams

billyp-rva
105pts32
app.ilograph.com 15d ago

Yt-Dlp Sequence Diagrams

billyp-rva
1pts0
app.ilograph.com 22d ago

Yt-Dlp Sequence Diagrams

billyp-rva
5pts0
www.nytimes.com 2mo ago

What AI Did to My College Class

billyp-rva
17pts1
www.ilograph.com 3mo ago

Why we create architecture diagrams (2022)

billyp-rva
2pts0
www.ilograph.com 4mo ago

More common mistakes to avoid when creating system architecture diagrams

billyp-rva
249pts70
www.ilograph.com 4mo ago

More common mistakes in architecture diagrams to avoid

billyp-rva
2pts0
app.ilograph.com 5mo ago

Visualizing one system 11 ways

billyp-rva
2pts0
www.ilograph.com 6mo ago

Avoiding fan traps in database design and system diagrams

billyp-rva
34pts4
www.ilograph.com 6mo ago

Avoid fan traps in system diagrams

billyp-rva
1pts0
www.ilograph.com 7mo ago

Avoid fan traps in system diagrams

billyp-rva
2pts0
app.ilograph.com 7mo ago

Visualizing recursive merge sort, recursively

billyp-rva
1pts0
app.ilograph.com 7mo ago

Visualizing recursive merge sort, recursively

billyp-rva
1pts0
app.ilograph.com 8mo ago

Recursive merge sort as a recursive sequence diagram

billyp-rva
1pts0
www.ilograph.com 9mo ago

Fixing AWS Architecture Diagrams: AI Document Processing

billyp-rva
1pts0
www.ilograph.com 9mo ago

Fixing AWS Architecture Diagrams: AI Document Processing

billyp-rva
1pts0
app.ilograph.com 10mo ago

In-depth system walkthrough: cloud-native A.I. document processing

billyp-rva
1pts0
www.ilograph.com 10mo ago

Fixing AWS Architecture Diagrams: AI Document Processing

billyp-rva
3pts0
app.ilograph.com 10mo ago

In-depth system walkthrough: serverless intelligent document processing

billyp-rva
1pts0
app.ilograph.com 1y ago

Fibonacci(50) as a Fractal Sequence Diagram

billyp-rva
7pts0
app.ilograph.com 1y ago

In-depth system walkthrough: cloud-based VOD

billyp-rva
13pts3
app.ilograph.com 1y ago

System Deep Dive: VOD processing, transcoding, and delivery

billyp-rva
1pts0
www.ilograph.com 1y ago

Breaking Up the Master Diagram

billyp-rva
2pts0
www.ilograph.com 1y ago

Diagrams AI can, and cannot, generate

billyp-rva
214pts68
www.ilograph.com 1y ago

Breaking Up the Master Diagram

billyp-rva
1pts0
www.ilograph.com 1y ago

Common mistakes in architecture diagrams (2020)

billyp-rva
201pts72
www.ilograph.com 1y ago

Breaking Up the Master Diagram

billyp-rva
1pts0
www.ilograph.com 1y ago

Common Mistakes in Architecture Diagrams (2020)

billyp-rva
4pts0
www.ilograph.com 1y ago

AI excels at whiteboarding, struggles with deep diagramming

billyp-rva
1pts0

Some might quibble with using AI for research, but this at least feels directionally correct. I'm not sure if ratings/MPAA is the right avenue to fix it, but the sheer laziness of manufacturing stakes by catastrophe instead of through characters definitely feels like its gotten worse.

and i would say json/yaml is not a dsl

But you can have DSLs that are json/yaml, is my point.

PlantUML is a real dsl.

PlantUML is a DSL that isn't json/yaml. That doesn't make it better, and you can make the argument that it is worse because the tooling around it won't be as good.

the premise is that because of these few existing dsls (like PlantUML mentioned) my "new dsl" will be equally effective. PlantUML has millions of examples in the training data, my new dsls are not (*specially if its not json/yaml* or just function chain based)

I can confirm that having a DSL that is json/yaml helps a ton. Kind of like static type checking, it eliminates entire swaths of syntactical errors, allowing the LLM to focus on the semantics.

because if then you are going to ask the llm to "compile the dsl to implementation" we are back to square 1.

I think this is an edge case; 99% of the time you (and/or the LLM) would have access to the implementor so it wouldn't need to do this.

Hi, author here. The app itself (Ilograph[0]) is fairly old; its first ShowHN was in 2019.

These particular yt-dlp diagrams were an experiment in getting meaningful sequence diagrams from a code repo using Claude. If you open the black tab on the left, you can see the source of the diagrams. Claude was able to generate most of this, albeit with a good amount of back-and-forth to get the details right, plus some manual tweaking in the end.

[0] https://www.ilograph.com

5 years later...

People who wanted to ask a specific question now won't have that option. Instead, they'll simply be shown whatever Google thinks is most relevant to them at that moment. The "Chat" UI we've grown so accustomed to is on its way out.

I’ve found that Claude can make decent mermaid diagrams pretty reliably.

When doing this, do you give it a codebase and ask for a diagram, or is it more of an iterative back-and-forth where you describe the system to it.

"OAuth 2.0 authorization code flow with PKCE as a sequence diagram — user, browser, app server, auth server, API"

If you do a Google image search for "OAuth 2.0 PKCE sequence diagram" you get good results also. Maybe if you ask for something more esoteric this becomes valuable? Of course, that also makes hallucinations more likely.

EFF is leaving X 3 months ago

Interested people will be following maybe even expecting to see them.

But they won't. That isn't how modern social networks work, and X definitely isn't an exception. The chronological feed of people you follow is long gone.

There was a time around 2016 where you weren't allowed to write a React application without also writing a "Getting Started with React" blog post. Having trained on all of that, the AI probably thinks React is web development.

JSDoc is TypeScript 7 months ago

Writing a Typescript program that takes external input but has no runtime error checking is already a mistake, though.

If it's a service, yes, and that's true no matter what technology the service is using. If it's a library, no, because...

and if you write type assertions without ensuring that the assertions are accurate, then that's on you, not Typescript.

That's on whoever is using the library, not the library author. If the library author provides type definitions, and you as the consumer choose to ignore them, then it's on you.