1 min lesson
Structure the 5-minute present
Put yourself in this case: "A peer reviews your trial project mid-build and says the accept control is hard to find. How you respond is being graded as much as the code. What's the strong move?" Give the clearest next step.
Step 1 of 2
Structure the 5-minute presentDemo skeleton
- 0:00–0:45 · Problem
- What interaction you tackled and why it's hard on an AI-native editor.
- 0:45–2:00 · Decisions
- Two or three real choices - a motion call, an a11y call, a scoping cut - with the reasoning behind each.
- 2:00–4:00 · Demo
- Drive it live. Show the happy path, then one edge case you handled on purpose.
- 4:00–5:00 · Next steps
- What's still at 90%, what you'd build next and what you'd want feedback on.
Decisions and demo carry the weight; problem and next-steps are the bookends.
A polished, finished, well-explained small feature beats a sprawling half-built one every time. The team is asking a single question across two days: would we want to ship next to this person on Monday? Finishing, explaining and taking a note gracefully answers yes louder than raw ambition does.
Getting defensive when the peer feedback lands is the quiet killer. If someone says the accept affordance is unclear, the win is “you're right, let me try the control inline instead of below” - visibly changing your work. Truth-seeking here means killing your own decision fast, not defending it.