5 ms·
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
by wax66 1mo 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 1mo agoso ironic to see “load bearing” in a comment about removing AI. certain phrases have been ruined by fable/opus 5 for all time.
- anslopic 1mo ago[flagged]
- sixothree 1mo agoDid you create this account simply to disparage a single company?
- anslopic 1mo ago[flagged]
- CookieCrisp 1mo agoSure sure sure
- sixothree 1mo agoI 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.
- HeyLaughingBoy 1mo agoI 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 1mo agoI 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 1mo agoThe 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/ https://nvie.com/posts/a-successful-git-branching-model/
- deleted 1mo ago[deleted]
- jaredsohn 1mo agoLinear does this, too. It provides a button that copies a branch name to the clipboard based on the ticket id/name.
- 1mo ago
- sixothree 1mo agoPretty much same. We only use it for internal projects when coding and for research for all team members, not just developers.
- bko 1mo agoNone of your engineers use AI to develop the product? Seems hard to believe
- AnimalMuppet 1mo agoI don't think that's what they said. They said they could remove AI from the workflow without much disruption.
- mancerayder 1mo ago>Luckily, we have no load bearing AI. Is this a subtle joke?
- rl3 1mo ago>Is this a subtle joke? Proper weight distribution is critical in determining where the seams are.
- notahacker 1mo agoYou're absolutely right! Honestly? It's not just a joke, it's a smoking gun.