51–60 of 102 posts
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.
Is this a subtle joke?
Earlier 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.
Earlier 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…
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.
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.
None of your engineers use AI to develop the product? Seems hard to believe
We’d save a lot of time not sitting on calls while managers show us the results of their brainstorming sessions with Claude. Instead we could focus on making the products better again.
We’d save a lot of time not sitting on calls while managers show us the results of their brainstorming sessions with Claude. Instead we could focus on making the products better again.
To be fair, if the managers are hands-on, those conversations with Claude might actually be useful.
The effort required to do most jobs has gone down and so has the output quality. Rather than doing the same quality work with less effort, some people use LLMs to produce minimum-quality work at minimum effort. LLMs are a cool tool but we’re over-encouraging use in every domain, even tasks they’re not good at. Every tech company in the world seems to be getting rich though how can I possibly say things would be bette…
But other than that nothing really.