Why Things Work Badly, Strangely, or Unexpectedly in Modern Life

We live in the most technologically advanced period in human history and somehow a website takes longer to load than it did in 2008. Your phone has more computing power than the hardware that landed humans on the moon, and you are using it to wait for a customer support chatbot to understand that you said "cancel subscription," not "keep subscription forever please."

This is not a coincidence. It is not laziness. It is not stupidity.

It is something much more interesting.

---

Most things were built for something else entirely

Here is the thing nobody tells you: a lot of the technology and systems you use every day were not built for the purpose you use them for. They were built for something completely different, succeeded, and then just... stayed. Like a houseguest who came for the weekend and is now on your lease.

The most incredible example is Android.

Android was not originally designed to be a phone operating system. Andy Rubin and his co-founders built it in 2003 as an operating system for digital cameras. The pitch to investors was: cameras should connect to the internet, share photos automatically, and have a smart interface. When that funding pitch failed, they pivoted. Google acquired them in 2005. The camera OS became the world's most-used mobile operating system.

The phone in your pocket, which you use for maps, banking, video calls, payments, and watching people fall off skateboards, is running software that was conceived to let your Canon upload photos to a PC.

Android is not even unusual. This is basically how technology works.

The pattern is real. Something gets built, the original purpose flops or evolves, and the thing finds a new home. Except now it carries the weight of its original design, the assumptions baked in, the limitations inherited from a different context, the quirks that made sense back then and make zero sense now.

QWERTY is the most famous example of this. The keyboard layout on every device you own was designed in the 1870s partly to slow down fast typists so typewriter keys would not jam. The mechanical constraint is gone. The layout survived anyway, because at some point enough people learned QWERTY that switching became a coordination problem no individual could solve alone.

You are currently typing at 1870s typewriter speed, on purpose, because of a problem that no longer exists.

---

The real issue: most things are optimized for someone else

Once you accept that things are often built for different purposes, the second realization hits harder.

Most things are not broken. They are working exactly as designed. Just not for you.

This is the hidden truth of modern frustration. When something feels stupid or annoying, the natural reaction is to assume incompetence. But a lot of the time, the thing is functioning perfectly as optimized. You are simply not the primary optimization target.

The self-checkout machine is a useful one to sit with. It is marketed as faster and more convenient. But what it actually does is transfer labor from the store to you, for free, while the store reduces payroll. You became an unpaid employee of the supermarket and the framing was "empowerment."

None of this means these companies are evil. It means they are optimizing, and optimization has a target. The target is rarely your comfort.

---

Technology does not remove friction. It relocates it.

There is a temptation to think that each wave of technology makes life genuinely easier, full stop. More convenient. Less effortful. Simpler.

That is not quite right.

Technology tends to remove one kind of friction and create another, usually less visible, kind. The problem does not disappear. It migrates.

We no longer wait weeks for letters. We now manage an inbox that never empties and a psychological anxiety about unread messages that earlier generations simply did not have. The waiting was replaced by the monitoring.

We have navigation everywhere. But studies consistently show that people who use GPS navigation have worse spatial memory and a reduced sense of direction compared to those who do not. The effortful thing (learning routes) was the thing that built the capability.

We have more entertainment than any human civilization in history, available instantly, for almost free. We also have something called "doomscrolling" and a documented collapse in average attention spans.

Every solved problem tends to create a new problem. The new problem is usually less visible because it is internal, psychological, or distributed across many people rather than obviously mechanical.

---

Why complexity only goes in one direction

You may have noticed that systems rarely get simpler over time. Software gets heavier. Government forms get longer. Customer support flows get more convoluted. Airports get larger and somehow slower.

There is a reason for this. It is almost a law.

Every rule, feature, regulation, or process that gets added to a system was added because something went wrong. An edge case appeared. A user complained. A regulator stepped in. A team wanted to prevent a specific failure.

Each of those additions made sense in isolation. In aggregate, they produce a machine that no single person fully understands.

Government websites look ancient because replacing them is genuinely risky. Ancient systems process real money, real identities, real benefits. A failed migration costs far more than a bad UI. The ugly interface is not incompetence. It is caution dressed badly.

Roads get dug up and repaired, then dug up again a week later, because the gas utility and the telecoms company and the water board are all on different budget cycles and none of them coordinates with the road authority before work begins. Each individual repair made perfect bureaucratic sense. Together they are a farce.

---

The adding roads problem

One of the most counterintuitive ideas in this space comes from transport planning. It is called Braess's Paradox.

In 1968, mathematician Dietrich Braess proved mathematically that adding a new road to a traffic network can, under certain conditions, make traffic worse for everyone. Not just locally. For everyone, on every route.

This has since been observed in real cities. In 1990, New York City closed 42nd Street for Earth Day and traffic actually improved. When Seoul demolished an elevated highway in 2003, traffic did not get worse as predicted. It got better.

The reason is that individual drivers optimize their own route, and when you give everyone a new shortcut, everyone takes it, eliminating the advantage and creating a new bottleneck. The system optimum and the individual optimum are not the same thing.

This happens everywhere, not just in traffic:

• Adding more features to an app can make the core use case harder to find
• Adding more information to a form can reduce completion rates
• Adding more meetings to improve communication can reduce the time available for actual work
• Adding more choice to a menu can cause decision paralysis and reduce customer satisfaction

More is not always more. Sometimes the system works better with less, and the act of improvement makes things worse.

---

The philosophical bit

We imagine progress as a straight line. Old world: bad, painful, limited. New world: better, easier, smarter. Each generation inherits a better starting position.

Reality is stranger than that. Progress is real, but it does not solve problems so much as it trades them.

Every era has its specific burdens. They simply change shape. The person in 1850 had no inbox anxiety, but they also died of infections that are now curable with cheap antibiotics. The person in 2026 has seamless communication and severe attention fragmentation. Both are real. Neither is simply better or worse. They are different.

What changes over time is not the amount of friction in life. What changes is which specific frictions you are dealing with, and which invisible infrastructure makes them tolerable.

The really interesting question is not "why is this broken?" but something harder:

Who benefits from this design? What tradeoff caused this? What problem was solved by creating this new problem? And is this actually broken, or just optimized elsewhere?

Those questions do not make the frustration disappear. But they do something more useful: they make the frustration legible. Once you see the incentive, the weird thing stops feeling random.

---

A final example to end on

Mirrors in elevators.

In the 1950s, elevator installations in Manhattan skyscrapers triggered a wave of complaints. The elevators were too slow. People were furious. Building managers lobbied elevator manufacturers for faster lifts. Engineers were brought in.

The engineers determined the elevators were already near peak mechanical speed. Making them faster would require enormously expensive infrastructure upgrades.

A psychologist suggested something different. Install mirrors in the elevators.

The complaints stopped almost immediately.

The elevators did not get faster. The wait did not get shorter. What changed was the experience of waiting. People had something to do: check their appearance, notice other people, exist slightly more entertainingly for thirty seconds. Perceived time slowed down. Real time stayed the same. The problem was not the elevator. The problem was boredom, and boredom was much cheaper to solve.

This is perhaps the best metaphor for modern design. Half the solutions around you are mirrors. The problem was not fixed. The experience of the problem was managed.

Knowing that does not mean you should be cynical about it. Sometimes a mirror in an elevator is exactly the right solution. But it is worth knowing the difference between a problem that was solved and a problem that was made more comfortable to live with. Most of what we call progress is the second thing.

And somehow, that is both slightly depressing and completely fine.