It seems this transformation, from physical object to vector of data, is a general and oft-repeated process in the history of technology, where new inventions begin in an early experimental phase in which they are treated and behave as singular individual things, but then evolve into vectors in a diffuse and regimented system as the technology advances and becomes standardized.
In the early history of aviation, airplanes were just airplanes, and each time a plane landed or crashed was a singular event. Today, I am told by airline-industry insiders, if you are a billionaire interested in starting your own airline, it is far easier to procure leases for actual physical airplanes, than it is to obtain approval for a new flight route. Making the individual thing fly is not a problem; inserting it into the system of flight, getting its data relayed to the ATC towers and to flightaware.com, is.
By World War II, we seem to have come to take new gadgets for granted or relied upon advertising to inform us of what was new. Whereas our great-grandparents apparently found the latest improvement on the fountain pen or the bicycle of intellectual interest, most people in our generation take only a commercial and utilitarian view of such things.
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.
Imagine the world like a cake. Imagine that you slice it into the customary slices by vertical cuts. Each slice of that cake should signify for us, a constituency. Each is geographically located as one segment of the larger cake. Each slice is more influenced by its immediate neighbors than by what might be in the cake quite far away.
What technology has done in the world increasingly is to put horizontal cuts in that cake. You don't only talk up and down. Now you can talk across barriers.
I remain mystified by what seems like an exponential increase in the need to communicate induced by the availability of a ready new means to do so, just as new highway capacity produces increased traffic. Witness the cabdrivers who talk uninterrupted on the phone as they travel the city, or the truly huge numbers of people who speak on the phone as they walk down the street: the medium has clearly become the message, if the meaning of the message remains somewhat opaque.
It is thought-provoking that this sense of estrangement and detachment is often evoked by the technologically most advanced settings, such as hospitals and airports.
Fascination with this potential for control of our environment has prompted the invention of mechanical systems that have made natural thermal strategies seem obsolete by comparison.
Motorola developed what it called a 'technology shelf', created by a small group of engineers, on which were placed possible technical solutions that other teams might use in the future; rather than trying to solve the problem outright, it developed tools whose immediate value was not clear.
Working in the typical dot-com office was an admixture of frenetic pace and a relaxed overall atmosphere, exemplifying that chilled-out anxiety which was the general mood of the 1990’s.
I believe our job as designers is to give you what you need as quickly and elegantly as we can. Our job as designers is to take you away from technology. Our job as designers is to make you smile. To make a profit by providing you something that enhances your life in the most seamless and wonderful way possible.
Some may find puzzling or distasteful the parallel I am drawing between the study of nature and the study of technology. After all, nature is good and good for you, whereas everyone knows that technology is ugly, evil, and dangerous.
A few centuries ago—say, on the American western frontier—a quite different view prevailed. Nature was seen as savage, hostile, cruel. Mountains and forests were barriers, not refuges. The lights of civilization were a comforting sight. We took our charter from the book of Genesis, which grants mankind dominion over the beasts, and felt it was both our entitlement and our duty to tame the wilderness, fell the trees, plow the land, and dam the rivers.
In the twenty-first century, the question most of us ask when disaster strikes is not "How could God let that happen?" but "Who screwed up?" This is a salutary development: We take responsibility for the world we live in. Whether or not our world is the best of all possible worlds, it is a world we have made for ourselves. We live in an engineered landscape, on an engineered planet. Our cities and farms, our dwellings and vehicles, our power plans and communication networks—these are all creations of human artifice. If we don't like it here, we have only ourselves to blame.
Technology is not the sum of the artifacts, of the wheels and gears, of the rails and electronic transmitters. Technology is a system. It entails far more than its individual material components. Technology involves organization, procedures, symbols, new words, equations, and, most of all, a mindset.
In the automobile's technological middle age, it is hard, if not impossible, to tune or repair one's own vehicle. Technical standardization of cars has occurred, and with it the elimination of the user's access to the machine itself. At the same time, the infrastructures that once served those who did not use automobiles atrophied and vanished. Some may say they were deliberately starved out. Railways gave way to more and more roadways. And thus a technology that had been perceived to liberate its users began to enslave them.
"The point is to get people to peel those visors off their faces, to remove the goggles, to abandon the screens. Those screens whose very purpose is to screen the actual world out. Who cares about virtuality when there's all this reality—this incredible, inexhaustible, insatiable, astonishing reality—present all around!"
Everyone who interacts with computers has in important ways always already been programming them.
Every time you make a folder or rename a file on your computer, the actions you take through moving your mouse and clicking on buttons, translate into text-based commands or scripts which eventually translate into binary.
Why are the common conceptions of what a programmer and user is so divorced from each other? The distinction between programmer and user is reinforced and maintained by a tech industry that benefits from a population rendered computationally passive. If we accept and adopt the role of less agency, we then make it harder for ourselves to come into more agency.
I recognize this is a very niche endeavor, but the art and craft of maintaining a homepage, with some of your writing and a page that's about you and whatever else over time, of course always includes addition and deletion, just like a garden — you're snipping the dead blooms. I do this a lot. I'll see something really old on my site, and I go, “you know what, I don't like this anymore,” and I will delete it.
But that's care. Both adding things and deleting things. Basically the sense of looking at something and saying, “is this good? Is this right? Can I make it better? What does this need right now?” Those are all expressions of care. And I think both the relentless abandonment of stuff that doesn't have a billion users by tech companies, and the relentless accretion of garbage on the blockchain, I think they're both kind of the antithesis, honestly, of care.
The Builder mindset often eschews policy completely and focuses on the macro issues, rather than the micro complexities. It is a mindset that seeks to find very elaborate, hypothetical-but-definitely-paradigm-shifting, futuristic technology to fix current problems, instead of focusing on a series of boring-sounding and modest reforms that might help people now.
…The worst version of Builder mentality is that their dreams become reality, but instead of maintaining their creations, they simply move onto the next Big Thing, leaving others to deal with the mess they’ve made.
There is a time to build and a time to repair. Repairing what is broken is difficult and important work that requires contextualizing technology and working within creative constraints…If we just keep building without repairing what exists or applying lessons learned along the way, we will continue to spin our wheels as the same problems accumulate and amplify. In this way, our technology may evolve, but our relationship to it (and to each other) can only degrade.
This is how NFTs make me feel: like the future is useless but expensive, and world-altering technology is now in the hands of a culture so aesthetically and spiritually impoverished that it should maybe go back to telling stories around the cooking fire for a while, just to remember how to mean something.
Conventional tech industry product practice will not produce deep enough subject matter insights to create transformative tools for thought.
...The aspiration is for any team serious about making transformative tools for thought. It’s to create a culture that combines the best parts of modern product practice with the best parts of the (very different) modern research culture. You need the insight-through-making loop to operate, whereby deep, original insights about the subject feed back to change and improve the system, and changes to the system result in deep, original insights about the subject.
There are two classes of problems caused by new technology. Class 1 problems are due to it not working perfectly. Class 2 problems are due to it working perfectly.
...Class 1 problems arise early and they are easy to imagine. Usually market forces will solve them. You could say, most Class 1 problems are solved along the way as they rush to become Class 2 problems. Class 2 problems are much harder to solve because they require more than just the invisible hand of the market to overcome them.
...Class 1 problems are caused by technology that is not perfect, and are solved by the marketplace. Class 2 problems are caused by technology that is perfect, and must be solved by extra-market forces such as cultural norms, regulation, and social imagination.
In 1800, if you’d said that you wanted something ‘made by hand’, that would be meaningless - everything was handmade. But half a century later, it could be a reaction against the age of the machine - of steam and coal-smoke and ‘dark satanic mills.’ The Arts and Crafts movement proposed slow, hand-made, imperfect craft in reaction to mass-produced ‘perfection’ (and a lot of other things besides). A century later this is one reason I’m fascinated by the new luxury goods platforms LVMH and Kering, or indeed Supreme. How do you mass-manufacture, mass-market and mass-retail things whose entire nature is supposedly that they’re individual?
...we keep building tools, but also we let go. That’s part of the progression - Arts and Crafts was a reaction against what became the machine age, but Bauhaus and futurism embraced it. If the ‘metaverse’ means anything, it reflects that we have all grown up with this now, and we’re looking at ways to absorb it, internalise it and reflect it in our lives and in popular culture - to take ownership of it. When software eats the world, it’s not software anymore.
Technology is seeing a little return to complexity. Dreamweaver gave way to hand-coding websites, which is now leading into Webflow, which is a lot like Dreamweaver. Evernote give way to minimal Markdown notes, which are now becoming Notion, Coda, or Craft. Visual Studio was “disrupted” by Sublime Text and TextMate, which are now getting replaced by Visual Studio Code. JIRA was replaced by GitHub issues, which is getting outmoded by Linear. The pendulum swings back and forth, which isn’t a bad thing
Even with all the features and plugins, Canvas presumes certain ways of organizing classes that might not be universal, just typical. And if (like me) you’re an atypical user, you have to choose between constantly fighting with the system or gradually doing more and more things the way Canvas wants you to do them. This, by the way, is why it’s never true to say that technologies are neutral and what matters is how you use them: every technology without exception has affordances, certain actions that it makes easy, and other actions that it makes difficult or impossible. A technology whose affordances run contrary to your convictions can rob you of your independence — and any technology deployed on the scale of Canvas will inevitably do that. It will turn every teacher into an obedient Canvas-user. I don’t want to be an obedient Canvas-user.
Increasingly, I think UX doesn't live up to its original meaning of "user experience." Instead, much of the discipline today, as it's practiced in Big Tech firms, is better described by a new name.
Consider, for example, how “broken world thinking” can benefit product design. What if the person (or team) who invented a new technology collaborated with the person (or team) who would one day repair the same technology? What if the innovation stakeholders and the infrastructure stakeholders collaborated closely with the end users? What if every new product designed by a technology company was designed in such as way as to factor in what happens to the product after planned obsolescence?
The Nintendo way of adapting technology is not to look for the state of the art but to utilize mature technology that can be mass-produced cheaply.
This is the reason a Nintendo console never has the fastest chips or the beefiest specs of its generation; instead, its remixes components in an interesting and generative way. Think of the Gameboy’s monochrome screen, the Wii’s motion controller, the Switch’s smartphone form.
[Gunpei Yokoi] is talking about reliability and predictability, in performance and supply alike. He wants the components to be boring, so their application can be daring.
I decided to record every broken interaction I had during one day.
If I decided to invest time into thinning this list down, I could theoretically...reduce this list from 27 down to 24. At least 24 annoyances per day I have to live with. That’s the world WE ALL are living in now. Welcome.
A name retroactively applied to a landmark computer demonstration, presented by Douglas Engelbart on December 9, 1968. The 90-minute presentation essentially demonstrated almost all the fundamental elements of modern personal computing:
What are the effects of this enumeration, of these metrics that count our social interactions? In other words, how are the designs of Facebook leading us to act, and to interact in certain ways and not in others? For example, would we add as many friends if we weren’t constantly confronted with how many we have? Would we “like” as many ads if we weren’t told how many others liked them before us? Would we comment on others’ statuses as often if we weren’t told how many friends responded to each comment?
In this paper, I question the effects of metrics from three angles. First I examine how our need for personal worth, within the confines of capitalism, transforms into an insatiable “desire for more.” Second, with this desire in mind, I analyze the metric components of Facebook’s interface using a software studies methodology, exploring how these numbers function and how they act upon the site’s users. Finally, I discuss my software, born from my research-based artistic practice, called Facebook Demetricator (2012-present). Facebook Demetricator removes all metrics from the Facebook interface, inviting the site’s users to try the system without the numbers and to see how that removal changes their experience. With this free web browser extension, I aim to disrupt the prescribed sociality produced through metrics, enabling a social media culture less dependent on quantification.
In the early 1980’s, English painter David Hockney began creating intricate photo collages that he called “joiners”. His earlier collages consisted of grid-like compositions made up of polaroid photographs. He then switched to photo lab processed 35mm photographs and created collages that took on a shape of their own, creating abstract representations of the scenes he had photographed. The varied exposures of the individual photographs that make up each collage give each work a fluidity and movement that otherwise might not be found.