An ethics of mutual care Foregrounding maintenance and repair as an aspect of technological work invites not only new functional but also moral relations to the world of technology. It references what is in fact a very old but routinely forgotten relationship of humans to things in the world: namely, an ethics of mutual care and responsibility. Steven J. Jackson, Rethinking Repair ethicshumanitymoralitytechnology
I choose a world with pyramids Which would you choose: a world with pyramids? Or without? Humanity has always dreamt of flight, but the dream is cursed. My aircraft are destined to become tools for slaughter and destruction. But still, I choose a world with pyramids in it. Which world will you choose? Hayao Miyazaki, The Wind Rises Beauty in flight flighthumanityinnovationmorality
The quality of the day It is something to be able to paint a particular picture, or to carve a statue, and so to make a few objects beautiful; but it is far more glorious to carve and paint the very atmosphere and medium through which we look, which morally we can do. To affect the quality of the day, that is the highest of arts. Henry David Thoreau, Walden Suburban Nation uxartmoralitybeauty
Nature undisturbed My chief aim is simply to describe and explain the technological fabric of society, not to judge whether it is good or bad, beautiful or ugly. And yet I would not argue that technology is neutral or value-free. Quite the contrary: I suggest that the signs of human presence are the only elements of the landscape that have and moral or aesthetic significance at all. In nature undisturbed, a desert is not better or worse than a forest or a swamp; there is simply no scale on which to rank such things unless it is a human scale of utility or beauty. Only when people intervene in nature is there any question of right or wrong, better or worse. Brian Hayes, Infrastructure: A Guide to the Industrial Landscape naturemoralityaestheticshumanity
We infantilize ourselves Here in the US, we expect government and law to be our conscience. Our superego, you could say. It has something to do with liberal individualism, and something to do with capitalism, but I don't understand much of the theoretical aspect—what I see is what I live in. Americans are in a way crazy. We infantilize ourselves. We don't think of ourselves as citizens—parts of something larger to which we have profound responsibilities. We think of ourselves as citizens when it comes to our rights and privileges, but not our responsibilities. We abdicate our civic responsibilities to the government and expect the government, in effect, to legislate morality. David Foster Wallace, The Pale King societygovernmentpoliticsmoralitycivics
List of games that Buddha would not play A List en.wikipedia.org … Guessing at letters traced with the finger in the air or on a friend's back. (letters in the Brahmi script) Guessing a friend's thoughts. … gameszenmorality
The amorality of Web 2.0 An Essay by Nicholas Carr www.roughtype.com The Internet is changing the economics of creative work – or, to put it more broadly, the economics of culture – and it’s doing it in a way that may well restrict rather than expand our choices. Wikipedia might be a pale shadow of the Britannica, but because it’s created by amateurs rather than professionals, it’s free. And free trumps quality all the time. wwwmoralityeconomicsgoodness
A Mindful Mobile OS An Article by Clo S. thistooshallgrow.com I read and loved Potential's "iOS 15, Humane" proposition. Published earlier in June by co-founders Welf and Oliver, it tackles how iOS could help us better protect our attention. As a designer who cares about and writes about digital wellness, I'm profoundly aligned with their suggestions. Persuasive design Disclosure requirement From infinite feeds to pages Was this time well spent? Regret tax Conditions of use moralityethicsuxsoftwaredesign
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