Writing a getting-started README for a new joiner — what is the most critical section?
README priority: "from zero to running locally in under 30 minutes" = good README. Sections: prerequisites → clone → configure → install dependencies → run → verify working.
The ADR template asks for 'Context and Problem Statement' — what should it contain?
ADR Context: future reader empathy. "In Q3 2023, we needed to choose a queue for async job processing. Constraints: existing Redis infrastructure, team unfamiliar with Kafka, expected volume < 10K/day..."
The onboarding docs have a 'Who to ask about what' section — why is this one of the most valuable resources?
"Who to ask": reduces invisible friction. Format: "For questions about X → ask @person or #channel". Empowers new joiners to seek help confidently.
Key vocab: "knowledge directory", "domain ownership map", "who-to-ask guide", "internal networking for new joiners".
4 / 5
The wiki was last updated 18 months ago — what is documentation drift and how does it affect onboarding?
Documentation drift: the longer since last update, the less trustworthy. Mitigation: documentation review on each substantial change, "last verified date" stamps, "known outdated" notices.
Writing a 'system overview' document for a new joiner — what level of detail is appropriate?
System overview: mental model first. Purpose → components → data flow → externals → "for more detail on X, see Y". Avoids detail overload before the mental model exists.
Key vocab: "system overview", "mental model document", "component map", "data flow", "jumping-off point to deeper docs".