This is already a softer statement than the rule proclaimed in the article (&quot;not many&quot; vs &quot;none&quot;).<p>And if you have to do something unusual due to limitations (say, a bug in a 3rd-party library) in your code I don&#x27;t want to know about that when reading the method&#x27;s documentation (what you refer to as &quot;summary&quot;) to be able to use your code. I want to be bothered with it when I have to read its implementation because I have to fix some bug in it.