Pages tagged sicp:

Structure and Interpretation of Computer Programs
http://www-mitpress.mit.edu/sicp/full-text/book/book.html
Abstract Heresies: Not Lisp again....
http://funcall.blogspot.com/2009/03/not-lisp-again.html

“In this course we will be using the programming language Lisp...” Argh! Not that again! What is it with Lisp? Ok, maybe at Harvard they do that sort of thing, but this was MIT! Don't they hack computers here?
“If you already know how to program, you may be at a disadvantage because you will have to unlearn some bad habits.”
interesting account of someone's first taste of lisp
SICP in Clojure
http://sicpinclojure.com/
This site exists to make it easier to use Clojure rather than Scheme while working through SICP.
This site exists to make it easier to use Clojure rather than Scheme while working through SICP. The folks behind SICP were kind enough to release it under a Creative Commons Attribution-Noncommercial 3.0 Unported License, which will allow me to annotate the text and adapt its source code and exercises to fit the Clojure language.
Why MIT switched from Scheme to Python | Wisdom and Wonder
http://www.wisdomandwonder.com/link/2110/why-mit-switched-from-scheme-to-python
* Why MIT switched from Scheme to Python
Dan Weinreb’s blog » Blog Archive » Why Did M.I.T. Switch from Scheme to Python?
http://danweinreb.org/blog/why-did-mit-switch-from-scheme-to-python
Why Did M.I.T. Switch from Scheme to Python?
The freshman software engineering course (...) is now nearly thirty years old. Engineering has changed quite a lot in thirty years. Since 1995, Gerry and his co-author Prof. Hal Abelson have advocated changing the freshman curriculum radically, not basing it on SICP. In 1980, computer engineering was based on starting with clearly-defined things (primitives or small programs) and using them to build larger things that ended up being clearly-defined. Composition of these fragments was the name of the game. However, nowadays, a real engineer is given a big software library, with a 300-page manual that’s full of errors. He’s also given a robot, whose exact behavior is extremely hard to characterize (what happens when a wheel slips?).
"In 1980, computer engineering was based on starting with clearly-defined things (primitives or small programs) and using them to build larger things that ended up being clearly-defined. Composition of these fragments was the name of the game... Nowadays, a real engineer is given a big software library, with a 300-page manual that’s full of errors. He’s also given a robot, whose exact behavior is extremely hard to characterize (what happens when a wheel slips?). The engineer must learn to perform scientific experiments to find out how the software and hardware actually work, at least enough to accomplish the job at hand. We may not like it this way (”because we’re old fogies”), but that’s the way it is..."
Dan Weinreb’s blog » Blog Archive » Why Did M.I.T. Switch from Scheme to Python?
Some explanation of why MIT switched from Scheme to Python.