[dkarl]

I would want something slightly different. I care a lot about how recently code has been changed. I usually don't care how much code is run in production, unless it isn't run at all, and then I care a lot. So:

Code that was changed within the last week: red

Code that was changed within the last month: yellow

Code that hasn't been changed in over a month: normal

Code that hasn't been touched in over a year: green

Dead code: blink tag, DOOM music plays

[vidanay]

I really like the idea of a "code heatmap". I actually think this could be easily implemented in one scenario: Visual Studio Code Lens already has that information. Massaging it into a background color probably wouldn't be too difficult.

https://docs.microsoft.com/en-us/visualstudio/ide/find-code-...

[sidpatil]

I believe TortoiseGit has this feature out-of-the-box: https://tortoisegit.org/docs/tortoisegit/tgit-dug-blame.html

[ludovicianul]

We've built an internal tool which does exactly this. Among a bunch of other correlations

[eligro91]

ever thought on making this open-source?

[ludovicianul]

yes. sensitive topic though (for now)

[mikewarot]

It sounds like you want to combine git blame with performance data.