-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ga-wdi-boston/sql #9
Comments
240 minutes including breaks, around 4.5 units. Reasons this went long:
I think I could do it in a long 3 next time. |
Refactored lesson may partly explain length. Some of the opening should be moved to the study. |
205 minutes, 4.1 units actual. |
4 points on the nose. Has never included delivery of |
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. |
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). |
No description provided.
The text was updated successfully, but these errors were encountered: