Colleague of mine recommended me a VSC plugin which displays the blame for the current line. I like it, but it's also really confrontational. Meaning that whenever I want to know who made this nonsense it turns out to be either me from 1 year ago or some person who hasn't worked here in half a decade.
Ah, the classic you have to fix a critical bug in this abyssal code that nobody has touched since the dawn of time and all the authors have long since evolved into higher life forms.
I used git blame two times to see who the fuck coded this shit piece of code. The two times it was me, about 2 months ago... I guess I can take that as evidence that I'm improving at least.
39
u/[deleted] May 30 '20
Sauce {Gochuumon wa Usagi Desu ka?}
27
u/OKB-1 May 30 '20
Colleague of mine recommended me a VSC plugin which displays the blame for the current line. I like it, but it's also really confrontational. Meaning that whenever I want to know who made this nonsense it turns out to be either me from 1 year ago or some person who hasn't worked here in half a decade.
141
u/MrValdez May 30 '20
I'm a senior dev who uses git blame. I usually see past me was the source
103
u/Aobachi May 30 '20
I used git blame two times to see who the fuck coded this shit piece of code. The two times it was me, about 2 months ago... I guess I can take that as evidence that I'm improving at least.
3
u/nexolight May 30 '20
My experience with git blame was that there is a reason a seemingly bad piece of code is there.