Content
@
0 reply
0 recast
2 reactions
greg
@gregfromstl
git blames serve no practical purpose and should be disabled
8 replies
11 recasts
42 reactions
Steve
@stevedylandev.eth
Bruh these hot takes 💀 I use it a good bit when collaborating on projects; helps me identify who I need to talk to if I have a question
1 reply
0 recast
7 reactions
greg
@gregfromstl
1. It rarely works in codebases with a lot of contributors and high velocity changes. You might have 3 people who contributed to a single line and a 4th who changed the formatting through an automated script. If I update the formatting rules in the repo boom I'm blamed for every single line 2. If you have to ask questions to the code author directly there are bigger problems (code isn't readble, not commented, etc)
1 reply
0 recast
1 reaction
alex
@alexgrover.eth
1. easily solvable with an ignoreRevsFile or just using your brain to look at the commit messages and going back in history if necessary 2. sometimes you have to ask questions about the domain or business logic if you're unfamiliar, even if the code is perfect this feels like bait to me ðŸ˜
1 reply
0 recast
1 reaction
greg
@gregfromstl
No one uses their brain here sir, you are in the wrong industry
2 replies
0 recast
2 reactions