alt Hacker NewsI had this conversation recently. Not only are search engines and comment threads getting filled with AI responses, but people are increasingly sounding like AI themselves. This makes it even harder to distinguish.
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. If any used paths in their branches, it was almost certainly their name. Now everyone uses this convention. Though, they do use correct capitalization instead of lowercase freaking _everything_ that AI does.
Replies
I've been using it at work since we moved from TF source control to TF-Git, close to a decade ago. feature/ticketno, release/number and user/initials/...
TF at least gave a nice folder view on the branches screen, which we've lost now we've moved to GitHub, but it has made it easier to enforce.
I think this is just a Jira/bitbucket thing. If you add a feature branch, that's how the naming convention defaults. I've been seeing it for years.
> Like using feature/xxxxx as the branch name. Last year exactly zero developers used this convention.
The AI learned it from somewhere though, it didn't come up with it on its own
What. Strict branch naming like feature/, bugfix/, chore/, release/ has been the standard for probably 10 years now in all projects I've been in, often enforced by auto-rejecting pushes that don't comply.