Ask HN: What would happen if your company stopped using all AI tomorrow?
41–50 of 102 posts
Re: Ask HN: What would happen if your company stopped using all AI tomorrow?
#42I’d have to stop interacting with meat proxies and wouldn’t have to read copy pasted LLM text.
I have the same feeling but don't really know why. Why do I dislike reading LLM text so much? Weird
Re: Ask HN: What would happen if your company stopped using all AI tomorrow?
#43If you tell every manager they need to show some sort of success with AI, you get a lot of projects that don't make sense, which then quietly die, and the process repeats.
Re: Ask HN: What would happen if your company stopped using all AI tomorrow?
#44Earlier quoted context omitted.
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 b…
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.
Re: Ask HN: What would happen if your company stopped using all AI tomorrow?
#45Re: Ask HN: What would happen if your company stopped using all AI tomorrow?
#46Earlier quoted context omitted.
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.
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…
(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/
Re: Ask HN: What would happen if your company stopped using all AI tomorrow?
#47Total collapse, idiot managers already fired everyone that knew how anything worked and now they're completely fucked. Frankly I have no idea how I've managed to hang on this long but likely to be gone myself in a few weeks as well.
Re: Ask HN: What would happen if your company stopped using all AI tomorrow?
#48Earlier quoted context omitted.
so ironic to see “load bearing” in a comment about removing AI. certain phrases have been ruined by fable/opus 5 for all time.
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 b…
People have been doing this for years.
Re: Ask HN: What would happen if your company stopped using all AI tomorrow?
#49Earlier quoted context omitted.
so ironic to see “load bearing” in a comment about removing AI. certain phrases have been ruined by fable/opus 5 for all time.
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 b…