An outline is a list of the points you plan to write about, arranged in the order you plan to cover them. Its job is to structure ideas before you spend time polishing sentences. section 4.3.1
Use an outline as a flexible working tool, not a ceremony:
- Choose any format that helps: a few bullets, a mind dump, or a formal hierarchy with multiple indentation levels. section 4.3.1
- Create the skeleton first, then hang details on it—or develop one section in depth before moving to the next. section 4.3.1
- Keep the outline in the file that will become the working draft, and add later ideas to the appropriate place. section 4.3.1
- Call it complete when it captures and organizes the main ideas; uneven detail across sections is acceptable. section 4.3.1
A technical outline
A Zig data migrator outline starts with the problem—migration costs and developer experience—then covers the proposed solution, Zig’s good and bad parts, the verdict, and a summary. The sequence gives the eventual article a story framework before prose exists. section 4.3.1
When the blank page is the problem, reverse-engineer the structure of an unrelated model article. Abstract its pattern rather than copying its technical ideas: problem statement, proposed solution, advantages, disadvantages, verdict, and summary can become a useful starting frame. section 4.3 section 4.3.3
For important or controversial work, share a decent outline with stakeholders and technical reviewers before fleshing it out. Early review exposes problems in focus and flow before sentence-level polishing creates expensive rework. section 6.4.1
For a book proposal, make the roadmap granular: include chapter titles, one-sentence descriptions, and the main sections. It helps estimate effort and scope, but may also become a contractual commitment. section 17.5.2
