I'm late to this party, but I cannot credit The Little Schemer enough for resetting how I think about code and computation. I think back on lessons directly from this text nearly every single time I write code, I can't think of anything else as indispensable or thoroughly enlightening.
Nope, never before reading that and not once since, save a little Clojure a few years ago. It's a book about programming, and more specifically recursion, not necessarily Scheme. Scheme is a very minimal language and almost functions more as a formal notation for computation than anything else.
If you dig in, I highly recommend following along with Racket. It takes a little discipline, but don't let yourself read the "answer" column until you've taken a stab at implementations yourself. The code built up throughout the book is cumulative, by the end you'll want to have it all saved anyway.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm late to this party, but I cannot credit The Little Schemer enough for resetting how I think about code and computation. I think back on lessons directly from this text nearly every single time I write code, I can't think of anything else as indispensable or thoroughly enlightening.
That's a serious endorsement! Do you use Scheme (or some other form of Lisp) much?
I see The Little Schemer recommended a lot, but have never read it myself. Maybe now is the time ...
Nope, never before reading that and not once since, save a little Clojure a few years ago. It's a book about programming, and more specifically recursion, not necessarily Scheme. Scheme is a very minimal language and almost functions more as a formal notation for computation than anything else.
Awesome -- I'll definitely check it out. From the link you've provided, I can see that the writing style is up my street.
Thanks Ben!
If you dig in, I highly recommend following along with Racket. It takes a little discipline, but don't let yourself read the "answer" column until you've taken a stab at implementations yourself. The code built up throughout the book is cumulative, by the end you'll want to have it all saved anyway.