undefined | Better HN

0 pointsSpivak7mo ago0 comments

I see it as the same issue as doctor's notes. They're extremely useful but it's a waste of time to actually make the doctor do them. At some places it's a person's whole job to follow around a doctor and do all the busy work for them.

I'm not nearly important enough to have an intern write my commit messages but now that AI can do them, and do them extremely well, I'm more than happy to offload the work and get back to the actual work. The AI is far more thorough than I would be and because it takes away nearly all the mental effort the end result is, I think, better.

0 comments

5 comments · 1 top-level

hrimfaxi7mo ago· 4 in thread

At least a scribe captures the doctor's thoughts. AI is not capturing the author's thoughts because it doesn't know what they were at commit time.

number67mo ago

As someone whos commit message are: fix, fix again, this hopefully works, again.

I am sure AI cannot even glims the frustration I feel committing these commits.

You can argue, that these messages are as poor as the code that I have written; but don't tell me you haven't been there -- and if you have please tell me your secret

skydhash7mo ago

My secret is intent (and magit). If I’ going to write code, I already have a few goals in mind. That’s what I put in the commit message. Magit is for I did other stuff, so I can stage individual hunks/lines instead of whole files.

nextaccountic7mo ago

My favorite git command is git commit --amend, my second is git rebase. Until you push, you don't need to keep adding new pointless commits

Actually I wish that we had two branches in parallel, one with cleaned up commits, another with how the software were actually edited. But we need tooling for that

Izkata7mo ago

If you go all the way to where the cleaned-up version is a squash merge, as so many unfortunately do, we already have that: regular, non-squashed merges.

If you don't go that far, you could mimic something like it with sub-branches and merge commits for each one into your working branch, but I imagine it would be annoying to handle at that granularity.

j / k navigate · click thread line to collapse