On the difference between simple and easy
Author Name
A line worth keeping, about why the simplest option so rarely feels like the convenient one.
Simple is not the same as easy. Simple describes how many things are tangled together. Easy describes how close something is to what you already know.
Replace this quotation with one of your own, and put the attribution in the `source` field of the frontmatter.
Why I keep coming back to it
Almost every architecture argument I have been in was really this distinction going unnoticed.
The option that is easy is the one that resembles what the team did last time. The option that is simple is the one with fewer things braided together. They are often not the same option, and the easy one wins by default because it is the one that can be started this afternoon.
Naming the difference does not settle the argument. It does make it possible to have the right argument: are we choosing this because it is untangled, or because it is familiar?