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
“Design” is now “Product” An Article by Dorian Taylor dorian.substack.com Design has very little to do with what tools or methodologies you use, or what your job title is, or what you have a degree in, or even anything like “creativity”; design is about your relationship to constraints. Rather: to what extent are you defining constraints rather than just obeying them? Design is about taking a universe of possibilities and converging onto exactly one outcome. Being handed a set of constraints which you treat like immutable laws of physics (because many of them are) and solving within that envelope is what engineering is. To wit: what most designers are doing most of the time is actually a form of engineering, and engineers are always doing at least some design. This is because genuine design—the power to define constraints—is a privileged political position within an organization, and not everybody can occupy it. In other words, the “seat at the table” comes first. Design is Steve Jobs infamously dropping an iPod prototype into his fish tank, pointing at the bubbles coming out and yelling at his staff to make it thinner. It doesn’t matter what your title is; Jobs is the designer in that scenario. Steve Jobs designengineeringconstraints