search

ga-wdi-boston / mongoose

An introduction to mongoose
Other
5 stars 136 forks source link

ga-wdi-boston/mongoose-crud #6

Open GA-MEB opened 8 years ago

GA-MEB commented 8 years ago

With breaks, this took almost exactly 3 hours.

By the end of hour 1, we were in the code-along, just about to start implementing CRUD. By the end of hour 2, we had implemented Create, Read, and Update, and were about to start working on Destroy. We started the lab at the 2.5hr mark, and one squad did finish the lab, but the others did not, so we may need to start the lab sooner.

RDegnen commented 8 years ago

Started at 1:30 due to outcomes and went all the way to 4. But wasn't able to get to the lab at the end.

berziiii commented 8 years ago

150 minutes. Good pace, but didn't get to lab during this timeframe. Lab was encouraged for 1-on-1/workshop time at the end of the day.

RealWeeks commented 8 years ago

All morning plus 15 minutes after lunch. Did not get to the lab during this time frame as well. Encouraged developers to work on lab in free time.

payne-chris-r commented 7 years ago

3 actual 2 in the afternoon and 1 in the morning.

payne-chris-r commented 7 years ago

This talk is too long and may need to be descoped (or scheduled better). Took me 940-2pm (with breaks + lunch). 200 minutes => 4 actual

BenGitsCode commented 7 years ago

9:40-1:00PM 200 minutes => 4 actual (3.3) one 5 min break, two 10 min breaks.

I agree with Chris’ comment above in that this needs to be restructured significantly. After delivering, I better understand the issues associated with this talk.

We were ready for the lab with just under an hour left, but I was getting great mongoose questions and some of the developers saw opportunities for enhancing our update action to better handle updating nested properties. I don’t think the solution we worked through together is ready to merge, but it’s a lot closer and I wanted to support that line commitment to bettering code.

With just under 20 minutes left we focused on doing CFU’s on objectives and wrapped up by revisiting the diagram I drew at the beginning, comparing the relationship of SQL->ActiveRecord->Rails with Mongo->Mongoose-> Express, making it clear that we haven’t taught express yet and that’s why we’re creating such a simple console app. Because we haven’t exposed that layer of node-built servers yet, and only want to focus on interacting with our mongo database with mongo, with no other concerns.

They were encouraged to work on lab during workshop and fist of five “defining crud actions using documentation and referencing this repository" came back strong (5s, 4s, a couple 3s and nothing less) I know that’s only as reliable as they are honest, but I got the sense it came together the most for people during the 45 minutes that we were focused on catching up from the code alongs and testing different commands in there terminal. (hands on)

I think diagrams and framing and defining Schema, model and document all give the necessary foundation that clicks into understanding when they actually get hands on with it—keeping them engaged up until that section was the hardest part, and would be much easier if there was a more incremented pattern of Demo, code-along, catch up, review, repeat. To keep them more active and engaged.

jrhorn424 commented 7 years ago

Please include as issues anything you'd like to see added or changed for future iterations. Thanks for the lengthy notes, @BenGitsCode!