3 ms·
The Scrum lords and managers might use LLMs to add beurocratic complexity instead of becoming efficient.
by rightbyte 1y ago
The Scrum lords and managers might use LLMs to add beurocratic complexity instead of becoming efficient.
- tart-lemonade 1y agoAlternatively, it could become more efficient at creating inefficiencies. Imagine pushing your vibe-coded changes triggering a CI hook that uses an LLM to create a TPS report per commit+pipeline in a merge request, which another LLM-based bureaucrat could use to decide whether the MR should be approved, generating its own TPS reports in turn which some middle manager could use their LLM to summarize. Think of all the shareholder value we could create by going all-in on AI!
- Gigachad 1y agoThe number of vibe coded PRs clogging up the review queues is going up. When you ask the submitter what some nonsense line of code is doing and what it's for, they have no idea. Slowing the whole process down.
- derwiki 1y agoIt definitely takes me more time to review PRs now, and I have more PRs to review. Agent created code seems “fine” but also seems like 30% more than is needed (total SWAG)
- Gigachad 1y agoThe worst part is how it destroys your implicit trust that the author ran and understood the code. The generated code looks fine but doesn't actually work because it was never run. So to properly review PRs today you have to spend a lot longer assuming nothing works and every detail needs to be carefully tested.
- derwiki 1y agoIs there’s no screenshots of it working or logs from a console showing it working, I kinda presume it won’t. In a previous role that was more front end facing (tablet experience for self driving cars), I had a few coworkers who would put out PRs that I knew could not have worked and were not tested. My nudge was “oh can you add a screenshot to the PR?” And they would realize it didn’t work and get back to me in a few days. Been dealing with this since before gen AI produced code haha.