SLIDES.PRG

WHAT IT IS.

A lecture deck for a 2018 associate-degree course at IESB Brasília on blockchain use cases — the same 24-hour course CHAINOPOLY.PRG was built to anchor.

HOW THE CLASS USED IT.

The course was my first real attempt to teach blockchain to a non-technical audience in 2018, and the deck grew up alongside the syllabus it was meant to support. Two months before the first session, I knew the biggest risk was being asked to put a number on what people were actually doing with the technology, and not having anywhere to point. Most of the audience had heard the words; very few had seen a real working example. The deck was therefore a survey first, which pivoted to the live example: Chainopoly was built to be the post-mortem the class walked through in the later sessions. So the deck's shape was survey-of-the-world → narrative-of-one-system. The first sessions named the patterns; the later sessions took them apart.

WHAT I LEARNED.

• The shape of a deck for a non-technical audience is survey first, then one worked example. Trying to teach by exception ("here's the one project we built, here are the others") reads as insider-only; starting with the wider world and then narrowing gives the audience time to put the chosen example in context.

• One HTML per session is the only revision shape worth committing in. A single monolithic deck either doesn't get revised after the first session or the diff becomes an unrelated blob. The per-day split made each session editable on the bus ride to class.

• Version control is honest about the deck in a way the slides themselves aren't. The commit log shows that the technical-stack material landed a month into the course, not on day one — a fact the deck itself never reveals to students who weren't there.

• The course deck outlives the course. The final commit rewrote the syllabus, not the slides — and it closed with a re-shaped outline, which is what the next instructor needs more than next session's slides do.