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.
Many of us have come to expect work to involve no slack time because of the negative way we perceive it. In a world of manic efficiency, slack often comes across as laziness or a lack of initiative. Without slack time, however, we know we won’t be able to get through new tasks straight away, and if someone insists we should, we have to drop whatever we were previously doing. One way or another, something gets delayed. The increase in busyness may well be futile.