Full Width [alt+shift+f] Shortcuts [alt+shift+k]
Sign Up [alt+shift+s] Log In [alt+shift+l]

Improve your reading experience

Logged in users get linked directly to articles resulting in a better reading experience. Please login for free, it takes less than 1 minute.

More from UX Collective

Our human habit of anthropomorphizing everything

Weekly curated resources for designers — thinkers and makers.

2 days ago 5 votes
UX, how can I trust you?

Weekly curated resources for designers — thinkers and makers.

2 weeks ago 13 votes
It’s time for design to think less and feel more

Weekly curated resources for designers — thinkers and makers.

3 weeks ago 16 votes
Why AI (desperately) needs designers

Weekly curated resources for designers — thinkers and makers.

a month ago 18 votes

More in design

METIC Lounge by ADS

As night falls, Metic Bar in Shanghai’s Putuo District stands out from the ordinary. All Design Studio (ADS) transforms the...

yesterday 2 votes
Design for a Small Planet

Back in 1971, “Diet for a Small Planet” by Frances Moore Lappé made it clear the costs of eating meat were far greater than we had assumed. If we wanted the planet to thrive, we needed to shift to a more resource-efficient way to eat. UX Design is going through its own “you cost too […]

yesterday 5 votes
Laconicum’s Museum of Everyday Pleasures

Laconicum, the renowned online cosmetics store, recently took a new step into the physical world with its first pop-up: ‘The...

yesterday 2 votes
Our human habit of anthropomorphizing everything

Weekly curated resources for designers — thinkers and makers.

2 days ago 5 votes
Ecosystems vs. Artifacts: Don’t Break the Web

Here’s Gordon Brander in an article titled “Don't fork the ecosystem”: Most of our software has been shaped by chance decisions made in haste by people who could not have predicted how the system would end up being used today. And if we could rebuild those systems today, knowing what we know now, we’d invent a whole new class of problems for ourselves twenty years from now. Software can be rebuilt, because software is a machine. But a software ecosystem is not a machine. It is a living system. When we attempt to rebuild the ecosystem, we’re making a category error. We confuse the software for the ecological process unfolding around it. Seems akin to hiring and firing. People are not cogs in a machine. Team dynamics are disrupted when people leave, as an ecosystem is being tampered with. When I was a kid, I did not understand why we couldn’t “just” go back to the moon. We’d already done it once before. So if we’d done it before, can’t we just do it again? I thought of it like riding a bicycle: once you know how to do it, can’t you just do it again whenever you want? Only as I grew older did I come to understand that an entire ecosystem of people, processes, tools, organizations, experience, storehouses of knowledge, and more made it possible to go to the moon. And you can’t just turn that back on with the flip of a switch. I was confusing the artifact (a human being on the moon) for the ecosystem that made it possible (NASA, contractors, government officials, technology, etc.) Carrying forward old baggage offends our sense of aesthetics, but hey, that’s how evolved systems work. Chickens still carry around the gene for dinosaur teeth. This is because a living system must be viable at every evolutionary stage. It can never pause, reset, or make a breaking change. The path of evolution is always through the adjacent possible. Lesson: the web isn’t an artifact. It’s an ecosystem. Don’t break the web. Email · Mastodon · Bluesky

3 days ago 5 votes