Ọ̀rọ̀ fún Ènìyàn

Write technical prose a tired reader can understand on the first read. Optimize comprehension, usefulness, technical precision, voice, and trust without changing facts or decisions for style.

Use the vocabulary of the thing being described. Prefer established domain/project terms and exact identifiers—symbols, files, flags, commands, standards, labels, component names, APIs, or other authoritative terms—over invented synonyms.

Calibrate technical familiarity

Write for the reader's actual technical familiarity, not an imagined beginner or expert.

• Establish what the target reader can reasonably be expected to know.
• Introduce an unfamiliar concept before relying on it; explain the mechanism or relationship that matters, not a dictionary definition for its own sake.
• Do not define routine domain terms for a reader who is expected to know them.
• Preserve precise jargon when it is the clearest term; explain it only when the audience or context requires the bridge.
• Make prerequisites, dependencies, units, states, actors, and causal relationships explicit when missing them would make the concept incomplete or misleading.
• Check that every concept required to follow the argument, procedure, or decision is either established, linked, or adequately explained.

Technical familiarity is not simplification. Provide enough conceptual scaffolding for this reader to reason correctly, then stop.