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