Really cool blog. I have been thinking about this recently as I was a center piece of our startup, and to me the hardest part of giving away responsibilities has been 2 phase: firstly that suddenly I feel like I am not in control, and second that people are spending time on things they don't like and because of that we are not leveraging their true potential/string sides (moneyball).

Curious to hear what other think about that - should you leave people focus only on their strong sides, or they should still help out with e2e things.

I understand, so you would much rather count an active Issue more valueable then few stars. I am saying active as I have seen already issues being open and as soon as a comment on my side gets in the person has disappeared, I suppose people are busy and don't have too much time for open-source anyway, so if the project doesn't run first try they give up.

So in order to keep the diagram up-to-date with commits we use the git difference of python files. An agent is tasked to firstly evaluate if the change is big enough to trigger a full clean analysis. If the change is not big enough we start doing the same thing component by component recursively and update only components which are affected by the new change.

But comparing the control-flow-graph probably makes more sense for a big refactor commits, as it might blow the context. However so far we haven't seen this be an issue.

Curious to hear what was your approach when building diagram represnetation!