From a4308a5722fc1436a4904f97221095495cefd670 Mon Sep 17 00:00:00 2001 From: Dan Connolly Date: Fri, 9 Oct 2026 14:09:46 -0500 Subject: [PATCH] hackmd-deck: drop the no-questions rule It came from one deck's revision, not from how these talks go; step 4 returns to the draft's wording. Co-Authored-By: Claude Opus 5.5 (1M context) --- hackmd-deck/SKILL.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/hackmd-deck/SKILL.md b/hackmd-deck/SKILL.md index 60d48eb..c4e91d2 100644 --- a/hackmd-deck/SKILL.md +++ b/hackmd-deck/SKILL.md @@ -36,7 +36,6 @@ A talk at something like Agoric's engineering show & tell: "Presentations should ## Forces -- The audience follows up afterward, or doesn't; the deck is no place to ask. - A TADA from a side thread leaves the audience waiting for a payoff that never comes. - Designed, built in dev, and deployed look alike on a slide. - Real code and real output convince; paraphrase doesn't. @@ -52,7 +51,7 @@ The arc: 1. 🎉 TADA! Look what I did. It must be on the thread the talk follows. 2. Now that you're hooked, how I did that. 3. Eye candy along the way: diagrams, verbatim code, test output. -4. Conclusions and challenges. Slides **show** challenges; they don't pose questions. +4. Conclusions and/or challenges that lead to discussion. Ground every slide in the record: quote code and test output verbatim (trim with `...`), check claims against the code and git history, and mark what's only designed or not deployed with ⏳.