Comment on: Show HN: Cq – Stack Overflow for AI coding agents
I'm surprised to see this getting so much positive reception. In my experience AI is still really bad with documenting the exact steps it took, much more so when those are dependent on its environment, and once there's a human in the loop at any point you can completely throw the idea out the window. The AI will just hallucinate intermediate steps that you may or may not have taken unless you spell out in exact detail every step you took.People in general seem super obsessed with AI context, bordering on psychosis. Even setting aside obvious examples like Gas Town or OpenClaw or that tweet I s
Comment on: Ask HN: How is AI-assisted coding going for you professionally?
Context: micro (5 person) software company with a mature SaaS product codebase.We use a mix of agentic and conversational tools, just pick your own and go with it.For Unity development (our main codebase and source of value) I give current gen tools a C- for effectiveness. For solving confined, well modularisable problems (eg refactor this texture loader; implement support for this material extension) it’s good. For most real day to day problems it’s hopelessly confused by the large codebase full of state, external dependency on chunks of Unity, implicit hardware-dependent behaviours, etc. It
Comment on: An Honest Review of AI Programming
Put it this way, the agent may well be hallucinating behind the scenes when it is coding for me, but I never see that, because it obviously verifies by compiling and testing the solution and won't show me something that is broken.
Comment on: Eight Myths on Software Engineering and GenAI
> observe that the agent day after day do handle user input safelyHow do you observe the issues that aren’t apparent via a GUI? Do you notice the circular logic in your reasoning?