Mark's talk focuses on four lessons in teaching computer science:
- "Increasing value through relevance and context"
- "Anchored collaboration helps (sometimes)"
- "We can teach computing by meeting students where they are"
- "We can restructure and improve learning materials based on research principles"
- for every software developer, there are 9 end user programmers (database queries, spreadsheet macros, etc) who don't know that computer science is a thing that can help them with what they do
- AP computer science in Georgia is predominately a white and Asian male test
- there are not a lot of people looking at why programming is so hard at a deep, cognitive level
- USCD implemented media computation with peer instruction and pair programming; since then, they have increased retention of CS majors into second year by 30%
- when teaching HS teachers about programming with videos, simply adding subgoal labels to the video significantly increases the teachers' ability to learn
Great video. In my opinion we have a big, HUGE problem all over the world and across many grades, from elementary school to university: people think that "computer science" is about using computer, they don't really think it's a good idea to understand how they work or why they work in "this or that" way. As long as there is this totally dumb misconception about what should be taught regarding CS in schools and universities (ok, except in degrees which are specifically technical) humanity will not go forward.
ReplyDeleteAgree! This is a big reason I aim to cover actual CS in the "intro to computers for arts and social sciences" class I sometimes teach. Traditionally it's mostly MS Office all term long.
ReplyDelete