I can see how this fits with Facebook&#x27;s &quot;move fast and break things&quot; philosophy. <i>Quantity over Quality</i>, and I&#x27;m okay with that if you&#x27;re in a nice sandboxed environment where you&#x27;re not accountable for your mistakes. In the case of Facebook, or indeed any vertically integrated environment this works fine but in a great many other environments you need to be more careful about mistakes. I agree that the approach of applying a strict quality control pipeline to creative output is over-applied in the industry as a whole - which Facebook have had some success with challenging - but in a great many other areas it is still absolutely necessary (advances in cloud platforms and devops perhaps notwithstanding). In many cases we have a lesser degree of control over software once it leaves the office, and it is a great pain for us to fix (more costly, more embarassing) once it is in the wild.<p>Similarly as a more general principle, or as more specifically applied to blog posts - I like other more &quot;ordinary&quot; people am held accountable for the the words that come out of my mouth, and for the material I put up on my blog. Since I&#x27;m not a lionized &quot;agent of influence&quot; the words I write will be more critically appraised; could easily be misunderstood, or taken out of context.<p>That said, and I have to admit to only reading a handful of his posts, the quality of Kent&#x27;s output could just be naturally &quot;that good&quot; that he doesn&#x27;t need to worry about these kinds of things. Which could well be one of the characteristics that has got him where he is. But I have to question this approach as applied more generally, to be emulated by mere mortals.