A brief glance at this SE seems to tell me it's more filled with "why doesn't this code work" questions as opposed to "How could this code work better" (which I believe is the actual point of this SE).
Best way to enforce the intention of this SE?
A brief glance at this SE seems to tell me it's more filled with "why doesn't this code work" questions as opposed to "How could this code work better" (which I believe is the actual point of this SE).
Best way to enforce the intention of this SE?
This is a good question. The rulebook is pretty clear about non-working code:
- Does my question contain code? (Please include the code in the question, not a link to it)
- Did I write that code?
- Is it actual code from a project rather than pseudo-code or example code?
- Do I want the code to be good code, (i.e. not code-golfing, obfuscation, or similar)
- To the best of my knowledge, does the code work?
- Do I want feedback about any or all facets of the code?
I agree that the rules could make it more visible that non-working code is off-topic. But there's people that don't read the manual and then there's people that won't read the manual.
We recently ran a contest here on meta, where the community voted on ad suggestions (at this time it's still showing up on the Community Bulletin). This is our winning entry:
The ad is now in effect on Programmers.SE and Stack Overflow. I find it makes a great job at capturing the site's essence, but there's indeed no explicit emphasis on working code. And the ad is quite successful, too.
We eventually want to have our own blog, which will give us an additional tribune for promoting Code Review and what CR is all about.
That's currently on hold until further notice though.
If anyone has any more ideas, bring them!
As you are talking about enforcing the intention of this SE-Site.
That's what we as Users do everyday, we comment, vote up, down, close and reopen questions, we edit, we chat, we ask, we answer,
And by doing so, everyday, we enforce the intention of what we see as Code Review