Question
An AI agent added a new service method to a large Java codebase. It works, tests pass. But your team has strong conventions: errors flow through a `Result<T>` type (never exceptions across service boundaries), all external calls go through a `@Resilient` wrapper, and logging uses structured `log.atInfo().with(...)`. The agent's new method throws raw exceptions, calls the HTTP client directly, and uses `System.out.println`. How do you efficiently verify a generated method conforms to house conventions, and why does this matter beyond style?
Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it — tests, edge cases, reading critically — and how you’d re-prompt or decompose to get it right.
Vibe coding: describe the solution in plain language (or narrate it) and the coach grades your approach. Generating runnable code from your description is coming next.