When AI writes the code, reading it is your main job. It's scored directly in AI-allowed rounds.
Read for what the author assumed. Most bugs live at boundaries: empty input, one item, duplicates, huge input, and bad data.
AI drafts have recurring faults. They handle the happy path well, invent APIs now and then, and may make a test pass by special-casing it.
Keep a fixed order so you don't skip things under pressure: purpose, boundaries, state, errors, cost.
- What's the five-step review order?
- Purpose, boundaries, state, errors, cost.
- Which inputs do you always check?
- Empty, one item, duplicates, very large, and malformed.
- Name three common faults in AI-written code.
- It handles only the happy path, invents an API or option, and may pass a test by special-casing it.
- Why is a plain object a risky map in JavaScript?
- It inherits keys like 'constructor'. A Map starts empty.
- What should you read when a fix turns a test green?
- The fix itself. A green test doesn't show the fix is real, since it may have special-cased that input.