|
|
|
|
|
by Err_Eek
2254 days ago
|
|
I've been going through SICP for a year and a half now on and off. At this point I don't feel I've been getting back all the effort I put in it. I think it's mostly recommended by people who didn't do all the exercises, or casually browsed through it and all they were left with was the fact that you can write a programming book without mentioning assignments until halfway through or that it's more easy to write a scheme interpreter in scheme than other languages. But the book is really dense, and you won't be left with much after trying to debug your hundreds line script meant to solve one problem. |
|
* the concept of assignment implying _time_ and messing with the substitution model.
* recursive functions that are iterative
* iterative structures that are recursive
* At the base of the base of the data abstraction in LISP is, well, nothing.
* Code as data, data as code, really strongly underlined.
* The whole LISP written in itself (as a sort of fixed point of a language that defines a language). That is really something.
* The idea of using a language to write a language that lets you express your problem.
That last one is probably obvious to most, but it was really novel to me (despite years of writing functions to compute answers).