(Replying to PARENT post)

Architecture diagrams are great and do indeed enable better conversations. They are just expensive to build, expensive to maintain and go out of date fast enough that they're practically ephemeral.

👤hitchstory🕑2y🔼0🗨️0

(Replying to PARENT post)

> They are just expensive to build, expensive to maintain and go out of date fast enough that they're practically ephemeral.

I agree with this if you're using drag-and-drop diagramming tools. Diagrams-as-code is a potential solution IMO: https://www.ilograph.com/blog/posts/its-time-to-drop-drag-an...

👤Veuxdo🕑2y🔼0🗨️0

(Replying to PARENT post)

Also, in order for them to capture appropriate granularities of detail, they take a lot of time and conversation with readers.

I usually go with as little graphs as possible and prefer to write text; it can capture more, better, faster, and be more iterable. For specific areas like state machines or packet sequences I will drill into graphical representations more but otherwise... eh. Text wins.

👤pnathan🕑2y🔼0🗨️0