Beyond the Basic Stuff with Python Best Practices for Writing Clean Code (Al Sweigart)（Z-Library）

【One-Line Pitch】 A practical bridge from "I can write Python" to "I can write Python other people want to maintain," covering tooling, style, debugging, profiling, and object-oriented design. Best for self-taught programmers and tutorial graduates who want professional habits without a computer science degree. 【Book Arc】 - **Opening (~0%–15%)**: Frames the novice-to-professional gap and sets expectations for who should read it and how to think about a programming journey. - **Early (~15%–30%)**: Establishes fundamentals of professional practice — reading tracebacks, asking good questions, and working confidently in the command line, filesystem, and environment variables. - **Middle (~30%–55%)**: The core best-practices toolkit: code formatting with Black, naming, code smells, Pythonic idioms, jargon, common gotchas, and effective functions. - **Late (~55%–75%)**: Documentation, type hints, Git-based project organization, and performance measurement with Big-O analysis, plus practice projects to apply the material. - **Ending (~75%–100%)**: Object-oriented Python — classes, inheritance, properties, and dunder methods — closing with a source-code walkthrough of two command-line games. 【Key Takeaways】 - **Professionalism starts with error literacy** (Early): reading tracebacks, searching error messages, and using linters to prevent bugs before they happen. - **The command line is a developer tool, not a relic** (Early): paths, processes, environment variables, and PATH management are prerequisites for running real tooling. - **Formatting is a solved problem — delegate it** (Middle): Black removes style debates; PEP 8 and spacing conventions matter mainly as shared expectations. - **Names carry most of your code's readability** (Middle): casing conventions, appropriate length, searchability, and avoiding built-in shadowing. - **Code smells are heuristics, not laws** (Middle): duplicate code, magic numbers, dead code, and nested comprehensions are warning signs — but the book explicitly debunks myths like "one return per function." - **Pythonic code means using the language's intended idioms** (Middle): enumerate over range, with over open/close, is for None, f-strings, defaultdict, and dictionaries instead of switch. - **Measure before optimizing** (Late): timeit and cProfile plus Big-O reasoning give you evidence rather than intuition about performance. - **OOP is an organizational tool, not a default** (Ending): classes, inheritance, properties, and dunder methods are introduced with the question of when they actually help. 【Reading Tips】 - Skim the environment/command-line chapter if you already live in a terminal; deep-read the code smells and Pythonic code chapters, which are the book's densest practical value. - Treat the two game walkthroughs (Tower of Hanoi, Four-in-a-Row) as exercises — implement before reading the breakdown to get real feedback on your habits. - Keep Black, a linter, and Git open alongside the book; the material is designed to be applied immediately, not just read. - The OOP section rewards readers who have already written messy procedural code — if you haven't, revisit it after a project. 【Coverage Limits】 The excerpts are dominated by front matter and the table of contents, so chapter-level detail beyond titles is thin; specifics of the practice projects and OOP chapters are not covered here.