jmac<p>I wrote up a tech-writing technique I call the assertions document. It helps you rapidly develop your own understanding of a new-to-you topic by getting your subject-matter experts engaged in the docs project as quickly as possible, and even eager to help you—largely by giving them ways to tell you how you're wrong. <a href="https://masto.nyc/tags/TechWriting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TechWriting</span></a> <a href="https://masto.nyc/tags/TechnicalWriting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TechnicalWriting</span></a> <a href="https://fogknife.com/2025-04-04-assert-your-way-to-stronger-technical-writing.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">fogknife.com/2025-04-04-assert</span><span class="invisible">-your-way-to-stronger-technical-writing.html</span></a></p>