2.5 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 markers for wins and friction, 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
I have done a bunch of stuff I think is interesting, but I can't justify the time to make a polished presentation.
Therefore
Let an agent do a quick-n-dirty one: a flashback, built from the record.
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 ⏳.
Mark wins, losses, challenges, and friction with emojis: visually appealing, intuitive at a glance.
- wins: 🎉 the TADA · ✅ shipped · ✨ sparkle, delight · 💡 aha: now I see how to address the issue · 🙌 help, or a gift from someone else's work
- friction and follow-ups: ⏳ delays, not yet · 🧰 fragile tooling, ceremony · 💤 silent failures · 📘 docs · 🔔 alerts · 📈 observability · 🪄 a wish, often one a problem brings to mind · 🔧 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 15 minutes: the agent spends 5, the presenter polishes for 10. The user pastes it into HackMD and uploads the images.