|
|
|
|
|
by zerocount
1634 days ago
|
|
Yep. I make a commit on every little change and every team I've been on makes me squash them on merge. Comments in Git commits are bad. Just comment the code and make sure the comments are updated while you're in the code. You can also look at them in a code review. The argument that they get outdated is easily remedied, but people just want to keep claiming they write 'self documented code.' |
|
To me both are important but for different reasons. I don't want to search the blame history of a line of code if a simple comment had been enough, neither would I want to primarily use code comments when bisecting.