wax66
4 hours ago
Pretty much nothing. We'd remove the AI integrations, the UI elements, then back to where we were. Luckily, we have no load bearing AI.
But if everyone else got to keep their AI, we'd lose customers very quickly.
joshuamoyers
4 hours ago
so ironic to see “load bearing” in a comment about removing AI. certain phrases have been ruined by fable/opus 5 for all time.
sixothree
3 hours ago
I 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.
distances
2 hours ago
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.
vips7L
44 minutes ago
Never used it in any of the projects I’ve been on.
rawling
2 hours ago
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.
HeyLaughingBoy
2 hours ago
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.
sixothree
2 hours ago
I assumed the convention came from somewhere before AI and maybe one of the new devs brought it in from there. We also have an analyst who used em-dashes before AI ruined them, and who justifiably complains about that every so often. I'm not sure that's a trend anyone wants to pick up on.
But for branches in addition to Feature/, we're seeing Hotfix/, Modernization/, you name it. If you're parking branches for a long time without completing them, I'm 100% appreciative they're categorized.
WorldMaker
36 minutes ago
The original git flow suggestion [0] was posted more than 15 years ago (date on the post is 2010). It didn't entirely invent the branch names/conventions from whole cloth, it was based on plenty of prior history in SVN spaces especially, which it picked up from CVS.
(Personally, for long term parked branches I prefer `{username/dev name}/` branches because then you know who the owner is without having to look at the commit log and guess based on recent commit authors. But that's the fun thing about branching conventions, there are so many to choose from, many of which have been around forever.)
[0] https://nvie.com/posts/a-successful-git-branching-model/
bluefirebrand
2 hours ago
> 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
anslopic
3 hours ago
Most people don’t use that shit.
Most just use Gemini or ChatGPT.
What does Anthropic bring to the table? Nothing, just a “me too” company
sixothree
2 hours ago
Did you create this account simply to disparage a single company?
anslopic
39 minutes ago
Are you retarded and just found the Internet?
CookieCrisp
2 hours ago
Sure sure sure
bko
an hour ago
None of your engineers use AI to develop the product? Seems hard to believe
sixothree
3 hours ago
Pretty much same. We only use it for internal projects when coding and for research for all team members, not just developers.