Computer Science From Scratch Building Interpreters, Art, Emulators and ML in Python (David Kopec)（Z-Library）

【One-Line Pitch】 A hands-on tour of computer science fundamentals for experienced Python programmers, taught through seven progressively harder projects—from a tiny Brainfuck interpreter to an NES emulator, retro graphics, and a KNN classifier. Read it if you want to understand how the machinery beneath your code actually works, not just how to use it. 【Book Arc】 - **Opening (~0%–10%)**: Frames the book's premise—experienced Pythonistas filling conceptual gaps—and starts with the smallest possible language, a Brainfuck interpreter, to introduce the core tenets of any interpreter (cells, instruction pointer, bracket matching). - **Early (~10%–35%)**: Builds a full NanoBASIC interpreter, covering imperative vs. declarative paradigms, grammar design, tokenizer/parser/interpreter phases, AST node types, and the distinction between parser (syntax) and interpreter (semantic) errors. - **Middle (~35%–50%)**: Shifts to retro image processing—dithering a modern photo to 1-bit black-and-white for a classic Macintosh, plus the PackBits compression scheme and MacPaint/MacBinary file formats and raw-byte handling. - **Late (~50%–85%)**: The book's hardest project, an NES emulator built from the ground up, teaching computer architecture and low-level instruction execution (excerpts do not detail the intermediate graphics/art chapters beyond the dithering project). - **Ending (~85%–100%)**: Demystifies machine learning by implementing a readable K-Nearest Neighbors classifier, closing the arc from language internals to hardware to data-driven decision-making. 【Key Takeaways】 - **Interpreters decompose into tokenizer, parser, and evaluator** (Early): the Brainfuck and NanoBASIC projects show how grammar production rules map directly onto recursive-descent parser functions and AST nodes. - **Grammar is a blueprint, not the whole story** (Early): syntax rules specify structure but leave semantics—like variable initialization—to the interpreter, which is why error handling splits into parser vs. interpreter errors. - **Imperative vs. declarative is a design lens** (Early): NanoBASIC's imperative style (explicit how) contrasts with declarative "what" thinking, sharpening how you reason about language design. - **Raw bytes and file formats matter** (Middle): working with `bytes`, `bytearray`, and `array("B")`, plus PackBits and MacBinary, reveals the practical layer beneath high-level abstractions. - **Compression schemes have structural limits** (Middle): PackBits' run-length cap is sidestepped by encoding MacPaint one row at a time—a lesson in designing around constraints. - **Emulation teaches architecture from the inside** (Late): building an NES emulator forces engagement with how a microprocessor executes instructions at a fundamental level. - **ML can be demystified with readable code** (Ending): a simple KNN model shows classification decisions without heavy math or black-box libraries. - **Projects are lessons, not tools** (Opening): each chapter ends with real-world context, extensions, and exercises, reinforcing that the goal is understanding mechanisms. 【Reading Tips】 - **Deep-read the interpreter chapters (1–2)**: they establish vocabulary (tokens, AST, grammar) reused throughout; skimming here makes later chapters harder. - **Skim the "Code Meets Life" interludes** for motivation, but don't skip the exercises—they're where the concepts consolidate. - **Treat the NES emulator as the hard summit**: expect the steepest climb; lean on the provided source code and tests rather than trying to derive everything yourself. - **Run the tests**: the book ships unit/integration tests and continuous integration; using them turns reading into active verification. - **Bridge chapters by theme**: interpreters → emulators → graphics → ML form a fundamentals-to-application progression; read in order to preserve that arc. 【Coverage Limits】 The excerpts are thin on the intermediate graphics/art chapters and the NES emulator internals; this guide reflects the interpreter, dithering, and framing material most fully represented, and does not cover chapter-level detail the excerpts omit.