Live data from Hacker News

Tell HN: It's official, I'm done with Claude

news.ycombinator.com

11–12 of 12 posts

Re: Tell HN: It's official, I'm done with Claude

#11

Serious question here. Have you taken a moment to step back and truly evaluate your productivity when using LLMs for code generation? I don't mean the obvious confirmation-bias tickling stuff like "create a form with these fields and validation". I mean from a whole-system, total effort analysis, from idea to production, support and maintenance. I'm curious what you find. My current theory is that the industry will l…

This resonates. The problem I keep running into isn't that the model is bad — it's that the feedback loop is too thin. A y/n in the terminal isn't enough to catch when the model does something subtly wrong.

Re: Tell HN: It's official, I'm done with Claude

#12

Serious question here. Have you taken a moment to step back and truly evaluate your productivity when using LLMs for code generation? I don't mean the obvious confirmation-bias tickling stuff like "create a form with these fields and validation". I mean from a whole-system, total effort analysis, from idea to production, support and maintenance. I'm curious what you find. My current theory is that the industry will l…

This resonates. The problem I keep running into isn't that the model is bad — it's that the feedback loop is too thin. A y/n in the terminal isn't enough to catch when the model does something subtly wrong.

I've been building a review UI layer for coding agents (Claude Code, Codex) that lets you actually inspect and edit what the agent is about to do before it executes: https://github.com/agentlayer-io/AgentClick

Turns out most of the "dumb" mistakes OP is talking about are catchable — you just need to actually see them before they ship.

Post reply on HN