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
Agile as Trauma An Essay by Dorian Taylor doriantaylor.com The Agile Manifesto is an immune response on the part of programmers to bad management. Many a corner officeIntramural brownie pointsFeature factories agilemanagement
Many a corner office I want you to consider instead the possibility that Waterfall came to exist, and continues to exist, for the convenience of managers: people whose methods are inherited from military and civil engineering, and who, more than anything else, need you to promise them something specific, and then deliver exactly what you promised them, when you promised you’d deliver it. There exists many a corner office whose occupant, if forced to choose, will take an absence of surprises over a substantive outcome. surpriseplanning
Intramural brownie points Features don’t work, in the sense that they can be easily gamed. A brittle and perfunctory implementation, done quickly, is going to score more intramural brownie points over a robust and complete one. If the question is "does product A have feature X?" then the answer is yes either way. features
Feature factories We use the term feature factory as a pejorative to designate companies addicted to adding features, while accumulating incalculable so-called technical debt. This situation is driven by management for the convenience of marketing, and I am skeptical that a more faithful application of Agile principles will correct it. Indeed, I suspect Agile processes are constitutionally vulnerable to this kind of compromise. The presence of a feature can only indicate to a user if a goal is possible, behavior will determine how painful it will be to achieve it. ux