ga-wdi-boston / ruby-enumerable-comparable

Other
1 stars 139 forks source link

ga-wdi-boston/ruby-enumerable-comparable #1

Open gaand opened 8 years ago

jrhorn424 commented 8 years ago

192 minutes actual, 3.84 units. Went into depth due to really solid questions from a variety of developers. Probably shouldn't have focused on reading starter code as much as using it.

Spent almost a unit reading Comparable documentation, first code example. It made reading Enumerable and using Enumerable a breeze.

gaand commented 8 years ago

75 minutes. Should have taken more.

jrhorn424 commented 8 years ago

165 minutes (3.3 units). Every minute was needed for this cohort. Developers appeared to have a strong grasp on attr_reader and friends in the previous days, but a significant fraction were completely lost when CFUs were made while reading deck.rb. Re-emphasized the difference between local variables, methods, and instance variables. Spent a lot of time on reading code line-by-line and asking what return values were.

Reading comprehension was good with the documentation. CFUs on how to make Enumerables and Comparables were fine. CFUs on learning objectives mostly solid. The lack of comprehension was entirely on reading Ruby code.

jrhorn424 commented 7 years ago

110 minutes, 2.2 units. Held questions until code-alongs. Focused in demo on describing what was happening rather than reading ruby line-by-line.

Focused on steps for implementing Enumerable methods, and steps for implement comparison methods. (In other words, focus on the learning objectives and stick to the script, without insisting on every CFU focusing on reading statements/expressions).

jrhorn424 commented 7 years ago

120 minutes, 2.4 units with 50 minutes per unit.

Went long this time due to our proclivity for entertaining questions during demos. Should have finished in 2 flat.

danman01 commented 7 years ago

~ 110 minutes, went pretty well as this builds nicely on the previous talk which I also gave. Doing both enumerable talks worked well as I knew exactly what I'd covered and what to review. We built the deck class as a code-along, and implemented each and included Enumerable. I left implementing SteppedRange for workshop time.