MWPLS practice talks

[ccshan]

Leave comments for MWPLS practice talks here.

[ccshan]

For a 5-minute talk, you get a budget of 10 slides (including transitions), including 1 slide of code and 2 bullet items. None of your grammars add any comprehensible detail to the talk. Use pictures. Develop an animation of monotonic increase. Depict relationships between key phrases by showing them on the screen and drawing labeled arrows between them. Avoid full sentences.

[ccshan]

Record and time yourself. Write down a script, practice it, memorize it, then throw it away.

[ccshan]

---

[ccshan]

I think the "demo" is not really a demo so it's more efficient to just turn it into slides

[ccshan]

---

[ccshan]

Double your font size. If you're going to point using a mouse pointer
at all, it should be as large as an uppercase letter.

Show your last two slides first, as one slide. This is the punch line!
PUNCH LINE FIRST!!!

Skip the grammar and just show the typing rules. Even better, can you
skip also the typing rules and just show programs that barely type-check
and programs that almost type-check? Then skip all theorems and the
definitions they depend on, and summarize in one slide.

[madheime]

Deyaa,
This feels like about a 15 or 20 minute talk, at least. You probably won't be able to explain things properly in 5 minutes. So

Thoughts for shortening it:

• This talk should have probably only one point. You could do one point from the paper: "here's something interesting we learned," or your point should be "you should go read this paper."
• Pick one (or zero!) complicated slide(s) that has the idea you really think people will want to hear, and build around that.
• Do you want to advertise the work, give a pearl of wisdom from it, or seek some feedback on it or insight of future/ongoing work?