Proposal: Atomic Coding
There has been a dispute about whether Atomic Coding still fits the Stack Exchange model. Atomic Coding has already been closed by a mod because it would require "too much innovation" in terms of implementation of new features. While this has already been dealt with through an edit to the original question, I need to ask: Will Atomic Coding be a fit for the Stack Exchange model?
Here is a step-by-step guide to how Atomic Coding can closely parallel the ideal Stack Exchange model cited in their introductory guide:
Atomic Coding is not meant to be a resting place for "low-quality" questions. It's a place for high-quality answers to FAQs about the basics of programming that Stack Overflow users should know.
Atomic Coding does not require a significantly different amount of collaboration than other Stack Exchange websites. Questions and answers would remain independent from each other, but Atomic Coding would take on a tone of collaboration to strip away less-viable answers and condense answers into final, atomic forms that are the ultimate accessible answers.
Consensus on Atomic Coding is not opinion-based--voting would be based on evidence that the questions being asked are of good form, frequently asked, and deserve a strong, definitive answer. Likewise, answers would be judged based on its terseness, compactness, and readability. Atomic Coding still does not facilitate opinion-decided questions or answers.
Atomic Coding's philosophy is to "don't repeat yourself" and "answer the frequent questions so that they won't be asked." Atomic Coding demands definitive, minimal, but effective answers to common programming problems or questions. It is not a website to punt all "low-quality" questions to.
Contrary to popular opinion on Stack Overflow, questions like "how can I debug this program, please help me" are actually quite valid questions in disguise; it's just they are written with bad form. Atomic Coding seeks to find evidence of common questions like these that are often mistaken as "poor-quality" and give users a helping hand to get them started on doing things "the right way," should they ask for it.
Tags would still play a key role in Atomic Coding, much like any other Stack Exchange site.
tl;dr: While Stack Overflow takes on a reactionary role to questions, Atomic Coding users would be encouraged to be proactive in finding questions that need answers, and then sharing their or collaborating with the community's knowledge to provide a strong, definitive answer that is devoid of cruft.
