3 ms·
I do, I think. I often blame individual lines to see if there's information in the commit about the reason for the change. It's often straightforward to underst
by paublyrne 7y ago
I do, I think. I often blame individual lines to see if there's information in the commit about the reason for the change. It's often straightforward to understand what's happening when reading code, the information that's often missing is the why.
Sometimes there are clues sometimes not, but you can often see the line change in the context of changes to other files and that can help.
For this reason I tend to make quite verbose commits with the context of why I'm making the change. A comment in the code would go out of date, and pollute readability, but a well written commit can be very useful.
- politelemon 7y agoThat's indeed useful, some IDEs/editors are able to show the commit message just above the line of code you're looking at, providing a lot of useful context when troubleshooting. Of course it does require discipline on our part, as it can fall over when a dev has been through hours of messages like "trying something..."