Related to code quality, I've noticed developers picking up tricks from AI. Like using feature/xxxxx as the branch name. Last year exactly zero developers used this convention.
Huh.
I've been using that convention for ages, but I have to remind Claude on new projects to actually use git in the first place, and then also specifically tell it to use branches.
Then again, I was using em-dashes before they got un-cool.
I'm not sure why you're arguing that when it's not the point of the statement. YOU have been using that convention. Now do an analysis of the people at your company.
Regex the pattern over time if you want to make an argument against my supporting example.
Comments
Huh.
I've been using that convention for ages, but I have to remind Claude on new projects to actually use git in the first place, and then also specifically tell it to use branches.
Then again, I was using em-dashes before they got un-cool.
I'm not sure why you're arguing that when it's not the point of the statement. YOU have been using that convention. Now do an analysis of the people at your company.
Regex the pattern over time if you want to make an argument against my supporting example.
'twas an expression of surprise, not an argument.
Surprise in both directions, 'cause what you like about Claude is one of the ways it fails for me.
It was mandatory at several of them.
I wonder which of the various employers I've had in the last decade would consider me regexing commits to be an NDA violation?
I choose not to discover.