Emacs as your code-compass: who is the person who refactored most in this project?
It is a while I don't post about code-compass. I recently jumped back in the consulting world and it is a hectic life! In a couple of months I moved from a project to another. Furthermore, I cannot say I got somebody introducing me to the software architecture of these projects (or even their status).
Lucky me these years (from Ph.D. to industry times) have given me some experience, so my boat is well equipped for this wavy sea. Also I have a great tool: in both projects I just had to rely on my Emacs for a reliable code-compass.
So armed of hotspots, knowledge and communication graphs with a bit of churn, fragmentation and complexity on the side, I could get up and running faster than ever! Yay!!
One thing I have been missing is to explore graphically who dedicated themselves to the lovely art of refactoring. Indeed, the project on which I rely, the fantastic code-maat, offers a refactoring analysis. This finds who has deleted most lines in a file using Git commits information.
Naturally deletions are an approximation for refactoring, but good enough as less code is always an improvement (at least for our eyes).
Well there I go: I added it just now. It was pretty easy because is super-similar to the knowledge graph implementation. So a tweak here and there and it is now available.
Below a video that gives you a sense of what it is about.
If you want to try that yourself it is easy: just try out code-compass ;)
Happy refactoring!