Leo Simons wrote:
>
> > > > :) I'm writing it. Really though, I am writing a three part paper
> > > > that I am going to donate to the Avalon project--I just need a word
> > > > processor to write it at the beginning.
> > >
> > > Good you repeated that. I think I'll go and work on the phoenix
> > > design documentation and javadoc then (I am assuming you are just
> > > doing a 'hands-on' for your presentation?)
> >
> > 'hands-on'?
>
> When you have like an hour you cannot really go into theoretical
> advantages of component development, possible designs solutions
> or detailed product comparisons on a high level.
I think that will be my approach--it's just that the docs will be much more.
> > The ApacheCon specifies all papers and slides need to be
> > made available in RTF (not HTML, Doc, PDF, or anything else).
> > If only FOP handled RTF....
>
> You could write in xml, xsl to html, open that in word, apply
> some word template and save that as rtf - it's what I've done
> occassionally.
To organize my thoughts, it really helps to have a formal word processor.
> > Here is my biggest delimna: I don't think I requested enough time
> > with my session. There is just too much information.
>
> fact: the average college graduate has trouble focusing on a given
> subject for more than 50 minutes. The first ten minutes of a class,
> lecture, session or whatever are almost completely non-productive.
> Peak productive lasts from around minute 20 to minute 35. After that,
> performance drops. How much depends on how motivated the audience is.
> In any case, a 15 minute break (at least) is wise to have once an hour
> (depending on your audience, preferably once every 40 to 70 minutes).
Sounds about right.
> > 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 would never plan to attend more than one session about a project
> I had not seen before (and I assume the vast majority of your
> audience isn't very familiar with Avalon).
I'll use this session to whet their appetite. I might have a recurring
theme (if I can come up with a series of sessions for successive
ApacheCons).
> > I am finding that it is very difficult to cram everything into one hour.
>
> ;) My advice: don't try to.
> It took me about - i dunno - 10 hours to learn how to work with
> Avalon, then another week to learn how it works internally, and
> then another week to learn how to work with avalon properly;
> how it will/should work internally is something we're still all
> trying to figure out. That is never going to fit in 2 hours =)
Yep. Part of that is because the docs need some serious improvement.
That's what we are focusing on now. I may have to write the docs
verbose, and summarize with my presentation later. Seriously, well
written docs will answer most questions.
> Here's a suggestion:
>
> "Avalon 101: use a cutting-edge Component Oriented framework to
> build more reliable software while reducing costs and increasing
> reusability. 1 hour session with Berin Loritsch."
I'll reexamine the description I have, it should be pretty catchy.
Anyway, I think what I am going to do only one session, and rely
on the docs to fill in the gaps that are inevitable. I am used to
a one-on-one style of teaching, but while it is effective, it isn't
the best use of my time. This is an opportunity to grow.
Perhaps we can talk more off line to help me out with some strategies...
> I have about 6 months of experience teaching kids of age 11-13
> mathematics. What I've learned there holds true for adults as
> well: within 3 minutes of getting interested in something, they
> should have a clear picture of why it useful to them and what
> steps they have to take to grasp the subject. My guess is that
> for programmers with a masters degree, you can stretch minutes
> into 6 or 7...if your first 6 minutes go well, the entire
> session will thereafter be a success. If not...well, that 2nd
> session will be a quiet one >:)
I have experience training adults in using software I've written,
but in very small groups (1-4 developers). I have an informal
approach to teaching in that I like to have a section set aside
for questions and answers. After I cover a major concept, I allow
for questions about what we just covered.
> Some things to leave out of the picture:
>
> - Cornerstone. Mention it exists, nothing more.
That was part of the plan.
> - LogKit. Most will be familiar with logging; logkit does the
> job perfectly.
Yep.
> - threading, pooling, and similar topics. Each of them deserves
> a separate session. Simply mention that avalon has implementations
> for all the most neccessary problems, and perhaps use one or
> two classes in examples.
The last section in the paper gives an overview of the what the
different Excalibur facilities are--allowing for exploration
independantly.
> You get the idea. I think an explanation of COP and patterns
> along with their advantages, and then how Avalon provides and
> enforces COP and pattern usage, followed by how to use
> Avalon is 90% of your first session. The rest goes to fancy
> talk about all the features of Avalon and why it will make you
> rich.
I'm not a motivational speaker, but I am aming at one session
for now. If I do a good job, I will most likely hold future sessions
later.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
