Thank you for your insights, that is very valuable. UI wise - I tried to make the browser back button work everywhere - so I assumed this as a standard ways of

Thank you for your insights, that is very valuable. UI wise - I tried to make the browser back button work everywhere - so I assumed this as a standard ways of going back where you've been. But maybe that is not what people expect and it should be more obvious. Yeah the collaboration is calculated two step. First I make a dynamic interaction graph, with timestamped edges. When a person touches a file I mark it as an interaction with everyone else who touched the file before (timestamped directed edges). Then I transform this interaction graph into collaboration graph. I consider two people collaborate on a file when the interaction is bi-directional - i.e. they both touched the same file within given time period. That way we can limit collaboration to a given time window, like for instance last 30 days, or whole project lifetime like the demo shows. But you make a very good point about refactoring and renaming for instance class name that might imply changes across many files that outside your expertise. Yet still a person profile shows "Collaborators by areas" what is a proxy to one expertise - the more collaborators you have in a certain area the more experienced you should be in there. The example from https://www.networkperspective.io/hr/ https://www.networkperspective.io/hr/ refers not only to code collaboration, but becomes more valid if you plug in other data sources like formal structure, meetings / email metadata, like shown on the other demo https://bit.ly/2VRWdaB https://bit.ly/2VRWdaB We hand a long journey with this product starting with survey data collection as we were obsessed with privacy, then adding other data sources (as it turned out we shouldn't worry about mining data that is public or semi public anyway). Now I implemented this git integration and hence asking HN community for an opinion about how useful this might be. Anyways thank you for all the feedback, I'll spend more time going through it today, and I appreciate it very much.