Miguel Afonso Caetano<p>"Errors in content, especially technical documentation, lead to mistrust. When you write a piece of content, consider the future of the content.</p><p>The future of the content depends on the purpose and type of content that you’re writing. This list contains some common expectations that readers might have about various content types:</p><p>- A blog post has a date stamp and isn’t kept continually updated.</p><p>- Technical documentation always matches the product version that it references.</p><p>- Architecture documents reflect the current state of the microservice architecture.</p><p>- An email gets the point across and can’t be edited after you send it.</p><p>You must consider the future and maintenance of any content that you write if your readers expect it to be kept up-to-date. To figure out how difficult maintaining your content will be, you can ask yourself these questions:</p><p>- How frequently does the thing I’m writing about change?</p><p>- How reliable does my content need to be?</p><p>- How quickly does my content need to be accurate (e.g., after a product release)?</p><p>By answering these questions, you can then make decisions about how you write your content.</p><p>- What level of detail will you include in your content?</p><p>- Will you focus your efforts on accuracy, speed, or content coverage?</p><p>- Do you want to include high-fidelity screenshots, gifs, or complex diagrams?</p><p>- Do you want to automate any part of your content creation?</p><p>- Who will review your content? How quickly and thoroughly will they review it?"</p><p><a href="https://thisisimportant.net/posts/how-can-i-get-better-at-writing/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">thisisimportant.net/posts/how-</span><span class="invisible">can-i-get-better-at-writing/</span></a></p><p><a href="https://tldr.nettime.org/tags/TechnicalWriting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechnicalWriting</span></a> <a href="https://tldr.nettime.org/tags/TechnicalCommunication" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechnicalCommunication</span></a> <a href="https://tldr.nettime.org/tags/ProfessionalWriting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ProfessionalWriting</span></a> <a href="https://tldr.nettime.org/tags/SoftwareDocumentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoftwareDocumentation</span></a> <a href="https://tldr.nettime.org/tags/InformationArchitecture" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>InformationArchitecture</span></a></p>