Appendix E — Sources & further reading

This guide was researched in September 2026 against primary sources wherever one existed: Apple's documentation and release notes, project changelogs and docs, vendor pricing pages, and official release schedules. Community sources are listed where they add practical knowledge Apple doesn't publish. Prices, version numbers, and dates will drift; the point of this appendix is to give you the places to re-check rather than to trust the guide forever.

Working notes from the research pass live in the repo's research/ directory, dated, if you want to see what was checked and when.

Apple — primary documentation#

Developer tooling — official docs and changelogs#

Community references worth trusting#

• Mr. Macintosh (mrmacintosh.com) — meticulous tracking of every macOS build, installer download links, and update quirks; the first place to look when an update misbehaves.
• Howard Oakley, The Eclectic Light Company (eclecticlight.co) — deep, tested explanations of APFS, Time Machine, XProtect, the unified log, Apple silicon boot and security; Oakley's free utilities (Mints, Silent Knight, T2M2) are referenced in ch. 17 and ch. 22.
• Six Colors (sixcolors.com) and Daring Fireball (daringfireball.net) — informed commentary on Apple releases; the Six Colors FileVault/recovery-key write-up informed ch. 16.
• MacRumors (macrumors.com) and 9to5Mac (9to5mac.com) — release roundups and hardware buyer's guides (macrumors.com/roundup); good for "what changed in 26.x" summaries and the MacBook Neo/M5/M6 launch coverage.
• Michael Tsai's blog (mjtsai.com) — link roundups on macOS developer and security issues, with the discussion that follows each change (Gatekeeper's right-click removal, TCC changes, Rosetta's retirement).
• ERNW macOS hardening guide (github.com/ernw/hardening) and the macOS Security and Privacy Guide (github.com/drduh/macOS-Security-and-Privacy-Guide) — the two community hardening references ch. 16 draws from and deliberately trims for a daily-driver machine.
• Apple Stack Exchange (apple.stackexchange.com) and Ask Different — the searchable Q&A corpus for "why does macOS do X"; look for answers with man page citations.
• awesome-mac (github.com/jaywcjlove/awesome-mac) and Awesome macOS Command Line (github.com/herrbischoff/awesome-macos-command-line) — exhaustive app and defaults lists; the latter is the best index of defaults write keys.
• macos-defaults.com — visual, per-key documentation of defaults write settings with screenshots of the effect.
• Mathias Bynens's .macos (github.com/mathiasbynens/dotfiles) — the ancestor of every macOS defaults script, including Appendix A's; many keys are now obsolete, so treat it as history.
• launchd.info — the friendliest reference for launchd.plist keys.
• The Arch Wiki (wiki.archlinux.org) — for anything that's really about zsh, tmux, Git, SSH, or Neovim, it's the clearest documentation on the internet regardless of OS.
• Julia Evans's zines (wizardzines.com) — Git, the shell, DNS, and networking explained better than anywhere else; recommended reading in ch. 20.
• The Missing Semester of Your CS Education (missing.csail.mit.edu) — MIT's course on the shell, editors, Git, debugging, and metaprogramming; the natural companion to Part III of this guide.
• r/macapps, r/MacOS, r/macsysadmin, MacAdmins Slack (macadmins.org) — where practical fixes surface first, especially for enterprise/university-managed Macs.

Release calendars to bookmark#

Check these each September (macOS/Xcode/Java), October (Node LTS, Python), and when a course pins a version.

How this guide was researched#

Each chapter started from Apple's documentation for the feature in question, then the tool's own docs, then release notes for the current version, then community sources for practical behaviour Apple doesn't document (e.g., which defaults keys still work, how Gatekeeper's "Open Anyway" flow behaves in 26.x, real-world OrbStack vs Docker Desktop performance). Prices were taken from vendor pages in September 2026 in USD, with education pricing from Apple's US education store. Where a claim couldn't be verified against a primary source it was either dropped or marked with hedging language ("check current terms").

Things that were not done: no synthetic benchmarks were run; no affiliate links exist anywhere in the guide; no vendor was consulted or paid. Recommendations reflect the author's judgment of the best default for a CS student or working engineer in 2026, and are explicitly opinions where the guide says so.

Reporting errors#

If something is wrong, out of date, or missing: open an issue or pull request at github.com/grandfactor/macos-setup. Every page on the site has an Edit on GitHub link in its footer. Corrections that cite a primary source get merged fastest. The single-file GUIDE.md is generated from the per-chapter sources in guide/ by build.py; edit the chapter file, not the generated output.