When I take a class, I take notes in that class. I write down interesting things; I try to replicate the structure of the lecture; I add my own thoughts when they come up (in boldface, since I type). I rarely ever look over my notes again. They simply allow me to commit to memory the content of a lecture by the act of typing them down.
I’ve been trying to learn scheme, and more importantly larger program design principles. I have not taken any notes. Why? Because there is no “big person” some 10-30 feet in front of me telling me all about these things. That situation does not sufficiently change my need to write down what I learn so I remember it. Duh.
I’m taking notes now. Here.
Part 4: Conditional Expressions and Functions
boolean values = truth values = true or false responses to conditions
think of x < y , x > y , x = y . these can be combined into compound claims
Scheme has:
true
false
= , < , > , <= , >=
[not a number!]
(< 4 5)
true
[for
(and (= 5 5) (<5 6))
(and true true)
trueand, all conditions must be true for the whole expression to be evaluated as true. or and not follow like you'd think]
I’m getting used to (define). Yay!
Intervals (between 6 and 7) and combinations/unions of intervals (between 6 and 7 or over 10)
I need to remember that contracts and purpose statements clean up my thinking. Very useful to write.
not reverses the > and < signs (when writing on a number line)
(more to follow)
0 Responses to “the process of learning”