dckcandClaude Opus 5.5
a4308a5722
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) <noreply@anthropic.com>
2.7 KiB
name, description
| name | description |
|---|---|
| hackmd-deck | HackMD slide deck for a light talk — use when asked to draft slides, a deck, or a talk for show & tell, office hours, or a demo; when someone says "hackmd deck", "whip up some slides", or names a talk title and points at work to present (repos, git history, session transcripts). Covers the flashback story arc, emoji retro tags, and real artifacts as eye candy. Not for .pptx files or polished conference talks. |
HackMD deck
---
title: Good Fences Make Good Agents
type: slide
---
# Good Fences Make Good Agents
---
## 🎉 Monday's issue drafts itself
---
## How: who holds what
Example: Good Fences Make Good Agents; an early, overboard one: Jun 25 slides.
Context
A talk at something like Agoric's engineering show & tell: "Presentations should take little to no preparation", by engineers for engineers. The work already exists in repos, commits, test output, and session transcripts.
Problem
A deck has to hook the room and carry a technical story in a few minutes, without hours of prep.
Forces
- 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.
- Every slide costs attention (grice-maxims).
- Images in a repo don't show up in HackMD until uploaded.
Therefore
Tell it as a flashback, built from real artifacts, with emoji tags that add up to a retro.
The arc:
- 🎉 TADA! Look what I did. It must be on the thread the talk follows.
- Now that you're hooked, how I did that.
- Eye candy along the way: diagrams, verbatim code, test output.
- 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 ⏳.
Tag slides and bullets as you go; the last slide gathers them:
- wins: 🎉 the TADA · ✅ shipped · ✨ insight · 🙌 help, or a gift from someone else's work
- friction and follow-ups: ⏳ delays, not yet · 🧰 fragile tooling, ceremony · 💤 silent failures · 📘 docs · 🔔 alerts · 📈 observability · 🪄 surprises · 🔧 fixes owed · 🧱 walls
Write the deck in the repo the talk is about (e.g. docs/<title>-slides.md), images beside it, and commit it.
Resulting context
The deck takes an hour, not a day, and the retro slide doubles as a to-do list. The user pastes it into HackMD and uploads the images.