Less, but better There must be millions less of things, less words, less gestures, less of everything. But every word and every gesture will become more valuable. If we can put it all into perspective we will need less things as a result. Sophie Lovell & Dieter Rams, Dieter Rams: As Little Design as Possible Omit needless wordsTo be truly simple makingrestraintproductionwasteminimalism
From consumption to production I see no other solution (political, economic) to the problems of mankind than the formation of small responsible communities involved in permaculture and appropriate technology. I believe that the days of centralised power are numbered, and that a re-tribalisation of society is an inevitable, if sometimes painful, process. The greatest change we need to make is from consumption to production, even if on a small scale, in our own gardens. Bill Mollison, Introduction to Permaculture societyconsumptionproduction
All-use environments Until the nineteenth century, virtually all cities were “all use” environments. Craft-scale production was typically carried out in a workshop below the home of the craftsperson, which often also served as the site of exchange. Michael Sorkin, 20 Minutes in Manhattan Small economies productionwork
Biggering I meant no harm. I most truly did not. But I had to grow bigger. So bigger I got. I biggered my factory. I biggered my roads. I biggered my wagons. I biggered the loads of the Thneed’s I shipped out. I was shipping them forth to the South! To the East! To the West! To the North! I went right on biggering...selling more Thneed’s. And I biggered my money, which everyone needs. Dr. Seuss, The Lorax capitalismproduction
This thing is a Thneed "Look, Lorax," I said. "There's no cause for alarm. I chopped just one tree. I am doing no harm. I'm being quite useful. This thing is a Thneed. A Thneed's a Fine-Something-That-All-People-Need! It’s a shirt. It's a sock. It's a glove. It's a hat. But it has other uses. Yes, far beyond that. You can use it for carpets. For pillows! For sheets! Or curtains! Or covers for bicycle seats!" The Lorax said, "Sir! You are crazy with greed. There is no one on earth who would buy that fool Thneed!" Dr. Seuss, The Lorax production
The life-giving continuum In System A, creation and production are organic in character, and are governed by human judgments that emanate from the underlying wholeness of situations, conditions, and surroundings. In System B, the production process is thought of as mechanical. What matters are regulations, procedures, categories, money, efficiency, and profit: all the machinery designed to make society run smoothly, as if society was working as a great machine. The production process is rarely context-sensitive. Wholeness is left out. Identifying these two categories helps us sharpen and clarify the range of differences among ways of creating the environment that exist in different societies. And the two categories serve to identify a dimension of great importance: the dimension that runs from more life-giving to less life-giving. Christopher Alexander, The Battle for the Life and Beauty of the Earth lifeproduction
Muda, Muri, Mura An Article mag.toyota.co.uk Eliminating waste is the key to efficiency – in the Toyota Production System, this is termed as: Muda (waste), Muri (overburden), and Mura (irregularity). productionwastemanagementefficiency
A Plea for Lean Software An Essay by Niklaus Wirth cr.yp.to Software's girth has surpassed its functionality, largely because hardware advances make this possible. The way to streamline software lies in disciplined methodologies and a return to the essentials. Measured by the number of its featuresEssential vs. nice to haveDependence is more profitable than educationThe most rewarding iterationsNever enough time A grossly obese set of requirementsFeatures and complexity softwareperformancefunction
Measured by the number of its features A primary cause of complexity is that software vendors uncritically adopt almost any feature that users want. Any incompatibility with the original system concept is either ignored or passes unrecognized, which renders the design more complicated and its use more cumbersome. When a system's power is measured by the number of its features, quantity becomes more important than quality. Every new release must offer additional features, even if some don't add functionality. featuresqualitycomplexity
Essential vs. nice to have Customers have trouble distinguishing between essential features and those that are just "nice to have." Examples of the latter class: those arbitrarily overlapping windows suggested by the uncritically but widely adopted desktop metaphor; and fancy icons decorating the screen display, such as antique mailboxes and garbage cans that are further enhanced by the visible movement of selected items toward their ultimate destination. These details are cute but not essential, and they have a hidden cost. / Increased complexity results in large part from our recent penchant for friendly user interaction. I've already mentioned windows and icons; color, gray-scales, shadows, pop-ups, pictures, and all kinds of gadgets can easily be added. Menus, Metaphors and Materials: Milestones of User Interface Designlittlebigdetails interfacesux
Dependence is more profitable than education A customer who pays—in advance—for service contracts is a more stable income source than a customer who has fully mastered a product's use. Customer dependence is more profitable than customer education. What I find truly baffling are manuals—hundreds of pages long—that accompany software applications, programming languages, and operating systems. Unmistakably, they signal both a contorted design that lacks clear concepts and an intent to hook customers. The design concept documentation
The most rewarding iterations Initial designs for sophisticated software applications are invariably complicated, even when developed by competent engineers. Truly good solutions emerge after iterative improvements or after redesigns that exploit new insights, and the most rewarding iterations are those that result in program simplifications. Evolutions of this kind, however, are extremely rare in current software practice—they require time-consuming thought processes that are rarely rewarded. Instead, software inadequacies are typically corrected by quickly conceived additions that invariably result in the well-known bulk. So that you can get feedback on it and make it betterTo anticipate all the uses and abuses agileiteration
Never enough time Time pressure is probably the foremost reason behind the emergence of bulky software. The time pressure that designers endure discourages careful planning. It also discourages improving acceptable solutions; instead, it encourages quickly conceived software additions and corrections. Time pressure gradually corrupts an engineer's standard of quality and perfection. It has a detrimental effect on people as well as products. Deadlines are bullshitThe Thing-deadline calculus