Hacker News Reader

And then you have the diagram evolution cycle:

Step 1: People want a simple high level architecture diagram. Step 2: People want more detail Step 3: People want to see how human components of the system work Step 4: The diagram is so complicated and non-obvious that people start asking for a simpler high level architecture diagram.

The only way to escape is to be clever about preserving multiple 'zoom' /C4 levels of diagram.

View on HN

> The only way to escape is to be clever about preserving multiple 'zoom' /C4 levels of diagram.

Fully agree. Having gone through startup funding rounds and acquisitions, that's the set of diagrams that I have ready or prepare for each one. The "suits" like the higher level stuff, while the people digging into technical due diligence or post-acquistion integration like the more detailed ones. They're also adaptable at many levels for any domain-specific "enhancements" that are necessary, such as a data flows, security flows, and the like.

Reply on news.ycombinator.com