3 ms·
TBH writing shell scripts (and automation tools generally) is the grunt work I most love it for. Git commits and PR descriptions? Those are probably best at le
by cmrdporcupine 4mo ago
TBH writing shell scripts (and automation tools generally) is the grunt work I most love it for.
Git commits and PR descriptions? Those are probably best at least edited/tuned by humans. Because they're meant to be read by humans.
- bunderbunder 4mo agoOur commit messages have become useless since we adopted a shared agent skill for making commits. The LLM tends to fill the messages with irrelevant details while still failing to mention what the change actually does.
- cmrdporcupine 4mo agoExactly. I was team / tech lead on the last contract gig I had, and I had a policy in writing that people should write their own commit messages and PR descriptions. For this reason and others. ... And follow conventional commit format. Linear commits. Rebasing / fast-forward, no merge commits. Etc. etc. Nobody paid any attention. The git history was next to useless. Bisecting would be completely impossible. People were mostly just pumping and dumping. I could have drawn a hard red line but the founder was the worst for it. We're doomed.
- duskdozer 3mo agoComments as well. It's exactly the type of commenting they taught us not to do because it was useless. I'm sure it's also a negative to the LLMs as well by polluting the memory with useless info.
- deleted 4mo ago[deleted]