ga-wdi-boston/api-token-auth about api-token-auth HOT 10 OPEN

Currently at 2 points (Friday 2:30 to 4:35 with an unintended 20 minute break).

from api-token-auth.

Monday an additional 3. Weekend issue?

5 seems too much. Should it fit in three? Maybe have a break topic then (from ajax) then come back to this?

from api-token-auth.

I'll defer to you on specifics, but 5 does seem like it's too much. Are there any good seams to break this apart, or refocus on (different, fewer) objectives?

from api-token-auth.

I think we need to reassess and compare to history (Tom gave a tutorial or something) and maybe it takes this long and we need to break it apart. Maybe better scaffolding would help?

I'm not sure about the seems. Maybe my suggestion of a break topic helps? We'll have to chat.

from api-token-auth.

Short 4.

from api-token-auth.

Short 4, but it was Friday and we got off topic in a good way a bunch of times. #module.exports

from api-token-auth.

225 Calling 5.

from api-token-auth.

Paced really well, not sure why. 210 minutes, 4 actual (4.2). 9:30am-1pm.

from api-token-auth.

5 Actual. Went long again. Not too bad considering some of the other actuals, but would like to get this down to 4 actual for 017.

from api-token-auth.

4 Actual. Went from 1215 to 445 with breaks including lunch. => 3.5 hrs. It was much better. Had @jrhorn424 watch and give feedback. He noticed that I often do CFUs for things that I don't expect them to know, just to see what they might guess. While it's a good exercise, we don't really have time for things like that. It helped me stay focused. Would've kept it to 3hrs if almost the entire class had been able to spell passwords with 3 ss instead of 2.

from api-token-auth.