Prep Room
Sign inCreate account
Code Room
Vibe codingMediumvc-g231
Subject Ai code reviewLevel Mid–Senior~15 minCommon in Algorithms & data structures interviewsIndustries Software development, Technology

Question

An AI agent submitted this Rust change to your event-ingestion service, claiming it "adds graceful retry with jitter using the existing tokio runtime":

rust
async fn send_with_retry(client: &Client, evt: &Event) -> Result<()> {    for attempt in 0..MAX_RETRIES {        match client.send(evt).await {            Ok(_) => return Ok(()),            Err(_) => {                let backoff = 2u64.pow(attempt) * 100;                tokio::time::delay_for(Duration::from_millis(backoff)).await;            }        }    }    Ok(())}

The agent says it compiles on its machine. What do you verify before believing that, and what real bugs are here?

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
Describe your solution

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.