Turn them into cycles Permaculture systems seek to stop the flow of nutrient and energy off the site and instead turn them into cycles, so that, for instance, kitchen wastes are recycles to compost; animal manures are directed to biogas production or to the soil; household greywater flows to the garden; green manures are turned into the earth; leaves are raked up around trees as mulch. Bill Mollison, Introduction to Permaculture Two CyclesAn ecological cycle ecosystemsrecyclinggardens
Introduction to Permaculture A Book by Bill Mollison modernfarmer.com The conscious design and maintenance of agriculturally productive systems which have the diversity, stability, and resilience of natural ecosystems. It is the harmonious integration of the landscape with people providing their food, energy, shelter and other material and non-material needs in a sustainable way. About PermaculturePermaculture ethicsUsing akido on the landscapePermaculture principlesDesign is a connection between things+25 More 172. Garden Growing WildProtected, yet tuned inHints towards a non-extractive economy farmingnatureecosystemssustainabilityagriculture
Stress systems An Article by Ethan Marcotte ethanmarcotte.com The [Lake Erie] ecosystem underwent a series of changes, each of which were related. There was an increase in the human population; which led to higher phosophorus levels in the water; which led, at last, to an increased level of algae in the lake. In effect, Lake Erie’s ecosystem was rewritten. Changed by human activities into…something else. But Franklin cites the study because it’s doing something slightly novel: applying Selye’s principle of stress to ecological systems, suggesting that they are, much like humans, just as susceptible to external stressors. And I’ve been thinking about that a lot lately, especially this week. Because Franklin’s suggesting that the work begins not by “fixing the system.” Rather, she suggests it’s about shifting the priority a little: to removing whatever stress you can. The Real World of Technology systemsecosystemsstress
Deadlines are bullshit An Article contrariantruth.substack.com In software development deadlines are a necessary evil. It is important to understand when they are necessary, and it is important to understand why they are evil. External vs. internal deadlinesWhy are internal deadlines evil?Engineers who love their work Hofstadter's LawThe Thing-deadline calculusNever enough timeDriving engineers to an arbitrary date is a value destroying mistake bureaucracysoftwareprocesswork
External vs. internal deadlines When are deadlines necessary? Contractual obligations Technical liabilities (e.g., dependency EOL) Compliance, government, investors, and other external stakeholders What do all of these deadlines have in common? They are all important. They are all deadlines that cannot be missed. They are all external. When are deadlines evil? Your manager says you have a deadline Your software development methodology says you have deadlines What do all of these deadlines have in common? None of them are important. They are arbitrary. They are all internal. They are all bullshit.
Why are internal deadlines evil? Estimation: When estimating engineering work a substantial time investment is required by an engineer in order to get an accurate estimate. Misaligned Incentives: There is an incentive to lie and give estimates much longer than the feature is truly expected to take. Low Morale: Deadlines are likely to be missed often. Repeated failure has a cost to the morale of the team. Micromanagement: Deadlines are wielded by middle managers as a whip to harass and annoy engineers working on features. High Stress: When engineers feel the pressure of other stakeholders holding deadlines over their heads it creates an environment of high stress. High Turnover: On teams with high turnover rates the best engineers have an easy time finding new work and leave quickly, the worst engineers have a difficult time finding work and remain. This selects for a lower quality team over time.
Engineers who love their work The resolution is simple. Never have internal deadlines. Operate on a prioritized and ordered list of features. Estimate only when necessary to prioritize and do so in a t-shirt sizing way. Trust your engineers and they will begin to love their work. Engineers who love their work are happy and productive. Building is never a straight line