# The Amish and cars

2018-06-18

> The Amish use us as an experiment. They watch what happens when we adopt new technology, and then decide whether that’s something they want to adopt themselves. I asked one Amish person why they didn’t use automobiles. He simply smiled and turned to me and said, “Look what they did to your society.” And I asked what do you mean? “Well, do you know your neighbor? Do you know the names of your neighbors?” And, at the time, I had to admit to the fact that I didn’t.

> […]

> At the beginning of the age of the automobile, nobody said, All right: 30,000 people a year are going to die. Is that a decision we want to make? What did happen is a very intense discussion about whether a car should be allowed on the road and who should be at fault when a car drives over a four-year-old in the street.

> In the 1930s, we ended up as a society deciding that four-year-olds should be the one to blame. We began to train people even before they began to speak about how to cross the street and how to avoid it in the street. We redesigned our world to be safe for automobiles and dangerous for children.

> The Amish understand a life-changing truth about technology the rest of us don’t (cache)

Interesting article which resonates with my writings 10 days ago and my current reevaluation of technologies. Communities or individuals depicted as weirdos might be part of a future we try to hide to ourselves.

A more resilient future?

Other articles in English: On caching links, Bushcraft retrospective, Into the Raft, Into the Bugs, Meritocracy crisis, The Seller, the Teacher and the Wise, Into the Good, Into the Mice, Into the Camp, Into the Wind, Into the Snow, Into the Cold, Async Python Frameworks, Distributed teams, Into the Wild, Without JavaScript, Inclusive Python, Micro-cultures and governance, Resilient Web and Tools, Bitcoin and energy, Team building, Inclusive developer, Cultural Intimacy, Tools and teams, Senior developer, Slow Data, Inclusive communities, Delivery and value(s), Collaboration debt, Communities and leadership, Specifications and APIs. Oh, and most of the 2018 thoughts.