Design docs, RFCs and ADRs · Proficient · Lesson 77 of 98 · about 7 hours
Clear technical writing
After this you can write technical prose that is short, precise and easy to scan: clear sentences, active voice, defined terms and useful structure.
Why it matters
Most engineers were never taught to write, and it shows in design docs nobody finishes reading. Good technical writing is a set of learnable habits: one idea per sentence, active voice, define terms before using them, put the conclusion first, and cut every word that does not help. Google's free Technical Writing One course is the best short training available. It takes a few hours and includes exercises. Trap: writing to sound thorough. Length signals effort to you and costs time for every reader.
How to use this resource
Free, self-paced, with exercises. Do the whole course; it is about four hours.
Go further
Go deeper