Free — no signup required

Introduction: Why Engineers Must Write

2 min read

Code is Not Enough

Think of a courtroom. A lawyer who can argue brilliantly in person but can't write a coherent brief will lose cases that a mediocre writer would win — because the written record is what persists, gets reviewed, and ultimately decides outcomes. Engineering organizations work the same way. Great code is the verdict, but the written arguments that led to it determine whether the right verdict was reached.

As organizations grow, verbal communication breaks down. You can't have a coffee chat with 500 people. Decisions made in a hallway are lost to history. The engineer who was in the room when the choice was made leaves the company, and six months later a new team re-litigates the same debate from scratch — wasting weeks and often reaching a worse conclusion.

A strong written culture is the antidote to this chaos. It forces clarity of thought. As the old saying goes, "If you can't write it down clearly, you probably don't understand it yet." Writing is not just a communication tool — it is a thinking tool. The act of constructing a coherent argument in prose exposes gaps in reasoning that a bullet-point slide or a verbal pitch can hide.

Writing things down provides several compounding benefits:

  1. Asynchronous Communication: People in different time zones can contribute without a meeting. A document written at 9 AM in London can be reviewed and commented on at 9 AM in San Francisco — no one waits.
  2. Scalability: A document can be read by one person or one thousand people with zero extra effort from the author. A meeting, by contrast, scales linearly with attendees and degrades in quality as the room grows.
  3. Organizational Memory: It creates a permanent record of why decisions were made, not just what was decided. This is the difference between a team that learns from its past and one that repeats it.
  4. Meritocracy of Ideas: In a meeting, the loudest or most senior voice often wins. In a written review, a junior engineer's well-reasoned argument can outweigh a VP's gut feeling — because the argument is visible, persistent, and can be evaluated on its merits.

In this topic, we will look at three specific, powerful formats for written communication used by top tech companies: the Narrative Memo (Amazon's 6-pager), the RFC (Request for Comments), and the Strategy Document.

This is one of 18 chapters

Every chapter is free — Kubernetes, Terraform, SRE, distributed systems, and more — with fast daily review built in.

Sign up free