# Sandy Maguire - How to Write Technical Posts (Highlights) ![rw-book-cover|256](https://readwise-assets.s3.amazonaws.com/static/images/article3.5c705a01b476.png) ## Metadata **Cover**:: https://readwise-assets.s3.amazonaws.com/static/images/article3.5c705a01b476.png **Source**:: #from/readwise **Zettel**:: #zettel/fleeting **Status**:: #x **Authors**:: [[Sandy Maguire]] **Full Title**:: How to Write Technical Posts **Category**:: #articles #readwise/articles **Category Icon**:: 📰 **Document Tags**:: #from/pocket #writing **URL**:: [reasonablypolymorphic.com](https://reasonablypolymorphic.com/blog/writing-technical-posts/) **Host**:: [[reasonablypolymorphic.com]] **Highlighted**:: [[2020-08-02]] **Created**:: [[2022-09-26]] ## Highlights - You’ll make it easier for people to understand what you’re trying to tell them The value of this post - four sentences to convince them - solutions to problems - focusing on *why* - first sentence of each paragraph should be sufficient to understand the rest of the paragraph - keep them on the same page Less distractions - Point out what they might be thinking, and then very explicitly show them what they should be thinking instead. - If you’re giving examples of something that fits a pattern, make sure you give examples of things that *do not* fit the pattern. - People learn by seeing lots of examples - Anticipate which parts of your argument will be difficult for your readers Empathy