Latest / Tech Leadership with Fexingo: Engineering Managers, CTOs, and Technical Leadership Conversations
Why You Should Write Your RFCs in Public
Most engineering teams write RFCs (Request for Comments) behind closed doors. In this episode, Lucas and Luna explore why publishing RFCs to the entire company — not just the engineering org — can catch architectural blind spots early, reduce rework, and build institutional knowledge. They dig into a case where a database migration proposal caught a critical data compliance issue because someone in legal spotted it during the public comment period. They discuss the trade-offs: more eyes means more noise, but also more signal. Lucas argues that the transparency forces authors to write more…
The skinny
The skinny isn't ready yet — notes appear once the transcript is processed.