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
Don't get me wrong An Article by Austin Kleon austinkleon.com No phrase makes me want to stop reading more. “Don’t get me wrong” is usually a tell — a kind of backpedaling that sets off an internal alarm and suggests I’m a) reading a hyperbolic argument (which, admittedly, describes the majority of online writing these days) or b) that the writer is just lazy. Either way, when I see “don’t get me wrong,” I start to suspect I’m reading a piece of writing that might not be worth my time. If you find yourself using “don’t get me wrong,” I have a suggestion: Delete the phrase and rewrite what came before it so I don’t get you wrong. writing