Hacker News Reader

Of course not all tickets are complex. Last week I had to fix a ticket which was to display the update date on a blog post next to the publish date. Perfect use case for AI to one shot.

View on HN

I'm using Opus on Claude Code and even on easy tasks, if you not review the changes properly, it creates tech debts. One of the most common issues is replicating the same logic with variables with different names (which makes grep harder to detect on future changes) in multiple places and lack of following project patterns. Even having a lot of .md files instructing to do the opposite. I still didn't find a workflow without human interaction that can be that efficient and reliable.

I suppose at that point I’m wondering if it would have just been faster for… you, (I’m assuming) the developer to make that change and deploy it? Is the AI really faster on small changes like that, if you understand the platform/code/CI/CD enough???

Maybe for a non-dev it would be nice to submit a ticket and have it auto-fixed by an agent. But in the devs case, it feels like it would be faster to just do it manually.

Reply on news.ycombinator.com