danryan.us

In which we learn the visual grammar of flow charts, black boxes, stepwise refinement, and modularity.
Visualizing action/process. Modularity. Dependency. Gannt charts too? Finish with classification flow charts and have this lead to BINARY and LOGIC?

How many and how likely? Another basic tool in our repertoire will be the ability to count things systematically. In which we make our way from Babylonian to Boolean and the way different ways of counting yield different ways of reasoning.

Process and flow is only half of our tactical tool kit. A jig is a type of custom-made tool or device that is used to control the location and/or motion of parts or other tools. A jig's purpose is to provide repeatability, accuracy, and interchangeability. The other half of our computational thinking arsenal is creative ways to structure information so that it is easier to operate on. In this workshop and the next we will meet a whole menagerie of useful "data structures." We will see that having your information in the right form is well over half the battle. Maybe big data? digital humanities? Names, nomenclature. Structures. Classes. Info hiding. Encapsulation.

An "iterative" approach to problem solution can mean two things. The first is problem solving based on gradual improvements to an initial guess at a solution. The second is problem solving by working over all the possible cases and combinations of inputs. In this module we will explore computational thinking in these two iterative modes. In which we encounter the affinity between geometric tile patterns, knitting, weaving, and music. For, While, Until. Encoding.

In which we learn how the skills of a power finder&replacer (and expert data cleaner) relate to everything else, all about regular expressions, finite state machines, lexical analyzers, and text parsers and maybe even data compression too.

We will make our way from graphs and networks up to constructing a neural network that can see in a spreadsheet (or maybe in an agent modeling platform like Netlogo or maybe we'll build a physical one in the the classroom).

Control engineering is about designing systems with desired behaviors within uncontrolled environments. In which we learn about feedback, bureaucracy, rules and regulations, and where the word "governor" comes from. Sensors. Feedback. Everyday machines. Internet of things. Systems. Introduce stopping problem?

What's the fuss about blockchain? Can I understand enough to become a crytpo-currency billionaire? (no) Can I understand it enough to be the smartest person at the dinner party? (yes). Algorithms, pointers, hash functions, cryptography

You can learn a lot by building something, we will "build" a robot. In class. And maybe have a guest lecturer too.

Let's review where we've been and where we can go from here.