ga-wdi-boston/sql about sql

[jrhorn424]

240 minutes including breaks, around 4.5 units. Reasons this went long:

• It was the first time I led it
• The sql-study was mis-scheduled to come after this lesson, so that slowed lecture portion

I think I could do it in a long 3 next time.

[gaand]

Refactored lesson may partly explain length. Some of the opening should be moved to the study.

[jrhorn424]

205 minutes, 4.1 units actual.

[gaand]

4 points on the nose. Has never included delivery of DELETE section.

[jrhorn424]

LM: 220 minutes, long 4. ln my opinion, this talk can consistently be given in four units if the presenter is mindful of cadence and question strategy (see notes below). I do not believe moving the introductory material will save an entire unit, as #15 suggests. LM as a whole was experienced with SQL so that section was skimmed, but I still went over. My best guess is that half a unit can be saved by moving introductory material.

[jrhorn424]

017: 170 minutes, long 3. As with other talks in this sequence, I didn't take many questions during the demo. I did take more during the code-along as well as during lab discussions. This delivery went surprisingly quickly, due to mindfulness of cadence and how frequently questions were entertained. It may, in fact, be possible to deliver this in 3 units (revising my opinion above).