2 ms·
Instead of relying on people actively checking the git-blame for all of the code they're reading, why not just put a clearly obvious comment within the code its
by mcntsh 1y ago
Instead of relying on people actively checking the git-blame for all of the code they're reading, why not just put a clearly obvious comment within the code itself?
- sublinear 1y agoI'm actually saying people can do both. What I take issue with is low quality writing. TODOs are a low quality comment. Commit messages that only tell "what" and not "why" are also low quality. Generally just not having a clean history to look at is bad project management.