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
Building Momentum An Article by Dan Mall danmall.com Fight the Waterfall Start all of the pieces of work a little bit earlier. The key to starting work early is not succumbing to the pressure of having to finish the work. Don’t worry about finishing. If you’re a developer, you can start doing things while your design or information architect are working because a lot of your work actually isn’t dependent on their work. Some of it is, so you probably won’t be able to finish, but that shouldn’t stop you from starting. Share Work-in-Progress Early and Often When you share work-in-progress, share it with the caveat that no feedback is needed at this point. You’re simply sharing it to let people know where you are. For example, if you have to make 12 wireframes, share it when you finish 2 or 3. Rather than spending a whole week to drop 12 wireframes, share 2 – 3 wireframes every 2 days. The more often you do this, you start to build rhythm, and rhythm builds momentum. processworkcollaboration