if you're using AI regularly to generate text/presentations that you intend to use persuasively i don't think i can trust a single thing you say. Where does the AI end and the human begin?

I think this is why im so against AI generated commit messages especially if the code was written by a human, you wrote the code so you should be able to demonstrate that you understand what the change does and why.

If you're deferring that to an AI and you made a subtle logic error that it decides to justify for you suddenly we have obfuscated our own fucking zero days. Good luck finding the bug if the commit message describes the error as if it was intentional.

For general text, if you start with the conclusion and let the AI write the justification then there is no justification!!! Details matter, having a paper trail for decision making matters.

I wonder how many executives will escape the consequences of their white collar crimes by blaming AI.

AI zombification is coming and it's going to create a distinct difference in communication styles between those who do and don't use it, honestly that point is already here.

And we're gonna find out yet again that marx was right when it becomes clear that AI usage correlates with class lines.

@cas At some level I agree re AI generated commit messages. At another I've had to deal with so many "some small fixes" commits that I'd almost rather have the slop machine give something at least somewhat relevant to what the "small fixes" were.

@cadey @cas I'd rather have --allow-empty-message than not being able to trust commit messages being accurate.

And yes, they may already not be. But when they're not, they were at least a human-made mistake.

And why the fuck should the generated commit message be baked into the commit? Why not let generation happen on-demand such that when the models improve, the message improves?

@samueldr @cas I hate to say it, but your suggestion makes too much sense for anyone to actually implement.
@cadey @samueldr @cas we gotta hammer things into the existing holes because redesigning the stack is inconceivable and/or too hard