Code Room
Vibe codingHard
Question
An AI assistant wrote this Java method to transfer funds between two accounts. Code review passed, tests pass. Under concurrent load, a few accounts end up with balances that don't reconcile.
@Transactionalpublic void transfer(long fromId, long toId, BigDecimal amt) { Account from = repo.findById(fromId); Account to = repo.findById(toId); if (from.getBalance().compareTo(amt) < 0) throw new InsufficientFundsException(); from.setBalance(from.getBalance().subtract(amt)); to.setBalance(to.getBalance().add(amt)); repo.save(from); repo.save(to);}What concurrency hazard exists despite `@Transactional`, and how do you fix it?
What a strong answer looks like
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.
Learn the concepts
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.
Run or narrate your approach, then ask the coach.