&gt; There&#x27;s hardly a post you couldn&#x27;t write in a day of hard work<p>I get paid a very high rate to edit and clean up articles written by techies who have this viewpoint.<p>When you are imparting technical knowledge that you know conceptually, it&#x27;s easy to just jot down a few thoughts. They make sense to _you_, after all. But in most cases, experts don&#x27;t recognize the assumptions that a reader might have, such as &quot;what this is&quot; and &quot;why it&#x27;s important.&quot; Like writing code, there&#x27;s a difference between &quot;make it work (at least the compiler doesn&#x27;t crash)&quot; and &quot;make it wonderful.&quot; That&#x27;s just the same for writing.<p>Personally, when I write in-depth articles, I spend a minimum of three days on it. It usually includes researching the topic, interviewing other people who know something about it (or wish they did), and writing the prose. Then I edit the prose. And I edit it again. Because I do my best to be clear and understandable, and to leave out the parts that people skip.