article
November 22, 2021
4 min read
0 views
Writing RFCs That Actually Get Read
Most internal RFCs are written for the author, not the reviewer. A format shift and a forcing function — a 48-hour async comment window — changed adoption rates on our team.
Most internal RFCs are written for the author, not the reviewer. A format shift and a forcing function — a 48-hour async comment window — changed adoption rates on our team.
Overview
This note is part of the field-notes archive generated for this site. The summary below is the published excerpt; you can expand the full write-up anytime in the CMS.
Related notes
Tags
- rfcs
- engineering-management
- documentation
- process
- communication
M
Manish Bookreader
Electronics enthusiast, Embedded Systems Expert, Linux/Networking programmer, and Software Engineer passionate about AI, electronics, books, and cooking.
