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
The small web is beautiful An Essay by Ben Hoyt benhoyt.com I believe that small websites are compelling aesthetically, but are also important to help us resist selling our souls to large tech companies. In this essay I present a vision for the “small web” as well as the small software and architectures that power it. Why aim small?Features and complexitySolving the problem of software bloatRaw size isn't enough Rediscovering the Small Web wwwmicrosites
Why aim small? Why aim small in this era of fast computers with plenty of RAM? A number of reasons, but the ones that are most important to me are: Fewer moving parts. It’s easier to create more robust systems and to fix things when they do go wrong. Small software is faster. Fewer bits to download and clog your computer’s memory. Reduced power consumption. This is important on a “save the planet” scale, but also on the very local scale of increasing the battery life of your phone and laptop. The light, frugal aesthetic. That’s personal, I know, but as you’ll see, I’m not alone. performancesystemsconservation
Features and complexity Niklaus Wirth of Pascal fame wrote a famous paper in 1995 called A Plea for Lean Software. His take is that “a primary cause for the complexity is that software vendors uncritically adopt almost any feature that users want”, and “when a system’s power is measured by the number of its features, quantity becomes more important than quality”. A Plea for Lean SoftwareSpeed is a featureRequirements proliferation featurescomplexity
Solving the problem of software bloat But instead of just complaining, how do we actually solve this problem? Concretely, I think we need to start doing the following: Care about size: this sounds obvious, but things only change when people think they’re important. Measure: both your executable’s size, and your program’s memory usage. You may want to measure over time, and make it a blocking issue if the measurements grow more than x% in a release. Or you could hold a memory-reduction sprint every so often. Language: choose a language that has a chance. Remove: cut down your feature set. Aim for a small number of high-quality features. My car can’t fly or float, and that’s okay – it drives well. Say no to new features: unless they really fit your philosophy, or add more than they cost over the lifetime of your project. Dependencies: understand the size and complexity of each dependency you pull in. Use only built-in libraries if you can.
Raw size isn't enough A few months ago there was a sequence of posts to Hacker News about various “clubs” you could post your small website on: the 1MB Club, 512KB Club, 250KB Club, and even the 10KB Club. I think those are a fun indicator of renewed interested in minimalism, but I will say that raw size isn’t enough – a 2KB site with no real content isn’t much good, and a page with 512KB of very slow JavaScript is worse than a snappy site with 4MB of well-chosen images. ...[Instead, it's about] an “ethos of small”. It’s caring about the users of your site: that your pages download fast, are easy to read, have interesting content, and don’t load scads of JavaScript for Google or Facebook’s trackers. minimalismcontentsize