{"id":1767,"date":"2014-06-18T00:00:00","date_gmt":"2014-06-17T22:00:00","guid":{"rendered":"https:\/\/wwwneu.strehle.de\/tim\/weblog\/archives\/2014\/06\/18\/1726\/"},"modified":"2014-06-18T00:00:00","modified_gmt":"2014-06-17T22:00:00","slug":"1726","status":"publish","type":"post","link":"https:\/\/www.strehle.de\/tim\/weblog\/archives\/2014\/06\/18\/1726\/","title":{"rendered":"Eric Steven Raymond: Basics of the Unix Philosophy"},"content":{"rendered":"<p>I keep coming <a href=\"\/tim\/weblog\/archives\/2003\/12\/16\/234\">back<\/a> to Eric Steven Raymond\u2019s 2003 <a href=\"http:\/\/www.faqs.org\/docs\/artu\/ch01s06.html\">Basics of the Unix Philosophy<\/a>:<\/p>\n<p>\u201cRule of Modularity: Write simple parts connected by clean interfaces.<\/p>\n<p>Rule of Clarity: Clarity is better than cleverness.<\/p>\n<p>Rule of Composition: Design programs to be connected to other programs.<\/p>\n<p>Rule of Separation: Separate policy from mechanism; separate interfaces from engines.<\/p>\n<p>Rule of Simplicity: Design for simplicity; add complexity only where you must.<\/p>\n<p>Rule of Parsimony: Write a big program only when it is clear by demonstration that nothing else will do.<\/p>\n<p>Rule of Transparency: Design for visibility to make inspection and debugging easier.<\/p>\n<p>Rule of Robustness: Robustness is the child of transparency and simplicity.<\/p>\n<p>Rule of Representation: Fold knowledge into data so program logic can be stupid and robust.<\/p>\n<p>Rule of Least Surprise: In interface design, always do the least surprising thing.<\/p>\n<p>Rule of Silence: When a program has nothing surprising to say, it should say nothing.<\/p>\n<p>Rule of Repair: When you must fail, fail noisily and as soon as possible.<\/p>\n<p>Rule of Economy: Programmer time is expensive; conserve it in preference to machine time.<\/p>\n<p>Rule of Generation: Avoid hand-hacking; write programs to write programs when you can.<\/p>\n<p>Rule of Optimization: Prototype before polishing. Get it working before you optimize it.<\/p>\n<p>Rule of Diversity: Distrust all claims for &#8222;one true way&#8220;.<\/p>\n<p>Rule of Extensibility: Design for the future, because it will be here sooner than you think.\u201d<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I keep coming back to Eric Steven Raymond\u2019s 2003 Basics of the Unix Philosophy: \u201cRule of Modularity: Write simple parts connected by clean interfaces. Rule of Clarity: Clarity is better than cleverness. Rule of Composition: Design programs to be connected to other programs. Rule of Separation: Separate policy from mechanism; separate interfaces from engines. Rule [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","_share_on_mastodon":"0"},"categories":[1],"tags":[],"class_list":["post-1767","post","type-post","status-publish","format-standard","hentry","category-weblog"],"share_on_mastodon":{"url":"","error":""},"_links":{"self":[{"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/posts\/1767","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/comments?post=1767"}],"version-history":[{"count":0,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/posts\/1767\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/media?parent=1767"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/categories?post=1767"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/tags?post=1767"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}