Permaculture principles 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. Use of edge and natural patterns for best effect. Bill Mollison, Introduction to Permaculture principles
Software developers have stopped caring about reliability An Article by Drew DeVault drewdevault.com 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. softwareprinciples
Software Engineering as a Craft An Article by Thomas Wilson thomaswilson.xyz The decreasingly tangible product of code, i.e. that all we have are files on a hard-drive, may make it easy to forget that writing software produces a thing. If you produce a wonky chair or an overly long fork, it’s easy to see the quality of work was not great. By calling for a perception of software as a craft, we fight against that ability to forget or not notice the final quality of the product. You could watch two software engineers with different levels of experience, or in different domains, and it wouldn’t necessarily be so easy to guess which is which, at least from a distance. So maybe there is something to be said for the value of software as a craft, for sometimes focusing on the practice of making better, or at least different, software just for the sake of it. craftsoftware