| ▲ | delecti an hour ago | |
It's not the ocean, it's the poster's own team. A simple "AI comments suck" in a sprint retro would be trivially easy and would at least start the conversation. | ||
| ▲ | swat535 a few seconds ago | parent | next [-] | |
You're going to have convince upper management why the team's velocity is suddenly affected in feature releases once they stop using AI. All the execs know that they can refresh the screen faster and see the features for marketing and sales. When has engineering ever had a voice anyway? The bean counters have been looking to cut us out since the inception of our industry. | ||
| ▲ | stronglikedan 29 minutes ago | parent | prev | next [-] | |
Doesn't matter. You'll come off as the baddie. It's the foreseeable future. Best just to learn how to interpret AI generated shit, or learn how to run it through AI and have it translate it to a more concise format without all the buzzwords. It'll take getting used to, but it'll save your career. | ||
| ▲ | VohuMana 41 minutes ago | parent | prev [-] | |
I think the biggest issue might not be the immediate team but upper leadership. Companies which have mandated AI usage override a lot of what an individual or individual team wants. If that’s the case then it would be a lot like fighting the ocean, especially if your immediate team sees having AI write docs as an easy way to move the needle on LT’s AI monitoring dashboard. | ||