Perlis' Epigrams (1982)

The most productive thing I&#x27;ll do all day:<p>```sh curl -s -L <a href="http:&#x2F;&#x2F;www.cs.yale.edu&#x2F;homes&#x2F;perlis-alan&#x2F;quotes.html" rel="nofollow">http:&#x2F;&#x2F;www.cs.yale.edu&#x2F;homes&#x2F;perlis-alan&#x2F;quotes.html</a> | tr &quot;\n&quot; &quot; &quot; | grep -o -e &quot;[0-9]\+\.[^\&lt;]*&quot; | sed -e &quot;s&#x2F;^[0-9]\+\. &#x2F;&#x2F;&quot; | sort -R | head -n1 | cowsay ```

&gt; 20. Wherever there is modularity there is the potential for misunderstanding: Hiding information implies a need to check communication.<p>This is a really great point. Along the same vein: modularity has a cost too. A cost in terms of communication. The benefits of modularity should be weighed against this cost.<p>We&#x27;re really good at talking about new patterns to increase modularity, in particular in the OOP tradition (always hide data, every data structure is its own little module with a public interface). We&#x27;re very bad at talking about the costs associated with these.

Another collection of wisdom, this time from David Farber. <a href="https:&#x2F;&#x2F;www2.cs.arizona.edu&#x2F;icon&#x2F;oddsends&#x2F;farber.htm" rel="nofollow">https:&#x2F;&#x2F;www2.cs.arizona.edu&#x2F;icon&#x2F;oddsends&#x2F;farber.htm</a><p>These days, Dave is in Japan. Co-Director, Cyber Civilization Research Center and Distinguished Professor, Keio University Tokyo Japan ------------------------------------------ ip: ip Permalink: <a href="https:&#x2F;&#x2F;ip.topicbox.com&#x2F;groups&#x2F;ip&#x2F;T5d02d25c6d0cdd1c-Mccf10bbd6665d60e202f992a" rel="nofollow">https:&#x2F;&#x2F;ip.topicbox.com&#x2F;groups&#x2F;ip&#x2F;T5d02d25c6d0cdd1c-Mccf10bb...</a> Delivery options: <a href="https:&#x2F;&#x2F;ip.topicbox.com&#x2F;groups&#x2F;ip&#x2F;subscription" rel="nofollow">https:&#x2F;&#x2F;ip.topicbox.com&#x2F;groups&#x2F;ip&#x2F;subscription</a>