Comment by dminik
14 hours ago
Yes. My Jira tickets used to be almost empty, but all of it was useful info. Now, my Jira tickets are way too long. The amount of useful info has also gone down.
Talk about an AI induced productivity increase ...
14 hours ago
Yes. My Jira tickets used to be almost empty, but all of it was useful info. Now, my Jira tickets are way too long. The amount of useful info has also gone down.
Talk about an AI induced productivity increase ...
Same thing with PR descriptions. The signal-to-noise ratio has completely flipped. Before, a short PR description meant the dev was lazy. Now, a long detailed one might just mean they hit generate description and didn't even read it. The length went up, the usefulness went down, and the reader has no way to tell which kind they're looking at.
My teammates hit the generate PR button. I'm not reading that, it's a summary of the changes that I am _already_ going to be looking at, wrapped in some flowery language about being "better architecture, cleaner code" etc.
So those PRs may as well not have a description at all as far as I'm concerned.
Right, better architecture, cleaner code is the AI equivalent of synergy in corporate emails. It sounds like it says something but it communicates nothing. The useful PR description is changed X because Y was breaking Z and that requires the author to actually think about what they did. If the tool is doing the thinking, the description is just decoration.
I do this quite often, but I also instruct Claude to limit its output to 2-3 sentences or paragraphs, depending on the context. Also "Write this for a team of software developers / MBA's" goes a long way too.
I also do the extra step of eliminating things that are not needed, or we review this during backlog refinement.
Sounds like a lot of work to ensure it's correct, without the guarantee that it's actually correct. Why not just do it oldschool? Is it really saving you that much time?
We went from Jira tickets with one or two sentences, "Implement feature X. Here are some caveats: (simple bullet points, a few words each)" to literal _pages_ of full-on unreadable garbage.
I'm taking a break from doing Clever Stuff and just working on the networks team at work, because there's a big infrastructure update happening and if you want a thing done right you have to do it yourself.
Anyway.
People are starting to log support tickets using Copilot. It's easily recognisable, and they just fire a Copilot-generated email into the Helldesk, which then means I have to pick through six paragraphs of scrool to find basic things like what's actually wrong and where. Apparently this is a great improvement for everyone over tickets that just say "John MacDonald's phone is crackling, extension number 2345" because that's somehow not informative enough for me to conf up a new one and throw it at the van driver to take to site next time he's passing, and then bring the broken one back for me to repair or scrap.
Progress, eh?
It's weird that there's little to no focus on making AI describe problems coherently for use-cases like this?