2026-11-08 22:21 UTC
Use the AI to fix technical debt. A lot of the changes needed to make codebase good were just humanly not possible (given the priority and urgency), but now you have a stochastic parrot to do the grunt work.
Setup CI, align docs to actual code, improve interfaces, refactor for the long term and not just what the next ticket needed. Treat it like free labour for some easy but time consuming stuff aka intern.
Using it per ticket without removing old debt will incur more debt. Once you are happy enough with the codebase that giving a ticket to a really capable but still stupid intern isn’t gonna result in unmanageable shit, then you can start tackling tickets with LLM harness like: adding a MCVE or checking if a ticket has enough info.
Outright solving tickets with AI will result in the team getting increasingly unfamiliar with their own codebase making. That will have similar effect has hiring a new senior engineer to any project with no team and only interns (LLM): lots of ideas and capabilities but almost all of the time is spent in understanding the effing codebase.
Using random ass scripts to make certain ticket managers happy will ‘help now’, but it’ll be really bad for a team of 10. Increasing velocity needs a large magnitude (ticket size * ticket count) as well as the right direction (based on codebase) so the mgmt strategy is bonkers.
Replies (1)
-
@RustyNova@lemmy.world 2026-11-08 22:54
But I love fixing the tech dept lol. It actually make me learn the different systems CI is not applicable here (It’s really a special type of development workflow I’d love to burn to the ground but coworkers can barely remember to commit on SVN…) As for tickets, i wouldn’t trust AI on any of it. Even with an MCP tailored to our app it keeps hallucinating (might be due to the lack of documentation). The only thing it’s good at is code gen, which is 20% of tickets…