this post was submitted on 03 Nov 2023
30 points (65.3% liked)
Programming
17349 readers
232 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Im more in favour in writting "my" commit message myself and let LLMs refotmulate and make concise.
Precision > concision && accuracy > concision. Just use your own wording as the commit message. I'd rather see an account of a code change from the viewpoint of the change's author than a shorter reformulation, even if that reformulation did come from a human who knew the problem space and wasn't prone to making shit up on the fly.
The problem is people are lazy and most places I’ve been, peoeple make bad commit messages and often very non informative.
I'd rather see no commit message than an AI-generated one.
Also if I wasn't misinterpreting OP, it sounded from the post I was responding to like OP provided a summary to the LLM along with code. If OP's writing a summary anyway, why not just proofread that and use that as the commit message rather than involving an LLM in the middle of the process?
Even in a hypothetical where the company hired human tech writers to write commit messages for developers, I'd rather have in the commit message what the developer had to say rather than the possible misinterpretation of the tech writer.