Simple Made Easy

The talk earns its length by giving two overloaded words different jobs. “Simple” describes relationships between parts; “easy” describes how close something is to our current understanding.

The practical question is not whether a system has many files or dependencies. Ask whether one decision forces you to understand, change, or coordinate another unrelated decision.

The talk is strongest as a design vocabulary, not as a universal rejection of objects, libraries, or state. The right test is whether a dependency keeps concerns separate in the system you actually operate.