Tue Oct 12

Discuss your work for the "exercises in style" task.

Possible discussion topics :

• description of problem
• inputs
• sub-tasks
• test cases
• useful data structures

Next week : long weekend; no assignment - use the time to relax and/or catch up.

Coming next : choose at least two of the different code styles to examine & explain

Projects : by Tue Oct 26, share an update of your progress so far, by posting sometning in the projects folder - a short explanation, code, screenshots - whatever seems appropriate. Come to class that day ready to show the class in a 5min "here's what I'm doing".

aside

• Understanding all of Python, through its builtins | hackernews discussion
• Peter Norvig joins Stanford Institute for Human-Centered AI - interview | hackernews discussion
  • from that interview: Learning to code is a useful skill. When I was in middle school, we didn’t have coding, but I was required to learn touch typing. That was also a useful skill. But learning to type well does not change the way you see the world, and by itself neither does learning the syntax of a programming language. The important part is what you do when you’re coding: moving past small rote-learning exercises to substantial multi-part projects; learning how to choose your own projects; learning to model some aspects of the world, make hypotheses, and test them; committing errors and correcting them without getting discouraged; working on a team; creating something useful that others will use, giving you pride of accomplishment. If you can do all that with coding, great. If you can do it with a no-code or low-code approach to technology, also great. If you can do it by sending kids out into nature to explore and do experiments on their own, equally great.