This post originated from an RSS feed registered with Java Buzz
by Chris Winters.
Original Post: Some notes after a presentation
Feed Title: cwinters.com
Feed URL: http://www.cwinters.com/search/registrar.php?domain=jroller.com®istrar=sedopark
Feed Description: Chris Winters on Java, programming and technology, usually in that order.
For the next time I think about doing a 3+ hour presentation:
Don't
Well, actually if you've done most of the work it's probably okay to do it.
Bribe the schedulers to ensure you don't go up against anybody with the words 'scalable' or enterprise in the titles. (Beer would probably work.)
...alternatively, put the words 'scalable' and/or 'enterprise' in your title.
It's a good idea to do something simple really quickly, then decompose in detail how it actually worked.
Slides showing code generally don't work...
...but slides with code that highlight each section of the code on successive slides accompanied by verbal descriptions work pretty well.
Live demos work well, but you must prepare prepare prepare. Then prepare some more. And for god's sake listen to your wife and don't modify the framework you're speaking about and using in the demos in the days before your presentation.
If the process of the live demo seems kind of clunky then you probably need to rethink the process
Previous Topic
