# FOCUS: Architecture for People Who Ship Software — Chapter 01: About the Author
- **Date Created**: 2026-10-01
- **Status**: In Progress — preview prepared; awaiting reading
- **Reading span**: PDF pages 13–20

---

## 1. Pre-Reading Briefing
- **Core Question**: How can software stay easy to change as it grows, without making a small change hard to locate or risky to make?
- **Key Points to Watch For**:
  - What the author's “F12 test” measures when navigating an unfamiliar codebase.
  - How the two project stories show different ways the cost of change can rise.
  - Which measure the author uses to judge an architecture, beyond its apparent simplicity.
  - How the author moves from those experiences to the proposed four-piece structure; what evidence would make that proposal convincing?
  - Why locating a rule may matter more when code can be generated quickly.
- **Context & Thread from Prior Chapters**: This is the first chapter. In *Context Engineering*, the reader is currently examining the claim that information available to a model shapes its output. Watch for whether code organization affects what a human or model can find; keep the question open while reading.

---

## 2. Reading Review & Reflections
- **Status**: Awaiting reader completion and active-recall responses.

---

## 3. Chapter Synthesis
- **Status**: Pending post-reading discussion.