This matches what I've seen. The teams that get the most value from AI coding aren't the ones with the best prompts — they're the ones with the best verification pipelines. Golden tests, type checking, automated lint. If your CI doesn't catch it, your users will. I'd rather spend time building good guardrails than writing better prompts.
The real unlock for me was treating AI context like onboarding docs. I wrote an AGENTS.md that describes our project conventions — ORM patterns, error handling, test expectations — and suddenly the same model that was 'hallucinating' started generating code that actually followed our patterns. The problem was never the model. It was that I was asking a new team member to code without any documentation.
Some comments may only be visible to logged-in visitors. Sign in to view all comments.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Top comments (3)
This matches what I've seen. The teams that get the most value from AI coding aren't the ones with the best prompts — they're the ones with the best verification pipelines. Golden tests, type checking, automated lint. If your CI doesn't catch it, your users will. I'd rather spend time building good guardrails than writing better prompts.
The real unlock for me was treating AI context like onboarding docs. I wrote an AGENTS.md that describes our project conventions — ORM patterns, error handling, test expectations — and suddenly the same model that was 'hallucinating' started generating code that actually followed our patterns. The problem was never the model. It was that I was asking a new team member to code without any documentation.
Some comments may only be visible to logged-in visitors. Sign in to view all comments.