flâneur

Know your unknowns — examples

thariqs.github.io · 323 words · saved by 1 readers

The map is not the territory — the gap between them is your unknowns. Eleven self-contained .html artifacts for discovering them before, during, and after implementation. Each page shows the exact prompt at the top and the artifact Claude produced below it: paste the prompt, get something like the page. Before any code is written is the cheapest place to find an unknown. Ask for a blindspot pass when the territory is unfamiliar, brainstorm and prototype when you'll only know it when you see it, let Claude interview you about the rest, and hand it references when words run out. No matter how much planning you do, unknowns lurk in the territory. Have Claude keep a running log of every place the code forced a deviation from the plan, so the next attempt starts smarter. Shipping means other people inheriting your unknowns. A pitch doc answers the objections reviewers were about to raise; a quiz proves you actually understand what changed before you merge it.

01 Pre-implementation 8 demos Before any code is written is the cheapest place to find an unknown. Ask for a blindspot pass when the territory is unfamiliar, brainstorm and prototype when you'll only know it when you see it, let Claude interview you about the rest, and hand it references when words run out. Blindspot pass Claude scans an unfamiliar auth module and reports your unknown unknowns — seven blindspot cards, each with a copyable prompt fix, assembled into one better implementation prompt. 01-blindspot-pass.html→ Teach me my unknowns An interactive color-grading explainer —…

saved by

related reading