add greenspun and shirky

Signed-off-by: Shai Sachs <[email protected]>

_laws/greenspun.md

@@ -0,0 +1,10 @@
+---
+layout: post
+title: Greenspun's tenth rule
+law: Any sufficiently complicated C or Fortran program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp.
+law-author: Philip Greenspun
+law-url: https://philip.greenspun.com/research/
+law-year: 
+---
+
+This "tenth" rule is not really preceded by nine other rules, and its original date of publication is unknown. It's a prescient warning about choosing the right rule for the job; a low-level language might not really be suitable for a sufficiently complicated task, and such a choice can in fact be self-defeating if it causes the programmer to reinvent higher-order abstractions imperfectly.

_laws/shirky.md

@@ -0,0 +1,10 @@
+---
+layout: post
+title: Shirky principle
+law: Institutions will try to preserve the problem to which they are the solution.
+law-author: Clay Shirky
+law-url: https://www.amazon.com/exec/obidos/ASIN/1594202532?&linkCode=ll1&tag=lawsofsoftwar-20&linkId=6c52158e683e33f8fcb0b106de7dbafc&language=en_US&ref_=as_li_ss_tl
+law-year: 2010
+---
+
+This law is really about business generally rather than software in particular. However, it has broad application to software since so much of software product design focuses on solving user problems. The law is a cautionary tale about the perverse incentives that can inadvertantly cuase organizations to prolong rather than solve problems. While the law was originally stated by Clay Shirky, it was coined the Shirky principle by [Kevin Kelly](https://kk.org/thetechnium/the-shirky-prin/).