> I had trouble editing technical topics I was familiar with, too, and found it incredibly aggravating. I'd write demonstrably true, helpful, factual content ab

> I had trouble editing technical topics I was familiar with, too, and found it incredibly aggravating. I'd write demonstrably true, helpful, factual content about something only to have it struck for lack of sourcing. > It took awhile to get through my head the model of the project, which included as a basic premise that I, as an editor, am not a valid source. It seems to me that the correct response to this is to mark the content as needing citations (or to look up the citations oneself), not to knee-jerk delete it every time. Well-cited material is best, but at least for uncontroversial technical subjects, poorly-cited but nonetheless accurate material is a lot better than nothing. There's another problem I've seen, particularly in non-technical subjects, with information that is so broadly accepted that nobody ever bothers to formally define it, so it's not allowed on Wikipedia. For example, in the fantasy genre, "high fantasy" broadly meant epic, heroic, good-vs-evil stuff (Lord of the Rings) and "low fantasy" broadly meant gritty shades-of-grey stuff (Fafhrd and the Grey Mouser, Thieves' World, Song of Ice and Fire). The terms were used this way for decades throughout the genre, and were so intuitive that no one needed to explicitly define them. In 1971, Lloyd Alexander wrote an essay that used "high fantasy" to, roughly, describe fantasy that takes place in an imaginary world, rather than in our own. This usage was never common or influential...until someone wrote a Wikipedia article about it, and used that one source to block any attempts to mention the original definition for many years. Now the "high fantasy" and "low fantasy" articles are conflicting muddles of the two different definitions, and the confusion has inevitably leaked into off-Wikipedia discussion.