That’s pretty good except one giant flaw. The author relies on counting commits. That doesn’t work in a lot of places, I prefer squashing commits when merging a PR/MR to reduce the back and forth noise, so you will find me in position 5 or 6 in the projects I am the top expert of. I don’t think git blame and counting number of lines would help either, because if we change our formatting standard and ask the junior to reformat the projects and make sure they continue working, he they will show up as top expert in something they know nothing about.

These commands make you feel good but tell nothing about the project and who are the experts.