What can be better next year?

[tommeagher]

What worked well this time? What could've gone better? What missed the mark? Is there anything we could've used more of or less of?

Any and all feedback and ideas are welcome.

@elainewong, @meli-lewis, @chrislkeller, @aboutaaron, @zufanka, @robroc, @esagara, @thejqs?

Any PyCAR students have advice or reactions?

[robroc]

One quick thought: we could update the HTML table used in the scraping portion. That 2015 table hosted on S3 is looking pretty dated.

[tommeagher]

@robroc, this is a good idea. I think we can fairly easily freshen that data with more recent films from the same source.

[thejqs]

Little bit of feedback I got was that we spent a lot of time explaining at the expense of helping them build up some muscle memory. (I'm paraphrasing.)

Almost all of us have helped with PyCAR more than once, and I found myself wondering, too, whether I spent too much energy anticipating problems and trying to pre-explain them out of existence instead of letting things happen more as learning-by-doing moments. It felt like they raised their hands for help less this year and that that might be a byproduct of less typing.

I'd be interested to hear what y'all thought about that.