It feels like a very light ruleset over what we would do naturally when explaining a system to another engineer. That's great.
Some of the ideas that stood out were:
1. Allow flexibility in the notation (shapes and color) as long as the abstractions are good.
2. When drawing arrows, make them unidirectional to show the main intent.
3. Hide details to express the main story (@ 27min in the video)
4. Don't just give names to components. Give short descriptions too.
5. Don't document the lowest levels. Code is better here.
It feels like a very light ruleset over what we would do naturally when explaining a system to another engineer. That's great.
Some of the ideas that stood out were:
1. Allow flexibility in the notation (shapes and color) as long as the abstractions are good.
2. When drawing arrows, make them unidirectional to show the main intent.
3. Hide details to express the main story (@ 27min in the video)
4. Don't just give names to components. Give short descriptions too.
5. Don't document the lowest levels. Code is better here.