Tesler’s Law, also known as "The Law of Conservation of Complexity", states that for any system there is a certain amount of complexity which cannot be reduced.<p>No matter which side you choose, complexity just doesn’t go away. All processes have a core of complexity that cannot be designed away. The only question is what handles it: "the system", or "the user".<p>By creating a control, the designer is making a choice, saying to the user in effect, “You handle this.” But if the system has to handle the complexity, it means all kinds of decisions have to be made for the user — your defaults have to be smart, and god help you if you get them wrong.<p>- Medium Article: <a href="https://odannyboy.medium.com/controls-are-choices-7de90363d0dd" rel="nofollow">https://odannyboy.medium.com/controls-are-choices-7de90363d0...</a><p>I tried to follow some of the design law's in <a href="https://hn.boxpiper.com/" rel="nofollow">https://hn.boxpiper.com/</a>, but after reading these, there's a lot of improvements required.