On 19/03/2012 22:15, David Neil wrote:
On 20/03/12 03:16, James Broadhead wrote:
On 19 March 2012 14:08, Jonathan Hartley<tart...@tartley.com> wrote:
On 19/03/2012 13:17, James Broadhead wrote:
Perhaps a "no interactive demos" rule would be good, as these always
take more time than you'd imagine.
But I *like* interactive / live-coding demos! I'd rather make sure the
speakers know they **will** be cut-off in mid-stride if they overrun
than
attempting to govern duration by the fairly indirect proxy of talk
format.
So do I, but in my experience they're the easiest way for the
presenter to completely lose track of time. If we were talking about
two 7.5 minute talks, yes. For a 5-minute talk though ...
I quite liked the semi-interactive (pseudo-interactive?) presentation
shell from last time's default argument talk, in that it managed to
replace slides with alternating printed code examples and running code
(without the presenter touching the keyboard). {Was a link to that
shared around?}
Why place limits?
The primary purpose of the meeting is not the lightning talks, although
they are a welcome bonus - but they eat into time for the remainder of
the dojo.
--
Jonathan Hartley tart...@tartley.com http://tartley.com
Made of meat. +44 7737 062 225 twitter/skype: tartley
_______________________________________________
python-uk mailing list
python-uk@python.org
http://mail.python.org/mailman/listinfo/python-uk
