The Laws of Software Process (2)
More laws and observations

These are also included in my book and are extensions of the three laws:

• Corollary to The First Law: You cannot have a process for something you have never down and do now know how to do.
  This is pretty evident  [1].

• The Reflexive Creation of Systems and Processes:
  1. The only way that effective systems can be created is through the application of effective processes.
  1. The only way that effective processes can be created is through the construction of effective systems.
  Both mutually and internally self-referential [4]

• The Lemma of Eternal Lateness: The only processes we can use on the current project were defined on previous projects.  Which were different.
  One project behind[5]

• The Dual Hypotheses of Knowledge Discovery:
  Hypothesis One: We can only "discover" knowledge in an environment that contains that knowledge
  Hypothesis Two: The only way to assert the validity of andy knowledge is to compare it to another source of knowledge.
  We have already address this 5]

• 
  

We will explore the ramifications of these "laws" in the large sense of knowledge creation, transcription, communication, and storage over the next few pages.

FOOTNOTES 

[1]  Phillip G. Armour The Laws of Software Process: A New Model for the Production and Management of Software Auerbach 2003  ISBN-10‏ : ‎ 0849314895

ISBN-13 ‏: ‎ 978-0849314896.
[2]  These are not "laws" in an explicit and definitive sense, more like heuristics such as "Murphy's Law".  So, some of the observations are intentionally wry and are not to be taken too seriously.

[3]  That "process" defined here is limited to the storage, rather than the acquisition of knowledge since the First Law statement specifies "...know how to do..." which means the knowledge has already been acquired.  Of course, there can be a "process" for acquiring knowledge but this is dependent on the storage target and, if the knowledge is entirely "new" and is being acquired the first time for anyone, the mechanism used must be more akin to a "meta-process" than a prescriptive stepwise process.
[4]  This is saying much the same thing as footnote [3] above.  True knowledge discovery must not be overly confining. 
[5]  The advent of AI-driven systems development is chipping away at this.  But while such approaches can, at present, create quite complex computer systems, they still have to be initiated by the input of some requirements by a human.  That is, a person still has to instruct the AI system what needs to be done while leaving the system to decide how it will be donw.  This is likely to change in the very near future and AI may create systems without any input from humans at all.