Suggest an article to hacker news. If the title does not pass spell check, is inconsistent, or is of unreasonable length, it will be rejected by the community. An title out of "style" will not be as successful as one in style with the community.
Suggest a patch to an open source project. If the code is not bug free, documented, and readable, it will be rejected.
Report a software bug. Writing a bug report that will be taken serious is almost an art.
Suggest a answer/question to stackexhange board. If the text is not readable, spam free, or on topic, it will be rejected.
Each community has a unique set of requirements for new contributions. It often takes different skill sets to successful contribute in a meaningful way. Most if not all communities suggest new users to first read and observe before making new contribution. Many forums makes this specific point in FAQ's and user guides.
Wikipedia's requirement on new article is harsh, but I would still put them as less harsh than adding a patch to a open source program or writing a bug report.
In fact, to make it simpler: what page did you edit on Wikipedia in which any of these things happened? The nice thing about Wikipedia strife is that it's all archived, so let's talk about specifics.
It's definitely much easier to wear people down if you're someone who is always on Wikipedia. In fact you can further wear them down by getting into a "Revert War" with the conflicting author. Since after 3 reverts you risk getting temporarily banned on Wikipedia for revert warring, after the 3 reverts you have to go to some random committee page on Wikipedia to settle the dispute.
The most important rule of editing Wikipedia is probably unspoken: start small and watch how the community reacts. Adding content and getting it reverted isn't a demerit; it's only painful if you are attached to the content. If you're going to start editing WP by getting involved with high-traffic pages, make your first edits small enough that you won't be upset when they're reverted.
Also, they do tend to play into the hands of misuse by PR companies and the like. Its very easy, for instance, for a PR company to find a few 'reliable' news sources to say something online, then add it to wikipedia (often removing opposing views) under the banner of 'Verifiability'. It doesn't even matter if it is completely untrue.... I'm sure there are ways at stopping this (like being stricter on 'reliability') if Wikimedia were interested in trying.
They could also do with creating a better front-end page for understanding/browsing the various policies and guidelines.
If, on the other hand, you dive in and start editing the main Mac OS_X article, you only need one more rule of thumb: start small and go slow. A lot of Wikipedia-vs-nerd grief arises from people making their first or second "serious" edit, committing themselves to many carefully written paragraphs of text, and finding those grafs shredded by other editors.
Cite sources. On heavily-trafficked articles, start small & go slow. This does not seem like a particularly egregious amount of internal politics to understand.
In my admittedly limited experience, `rules' are often exploited to change (or expunge) articles with anything that remotely challenges the opinions of that select cabal of `veteran' editors.