TechInfoDepot:What "Ignore all rules" means

If a rule prevents you from improving or maintaining TechInfoDepot, ignore it.

What "Ignore all rules" means
"Rules are mostly made to be broken and are too often for the lazy to hide behind."

- Douglas MacArthur

"Rules are for fools"

- Unknown. (As used by coaches/motivators)

"By all means break the rules, and break them beautifully, deliberately and well. That is one of the ends for which they exist."

- Robert Bringhurst

"The code is more what you call "guidelines" than actual rules."

- Captain Barbossa

"The rules are only barriers to keep children from falling."

- Madame de Staël

"Give me the judgment of balanced minds in preference to laws every time. Codes and manuals create patterned behavior. All patterned behavior tends to go unquestioned, gathering destructive momentum."

- Darwi Odrade

You do not need to read any rules before contributing to TechInfoDepot. If you do what seems sensible, it will usually be right, and if it's not right, don't worry. Even the worst mistakes are easy to correct: older versions of a page remain in the revision history and can be restored. If we disagree with your changes, we'll talk about it thoughtfully and politely, and we'll figure out what to do. So don't worry. Be bold, and enjoy helping to build this free encyclopedia.
 * You are not required to learn the rules before contributing. Yes, we already said that, but it is worth repeating.
 * Don't follow written instructions mindlessly, but rather, consider how the encyclopedia is improved or damaged by each edit (see also Use common sense, below).
 * Rules derive their power to compel not from being written down on a page labeled "guideline" or "policy", but from being a reflection of the shared opinions and practices of many editors (see also TechInfoDepot:Consensus).
 * Most rules are ultimately descriptive, not prescriptive; they describe existing current practice. They sometimes lag behind the practices they describe (see also TechInfoDepot:Product, process, policy).
 * Wikilawyering doesn't work. Loopholes and technicalities do not exist on the Wiki. TechInfoDepot is not a bureaucracy; nor moot court, nor nomic, nor Mao.
 * The spirit of the rule trumps the letter of the rule. The common purpose of building a free encyclopedia trumps both.  If this common purpose is better served by ignoring the letter of a particular rule, then that rule should be ignored (see also TechInfoDepot:The rules are principles).
 * Following the rules is less important than using good judgment and being thoughtful and considerate, always bearing in mind that good judgment is not displayed only by those who agree with you (see also TechInfoDepot:Civility).

History
Ignore all rules is one of the oldest rules on TechInfoDepot, written by Larry Sanger in 2001. The original wording was a bit different from today's version. It said: "If rules make you nervous and depressed, and not desirous of participating in the wiki, then ignore them entirely and go about your business."

Note that while ignoring all rules is alright, it is subtly but importantly different from deliberately breaking them. Meditate on that carefully before you actually apply this rule.

What "Ignore all rules" does not mean
"Pedantry and mastery are opposite attitudes toward rules. To apply a rule to the letter, rigidly, unquestioningly, in cases where it fits and in cases where it does not fit, is pedantry... To apply a rule with natural ease, with judgment, noticing the cases where it fits, and without ever letting the words of the rule obscure the purpose of the action or the opportunities of the situation, is mastery."

- George Pólya

"Ignore all rules – including this one."

Despite its name, "Ignore all rules" does not sabotage the other rules. Its purpose is to keep them from sabotaging what we're doing here: building a free encyclopedia. Rules have zero importance compared with that goal. If they aid that goal, good. If they interfere with it, they are instantly negated.
 * "Ignore all rules" does not mean that every action is justifiable. It is neither a trump card nor a carte blanche. Rule ignorers must justify how their actions improve the encyclopedia if challenged. Actually, everyone should be able to do that at all times. In cases of conflict, what counts as an improvement is decided by consensus.
 * "Ignore all rules" does not stop you from pointing out a rule to someone who has broken it, but do consider that his or her judgment may have been correct, and that they almost certainly thought it was (see also TechInfoDepot:Assume good faith).
 * "Ignore all rules" is not in itself a valid answer if someone asks you why you broke a rule. Most of the rules are derived from a lot of thoughtful experience and exist for pretty good reasons; they should therefore only be broken for good reasons.
 * "Ignore all rules" is not an exemption from accountability. You're still responsible for reasonably foreseeable effects of your actions on the encyclopedia and on other editors.
 * "Ignore all rules" is not an invitation to use TechInfoDepot for purposes contrary to that of building a free encyclopedia (see also TechInfoDepot:About and TechInfoDepot:What TechInfoDepot is not).
 * "Ignore all rules" does not mean there is necessarily an exception to every rule. A typical copyright violation, for instance, does not make for a better free encyclopedia.
 * "Ignore all rules" does not mean that you can violate TechInfoDepot:Office actions without being blocked for disruption.

Use common sense
TechInfoDepot has many rules. Instead of following every rule, it is acceptable to use common sense as you go about editing. Being too wrapped up in rules can cause loss of perspective, so there are times when it is better to ignore a rule. Even if a contribution "violates" the precise wording of a rule, it might still be a good contribution. Similarly, just because something is not forbidden in a written document, or is even explicitly permitted, doesn't mean it's a good idea in the given situation. Our goal is to improve TechInfoDepot so that it better informs readers. Being able to articulate "common sense" reasons why a change helps the encyclopedia is good, and editors should not ignore those reasons because they don't include a bunch of policy shortcuts. The principle of the rules—to make TechInfoDepot and its sister projects thrive—is more important than the letter. Editors must use their best judgment.

Why isn't "use common sense" an official policy? It doesn't need to be; as a fundamental principle, it is above any policy.

There is no common sense
"Good sense is of all things in the world the most equally distributed, for everybody thinks he is so well supplied with it that even those most difficult to please in all other matters never desire more of it than they already possess."

- René Descartes

When advancing a position or justifying an action, base your argument on existing agreements, community foundation issues and the interests of the encyclopedia, not your own common sense. Exhorting another editor to "just use common sense" is likely to be taken as insulting, for good reasons. If in a particular case you feel that literally following a rule harms the encyclopedia, or that doing something which the rules technically allow degrades it, then instead of telling someone who disagrees to use common sense, just focus on explaining why ignoring the rules will improve TechInfoDepot in that instance.

Be careful about citing this principle too aggressively. While it's quite acceptable to explain your own actions by saying, "it seemed like common sense to me," you should be careful not to imply that other editors are lacking in common sense, which may be seen as uncivil. TechInfoDepotns come from diverse ethnic, religious, political, cultural and ideological backgrounds and have vastly different perceptions regarding everything from science to shoe shopping. Other editors are likely to ascribe very different meanings and values to words and concepts than you, so try to state your arguments as fully as possible. Citing concrete policies and guidelines is likely to be more effective than simply citing "common sense" and leaving it at that.