4 ms·

Always check git blame before winging out insults. Then, only blame people no longer at the company ;)

• kingcharles 5y ago
  This is standard development policy at every corporation I've worked at.
• taocoyote 5y ago
  Find incomprehensible code. Get email from blame. Search for them on Linkedin. If they are working as a developer in some senior capacity, then the code is probably a learning opportunity for me. If they are working as a scrum master code is probably as bad as it looks. I say this in jest, mostly...
  • lostcolony 5y ago
    I dunno; I've known horrible senior devs who wrote solutions that were clearly resume driven development who ended up as tech leads elsewhere when there was a regime change and actual scrutiny began to be applied to them.
  • joshka 5y ago
    ... as a service... ;)
• terafo 5y ago
  You should check out GitLens for VSCode, it makes the process of working with git blame seamless.
• wnoise 5y ago
  https://github.com/jayphelps/git-blame-someone-else https://github.com/jayphelps/git-blame-someone-else
• deleted 5y ago
  [deleted]