&gt; There is value in providing good defaults, but users will and should be encouraged to go beyond them. That&#x27;s what the documentation is for.<p>While the original article does not state this directly, it is implied that he&#x27;s talking about programs where you have to read the manual to be able to use even its most basic functionality. Right now, I want to get a job done. Exploring can come later when I&#x27;ve got time for it.<p>&gt; Being frustrated is also normal. It&#x27;s a natural part of the learning process.<p>It&#x27;s part of the learning process when you&#x27;re breaking ground. It&#x27;s not appropriate when you&#x27;re trodding the well-worn path. If your users have to resort to SO questions just to do common case things, you&#x27;ve failed them.<p>&gt; I don&#x27;t think it justifies turning everything into unconfigurable featureless appliances or not writing documentation.<p>He is recommending neither.