5 ms·
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, unle
by dkarl 4y ago
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
- sidpatil 4y agoI believe TortoiseGit has this feature out-of-the-box: https://tortoisegit.org/docs/tortoisegit/tgit-dug-blame.html https://tortoisegit.org/docs/tortoisegit/tgit-dug-blame.html
- mikewarot 4y agoIt sounds like you want to combine git blame with performance data.
- vidanay 4y agoI 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-changes-and-other-history-with-codelens?view=vs-2022 https://docs.microsoft.com/en-us/visualstudio/ide/find-code-...
- ludovicianul 4y agoWe've built an internal tool which does exactly this. Among a bunch of other correlations
- eligro91 4y agoever thought on making this open-source?
- ludovicianul 4y agoyes. sensitive topic though (for now)