Say it like this
- We should RFC this architecture change before we start coding.
- Can you open an RFC for the new API design?
- I left comments on your RFC in the shared doc.
Use it at work
Proposing
- I've written an RFC for the new auth system.
- Please comment on the RFC by Friday.
Decision process
- Big changes need an RFC first.
- The RFC was approved with small changes.
Standards
- That behavior is defined in the HTTP RFC.
- Which RFC covers this?
Don't say this
RFC is not a verb meaning to approve; use 'publish' or 'open' instead. RFC is the document or process.
Don't mix it up
| Term | What it is | Who writes or uses it | When |
|---|---|---|---|
| RFC | Proposal for feedback | Engineers | Before deciding |
| ADR | Record of a decision made | Engineers | After deciding |
| design doc | How it will be built | Engineers | Before building |
Practice
Try it
4 quick exercises
1. Your team is planning a major database change. What do you say?
2. Before we redesign the payment system, we must _______ an RFC to gather feedback from the finance and security teams.
3. Which sentence uses RFC incorrectly?
4. Rewrite this using RFC: 'Before we make this big technical decision, we should write a document and have everyone discuss it and give us feedback.'
Say it out loud
Phrase 1 of 3
"We should RFC this architecture change before we start coding."
We don't save your recording. The word check uses your browser's speech recognition.
More about RFC
Real examples(3)
- in a standup
"I started an RFC for the database migration. Please review it and add your comments by Friday."
- in an email
"Before we redesign the authentication system, let's publish an RFC to gather feedback from the security team."
- in a code review
"This change is large enough that it should have gone through the RFC process first."
More mistakes(2)
Handle with care. RFC is not a request for permission but a formal proposal inviting discussion and feedback. Do not use it for quick approvals or urgent decisions.
- ✕Send me an RFC if you need my approval on this feature.✓Send me an RFC if you want feedback and discussion on this feature proposal.
An RFC invites discussion and consensus, not a quick approval. RFCs are for significant decisions, not minor requests.
- ✕I will RFC that bug fix tomorrow.✓I will open an RFC for the refactoring plan tomorrow.
Small bug fixes do not require an RFC. Use RFC for major features, architecture changes, or decisions affecting multiple teams.
Other forms(2)
- RFC noun
"The RFC for the new caching strategy is ready for review."
- to open/publish/submit an RFC noun
"We plan to open an RFC next week for the microservices migration."
Often used with(5)
- open an RFC · to initiate or create a new RFC document for team discussion
- submit an RFC · to formally present an RFC for review and feedback
- review an RFC · to read and provide comments on a proposed RFC
- approve an RFC · to sign off on an RFC after discussion, clearing it for implementation
- RFC feedback · comments and suggestions from team members on an RFC
Similar words(3)
- design document · broader term; an RFC is a specific type of design document with a defined review process
- proposal · more general; an RFC is a formal, structured proposal in tech
- specification · RFC specifies what will be built, but usually at a higher level than a full technical spec
Opposites(2)
- implementation
- code review
Questions(6)
- What does RFC stand for?
- RFC stands for Request for Comments. In software engineering, it is a formal document proposing a significant technical change or feature, designed to invite feedback and discussion from the team before implementation.
- When should I write an RFC?
- Write an RFC for major architectural changes, significant new features, refactoring efforts that affect multiple systems, or any decision that impacts multiple teams or the product roadmap. Do not use RFC for small bug fixes or routine tasks.
- What should an RFC include?
- A good RFC typically includes: a clear problem statement, the proposed solution, alternative approaches considered, tradeoffs and risks, implementation timeline, and impact on other systems. The exact format varies by company, but the goal is always to enable informed discussion.
- Is RFC formal or informal?
- RFC is neutral to formal. It is a structured, professional process used in technical discussions, but the tone of discussion can be collaborative and informal. The document itself is formal, but the feedback process often encourages open dialogue.
- How long should an RFC be?
- RFCs vary in length depending on complexity. Simple proposals might be 1-2 pages; complex architectural changes could be 5-10 pages. The goal is to provide enough detail for informed feedback without being overwhelming.
- What happens after an RFC is approved?
- After an RFC is approved through discussion and consensus, the engineering team begins implementation. The RFC becomes a reference document throughout the project, and the final implementation is often compared against the RFC to ensure alignment.
