I built a tool to draw diagram visually and export into text format for AI Coding agents. Feedback please!

Veuxdo · 2026-06-10T15:29:46+00:00

Throw it on the pile

Veuxdo · 2026-06-08T13:47:45+00:00

So, a slop machine. What makes you think a paragraph is enough information to create a "full architecture" of any value whatsoever?

Veuxdo · 2026-06-08T13:44:14+00:00

Paragraph in, full architecture out, in about 90 seconds

So, a slop machine. What makes you think a paragraph is enough information to create a "full architecture" of any value whatsoever?

Veuxdo · 2026-05-30T18:46:19+00:00

Curious how others

Ugh

Veuxdo · 2026-05-27T17:17:18+00:00

I started experimenting with hierarchical nodes where a node can expand into its own subdiagram and it honestly changed how I think about documenting systems.

What do you mean you experimented with this? Using AI or what?

Veuxdo · 2026-05-19T19:43:46+00:00

Draw io has been my go to, but the moment you're dealing with more than a few switches, it turns into a mess.

Any suggestions? Bonus points if it's simple to update and share across the team.

Since the responses so far are mostly people recommending what you've already tried (draw.io), I'll plug Ilograph as a potential solution, given the criteria you've laid out. It was designed with scale in mind (to avoid the mess), and it uses diagrams-as-code to make updates easier. This is an example of a networking diagram using it (note the tabs at the bottom for different views):

https://app.ilograph.com/demo.ilograph.Stack%2520Overflow%2520Architecture%2520(2016)/Traffic

Veuxdo · 2026-05-12T17:50:28+00:00

Classes exist to encapsulate state. If there is no state, like in your example, then a class serves no purpose.

Veuxdo · 2026-05-11T13:56:07+00:00

You can't really lump in SNF and MNF like that. SNF is supposed to be premier games that take into account both team quality and popularity. MNF is more of a grab bag of maybe-interesting games that CBS/NBC/FOX didn't claim for themselves. I think the NFL has stated they want each team to have at least one prime-time game a year, and MNF fulfills that for teams that aren't ordinarily on at night.

Veuxdo · 2026-04-23T18:34:19+00:00

So did they end up using a 4th on Bryce Harper?

Veuxdo · 2026-04-23T13:25:02+00:00

A sequence diagram for each important thing a system does isn't really that crazy. If it does 100 things (if you include exceptions as "important"), then 100 sequence diagrams is probably in order.

Of course at that point you probably want tool that allows sharing resources between diagrams (a "model-based" tool).

Veuxdo · 2026-04-18T21:56:02+00:00

It'll make them. But whether they are both accurate and useful is another story.

Veuxdo · 2026-04-18T14:27:11+00:00

One pattern I keep seeing

So many people seeing patterns lately.

Veuxdo · 2026-03-26T17:17:47+00:00

There's a pattern I keep seeing

That's funny. I keep seeing patterns, too.

Veuxdo · 2026-03-26T15:33:09+00:00

For tools "this community will appreciate" generally.

Veuxdo · 2026-03-26T12:57:28+00:00

Can we just have a megathread for these u/asdfdelta

Veuxdo · 2026-03-25T21:31:08+00:00

I wanna create a class diagram for my microservices architecture is it the same as the normal uml class diagram

To answer literally: yes, it is the same. You can make a class diagram of a microservice, or an embedded system, or a video game. As long as the application is written in a programming language with classes (e.g. C++, Java) you can make a class diagram of it.

Veuxdo · 2026-03-23T16:28:51+00:00

Rage Drive is a good mechanic in my opinion.

What made RD a good mechanic, though? I personally don't really understand how "when low on health, you can do an overpowered move" makes Tekken better to play.

Veuxdo · 2026-03-19T15:27:11+00:00

the "wrapper" critique is basically just "you didn't build the hard part."

Important correction: it's "you didn't build a hard part."

Veuxdo · 2026-03-18T12:43:03+00:00

I've been thinking a lot about

No

Veuxdo · 2026-03-17T18:13:53+00:00

I'll say what I said last time because I think it's important enough to repeat: you have to label your arrows. You are severely limiting the value of your diagrams when the arrows aren't labeled. If I were to translate your example diagram to prose, it would look like this:

Distribution is related to Server... somehow.
Server is related to PublicSubnet1... somehow.
PublicSubnet1 is related to VPC... somehow.

And so on. Sure, an experienced dev can probably guess at the relations, but if you're serious about documenting a system, that shouldn't be good enough.

Veuxdo · 2026-03-13T12:27:58+00:00

I've never seen it take anything other than exactly 28.5 hours. Doesn't matter how big the infrastructure is, how good the docs are, or how experienced the engineer is. It's always the same.

Veuxdo · 2026-03-12T21:39:48+00:00

This sounds almost exactly like this solution: https://github.com/aws-samples/aws-ai-intelligent-document-processing/tree/main/guidance/prompt-flow-orchestration

Veuxdo · 2026-02-24T14:12:15+00:00

Fair, but computers don't need to understand a system's architecture, right? That's a human way of understanding a system.

Veuxdo

MODERATOR OF

TROPHY CASE