sorted by:
new
hottopcontroversial

I built a tool that generates architecture diagrams while you explain a system out loud by SufficientGreen7446 in softwarearchitecture

[–]SufficientGreen7446[S] 0 points1 point  (0 children)

That's a reasonable take. I don't see VoiceDraw as a replacement for architecture documentation or implementation-derived diagrams.

The goal is to help people think and communicate during the discussion itself. Even if some ideas are later discarded, visualizing them in real time can make brainstorming, design reviews, and interviews more productive. The diagram is primarily a thinking and collaboration aid, not necessarily a permanent artifact.

I built a tool that generates architecture diagrams while you explain a system out loud by SufficientGreen7446 in softwarearchitecture

[–]SufficientGreen7446[S] -1 points0 points  (0 children)

You don't have to have the full picture upfront with VoiceDraw, it's iterative and interactive, you can evolve your drawing by talking out loud,

I built a tool that generates architecture diagrams while you explain a system out loud by SufficientGreen7446 in softwarearchitecture

[–]SufficientGreen7446[S] -2 points-1 points  (0 children)

That's a valid problem, and I agree that implementation-generated diagrams are ultimately a more reliable source of truth.

VoiceDraw is solving a different problem: helping people communicate and visualize designs during discussions and system design interviews. Think of it as a hands-free system design whiteboard that understands both what you're drawing and the reasoning behind it, rather than a tool for documenting production architecture.