<i>compare the experience of using both coffee machines, even if the former doesn’t give you the exact kind of coffee you want, you are still far better off.</i><p><i>Documentation is terrible for applications. If you think that your application really requires documentation, it’s too complicated, and it’s going to make your users frustrated.</i><p>I strongly disagree. 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>Being frustrated is also normal. It&#x27;s a natural part of the learning process. If everyone was always expecting everything to &quot;just work&quot; and gave up the moment they encountered the smallest bit of frustration, nothing would ever get done.<p>That said, although there is a lot of superfluous complexity in software today (dependencies are mostly responsible), I don&#x27;t think it justifies turning everything into unconfigurable featureless appliances or not writing documentation. General-purpose computers are immensely flexible and powerful, and if we want them to remain that way, I think it&#x27;s well worth putting in the effort to learn. The culture of instant gratification that seems so prevalent today may become counterproductive in the long term.