Gergely Orosz outlines why written communication has become a prerequisite for career progression beyond senior engineering levels. While immediate code output impacts individual tasks, written documents—such as design proposals, planning documents, postmortems, and runbooks—create durable records that influence broader organisations.
The Writing and Editing Workflow
A polished piece requires distinct stages: drafting content, rigorous editing, and collecting peer feedback. Orosz notes that concise writing requires significant effort, pointing to Amazon's strict six-page document limit as an example of forcing teams to eliminate unneeded filler.
Practical Editing Approaches
The article details several practical tactics for day-to-day work:
- Formatting for scanning: Breaking walls of text into short paragraphs, using numbered or bulleted lists, and selectively bolding key takeaways.
- Sentence structure: Trimming unnecessary introductory disclaimers and keeping sentences short to avoid confusion.
- Visual context: Incorporating screenshots and architectural diagrams, similar to Cloudflare's outage analyses, to replace dense prose.
- Tooling: Leveraging software like Hemingway Editor and Grammarly to refine clarity and eliminate grammatical errors.