So did you read it, /g/?

>>58713050
Seriously, can someone explain the benefits of this book over just learning through building small projects? Will this bridge some important theoretical concepts that I won't get from googling shit everytime I'm stuck? It's pretty long and I'm trying to justify committing time to it.

>>58713050
>Seriously, can someone explain the benefits of this book over just learning through building small projects? Will this bridge some important theoretical concepts that I won't get from googling shit everytime I'm stuck? It's pretty long and I'm trying to justify committing time to it.
KYS

>>58713238
Fuck off faggot, I'm trying to better myself. I'm in third year accounting and it's fucking busy.

File: 81gtKoapHFL.jpg (284KB, 1352x1701px) Image search: [Google]

284KB, 1352x1701px

No, I'm reading something more relevant.

>>58713219

SICP is not recommended as a beginners tutorial by anybody who is at all serious about teaching programming these days. It's simply too low-level.

In addition, the language used is a historical curiosity whose homoiconicity properties make it perfect for the book (data is code is data), but it's not the kind of feature you can ever expect to run into in real-world programming languages.

The only reason anybody would actually recommend this text for beginners is if they're secretly hoping you fail. Save it for when you're already experienced and feel like enlightenment.

>>58713050
>So did you read it, /g/?

I skimmed it a little bit recently. The order of topics makes it quite unsuitable for use in a standard computer science curriculum, and it's just pretty badly out of touch with the needs of most students.

For example, it starts right out in chapter 1 by jumping into recursion and recursive tree algorithms. A vast majority of computer science faculty know that you can't just walk into a class of first-year or second-year students and on the first week show the students how Ackermann's function works, and how to recursively calculate the nth Fibonacci number in log n time using a clever tree-walking approach. It's no surprise that the book is pretty much totally ignored by a vast majority of computer science departments.

It's on my TODO list. I know it's great for programming theory and lambda calculus stuff related to the Church-Turing thesis, but I need to get stuff done. Most of that stuff isn't helped by pure theory and the stuff that is helped is better off being helped by applied maths.

>>58713903
>TODO
When I see TODO in someone's program, does that mean they still have to do something, or is it a command?