Technical Writing
Writing RFCs and Design Notes
Turn half-formed ideas into readable proposals teammates comment on without confusion.
6 weeks Blended Advanced
USD 110 informational until invoiced
Program narrative
We study lightweight RFC templates, decision logs, and ADR snippets. You outline tradeoffs, capture non-goals, and invite dissent politely—skills that transfer across startups and enterprises.
What ships in the syllabus
- Skeletons for one-pagers vs multi-page proposals
- Language for “non-goals” and “open questions” sections
- Workshops on commenting culture: firm vs friendly
- Peer review using a two-color markup method
- Examples from API versioning and data migration decisions
- Office hours with reviewers who published internal RFCs
- Library of transition sentences between technical sections
Outcomes you can demonstrate
- Draft a one-page RFC with context, proposal, and risks
- Summarize feedback themes without defensive language
- Cut jargon that obscures the decision you need
Lead mentor
Diego Salazar
Staff engineer alumni network; focuses on async writing hygiene.
Cohort questions
Includes an explicit limitation on scope.
Do I need an idea ready?
We supply prompts if you prefer not to expose proprietary work.
Is markdown required?
Recommended, but you may use Google Docs with heading styles mapped similarly.
What is not included?
Legal review of contracts or external publishing—internal-style docs only.
Recent participant notes
“Anonymous — non-goals section stopped my RFCs from ballooning. Review salon timing was tight for my timezone; recordings helped.”