Python presentations

[Cameron Simpson]

On 13Sep2012 17:00, andrea crotti <andrea.crotti.0 at gmail.com> wrote:
| I have to give a couple of Python presentations in the next weeks, and
| I'm still thinking what is the best approach.
| 
| In one presentation for example I will present decorators and context
| managers, and my biggest doubt is how much I should show and explain in
| slides and how much in an interactive way (with ipython for example).
| 
| For my experience if I only see code in slides I tend not to believe
| that it works somehow, but also only looking at someone typing can be
| hard to follow and understand what is going on..
| 
| So maybe I should do first slides and then interactive demo, or the
| other way around, showing first how everything works and then explaining
| the code with slides.

Slides first.

My own experience is that someone typing code where I've not seen at
least a summary explaination ahead of time slides straight off my brain.

Ideally, two projectors: the current slides and an interactive python
environment for demos. That way people can cross reference.

But otherwise: a few slides, then a short demo if what was just spoken
about, then slides...
-- 
Cameron Simpson <cs at zip.com.au>

Standing on the faces of midgets, I can see for yards.
        - David N Stivers D0D#857 <stiv at stat.rice.edu>