1 min lesson
The anti-pattern versus the signal
Choose two examples from the table in "The anti-pattern versus the signal" and explain what each teaches you to do.
Step 1 of 2
The anti-pattern versus the signal
- Cultural anti-pattern
- Paste model output and move on
- What they want instead
- Read it, run it, prove it works before it counts
- Cultural anti-pattern
- "The AI wrote it" as an excuse for a bug
- What they want instead
- "I shipped it" - you own output you accepted
- Cultural anti-pattern
- Avoid AI to look smart
- What they want instead
- Use AI hard and show judgment on top of it
- Cultural anti-pattern
- Trust the suggestion because it looks fluent
- What they want instead
- Distrust fluency; verify the claim under it
| Cultural anti-pattern | What they want instead |
|---|---|
| Paste model output and move on | Read it, run it, prove it works before it counts |
| "The AI wrote it" as an excuse for a bug | "I shipped it" - you own output you accepted |
| Avoid AI to look smart | Use AI hard and show judgment on top of it |
| Trust the suggestion because it looks fluent | Distrust fluency; verify the claim under it |
Watch out
On the paid onsite especially, narrate your judgment. Silently accepting good AI output looks identical to silently accepting bad output. Saying "I'm rejecting this suggestion because it ignores our auth boundary" is the signal they can't see otherwise.
Where it shows up
This mindset isn't confined to the build round. It surfaces in technical phone screens, the onsite and the behavioral round when they ask how you work with AI. Treat "AI drafted it, I verified and owned it" as a through-line for the whole loop.