Re:It's probably time to stop recommending Clean Code (2020)
by richardxia on Tuesday May 25, 2021 @11:49AM
(#27278390)
Was going to post the exact same thing. I make use of this repeated git blame method all the time, and for everyone who is just learning this for the first time, you'll actually want to write `git blame <commit>~` to go back one commit from the commit hash in the blame, because otherwise you'll still get the same results on the line you're looking at.
Also, if you're using GitHub, their Blame view also a button that looks like a stack of rectangles between the commit information and the code. Clicking that will essentially do the same thing command-line git operation above.
Re:It's probably time to stop recommending Clean Code (2020)
by erik_seaberg on Tuesday May 25, 2021 @06:53PM
(#27283813)
git blame --ignore-rev helps with filtering out meaningless changes in commits.
Re:It's probably time to stop recommending Clean Code (2020)
by triceratops on Tuesday May 25, 2021 @11:41AM
(#27278281)
Good idea. TIL.
(I'm embarrassed I didn't think of it before)
All in all it has a negligible impact on the readability of the code. It's mostly aesthetic for me. It's ugly and only solves far fetched problems.
Do you scratch your name and SSN into the side of your car? What if your title blows away in the wind on the same day that city hall burns down destroying all ownership records?