Most engineers donโ€™t think of themselves as writers

Most engineers I know donโ€™t think of themselves as writers. But writing is a core part of the job, whether it’s writing commit messages, documenting designs, updating documentation, or sharing the occasional blog post.

The challenge isnโ€™t knowing what to write, itโ€™s writing it so someone else can easily read it. Clarity doesnโ€™t mean dumbing things down. It means doing the hard work of making complexity digestible, without losing accuracy.

A few principles that have helped me:

  • Writing is part of the engineering process, not a separate task.
  • Write it like you’re explaining it to a technical friend.
  • Youโ€™re not dumbing it down, youโ€™re making it readable.
  • Comments are writing too, treat them with care.
  • Your voice matters, even in technical writing.
  • If no one reads it, it didnโ€™t happen.

Better writing doesnโ€™t just help your team; it builds credibility and increases your impact. Itโ€™s not just a soft skill, itโ€™s a superpower.