Code Room
Vibe codingHard
Question
An AI built this Java Kafka consumer that applies account state-change events. It parallelizes processing across a thread pool for throughput. Review the ordering assumptions.
void onRecords(ConsumerRecords<String, Event> records) { for (ConsumerRecord<String, Event> rec : records) { executor.submit(() -> { Account a = repo.load(rec.value().accountId()); a.apply(rec.value()); // e.g. SET_STATUS, then later DELETE repo.save(a); }); } consumer.commitSync(); // commit after dispatching}What correctness bug does the parallelism introduce, and what's the safe design?
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.