← log
Complexity Is Not the Same as Complication

photo by Unsplash / Unsplash

Apr 10, 2026 · 1 min read

Complexity Is Not the Same as Complication

Some things are hard because they contain many moving parts. Others are hard because we assembled them badly. Those are not the same problem.

#systems#thinking#code

I keep coming back to a distinction that feels obvious once you see it: complexity and complication are not the same thing.

Complexity is what happens when reality has many parts that genuinely interact. A city is complex. A climate is complex. A codebase that supports a lot of real behavior may be complex too, even if it is well designed. You cannot remove that kind of difficulty without removing something real.

Complication is different. Complication is extra friction. It is the layer of confusion added by bad naming, unnecessary steps, hidden assumptions, or systems that make simple things feel harder than they are. Complexity can be inevitable. Complication is usually homemade.

I think this matters because we often treat all difficulty as if it belongs to the world. Then we become strangely respectful of problems we created ourselves. We say something is "just complicated" when what we often mean is that nobody stopped to make it clear.

The useful question, then, is not just "why is this hard?" It is "what kind of hard is this?"

If something is complex, the answer may be better models, patience, and humility. If something is complicated, the answer is often subtraction.

That feels true far beyond code. Some parts of life are dense because they are real. Other parts are dense because we are carrying avoidable knots.

Knowing the difference does not solve the problem.

But it tells you whether to study it more carefully, or start cutting things away.


Photo by Omar Flores on Unsplash

What Finishing TeachesApr 15, 2026What Debugging Reveals About AssumptionsApr 12, 2026The Shape of UncertaintyApr 9, 2026
↑ top