search

ga-wdi-boston / rails-api-one-to-many

Other
0 stars 92 forks source link

ga-wdi-boston/rails-api-one-to-many #1

Open laurenfazah opened 8 years ago

laurenfazah commented 8 years ago

We spent an hour at the top setting the ga-wdi-boston remote as upstream to pull updated branches into domain repos. However, I also forgot to discuss serializers. I'd estimate 4.5 points for next time with upstream hammered out and adding in serializers.

jrhorn424 commented 8 years ago

@payne-chris-r I know Brian had to leave early, as did I. Was this finished by 4 PM? IIRC we started at 12:30 PM that day, since I took until 11:30 AM for my morning talk.

cc @ga-wdi-boston/core

berziiii commented 8 years ago

We did finish the code-along by 4pm. We then used 1-on-1 time and continues through lab and provided support. total, 210 minutes for everything, including lab support.

payne-chris-r commented 8 years ago

Was this resolved? It looks like @berziiii answered the questions. I don't remember far back enough on this one, but I'm clearing my 'assigned' and just came across this...

payne-chris-r commented 8 years ago

9:40-2:15 with breaks and lunch. I think it would go faster if we addressed #7. Or at LEAST mentioned that they need 2 terminal windows open (one for code along, one for lab) that each have 2 tabs (rails server and repo for generating).

jrhorn424 commented 7 years ago

195 minutes, 3.9 actual.

Code-along and Lab were lumped together as exercises for the developers. Did not cover serializers and serializing out related objects, which is definitely necessary.

This README needs to be scaffolded better (my responsibility, which I failed to do this iteration), and I think we can cover all relevant topics in 4 units.

samguergen commented 7 years ago

200min. 5 actuals. 3 breaks. Delivery went smoothly, especially from the middle of the talk, and all topics were covered.