Learning Resources
This module deliberately adds no new required books. The goal is synthesis, not new reading. The external sources below are examples of engineering voice, career thinking, and portfolio-quality writing -- read them to pattern-match, not to study.
Every URL below has been curation-verified.
Canonical Book Backbone
Use these canonical book routes when you need book-backed reinforcement for engineering judgment, communication, and evidence of craft:
- Software Engineering at Google for engineering voice, review culture, and evidence-backed technical work.
- Fundamentals of Software Architecture for explaining architecture decisions clearly in a case study or portfolio artifact.
- Clean Code for public evidence of craft, maintainability, and standards you can defend in portfolio review.
Source Stack
| Source | Role | How to use it in this module |
|---|---|---|
| Staff Engineer (Will Larson) | Revisit-only | Career trajectory and technical leadership framing; most useful for Clusters 4 and 5 |
| The Pragmatic Programmer (Thomas & Hunt) | Revisit-only | Engineering judgment, pragmatism, craft under pressure; useful across all clusters |
| staffeng.com/guides | Career / specialization reference | Archetype and path material; pattern for Cluster 4 rubric thinking |
| lethain.com | Voice + strategy reference | Long-running example of sustainable technical writing and career thinking |
| kalzumeus.com/standing-invitation | Portfolio posture reference | Example of direct, reader-first personal page |
| randsinrepose.com | Voice reference | Tight paragraphs, specific stories, almost never hedge |
| martinfowler.com/articles/patterns-of-distributed-systems | Portfolio-quality technical writing reference | Each pattern is a one-page case study with load-bearing diagrams |
| fs.blog/feynman-learning-technique | Feynman challenge reference | The 4-step original structure |
| capd.mit.edu STAR guide | Behavioral defense reference | Canonical STAR writeup |
| staffeng.com/guides/promo-packets | Evidence-packaging reference | Promo packet thinking maps closely to portfolio thinking |
Resource Map by Cluster
Cluster 1: The Capstone Case Study
| Need | Source | Why |
|---|---|---|
| Example of a tight problem/approach/outcome case study | martinfowler.com -- patterns of distributed systems | Each pattern page is structurally identical to a one-page case study |
| Instinct for what is load-bearing vs decorative | randsinrepose.com | Paragraphs are short and specific; almost no padding |
| Technical narrative with stakes and decisions visible | lethain.com | Long-form essays where tradeoffs are named, not hidden |
Cluster 2: Engineering Portfolio
| Need | Source | Why |
|---|---|---|
| Portfolio-as-signpost thinking | kalzumeus.com/standing-invitation | One page, direct, no decoration |
| Evidence-packaging pattern | staffeng.com/guides/promo-packets | Same thinking as a portfolio README at org scope |
| Craft signal benchmark | Your own capstone repo after Module 2 and Module 3 | Use the tests + CI + ADR output you already produced |
Cluster 3: Written Engineering Voice
| Need | Source | Why |
|---|---|---|
| Bio voice example | lethain.com | Short bio, evidence-first |
| Blog cadence example at steady rate | lethain.com | Two decades of consistent posting |
| Tight editing example | randsinrepose.com | Short paragraphs, almost no hedges |
| Direct reader-first posture | kalzumeus.com/standing-invitation | Example of voice that respects reader time |
Cluster 4: Specialization Decision
| Need | Source | Why |
|---|---|---|
| Track definitions and archetypes | staffeng.com/guides | Staff-plus archetypes and the path material |
| Career strategy essays | lethain.com | Seasons of career, strategy-first thinking |
| Staff Engineer (book, already in your library) | Chapter on picking where to invest | Revisit only the relevant chapters |
Cluster 5: Defending the Degree
| Need | Source | Why |
|---|---|---|
| Feynman method structure | fs.blog -- Feynman learning technique | The canonical 4-step framing |
| Behavioral interview structure | capd.mit.edu -- STAR method | Canonical STAR writeup with examples |
| Honest gap-list posture | lethain.com | Essays regularly include "what I didn't figure out yet" |
Use Rules
- Open one source for one specific concept gap; do not read entire sites.
- If a source adds no specific help on your current artifact, close it.
- Do not try to imitate voice from a single post; read three to five posts from a source to absorb the pattern.
- Prefer rereading Staff Engineer or The Pragmatic Programmer chapters over adding a new book in the final two weeks before graduation.