this post was submitted on 03 Nov 2023
30 points (65.3% liked)

Programming

17314 readers
187 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 !webdev@programming.dev



founded 1 year ago
MODERATORS
 

It writes more informative commits than I could ever make so I'm just reading what it says and mostly copy/pasting completely most of the time, I write all of the changes I've made into an LLM with a large context window and it write a very detailed commit not just with a title but with bullet points describing each of the changes precisely

you are viewing a single comment's thread
view the rest of the comments
[–] DmMacniel@feddit.de 23 points 1 year ago* (last edited 1 year ago) (2 children)

Why don't you know WHY you did something to the codebase that you now want to commit?

Relying on an LLM for that sounds like a crutch that you need to get rid of ASAP!

[–] PoisonedPrisonPanda@discuss.tchncs.de 3 points 1 year ago (1 children)

Im more in favour in writting "my" commit message myself and let LLMs refotmulate and make concise.

[–] TootSweet@lemmy.world 3 points 1 year ago* (last edited 1 year ago) (1 children)

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.

[–] balder1993@programming.dev 2 points 1 year ago* (last edited 1 year ago) (1 children)

The problem is people are lazy and most places I’ve been, peoeple make bad commit messages and often very non informative.

[–] TootSweet@lemmy.world 1 points 1 year ago

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.

[–] wagesj45@kbin.social 1 points 1 year ago (1 children)

Of course he knows why he made the changes. He made them. But computers are much faster as typing and with a sophisticated enough LLM you can offload some gruntwork. I'd argue if you're not utilizing all the tools at your disposal, you're not performing like you should.

[–] DmMacniel@feddit.de 3 points 1 year ago

we are talking about programmers/software developers. Speed typing is in our nature. If you can't type 50 characters faster than writing the prompt to get the LLM to spat out a commit meesage, then I will question your competence.

Also the opposite is true, when the Boss realise that major parts or grunt work as you say can be automated by utilising LLM, then they would be inclined to employ that and reduce your wage. Because do you really deserve 6 figures when a computer can do the grunt work for their expensive human resources?