Write the READMEs, design docs, and proposals that get read, get understood, and move work forward.
Engineers are told writing is a soft skill, a thing you do when the real work is done. That framing is exactly backwards. The document that explains a system is what lets ten people build on it instead of one. The design doc that gets read is how a risky change gets aligned before a line of code is written. The clear proposal is how good ideas win. Writing is not the paperwork around engineering; it is one of the highest-leverage things a technical person does.
This course teaches the writing that technical professionals actually produce and depend on: READMEs and code comments, API and reference docs, design documents and RFCs, technical proposals, and incident postmortems. You will learn to write for the reader instead of yourself, put the bottom line up front, cut the clutter that hides your point, and structure documents people can skim and trust. The teaching leans on the field's best sources, from Zinsser and Strunk and White to the Diataxis framework and Google's postmortem practice. Every chapter ends with a quiz, and the course ends with a timed final exam and a verifiable certificate.
Nathan Okoro is a staff engineer who noticed early that the people whose work spread fastest were not the best coders but the clearest writers. He has spent years teaching engineers that a design doc nobody reads is a design that nobody trusts, and that fixing the writing is usually easier than they fear.