Paulo meeting 2019-09-17

Paulo meeting 2019-09-17

RESEARCH STATEMENT What’s expected–references? Not?

Cool findings. What my research found. It’s impressive and cool. I actually make real software that’s used in schools, that leads to change. think about limiting customization to just the first and last paragraphs.

TEACHING STATEMENT Back up the testimonials with quantitative data. Say what I would be comfortable teaching, and what courses I would like to design. Learn about the department structure Design the teaching load (design, CS, …) Experience with TLTL: interdisciplnary coolness Experience with Stanford’s inviting intro CS courses. I would be excited to be a bridge between the departments. Often CS and education people don’t collaborate that much; I have been successful in bridging those worlds. Teaching CS as an option.

COVER LETTER hi, here are my materials, my publications.

CV Manuscript in preparation. Already contacted the editor, who reacted positively.

CHAPTER 4 Even though it’s a grounded analysis, have categories and framework for analysis more or less defined. The two directions–taking up the stories in classroom, and taking up computational stuff. What would constitute an event for each one.

Are these two case studies enough? Do they generalize? Might I choose a third student, who is not a particularly charismatic research subject? Brianna? I could also consider using the third student as a sort of validation. Guide the analysis.

CHAPTER 3 Plot the use of syntactic elements over time; possibly cluster Is there a kind of kid who’s going to take up everything.