3 ms·
We have a guy using LLMs for generating things like this at work. I’d rather he didn’t. The AI doesn’t understand business or product context, only the code. I
by nucleardog 3y ago
We have a guy using LLMs for generating things like this at work. I’d rather he didn’t.
The AI doesn’t understand business or product context, only the code. It can’t explain _why_ the change was made or the higher level reasoning or impacts which are the main point—the “what” is already present in the diff.
A commit or MR that says “Added a method to the controller that calls the new `frobulate` method on FooService” answers none of the questions someone would have looking back at this in six months and provides no helpful information for someone trying to debug or modify it later.
- smcleod 3y agoI’d argue that a commit message is not the place for (detailed) business reasoning. Sure put a link to the issue that contains the requirement / fix details - better yet have it auto-link based on an identifier. Personally I’d much rather see a brief description of the technical change and if there’s any hard to grasp concepts.