I say ready, but I am going in the wrong direction with time. Something is
going to have to give, either with the next section or these existing
ones. I want time for interactive demonstrations.
This is still too long, so I'm going to need another round. There's also a
conclusion that does not yet exist. I had also wanted to type some things
out at the keyboard in place of certain slides, which would take even _more_
time.
More work to be done, and not much time to do it. And then I have to
actually rehearse without my notes (which does sometimes change the times
slightly) and start rehearsing sections all the way through (a section may be
less than the sum of its times beacuse of rounding done on each slide).
And of couse timing varies during the talk. Though with my SAPSF talk two
years ago I had the timing at a perfect 40m in practice and in presentation.
This talk is now officially far too long. I need to shave off quite a bit
of time.
So the next steps are going to be to sort out what I want to do with the
intro, start stripping down some sections, and then further refine the times
by practicing them out loud a bit more. Some sections could benefit from a
little tweaking in general.
It always sucks when this happens because it feels like I'm throwing out
work, but that's how it goes, in programming and in everything else---you
need to get everything out there so you can distill the good stuff from it.
This is the last section of the talk. It will be augmented slightly once I
have a better idea of where I stand with the earlier sections.
I wasn't able to fit in even close to everything that I wanted to, but I
didn't expect to.
This is likely sufficient to get me through my entire talk time, but I have
a number of other interesting things I want to get to. Let's see what the
timing looks like in a couple of commits.
This is the correct order. Things start out DEVOID of information,
then are LACKING when they contain only pieces of the final slide
and notes, and then are RAW when they contain both but haven't yet
been proofread / further refined.
Moving along, though I'm spending way more time on getting up to speed than
I originally expected. I suspect that I'm going to have to trim this a
bit. All the more reason to get it versioned so I can reference old
versions if I trim it too much.
I fly out to BOS in under 13 days and my talk is in under 15. Getting close
again. The difference this time, though, is that I don't have to do any
research, which is saving me a ton of time compared to the last couple of
years, which were research talks. Much less stressful. I could give the
presentation ad-hoc without preparation, though it'd be a tad bit messy
and disorganized if I did that.
Alright, now I feel like I'm stalling in typing this commit message. Back
to work for me.
Some of the talking may need to be shortened. I havne't timed it yet, but
it sure does feel like a lot.
With that said, this is a very important part of the talk, since it sets the
stage for everything that's about to follow.
Mike Gerwitz