I think that there needs to be, both for the developer and the designer, an understanding that rules are made to be broken. Knowing or learning when and how to

I think that there needs to be, both for the developer and the designer, an understanding that rules are made to be broken. Knowing or learning when and how to break them might be beyond the scope of any number of tweet sized aphorisms Lists like this make me want to try and find a huge set of software engineering "bumper stickers" my dad sent me 15 years ago, containing dubious gems like... pi seconds is a nano-century Never debug standing up (predates standing desk fad) Some projects can only be accomplished with fewer than 10 or greater than 100 people, but by no number in-between