This is over-the-top negative. An RFC is not intended to be "paperwork", about the manager, or about "shouting each other down until an idea wins" - it's way mo

This is over-the-top negative. An RFC is not intended to be "paperwork", about the manager, or about "shouting each other down until an idea wins" - it's way more about the engineer, and helping us create a good design that has broad buy-in. Specifically, writing RFCs asks an engineer to articulate a design, consider and list the tradeoffs involved, and evaluate it against a set of motivating use cases. It also invites feedback: other people may have legitimate concerns or find blind spots. As the writer you don't have to make changes to incorporate everyone's views: it's up to you to decide on a case-by-case basis if their feedback needs to be incorporated or not.