3 ms·
Writing good commit messages can be good self-promotion. You may not realize who is watching the repo and this is an easy way to differentiate yourself from you
by norir 2y ago
Writing good commit messages can be good self-promotion. You may not realize who is watching the repo and this is an easy way to differentiate yourself from you colleagues and make your work appear interesting and important.
Also, I have found that writing commit messages often forced me to rework a poor solution whose weakness became apparent only when I tried to explain it. In other words, often the value of the commit message is not the message itself but rather the process that produced it. It's a bit like musical scales. Almost no one is performing scales at a concert but also almost no one is performing without scales as a part of their regular practice.
- hitchstory 2y ago>can be good self-promotion. You may not realize When I said nebulous and hard to pin down this is kinda what I meant. Do you routinely monitor commit messages on adjacent teams' repos? I dont. I dont know anybody who does. When I want to know something about their code I ping them a slack message and vice versa. I dont think the CTO is reading commit messages either, theyre too busy. I think it's good to ask when and why people actually do read commit messages to make sure what you write aligns with what they want to see.