My undergrad intro class used this. At the time I found it patronizing and silly and artificially limiting, having coded before (the design recipe, the different "levels" of scheme). But I saw some of the wisdom in the approach when I later tutored the class. People would try to rush into coding problems without doing real analysis of what the cases would be, and had a foggy notion of different parts of program havin…
Matthias Felleisen was my professor at Rice 2 decades ago and I can still hear his distinctive voice clearly in my head! I too was resistant at first having done some programming in high school, but I wish I could go back and tell myself to pay attention more. Now I know Matthias was both wise and passionate and that combination doesn’t show up in every CS class, so to this day I’m nostalgic for the way he introduced…
He came off as incredibly self-absorbed and at times, borderline hostile. A sibling poster quoted him as saying "don't put your ego in your code", but in the 4+ years I dealt with him, he was nothing but ego.
I don't doubt his intelligence and obviously he's a very accomplished individual, but I just don't see what everyone else saw in him.