Lib author here. Like most teams, we ship fast, and increasingly the important thing for us is making sure the overall system is healthy. Working code isn't enough.
So, before reading the code diff on PRs, we can judge from visually rich architecture and data flow diagrams. This helps us keep a clear mental model of how every part of the system is evolving.
We built a new renderer to support some of the rich visualisations, and curious if it's helpful for others
So, before reading the code diff on PRs, we can judge from visually rich architecture and data flow diagrams. This helps us keep a clear mental model of how every part of the system is evolving.
We built a new renderer to support some of the rich visualisations, and curious if it's helpful for others