Appendix B — Author’s reading list
Books from the author’s Goodreads library (export of 2026-09-12, 221 titles) that bear on this book, trimmed to 69. Fiction, finance, health, parenting, and language-specific programming books are left out. Ratings are the author’s Goodreads stars (1 to 5; blank means unrated). “Read” dates are as recorded on Goodreads; older reads carry no date.
How to use this list
- This is a shelf, not a ledger. A title here says the author has read it and finds it relevant; it says nothing about whether a particular claim in it holds. Every claim, number, or quotation taken from one of these books still gets a row in
claims.mdand followsskills/researching-a-claim: open the book, find the passage, record the setting and the source’s own caveats. - No quotation enters the manuscript from this list. The “Look for” column names topics and well-known ideas to find in the book; it is not a quotation and must not be paraphrased into one.
references.bibgets an entry only once a row inclaims.mdissupportedorpartial. ISBNs are given here so the entry can be built without a second lookup.- The “Chapters” column maps to
chapters/03-book-outline.qmd. - Books already cited: Meadows (Meadows 2008) and Brooks (Brooks 1986) (the anniversary edition of The Mythical Man-Month reprints “No Silver Bullet”).
Part I: the human constraint (chapters 1 and 2)
Cognition, attention, expertise, flow, and calibrated confidence.
| Title | Author(s) | Year | Rating | Read | ISBN-13 | Chapters | Look for | Caution |
|---|---|---|---|---|---|---|---|---|
| The Programmer’s Brain | Felienne Hermans | 2021 | 4 | 2021 | 9781617298677 | 2, 3, 4 | The one book on the shelf about program comprehension specifically: working memory, long-term memory, and short-term memory in reading code; chunking and beacons; cognitive load types applied to code; naming and its effect on comprehension; onboarding. Cites the primary studies the ledger needs (C-014, C-015) | Popular synthesis; go to the studies it cites for numbers |
| Pragmatic Thinking and Learning: Refactor Your Wetware | Andy Hunt | 2008 | 5 | 9781937785239 | 2, 3 | Dreyfus model of skill acquisition (novice to expert), why experts and novices need different maps; attention, context switching cost; externalizing thinking | Dreyfus model is a framework, not an empirical result; Hunt’s own caveats apply | |
| Flow: The Psychology of Optimal Experience | Mihály Csíkszentmihályi | 1990 | 5 | 2 | The primary source for flow: clear goals, immediate feedback, challenge matched to skill, sense of control, loss of self-consciousness. Chapter 2 leans on this | Based on experience-sampling studies of the 1970s and 80s, not on software work; quote the conditions, not the productivity claims | ||
| Thinking, Fast and Slow | Daniel Kahneman | 2011 | 3 | 2023 | 9780374275631 | 2, 7 | System 1 and System 2; cognitive ease and the fluency illusion (the feeling of understanding versus its grounds); “what you see is all there is”; overconfidence | Several chapters rest on priming studies that failed replication; Kahneman later conceded this. Cite only the parts with a robust base and say so |
| Deep Work | Cal Newport | 2016 | 4 | 2022 | 9781455586691 | 2 | Attention residue (Newport draws on Sophie Leroy’s work), cost of switching, the argument that concentration is a scarce skill | Self-help register; go to Leroy 2009 for attention residue rather than Newport |
| Digital Minimalism | Cal Newport | 2019 | 4 | 2022 | 2 | Attention as a finite resource; solitude deprivation | Weaker than Deep Work for this book; secondary | |
| Peopleware: Productive Projects and Teams | Tom DeMarco, Timothy Lister | 1987 | 5 | 9780932633439 | 2, 6 | Flow and the cost of interruption for knowledge workers; the “E-factor” (uninterrupted hours over body-present hours); office environment; teamicide. Rare early attempt to measure developer environment effects (Coding War Games) | 1980s data, self-selected participants; the Coding War Games numbers need the original’s stated method | |
| Drive: The Surprising Truth About What Motivates Us | Daniel H. Pink | 2009 | 5 | 9781594488849 | 2, 7 | Autonomy, mastery, purpose as intrinsic motivators; the agency lens in one popular frame | Pink summarizes Deci and Ryan (self-determination theory); cite them for the mechanism | |
| The Great Mental Models: General Thinking Concepts | Shane Parrish, Rhiannon Beaubien | 2018 | 5 | 2022 | 3 | “The map is not the territory”, circle of competence, first principles, thought experiment, second-order thinking; a vocabulary for chapter 3’s “mental model” | Compilation, not primary; useful for framing, not evidence | |
| Superforecasting: The Art and Science of Prediction | Philip E. Tetlock, Dan Gardner | 2015 | 4 | 2023 | 9780804136693 | 2, 3, 5 | Calibration versus confidence; Brier scores; the habit of making a prediction and checking it; updating in small steps. Directly relevant to “predict before you check” in chapter 3 | Forecasting geopolitics, not code; transfer is by analogy |
| The Scout Mindset | Julia Galef | 2021 | 3 | 2022 | 9780735217553 | 2, 3, 7 | Scout versus soldier mindset; calibrated confidence; distinguishing feeling certain from having grounds | Popular; anecdote-heavy |
| Think Again: The Power of Knowing What You Don’t Know | Adam Grant | 2021 | 4 | 2022 | 9781984878106 | 3, 7 | Rethinking and unlearning; the preacher, prosecutor, politician, scientist modes; confident humility | Popular synthesis; check any study he cites |
| The Biggest Bluff | Maria Konnikova | 2020 | 5 | 2023 | 9780525522621 | 2, 5, 7 | Decision-making under uncertainty in poker: separating decision quality from outcome, variance, tilt, attention. A vivid frame for “a passing test is not proof” | Memoir; use for framing and metaphor, never as evidence |
| Factfulness | Hans Rosling, Ola Rosling, Anna Rosling Rönnlund | 2018 | 5 | 2021 | 9781473637467 | 3, 8 | The ten instincts that distort a worldview (gap, negativity, straight line, fear, size, generalization, destiny, single perspective, blame, urgency); the discipline of checking a belief against data | About global development data; the instincts transfer as a checklist, not as findings about engineers |
| The 5 Elements of Effective Thinking | Edward B. Burger, Michael Starbird | 2012 | to-read | 9780691156668 | 3 | Understanding deeply, making mistakes, raising questions, following the flow of ideas | Unread | |
| Four Thousand Weeks | Oliver Burkeman | 2021 | to-read | 9780374159122 | 2 | Finitude of attention; the trap of efficiency | Unread; marginal |
Part II: design for bounded understanding (chapters 3 and 4)
Mental models, modularity, local reasoning, abstraction, and the historical anchors.
| Title | Author(s) | Year | Rating | Read | ISBN-13 | Chapters | Look for | Caution |
|---|---|---|---|---|---|---|---|---|
| The Mythical Man-Month (anniversary edition) | Frederick P. Brooks Jr. | 1975 / 1995 | 4 | 9780201835953 | 1, 6 | Already cited for “No Silver Bullet” (C-012). Also: Brooks’s Law and communication overhead (chapter 6); conceptual integrity and the surgical team; “plan to throw one away”; “No Silver Bullet Refired” (ch. 17) for Brooks’s answer to critics, noted as unopened in C-012 | 1960s and 70s projects; quote with the original’s scope | |
| Domain-Driven Design: Tackling Complexity in the Heart of Software | Eric Evans | 2003 | 5 | 9780321125217 | 3, 4, 6 | Ubiquitous language (a shared model between people); bounded contexts (a boundary that contains reasoning, not just deployment); context maps; aggregates as consistency boundaries; anticorruption layer; the “big ball of mud” as a named context. The subtitle alone is a chapter 1 epigraph candidate | Experience-based; no empirical claims to lean on, so cite it for concepts and definitions | |
| Working Effectively with Legacy Code | Michael C. Feathers | 2004 | 5 | 9780131177055 | 3, 5, 6 | The definition “legacy code is code without tests”; seams; characterization tests (write the test that records what the code does before changing it); the “edit and pray” versus “cover and modify” contrast; sprouting and wrapping as additive fixes | The definition is Feathers’s own and contested; present it as his | |
| Refactoring: Improving the Design of Existing Code | Martin Fowler, with Kent Beck et al. | 1999 | 5 | 9780201485677 | 4, 6 | The definition of refactoring (behavior-preserving change); code smells as a vocabulary (Shotgun Surgery, Feature Envy, Divergent Change, Speculative Generality); small steps with tests between them. The author’s blog already uses “Avoid Shotgun Surgery” | 1999 edition on the shelf; the 2018 second edition renames some refactorings | |
| Patterns of Enterprise Application Architecture | Martin Fowler | 2002 | 4 | 9780321127426 | 4 | Layering; the trade-off table for domain logic patterns; “the first law of distributed object design: don’t distribute your objects” (chapter 4’s multi-service case) | Java and .NET of 2002; the distribution argument still holds, the patterns are dated | |
| OSGi and Equinox: Creating Highly Modular Java Systems | Jeff McAffer, Paul VanderLei, Simon Archer | 2009 | 4 | 9780321585714 | 4 | Modularity made explicit: bundles, exported and imported packages, versioned dependencies, what an enforced boundary costs. The author worked in this ecosystem, so first-person stories may exist in STORIES.md |
Platform-specific; use for a concrete instance of enforced information hiding, not as a general result | |
| Java Concurrency in Practice | Brian Goetz, Tim Peierls, Joshua Bloch, et al. | 2005 | 5 | 9780321349606 | 1, 4 | Why a short concurrent routine is hard to reason about: visibility, atomicity, ordering, the Java memory model; invariants and state ownership; “thread confinement” and immutability as ways to make local reasoning valid. The outline’s chapter 1 example (“a short concurrent routine”) can be grounded here | Java-specific; the reasoning problem is general | |
| Effective Java | Joshua Bloch | 2001 / 2017 | 5 | 9780134685991 | 4 | Minimize accessibility, favor immutability, design and document for inheritance or prohibit it; items that make a class’s contract explicit | Language-specific advice; cite for the principle, not the item number | |
| Elegant Objects | Yegor Bugayenko | 2016 | 3 | 9781519166913 | 4 | Opinionated case for immutability and small objects; useful as a foil | Contrarian; do not present its rules as consensus | |
| Clean Code | Robert C. Martin | 2007 | 4 | 9780132350884 | 3, 4 | Naming, small functions, “code is read far more than it is written” (the ratio he gives is unsourced) | The 10:1 read/write ratio is folklore; do not cite it as a measurement | |
| The Clean Coder | Robert C. Martin | 2011 | 3 | 9780137081073 | 7 | Professional responsibility, saying no, estimates as distributions | Secondary | |
| The Pragmatic Programmer: From Journeyman to Master | Andy Hunt, Dave Thomas | 1999 | 5 | 2021 | 9780201616224 | 3, 4, 5 | DRY; orthogonality (change one thing without affecting others, the cleanest early statement of local reasoning as a design goal); tracer bullets; “programming by coincidence” versus deliberate programming; broken windows; rubber-duck debugging | 1999 edition on the shelf; the 2019 20th-anniversary edition rewrote much of it, so check page references against the edition cited |
| 97 Things Every Programmer Should Know | Kevlin Henney (ed.) | 2010 | 5 | 9780596809485 | various | Two-page essays by named practitioners; scan for essays on comprehension, simplicity, and feedback that can be cited to their own authors | Anthology; cite the essay author, not the editor | |
| 97 Things Every Java Programmer Should Know | Kevlin Henney, Trisha Gee (eds.) | 2020 | 5 | 2020 | 9781491952696 | various | Same format; Java-flavored | Anthology |
| The Thoughtworks Anthology | Roy Singham et al. | 2008 | 5 | 9781934356142 | 4, 5 | Essays including “Object Calisthenics” (Jeff Bay) and pieces on build and deployment; cite by essay | Anthology; dated |
Part III: keep understanding alive (chapters 5 and 6)
Feedback, testing, delivery, production, accumulation, teams, and flow of work.
| Title | Author(s) | Year | Rating | Read | ISBN-13 | Chapters | Look for | Caution |
|---|---|---|---|---|---|---|---|---|
| Growing Object-Oriented Software, Guided by Tests | Steve Freeman, Nat Pryce | 2009 | 5 | 9780321503626 | 3, 5 | Tests as executable specifications; the walking skeleton; “listening to the tests” (a hard-to-write test is design feedback); the outer and inner feedback loops | Their own project experience; cite for the practice and its rationale | |
| Continuous Delivery | Jez Humble, David Farley | 2010 | 4 | 9780321601919 | 5, 7 | The deployment pipeline as staged feedback at increasing cost and fidelity; “if it hurts, do it more often”; small batches; the value of a fast commit stage. Chapter 5’s “feedback at different distances” has a ready-made structure here | Experience-based; the Accelerate metrics came later (Forsgren, Humble, Kim 2018, not on the shelf) | |
| Release It! Design and Deploy Production-Ready Software | Michael T. Nygard | 2007 | 4 | 9780978739218 | 4, 5, 6 | Stability patterns and antipatterns: circuit breaker, bulkhead, timeouts, cascading failures, integration points as the number one killer; the retry-and-duplicate-side-effects problem that chapter 4’s retry wrapper example needs | First edition (2007) on the shelf; the 2018 second edition revised much. Case studies are anonymized and narrated | |
| Site Reliability Engineering: How Google Runs Production Systems | Betsy Beyer, Chris Jones, Jennifer Petoff, Niall Murphy (eds.) | 2016 | 3 | 9781491929124 | 5, 8 | Error budgets; SLOs; observability and the four golden signals; blameless postmortems; toil. The “grounds for confidence” framing in chapter 5 can use SLOs as a measured example | Google-specific scale; the authors say so | |
| How Google Tests Software | James A. Whittaker, Jason Arbon, Jeff Carollo | 2012 | 5 | 9780321803023 | 5 | Small, medium, large tests; test roles; the argument that testing is everyone’s job | 2012 Google; some of it Google has since abandoned | |
| Software Engineering at Google | Titus Winters, Tom Manshreck, Hyrum Wright (eds.) | 2020 | reading | 9781492082798 | 4, 5, 6, 7 | “Software engineering is programming integrated over time”; Hyrum’s Law (every observable behavior will be depended on: the epistemic trap of chapter 1 and the leak of chapter 4); code review as knowledge transfer; the test pyramid and flaky tests; large-scale changes; deprecation | Currently reading; Google-specific | |
| The Phoenix Project | Gene Kim, Kevin Behr, George Spafford | 2013 | 3 | 9780988262591 | 2, 6 | The Three Ways (flow, feedback, continual learning); the “Brent” problem (one expert every change waits on; chapter 6’s example); WIP and unplanned work | A novel. Cite the ideas to The DevOps Handbook or to Goldratt for the theory of constraints; do not quote fictional events as cases | |
| Making Work Visible: Exposing Time Theft to Optimize Work & Flow | Dominica DeGrandis | 2017 | 3 | 2022 | 9781942788188 | 2, 6 | The five thieves of time: too much WIP, unknown dependencies, unplanned work, conflicting priorities, neglected work; queues and waiting as the hidden cost of platform boundaries | Kanban practitioner’s book; little empirical support |
| Adrenaline Junkies and Template Zombies: Understanding Patterns of Project Behavior | Tom DeMarco, Peter Hruschka, Tim Lister, et al. | 2008 | 5 | 9780932633675 | 2, 6 | 86 named patterns of project behavior (e.g. “Dead Fish”, “Film Critics”, “Template Zombies”, “Rattle Yer Dags”); a catalogue of defensive and organizational behavior chapter 2 and 9 can borrow labels from | Named patterns from consulting experience; no data | |
| Staff Engineer: Leadership Beyond the Management Track | Will Larson | 2021 | 5 | 2021 | 6, 7 | Staff archetypes; “writing engineering strategy”; how ownership and technical direction get distributed without a manager | Interview-based; cite interviewees by name where quoted | |
| The Staff Engineer’s Path | Tanya Reilly | 2022 | 5 | 2023 | 9781098118730 | 6, 7, 8 | “The big picture”; taking on the projects nobody owns; the “glue work” argument; deciding what to stop doing (the director’s question in STYLE.md) |
Practitioner advice |
| The Five Dysfunctions of a Team | Patrick Lencioni | 2002 | 4 | 9780787960759 | 6 | Trust, conflict, commitment, accountability, results as a stack | A fable with a model; no evidence base | |
| The Culture Map | Erin Meyer | 2014 | 3 | 2022 | 6 | Low- versus high-context communication; how the same handoff reads differently across cultures | Country-level generalizations; use lightly | |
| Creativity, Inc. | Ed Catmull, Amy Wallace | 2014 | 4 | 2022 | 9780812993011 | 6, 8 | The Braintrust (candid review without authority); “the hidden” (what leaders cannot see); postmortems; “fail early, fail fast” | Memoir of Pixar |
| Extreme Ownership | Jocko Willink, Leif Babin | 2015 | 3 | 2023 | 9781250067050 | 6, 7 | Ownership as a stance; “decentralized command” with clear intent (bounded delegation) | Military anecdotes; a metaphor at most |
| Rebels at Work | Lois Kelly, Carmen Medina | 2014 | 3 | 2022 | 9781491903957 | 8 | Leading change without authority | Secondary |
| Hack Your Bureaucracy | Marina Nitze, Nick Sinai | 2022 | 3 | 2023 | 9780306827754 | 6, 8 | Tactics for changing large organizations from inside; “find the real process” | Secondary |
| Rework | Jason Fried, David Heinemeier Hansson | 2010 | 5 | 9780307463746 | 2, 6 | Short essays: “underdo the competition”, interruption as the enemy, “planning is guessing” | Opinion; quotable aphorisms, no evidence | |
| Build: An Unorthodox Guide to Making Things Worth Making | Tony Fadell | 2022 | 5 | 2023 | 9781787634114 | 6, 7 | Product decision-making; “opinion-driven” versus “data-driven” decisions; how to delegate without abdicating | Memoir and advice |
| Inspired: How to Create Tech Products Customers Love | Marty Cagan | 2008 / 2017 | 4 | 2022 | 9781119387503 | 6 | Product discovery; empowered teams | Secondary |
| Just for Fun | Linus Torvalds, David Diamond | 2001 | 2017 | 9780066620732 | 6 | The origin of Linux; distributed ownership in open source | Memoir; secondary | |
| An Astronaut’s Guide to Life on Earth | Chris Hadfield | 2013 | 5 | 2022 | 9780316253017 | 5, 7 | “Sweat the small stuff”; simulations and rehearsing failure (“what’s the next thing that could kill me”); the case for practicing recovery before it is needed, which chapter 7’s recovery exercise can borrow | Memoir; metaphor only |
Part IV: AI, automation, and evidence (chapters 7 and 8)
Automation bias, correlated errors, statistics, and what machine systems do to understanding.
| Title | Author(s) | Year | Rating | Read | ISBN-13 | Chapters | Look for | Caution |
|---|---|---|---|---|---|---|---|---|
| Hello World: Being Human in the Age of Algorithms | Hannah Fry | 2018 | 4 | 2022 | 9780393357363 | 7 | Automation bias and over-trust in algorithmic output (the drivers who followed satnav into rivers); when to keep a human in the loop; the argument that algorithms should be questioned like any other authority | Popular; go to the automation-bias literature she cites (Parasuraman, Skitka) for the mechanism |
| The Wisdom of Crowds | James Surowiecki | 2004 | 3 | 2022 | 9780385721707 | 7 | The conditions for a crowd to beat its members: diversity, independence, decentralization, aggregation. The independence condition is the frame for chapter 7’s “generated tests that repeat the implementation’s assumptions”: correlated errors do not cancel | Popular; the conditions are from Galton and from decision-theory work he summarizes |
| Designing Machine Learning Systems | Chip Huyen | 2022 | 4 | 2023 | 9781098107963 | 5, 7 | Data distribution shift, feedback loops between model and data, monitoring in production; the difference between an evaluation passing and a system working | ML-engineering practice; useful for the feedback chapter’s “distance from the decision” |
| GPT-3: Building Innovative NLP Products using LLMs | Sandra Kublik, Shubham Saboo | 2022 | 3 | 2022 | 9781098113629 | 7 | Early practitioner view of LLM products; useful only as a dated snapshot of what people expected in 2022 | Aged; do not cite for current capability |
| Naked Statistics | Charles Wheelan | 2012 | 4 | 2022 | 9780393347777 | 5, 8 | Correlation and causation, selection bias, regression to the mean, what a measurement can and cannot support; chapter 8’s “provisional signals, not a score” | Popular introduction |
| The Art of Statistics | David Spiegelhalter | 2019 | to-read | 9781541618510 | 5, 8 | Same territory with more rigor; the PPDAC cycle (problem, plan, data, analysis, conclusion) maps onto chapter 3’s exploration loop | Unread | |
| Numbers Don’t Lie | Vaclav Smil | 2020 | 3 | 2021 | 9780241454411 | 8 | Discipline of stating a number with its unit, source, and scope | Secondary |
| Invisible Women: Data Bias in a World Designed for Men | Caroline Criado Pérez | 2019 | 4 | 2022 | 9781419729072 | 7 | What a system built on unrepresentative data gets wrong by default; a case for asking who the data covers before trusting a generated result | Not about software engineering; use for one example at most |
| Die kleinste gemeinsame Wirklichkeit | Mai Thi Nguyen-Kim | 2021 | 5 | 2022 | 9783426278222 | 3, 5, 7 | How to weigh evidence quality when experts disagree; distinguishing what is known, plausible, and contested (the ledger’s own status words). German; translate any quotation and give the original | German-language; popular science |
| Made to Stick | Chip Heath, Dan Heath | 2006 | 3 | 2022 | 9781400064281 | 3, 4 | The “curse of knowledge” (experts cannot imagine not knowing); simple, unexpected, concrete, credible, emotional, stories. Relevant to why experts and newcomers need different maps, and to naming techniques | Popular; the curse of knowledge traces to Camerer, Loewenstein, Weber 1989 |
| Atomic Habits | James Clear | 2018 | 3 | 2022 | 6 | Small changes compounding; environment design over willpower (the “change the environment, not the person” stance of chapter 2) | Self-help; evidence thin |
Complex systems and systems thinking (chapter 1 and throughout)
| Title | Author(s) | Year | Rating | Read | ISBN-13 | Chapters | Look for | Caution |
|---|---|---|---|---|---|---|---|---|
| Thinking in Systems: A Primer | Donella H. Meadows | 2008 | 5 | 9781603580557 | 1, 6 | Already cited (C-001, C-009, C-011). Still to mine: “leverage points”; “the bounded rationality of actors in a system”; system traps (policy resistance, shifting the burden, drift to low performance, rule beating); “shifting the burden” is the additive-fix loop of chapter 6 in her words | Cite only where she says it; see C-011 for what she does not say | |
| Limits to Growth: The 30-Year Update | Donella Meadows, Jørgen Randers, Dennis Meadows | 1972 / 2004 | to-read | 9781931498586 | 1 | The World3 model; overshoot and delayed feedback; the original case study behind Thinking in Systems | Unread; contested reception | |
| Understanding Complexity | Scott E. Page | 2009 | 4 | 2022 | 1 | A course (The Great Courses, 12 lectures), not a book: definitions of complex versus complicated, emergence, tipping points, path dependence, diversity and robustness; the candidate source for C-010 and C-011 where Meadows falls short | Cite as an audio/video course with lecture number; Page’s Diversity and Complexity (2010) is the book form, not on the shelf | |
| Chaos: Making a New Science | James Gleick | 1987 | 2 | 2023 | 9780140092509 | 1 | Sensitivity to initial conditions (Lorenz), nonlinearity, why deterministic systems can be unpredictable; the history of the field | Author rated it 2; use for one historical anchor at most |
| Engineering in Plain Sight | Grady Hillhouse | 2022 | 4 | 2023 | 9781718502321 | 1, 4 | The constructed environment as layered, mostly invisible infrastructure; a source of physical metaphors for abstraction and hidden dependencies, with their limits visible | Metaphor source only |
Left out, and why
- Fiction (Crouch, Rowling, Kling, Dusse, Thiemeyer, Weir, Orwell, and the rest): no claims to make. QualityLand (Kling) and 1984 could supply an epigraph on automation, which is a
for:authorchoice. - Personal finance (Kommer, Kiyosaki, Housel, Hagstrom, Muto): off topic.
- Health and parenting (Walker, Fung, Taubes, Inchauspé, Juul, Saalfrank, Tawwab, Shojai, Kwik): off topic; Why We Sleep is also contested.
- Biography and memoir without an engineering-practice angle (Isaacson’s Jobs, Einstein, da Vinci, Doudna; Vance; Iger; Nadella; Obama; Smith; Perry; Snowden; Kay; Chan; Savage; Bilton; Kushner; Kurbjuweit; Olson): a story from one might serve as an example, but none carries a claim the book needs.
- Language and tool manuals (TypeScript, Node.js, React Native, Visual Studio extensibility, Python, data structures, interpreters and compilers in Go, JUnit, NoSQL, genetic algorithms, applied NLP): no claims about comprehension or complexity.
- Popular science outside the thesis (Bryson, Lesch, Randall, Hawking, Czerski, Munroe, Parker, Humphries, Shaw, Reichholf, Fowler’s Seeds on Ice, Schätzing, Mann, Gates, Holler, Herrmann, Eddo-Lodge): read for pleasure, not for this argument. Nguyen-Kim is kept, above.
- Productivity self-help (Covey, Ferriss, Tracy, Manson): the book’s register avoids them. Newport’s Digital Minimalism is kept as secondary.
- Negotiation (Voss, currently reading): no obvious chapter; revisit if chapter 6’s material on knowledge concentration needs it.
Brooks, Frederick P., Jr. 1986. “No Silver Bullet: Essence and Accident in Software Engineering.” In Proceedings of the IFIP Tenth World Computing Conference, edited by H.-J. Kugler, 1069–76. Amsterdam: Elsevier Science.
Meadows, Donella H. 2008. Thinking in Systems: A Primer. Edited by Diana Wright. White River Junction, VT: Chelsea Green Publishing.