Welcome to the staging ground for new communities! Each proposal has a description in the "Descriptions" category and a body of questions and answers in "Incubator Q&A". You can ask questions (and get answers, we hope!) right away, and start new proposals.
Are you here to participate in a specific proposal? Click on the proposal tag (with the dark outline) to see only posts about that proposal and not all of the others that are in progress. Tags are at the bottom of each post.
Comments on Home Improvement: Is it necessary to expand acronyms like OSB?
Parent
Home Improvement: Is it necessary to expand acronyms like OSB?
There are some acronyms related to home improvement that are very well known: OSB, MDF, PVC. Most people who know the material they refer to, know the acronym. In fact, I would guess that a lot of people know the acronym but not what it stands for.
On a board about home improvement, it would be tedious to spell out oriented strand board every time. It would be like spelling out personal identification number on a security site, or automated teller machine on a banking site. Moreover, I would expect that people who don't know the acronym would simply use a search engine, which returns the correct result for these (and it didn't, adding "home improvement" certainly would). But this is all just my opinion.
For people interested in participating in the Home Improvement proposal, what do you think is the best option and why?
- Change nothing, let people use well-known acronyms without spelling them out.
- Require people to spell out all acronyms, no exceptions. Downvote and comment on questions that don't.
- Create tags for each acronym, like
oriented-strand-board. Ensure the tag mentions both the full name, the acronym (I'm assuming typingosbcan be made to still suggestoriented-strand-board) and an appropriate reference site like the wikipedia page. - Something else (please explain in your answer).
Post
Personal opinion, not speaking for the team:
There is a tension between being accessible to all, on the one hand, and assuming a baseline of knowledge in a site's topic. On a software-development site no one would expect you to explain what object-oriented programming is if you asked a question about inheritance. If you asked a question about configuring Eclipse no one would expect you to explain what Eclipse or an IDE is. At the other extreme, if you asked a question about implementing an obscure algorithm, people might expect you to link to or otherwise explain it. On an electrical-engineering site you shouldn't have to explain what voltage is, but might need to explain what an RMS detector is or spell it out. On a home-improvement site I don't think anybody would expect you to explain what a band saw or galvanized nails are, but for a question that depends on an obscure building code, people would probably expect some details.
I participated in another community in the past that was prone to jargon, and the convention we arrived at was: if the term will be understood by anybody who would be interested in the question, then it's ok, and otherwise find a way to add some explanation or context. We sometimes had expert-level questions on obscure edge cases that required precise technical terms where, to a beginner, those terms were the least of the barriers -- if you didn't have the background knowledge in that topic to begin with, you weren't going to understand the question no matter how carefully the technical terms were explained. Meanwhile, if those explanations had been required every time, some of those questions wouldn't have been asked at all.
All of this is incredibly subjective. We don't have lists of things that are basic knowledge and things that require explanation. I didn't know what OSB was when I read a question about it, but the title of the question referred to "engineered wood" (and there was a tag), so I was able to understand the question. If there were something specific, in the question's context, about this particular type of engineered wood compared to other types, that would be something that would benefit from clarification. If OSB is the only, or main, type of engineered wood used for (in this case) siding, then I don't think it requires more detail.
But if someone asks for more information, it's worth seeing if there's a way to provide it without it being burdensome. Sometimes it's worth editing in a few more words; other times replying to the comment might be enough to help the newcomer with a term most community members will already know. It's a judgement call. In this case there was a tag, so that might be a good place to expand "OSB" once, rather than in every associated question, while describing engineered wood.
1 comment thread
2 comment threads