<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Rfc on Bits, Trades &amp; Systems</title>
    <link>https://blog.turboawesome.win/tags/rfc/</link>
    <description>Recent content in Rfc on Bits, Trades &amp; Systems</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 21 Aug 2024 09:45:00 +0000</lastBuildDate>
    <atom:link href="https://blog.turboawesome.win/tags/rfc/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Writing RFCs for Wide Audiences</title>
      <link>https://blog.turboawesome.win/2024/08/writing-rfcs-for-wide-audiences/</link>
      <pubDate>Wed, 21 Aug 2024 09:45:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2024/08/writing-rfcs-for-wide-audiences/</guid>
      <description>RFCs that need sign-off from multiple teams or leadership require a different structure than internal team proposals. The writing changes when the audience includes people who don&amp;#39;t share your context.</description>
    </item>
  </channel>
</rss>
