There are two basic steps to good permaculture design. The first deals with laws and principles, while the second is more closely associated with practical techniques.
The principles are inherent in any permaculture design, in any climate, and at any scale. They are, briefly:
Relative location: every element is placed in relationship to another so that they assist each other
Each element performs many functions.
Each important function is supported by many elements.
Efficient energy planning for house and settlement.
Emphasis on the use of biological resources over fossil fuel resources.
Energy recycling on site.
Using and accelerating natural plant succession to establish favourable sites and soils.
Polyculture and diversity of beneficial species for a productive, interactive system.
Of all the principles of software engineering which has fallen by the wayside in the modern “move fast and break things” mentality of assholes modern software developers, reliability is perhaps the most neglected, along with its cousin, robustness. Almost all software that users encounter in $CURRENTYEAR is straight-up broken, and often badly.
The human maker, working in unself-conscious matter, receives no worship from his creatures, since their will is no part of his material; he can only receive the response of their nature, and he is alone in fault if that response is not forthcoming. If he tortures his material, if the stone looks unhappy when he has wrought it into a pattern alien to its own nature, if his writing is an abuse of language, his music a succession of unmeaning intervals, the helpless discomfort of his material universe is a reproach to him alone; similarly, if he respects and interprets the integrity of his material, the seemliness of the ordered work proclaims his praise, and his only, without will, but in a passive beauty of right structure.