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
Beyond Artboards An Essay by Chuánqí Sun medium.com The Pursuit of Lossless Design-Development Handoffs. Can't developers just see?We are the ones who paved the pathUntil we get there processinterfacesdesign
Can't developers just see? We designers love artboards. From rough UI sketches to high fidelity mockups, we see ourselves as visual artists expressing ideas on artboards that have a pre-defined width and height. To start a new project, we declare the size of the artboard in the first step. What about responsive design? Not a problem! We diligently design on three artboards — one for mobile, one for tablet, and one for desktop — with content elegantly adapting, scaling, reflowing, reordering, and reprioritizing. We proudly hand off the artboards to developers while patting ourselves on the back: this is how responsive design should be done. After weeks of arduous engineering, the product finally comes out. We find, to our great dismay, that some copy is hanging off the grid, the focal point of the hero image has been cropped out, the font sizes don’t even come close to the type ramp. What went wrong? Can’t the developers just see everything on all those artboards? Nope. Start drawing, then put the box around it
We are the ones who paved the path No matter how many screen sizes our artboards account for, some user’s browser will break loose from our prescription. With users resizing, rotating, and zooming the screen, new devices stretching, squashing, curving, and cutting (e.g. the speaker area in iPhone X) the screen, the sizes become infinite. Good luck making an artboard for each one of them. Artboards are a lossy format. Using artboards in a handoff is a lossy process. When we pitch a finite number of plans against an infinite number of situations. We inevitably get in-betweens. Once there are in-betweens, there are unknowns. Once there are unknowns there is guesswork. Once there is guesswork, there are surprises. Engineers take the path of least resistance. We are ones who paved the path. gridless.designChanging Our Development Mindset
Until we get there As a designer, learn writing HTML, or better still, semantic HTML. If coding up the entire design is too hard, try coding up one component at a time, and not worrying about CSS. The HTML alone will prove invaluable for developers to understand the content structure. In addition, you are forced to optimize the information architecture as you work out the code from content. If coding by yourself is out of the question, pair up with the engineer who will receive the design. Work closely with him or her to prototype the design, validate responsive behaviors, and obtain feedback on the feasibility. Don’t call it an iteration until the design has seen played with in code. As a manager for large enterprise, co-locate your designers and developers, encourage interdisciplinary learning, understand that each minute spent on coding before the handoff translates to ten minutes saved from changing and fixing issues after the handoff. As a stakeholder in the handoff meeting, give the designer a thumbs-up when he or she demos live code running in browsers in place of mockups on artboards. That’s a design champion you are looking at. html