Book · 1984
Structure and Interpretation of Computer Programs
by Harold Abelson
Six chapters into Scheme, you're writing an interpreter for a language you invented an hour ago.
What does Reddit think of Structure and Interpretation of Computer Programs?
The most-upvoted excerpts here (↑2282, ↑1031, ↑446) aren't reviews of Structure and Interpretation of Computer Programs at all; they're the 'personal library' copypasta, a running r/programming joke about someone name-dropping SICP, On Lisp, and TAOCP to prove they're not a bad developer. That's the book functioning as a punchline about credentialism, not a verdict on the content. The actual recommendation sits over in r/learnprogramming, where the tone flips: one comment (↑252) calls it 'an absolute classic' that will make you write better code, full stop, no hedge. r/compsci and r/cscareerquestions mention it in passing rather than arguing about it. Nobody in the displayed excerpts disputes the book's difficulty or its reputation; the disagreement, such as it is, is about whether owning a copy means anything.
Community feedback & reader fit
Themes
- · Functions as internet shorthand for 'has read the canon,' independent of whether anyone finished it
- · The 'personal library' copypasta turning the title into a punchline about resume padding
- · A genuine, hedge-free recommendation once the conversation moves to r/learnprogramming
- · Teaching recursion and abstraction by building small interpreters, not by syntax drills
Common praise
- + The ↑252 r/learnprogramming comment calls it an absolute classic and says it'll make you write better code, no hedge attached.
- + Even the joke thread treats it as an entry any serious personal library needs, right alongside On Lisp and TAOCP.
Common criticism
- − The top-upvoted r/programming excerpts (↑2282, ↑1031) don't actually discuss the book; they're a copypasta mocking someone for reciting it as a credential.
- − The ↑446 reply treats that same book list as evidence the original poster was reciting flex-bait, not describing real reading.
Who it's for
Don't expect a straightforward tutorial: this is Scheme-flavored, code-first, and the r/learnprogramming crowd treats it as a rite of passage rather than a quick read. If you already know how to code and want the abstraction layer underneath the syntax, this delivers exactly what the ↑252 comment promises. Mentioning it on a résumé won't do what you think, per the copypasta everyone in r/programming apparently has memorized.
Mentions over time
Which Reddit comments matter for Structure and Interpretation of Computer Programs?
The most relevant excerpts across the subreddits where this book is mentioned — opinionated, argued takes first, then top-upvoted mentions. Click through to read the full thread.
“>I have a personal library that includes SICP, On Lisp, TAOCP, Expert C Programming, Effective C++, and textbooks on algorithms, distributed computing, security, graphics, and various branches of math. >I contribute to open-source projects in multiple languages such as C++, Perl, Python, and variou…
“>What distinguishes a bad developer? I have a personal library that includes SICP, On Lisp, TAOCP, Expert C Programming, Effective C++, and textbooks on algorithms, distributed computing, security, graphics, and various branches of math. While I may not have a university degree, I am a passionate pr…
“Here's the list, for anyone interested in just that: 1. The Pragmatic Programmer by David Thomas & Andrew Hunt (67% recommended) 2. Clean Code by Robert C. Martin (66% recommended) 3. Code Complete by Steve McConnell (42% recommended) 4. Refactoring by Martin Fowler (35% recommended) 5. Hea…
“I think the concept of 'programming' is so nebulous that we have a difficult time agreeing on this. There are great differences between coding a shell script to automate a repetitive action versus a business developer making a c# webapp versus someone working onna graphics api. All are programming…
“THANK YOU. I feel like I am going insane. “I have a personal library that includes SICP, On Lisp, TAOCP, Expert C Programming, Effective C++, and textbooks on algorithms, distributed computing, security, graphics, and various branches of math.” Here I thought he was going to list the libraries he …
“Structure and Interpretation of Computer Programs It's an absolute classic, and you will write better code after having read it.
“Probably, you should go for books that deal with pragmatic approaches to programming and code quality: + "Think Like A Programmer" by V. Anton Spraul + "The Pragmatic Programmer" by Andrew Hunt and David Thomas + "Structure and Interpretation of Computer Programs" (SICP) by Abelson, Sussman, Sussma…
“Yes. It's not all beautifully crafted code that you'd find in a tutorial or in SICP, if that's what you're picturing.
“Designing Data Intensive Applications by Martin Kleppmann Fluent Python if you’re a python programmer. I’m gonna just call Knuth / SICP / Clean Code / Design Patterns out as doorstops people never actually read.
“An absolute must watch. I view SICP as a watershed moment in my development, it makes it 1000 times easier to learn any language.
“SICP's (considered a CS essential) cover features a wizard holding a crystal ball and summoning the spectre of lambda. The author goes on to draw parallels between wizards conjuring spells and programmers writing programs. Yea. We're a wierd people.
“1- Read and do the exercises from the book Structure and Interpretation of Computer Programs. If you finish that book, you will build a better intuition for writing programs. 2- play with code, tinker around, experiment. Don't just follow projects. Again, you've got to build your intuition for wri…
“+1. Better structured, less fluff, and more concrete resources, than OSSU. Edit: I would also like to add the "gateway" material which teachyourselfcs mentions. SICP, CS:APP, and Designing Data-Intensive Applications. Maybe nand2tetris, at least the first 6 chapters for hardware.
“Just reading other peoples code and couple good books. SICP is a highlight. Code should be written in a way that you can tell **what** a function does by just reading the function signature, you should be able to understand **how** it does it from the function implementation and comments should exp…
“Awesome! If you want some more practice on recursion to help fully wrap your head around it (it's one of those things where there are multiple OHHHHHH moments) I would highly suggest you read a little of Structure and Interpretation of Computer Programs. …
Convinced? Pick up Structure and Interpretation of Computer Programs
Readers also mention
Books that share discussion threads with Structure and Interpretation of Computer Programs — counted from the comments, not curated.
Guides featuring Structure and Interpretation of Computer Programs
Ranked best-of lists and editorial guides where this book's tracked mentions place it.
Structure and Interpretation of Computer Programs — frequently asked
Is Structure and Interpretation of Computer Programs worth reading in 2026?+
Yes, per the one comment in this data set actually arguing for it rather than joking about it. The ↑252 r/learnprogramming excerpt calls it 'an absolute classic' and says directly that you'll write better code after finishing it. Nothing displayed here contradicts that; the pushback that exists is aimed at how people cite it, not at the content.
Why does Reddit joke about Structure and Interpretation of Computer Programs?+
Because of a specific copypasta. The top three r/programming excerpts (↑2282, ↑1031, ↑446) are a bit about someone listing SICP alongside On Lisp and TAOCP to prove they're not a bad developer, mocked as credential-flexing rather than evidence of actual reading.
Is Structure and Interpretation of Computer Programs a beginner book?+
Not obviously. It gets posted to r/learnprogramming as a classic (↑252), but the same title also appears in a copypasta where it's part of an advanced programmer's flex library alongside TAOCP and Effective C++. Read both signals together and it looks aimed at programmers past their first year, not day one.
Do people actually finish Structure and Interpretation of Computer Programs, or just cite it?+
The data leans toward citing. The dominant excerpts here are a copypasta built entirely around someone listing the book as proof of expertise, and the ↑446 reply calls that exact move out as suspicious. The one unambiguous endorsement (↑252) comes from someone actually working through it, not name-dropping it.