The more constraints one imposes, the more one frees one's self. And the arbitrariness of the constraint serves only to obtain precision of execution.
Sentiment: NEGATIVE
They say that structure is freedom, and in a sense it is. When you're dealing with multiple constraints, you have to figure out what you can get out of that.
Software constraints are only confining if you use them for what they're intended to be used for.
The true self seeks release, not constraint. It doesn't want to be corseted in a sonnet or made to learn a system of musical notations. It wants liberation, which is why very often it fastens on the novel, for the novel seems spacious, undefined, free.
If we can think about not the object, but the process of creating the object, in short, we have no constraints. We have processes in our hands that allow us to create structures at all scales that at one point we couldn't even have dreamed of.
Precision, speed, unambiguity, knowledge of files, continuity, discretion, unity, strict subordination, reduction of friction and of material and personal costs - these are raised to the optimum point in the strictly bureaucratic administration.
Constrained circumstances can bring the best out of you.
I'm phobic about the idea of being constrained.
Because mechanism designers do not generally know which outcomes are optimal in advance, they have to proceed more indirectly than simply prescribing outcomes by fiat; in particular, the mechanisms designed must generate the information needed as they are executed.
Problems are hidden opportunities, and constraints can actually boost creativity.
The principle inherent in the clause that prohibits pointless infliction of excessive punishment when less severe punishment can adequately achieve the same purposes invalidates the punishment.
No opposing quotes found.