At 08:55 15/5/01 -0400, Berin Loritsch wrote: >Here is my biggest delimna: I don't think I requested enough time >with my session. There is just too much information. I think that >it's a double edged sword, and if I make the session too long, it >will be a deterent, and if I make it too short I won't be able to >disseminate the information.
;) >I may have to break it down into 2 or three sessions. But, I would >need to know--if you were at the ApacheCon (hypothetically speaking) >how many sessions on Avalon would you attend? > >I am thinking of doing the following approach: > >30min: Introduction to Avalon >60min: Programming with Avalon >60min: Designing with Avalon If I had no idea what Avalon was then there is no way I would schedule myself to see all three sessions. I may end up at three if the first one or two was good but not by design. >Is this too much? Or, should I do two sessions: > >60min: Designing with Avalon (introduction and analysis techniques) >60min: Programming with Avalon I would definetly think about attending a talk if there was two sessions (ie one introduction and one advancedish). I would probably think of more sexier names if I were you - something that emphasized "component", "reuse" and "money-saving" ;) (Or something better - I am not much of a salesperson). However I would probably like to see programming and design in both - Some say I have a short attention span though ;) >I am finding that it is very difficult to cram everything into one hour. I can imagine ;) Cheers, Pete *-----------------------------------------------------* | "Faced with the choice between changing one's mind, | | and proving that there is no need to do so - almost | | everyone gets busy on the proof." | | - John Kenneth Galbraith | *-----------------------------------------------------* --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
